From: Morris, Jason L. (Jasmorris@checkngo.com)
Date: Tue May 27 2008 - 14:08:32 ART
Funny this should come up. I was just talking to a friend about an hour
ago who's having trouble passing traffic between two sites that are both
connecting to a metro-e network with dot1q trunks between them. He's
using VLAN1 as his default vlan for all the data (yeah I know), and has
been having problems passing traffic on that vlan. The first think I
told him to try was tagging the native vlan on his edge switches. I
think he's going to try it tonight or sometime within the next couple of
days. I'll keep you updated.
Jason Morris
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Johan Kusuma Chandra
Sent: Sunday, May 25, 2008 9:16 AM
To: Sadiq Yakasai
Cc: ccielab@groupstudy.com
Subject: Re: RE: Dot1Q Tunneling
Hi Mr Sadiq and other Experts,
Thanks a lot for your advice. I was thinking the same thing with you..
However when I'm doing this Graded Mock Lab, I did the dot1q tunnel
and add the native vlan tagging as requested (everything works fine).
And on the report sheet the Proctor told me that I should configure the
Native VLAN on the other switches (Customer Switches) too. Eventhough
not explicitly tasked.
If I may further request for your kind advices, in your experience is
there any possible requirement outside the Dot1Q tunnel (in scope of
CCIE R&S Lab Exam) that may implicitly lead to the configuration of
Dot1Q Native VLAN tagging?
Thanks again for your advices.
Johan KC
Sadiq Yakasai <sadiqtanko@gmail.com> wrote:
Hi Johan,
It is not a requirement to configure the customer switches to tag
native VLANs in a setup like that one. Find more information about
that here:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3560/software/relea
se/12.2_44_se/configuration/guide/swtunnel.html#wp1008635
HTH
Sadiq
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:18 ART