Improve company productivity with a Business Account.Sign Up


Windows Server 2012 NIC Team & Hyper-V

Posted on 2014-02-21
Medium Priority
Last Modified: 2016-11-23
I have a Dell PowerEdge R720 server of which I setup a NIC Teaming.  This server has a total of four NICs, and I wanted to ensure the connection to the Hyper-V host stays connected at all time, so my thinking was to enable a NIC Team.  The other remaining NICs would be dedicated to two VMs.

First, I guess I need to know if configuring a NIC team on the host is recommended?

I am now installing Hyper-V Role, and during the process I selected the NIC Team adapter to Create Virtual Switches.  However, after installing Hype-V role I noticed it created an extra vitual adapter (vEthernet (Microsoft Network Adapter Multiplexor Driver - Virtual Switch).  I do not think we need virtual adapter since I have plenty of physical NICs, so unchecked the Virtual Switch Manager - Virtual Switch Properties - "Allow management operating system to share this network adapter".  After doing so, the server cannot access the network.  Now I cannot access the server via RDP, the server itself cannot access the network.  

If NIC Teams for the host is recommended, and works then how is Hyper-V installed and configured without the need of using a virtual adapter?
Question by:cmp119
LVL 14

Expert Comment

by:Justin Yeung
ID: 39877633
LVL 20

Expert Comment

by:Svet Paperov
ID: 39877961
Yes, the NIC teaming has to be done on the host level. Now, with Windows Server 2012 we have a choice of creating a team by using the manufacture driver or by using Windows Server 2012 teaming. I don’t have Windows Server 2012 teaming in production environment, so I cannot say which one is better.

Then, after the team is created, you create a virtual adapter (virtual switch) from the teamed adapter.

However, I would do the NIC setup a little bit differently:
- I will keep one NIC for host management, without creating a virtual switch from it
- I will team the 3 remaining NICs in Link Aggregation mode
- Create the virtual switch from the teamed adapter (3x 1Gbps)
- Disable the Management traffic on the virtual adapter

In that way you will have Hyper-V management traffic completely separated from the data from the virtual machines. And, the connection between virtual machines connected to the same virtual switch is theoretically 10Gbps.

Author Comment

ID: 39913108
I am sorry for the severe delay getting back with you on this.  

I have abandoned nic teaming altogether and deciding going with one nic for the hypervisor.  There is something I am not understanding that I need clarification:

The server has a total of 4 physical NICs.

I want to use a NIC for the Hypervisor (VMHost).

One NIC for a Exchange 2010 VM (Exchange2010).  Will be conducting an Exchange 2003 to 2010 migration soon.

One NIC for an Exchange 2013 VM (Exchange2013) that will be created sometime in the future for Exchange 2010 to 2013 migration.

The last NIC (NIC1) was disabled since I do not need it for now.  

My first question is with Windows Server 2012, when installing the Hyper-V role it automatically created a virtual switch adapter.  I had all adapters disabled with the exception of (VMHost adapter).

I simply want to use the actual adapter for Hypervisor (Host).  

My question is the virtual switch adapter necessary for the hypervisror and each VM when I have physical adapter for all?  I spoke with a Dell rep and he stated it was needed and that's the only way it will work.  

I basically need a step-by-step instruction on how to setup the hypervisor nic properly, and then defining the nics for each installed vm.  I tried installing my first vm, and it would not display any physical nic that was enabled, and simply displayed Not connected and the virtual switch.

So, what I want to know exactly how to setup the adapters in a correct manner for the hypervisor host and then each vm.
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

LVL 20

Expert Comment

by:Svet Paperov
ID: 39913376
Yes, it is required.

Why did you abandon the teaming? As I said in my previous post, the best approach is to use one NIC for the Hyper-V host management traffic only and the other 3 in a team for traffic from all virtual machines.

Optionally, one physical NIC could be kept off for future expansion with iSCSI attached devices or for live migration between two Hyper-V hosts in a cluster, if ever used.

I will recommend against the approach of reserving a physical NIC per virtual machine, especially if there is communication going on between VMs on the same host.

Here is link to Windows Server 2012 Hyper-V Best Practices and a video about configuring Hyper-V virtual switches in 2012

Author Comment

ID: 39920613
I modified the configuration again as you suggested in that the Hypervisor NIC without creating a virtual switch for it.  

However, if I were to create a two NIC team via Windows Server 2012 teaming, how would would I be able to assign static IPs for each VM of which will use the same virtual switch.  

I presume we'll have one virtual switch for the team, and then I will be able to assign this same virtual switch to both VMs, but how will I be able to assign static IPs for each?
LVL 20

Accepted Solution

Svet Paperov earned 2000 total points
ID: 39920680
There is no IP address to configure on the virtual switch.

On the configuration panel of each virtual machine, you create a virtual adapter and connect it to the switch. After powering up the virtual machine, you can set up its IP address within the VM as you do it on a regular computer.

You may want to take a look at the following TechNet pages: and

Author Closing Comment

ID: 39921202
Svet - I followed your advice.  All looks good!!!  Thank you.
LVL 41

Expert Comment

by:Philip Elder
ID: 40469101
My E-E Article: Some Hyper-V Software and Hardware Best Practices.

Please check out the article as it is based on building out Hyper-V standalone and cluster solutions since 2008 RTM.

We _always_ team unless the backend is a Scale-Out File Server cluster and we are using SMB Multi-Channel via 10GbE or higher with multiple NIC ports.

Why have a single point of failure, the physical NIC, when the goal is to create as much resilience to failure as possible?

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

I’m willing to make a bet that your organization stores sensitive data in your Windows File Servers; files and folders that you really don’t want making it into the wrong hands.
The article describes step by step how to validate the SRA software certificate once installed on the Site Recovery Manager server. I hope it will be very useful for all administrators of virtualized environments.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
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…

595 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