No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Outgoing Traffic Fails to Be Load Balanced on the Three Member Interfaces in the Eth-Trunk Interface on an NE5000E at a

Publication Date:  2013-01-08 Views:  22 Downloads:  0
Issue Description

Three member interfaces are added to an Eth-Trunk interface on an NE5000E at a site. After per-packet load balancing is configured on the NE5000E, the outgoing traffic fails to be load balanced across the three links.

Handling Process

There are 16 route entries for Eth-Trunk load balancing on an NE5000E. Even though per-packet load balancing is configured, the 16 routes take over traffic based on a specific interface number ration. The best ratio in the number of outbound interfaces is 2:4:8:16, ensuring that traffic is evenly distributed. However, there are three links at this site. Traffic is distributed across the three links based on the ratio 5:5:6. The on-site Huawei technical support personnel view the traffic information on the Eth-Trunk interface, which proves their analysis.

eth-trunk21 up up 0% 0% 2959 0

gigabitethernet4/0/1 up up 26% 52% 0 0

gigabitethernet5/0/1 up up 27% 52% 0 0

gigabitethernet7/1/1 up up 24% 63% 0 0

Root Cause

 

Configure the number of links to be 2n the number of member interfaces in the Eth-Trunk interface.

Solution

Configure the number of links to be 2n the number of member interfaces in the Eth-Trunk interface.

Suggestions
When an Eth-Trunk interface is configured and per-packet load balancing is configured, using 2n interfaces is recommended. In this way, traffic can be evenly distributed.

END