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.


CLI-based Configuration Guide - QoS

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

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 a Traffic Behavior

Configuring a Traffic Behavior

Pre-configuration Tasks

Before configuring a traffic behavior, configure link layer attributes of interfaces to ensure that the interfaces work properly.


The device supports actions including packet filtering, priority re-marking, redirection, traffic policing, and traffic statistics collection.


  1. Run system-view

    The system view is displayed.

  2. Run traffic behavior behavior-name

    A traffic behavior is created and the traffic behavior view is displayed, or the view of an existing traffic behavior is displayed.

  3. Define actions in the traffic behavior. You can configure multiple non-conflicting actions in a traffic behavior.



    Packet filtering

    deny | permit

    Configure a QoS group that packets belong to

    remark qos-group qos-group-value

    Priority re-marking by MQC

    remark 8021p 8021p-value

    remark cvlan-8021p 8021p-value

    remark dscp { dscp-name | dscp-value }

    remark mpls-exp exp-value(AR1200-S&AR2200-S&AR3200-S series)

    remark fr-de fr-de-value

    remark local-precedence local-precedence-value


    If a traffic behavior contains remark 8021p or remark dscp, but not remark local-precedence, the device marks the local priority of packets with 0.

    Traffic policing by MQC

    car cir { cir-value | pct cir-percentage } [ pir { pir-value | pct pir-percentage } ] [ cbs cbs-value pbs pbs-value ] [ share ] [ mode { color-blind | color-aware } ] [ green { discard | pass [ remark-8021p 8021p-value | remark-dscp dscp-value ] } ] [ yellow { discard | pass [ remark-8021p 8021p-value | remark-dscp dscp-value ] } ] [ red { discard | pass [ remark-8021p 8021p-value | remark-dscp dscp-value ] } ]

    Traffic shaping by MQC

    gts cir { cir-value [ cbs cbs-value ] | pct pct-value } [ queue-length queue-length ]

    Adaptive traffic shaping by MQC

    gts adaptation-profile adaptation-profile-name

    Congestion management by MQC

    queue af bandwidth { bandwidth | [ remaining ] pct percentage }

    queue ef bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

    queue llq bandwidth { bandwidth [ cbs cbs-value ] | pct percentage [ cbs cbs-value ] }

    queue wfq [ queue-number total-queue-number ]

    queue-length { bytes bytes-value | packets packets-value }*

    Congestion avoidance by MQC

    drop-profile drop-profile-name

    Sampling of NetStream statistics by MQC

    ip netstream sampler { fix-packets packet-interval | fix-time time-interval | random-packets packet-interval | random-time time-interval } { multicast | rpf-failure | unicast }*

    • The device does not support sampling of NetStream statistics for IPv6 and MPLS packets, so traffic classification rules cannot contain IPv6 or MPLS.

    • Layer 2 VE interfaces do not support this function.

    Unicast PBR

    redirect ip-nexthop ip-address [ vpn-instance vpn-instance-name ] [ track { nqa admin-name test-name | ip-route ip-address { mask | mask-length } | interface interface-type interface-number } ] [ post-nat ] [ discard ] [ sfc-nsh spi spi-index si si-index ]


    If DSCP priority matching is configured in a traffic policy, the SAE220 (WSIC) and SAE550 (XSIC) cards do not support redirect ip-nexthop ip-address post-nat.

    redirect ipv6-nexthop ipv6-address [ track { nqa nqa-admin nqa-name | ipv6-route ipv6–address mask-length } ] [ discard ]

    redirect interface interface-type interface-number [ track { nqa admin-name test-name | ip-route ip-address { mask | mask-length } | ipv6-route ipv6-address mask-length } ] [ discard ]

    redirect vpn-instance vpn-instance-name


    Layer 2 VE interfaces do not support this function.

    redirect backup-nexthop ip-address

    Sub traffic policy binding

    traffic-policy policy-name

    Traffic statistics

    statistic enable

    Configure MQC to implement URL filtering

    url-filter-profile profile-name

    When an interface is added to a network bridge, the traffic behavior that is configured on the interface in the inbound direction can only define the following actions:
    • Re-marking the 802.1p priority in VLAN packets.
    • Configuring MQC to implement traffic policing.
    • Traffic statistics.

  4. Run quit

    Exit from the traffic behavior view.

Updated: 2019-05-17

Document ID: EDOC1000174115

Views: 42247

Downloads: 30

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