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.


NE40E V800R010C10SPC500 Configuration Guide - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS
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).
(Optional) Configuring the Shared Threshold of Buffer Resources

(Optional) Configuring the Shared Threshold of Buffer Resources

This section describes how to configure the shared threshold of buffer resources.


Perform the following steps on the router:

Queues share buffer resources. If the buffer resources are exhausted, packet loss occurs even if the queues are not congested. To prevent buffer resources from being exhausted by some queues, control flow-wred scheduling. If the flow-wred value is set to a small value, packet loss occurs in traffic bursts. To resolve this problem, run the qos global-buffer command to set the shared threshold of buffer resources. Before the shared buffer resources are exhausted, flow-wred configurations do not take effect to prevent packet loss.


  1. Run system-view

    The system view is displayed.

  2. Run slot slot-id

    The slot view is displayed.

  3. Run qos global-buffer { share-threshold share-value | { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } share } { inbound | outbound }

    Flow-wred scheduling is controlled on a board. Before the buffer resources shared by queues are exhausted, the flow-wred configurations for specific queues do not take effect.

  4. Run commit

    The configuration is committed.

Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 22474

Downloads: 115

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