Licensing Requirements and Limitations for Ethernet Link Aggregation
Involved Network Element
Other network elements are not required.
Licensing Requirements
Ethernet link aggregation is a basic function of the switch, and as such is controlled by the license for basic software functions. The license for basic software functions has been loaded and activated before delivery. You do not need to manually activate it.
Version Requirements
Product |
Minimum Version Required |
|---|---|
CE12804/CE12808/CE12812 |
V100R001C00 |
CE12816 |
V100R003C00 |
CE12804S/CE12808S |
V100R005C00 |
CE12804E/CE12808E/CE12816E |
V200R002C50 |
For details about the mapping between software versions and switch models, see the Hardware Query Tool.
Software version evolution: V100R001C00 -> V100R002C00 -> V100R003C00 -> V100R003C10 -> V100R005C00 -> V100R005C10 -> V100R006C00 -> V200R001C00 -> V200R002C50 -> V200R003C00 -> V200R005C00 -> V200R005C10 -> V200R019C00 -> V200R019C10
Feature Limitations
- To V200R019C10 earlier versions, each Eth-Trunk supports a maximum of 64 member interfaces on the CE12800E that has the ED-E/EG-E/EGA-E series cards installed in a standalone scenario. To V200R019C10 and later versions, each Eth-Trunk supports a maximum of 128 member interfaces on the CE12800E that has the ED-E/EG-E/EGA-E series cards installed in a standalone scenario.
- In a standalone scenario, on CE12800E that has the FD-X series cards installed and CE12800 series switches, the maximum number of member interfaces in each Eth-Trunk depends on the assign forward eth-trunk mode command. After the maximum number of LAGs supported by the device is set, restart the device to make the configuration take effect.
In versions earlier than V200R002C50, member interfaces of an Eth-Trunk must use the same rate.
For example, GE and 10GE interfaces cannot join the same Eth-Trunk, whereas GE electrical and optical interfaces can join the same Eth-Trunk.
In V200R002C50 and later versions, Ethernet interfaces working with different rates can join the same Eth-Trunk.
- The number of member interfaces of an Eth-Trunk cannot exceed the maximum number of member interfaces allowed.
- Member interfaces cannot be configured with some services or static MAC address entries. For example, when an interface is added to an Eth-Trunk, the interface must use the default link type.
- Member interfaces of an Eth-Trunk cannot be an Eth-Trunk.
- Device connection
- If an interface of the local device is added to an Eth-Trunk, an interface of the remote device directly connected to the interface of the local device must also be added to an Eth-Trunk. Otherwise, communication between the two devices will fail.
- Both devices of the Eth-Trunk must use the same number of physical interfaces, interface rate, duplex mode, jumbo, and flow control mode.
- Both devices of an Eth-Trunk must use the same link aggregation mode.
- Preferential forwarding of local traffic is only valid for known unicast packets. It is invalid for broadcast packets, multicast packets, and unknown unicast packets.
When a new LPU is installed on a device of which the supported numbers of LAGs differs from that of the LPU, the LPU restarts and complies with the device's LAG specifications. If the LPU is used as the stack card, the LPU does not restart automatically. Run the save command to save the configuration, and then restart the stack card to ensure that the configurations on the LPU and device are the same.
VLANs, VXLANs, carrier VLANs, Eth-Trunk interfaces whose card interoperability mode is enhanced mode, and main interfaces share system resources. If system resources are insufficient, the configurations of these features may fail.
- An Ethernet interface can be added to only one Eth-Trunk. To add an Ethernet interface to another Eth-Trunk, delete it from the original one first.
- When an Eth-Trunk member interface is removed from an Eth-Trunk or a physical interface is added to an Eth-Trunk, run the shutdown command for the Eth-Trunk member interface or physical interface, and then run the undo shutdown command after the Eth-Trunk member interface is removed from or the physical interface is added to the Eth-Trunk.
- After an interface is added to an Eth-Trunk, the Eth-Trunk learns MAC address entries or ARP entries, but the member interface does not.
- Before deleting an Eth-Trunk, delete member interfaces from the Eth-Trunk.
Multicast resources are shared by multiple services including VLAN, MAC, Eth-Trunk, M-LAG, Layer 2 protocol transparent transmission, Layer 3 physical interface, and multicast. If multicast resources in the system are insufficient for any of these services you are configuring, the system will display a configuration failure message. To solve this problem, you can delete some unnecessary service configuration, for example, delete unused VLANs.
For the CE12800: The following services are in descending order of priority: M-LAG unidirectional isolation > MQC (traffic policing, traffic statistics collection, and packet filtering) > querying the outbound interface of packets with specified 5-tuple information, source MAC address, and destination MAC address > local VLAN mirroring > sFlow > NetStream > statistics collection on VLANIF interfaces or Layer 3 sub-interfaces. When the services are configured on an interface in the outbound direction, only the service with the highest priority takes effect. For example, when both packet filtering and statistics collection on VLANIF interfaces are configured on a VLANIF interface, only packet filtering takes effect.
For sFlow and NetStream, the preceding limitations apply to all interfaces in V100R005C10 and earlier versions and only to Layer 2 sub-interfaces and Layer 3 sub-interfaces in V100R006C00 and later versions. For details about the priorities between MQC-based traffic statistics collection and traffic statistics collection on a VLANIF interface or a Layer 3 sub-interface, see Licensing Requirements and Limitations for Traffic Statistics Collection.
After an upgrade from a version earlier than V100R005C10SPC200 to V100R005C10SPC200 or later, the default value of universal-id for Eth-Trunk load balancing changes from 1 to 11.
The switches can capture the packets to be sent to the CPU only on Eth-Trunks, but not on member interfaces of the Eth-Trunks.