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.


S12700 V200R010C00 Configuration Guide - QoS

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, ACL-based simplified traffic policy, and HQoS.

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


HQoS implements hierarchical scheduling based on queues. The switch supports the flow queue (FQ) and subscriber queue (SQ). The HQoS hierarchy is a tree structure, with flow queues as the leaf nodes and subscriber queues as root nodes. Packets on an interface are first sent to leaf nodes, scheduled, and sent out of the root node. In addition, packets can be further scheduled. For example, the packets can be scheduled in port queues. The device supports the mapping between flow queues and port queues to schedule the same service from different users, as shown in Figure 10-1.

Figure 10-1  HQoS scheduling

Flow Queue

Based on the DiffServ model, the switch enabled with HQoS sends packets to flow queues based on mapped internal priorities to differentiate services. Each user has eight flow queues corresponding to eight service priorities. The eight service priorities are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. Priority Queuing (PQ) or Weighted Fair Queueing (WFQ) can be configured for the flow queues. A flow queue supports Weighted Random Early Detection (WRED) and traffic shaping, allowing preference in bandwidth and scheduling for high-priority services.

Subscriber Queue

Subscriber queues differentiate users. Users can be VLANs or VPNs and are differentiated using access control lists (ACLs). Subscriber queues are the aggregation of eight flow queues, with each user utilizing a subscriber queue. Traffic shaping can be configured to limit the total bandwidth of each user.

Interface Queue

Similar to flow queues, the eight interface queues correspond to eight service types. Priority Queuing (PQ) or Weighted Deficit Round Robin (WDRR) scheduling can be configured for the eight interface queues. Each queue supports WRED and traffic shaping. For details, see Configuring Congestion Management, Configuring Congestion Avoidance, and Configuring Traffic Shaping. The device supports the mapping between flow queues (BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7) and port queues. The mapping allows the device to flexibly send service traffic in a flow queue to a port queue.

Target Port

Target ports are physical interfaces through which outbound data is sent. Traffic shaping can be performed for each target port after the completion of flow, subscriber, and port queue scheduling. For details, see Configuring Outbound Interface-based Rate Limiting.

Updated: 2019-12-28

Document ID: EDOC1000142089

Views: 52717

Downloads: 89

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next