Reset Search
 

 

Article

How to redirect traffic to egress a specific port in a LAG?

« Go Back

Information

 
TitleHow to redirect traffic to egress a specific port in a LAG?
Objective
The objective is to use the "redirect-port-no-sharing" action modifier in an ACL to make traffic egress a specific port in a LAG
Environment
  • All EXOS
  • All Summit
  • All Blackdiamond
Procedure
Syntax: In the ACL action modifier, we need to use -
redirect-port-no-sharing <port number>

Example: Assuming port(s) 1,2 is in a LAG group and port 1 is the LAG master. We can also assume that, by hashing, the traffic takes port 1 to egress.
If we want to redirect traffic destined to 10.1.1.1/32 through port 2 in the LAG group, we can use the following ACL -
entry one {
if {
destination-address 10.1.1.1/32;
} then {
redirect-port-no-sharing 2;
}
}
Additional notes
When using the "redirect-port-no-sharing <port #>" syntax, it ignores the hashing algorithm and directly sends the traffic out through the assigned redirect port in the ACL.
However, if we use the regular "redirect-port <port #>" modifier, the traffic will still be subjected to hashing on egress and exit via the port determined post hashing.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255