I have cases open with both Cisco and Juniper on this, but wanted to see if
anyone else had seen an issue like this because support has no idea.
I have a Juniper QFX 5100 Core running in Virtual Chassis mode with 4
switches. I have 4 separate stacks of Cisco 3750 switches with 2x1GB
uplinks bound
my head and not really thinking it through.
Robert
-Original Message-
From: NANOG On Behalf Of Joseph Jenkins
Sent: Thursday, April 5, 2018 4:58 PM
To: nanog@nanog.org
Subject: Juniper Config Commit causes Cisco Etherchannels to go into
err-disable state
I have cases open with both Cisco
On Thu, Apr 5, 2018 at 3:58 PM Joseph Jenkins
wrote:
> Mar 14 07:11:33: %PM-4-ERR_DISABLE: channel-misconfig (STP) error detected
> on Po17, putting Po17 in err-disable state
>
We have to do this on all of our Cisco Port-channels that lead to Brocade
ICX switches:
no spanning-tree etherchannel g
of my head and not really thinking it
> through.
>
> Robert
>
> -Original Message-
> From: NANOG On Behalf Of Joseph Jenkins
> Sent: Thursday, April 5, 2018 4:58 PM
> To: nanog@nanog.org
> Subject: Juniper Config Commit causes Cisco Etherchannels to go into
> er
Chicago IL
>-Original Message-
>From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Joseph Jenkins
>Sent: Thursday, April 05, 2018 3:58 PM
>To: nanog@nanog.org
>ubject: Juniper Config Commit causes Cisco Etherchannels to go into
>err-disable state
>
>I h
rg
>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 misco
: NANOG [mailto:nanog-boun...@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 t
-boun...@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
>> >
>>
VLAN limited.
Steve
>-Original Message-
>From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Joseph Jenkins
>Sent: Thursday, April 05, 2018 4:34 PM
>To: nanog@nanog.org
>Subject: Re: Juniper Config Commit causes Cisco Etherchannels to go into
>err-disable state
>
>
> Steven Naslund
> Chicago IL
>
>> -Original Message-
>> From: NANOG [mailto:nanog-boun...@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 Co
ten or you could get really hard to isolate issues.
> >
> > Steven Naslund
> > Chicago IL
> >
> >> -Original Message-
> >> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Joseph Jenkins
> >> Sent: Thursday, April 05, 2018 4:16 P
Sounds like the Juniper is leaking a "default" BPDU as it resets the
various internal chip configurations, which the Cisco receives thus
triggering the err-disable.
/mark
Not sure exactly what your environment looks like, but we encountered
something similar when trunking Cisco-DELL and Cisco-Juniper switches.
We run RSTP on DELL and Juniper switches, but RPVST+ on Cisco. In the
beginning we just allow those VLANS we need between Cisco-DELL/Juniper
switches, then en
13 matches
Mail list logo
