Configuring Windows Server 2012 NIC Teaming to a Hyper-V Virtual Machine
NIC teaming is a new feature of Windows Server 2012, which allows multiple network adapters to be placed into a team for the purpose of providing network fault tolerance and continuous availability. When one of the network adapters fail, the other one takes over without requiring third-party hardware or software. Windows Server 2012 NIC teaming is supported by any vendor’s network card but both are recommended to be identical, in terms of speed and vendor.
Windows Server 2012 supports NIC Teaming up to 32 Network Cards. Hyper-V supports only two.
Image Copy From http://www.aidanfinn.com
Here we will configure NIC teaming for Hyper-V virtual machine. In the following steps, we will create, configure and add NIC teaming to a Hyper-V virtual machine.
1. Open Server Manager, click on All Servers or Hyper-V on the left-hand side pane, then right-click on the server, HOST1 to enable NIC teaming and select Configure NIC Teaming.
2. In the NIC Teaming dialog-box, click on TASKS and click New Team.
3. In the New team dialog-box, In Team name: type Corporate External Team as the Team name and under Member adapters select the network adapter to add to the NIC teaming. Under Additional properties, select the Teaming mode: Switch Independent, Load balancing mode: Hyper-V Port, Standby adapter: None (all adapters Active), Primary team interface: Corporate External Team: Default VLAN and then Click OK.
4. For the few seconds, we get Fault Status in NIC Teaming dialog-box and then get Online Status.
5. Under ADAPTERS AND INTERFACES, Click Team Interfaces Tab, Right-Click on Team Interface name, Corporate External Team and Click Properties.
6. In the Network Adapter Properties dialog box, under General information, noted Description: Microsoft Network Adapter Multiplexor Driver. Verify Default VLAN membership and Click OK.
7. In the Network Control Panel, verify Microsoft Network Adapter Multiplexor Protocol under Team Network Properties.
8. In Hyper-V Manager, on the Action pane, click Virtual Switch Manager. In the Virtual Switch Manager dialog box, select New virtual network switch, Ensure that External is selected and Click on Create Virtual Switch. Under External network select Microsoft Network Adapter Multiplexor Driver then Click Apply, review the warning, and then click Yes.
9. Open the Settings of Hyper-V virtual machine, click Network Adapter on the left pane, and select Corporate Network under Virtual switch. Then Click Advanced Features on left pane, then Click on Enable this network adapter to be part of a team in the guest operating system under NIC Teaming, Click Apply and Click OK.
10.To verify NIC Teaming, Unplug Network Cable one of the NIC and PING the Destination Server. We will get Reply from the Destination Server.
Network Fault tolerance is often overlooked. In High Availability Systems, this feature can be of great utility as the downtime is zero in terms of Network connectivity due to NIC failure.
- My Precious IT Books Collections - March 1, 2018
- Configuring Azure Traffic Manager using Performance Based Routing Method - January 20, 2018
- Configuring a Point-to-Site Connection to a VNet using Azure Portal - November 28, 2017
- Configuring a VNet-to-VNet VPN Gateway Connection Using the Azure Portal - October 27, 2017
- Configuring Azure VNet Peering by using the Azure Portal - October 19, 2017
- Using the Azure Portal to Create Virtual Networks, Add Subnets and Setting up a DNS Server Address - October 17, 2017
- Extend Azure Virtual Machine OS drive using Azure Portal - June 30, 2017
- Creating a Windows Virtual Machine and Availability Set at the same time using the Azure Portal - June 11, 2017
- Remove a Node from a Windows Server 2016 Hyper-V Cluster and Destroy a Cluster Procedure - May 14, 2017
- Best Practices on Setting up Hyper-V Cluster Networks in Windows Server 2016 - May 10, 2017