網頁

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?
ScreenHunter_03
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
ScreenHunter_02Shutdown/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.ScreenHunter_04Open Hyper-V Manager and click Virtual Switch Manager…ScreenHunter_05Select the original virtual network switch next to click Remove buttonScreenHunter_06Click Apply buttonScreenHunter_07Click Yes buttonScreenHunter_08Click OK buttonScreenHunter_13In next step, we will change static IP setting to DHCP.ScreenHunter_18In Server Manager/Local Server dashboard, click Disabled link in NIC Teaming fieldScreenHunter_19In NIC Teaming UI, select the multiple network card that want to build a Team next to click Add to New Team in TASK.ScreenHunter_20Write down Team name and select Additional properties next to click OK button.ScreenHunter_21So does that the Hype-v NIC Teaming is created.ScreenHunter_22In Network Connections windows, open Hyper-V NIC Teaming Properties and click Internet Protocol Version 4 (TCP/IPv4) to set the static IP addressScreenHunter_25Now the NIC Teaming will be createdScreenHunter_26Return to Hyper-V Manager and click Hyper-V Settings… link againScreenHunter_27In Virtual Switch Manager page, select New virtual network switch and External next to click Create Virtual Switch buttonScreenHunter_28Write down a Name as “External-01”, select External network option and Microsoft Network Adapter Multiplexor Driver next to click Apply buttonScreenHunter_29Click Yes buttonScreenHunter_30So does that NIC Teaming will integrate with the external network of Hyper-V system nowScreenHunter_32
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 ServerScreenHunter_01Before change anything…ScreenHunter_02After add a new network card when shutdown & power off this Server…ScreenHunter_03In Server Manager/Local Server dashboard, click Enabled link in NIC Teaming fieldScreenHunter_05In NIC Teaming window, select Network Adapters, choose a new network card, click Task next to then click Add to New TeamScreenHunter_06In New team page, assign a Team name next to click OK buttonScreenHunter_07So dose that the second NIC teaming is created nowScreenHunter_08and its IP address will be from DHCP by default.ScreenHunter_09Because 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.ScreenHunter_10Continuously, the IP address of this NIC teaming will set into the the original and static IP value.ScreenHunter_11So do that we finish the IP exchange now.ScreenHunter_12Click Enabled link again in NIC Teaming fieldScreenHunter_13In 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”ScreenHunter_14Finally, this network card has already been this membership of NIC teaming.ScreenHunter_15We also finish adding a NIC Teaming by the second Method.ScreenHunter_16
I believe maybe there is more and more methods about adding the new NIC teaming or someone think the above steps is complex. But I know the Hyper-V function as network access or live migration is normal after follow the above methods to create NIC teaming.

Reference:
(# 1) Windows Server 2012 NIC Teaming (LBFO) Deployment and Management
(# 2) NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

<<<   Live Migration without Shared Storage on Non-Clustered Virtual Machines (part 1)

沒有留言:

張貼留言

Since 2010 Design by Davidwa
©Copyright Davidwa Inc. All rights reserved.