RE: DOT1Q NATIVE VLAN STANDARD or NON-STANDARD

From: Larry Letterman \(lletterm\) (lletterm@cisco.com)
Date: Wed Oct 12 2005 - 13:21:22 GMT-3


Ed,

Set up two routers with dot1q sub-interfaces...connect the FaEthernets
to a 3550/3750,
Set the trunk ports for that switch so that the data vlan is the native
vlan. Setup the hsrp
On the routers, and you'll see that the native vlan being set
incorrectly will alter the
Opeartion of things..you can always leave it to the default of vlan 1..

 
Larry Letterman
INS-NW-WEST
Cisco Systems
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Ed Lui
Sent: Wednesday, October 12, 2005 11:03 AM
To: ccielab@groupstudy.com
Subject: DOT1Q NATIVE VLAN STANDARD or NON-STANDARD

Hi group,
I have no luck finding out why we need native vlan in dot1q. I
understand that native vlan should be defined on a trunk port. I came
across a router on a stick lab scenario, which I did not define the
native vlan and it is still working fine. Read through the dot1q
standard on ieee.org<http://ieee.org>but still can not figure out my
question.
 So, what is the difference between having a native and not having a
native vlan defined ? The only thing I can think of is, tagged frame can
carry QoS information. Other than that, what is the benefit or
difference between tagged and untagged frames ? Why define a native ?

Thanks in advance for any help or hint,

Ed Lui

TRUNK W/O NATIVE VLAN
2621=============================3550



This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:50 GMT-3