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>Search


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

Knowledge Base

FAQ-What Is the Difference of the hash-context Command in the System View and in the Eth-Trunk View of the NE80 or NE40

Publication Date:  2012-07-27  |   Views:  138  |   Downloads:  0  |   Author:  w93777  |   Document ID:  EKB0000358343


Issue Description

What is the difference of the hash-context command in the system view and in the Eth-Trunk view of the NE80 or NE40?

Alarm Information


Handling Process

The hash-context next-hop packet command exists in the system view of the NE80 and NE40. This command is run for packet-based load balancing when the NE80 or NE40 has the equal cost routes. In fact, it indicates the load balancing mode of routes.
The hash-context packet command in the Eth-Trunk view is run for the packet-based load balancing among the Eth-Trunk physical ports. In fact, it indicates the load balancing mode of ports.
The NE40/NE80 platform supports flow-based load balancing by default. However, due to the defect of the NE40/NE80 VPR3 of Huawei in the load balancing algorithm, the test conducted on the current network manifested that the flow-based load balancing was hard to realize and the traffic jittered greatly. It is difficult to find these defects on the NE80 because the traffic through the NE80 is collected every five minutes. It is recommended to change the load balancing mode into packet-based load balancing when the traffic occupies more than 50% bandwidth of the ports on the NE80.


Root Cause