Your network contains five servers that run Windows Server 2012 R2.
You install the Hyper-V server role on the servers. You create an external virtual network
switch on each server.
You plan to deploy five virtual machines to each Hyper-V server. Each virtual machine will
have a virtual network adapter that is connected to the external virtual network switch and
that has a VLAN identifier of 1.
Each virtual machine will run Windows Server 2012 R2. All of the virtual machines will run
the identical web application.
You plan to install the Network Load Balancing (NLB) feature on each virtual machine and
join each virtual machine to an NLB cluster. The cluster will be configured to use unicast
only.
You need to ensure that the NLB feature can distribute connections across all of the virtual machines.
Solution: From the properties of each virtual machine, you add a second virtual network
adapter. You connect the new virtual network adapters to the external virtual network switch
and configure the new virtual network adapters to use a VLAN identifier of 2.
Does this meet the goal?
A.
Yes
B.
No
Wy is the answer “No”? Because you would need an second external virtual switch on a second NIC on the Hyper-V host to run this configuration?
given answer is right.. A
https://technet.microsoft.com/en-us/library/cc782694%28v=ws.10%29.aspx
sorry wrongly comment here… its B
NLB Hijacks the MAC address of all the Hyper-V Hosts’ Network adapter. NLB then creates one shared MAC address which is assigned to the physical Network Adapter of all the hosts. NLB uses this Shared MAC address (essentially the MAC of the Cluster, if the cluster where a physical “machine” too) to send NLB traffic.
This NLB traffic is distributed to ALL the Hosts (because all the hosts have the same MAC address, they will obviously receive this traffic too). The traffic is then distributed on ALL ports in the Clusters common Network Adapter.
To enable the Virtual Machine Guests to be distinguished, we enable MAC Address Spoofing which grants each VM its own spoofed MAC address.
This will allow all the VIRTUAL MACHINES to talk amongst each other, and for NLB to manage them as they are all talking across the Common/Combined Host Adapter.
This will NOT allow the actually HOST machines to talk amongst each other, or to talk to the corporate network anymore because their physical network adapters have been hijacked by NLB.
To enable the physical Host machines to talk to the corporate network/external network again we need to add a second network adapter.
https://technet.microsoft.com/en-us/library/cc757150%28v=ws.10%29.aspx
SO B… we have not enabled MAC Address Spoofing, so communication cannot be distributed to virtual machines.
Once MAC Address Spoofing is enabled, communication on the NLB network adapter can be directed towards the virtual machines, but the HOST machines will have no connection to the corporate network unless we add a second network adapter that is connected to the corpnet to them.
2 Network Adapters are NOT required for NLB, they are recommended though.
To meet the requirement “You need to ensure that the NLB feature can distribute connections across all of the virtual machines.” We do not need to have communication to the corpnet, we only need the NLB network adapter to be able to speak to the VMs – enable MAC Spoofing.