From: Daniel_Steyn@Dell.com
Date: Thu Mar 22 2007 - 17:20:23 ART
Dot1q also works for backward compatibility for devices that do not
support tagging. Obviously this doesn't matter on links between
switches but it does matter when you are tagging to the edge. Take the
voip world for example - the phone will typically tag all voip traffic
with a specified vlan but will just pass through the data traffic
without a tag. If someone were to remove the phone and plug the
workstation directly into that same port on the switch they would still
have access without the use of the phone as traffic would traverse the
native vlan.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
anthony.sequeira@thomson.com
Sent: Thursday, March 22, 2007 9:34 AM
To: ivanov.ivan@gmail.com; joshualixin@gmail.com
Cc: ccielab@groupstudy.com
Subject: RE: Native VLAN
I think the feature was originally designed as kind of a safety
mechanism to ensure traffic would still flow through a topology for one
VLAN if something happened to trunk link status.
I would guess that the Management VLAN was the one they had in mind so
that you could still manage your devices if trunk links failed to be
trunk links anymore.
Perhaps someone a bit more "old school" can shed light on why we are
stuck with the Native VLAN in 802.1Q.
Anthony J. Sequeira
#15626
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ivan Ivanov
Sent: Thursday, March 22, 2007 3:31 AM
To: Joshua
Cc: ccielab@groupstudy.com
Subject: Re: Native VLAN
Hello,
Here you can see some examples
http://www.netmasterclass.net/site/articles/Mini%20Scenarios%20with%20th
e%20Native%20VLAN.pdf
Hope this helps!
On 3/22/07, Joshua <joshualixin@gmail.com> wrote:
> Hi,
>
> A simple question, but has confused me. Why we need a native VLAN in
Dot1q?
> What the purpose?
>
> Thanks!
>
>
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:52 ART