Hyper-V R2 NIC questions

Question

Hi,
I'm new to hyper-v and I have some questions to ask. My hyper-v is Hyper-V 2008 R2.My current setup is I have 1 physical nic and is both shared by management OS and two VMs. When I unhecked the "Allow management operating system to share this network
adapter" I'm all of a sudden unable to connect to the host machine. How do I turn this back so I can access the management machine again?
Another question is this. I have configured the switch port to where the physical nic of host machine as trunk. Now, my physical servers are all in VLAN 50. Do I have to configure the nics of my VMs to use vlan 50?
If I use two physical nics, 1 for the management os and another for the VMs, do I need to assign an ip to the second physical nic for the VMs? Also, if the nic of the management gets disconnected will the connection of the VMs get disconnected also given
that they are on a separate physical nic?
I want to use two physical nics for the VMS and team the nics together for fault tolerant. What is the powershell command to do this?
Thanks Very much in advance!

Answer 1

Hello dear Janus,
As for the first question:
How do I turn this back so I can access the management machine again?
If you still have local physical access to the server, you can login and enable “Allow management operating
system to share this network adapter”, if not you need to use ILO for HP and IDRAQ for Dell server or a similar remote management baseboard.
Do you have the CodePlex PowerShell tool installed on your Hyper-V 2008 R2 host?
Hyper-V 2008 R2 does not come with PowerShell module like Hyper-V 2012 and 2012 R2.
Here is the PowerShell cmdlet to enable the Management OS again in Hyper-V 2012:
PS C:\
Set-VMSwitch -Name XXXXX -AllowManagementOS $true
For the second question:
Another question is this. I have configured the switch port to where the physical NIC of host machine as trunk.
Now, my physical servers are all in VLAN 50. Do I have to configure the NICs of my VMs to use VLAN 50?
If you have configured the switch port as a trunk, you need to set the VLAN Id 50 for the virtual machine under VM
Settings\Network Adapter in order to communicate with other servers on VLAN 50.
For the third question:
If I use two physical NICs, 1 for the management OS and another for the VMs, do I need to assign an IP to the second physical
NIC for the VMs? Also, if the NIC of the management gets disconnected will the connection of the VMs get disconnected also given that they are on a separate physical NIC?
You don’t need to assign an IP to the second physical NIC for the VMs, as soon as you create the External Virtual
Switch, the settings on the physical NIC will be gone.
No, if the NIC of the management OS gets disconnected, the connection of the VMs won’t get disconnected, because
they are on two separate physical NICs.
I want to use two physical NICs for the VMS and team the NICs together for fault tolerant. What is the Powershell command to
do this?
Since you are using Hyper-V 2008 R2, there is no PowerShell command or NIC teaming built-in in Windows, you need to use the
NIC vendor software.
If you are using Hyper-V 2012 or 2012 R2, here is the PowerShell cmdlet:
Hyper-V 2012:
New-NetLBFOTeam
-Name “Team01”
-TeamMembers “Ethernet 1”,
“Ethernet 2” -TeamingMode
SwitchIndependent
-LoadBalancingAlgorithm HyperVPort
-Confirm:$false
Hyper-V 2012 R2:
New-NetLBFOTeam
-Name “Team01”
-TeamMembers “Ethernet 1”,
“Ethernet 2” -TeamingMode
SwitchIndependent
-LoadBalancingAlgorithm Dynamic
-Confirm:$false
Hope this help.
Charbel Nemnom
MCSA, MCSE, MCS, MCITP
Blog: www.charbelnemnom.com
Please remember to click “Mark as Answer” on the post that helps
you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.