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

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

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 MQC to Implement Adaptive Traffic Shaping

Configuring MQC to Implement Adaptive Traffic Shaping

When the outgoing traffic rate needs to be limited on an upstream device but the inbound interface rate on the downstream device is variable, configure MQC to implement adaptive traffic shaping on the outbound interface of the upstream device. When the rate of packets matching the specified traffic classifier exceeds the rate limit, the upstream device buffers excess packets. When there are sufficient tokens in the token bucket, the device forwards the buffered packets at an even rate. When the buffer queue is full, the device discards the buffered packets. MQC-based adaptive traffic shaping enables the device to identify different service flows using traffic classifiers and provide differentiated services on a per flow basis.

Adaptive traffic shaping is implemented by associating an NQA test instance with an adaptive traffic profile on the upstream device. The NQA test instance detects the packet loss ratio on the downstream device, and the upstream device dynamically adjusts traffic shaping parameters based on the packet loss ratio as follows:
  • Reduces the traffic shaping rate when the NQA test instance detects that the packet loss ratio is larger than the upper threshold in the adaptive traffic profile.
  • Increases the traffic shaping rate when all the following conditions are met:
    • The NQA test instance detects that the packet loss ratio is lower than the lower threshold in the adaptive traffic profile.
    • Congestion occurs on the outbound interface of the upstream device.
    • The interval for increasing the traffic shaping rate is reached.
  • Retains the traffic shaping rate in one of the following scenarios:
    • The NQA test instance detects that the packet loss ratio is smaller than the lower threshold in the adaptive traffic profile and no congestion occurs on the outbound interface of the upstream device.
    • The detected packet loss ratio is within the packet loss ratio range in the adaptive traffic profile.
  • Uses the upper threshold for the traffic shaping rate in the adaptive traffic profile when the NQA test fails.
  • Uses the upper threshold for the traffic shaping rate in the adaptive traffic profile when the adaptive traffic profile is not bound to any NQA test instance.

After an adaptive traffic profile is bound to a traffic behavior, associate the traffic behavior with a traffic classifier in a traffic policy and apply the traffic policy to an interface. Then parameters in the adaptive traffic profile take effect on the interface.

NOTE:

A traffic policy containing an adaptive traffic shaping behavior can be applied to the outbound direction on a WAN interface or layer 2 VE interfaces.

