Hi all,
I seem to be having an unusual problem getting a switch trunk port to recognize the Hyper-V vlan-id tags.
Here is the problem:
Environment:
- Virtual Machine: Windows Server 2012r2 eval (vhd) configured as a domain controller
- Physical Switch: Cisco Catalyst 3550
- Host/Physical Server: Windows Server 2012 (not R2) Standard
(no big name parts: motherboard and nic's put together from various sources)
I am following the instructions listed in the Hyper-V: Configure VLANs and VLAN Tagging forum article that I see many linking to...BTW, I am not using NIC teaming.
This all seems simple enough--and it seems that many others are getting this to work...but not for me :-(
Here is the problem:
This works:
- Configure the physical switch port as an access port for the specific VLAN (129)
- Configure an 'external' virtual switch (no vlan-id) and attach to the above access port
- Do not configure a vlan-id for the VM
This does not work:
- Configure the physical switch port as a trunk port (with all VLANs allowed)
- Configure an 'external' virtual switch (no vlan-id) and attach to the above trunk port
- Configure vlan-id 129 on the VM
When I do this configuration I am no longer able to access the 129 VLAN. On the physical switch, I can see that the packets are delivered, however they are untagged (they show as belonging to the native vlan-id 1). However, I do see that the physical switch recognizes the virtual switch as a peer and trunking is enabled between them. If I run 'Get-VMNetworkAdapterVlan' in powershell on the host machine, I see that the network adapter for the VM is in Access mode and the Vlanlist (vlan-id?) is 129.
So, it looks like Hyper-V thinks it is tagging the traffic, but the Cisco switch does not see the tags. This would seem to point to the physical NIC I am using on the host server. However, I can find no other example in the forums of a NIC not supporting Trunk mode. Also, the switch recognizes the virtual switch and sets up a trunk session with it.
I feel like I am missing something very obvious here. Can anyone offer any suggestions? My goal is to be able to setup multiple VLANs to isolate/route traffic between VMs and the rest of the external network. This is a test/learning environment so experimentation is welcome ;-)
Thanks,
Alex.