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

Reply via email to