I don't see any issue with the snippet of the config you provided for the
"Firewall Port". Is there a chance that the port ge-0/0/67 is referenced
somewhere else in the Juniper config that when applying your trunk setup is
causing issues?
Just throw that out off the top of my head and not reall
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
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.
On Thu, Apr 5, 2018 at 2:10 PM, Robert Webb wrote:
> I don't see any issue
I am kind of confused by your configuration. If the Cisco side is configured
as LACP trunk, then the Juniper side also needs to be configured as LACP
trunks. Spanning-tree would be getting confused because the Cisco is treating
the LACP trunk as a single interface for purposes of spanning-tree
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
12 matches
Mail list logo
