[no] lag [lag-id]
config
Supported on all 7210 SAS platforms as described in this document
This command enables the context for configuring Link Aggregation Group (LAG) attributes.
A LAG can be used to group multiple ports into one logical link. The aggregation of multiple physical links allows for load sharing and provides seamless redundancy. If one of the links fails, traffic will be redistributed over the remaining links.
There are three possible settings for autonegotiation:
‟on” or enabled with full port capabilities advertised
‟off” or disabled where there is no autonegotiation advertisements
‟limited” where a single speed/duplex is advertised.
When autonegotiation is enabled on a port, the link attempts to automatically negotiate the link speed and duplex parameters. If autonegotiation is enabled, the configured duplex and speed parameters are ignored.
When autonegotiation is disabled on a port, the port does not attempt to autonegotiate and will only operate at the speed and duplex settings configured for the port. Note that disabling autonegotiation on gigabit ports is not allowed as the IEEE 802.3 specification for gigabit Ethernet requires autonegotiation be enabled for far end fault indication.
If the autonegotiate limited keyword option is specified the port will autonegotiate but will only advertise a specific speed and duplex. The speed and duplex advertised are the speed and duplex settings configured for the port. One use for limited mode is for multispeed gigabit ports to force gigabit operation while keeping autonegotiation is enabled for compliance with IEEE 801.3.
The system requires that autonegotiation be disabled or limited for ports in a LAG to guarantee a specific port speed.
The no form of this command deletes the LAG from the configuration. Deleting a LAG can only be performed while the LAG is administratively shut down. Any dependencies such as IP-Interfaces configurations must be removed from the configuration before issuing the no lag command.
The LAG identifier, expressed as a decimal integer.
[no] dynamic-cost
config>lag
Supported on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables OSPF costing of a Link Aggregation Group (LAG) based on the available aggregated operational bandwidth.
The path cost is dynamically calculated based on the interface bandwidth. OSPF path cost can be changed through the interface metric or the reference bandwidth.
If dynamic cost is configured, then costing is applied based on the total number of links configured and the cost advertised is inversely proportional to the number of links available at the time. This is provided that the number of links that are up exceeds the configured LAG threshold value at which time the configured threshold action determines if, and at what cost, this LAG will be advertised.
For example:
Assume a physical link in OSPF has a cost associated with it of 100, and the LAG consists of four physical links. The cost associated with the logical link is 25. If one link fails then the cost would automatically be adjusted to 33.
If dynamic cost is not configured and OSPF autocost is configured, then costing is applied based on the total number of links configured. This cost will remain static provided the number of links that are up exceeds the configured LAG threshold value at which time the configured threshold action determines if and at what cost this LAG will be advertised.
If dynamic cost is configured and OSPF autocost is not configured, the cost is determined by the cost configured on the OSPF metric provided the number of links available exceeds the configured LAG threshold value at which time the configured threshold action determines if this LAG will be advertised.
If neither dynamic-cost nor OSPF autocost are configured, the cost advertised is determined by the cost configured on the OSPF metric provided the number of links available exceeds the configured LAG threshold value at which time the configured threshold action determines if this LAG will be advertised.
The no form of this command removes dynamic costing from the LAG.
no dynamic-cost
encap-type {dot1q | null | qinq}
no encap-type
config>lag
Supported on all 7210 SAS platforms as described in this document
This command configures the encapsulation method used to distinguish customer traffic on a LAG. The encapsulation type is configurable on a LAG port. The LAG port and the port member encapsulation types must match when adding a port member.
If the encapsulation type of the LAG port is changed, the encapsulation type on all the port members will also change. The encapsulation type can be changed on the LAG port only if there is no interface associated with it. If the MTU is set to a non default value, it will be reset to the default value when the encap type is changed. All traffic on the port belongs to a single service or VLAN.
On the 7210 SAS-D ETR, 7210 SAS-Dxp, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, the qinq encapsulation type can be configured for both access and access-uplink port LAGs. The null and dot1q encapsulation types can be specified only for access port LAGs.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the null and dot1q encapsulation types can be specified for network port LAGs. The dot1q and qinq encapsulation types can be specified for hybrid port LAGs.
The no form of this command reverts the default.
null
Specifies that the ingress frames will carry 802.1Q tags where each tag signifies a different service.
Specifies that the ingress frames will not use any tags to delineate a service. As a result, only one service can be configured on a port with a null encapsulation type.
Specifies QinQ encapsulation.
hold-time down hold-down-time
no hold-time
config>lag
Supported on all 7210 SAS platforms as described in this document
This command specifies the timer, in tenths of seconds, which controls the delay between detecting that a LAG is down (all active ports are down) and reporting it to the higher levels.
A non-zero value can be configured, for example, when active/standby signaling is used in a 1:1 fashion to avoid informing higher levels during the small time interval between detecting that the LAG is down and the time needed to activate the standby link.
0
Specifies the hold-time for event reporting.
lacp [mode] [administrative-key admin-key] [system-id system-id] [system-priority priority]
config>lag
Supported on all 7210 SAS platforms as described in this document
This command enables the Link Aggregation Control Protocol (LACP) mode for aggregated Ethernet interfaces only. Per the IEEE 802.3ax standard (formerly 802.3ad), the LACP provides a standardized means for exchanging information between Partner Systems on a link. This allow their Link Aggregation Control instances to reach agreement on the identity of the Link Aggregation Group to which the link belongs, move the link to that Link Aggregation Group, and enable its transmission and reception functions in an orderly manner. LACP can be enabled on a maximum of 256 ports.
no lacp
Specifies the mode in which LACP will operate.
Specifies an administrative key value to identify the channel group on each port configured to use LACP. This value should be configured only in exceptional cases. If it is not specified, a random key is assigned.
Specifies a 6 byte value expressed in the same notation as MAC address
Specifies the system priority to be used for the LAG in the context of the MC-LAG.
[no] lacp-xmit-interval {slow | fast}
config>lag
Supported on all 7210 SAS platforms as described in this document
This command specifies the interval signaled to the peer and tells the peer at which rate it should transmit.
fast
Specifies that packets will transmit every 30 seconds.
Specifies that packets will transmit every second.
[no] lacp-xmit-stdby
config>lag
Supported on all 7210 SAS platforms as described in this document
This command enables LACP message transmission on standby links.
The no form of this command disables LACP message transmission. This command should be disabled for compatibility when using active/standby groups. This forces a timeout of the standby links by the peer. Use the no form if the peer does not implement the correct behavior regarding the lacp sync bit.
lacp-xmit-stdby
port port-id [port-id …up to n total] [priority priority] [subgroup sub-group-id]
no port port-id [port-id …up to n total]
config>lag
Supported on all 7210 SAS platforms as described in this document
This command adds ports (links) to a Link Aggregation Group (LAG).
The port configuration of the first port added to the LAG is used as a basis to compare to subsequently added ports. If a discrepancy is found with a newly added port, that port is not added to the LAG.
The maximum number of ports allowed in a LAG depends on the platform. The following are the limits per platform:
On the 7210 SAS-D and 7210 SAS-Dxp, a maximum of four 1 GE ports can be added to or removed from the LAG. The 7210 SAS-Dxp also supports up to two 10 GE ports in a LAG.
On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, a maximum of three 1 GE ports can be added to or removed from the LAG.
On the 7210 SAS-K 3SFP+ 8C, a maximum of two 10 GE ports can be added to or removed from a LAG.
All ports added to a LAG must share the same characteristics (speed, duplex, and so on). An error message is displayed when adding ports that do not share the same characteristics. Hold timers must be 0. Ports that are part of a LAG must be configured with autonegotiation set to limited mode or disabled. No ports are defined as members of a LAG.
The no form of this command removes ports from the LAG.
Specifies the port ID configured or displayed in the slot/mda/port format.
Specifies the port priority used by LACP. The port priority is also used to determine the primary port. The port with the lowest priority is the primary port. In the event of a tie, the smallest port ID becomes the primary port.
Specifies a LAG subgroup. Subgroups in a LAG must be configured on only one side of the LAG, not both. Having only one side perform the active/standby selection guarantees a consistent selection and fast convergence. The active/standby selection is signaled through LACP to the other side. The hold time should be configured when using subgroups to prevent the LAG going down when switching between active and standby links, in the case where no links are usable for a short time, especially in case a subgroup consists of one member.
port-threshold value[action {down}]
no port-threshold
config>lag
Supported on all 7210 SAS platforms as described in this document
This command configures the behavior for the Link Aggregation Group (LAG) if the number of operational links is equal to or below a threshold level.
The no form of this command reverts to the default values.
‟0” action down
Specifies the decimal integer threshold number of operational links for the LAG at or below which the configured action will be invoked. If the number of operational links exceeds the port-threshold value, any action taken for being below the threshold value will cease.
Specifies the action to take if the number of active links in the LAG is at or below the threshold value.
If the number of operational links is equal to or less than the configured threshold value and action down is specified, the LAG is brought to an operationally down state. The LAG is considered as operationally up only when the number of operational links exceeds the configured threshold value.
selection-criteria [{highest-count | highest-weight | best-port}] [slave-to-partner]
no selection-criteria
config>lag
Supported on all 7210 SAS platforms as described in this document
This command specifies which selection criteria should be used to select the active sub-group.
highest-count
Specifies sub-group with the highest number of eligible members.
Specifies sub-group with the highest aggregate weight.
Specifies the selection criteria used with ‟power-off” mode of operation. The sub-group containing the port with highest priority port. In case of equal port priorities the sub-group containing the port with the lowest port-id is taken
Specifies that, together with the selection criteria, the slave-to-partner keyword should be used to select the active sub-group. An eligible member is a lag-member link which can potentially become active. This means it is operationally up (not disabled) for use by the remote side. The slave-to-partner parameter can be used to control whether or not this latter condition is taken into account.
standby-signalling {lacp | power-off}
no standby-signalling
config>lag
Supported on all 7210 SAS platforms as described in this document
This command specifies how the state of a member port is signaled to the remote side when the status corresponding to this member port has the standby value.
lacp
Specifies that LACP protocol is used to signal standby links of the LAG.
The laser of the standby links in the LAG are shutoff to indicate standby status. It allows user to use LAG standby link feature without LACP, if the peer node does not support LACP.