I'm having trouble getting VLAN tagging to work correctly in Hyper-V. I've set up two 1Gb NICs in a Switch Embedded Team (SET) team, with switch ports configured to only carry tagged VLANs. There's also a spare standalone NIC for iSCSI and management that is functioning normally. The problem arises with my VM's virtual NIC, which has VLAN ID 20 assigned. On the switch side, VLAN 20 is set up as tagged on the uplink, and there is a DHCP server on this VLAN. However, the VM is not receiving an IP address, and no network traffic seems to flow through. My configuration goes like this: Tagged VM → vSwitch → SET team → switch (tagged VLAN 20), but nothing is passing through. Before I dive deep into troubleshooting, I'd appreciate any insights on what misconfiguration I might have or any common pitfalls with Hyper-V and VLAN tagging that I should check.
5 Answers
First, try breaking the team and see if your VM works when only using a standalone NIC configured for VLAN 20. That can help you determine if the issue is with the team configuration or something else.
You might need to verify that the VLAN tag is correctly configured on the VM's NIC settings in Hyper-V. Double-check that part because sometimes it's easy to overlook.
Your setup sounds similar to what I've done in the past. I would recommend first assigning a static IP to see if that works. If it doesn’t, double-check the switch uplink and also try to get two VMs on VLAN 20 with static IPs to see if they can communicate. Additionally, if you have other VLANs set up, test those as well.
I'm not entirely sure that the SET configuration plays well with VLAN tagging, but you might want to consider if it's possible to set the team to use 802.3ad/LACP instead. Just a thought!
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures