Configuring Traffic Redirecting; Configuration Restrictions And Guidelines; Configuration Procedure - HP 6125G Configuration Manual

Configuring traffic redirecting

Traffic redirecting is the action of redirecting the packets matching the specific match criteria to a certain
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. Note that this action applies to only Layer 2 packets, and the target interface must be a
Layer 2 interface.
Redirecting traffic to the next hop—redirects packets that require processing by an interface to the
•
interface. This action only applies to Layer 3 packets.

Configuration restrictions and guidelines

The actions of redirecting traffic to the CPU, redirecting traffic to an interface, and redirecting traffic
•
to the next hop are mutually exclusive with each other in the same traffic behavior.
A QoS policy with traffic redirecting actions can be applied to only the inbound direction of a port,
•
VLAN, or all ports.
You can use the display traffic behavior user-defined command to view the traffic redirecting
•
configuration.

Configuration procedure

To configure traffic redirecting:
Step
1. Enter system view.
2. Create a class and enter class
view.
3. Configure match criteria.
4. Return to system view.
5. Create a behavior and enter
behavior view.
6. Configure a traffic redirecting
action.
7. Return to system view.
8. Create a policy and enter
policy view.
Command
system-view
traffic classifier tcl-name [ operator { and | or } ]
if-match match-criteria
quit
traffic behavior behavior-name
redirect { cpu | interface interface-type
interface-number | next-hop { ipv4-add1
[ ipv4-add2 ] | ipv6-add1 [ interface-type
interface-number ] [ ipv6-add2 [ interface-type
interface-number ] ] } }
quit
qos policy policy-name
59
Remarks
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A