This begins to look like a serial story. Hyper-V and NIC Teaming. Ever since I wrote a blog on using native VLANs with HP NIC Teaming and Hyper-V, I have been reluctant to try new versions. Now that Windows Server 2008 R2 SP1 was published almost a month ago, I have attempted to evaluate the consequences for this lovely combination.
Let me begin with referring to my blogs on NIC Teaming:
As from HP Network Configuration Utility (NCU) 10.10.0.x it is possible to use native VLANs in combination with Hyper-V without going through the hassle of manually adding multiple VLANs on the team and creating Hyper-V virtual networks and string those two together. By using a team setting called Promiscuous Mode we only had to make sure VLANs were known on the trunk and we were able to apply a VLAN ID to the virtual network adapter in the Hyper-V guest.
I have tested a couple of combinations:
TESTED CONFIGURATION 1
Config: Windows Server 2008 R2 SP1 with NCU 10.10.0.0 and Broadcom 5.2.22.x drivers from HP PSP 8.60 but without teaming configured. VLAN configured on adapter itself.
Result: Guest can communicate with network. VLANs are passed through correctly.
Conclusion: Although you have no network redundancy in this configuration, it is easy to add a VLAN id to the vNIC in the guest. Promiscuous mode is not applicable here.
TESTED CONFIGURATION 2