From: Scott M Vermillion (scott_ccie_list@it-ag.com)
Date: Thu Oct 02 2008 - 16:52:36 ART
Hey Nit,
One area where I think you want to take special care with this is q-in-q
tunneling. The example that used to be on the DocCD was horrible in terms
of its clarity (not sure what might be out there now). But probably about
this time last year we had some protracted discussions about how
customer/enterprise traffic can get scattered to the winds inside of the
carrier network in q-in-q tunneling scenarios.
If that's what you were contemplating, I'll see if I can dig up any of that
old traffic and forward it along (no promises, though - some of these
folders have grown rather bloated)...
Cheers,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
GAURAV MADAN
Sent: Thursday, October 02, 2008 12:08 PM
To: Nitro Drops
Cc: ccielab@groupstudy.com
Subject: Re: Dot1q
If You want that even the native vlan should be tagged .. use this CLI .
By default native vlan ( default vlan 1 ) is not tagged over a dot1q trunk
link
HTH
Gaurav Madan
On Thu, Oct 2, 2008 at 8:57 AM, Nitro Drops <nitrodrops@hotmail.com> wrote:
> When configuring the trunk using 'encapsulation dot1q', is it always a
> mandatory to configure 'vlan dot1q tag native' under the global
> configurations? to make vlan1 become untag over the trunk?
> _________________________________________________________________
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:18 ARST