[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
- Subject: Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
- From: SNaslund at medline.com (Naslund, Steve)
- Date: Thu, 5 Apr 2018 21:26:14 +0000
- In-reply-to: <CACUUO4H7Wx5=vUVyDNCYQZiAnyRm_Q-Vyyh6-bB2LjPfLoaJVA@mail.gmail.com>
- References: <CACUUO4FSnMDGv72Z74W0q+WXKMmZn0CRC4W0fON1TS=WexVPXg@mail.gmail.com> <BL0PR1501MB213188C1CF3EF566973D1455C8BB0@BL0PR1501MB2131.namprd15.prod.outlook.com> <CACUUO4H7Wx5=vUVyDNCYQZiAnyRm_Q-Vyyh6-bB2LjPfLoaJVA@mail.gmail.com>
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 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.
>
>Thanks Everyone.