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.


Configuration Guide - QoS

CloudEngine 8800, 7800, 6800, and 5800 V200R002C50

This document describes the configurations of QoS functions, including MQC, priority mapping, traffic policing, traffic shaping, interface-based rate limiting, congestion avoidance, congestion management, packet filtering, redirection, traffic statistics, and ACL-based simplified traffic policy.
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).
Licensing Requirements and Limitations for Congestion Monitoring and Analysis

Licensing Requirements and Limitations for Congestion Monitoring and Analysis

Involved Network Elements

Other network elements are not required.

Licensing Requirements

Congestion monitoring and analysis are a basic feature of the device and are not under license control.

Version Requirements

Table 7-1 Products and minimum version supporting congestion monitoring and analysis


Minimum Version Required

CE8860EI V100R006C00
CE8850-32CQ-EI V200R002C50

Feature Limitations

Common Constraints

After the system time of a device is modified, the time in the congestion monitoring and analysis result is still calculated based on the original system time. The time is automatically updated within 2 minutes after the modification.

Limitations on Congestion Monitoring
  • The device saves a maximum of 100 pieces of historical congestion monitoring information for each queue.
  • The accuracy between two pieces of historical congestion monitoring information for the same queue is within 2 ms.
  • All historical congestion monitoring information can be saved for a maximum of 30s.
Limitations on Congestion Analysis
  • Interface-based congestion analysis affects the system performance, so do not enable interface-based congestion analysis for a long period of time.

  • The device parses only Layer 3 information of IPv4, TCP, UDP, and ICMP packets, and only Layer 2 information of other packets.
  • Congestion analysis can be enabled on only one interface of the device.
  • The device sorts analysis results based on the proportion of congested packets and displays only 10 types of the most congested packets.
  • The device saves only the packet analysis result for the congestion that occurred last time.
  • There is an interval between queue congestion detection and queue packet obtaining, so congestion analysis is mainly used in scenarios where congestion occurs for a long period of time.
  • The device only obtains packets in a short period of time when the buffer usage is higher than higher buffer threshold. If the buffer usage is often higher than the high buffer threshold, packet analysis may be inaccurate.
Updated: 2019-03-21

Document ID: EDOC1000166640

Views: 51754

Downloads: 221

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