Traffic is not forwarded through all member interfaces of an Eth-Trunk in a stack. Why

When a stack device forwards traffic, an Eth-Trunk may select a member interface of another stack device through the hash algorithm, which occupies bandwidth resources between stack devices and reduces the traffic forwarding efficiency. To address the preceding problem, run the local-preference enable command to enable the Eth-Trunk to preferentially forward local traffic. That is, traffic arriving at the local device is preferentially forwarded through member interfaces of the local device. If the local device has no member interface, the member interface of another stack device is used to forward traffic. This saves bandwidth resources between stack devices and improves the traffic forwarding efficiency.

By default, an Eth-Trunk is enabled to preferentially forward local traffic. Before configuring an Eth-Trunk to preferentially forward local traffic, ensure that the outbound bandwidth of Eth-Trunk member interfaces is sufficient for forwarding local traffic. If the outbound interface bandwidth is insufficient, some packets are dropped.

Scroll to top