Re: Juniper Config Commit causes Cisco Etherchannels to go into err-disable state

[Joseph Jenkins <joe () breathe-underwater com>]

Steve let me clarify the config I am applying has nothing to do with an
LACP trunk or any of my existing LACP trunks. It is a completely different
configuration on a completely different interface, the only similarity is
that I am trying to configure a trunk interface on the Juniper side for
multiple vlans. There is no LACP configuration involved.

On Thu, Apr 5, 2018 at 2:26 PM, Naslund, Steve <SNaslund () medline com> wrote:

> It really does not resolve anything it just allows a bad configuration to
> work.  The guard is there so that if one side is configured as a channel
> and the other side is not, the channel gets shut down.  Allowing it to
> remain up can cause a BPDU loop.  Your spanning tree is trying to tell you
> something, you should listen or you could get really hard to isolate issues.
>
> Steven Naslund
> Chicago IL
>
> > -----Original Message-----
> > From: NANOG [mailto:nanog-bounces () nanog org] On Behalf Of Joseph Jenkins
> > Sent: Thursday, April 05, 2018 4:16 PM
> > To: Robert Webb
> > Cc: nanog () nanog org
> > Subject: Re: Juniper Config Commit causes Cisco Etherchannels to go into
> err-disable state
> > No there isn't, but from what I am getting responses both onlist and off
> list is to just run this on the Cisco switches:
> > no spanning-tree etherchannel guard misconfig
> >
> > and that should resolve the issue.
> >
> > Thanks Everyone.