[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
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.
>From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Joseph Jenkins
>Sent: Thursday, April 05, 2018 4:16 PM
>To: Robert Webb
>Cc: nanog at 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.