To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The quality of voice services subordinate to an NE40E in country M became poor and automatically became normal several hours later.
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.
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.
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.