Configuring traffic redirecting
Traffic redirecting redirects packets matching the specified match criteria to a location for processing.
The following redirect actions are supported:
Redirecting traffic to the CPU—Redirects packets that require processing by the CPU to the CPU.
•
Redirecting traffic to an interface—Redirects packets that require processing by an interface to the
•
interface. This action applies only to Layer 2 packets, and the target interface must be a Layer 2
interface.
Configuration procedure
To configure traffic redirecting:
Step
1.
Enter system view.
2.
Create a traffic class and
enter traffic class view.
3.
Configure match criteria.
4.
Return to system view.
5.
Create a traffic behavior
and enter traffic behavior
view.
6.
Configure a traffic
redirecting action.
7.
Return to system view.
Command
system-view
traffic classifier classifier-name [ operator { and
| or } ]
if-match match-criteria
quit
traffic behavior behavior-name
redirect { cpu | interface interface-type
interface-number }
quit
75
Remarks
N/A
By default, no traffic class
exists.
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.
N/A
By default, no traffic
behavior exists.
By default, no traffic
redirecting action is
configured for a traffic
behavior.
The actions of redirecting
traffic to the CPU and
redirecting traffic to an
interface are mutually
exclusive with each other
in the same traffic
behavior. The last
redirecting action
configured takes effect.
N/A