jacksch4820
asked on
Vlan tagging / trunk port question
Hi
Please see my network diagram attached.
My question is must I create vlan 10 20 and 30 on all 3 switches so my virtual machines in vlan 10 20 and 30 can communicate across the switches/trunk witch each other.
Please advice
Network-Diagram.jpg
Please see my network diagram attached.
My question is must I create vlan 10 20 and 30 on all 3 switches so my virtual machines in vlan 10 20 and 30 can communicate across the switches/trunk witch each other.
Please advice
Network-Diagram.jpg
ASKER
Hi Helge000
i dont have GVRP running on my switches.
i just want to pipe the vlans through how can i tag the trunks
i dont have GVRP running on my switches.
i just want to pipe the vlans through how can i tag the trunks
This depends on your switches of course - but generally you have a management vlan, and your vlan's 10,20,30 (I just assume that). Also, I will call your mgmt vlan '1'.
In vlan config of your switch should see the trunks as 'one' virtual interface, even if you did bond a few physical ports together.
On switch 1, look for your trunk.
Tagglist:
- vlan 1 untagged
- vlan 10,20,30 tagged
Based on your switches untagged vlan's might be called something like 'PVID' (primary vlan identification, esp. Netgear)
Do the same on all the interswitch trunks of the other switches and you should be good.
In vlan config of your switch should see the trunks as 'one' virtual interface, even if you did bond a few physical ports together.
On switch 1, look for your trunk.
Tagglist:
- vlan 1 untagged
- vlan 10,20,30 tagged
Based on your switches untagged vlan's might be called something like 'PVID' (primary vlan identification, esp. Netgear)
Do the same on all the interswitch trunks of the other switches and you should be good.
My question is must I create vlan 10 20 and 30 on all 3 switches so my virtual machines in vlan 10 20 and 30 can communicate across the switches/trunk witch each other.The VLANs must exist on all switches that traffic from those VLANs transits. How those VLANs come to exist is a variable. But whether you manually create them, use VTP or GVRP, the VLANs must exist on all three of those switches.
True! You still need to create the vlan on the switch with GVRP, but you do not need to tag the ports. Sorry, this was unclear. Thanks donjonston!
ASKER
Ok they all are Cisco switches.
So basically I got three options to that.
1. Using GVRP
2. Tagging needed vlans on all trunk ports.
3. Create vlans on all switches.
Please advice if I’m correct
So basically I got three options to that.
1. Using GVRP
2. Tagging needed vlans on all trunk ports.
3. Create vlans on all switches.
Please advice if I’m correct
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
depending if you have something like GVRP running witch basically doeus the job for you - you will have to create each and every vlan on the switches which need need to 'see' the vlan.
If you just want to 'pipe' the vlan's through the middle switch it will do if you just tag the trunks (on every switch).
HTH!