[f-nsp] LAG behavior on MLXe-4

George B. georgeb at gmail.com
Fri Mar 9 13:46:01 EST 2012


On Fri, Mar 9, 2012 at 10:27 AM, William McLendon <wimclend at gmail.com> wrote:
> if LACP is used, at least one side must be configured as Active (it will send the LACP PDUs).  both sides can be active, but both sides can not be passive, or it will not work because neither side would be sending LACP PDUs, and thus not know about each other.
>
>
> Will
>

As is the case with Static on one side and Passive on the other.  A
static lag will not transmit LACP and so the passive side will not
link up (and neither will an active, in this case).  If one side is
"Static" or "On" then both sides need to be static or on.  If one side
is active, then the other side must be either active or passive.  If
one side is passive, then the other side must be active.

Active -> Passive  works
Active -> Active  works
Static -> Static works
Passive -> Passive will not work
Static -> Passive will not work
Static -> Active will not work




More information about the foundry-nsp mailing list