Enables the switch to configure port link aggregation, or load sharing. By using link aggregation, you use multiple ports as a single logical port. Link aggregation also provides redundancy because traffic is redistributed to the remaining ports in the LAG (Link Aggregation Group) if one port in the group goes down. LACP allows the system to dynamically configure the LAGs.
The port-based keyword was added to the command to support the creation of port-based load sharing groups.
| port | Specifies the master logical port for a load-sharing group or link aggregation group (LAG). |
| port_list | Specifies one or more ports or slots and ports to be grouped to the logical port. |
| address-based | Specifies link aggregation by address-based algorithm. |
| L2 | Specifies address-based link aggregation by Layer 2. This is the default value. |
| L3 | Specifies address-based link
aggregation by Layer 3. Note: The L3 algorithm
will be deprecated. Selection of L3 behaves the same as L3_L4.
The inclusion of Layer 4 ports for distribution is not available
on a per group basis. The inclusion of Layer4 ports for
distribution is controlled globally for all LAGs in a switch via
the configure forwarding
sharing [L3 | L3_L4] command.
|
| L3_L4 | Specifies address-based link
aggregation by Layer 3 IP plus Layer4 port. Note: The inclusion of Layer4 ports for
distribution is not available on a per group basis. The
inclusion of Layer4 ports for distribution is controlled
globally for all LAGs in a switch via the configure forwarding sharing
[L3 | L3_L4] command.
|
| custom | Selects the custom link
aggregation algorithm configured with the following command:
configure sharing
address-based custom [ipv4 [L3-and-L4 | source-only |
destination-only | source-and-destination] | hash-algorithm
[xor | crc-16]]. The configuration of the custom option applies to all LAGs on the switch. |
| port-based | Supports the creation of port-based load sharing groups. |
| all | All active members of the group are eligible for distribution on all slots in the switch. |
| local-slot | If there are one or more active members of the group on the slot where traffic is received, distribution wil be restricted to these local-slot members. |
| port-lists | If there are one or more active members of the group in the configured distribution port list for the slot on which traffic is received, distribution will be restrcited to these configured ports. |
| resilient-hashing | Enables the resilient hashing hardware-based capability that minimizes the remapping of flows to aggregator member ports during aggregator member changes. |
| lacp | Specifies dynamic link aggregation, or load sharing, using the LACP. |
| health-check | Specifies a health check type of link aggregation group. |
Disabled.
Link aggregation, or load sharing, allows you to increase bandwidth and availability between switches by using a group of ports to carry traffic in parallel between switches. The aggregation algorithm allows the switch to use multiple ports as a single logical port. For example, VLAN (Virtual LAN)s see the link aggregation group (LAG) as a single logical port.
Note
All ports that are designated for the LAG must be removed from all VLANs prior to configuring the LAG.You can enable and configure dynamic link aggregation, using LACP or health-check link aggregation. Static link aggregation is the default link aggregation method.
Note
Always verify the LACP configuration by issuing the show ports sharing command. Look for the ports listed as being in the aggregator.If a port in a LAG fails, traffic is redistributed to the remaining ports in the LAG. If the failed port becomes active again, traffic is redistributed to include that port.
Link aggregation must be enabled on both ends of the link, or a network loop will result.
Any attempt to enable sharing on ports that have an MLAG (Multi-switch Link Aggregation Group) configuration is denied with following error message:
ERROR: Sharing configuration on MLAG ports cannot be modified. Use "disable mlag port <port>" to remove port from MLAG group first.
Note
See the appropraite volume of the ExtremeXOS 22.3 User Guide for information on the interaction of port-based ACLs and LAGs of ports.LAGs are defined according to the following rules:
Link aggregation, or load-sharing, algorithms allow you to select the distribution technique used by the LAG to determine the output port selection. Algorithm selection is not intended for use in predictive traffic engineering.
ExtremeXOS switches use address based algorithms to determine which physical port in the LAG to use for forwarding traffic out of the switch. Refer to configure sharing address-based custom for more information on using addressing information.
For Port-based load sharing:
Note
If you attempt to create a port-based load sharing group with more than 16 possible aggregator ports, the following message will be displayed:Error: The system can have a maximum of 16 ports in a load sharing group withthe configured algorithm.This message indicates enforcement of the limit of 16 aggregator ports in a port-based LAG. Existing error messages are also used to enforce the 16 aggregator port limit for port-based load sharing groups modified by the configure sharing port add portsport_list command.
You cannot enable sharing on ports that have MVRP enabled.
The following guidelines apply to link aggregation on all switches:
This command was first available in ExtremeXOS 10.1.
The address-based algorithm was added in ExtremeXOS 11.0.
The L2 and L3 optional parameters were added in ExtremeXOS 11.1.
IPv6-compatibility was added in ExtremeXOS 11.2.
Dynamic link aggregation, using LACP, was added in ExtremeXOS 11.3.
The L3_L4 optional parameter was added in ExtremeXOS 11.5.
SummitStack functionality was added in ExtremeXOS 12.0.
Health-check link aggregation was added in ExtremeXOS 12.1.3.
The custom keyword was added in ExtremeXOS 12.3.
The port-based keyword was added in ExtremeXOS 15.4.
The resilient-hashing keyword was added in ExtremeXOS 21.1.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB