Policy Action Redirect Port - Alcatel-Lucent OmniSwitch 6850-48 Cli Reference Manual

policy action redirect port

Redirects all traffic (flooded, bridged, routed, and multicast) matching a redirect policy to the specified
port instead of the port to which the traffic was destined.
policy action action_name redirect port slot/port
policy action action_name no redirect port
Syntax Definitions
action_name
slot/port
Defaults
N/A
Platforms Supported
OmniSwitch 6400, 6850, 6850E, 6855, 9000E
Usage Guidelines
•
Use the no form of the command to remove redirect port from the policy action.
•
When redirecting routed traffic from VLAN A to VLAN B, the redirect port must belong to VLAN B
(tagged or default VLAN).
•
Routed packets (from VLAN A to VLAN B) are not modified after they are redirected; the source and
MAC address remain the same. In addition, if the redirect port is tagged, the redirected packets will
have a tag from the ingress VLAN A.
•
If a route exists for the redirected flow, then redirected packets are the final post-routing packets.
•
If a route does not exist for the redirected flow, the flow is not redirected to the specified port or link
aggregate and is "blackholed". As soon as a route is available, the flow is then redirected as specified
in the policy.
•
In most cases, a redirected flow will not trigger an update to the routing and ARP tables. If necessary,
create a static route for the flow or assign the redirect port to the ingress VLAN (VLAN A) to send
packets to the redirect port until a route is available.
•
When redirecting bridged traffic on VLAN A, the redirect port must belong to VLAN A (tagged or
default VLAN).
Examples
-> policy action rp01 redirect port 1/12
-> policy action rp01 no redirect port
page 33-160
The name of the action.
The slot and port number (or range of ports) that will receive the redi-
rected traffic.
QoS Policy Commands
OmniSwitch CLI Reference Guide June 2012