Configuration procedure
To configure traffic redirecting:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create a traffic class and enter traffic class view. | traffic classifier classifier-name [ operator { and | or } ] | By default, no traffic classes exist. |
3. Configure a match criterion. | if-match match-criteria | By default, no match criterion is configured for a traffic class. For more information about the match criteria, see the if-match command in ACL and QoS Command Reference. |
4. Return to system view. | quit | N/A |
5. Create a traffic behavior and enter traffic behavior view. | traffic behavior behavior-name | By default, no traffic behaviors exist. |
6. Configure a traffic redirecting action. | redirect { cpu | interface interface-type interface-number } | By default, no traffic redirecting action is configured for a traffic behavior. If you execute this command multiple times, the most recent configuration takes effect. |
7. Return to system view. | quit | N/A |
8. Create a QoS policy and enter QoS policy view. | qos policy policy-name | By default, no QoS policies exist. |
9. Associate the traffic class with the traffic behavior in the QoS policy. | classifier classifier-name behavior behavior-name [ insert-before before-classifier-name ] | By default, a traffic class is not associated with a traffic behavior. |
10. Return to system view. | quit | N/A |
11. Apply the QoS policy. | Choose one of the application destinations as needed. By default, no QoS policy is applied. If a QoS policy applied to a user profile contains a redirect interface action, make sure the destination interface and the incoming interface of packets are in the same VLAN. The traffic redirecting action takes effect only when the QoS policy is applied to the inbound direction. | |
12. (Optional.) Display traffic redirecting configuration. | display traffic behavior user-defined [ behavior-name ] | Available in any view. |