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

Voice Service Quality Was Poor Because MP-Groups on NE40E LPUK Board Did Not Share Load Evenly

Publication Date:  2013-10-08 Views:  23 Downloads:  0
Issue Description

The quality of voice services subordinate to an NE40E in country M became poor and automatically became normal several hours later.

Version: V600R001C00SPC800

CID:/icase/servlet/download?dlType=HtmlAreaImage&imageId=2921
Handling Process

Huawei performed the following operations to address the problem:

1. Logged in to the NE40E and performed ping tests on the interface carrying voice services. Packet loss occurred.

2. Checked status of the MP-group 2/0/1 interface and found that the three interfaces did not share load evenly.

According to core network engineers, data traffic on the live networks consisted of UDP packets and the UDP destination interface numbers were allocated based on the hash algorithm. Therefore, data traffic could be manually distributed to the three links.

Configured redirection policies on the user-side interfaces (GE interfaces in the preceding figure) on NE40Es. Classified UDP destination interface numbers into three segments and specified the UDP packets to flow to MP-group 2/0/1, MP-group 2/0/2, and MP-group 2/2/1 respectively, implementing even load sharing manually.
Root Cause

1. Checked status of MP-group 2/0/1 and fund that the bandwidth usage of MP-group 2/0/1 reached 90%, much greater than those of the other two interfaces. It was concluded that MP-group 2/0/1 had congestion, resulting in packet loss. However, the three interfaces were configured to work in load sharing mode, and their usage should be approximate.

2. Checked the related boards and found that the uplink board (LPU 1 board) was an LPUK board that supported only the 2-tuple hash algorithm. Therefore, different services (carrying different interface IDs and protocols) with the same source IP and destination IP were considered as the same flow and allocated to the same link. Therefore, if most packets carry the same source IP and destination IP, one link might have high usage and others had low usage.
Solution
Replaced the LPUK board with an LPUF-10 that supported the 5-tuple hash algorithm.
Suggestions

1. Evaluate that whether an uplink LPUK board affects services if the router works in load sharing mode and most packets carry the same source IP and destination IP.

2. Before deploying the load sharing solution, contact R&D to ensure that the load sharing solution can be properly implemented.

END