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 Congestion Management

Configuring MQC to Implement Congestion Management

Context

The device provides the following queues for data packets matching traffic classification rules:
  • AF: ensures a low drop probability of packets when the rate of outgoing service traffic does not exceed the minimum bandwidth. It is applied to services of heavy traffic that needs to be ensured.
  • EF/LLQ: is applied to services requiring a low delay, low drop probability, and assured bandwidth. EF or LLQ is also applied to services occupying low bandwidth, for example, voice packets. After packets matching traffic classification rules enter EF or LLQ queues, they are scheduled in Strict Priority (SP) mode. Packets in other queues are scheduled only after all the packets in EF or LLQ queues are scheduled. When AF or BE queues have idle bandwidth, EF queues can occupy the idle bandwidth.

    NOTE:

    If an EF queue is configured in a traffic behavior of a parent traffic policy, the EF queue does not preempt the idle bandwidth.

    Compared with EF, LLQ provides shorter delay.

  • BE: is used with the default traffic classifier. The remaining packets that do not enter AF or EF queues enter BE queues. BE queues use WFQ scheduling. When a greater number of queues are configured, WFQ allocates bandwidth more evenly but more resources are occupied. WFQ is applied to the services insensitive to the delay and packet loss, for example, Internet access services.
AF queues and bandwidth can be configured for the default traffic classifier, but BE queues are configured for the default traffic classifier in most situations.
  • When the default traffic classifier is associated with AF queues:
    • The total bandwidth used by AF and EF queues cannot exceed the interface bandwidth.
    • AF queues share the remaining bandwidth based on their weights. The remaining bandwidth is calculated as follows:

      Remaining bandwidth = Available bandwidth — Bandwidth used by EF queues

  • When the default traffic classifier is associated with BE queues:
    • If the bandwidth percentage is used to configure the minimum bandwidth for AF queues:
      • The system allocates 10% of the interface's available bandwidth to BE queues.
      • The bandwidth used by AF and EF queues cannot exceed 99% of the interface bandwidth.
      • When the percentage of bandwidths of AF and EF queues to the interface's available bandwidth is less than 90%, the system allocates 10% of the interface's available bandwidth to BE queues by default.
      • When the percentage of bandwidths of AF and EF queues to the interface's available bandwidth is larger than 90% (for example, A%), the system allocates A% subtracted from 100% of the bandwidth to BE queues by default.
      • AF and BE queues share the remaining bandwidth based on their weights. The remaining bandwidth is calculated as follows:

        Remaining bandwidth = Available bandwidth — Bandwidth used by EF queues

    • If the bandwidth is used to configure the minimum bandwidth for AF queues, AF and BE queues share the remaining bandwidth in the ratio of 9:1. The remaining bandwidth refers to the bandwidth occupied by EF queues that is subtracted from the available bandwidth.

The system allocates bandwidth to queues based on their weights.

Table 4-4 provides an example of bandwidth allocation.

Table 4-4  Example of congestion management parameter settings
Interface's Available Bandwidth Configuration
100 Mbit/s EF queues: a minimum of 50% of the interface bandwidth
AF queues: a minimum bandwidth of 30 Mbit/s
BE queues: 1/9 of the bandwidth for AF queues by default when the default traffic classifier is associated with BE queues
The system first allocates bandwidth to EF queues. AF and BE queues share the remaining bandwidth based on weights:
  • Bandwidth of EF queues: 100 Mbit/s x 50% = 50 Mbit/s
  • Remaining bandwidth: 100 Mbit/s - 50 Mbit/s = 50 Mbit/s
  • AF queues and BE queues share the remaining bandwidth in the proportion of 9:1:
    • Bandwidth of AF queues: 50 Mbit/s x [9/(9+1)]= 45 Mbit/s
    • Bandwidth of BE queues: 50 Mbit/s x [1/(9+1)]= 5 Mbit/s
Flow-based congestion management, also called CBQ, on the main interface or sub-interface cannot be used with the queue profile or traffic shaping on the same main interface or sub-interface.

CBQ Configuration

Whether the Queue Profile Can Be Configured (qos queue-profile (interface view))

Whether Traffic Shaping Can Be Configured (qos gts or qos gts adaptation-profile)

Main interface

Main interface: No

Main interface: Yes

Sub-interface: No

Sub-interface: No

Sub-interface

Main interface: Yes

Main interface: Yes

Sub-interface: No

Sub-interface: Yes

NOTE:

Flow-based congestion management can be configured on WAN interfaces and layer 2 VE interfaces.

Procedure

  1. 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.

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

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

    2. Run the following commands as required.

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

        AF is configured for packets of a certain type and the minimum bandwidth is set.

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

        EF is configured for packets of a certain type and the minimum bandwidth is set.

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

        LLQ is configured for packets of a certain type and the maximum bandwidth is set.

      • Run queue wfq [ queue-number total-queue-number ]

        The device is configured to send packets matching the default traffic classifier to BE queues in WFQ mode and the number of queues is set.

    3. (Optional) Run queue-length { bytes bytes-value | packets packets-value }*

      The maximum length of a queue is set.

      NOTE:

      You cannot use the queue-length command to set the length for LLQ queues.

    4. (Optional) Run statistic enable

      The traffic statistics function is enabled.

    5. Run quit

      Exit from the traffic behavior view.

    6. Run quit

      Exit from the system view.

  3. 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.

  4. 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: 39930

Downloads: 28

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