70
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 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
class exists.
3. Configure match criteria.
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
behavior exists.
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.
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.
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
policy exists.
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, no
class-behavior
association is configured
for a QoS policy.
To Next Page
Loading...
Need help?
General