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.


Different CAR Mechanisms of the MA5200G and the ME60 Causes the Large Service Delay

Publication Date:  2012-07-27 Views:  2 Downloads:  0

Issue Description

The MA5200G is used to take over services from the ME60. During the P2P traffic downloading that does not occupy all bandwidth, a web site is pinged from a 10 Mbit/s dial-up user PC. The user delay is about 100 ms, but before the cutover, the user delay is about 20 ms.  

Alarm Information


Handling Process

Use the following commands in the domain view: /*Trigger the queue scheduling*/
user-max-session 1
user-group xx
Run the following commands on the interface used for going online: /*Add the user to the default queue. Parameter none indicates that no queue scheduling is implemented, and the user is added to the default queue.*/
qos schedule none
After the preceding configurations are complete, the user is added to the default queue. The queue has sufficient bandwidth and the user does not have large delay. 

Root Cause

The ME60 uses the TM to implement CAR on users. It adds each user to a queue. When the load is full, traffic is put into the cache and waits to be processed later. Therefore, when the user downloads a large volume of traffic which occupies most bandwidth resources, other application traffic is added to the queue cache. At this time, no packet loss, but a large delay occurs. The MA5200G uses the NP technology to implement CAR. Multiple queues are created on each interface, and multiple users use the same queue. Therefore, even when the user’s maximum bandwidth is reached, the user delay does not change obviously.