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

Configuring Queue-based Congestion Management

Context

After packets enter queues on an interface based on priority mapping, they are scheduled based on rules. Interfaces on the device support different scheduling modes. PQ queues are scheduled first, and multiple PQ queues are scheduled in descending order of priority. After all the PQ queues are scheduled, the device schedules DRR, WFQ, or WRR queues in turn. Table 4-3 describes the scheduling modes supported by each interface.
Table 4-3  Scheduling modes supported by each interface
Interface Scheduling Mode
LAN interface
  • PQ
  • DRR
  • WRR
  • PQ+DRR
  • PQ+WRR
NOTE:
  • Layer 2 interfaces on the AR150-S (except he AR151-S2)&AR200-S series support only PQ, WRR, and PQ+WRR, but do not support DRR.

  • Layer 2 interfaces on the AR1200-S (except the AR1220E-S and AR1220F-S) series SRU support only PQ, WRR, and PQ+WRR, but do not support DRR.

  • Layer 2 VE interfaces only support PQ, WFQ and PQ+WFQ.
WAN interface
  • PQ
  • WFQ
  • PQ+WFQ

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run qos queue-profile queue-profile-name

    A queue profile is created and the queue profile view is displayed.

  3. Run the following commands as required.

    • On a WAN interface, run schedule { pq start-queue-index [ to end-queue-index ] | wfq start-queue-index [ to end-queue-index ] }*

      A scheduling mode is configured for each queue on the WAN interface.

    • On a layer 2 VE interface, run schedule { pq start-queue-index [ to end-queue-index ] | wfq start-queue-index [ to end-queue-index ] }*

      A scheduling mode is configured for each queue on the layer 2 VE interface.

    • On a LAN interface, run schedule { pq start-queue-index [ to end-queue-index ] | drr start-queue-index [ to end-queue-index ] | wrr start-queue-index [ to end-queue-index ] }*

      A scheduling mode is configured for each queue on the LAN interface.

      By default, all the queues on the LAN side use WRR; Ethernet WAN interfaces do not use queue scheduling, and other WAN interfaces use WFQ.

  4. (Optional) Run queue { start-queue-index [ to end-queue-index ] } &<1-10> length { bytes bytes-value | packets packets-value }*

    The length of each queue is set on the interface.

    NOTE:
    • A queue profile that defines the queue length using the queue length command cannot be applied to an interface of the 4ES2G-S, 4ES2GP-S, or 9ES2 card.

    • A queue profile that defines the queue length using the queue length command cannot be applied to Layer 2 interfaces of the AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series SRU.

    • When a queue profile is applied to a LAN interface, the queue length can be set to an integer in the range of 1 to 25.

  5. (Optional) Run queue { start-queue-index [ to end-queue-index ] } &<1-10> weight weight-value

    The weight of each queue is set on the interface.

    By default, the weight of a queue is 10.

    NOTE:
    • A queue profile that defines the queue weight using the queue weight command cannot be applied to an interface of the 4ES2G-S, 4ES2GP-S, or 9ES2 card.

    • A queue profile that defines the queue length using the queue weight command cannot be applied to Layer 2 interfaces of the AR100-S&AR110-S&AR120-S&AR150-S&AR160-S&AR200-S&AR1200-S series SRU.

  6. Run quit

    Exit from the queue profile view.

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

    The interface view or sub-interface view is displayed.

  8. Run qos queue-profile queue-profile-name

    The queue profile is applied to the interface or sub-interface.

Translation
Download
Updated: 2019-05-17

Document ID: EDOC1000174115

Views: 40618

Downloads: 28

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