native vlan question|
|
|
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
Posted by on April 15, 2008, 3:51 am
Please log in for more thread options
I think using "vlan dot1q tag native" should eliminate this question. at least for sw---sw connection. (all tagged just like isl) I may not fully understand what's purpose why cisco make "native vlan". Some article say because of backward compatible with 802.3. Can anyone give an example? TIA, st | |
|
Posted by Trendkill on April 15, 2008, 7:13 am
Please log in for more thread options Here are some good posts on this topic. Probably better than one of us typing up several paragraphs. The second article explains native vlan / vlan 1, and management interface concerns. http://www.velocityreviews.com/forums/t30335-native-vlan.html http://www.velocityreviews.com/forums/t40938-native-and-management-vlan-quotvlan-1quot.html | |
|
Posted by on April 15, 2008, 1:07 pm
Please log in for more thread options On 4=D4=C215=C8=D5, =C9=CF=CE=E74=CA=B113=B7=D6, Trendkill <jpma...@gmail.co=
m> wrote:
> On Apr 15, 3:51 am, aaabb...@hotmail.com wrote: > > > A lot of people ask native vlan question.
> > I think using "vlan dot1q tag native" should eliminate this question. > > at least for sw---sw connection. (all tagged just like isl) > > I may not fully understand what's purpose why cisco make "native > > vlan". > > Some article say because of backward compatible with 802.3. > > Can anyone give an example? >
> > TIA,
> > st >
locityreviews.com/forums/t40938-native-and-management-vl...
> Here are some good posts on this topic. Probably better than one of > us typing up several paragraphs. The second article explains native > vlan / vlan 1, and management interface concerns. > > http://www.velocityreviews.com/forums/t30335-native-vlan.htmlhttp://www.ve= Still confuse something. | |
|
Posted by stephen on April 15, 2008, 4:13 pm
Please log in for more thread options > A lot of people ask native vlan question.
> I think using "vlan dot1q tag native" should eliminate this question. > at least for sw---sw connection. (all tagged just like isl) > I may not fully understand what's purpose why cisco make "native > vlan". cisco didnt invent this - it is part of 802.1Q. > Some article say because of backward compatible with 802.3.
i suggest you try to find the standard and read around that, maybe start at www.ieee.org AFAIR some of the standards docs are without charge for Ethernet. > Can anyone give an example?
there are 2 Qs to think about. 1. set a port to be tagged - what do you do with a packet that arrives with no tag? the 2 common answers are to throw it away, or to put it into some sort of "default VLAN" - that is what untagged means for incoming packets. not putting a tag on outbound packets form that VLAN on that port allows 2 way comms. this sounds silly - but it is what often needs to happen when you hook up an unconfigured device to set it up. 2. what happens when you want to split up 2 streams of packets on a port? sometimes you have a device that will add its own stream of packets to a set it gets from elsewhere - the classic case is an IP phone where there is a plug on the phone to connect a PC. - Pcs dont normally send tagged frames, and the 3 port bridge in the phone doesnt have the horsepower to wrap a tag around every packet. - but you want the phone traffic kept separate from PC (security, QoS and so on). So - pass the PC packet thru untagged, and tag the phone traffic. At the switch the PC "stuff" is untagged and goes into the native VLAN, phone traffic is tagged and goes into a different VLAN. >
--
> TIA, > st > Regards stephen_hope@xyzworld.com - replace xyz with ntl | |
|
Posted by on April 15, 2008, 11:31 pm
Please log in for more thread options On 4=D4=C215=C8=D5, =CF=C2=CE=E71=CA=B113=B7=D6, "stephen" <stephen_h...@xyz=
world.com> wrote:
> > > > A lot of people ask native vlan question.
> > I think using "vlan dot1q tag native" should eliminate this question. > > at least for sw---sw connection. (all tagged just like isl) > > I may not fully understand what's purpose why cisco make "native > > vlan". >
> cisco didnt invent this - it is part of 802.1Q. > > > Some article say because of backward compatible with 802.3.
>
> i suggest you try to find the standard and read around that, > maybe start atwww.ieee.org > > AFAIR some of the standards docs are without charge for Ethernet. > > > Can anyone give an example?
>
> there are 2 Qs to think about. > > 1. set a port to be tagged > - what do you do with a packet that arrives with no tag? > > the 2 common answers are to throw it away, or to put it into some sort of > "default VLAN" - that is what untagged means for incoming packets. > > not putting a tag on outbound packets form that VLAN on that port allows 2= > way comms.
an
> > this sounds silly - but it is what often needs to happen when you hook up = > unconfigured device to set it up.
et
> > 2. what happens when you want to split up 2 streams of packets on a port? > > sometimes you have a device that will add its own stream of packets to a s= > it gets from elsewhere
> - the classic case is an IP phone where there is a plug on the phone to > connect a PC. > - Pcs dont normally send tagged frames, and the 3 port bridge in the phone= > doesnt have the horsepower to wrap a tag around every packet.
> - but you want the phone traffic kept separate from PC (security, QoS and= > so on).
> > So - pass the PC packet thru untagged, and tag the phone traffic. > At the switch the PC "stuff" is untagged and goes into the native VLAN, > phone traffic is tagged and goes into a different VLAN. > > > TIA,
> > st >
> -- > Regards > > stephen_h...@xyzworld.com - replace xyz with ntl Thanks, For "Some article say because of backward compatible with 802.3" they may think far end is Hub or switch/bridge which does not support 802.3, right? One more question, when a access port receive a untag frame, does it add a 802.1q tag or some other tag to make sure it can go same vlan inside of this switch? | |
| Similar Threads | Posted |
| Native VLAN question | November 22, 2005, 5:58 am |
| native vlan question | April 15, 2008, 3:51 am |
| Native, and management vlan "Vlan 1" | September 21, 2005, 2:50 pm |
| VLAN Project and Native VLAN | July 13, 2007, 5:06 am |
| Native VLAN | February 8, 2007, 9:40 pm |
| native vlan | December 18, 2008, 6:45 am |
| Native VLAN Warning | August 23, 2005, 8:24 am |
| understanding native VLAN | September 23, 2005, 10:10 pm |
| native vlan for mgmt | July 18, 2009, 9:20 pm |
| Change native VLAN on ASA 5520 | July 5, 2007, 6:17 am |
| Native Vlan Mismatch error | January 20, 2008, 2:09 am |
| change native vlan globaly on 3560 | January 5, 2007, 2:08 pm |
| Native VLAN mismatch on Cisco 2950 | August 9, 2007, 6:30 pm |
| Changing native vlan on access port | August 12, 2009, 6:53 pm |
| Native Vlan Cisco 1200 Access Point | March 11, 2006, 7:50 pm |
|
Home Cabling GuideFinally, an instantly downloadable book that saves you thousands in home improvement dollars! Enjoy living in 21st century technology-advanced home while increasing its selling value and competitive advantage on the real estate market. Whether your cabling is for home office or high-tech leisure, you can wire your home yourself or learn "wirish" to speak with your cabling contractors in their language! Learn More |
> I think using "vlan dot1q tag native" should eliminate this question.
> at least for sw---sw connection. (all tagged just like isl)
> I may not fully understand what's purpose why cisco make "native
> vlan".
> Some article say because of backward compatible with 802.3.
> Can anyone give an example?
>
> TIA,
> st