Typically you see this when a port configured for "switchport mode dot1q-tunnel" and "l2protocol-tunnel" is receiving an l2protocol-tunnel frame from another switch that it is connected to. Make sure your customer is not configuring l2protocol-tunnel anywhere on their end, and is simply trunking to you.
On Wed, Sep 9, 2009 at 10:20 AM, Justin Guagliata <[email protected]> wrote: > I have a link with a provider spanning two locations. The provider is > running QinQ and we have a trunk setup across the link. Recently we had the > requirement to start doing QnQ for a few "customers" so we attempted to do > QinQ for our downstream neighbors. The problem is, when our downstream > "customer" plugs in one switch, our port on the provider side goes into > errdisable due to l2ptguard. > > I believe if the customer plugs a switch on the other side, the link will > come up and be fine. The problem is, we can't afford to lose our link > because the customer had a switch die or is missing a switch on one side for > some other reason. > > The only solution i can think up is to have the provider disable errdiable > for the l2ptguard cause. > > Does anyone else have any ideas, suggestion? > > Thanks, > > Justin > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > -- Regards, Joe Astorino - CCIE #24347 R&S Technical Instructor - IPexpert, Inc. Cell: +1.586.212.6107 Fax: +1.810.454.0130 Mailto: [email protected]
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
