I have followed the whitepaper "VLAN-Based Network Segmentation" to setup a VLAN between 2 swtiches.
Setup:
Switch-1:
Port 1 - Access VLAN 244
Port 2 - Access VLAN 244
Port g4 - Trunk VLAN 1 untaggged ,244 tagged
Switch-2:
Port 1 - General VLAN 1 untagged, 244 untagged
Port g4 - Trunk VLAN 1 untaggged ,244 tagged
Port Switch1-1 and Switch1-2 can communicate without any
problem at all. However, Switch2-1 is unable to communcate with
either of the 2 ports on Switch1. Can anybody see what
I have wrong?
If there is any more info that can be of help please let me know.
I am quickly running out of hair.
I have tried setting the general port to tagged, and creating a VLAN on the NIC inside the server. This just made the NIC unable to communicate on VLAN 1 also...
Message Edited by bigboyblue on 01-29-200712:03 PM
Check the PVID ( port VLAN ID ) for port 1 on switch 2, it needs to be set to 244...I suspect its set to 1.
This tells the switch that any untagged packet arriving as ingress to port 1 should be tagged witha VLAN ID of 244 and then forwarded; when it arrives at switch 1, it is carrying a VLAN tag of 244, so will be forwarded accordingly
A port can be in multiple VLANs, but only as a tagged port , this means that packets arriving for ingress to the port carry a VLAN ID; it can only be in 1 VLAN for untagged packets, where it will add the PVID as a VLAN tag for you.
Here's an example....a Voice over ip set up, where the PC is plugged into the back of the phone, and the phone is plugged into a port on the switch...
The PC is in VLAN 100, the VoIP VLAN is VLAN 200.
On the phone set up, you would tell it that the VoIP VLAN is 200.
Any packet originating at the phone would be tagged by the phone with a VLAN ID of 200.
The PC issues untagged packets, which pass through the phone untagged.
So arriving at the switch are VoIP packets tagged for 200 ,and PC packets that are untagged.
The port on the switch is in VLAN 100 as untagged and VLAN 200 as taggged, and the PVID is set to 100.
Any packet arriving at the switch tagged for 200, the switch knows what to do with it - forward it within VLAN 200, as a tagged packet.
Any packet arriving untagged - the switch adds the PVID setting, 100, as the tag, and forwards it within VLAN 100 as a tagged packet.
From this you can see that if you want to use 802.1q VLANs across multiple switches, you must have the PVID setting to add a suitable VLAN ID, but this can only be done on a one VLAN per port basis.
So, I figure what you are saying is that the packets coming from the machine
on Switch2:port 1 need to be marked as the corect VLAN right? I tried this,
but still nothing. I understand that the PVID is a default VLAN to be used
for untagged packets. But since we will have multiple VLANs I don't think this
is the solution.
Let me see if I understand this:
A general mode port can be connected for multiple VLANs, and the
those VLANs must also be created within the machine connected to the
port. The VLANs member ports must also be marked as tagged so the
VLAN tag is not removed when traffic passes through the port.
Is this right? This is what I did but still not traffic going between the
switches.
"A general mode port can be connected for multiple VLANs, and the
those VLANs must also be created within the machine connected to the
port. The VLANs member ports must also be marked as tagged so the
VLAN tag is not removed when traffic passes through the port.
Is this right? This is what I did but still not traffic going between the
switches."
Exactly; a port configured as an access port can belong to just one VLAN, so whatever VLAN you put it in, thats its PVID as well.
A general port can be placed into multiple VLANs, and it will forward packets according to the VLAN tag. In this case, you set the PVID to add a VLAN ID for untagged packets arriving at the ports, so it works for one VLAN only.
A trunk port is for two 802.1q arare devices i.e. two switches to talk to each other, so thats what you use for switch uplinks; here, only VLAN 1 is trreated as untagged, the assumption is that. all other packets are tagged.
So, providing that a) the end device( PC, server etc ) can have a VLAN ID set so that all packets it transmits are tagged, and b) the ports the devices are connected to have the port tagged into the VLAN for that device, and c) that the ports linking the two switches are configured as trunk ports and tagged into all VLANs, then that should work.
bigboyblue
1 Rookie
•
16 Posts
424
0
Posted January 29th, 2007 00:00
Extra info:
I have tried setting the general port to tagged, and creating a VLAN on the NIC inside the server. This just made the NIC unable to communicate on VLAN 1 also...
Message Edited by bigboyblue on 01-29-200712:03 PM