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.


S12700 V200R010C00 Configuration Guide - QoS

This document describes the configurations of QoS functions, including MQC, priority mapping, traffic policing, traffic shaping, interface-based rate limiting, congestion avoidance, congestion management, packet filtering, redirection, traffic statistics, ACL-based simplified traffic policy, and HQoS.

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 Hierarchical Traffic Policing

Configuring Hierarchical Traffic Policing


The device supports hierarchical traffic policing. After the system uses MQC to implement traffic policing (level-1 CAR) for service flows matching a traffic classifier in a traffic policy, the system aggregates all the service flows matching the traffic classifiers associated with the level-1 CAR in the same traffic policy and performs traffic policing (level-2 CAR) for the aggregated flow. Hierarchical traffic policing implements statistical multiplexing of traffic and provides fine-grained service control. For details about level-1 CAR, see Configuring MQC to Implement Traffic Policing.


  1. Run:


    The system view is displayed.

  2. Run:

    qos car car-name cir cir-value [ cbs cbs-value [ pbs pbs-value ] | pir pir-value [ cbs cbs-value pbs pbs-value ] ]

    A QoS CAR profile is created and CAR parameters are configured.

  3. Run:

    traffic behavior behavior-name

    The traffic behavior view is displayed.

  4. Run:

    car car-name share

    The aggregated CAR action is configured.

    • The ET1D2X48SEC0, SA series, and SC series cards do not support aggregated CAR.

    • The traffic policy defining the aggregated CAR action can only be used in the inbound direction.

    • After aggregated CAR is configured, all the rules in the traffic classifiers bound to the same traffic behavior share the CAR index. The system aggregates all the flows matching these traffic classifiers and uses CAR to limit the rate of the flows. If the traffic classifiers define both Layer 2 and Layer 3 information, the aggregated CAR configuration is invalid.

Updated: 2019-12-28

Document ID: EDOC1000142089

Views: 49395

Downloads: 88

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next