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 - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS

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 Traffic Shaping

Configuring Traffic Shaping

Traffic shaping is similar to that of traffic policing. Traffic shaping buffers packets that need to be dropped by traffic policing by means of buffer and token bucket.

Usage Scenario

When the traffic volume on a network is heavy, nonconforming packets are directly discarded. If the upstream router sends a large volume of data traffic, the downstream network may be congested or a great number of packets are dropped. To prevent this situation, configure traffic shaping on the outbound interface of the upstream router to limit the traffic. Traffic shaping enables packets to be transmitted at an even rate and improves the allocation of bandwidth resources between the upstream and downstream networks.

Traffic shaping is carried out using buffers and token buckets. If packets are sent at a high rate, nonconforming packets are not dropped. Instead, such packets are placed in buffer queues. Under the control of token buckets, buffered packets are sent at an even rate by queue scheduling priority when the network is idle. As a result, packet retransmissions in case of packet dropping is prevented.


Differentiated service (DiffServ) is used to guarantee the bandwidth for behavior aggregate (BA) data traffic. The NE40E uses the queue scheduling mechanism to allocate resources to the services of different classes, such as expedited forwarding (EF) and assured forwarding (AF) queues. You do not need to configure queue management.

Currently, the NE40E supports traffic shaping only for the outgoing traffic on interfaces.

Pre-configuration Tasks

Before configuring traffic shaping, complete the following tasks:

  • Configure parameters for physical interfaces.

  • Configure link layer attributes for interfaces to ensure their normal operating.

  • Configure IP addresses for interfaces.

  • Enable a routing protocol for communication between devices.


  • Configure traffic shaping on an interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run port shaping { shaping-value | shaping-percentage shaping-percentage-value } [ network-header-length network-header-length ] [ pbs pbs-value ]

      Traffic shaping is configured for outgoing traffic on the interface.

      To allocate shaping values based on the weight values of member interfaces, run the port shaping shaping-value [ weight-mode ] command.

    4. Run commit

      The configuration is committed.

  • (Optional) Configure a service profile and apply it to an interface.
    1. Run system-view

      The system view is displayed.

    2. Run service-template service-template-name [ slot slot-number ]

      The service profile view is displayed.

    3. Run network-header-length network-header-length { inbound | outbound }

      A network header length is set for the service profile.


      After packets enter the device, there is a difference between the length of a processed packet and the original packet. A network header length is required to achieve precise flow control by compensating a processed packet with a certain length.

    4. Run commit

      The configuration is committed.

    5. Run quit

      Return to the system view.

    6. Run interface interface-type interface-number

      The interface view is displayed.

    7. Run shaping service-template service-template-name

      The service profile is used on the interface.

    8. Run commit

      The configuration is committed.

  • Configuring Traffic Shaping for MTI in the Slot View
    1. Run system-view

      The system view is displayed.

    2. Run slot slot-id

      The slot view is displayed.

    3. Run port shaping cos-value { { pq | wfq weight weight-value | lpq } | shaping { shaping-value | shaping-percentage shaping-percentage-value } | port-wred wred-name } * outbound bind mtunnel

      a Peak rate is set at which the MTunnel interface in the distributed multicast VPN can send data.

    4. Run commit

      The configuration is committed.

Checking the Configuration

After you configure traffic shaping, check whether the configuration takes effect.

  • Run the display interface [ interface-type [ interface-number ] ] command to check traffic information on a specific interface.

  • Run the display service-template configuration [ verbose [ service-template-name ] ] command to check a user-defined service profile.
<HUAWEI> display service-template configuration verbose 
[service-template detail information]
total number :1
slot all     :1

service-template-name : templatel
 slot : all
 [current configuration]
  inbound network-header-length:  NA

  outbound network-header-length: 20

 [reference relationship]
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 30357

Downloads: 141

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next