LAG Overview
A link aggregation group (LAG) combines multiple physical links into a single logical interface which is referred to as a bundle interface. These physical links are connected between two devices. The device uses LACP protocol to bundle the member links and create high speed connections. Although a bundle can be created based on static configuration, bandwidth can be increased by adding member links to the bundle. This also allows load sharing among the physical links. Thus, a group of ports combined together is called a link aggregation group, or LAG.
The LAG interface combines the bandwidth of the individual member links. The properties like speed and bandwidth of the individual member links should be the same to make it part of that LAG. The traffic which is directed towards the LAG interface is sent on the individual member links. This traffic is not pinned to a specific member link but rather determined by a specific flow. This hash could be calculated based on various fields in the packet.
LAG Interface Modes
The LAG interface could be formed statically or dynamically. LACP protocol helps to bring up the interface dynamically. The two modes of LAG interface are:
-
Static LAG: In this mode, the member links do not initiate or process any of the LACP packets received. The device brings up the LAG interface without LACP negotiation.
-
Dynamic LAG: In this mode, the member links process the LACP packets received. Under this mode, there two sub modes:
-
active: LACP packets are generated on each of the member links on the transmit side.
-
passive: LACP packets are generated on the member link in response to the LACP packet received. That means, at least one side of the LAG should be configured as
activeto bring up the LAG interface.
-
Layer2 and Layer 3 Interfaces
LAG interfaces can be used as layer 2 and layer 3 interfaces. A regular layer 2 or layer 3 interface can be created on top of the single LAG interface. These interfaces can be divided based on 802.1q VLAN ID’s. Multiple layer 3 interfaces can be created and each of them can be associated with different instances.
LACP (Link Aggregation Control Protocol)
LACP is part of an IEEE specification (802.3ad) that allows several physical ports to be grouped to form a single logical interface. LACP allows a switch to negotiate an LAG by sending LACP packets on its member links. It negotiates the various configuration parameters to bring up the individual member links.
Interface Holddown
The Interface Holddown feature remains supported when interfaces are grouped in a LAG. For more information about the Interface Holddown feature, see Interface Holddown.
Guidelines and Limitations
-
You cannot configure logical interfaces on a LAG member ports.
-
You cannot configure L2X on a LAG member port.
LAG Hashing Algorithm
The LAG hashing algorithm distributes traffic across multiple paths or links for load balancing. It achieves this by using various packet header fields (like IP addresses, port numbers, or MAC addresses) to generate a hash value, ensuring probability and an equitable distribution of network traffic.
The following table lists the packet header fields that are used by the LAG hashing algorithm to generate a hash value, which in turn determines how traffic is distributed. A tick (✓) indicates that the field is used by the hashing algorithm. A cross mark (✗) indicates that the field is not used by the hashing algorithm.
IPv4 UDP/TCP
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling IPv4 UDP/TCP traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
Source IP Address (SIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination IP Address (DIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Protocol |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Source Port |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination Port |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
IPv4
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling IPv4 traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
Source IP Address (SIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination IP Address (DIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Protocol |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
IPv6 UDP/TCP
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling IPv6 UDP/TCP traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
Source IP Address (SIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination IP Address (DIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Next Header |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Source Port |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination Port |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Flow Label (FL) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
IPv6
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling IPv6 traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
Source IP Address (SIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination IP Address (DIP) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Next Header |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Flow Label (FL) |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Ethernet (L2 Forwarding)
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling Ethernet (L2 Forwarding) traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
Source MAC |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Destination MAC |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
EtherType |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
VLAN |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
MPLS
The following table lists the header fields used in the LAG hashing algorithm for different platforms when handling MPLS traffic.
| Header Field | UfiSpace S9600-102XC | UfiSpace S9600-72XC | UfiSpace S9600-32X | UfiSpace S9510-28DC | UfiSpace S9500-22XST | Edgecore AGR420 | Edgecore AGR400 | Edgecore CSR440 |
|---|---|---|---|---|---|---|---|---|
All MPLS Labels |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Field Definitions
- SIP/DIP (Source/Destination IP Address)
-
Identifies the source/destination of the packet, that is, IPv4/IPv6
- Next Header/Protocol
-
Identifies the type of payload, such as TCP, UDP etc.
- L4 Ports (Source/Destination Port)
-
Used in TCP/UDP headers to identify application endpoints
- FL (Flow Label)
-
Used for IPv6 to improve load balancing
- MAC Addresses (Source/Destination MAC)
-
Used in Ethernet frames for identifying source and destination devices
- EtherType
-
Indicates the protocol encapsulated in the Ethernet frame
- VLAN
-
Identifies the VLAN to which the frame belongs
- MPLS Labels
-
Used in MPLS networks to identify the destination / Forward Equivalence Class for packet forwarding
Supported Platforms
Not all features are necessarily supported on each hardware platform. Refer to the Platform Guide for the features and the sub-features that are or are not supported by each platform.
Supported Number of LAG Interfaces on Platforms
For information on the maximum number of LAG interfaces and members per LAG supported on each hardware platform, refer to the Supported Platforms section of the Platform Guide.