From: Scott Vermillion (scott_ccie_list.com@it-ag.com)
Date: Fri Sep 14 2007 - 14:28:21 ART
Ahhhh. I think this makes much more sense now! I wonder why they reflect
the customer switches (A & D) as having Native VLAN 40? It seems to be
irrelevant and leads one to believe this where the problem lies. But I now
see too that they show the B <-> C carrier trunk as native VLAN 40, where
the true problem lies...
Thanks Eric!
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Eric
Leung
Sent: Friday, September 14, 2007 12:33 AM
To: Scott M Vermillion
Cc: Cisco certification
Subject: Re: Q-in-Q Native VLAN
Hi Scott,
The native vlan of the tunneling port at the SP Edge SW should not be the
same as the native vlan of the trunk between SP Edge switch and other SP
Core Switch. It's nothing related to the native vlan of the customer switch.
Thanks,
Eric.
2007/9/14, Scott M Vermillion <scott@it-ag.com>:
>
> All,
>
>
>
> Under the "Native VLAN" discussion in the below link, it is explained that
> if the customer native VLAN happens to be the same as the tunnel port
> access
> VLAN, then no metro tags are added to any of that customer's traffic. In
> the example, VLAN 40 is native on the customer trunk and that is the
> access
> VLAN of the carrier tunnel port. VLAN 30 traffic comes in and is not
> tagged. Is this something I'm just supposed to accept and not fully
> understand or is there a common-sense logic to this that I'm just plain
> missing?
>
>
>
> Thanks in advance,
>
>
> Scott
>
>
>
>
>
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12240se/scg/swtu
> nnel.htm
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:11 ART