[j-nsp] LACP/LAG

Kurt Bales kwbales at kwbales.net
Thu Oct 17 18:31:42 EDT 2013


Like most of the replies here, I usually run LACP where ever possible. Its
a worth it for the added assurance that things are cabled correctly and
both sides agree on port pairs.

Having said that, there are some caveats:
 - On some hardware, certain features are not supported on AE interfaces,
but this is regardless of whether you are using LACP or not.
 - It would appear that the LACP process is one of the very last processes
to come up after reboot. It makes sense of course as the IO cards and
controllers need to become fully operational before the control plane can
start looking for LACP peers, but this can add additional time during a
reboot scenario. Just be aware and test that the timing is appropriate /
acceptable.

Regards,

Kurt Bales
@networkjanitor JNCIE-ENT #368




> > Hi.
> >
> > Any reason not to run LACP on a LAG link?
> >
> > Setting up a new LAG with some gear on our MX and have setup the AE
> > interface and turned it up, but have not actually cut traffic over to it
> yet.
> >
> > They were saying run in passive or no LACP, with it just
> >
> > On cisco one does: channel-group <x> mode on/active/passive and I
> > did have trouble getting both sides to come up properly on the cisco, one
> > side would always come up suspended until I set the ports to just on.
> >
> > I have done the same on the MX side, except I did not use
> aggregated-ether-options lacp
> > and just left that statement out.
> >
> > Both sides came up on the MX and it looks ok. Am I going to get bitten
> in the ass
> > at some point for not running LACP?
> >
> > Docs I see always configure LACP for LAGs, and mention not running it
> but never really
> > why you would.
> >
> > Thanks,
> > Keith
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> --
> ------------------------------------------------------------------------
> Christopher E. Brown   <chris.brown at acsalaska.net>   desk (907) 550-8393
>                                                      cell (907) 632-8492
> IP Engineer - ACS
> ------------------------------------------------------------------------
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list