Hyper-V - NIC Teaming for a VM

We're trying to implement NIC teaming within our environment for virtual servers, I'm working on the following 3 scenarios (Windows Server 2012 R2 on host and VM):

1. NIC Teaming on the host
2. NIC Teaming within the VM: Attaching two external NIC's to the VM and implementing NIC Teaming within the VM itself

3. The following scenario is the one I'm having difficulty with:

I would like to create a NIC team on the host and share that team with the VM, I have done the following:
- Created the NIC Team on the host consisting of only 2 NIC's with equal spec
- Within Hyper-V, created the Virtual switch as 'External' and connected to the 'Microsoft Network Adapter Multiplexor Driver' which represents the NIC Team. (I have tested sharing with the host and sometimes not)
- Within the settings of the VM for the network adapter, selected the Virtual Switch for the Team and under advanced features, selected the option for enabling this network adapter to be part of a team

When I start up the VM I have no connectivity to the network, DHCP does not assign a address and even when statically assigned there is no connectivity.

Is there any specific reason for this that I'm missing?

Thanks
KevinSmrSAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

bas2754Commented:
If I understand what you are trying to accomplish, you are attempting to Team a NIC within a VM that is connected to a Virtual Switch that is using an already physically teamed NIC?  Is that correct?  

I have not personally tried to do that as we team our nics at the host level and then simply put the a single NIC in the VM connected to the Team.  

I may be incorrect, but this seems like a possible scenario that is not supported under Hyper-V, although I cannot speak authoritatively on this as I, again have never tried it....if I have time today I will test it for myself and see what happens.
0
KevinSmrSAuthor Commented:
Thanks for the feedback but not quite, basically what you mentioned:
'I have not personally tried to do that as we team our nics at the host level and then simply put the a single NIC in the VM connected to the Team'...
sounds almost exactly what I'm trying to do, could you provide a brief breakdown as to how you went about this?
0
Abdul Khadja AlaoudineCommented:
Usually NIC Teaming on the VM is used for SR-IOV. If you are not using SR-IOV I would suggest you stick with NIC teaming *only* on the Host.

Anyway, if you still want it then try this:

For the virtual NICs in the VM, on the VM's Settings... --> did you go to Advanced Features of the Network Adapter and enabled NIC Teaming?
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

KevinSmrSAuthor Commented:
Thanks for the info, agreed on the teaming only on the host. We don't require SR-IOV therefore we would like to only configure teaming on the host then make the team available to the VM.

I have previously tried the advanced features within the network adapter and enabled the teaming option without success.
0
KevinSmrSAuthor Commented:
Found another thread covering the same issue as I'm experiencing: Virtual NIC is saying unidentified network

Also, the article mentioned is one I've used before: Configuring Windows Server 2012 NIC Teaming to a Hyper-V Virtual Machine

Unfortunately even though all steps are followed I still end up with a network connectivity issue...
0
Abdul Khadja AlaoudineCommented:
What's the State reported for teamed virtual NICs?

Any error message in System or Application event logs?

Does it work when the virtual NICs are not teamed? both of them?
0
KevinSmrSAuthor Commented:
When the NIC's:
- Are not teamed, individually they work as expected
- Are teamed on the host, the team works as expected
- Have external virtual switches created for each of them within Hyper-V manager, both attached to a VM and teaming then created within the VM itself, they work as expected

When teaming on the host then making the team available to a VM using the procedure shown in the links above, the VM shows the network as public and has an apipa address assigned, even when statically assigning an address there is no connectivity.

I'll run through the event logs for specific errors and see what can be found.
0
KevinSmrSAuthor Commented:
Interesting, the problem has been resolved.

Found the machine being used was built using desktop hardware which seems to have pushed through some limitations to teaming, tried the exact procedure on server hardware and teaming works flawlessly.

Thanks to all for the assistance.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
KevinSmrSAuthor Commented:
Found the issue to be the hardware the NIC teaming had been configured on, the issue was not really software related as what most solutions would believe it to be.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.