Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

sameat

6 Posts

7160

October 27th, 2006 14:00

VLAN Basics

I have a very simple vlan implementation that I am trying to improve.

Using several 3448's connected to a 6024, I have created vlan2 on several of the 3448's. All ports in the second vlan are untagged. I am using separate cables (one for each vlan) to connect to the 6024 , but I am quickly using up the ports on the 6024.

I want to create a trunk so that traffic from both VLANs gets to the 6024 on one cable.

Can anybody give some quick tips?

Thanks

cerbera_a84f2d

176 Posts

October 27th, 2006 15:00

Ifd you are using the web interface, there are two screens you will need to use, VLAN membership and VLAN Port Settings.
 
First thing you need to do is create the VLANs on each switch using the membership page.
 
On the port settings page, there are two things that you need to be aware of, Port VLAN mode and Port VLAN ID(PVID)
 
The port that links the 3400 to the 6024 needs to be configured as a 'trunk' port - this allows the port to carry traffic tagged for all VLANs whilst keeping separation between them. You then need to place this port into every VLAN as a tagged port.
 
The other ports will be 'access' by default with a PVID of 1 until you move them to another VLAN; they can be configured as general ports, which means that you can tag the port into more than 1 VLAN; if you use 'general' then you can set the PVID to the VLAN of your choice.
 
The PVID is important, as it is that value which identifies the data into a particular VLAN  - example......port 10 is an access port, placed into VLAN 10 with a PVID of 10, port 11 into VLAN 11 with a PVID off 11, and port g1 is an uplink port to another switch, and is configured as a trunk port, tagged into VLANs 10 & 11.
 
Untagged packet ( untagged means it carries no VLAN ID ) arrives at port 10; the switch will add a VLAN tag of 10, and forward it accordingly - if the destination is across the uplink it will be forwarded up the trunk port; when it arrives at the destination switch, the tag tells that switch it is for VLAN 10, and is then again forwarded as appropriate.
 
When an untagged packet arrives at port 11, exactly the same thing happens, but with a tag of 11 being added.
 
So to summarise, lets say you have two 3400s , uplinked from g1 to port 23 and 24 respectively on the 6024, and you want to trunk VLANs 10 & 11 across the switches.
 
Create VLANs 10&11 on all three switches; configure G1 on the 3400s and ports 23 and 24 on the 6024 as 'trunk' ports; place all of these ports into VLANs 10 & 11 as tagged ports.
 
Then just place the ports on the 3400s into VLAN 10 or 11 as you wish.
 

Message Edited by cerbera on 10-27-2006 11:18 AM

sameat

6 Posts

October 28th, 2006 15:00

Thanks for taking the time to write that up. I'm going to play with this a little, and I might be back with question.

I appreciate the help.

Was this post helpful?

View All

0 events found

No Events found!

Top