frnkblk at iname
Mar 10, 2012, 9:59 PM
Post #5 of 5
Thanks for all the clarification received on and off list. I was operating
under the understanding that when in passive mode it fell back to static,
but that's not the case.
From: foundry-nsp-bounces [at] puck
[mailto:foundry-nsp-bounces [at] puck] On Behalf Of George B.
Sent: Friday, March 09, 2012 12:46 PM
To: William McLendon
Cc: foundry-nsp [at] puck
Subject: Re: [f-nsp] LAG behavior on MLXe-4
On Fri, Mar 9, 2012 at 10:27 AM, William McLendon <wimclend [at] gmail>
> 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.
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
foundry-nsp mailing list
foundry-nsp [at] puck