Search This Blog

Tuesday, August 14, 2012

Teaming in A Virtual Machine using Windows Server 2012 Hyper-V

 

Hey! We have heard about new feature called “NIC Teaming in Windows Server 2012”. In my previous post, i have talked about physical NIC Teaming using Windows Server 2012 as well, you can always refer to here.

Now, won’t it be an interesting to have a teaming in a virtual machine as well?. In this article, we will look on how to configure teaming in the guest virtual machine.

image

Configuration:-

1. Shutdown the virtual machine

2. Add 2 Network Adapter or 2 Legacy Network Adapter to the virtual machine. If you select Network Adapter, please remember to install the Integration Service Component.

3. On the network adapter:-

  • Point 1st Network Adapter to Virtual Switch 1
  • Point 2nd Network Adapter to Virtual Switch 2

image

4. On the Advanced features of the network adapter, remember to Tick “Enable this network adapter to be part of a team in the guest operating system”.

5. Connect to Virtual machine and select NIC Teaming using Server Manager snap-in.

6. Then, on the Adapter and Interfaces, select both Ethernet , click Tasks and select Add New Team.

7. For the virtual machine, create a NIC Teaming with only the following configuration

  • Teaming mode: Switch Independent
  • Load Balancing : Address Hashing

image

8. Now you have successful created a NIC teaming in a virtual machine which will provide failover and load balancing features.

Related post:-

9 comments:

  1. At first I wondered what the point to this would be....but I have realised that Windows NLB in VMs doesnt work if the physical NICs are in a team. This would certainly be one way around that issue?

    ReplyDelete
  2. Initially I also think the same. What's the point of having NIC teaming in the vm if physical host has teamed. Then I got a scenario whereby some of my customer prefer to create multiple virtual switch which point to same subnet. Then this will become useful as fault tolerance and load balance the traffic as well.

    ReplyDelete
  3. @Lai: Can you elaborate on the scenario why some customers would create multiple virtual switches? I create virtual switches for DMZ traffic, Private traffic, and then a vitual switch each for iSCSI traffic (proper MPIO). I use VLAN tagging on the vNICs of the VMs to access different subnets.

    ReplyDelete
  4. Hi Richard,
    They would like to separate the traffic and dedicate 1 virtual switch to few VMs. Let say , 3 or 4 VM. Then another 3 or 4 VM on 2nd virtual switch. This will reduce congested and interruption to other VM.
    Previously version, you cannot configure QOS on the VM. But 2012, was able to configure bandwidth management.

    ReplyDelete
  5. Makes sense - thanks for the reply. Looking at it now, it does also allow you segregate your networking hardware. Low-end VMs can run on 100MB switches and high end can run on 1Gb expensive switches, and teaming in the VM can failover over to the other in case of switch failure.

    ReplyDelete
  6. The scenario where two virtual switches are needed might be the use the SR-IOV feature .
    Since the microsoft driver for teaming does not support SR-IOV feature you might need to create two virtual switches with SR-IOV enabled and then team them internally into the VM .
    BUT my question is , is vm teaming supported also on windows 2008 R2 ?

    ReplyDelete
  7. 1. SR-IOV does not support in teaming.
    2. VM Teaming support on Win 2012. You cannot use Win 2008 R2 (3rd party teaming in the vm)

    ReplyDelete