I have a 5500, ports are placed for example in VLAN 1 or VLAN 2
The port is set up as a trunk for all VLANs.
So does this trunk all the VLANs and if so what is the relevance od the port
being in particular VLAN??
Connected to an access port is typically a single host. Connected to a
trunk port is another trunk port, which then gives you a "trunk link". At
the end of the trunk link, the destination port/s for each frame is based on
its VLAN tag. If there are no access ports that match the VLAN tag or trunk
links which trunk the VLAN further, the frame would be dropped.
Of course with VTP pruning the frame would not have been trunked across a
link which didn't have an option to proceed further.
BernieM
"Dave Bradley" <d.j.bradley@[no spam please]btinternet.com> wrote in message
news:9tqeej$650$1...@neptunium.btinternet.com...
the port in question is on a ditribution switch placed in a vlan & setup as
a trunk for vlans 1- 1005 this is connected to an access switch
e.g.
set vlan 560 4/10
set trunk 4/10 1-1005
both commands on one port..
"Bernie M" <m...@home.com> wrote in message
news:3c00c59e$0$10231$afc3...@news.optusnet.com.au...
--
-=Repy to group only... no personal=-
"Dave Bradley" <d.j.bradley@[no spam please]btinternet.com> wrote in message
news:9tr2p6$8ts$1...@neptunium.btinternet.com...
The first sets 4/10's native VLAN as 560. Actually, it just sets the
vlan of the port to 560 (native vlan comes into play after you trunk
it). Then the second line tells the switch to trunk VLANs 1 through
1005. If the trunk should fail, only the native VLAN will be
transported across the link.
"Sho trunk" will tell you what current native vlan is. Also, dot1q will
not tag native vlan by default, Newer CatOS has the option of "dot1q-
tag-all" (or something like that) to tag the native vlan as well.
--
hsb
"Somehow I imagined this experience would be more rewarding" Calvin
********************************************************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************
--
-=Repy to group only... no personal=-
"Hansang Bae" <hbae_@_nyc.rr.com.REMOVE_> wrote in message
news:MPG.166afaebe...@news-server.nyc.rr.com...
"Dennis" <den...@nospam.com> wrote in message
news:xzdM7.500414$Lg.20...@sjcpnn01.usenetserver.com...
> "Hansang Bae" <hbae_@_nyc.rr.com.REMOVE_> wrote in message
> > The first sets 4/10's native VLAN as 560. Actually, it just sets the
> > vlan of the port to 560 (native vlan comes into play after you trunk
> > it). Then the second line tells the switch to trunk VLANs 1 through
> > 1005. If the trunk should fail, only the native VLAN will be
> > transported across the link.
> > "Sho trunk" will tell you what current native vlan is. Also, dot1q will
> > not tag native vlan by default, Newer CatOS has the option of "dot1q-
> > tag-all" (or something like that) to tag the native vlan as well.
In article <xzdM7.500414$Lg.20...@sjcpnn01.usenetserver.com>,
den...@nospam.com says...
> So you're saying you can use the two together... set the port as member of a
> vlan and set the port as a trunk port?
*IF* the trunk dies, only the native VLAN's packets will be transported.
So while the trunk is active, it's kind of a moot point.
Also, in dot1q, since the native vlans are not tagged by default, I
guess you can say that VLAN 560 and trunked vlans are working together.
BTW, is this a study question or do you have a specific reason for
asking?
Dennis
--
-=Repy to group only... no personal=-
"Hansang Bae" <hbae_@_nyc.rr.com.REMOVE_> wrote in message
news:MPG.166b441f...@news-server.nyc.rr.com...
I am actually a CCNP and this is a issue that I have found in my job.
I've been working with routers for some time but not a great deal with
switches and in particular the 'set' based switches and the larger switches
aimed at the core/distribution level.
This industry is always a learning experience, even bearing in mind all the
courses you cover just scratch the surface!
My next foray is VoIP, that will be fun!
"Hansang Bae" <hbae_@_nyc.rr.com.REMOVE_> wrote in message
news:MPG.166b441f...@news-server.nyc.rr.com...