茶米王(DAVIDWA): 2013/1/13

2013年1月13日星期日

Hyper-V 3.0 --- Create NIC Teaming after Hyper-V online (part 2)

Although Linux NIC Teaming has already been built-in for a long time,Microsoft never exist this function until Windows Server 2012 is released. We can directly use this new function in Windows Server 2012 so that it doesn’t depend on Vendor’s NIC driver or management software and choose the same network card for building NIC teaming. Due to Microsoft did not support NIC teaming for Hyper-V 2.0 network in the pass, sometime there is problem happened by NIC driver or teaming issue if we use it in Hyper-V environment. For stability, we need to give up availability usage in Hyper-V. Now it will be good news that NIC teaming has already been part of the Microsoft Operating System.

How to do NIC Teaming? It is very simple that can study the related knowledge from Microsoft or friendly web site.
If Hyper-V system has already been in production, how to set it but never influence online service?

To create the first NIC team for Hyper-V External networkMethod I : Combine with multiple network cards to form a NIC TeamAt first, confirm Hyper-V Server never exist any VM object

Shutdown/Power Off the standby server as “VW-HYPERV-02” for adding a new network card. When power on it again, we will see a new network card in Server Manager/Local Server dashboard.

Open Hyper-V Manager and click Virtual Switch Manager…Select the original virtual network switch next to click Remove button

Click Apply button

Click Yes button

Click OK button

In next step, we will change static IP setting to DHCP.

In Server Manager/Local Server dashboard, click Disabled link in NIC Teaming field

In NIC Teaming UI, select the multiple network card that want to build a Team next to click Add to New Team in TASK.

Write down Team name and select Additional properties next to click OK button.

So does that the Hype-v NIC Teaming is created.

In Network Connections windows, open Hyper-V NIC Teaming Properties and click Internet Protocol Version 4 (TCP/IPv4) to set the static IP address

Now the NIC Teaming will be created

Return to Hyper-V Manager and click Hyper-V Settings… link again

In Virtual Switch Manager page, select New virtual network switch and External next to click Create Virtual Switch button

Write down a Name as “External-01”, select External network option and Microsoft Network Adapter Multiplexor Driver next to click Apply button

Click Yes button

So does that NIC Teaming will integrate with the external network of Hyper-V system now

To add another NIC Team for Hyper-V Live migration networkMethod II: Add a new network Interface to an existing team
To do the same prerequisite, confirm never exist any VM in this Hyper-V Server

Before change anything…

After add a new network card when shutdown & power off this Server…

In Server Manager/Local Server dashboard, click Enabled link in NIC Teaming field

In NIC Teaming window, select Network Adapters, choose a new network card, click Task next to then click Add to New Team

In New team page, assign a Team name next to click OK button

So dose that the second NIC teaming is created now

and its IP address will be from DHCP by default.

Because our target will be replace this dynamic IP with the original and static IP of Live Migration, we first need to change the Live Migration IP Address from static to dynamic setting.

Continuously, the IP address of this NIC teaming will set into the the original and static IP value.

So do that we finish the IP exchange now.

Click Enabled link again in NIC Teaming field

In NIC Teaming windows, select a team as “Live Migration NIC teaming” in TEAMS, right-click a network card that want to join the selected team next to click Add to Team “Live Migration NIC teaming”