Similar to this question:
What happens when a port is configured as ACCESS and is a part of VLAN 'X' and we get a packet of VLAN 'Y' on that port? Will the switch drop it or it will add a VLAN header 'X' and forward to the respective port/ports (Double VLAN tagging).
Suppose I have the a switch stack (HP/3COM A5120) with a port range configured as
- Untagged: 1
- Tagged: None
- PVID: 1
connected to NICs on vSwitch0 has a local network set as VLAN 0. Traffic from that switch ends up on VLAN 1 inside the physical network and is routed correctly.
What will happen if I change the vSwitch VLAN ID to 1? Will the frames be dropped? Will they be double tagged? Will the tagging be stripped and the frames end up on VLAN 1?
I want to add another VM Port Group (VM network) to that vSwitch & a corresponding VLAN on the HP switch ports, but I'm wondering if I should explicitly assign the VLAN on the existing vSwitch port group first and whether doing so will break things.
Best Answer
I found the following from the product manuals:
This doesn't seem to match the behaviour I observed (frames were being dropped), so I've ended up using a trunk port instead and making sure the VLAN I'm using on my vSwitch is permitted on the trunk port.