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

AR Router Troubleshooting Guide

This Product Documentation provides guidance for maintaining AR Enterprise Router, covering common information collection and fault diagnostic commands, typical fault troubleshooting guide, and troubleshooting.
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).
How Do I Use the AF, EF, BE, and LLQ Queues, and What Are the Differences Between Them?

How Do I Use the AF, EF, BE, and LLQ Queues, and What Are the Differences Between Them?

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: is applied to services requiring a low delay, low drop probability, and assured bandwidth. EF is also applied to services occupying low bandwidth, for example, voice packets. After packets matching traffic classification rules enter EF queues, they are scheduled in Strict Priority (SP) mode. Packets in other queues are scheduled only after all the packets in EF queues are scheduled. When AF or BE queues have idle bandwidth, EF queues can occupy the idle bandwidth.

    In addition to common EF queues, the device provides a special EF queue, LLQ queue. 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.
Translation
Download
Updated: 2019-05-10

Document ID: EDOC1000079719

Views: 452050

Downloads: 4311

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