Configuring traffic redirecting, Overview, Configuration restrictions and guidelines – H3C Technologies H3C S12500 Series Switches User Manual
Page 74
65
Configuring traffic redirecting
Overview
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. 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
When you configure traffic redirecting, follow these 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.
•
If you specify a next hop as the redirect destination, make sure the traffic identified by match criteria
has the same IP version as the IP address of the next hop. For example, if the next hop is an IPv4
node, avoid using an IPv6 ACL for classification.
•
The default of the fail-action keyword, if supported, is forward.
•
You can use the display traffic behavior user-defined [ behavior-name ] [ | { begin | exclude |
include } regular-expression ] command to view the traffic redirecting configuration.
•
In IRF mode, the switch does not support redirecting traffic to an aggregate interface.
•
Different from looking up the routing table based on the destination address of an IP packet, the
policy-based routing (the action of redirecting traffic to the next hop) can flexibly select routes for
traffic based on source IP address, and so on. The policy-based routing takes precedence over
common routing. A packet is forwarded according to common routing if it does not match the
policy-based routing configuration.
•
On a switch operating in IRF mode, when you configure cross-switch traffic redirecting to a port of
an OAA card, make sure the port of the OAA card is in VLAN 1.
•
In standalone mode, the switch does not support redirecting traffic to an aggregate interface on an
LST1IPS2A1 card.
•
In IRF mode, the switch does not support redirecting traffic to the second internal port on an
LST1IPS2A1 card on another member device.
•
To redirect traffic correctly to an internal port on an LST1IPS2A1 card by using a QoS policy, you
must perform the following tasks:
{
Assign the two internal ports to an aggregation group.
{
Set the minimum number of Selected ports in the aggregation group to 2.