Feature Requirements |
Series |
Models |
|---|---|---|
The default weight of an Eth-Trunk member interface is 1, which can be modified through configuration. However, the modification changes the forwarding behavior of trunk interfaces. The hash operation is more likely to be performed on member interfaces with greater weight. The total weight of all member interfaces cannot exceed the maximum number of trunk member interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Limited by the capability of the trunk scheduling node in the chip, the traffic bandwidth of the trunk interface on the F2A product is limited. When 100GE0/1/0–7 and 100GE0/1/37–46 are trunk member interfaces, bandwidth convergence occurs on the board, in the worst case, the capacity is reduced from 6.8 TB to 5 TB. Suggestion: Do not configure 100GE0/1/0–7 and 100GE0/1/37–46 as trunk member interfaces. Using other interfaces as trunk member interfaces does not affect board bandwidth. |
NetEngine 8000 F |
NetEngine 8000 F2A |
The user specification supported by an intra-board trunk interface is the same as the user specification supported on the board. The user specification supported by an inter-board trunk interface is the same as the minimum user specification supported on all member boards. You are recommended to ensure that the number of users on a trunk does not exceed the minimum user specification supported on all member boards. |
NetEngine 8000 F |
NetEngine 8000 F1A |
In 1:N static LACP mode, if the maximum number of active member links allowed for an Eth-Trunk interface is 1, after the active link goes Down, the Down event is reported to the Eth-Trunk interface when any of the following occurs:In 1:N static LACP mode, if the maximum number of active member links allowed for an Eth-Trunk interface is 1, after the active link goes Down, the Down event is reported to the Eth-Trunk interface when any of the following occurs: 1. The timeout period (60s) for reporting the Down state elapses. 2. The backup link fails and cannot go Up. The preceding description does not apply to scenarios where an Eth-Trunk in static LACP mode or E-Trunk is associated with VRRP. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Manual 1:1 active/standby mode is supported on Layer 2 Eth-Trunk interfaces, but is not supported on Layer 3 Eth-Trunk interfaces. Configure properly. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When Eth-Trunk interfaces work in static LACP mode, the two devices forming an E-Trunk must be configured with the same LACP system ID and LACP priority.Status of Eth-Trunk interfaces cannot change in accordance with status delivered by the E-Trunk. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |