70-414
Microsoft
Implementing an Advanced Server Infrastructure

QUESTION:
137
You have a server named Server1 that runs Windows Server 2012 R2. You plan to
enable Hyper-V Network Virtualization on Server1. You need to install the
Windows Network Virtualization Filter Driver on Server1. Which Windows
PowerShell cmdlet should you run?
A. Set-NetVirtualizationGlobal
B. Enable-NetAdapterBinding
C. Add - WindowsFeature
D. Set-NetAdapterVmq
Answer:
B
Explanation:
Hyper-V Network Virtrtualization runs multiple virtual networks on a physical
network. And each virtual network operates as if it is running as a physical
network.
The The Set-NetAdaptercmdlet sets the basic properties of a network adapter such
as virtual LAN (VLAN) identifier (ID) and MAC address.
Thus if you add the binding parameter to the command then you will be able to
install the Windows Network Virtualization Filter Driver.
Step one:Enable Windows Network Virtualization (WNV). This is a binding that is
applied to the NIC that you External Virtual Switch is bound to.
This can be a physical NIC, it can be an LBFO NIC team. Either way, it is the
network adapter that your External Virtual Switch uses to exit the server.
This also means that if you have multiple virtual networks or multiple interfaces
that you can pick and choose and it is not some global setting.
If you have one External Virtual Switch this is fairly easy:
$vSwitch = Get-VMSwitch -SwitchType External# Check if Network
Virtualization is bound# This could be done by checking for the binding and
seeing if it is enabledForEach-Object - InputObject $vSwitch {if ((Get-
NetAdapterBinding -ComponentID "ms_netwnv" -
InterfaceDescription$_.NetAdapterInterfaceDescription).Enabled -eq $false){ #


You've reached the end of your free preview.
Want to read all 8 pages?
- Fall '20
- virtual machine, virtual network