From: Swan, Jay (jswan@sugf.com)
Date: Thu Mar 22 2007 - 19:02:46 ART
One "old school" reason I know of is this: say you have two switches
that connect through a hub. With the native VLAN feature you can attach
devices to the hub, and as long as they're in the native VLAN, they'll
be able to process the untagged traffic correctly. When they receive
traffic for other VLANs that have the dot1q tag attached, they'll simply
discard it.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
anthony.sequeira@thomson.com
Sent: Thursday, March 22, 2007 8: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
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:52 ART