Configuring a Traffic Policy

Pre-configuration Tasks

• Configure a traffic classifier.
• Configure a traffic behavior.

Procedure

1. Run system-view

   The system view is displayed.

2. Perform the following operations according to actual situations:

   • On the S2720-EI, S5720I-SI, S5720-LI, S5720S-LI, S5720S-SI, S5720-SI, S5730S-EI, S5730-SI, S6720-LI, S6720S-LI, S6720S-SI, and S6720-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 S5720-EI, S5720-HI, S5730-HI, S5731-H, S5731-S, S5731S-H, S5731S-S, S5732-H, S5735-L, S5735S-L, S5735S-L-M, S5735-S, S5735S-S, S5735-S-I, S6720-EI, S6720-HI, S6720S-EI, S6730-H, S6730S-H, S6730-S, and S6730S-S, 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 you do not specify the matching order of traffic classifiers when creating 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 then specify the matching order.

     When creating a traffic policy, you can specify the matching order of matching rules in the traffic policy. The matching order can be either the automatic order (auto) or configuration order (config):

     • If the automatic order is used, traffic classifiers are matched based on the priorities of their types. If the traffic policy is applied to the inbound direction on the S5720-EI, S6720-EI, or S6720S-EI, traffic classifiers based on the following information are matched in descending order of priority: Layer 2 and IPv4 Layer 3 information > advanced ACL6 > basic ACL6 > IPv4 Layer 3 information > Layer 2 information > user-defined ACL information. In other cases, traffic classifiers based on the following information are matched 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 > user-defined ACL information. If data traffic matches multiple traffic classifiers and the bound traffic behaviors conflict with each other, the traffic behavior corresponding to the highest priority rule takes effect.
     • If the configuration order is used, traffic classifiers are matched based on the sequence in which they are 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 ACL rules need to be updated, delete the traffic policy from the interface, VLAN, and system and re-configure a traffic policy in sequence.

3. Run classifier classifier-name behavior behavior-name

   A traffic behavior is bound to a traffic classifier in the traffic policy.

4. Run quit

   Exit from the traffic policy view.

5. Run quit

   Exit from the system view.