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?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Huawei performed the following operations to address the problem:
1. Tested other types of services between the ME60 and the E320 and switched interfaces and optical lines.
No packet loss occurred in the test. The problem persisted after interfaces and optical lines were switched.
2. Confirmed that the same L2TP services between the E320 and an MA5200G that served as the LNS were normal.
3. Adjusted the MTU and MSS in the VT profile based on experience.
The problem persisted.
4. Performed repeated tests and found that the Internet access speed of the test PC was high immediately after an L2TP tunnel was reset or was configured on another interface, and then decreased gradually.
According to the traffic statistics on interfaces between the LNS and the LAC, the traffic was always not more than 10 Mbit/s regardless of the number of online users (the rate limit for a user account was 10 Mbit/s). Therefore, it was suspected that a rate limit policy caused the problem. According to R&D explanations, if ME60 running V600R002C02SPC700 functions as an LNS, it applies the tunnel-based QoS scheduling scheme to L2TP users by default. This means that the account rate limit is directly applied to L2TP tunnels. After the rate limit policy for L2TP tunnels was changed to the session-based scheme, the problem was resolved.l2tp-group default-lns
Changed rate limit policy for L2TP groups to be the session-based scheme.l2tp-group default-lns