I'm migrating a Hyper-V R1 Cluster to R2. In this case I'm restructuring the old Network Setup.
the scenario is like this:
- 4 Cluster Nodes
- connected to 2 Switches with an 8 Port LACP-Team
- 1 untagged and 4 additional tagged VLANs
The problem I'm having is, that i can use the tagging of Hyper-V without Teaming, but when i use Teaming and Setup VLANs on the Trunk, i cannot use them in Hyper-V.
I tried the following things:
- using the Hyper-V Tagging feature for the VM directly on the Trunk-NIC
- using the Intel driver to setup NICs for the VLANs and use them directly in Hyper-V
- enabled and disabled the VlanFiltering via Registry on the Intel NICs
The problem is, that the tagging is working on the parent partition. Even the parent partition an the VM can communicate.
The strange thing is, i can not ping both, VM nor parent partition from another host in the tagged vlan. But I sometimes can ping the host from the VM.
I believe it's some strange tagfiltering behaviour of the Intel driver or the Hyper-V switch.
does anyone have an idea how to get this setup working?
Teaming under Hyper-V is a tricky thing :-)
We had several issues with our drivers under a teaming environment. Our latest drivers however fix them :-) If you go to support.intel.com and wade through the menu's, you will be albe to get to our latest drivers and things should magically start working for you.
I would have waded through the menu's for you, howver I don't know which Pro 1000 nor which version of Hyper-V you are running (32/64 bit).
thanks for your help.
I think I've got the problem. I made a fresh install of the System, disabled the Broadcom protocol-bindings for all NICs, created the team with ProSet and disabled VLANFiltering in the registry.
I use the primary, untagged VLAN for the parent and sometimes in the VMs, and make the tagging for the VMs in the Hyper-V config.
Now it seems to be working like a charme.