R3303-HP HSR6800 Routers ACL and QoS Configuration Guide

95
Configuring traffic redirecting
This feature is supported only on SAP modules operating in bridge mode.
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 guidelines
• 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.
• You can use the display traffic behavior { system-defined | user-defined } [ behavior-name ] [ |
{ begin | exclude | include } regular-expression ] command to view the traffic redirecting
configuration.
Configuration procedure
To configure traffic redirecting:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Create a class and enter
class view.
traffic classifier classifier-name [ operator { and
| or } ]
N/A
3. Configure match criteria.
if-match [ not ] match-criteria N/A
4. Return to system view.
quit N/A
5. Create a behavior and
enter behavior view.
traffic behavior behavior-name N/A
6. Configure a traffic
redirecting action.
redirect { cpu | interface interface-type
interface-number | next-hop { ipv4-add1
[ ipv4-add2 ]| ipv6-add1 [ ipv6-add2 ] } }
Optional.
7. Return to system view.
quit N/A
8. Create a policy and enter
policy view.
qos policy policy-name N/A