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.


NE40E V800R010C10SPC500 Configuration Guide - User Access 01

This is NE40E V800R010C10SPC500 Configuration Guide - User Access
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring the L2TP HQoS Scheduling Mode

Configuring the L2TP HQoS Scheduling Mode

In the L2TP service wholesale, the actual service control point is the LNS. Therefore, the L2TP HQoS scheduling mode should be configured on the LNS.


Perform the following steps on the NE40E that functions as the LNS:


  1. Run system-view

    The system view is displayed.

  2. Run l2tp-group group-name

    The L2TP group is created and the L2TP group view is displayed.

    The L2TP group must be the L2TP group of the LNS.

  3. Run qos scheduling-mode { session | tunnel }

    The L2TP HQoS scheduling mode is set.

    L2TP HQoS has the following scheduling modes:

    • Scheduling by tunnel: In this mode, user services are not differentiated. As a result, tunnel traffic, not user traffic is scheduled into user queues.

    • Scheduling by session: In this mode, user traffic is scheduled into user queues with priorities ranging from 1 to 8 and tunnel traffic is scheduled into group queues. SP or WFQ scheduling can be performed between any of the user queues.

  4. (Optional) Run user-group-queue user-group-queue-name [ inbound | outbound ]

    The user-group-queue is specified.


    If the scheduling is set to be performed by session, this command must be run; otherwise, you do not need to run this command.

  5. Run commit

    The configuration is committed.

Updated: 2019-01-03

Document ID: EDOC1100055031

Views: 17221

Downloads: 70

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next