Procedure

  1. Configure an adaptive traffic profile.
    1. Run system-view

      The system view is displayed.

    2. Run qos adaptation-profile adaptation-profile-name

      An adaptive traffic profile is created and its view is displayed.

    3. Run rate-range low-threshold low-threshold-value high-threshold high-threshold-value

      The traffic shaping rate range is set.

    4. (Optional) Run rate-adjust step step

      The traffic shaping rate adaptation step is set.

    5. (Optional) Run rate-adjust increase interval interval-value

      The interval for increasing the traffic shaping rate is set.

    6. (Optional) Run rate-adjust loss low-threshold low-threshold-percentage high-threshold high-threshold-percentage

      The packet loss ratio range is set.

    7. Run track nqa admin-name test-name

      An NQA test instance is bound to the adaptive traffic profile.

      NOTE:

      When configuring an NQA test instance, ensure that NQA packets can enter high-priority queues so that they are not discarded in the case of heavy traffic.

    8. Run quit

      Exit from the adaptive traffic profile.

    9. Run quit

      Exit from the system view.

  2. Configure a traffic classifier.
    1. Run system-view

      The system view is displayed.

    2. Run traffic classifier classifier-name [ operator { and | or } ]

      A traffic classifier is created and the traffic classifier view is displayed.

      and indicates that rules are ANDed with each other.
      • If a traffic classifier contains ACL rules, packets match the traffic classifier only when they match one ACL rule and all the non-ACL rules.

      • If a traffic classifier does not contain ACL rules, packets match the traffic classifier only when the packets match all the non-ACL rules.

      or indicates that the relationship between rules is OR. Packets match a traffic classifier as long as packets match only one rule of the traffic classifier.

      By default, the relationship between rules in a traffic classifier is OR.

    3. Run the following commands as required.

      Matching Rule

      Command

      Outer VLAN ID

      if-match vlan-id start-vlan-id [ to end-vlan-id ]

      Inner VLAN IDs in QinQ packets

      if-match cvlan-id start-vlan-id [ to end-vlan-id ]

      802.1p priority in VLAN packets

      if-match 8021p 8021p-value &<1-8>

      Inner 802.1p priority in QinQ packets

      if-match cvlan-8021p 8021p-value &<1-8>

      EXP priority in MPLS packets (AR1200-S series, AR2200-S series and AR3200-S series)

      if-match mpls-exp exp-value &<1-8>

      Destination MAC address

      if-match destination-mac mac-address [ mac-address-mask mac-address-mask ]

      Source MAC address

      if-match source-mac mac-address [ mac-address-mask mac-address-mask ]

      DLCI value in FR packets

      if-match dlci start-dlci-number [ to end-dlci-number ]

      DE value in FR packets

      if-match fr-de

      Protocol type field encapsulated in the Ethernet frame header

      if-match l2-protocol { arp | ip | mpls | rarp | protocol-value }

      All packets

      if-match any

      DSCP priority in IP packets

      if-match [ ipv6 ] dscp dscp-value &<1-8>
      NOTE:

      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.

      IP precedence in IP packets

      if-match ip-precedence ip-precedence-value &<1-8>
      NOTE:

      if-match [ ipv6 ] dscp and if-match ip-precedence cannot be configured simultaneously in a traffic classifier where the relationship between rules is AND.

      Layer 3 protocol type

      if-match protocol { ip | ipv6 }

      QoS group index of packets

      if-match qos-group qos-group-value

      IPv4 packet length

      if-match packet-length min-length [ to max-length ]

      PVC information in ATM packets

      if-match pvc vpi-number/vci-number

      RTP port number

      if-match rtp start-port start-port-number end-port end-port-number

      SYN Flag in the TCP packet header

      if-match tcp syn-flag { ack | fin | psh | rst | syn | urg } *

      Inbound interface

      if-match inbound-interface interface-type interface-number

      Outbound interface

      if-match outbound-interface Cellular interface-number:channel

      ACL rule

      if-match acl { acl-number | acl-name }
      NOTE:
      • Before defining a matching rule for traffic classification based on an ACL, create the ACL.

      • To use an ACL in a traffic classifier to match the source IP address, run the qos pre-nat command on an interface to configure NAT pre-classification. NAT pre-classification enables the NAT-enabled device to carry the private IP address before translation on the outbound interface so that the NAT-enabled device can classify IP packets based on private IP addresses and provide differentiated services.

      ACL6 rule

      if-match ipv6 acl { acl-number | acl-name }
      NOTE:
      • Before defining a matching rule for traffic classification based on an ACL, create the ACL.

      • To use an ACL in a traffic classifier to match the source IP address, run the qos pre-nat command on an interface to configure NAT pre-classification. NAT pre-classification enables the NAT-enabled device to carry the private IP address before translation on the outbound interface so that the NAT-enabled device can classify IP packets based on private IP addresses and provide differentiated services.

      Application protocol

      if-match application application-name [ user-set user-set-name ] [ time-range time-name ]

      NOTE:

      Before defining a matching rule based on an application protocol, enable Smart Application Control (SA) and load the signature file.

      SA group

      if-match category category-name [ user-set user-set-name ] [ time-range time-name ]

      NOTE:
      • Before defining a matching rule based on an application protocol, enable Smart Application Control (SA) and load the signature file.

      User group

      if-match user-set user-set-name [ time-range time-range-name ]

    4. Run quit

      Exit from the traffic classifier view.

  3. Configure a traffic behavior.
    1. Run traffic behavior behavior-name

      A traffic behavior is created and its view is displayed.

    2. Run gts adaptation-profile adaptation-profile-name

      An adaptive traffic profile is bound to the traffic behavior.

      NOTE:

      The adaptive traffic profile must have been created and configured.

    3. (Optional) Run statistic enable

      Traffic statistics collection is enabled.

    4. Run quit

      Exit from the traffic behavior view.

    5. (Optional) Run qos overhead layer { link | physics }

      A mode is specified for calculating packet lengths during traffic policing or traffic shaping.

      By default, the system counts the physical-layer and link-layer compensation information in packet lengths during traffic policing or traffic shaping.

    6. Run quit

      Exit from the system view.

  4. Configure a traffic policy.
    1. Run system-view

      The system view is displayed.

    2. Run traffic policy policy-name

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

      By default, no traffic policy is created in the system.

    3. Run classifier classifier-name behavior behavior-name [ precedence precedence-value ]

      A traffic behavior is bound to a traffic classifier in a traffic policy.

      By default, no traffic classifier or traffic behavior is bound to a traffic policy.

    4. Run quit

      Exit from the traffic policy view.

    5. Run quit

      Exit from the system view.

  5. Apply the traffic policy.
    • Apply the traffic policy to an interface.

      1. Run system-view

        The system view is displayed.

      2. Run interface interface-type interface-number [.subinterface-number ]

        The interface view is displayed.

      3. Run traffic-policy policy-name { inbound | outbound }

        The traffic policy is applied to the inbound or outbound direction on the interface.

        By default, no traffic policy is applied to an interface.

    • Apply the traffic policy to an interzone.
      NOTE:

      Only the AR100-S&AR110-S&AR120-S&AR150-S&AR200-S series routers support this configuration.

      1. Run system-view

        The system view is displayed.

      2. Run firewall interzone zone-name1 zone-name2

        An interzone is created and the interzone view is displayed.

        By default, no interzone is created.

        You must specify two existing zones for the interzone.

      3. Run traffic-policy policy-name

        The traffic policy is bound to the interzone.

        By default, no traffic policy is bound to an interzone.

    • Apply the traffic policy to a BD.
      NOTE:

      Only the AR100-S&AR110-S&AR120-S&AR150-S&AR200-S&AR1200-S series routers support this configuration.

      1. Run system-view

        The system view is displayed.

      2. Run bridge-domain bd-id

        A BD is created and the BD view is displayed.

        By default, no BD is created.

      3. Run traffic-policy policy-name { inbound | outbound }

        The traffic policy is applied to the BD.

        By default, no traffic policy is applied to a BD.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174115

Views: 40610

Downloads: 28

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