S1720, S2700, S5700, and S6720 V200R011C10 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.
Configuring a Traffic Policy
Pre-configuration Tasks
Procedure
Run system-view
The system view is displayed.
- Run the following commands as required.
On the S1720GFR, S1720GW, S1720GWR, S1720X, S1720GW-E, S1720GWR-E, S1720X-E, S2720EI, S2750EI, S5700LI, S5700S-LI, S5710-X-LI, S5720LI, S5720S-LI, S5720SI, S5720S-SI, S5730SI, S5730S-EI, S6720LI, S6720S-LI, S6720SI, and S6720S-SI, run traffic policy policy-name
A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed.
On the S5720EI, S5720HI, S6720EI, and S6720S-EI, run traffic policy policy-name [ match-order { auto | config } ]
A traffic policy is created and the traffic policy view is displayed, or the view of an existing traffic policy is displayed. If no matching order is specified when you create a traffic policy, the default matching order is config.
After a traffic policy is applied, you cannot use the traffic policy command to modify the matching order of traffic classifiers in the traffic policy. To modify the matching order, delete the traffic policy, create a traffic policy, and specify the matching order.
When creating a traffic policy, you can specify the matching order of its matching rules. The matching order can be either automatic order or configuration order:- Automatic order: Traffic classifiers are matched based on the priorities of their types. Traffic classifiers based on the following information are in descending order of priority: Layer 2 and IPv4 Layer 3 information, advanced ACL6 information, basic ACL6 information, Layer 2 information, IPv4 Layer 3 information, and user-defined ACL information. If data traffic matches multiple traffic classifiers, and the traffic behaviors conflict with each other, the traffic behavior corresponding to the highest priority rule takes effect.
- Configuration order: Traffic classifiers are matched based on the sequence in which traffic classifiers were bound to traffic behaviors.
![]()
If more than 128 ACL rules defining CAR are configured, a traffic policy must be applied to an interface, a VLAN, and the system in sequence in the outbound direction. In the preceding situation, if you need to update ACL rules, delete the traffic policy from the interface, VLAN, and system and reconfigure it in sequence.
Run classifier classifier-name behavior behavior-name
A traffic behavior is bound to a traffic classifier in a traffic policy.
Run quit
Exit from the traffic policy view.
Run quit
Exit from the system view.
