Thanks for the response guys. Tyson my first instinct was to do the debug l2protocol-tunnel however i dont think i saw anything of importance.
Maybe i will go back and cause the problem with the debug on and see what happens. This task really beat me up and anything that woudl help isolate the exact issue quickly is what i was going for. Thanks Again Aaron On Sat, Aug 14, 2010 at 10:10 PM, Tyson Scott <[email protected]> wrote: > debug l2protocol-tunnel [option] > > > > In a SP environment you would never have the same switch connected without > a q-in-q and another interface with a q-in-q tunnel. The CCIE lab is a lone > situation of this problem. (permitting you have it configured properly in > real world situations). > > > > Regards, > > > > Tyson Scott - CCIE #13513 R&S, Security, and SP > > Managing Partner / Sr. Instructor - IPexpert, Inc. > > Mailto: [email protected] > > Telephone: +1.810.326.1444, ext. 208 > > Live Assistance, Please visit: www.ipexpert.com/chat > > eFax: +1.810.454.0130 > > > > IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, > Audio Tools, Online Hardware Rental and Classroom Training for the Cisco > CCIE (R&S, Voice, Security & Service Provider) certification(s) with > training locations throughout the United States, Europe, South Asia and > Australia. Be sure to visit our online communities at > www.ipexpert.com/communities and our public website at www.ipexpert.com > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Aaron Moreck > *Sent:* Saturday, August 14, 2010 11:00 AM > *To:* [email protected] > *Subject:* [OSL | CCIE_RS] dot1q-in-q with L2 Protocol Tunneling > > > > I was having a bit of an issue with dot1q-in-q and l2 protocol tunneling > where nterfaces were going err-disabled. > > I understand now (and I stresss the word now) that if a packet with the > special multicast mac address used for tunneling is recieved on an > interface configured for l2 protocol tunneling it will go err-disabled. > > > > The fix for this is to restrict specific VLANS on the trunks. > > > > However, I found this easier said than done (especially if this was a large > service provider network). I have to admit that this is the very first time > playing with dot1q-in-q tunneling so i am hoping some of you guys have been > there and done that so to speak. > > > > Is there any debug command or show command that can help me determine what > VLAN is causing the issue to make it easier to track down? > > > Thanks > > Aaron >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
