Solved

Hyper-V - NIC Teaming for a VM

Posted on 2014-10-09
9
228 Views
Last Modified: 2014-11-12
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
0
Comment
Question by:KevinSmrS
  • 6
  • 2
9 Comments
 
LVL 9

Expert Comment

by:bas2754
ID: 40370754
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
 

Author Comment

by:KevinSmrS
ID: 40370813
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
 
LVL 5

Expert Comment

by:Abdul Khadja Alaoudine
ID: 40371049
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
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:KevinSmrS
ID: 40371199
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
 

Author Comment

by:KevinSmrS
ID: 40372447
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
 
LVL 5

Expert Comment

by:Abdul Khadja Alaoudine
ID: 40372474
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
 

Author Comment

by:KevinSmrS
ID: 40374085
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
 

Accepted Solution

by:
KevinSmrS earned 0 total points
ID: 40376561
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
 

Author Closing Comment

by:KevinSmrS
ID: 40388194
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

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will review the basic installation and configuration for Windows Software Update Services (WSUS) in a Windows 2012 R2 environment.  WSUS is a Microsoft tool that allows administrators to manage and control updates to be approved and ins…
OfficeMate Freezes on login or does not load after login credentials are input.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question