Matching order of packets when multiple pairs of traffic classifiers and traffic behaviors are defined in a traffic policy

12

For S series switches (except the S1700):
For X series cards of modular switches, the matching order depends on priorities of traffic classifiers, that is, the value of the precedence precedence-value parameter in the traffic classifier command. A smaller value indicates a higher priority.
For cards of modular switches except X series cards:
- config: The matching order depends on priorities of traffic classifiers, that is, the value of the precedence precedence-value parameter in the traffic classifier command. A smaller value indicates a higher priority.
- auto: The matching order depends on priorities of traffic classifier types predefined on the system. The traffic classifiers based on the following information are in descending order of priority: Layer 2 and Layer 3 information, advanced ACL6 rule, basic ACL6 rule, Layer 2 information, Layer 3 information, and user-defined ACL rule. If actions in traffic behaviors do not conflict, all the matching traffic classifiers and traffic behaviors take effect. If actions in traffic behaviors conflict, the traffic classifier and traffic behavior with the highest priority of traffic classifier type takes effect.
For S series fixed switches S600-E, packets match traffic classifiers and traffic behaviors according to the sequence in which the traffic classifiers and traffic behaviors are configured. If the first traffic classifier is not matched, the switch matches packets with the second traffic classifier, and so on. If the packets match a traffic classifier, the switch does not match the packets with subsequent traffic classifiers. Only the first pair of the matching traffic classifier and traffic behavior takes effect.
For S series modular switches, you can specify the matching order of rules in the traffic policy when creating a traffic policy. The matching orders are classified into the configuration order (config) and automatic order (auto).
For other fixed switches, see "How Does the Switch Match Packets When Multiple Pairs of Traffic Classifiers and Traffic Behaviors Are Defined in a Traffic Policy?" in FAQ-QoS.

Other related questions:
A traffic policy is bound to multiple pairs of traffic classifiers and traffic behaviors. What Is the sequence in which traffic classifiers and traffic behaviors are used
If the classifier classifier-name behavior behavior-name command is executed for a traffic policy multiple times, the configured behaviors are executed in the order in which they are configured. For example, a traffic policy contains the following four behaviors: classifier classifier1 behavior behavior1 classifier classifier2 behavior behavior2 classifier classifier3 behavior behavior3 classifier classifier4 behavior behavior4 The received packet is first checked against classifier1. If the packet matches classifier1, the packet is processed according to behavior1 and does not need to be checked against classifier2. If the packet does not match classifier1, the packet is checked against classifier2. If the packet matches classifier2, the packet is processed according to behavior2 and does not need to be checked against classifier3...

Can multiple pairs of traffic classifiers and traffic behaviors be bound to a traffic policy on an AR
An AR can be configured with multiple pairs of traffic classifiers and traffic behaviors in a traffic policy. The traffic classifiers and traffic behaviors are executed in the order in which they are configured. For example, four pairs of traffic classifiers and traffic behaviors are configured in a traffic policy: classifier classifier1 behavior behavior1 classifier classifier2 behavior behavior2 classifier classifier3 behavior behavior3 classifier classifier4 behavior behavior4 After an AR receives packets, it checks whether the packets match classifier1. If the packets match classifier1, the AR takes the action defined in behavior1 for the packets. If the packets do not match classifier1, the AR checks whether the packets match classifier2. If the packets match classifier2, the AR takes the action defined in behavior2 for the packets. The other processes can be deducted by analogy.

In what order does an applied traffic policy take effect on S series switches
For S series switches (except the S1700), a traffic policy can be applied in the system view, interface view, and VLAN view simultaneously. When applying a traffic policy in multiple views, configure the traffic policy in the sequence of interface view, VLAN view, and system view. When multiple traffic policies are applied in different views and packets simultaneously match different traffic policies, the traffic policies take effect in the following orders: - If traffic classification rules in the traffic policies are of the same type, that is, the rules are all user-defined ACL rules, Layer 2 rules, or Layer 3 rules, only one traffic policy takes effect. The traffic policy that takes effect depends on the view in which the traffic policy has been applied. The view priority is as follows: interface view > VLAN view > system view. - For cards of modular switches except X series cards and fixed switches S5700HI, S5700EI, S5710EI, S5720EI, S5710HI, S6700EI, S6720EI, and S6720S-EI, if traffic classification rules in the traffic policies are of different types and actions in traffic behaviors do not conflict, traffic policies in all views take effect. If actions in traffic behaviors conflict, only one traffic policy takes effect and the traffic policy that takes effect is relevant to rules. The rule priority is as follows: Layer 2 rule and Layer 3 rule > advanced ACL6 rule > basic ACL6 rule > Layer 3 rule > Layer 2 rule > user-defined ACL rule. - For X series cards of modular switches and E series and S series fixed switches S600-E, S1720GFR, S1720GW-E, S1720GWR-E, S2720, S2750, 5700SI, S5700LI, S5700S-LI, S5720LI, S5720S-LI, S5710-X-LI, S5720SI, S5720S-SI, and S5720HI, if traffic classification rules in the traffic policies are of different types, the traffic policy in only one view takes effect and the traffic policy that takes effect is relevant to the view in which it is applied. The view priority is as follows: interface view > VLAN view > system view. It is recommended that you configure the traffic policy based on the priority. Otherwise, the configured traffic policy may not take effect immediately. Note: MQC cannot be configured on the S2700SI.

A traffic policy contains multiple pairs of traffic classifiers and behaviors. How to handle the problem if the GTS CIR command is executed in these pairs and the CIR configured is greater than the CIR configured on the interfaces
If a traffic policy includes multiple pairs of traffic classifiers and behaviors and the GTS CIR command is configured in these pairs. If the CIR of these pairs is greater than that configured on the interface, rate limiting will be configured for the pairs and interfaces.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top