Hey everyone! We've been using VMware for years, but due to the recent price hikes, we're making the switch to Hyper-V. Currently, we have around 50 virtual machines across roughly 20 VLANs, utilizing two teamed 10GbE NICs. Setting this up was straightforward in VMware, but we're hitting a wall with Hyper-V.
The catch is that we need the OS to communicate with devices across VLANs, not just with the VMs. We thought we found a solution with Switch Embedded Teaming (SET), but it's not functioning as expected. After a few frustrating days of troubleshooting, I even downgraded one of our hosts from Hyper-V 2025 to 2022, but the issue remains.
We are using two Dell switches configured with a link aggregation group (LAG). On the switch, we have:
- Port Channel 1 set to trunk mode, allowing several VLANs.
- Hosts connected to each switch with trunk mode on their respective ports, and a separate port for a non-VLAN-aware device.
So far, everything seems normal. We can ping an IP from the device that's connected directly to the switch. For the SET team, we set it up with PowerShell commands, added the network adapters, and assigned a VLAN for the management OS, but the vNIC isn't responding when we try to ping the other device across VLAN 225.
I think there might be some routing issues since the traceroute indicates packets are being sent out via the default gateway. This setup feels complex (though it seems like it should be straightforward), and I would appreciate any tips! I've tried various configurations but haven't found a solution. Thanks!
3 Answers
You might want to reconsider using teaming at all. The whole point of SET is to minimize complexity, but if you need reliability, I get why you're trying it. Just ensure your configuration on both the switch and the Hyper-V server is solid. Double-check VLAN tagging and settings to make sure everything is aligned!
Are you using jumbo frames? Sometimes enabling jumbo packets can improve performance and help with connectivity issues like this.
It can be tricky setting up SET properly. The main point of SET is to treat the ports on your switch as dumb ports and manage everything through the hypervisor instead. Make sure all interfaces in the SET switch have the same configuration. Hyper-V should handle everything like load balancing and failover automatically across the interfaces you added. It's all about simplicity on the switch side—keep it basic!
We really need redundancy, so that's why teaming is essential for us. Still trying to get it figured out!