You have a Hyper-V host named Server1 that runs Windows Server 2012 R2. Server1 has the virtual
switches listed in the following table.
You create a virtual machine named VM1. VM1 has two network adapters. One network adapter
connects to vSwitch1. The other network adapter connects to vSwitch2. You configure NIC teaming
on VM1.
You need to ensure that if a physical NIC fails on Server1, VM1 remains connected to the network.
What should you do on Server1?
A.
Run the Set-VmNetworkAdapter cmdlet.
B.
Create a new virtual switch on Server1.
C.
Modify the properties of vSwitch1 and vSwitch2.
D.
Add a new network adapter to VM1.
no correct answer
New-NetLbfoTeam or New-NetSwitchTeam
0
0
Answer is correct. See info below or link to doc below with pictures for visual rep of info below.
3.5 NIC teaming inside of Virtual Machines (VMs)
NIC Teaming in a VM only applies to vmNICs connected to external switches; vmNICs connected to internal or private switches will show as disconnected when they are in a team.
NIC teaming in Windows Server 2012 R2 may also be deployed in a VM. This allows a VM to have virtual NICs connected to more than one Hyper-V switch and still maintain connectivity even if the physical NIC under one switch gets disconnected. This is particularly important when working with Single Root I/O Virtualization (SR-IOV) because SR-IOV traffic doesn’t go through the Hyper-V switch and thus cannot be protected by a team in or under the Hyper-V host. With the VM-teaming option an administrator can set up two Hyper-V switches, each connected to its own SR-IOV-capable NIC.
• Each VM can have a virtual function (VF) from one or both SR-IOV NICs and, in the event of a NIC disconnect, fail-over from the primary VF to the back-up adapter (VF).
• Alternately, the VM may have a VF from one NIC and a non-VF vmNIC connected to another switch. If the NIC associated with the VF gets disconnected, the traffic can fail-over to the other switch without loss of connectivity.
Note: Because fail-over between NICs in a VM might result in traffic being sent with the MAC address of the other vmNIC, each Hyper-V switch port associated with a VM that is using NIC Teaming must be set to allow teaming There are two ways to enable NIC Teaming in the VM:
1) In the Hyper-V Manager, in the settings for the VM, select the VM’s NIC and the Advanced Settings item, then enable the checkbox for NIC Teaming in the VM. See Figure 4.
2) Run the following Windows PowerShell cmdlet in the host with elevated (Administrator) privileges.
Set-VMNetworkAdapter -VMName -AllowTeaming On
Teams created in a VM can only run in Switch Independent configuration using one of the Address Hash distribution modes. Only teams where each of the team members is connected to a different external Hyper-V switch are supported.
Teaming in the VM does not affect Live Migration. The same rules exist for Live Migration whether or not NIC teaming is present in the VM.
https://gallery.technet.microsoft.com/windows-server-2012-r2-nic-85aa1318
Download and see page 14.
0
0
Or see:
https://technet.microsoft.com/en-us/library/mt179272.aspx
0
0