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

• Previous message (by thread): Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
• Next message (by thread): Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Got it.  Do any of those trunks add a new VLAN to the switch that was not active before?  If so, that would cause a BPDU over all trunks that allow that VLAN.  Even if the port is not up yet, by adding the VLAN to ANY trunk you are implying that it should be active on ALL trunks that are not VLAN limited.

Steve

>-----Original Message-----
>From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Joseph Jenkins
>Sent: Thursday, April 05, 2018 4:34 PM
>To: nanog at nanog.org
>Subject: Re: Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
>
>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.

• Previous message (by thread): Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
• Next message (by thread): Juniper Config Commit causes Cisco Etherchannels to go into err-disable state
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]