Answered by:

Hyper-V 2012 and NIC Teaming, causes Hyper-V service to fail

Question

I was just curious if the configuration I'm attempting is supported or not. I know that with the release of Server 2012, NIC teaming is now supported, but I’m unsure to what level once you add
Hyper-V to the mix.

Basically this is what I'm attempting, i have a 1GB NIC, and 10GB NIC in my server. I then created two teams, based on the following:

All replies

It appears that you are attempting to team NICs that are on different physical VLANs.

Is this accurate? What are you attempting to accomplish?

Teaming is not designed to sort out the proper VLAN for the traffic, the assumption is that all NICs in a Team are on the same physical segemnet. And having individual team members on different VLANs also does not give any type of failover, link aggregation,
or any other benefits of teaming.

No, not quite. I'm teaming two 1GB NIC's that have multiple VLANs trunked to them, and then I'm creating a virtual NIC for each of the VLANs. Then on the 10GB NIC's, i'm once again teaming two 10GB physical NIC's together that have approximately
25 VLAN's trunked. I am then creating a virtual NIC specifically for Live Migration traffic, and then a 2nd virtual NIC for VM use.

So do you mean you have a two node Hyper-V cluster, each node have 4 physical NIC, two 1GB NIC, two 10GB NIC.

> I am then creating a virtual NIC specifically for Live Migration traffic, and then a 2nd virtual NIC for VM use.

We do live migration on physical hyper-V Host, so live migration use the 10 GB teaming network, what do you mean create virtual NIC for Live migration traffic?

If your 2nd virtual NIC is Internal network, it not change teaming NIC settings. If the 2nd virtual NIC is external network, it replace the position of the Physical teaming NIC, then you can use the virtual NIC for live migration traffic.

At this point via Hyper-V Manager, i created a external vswitch, utilizing the Shared NIC which shows up in the drop down as "Microsoft Network Adapter Multiplexor Driver #7"

Ultimately the vswitch on one server works, and the vswitch on the other server does not. Also, the LiveMigration lbfo team nic's work fine on both servers, and they can communicate with each other just fine, the same is true for all other lbfo team
nic's configured via Team1.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Unfortunately the results are too big for a post. needless to say, there was only one potential problem, which I have provided below. Keep in mind, we are not running Hyper-V Replica, so I'm pretty sure this can be ignored.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.