Virtual Switches bound to an ANS VLAN will have the same MAC address as the VLAN, which will have the same
address as the underlying NIC or team. If you have several VLANs bound to a team and bind a virtual switch to each
VLAN, all of the virtual switches will have the same MAC address. Clustering the virtual switches together will cause a
network error in Microsoft’s cluster validation tool. In some cases, ignoring this error will not impact the performance of
the cluster. However, such a cluster is not supported by Microsoft. Using Device Manager to give each of the virtual
switches a unique address will resolve the issue. See the Microsoft Technet article
Configure MAC Address Spoofing
for Virtual Network Adapters
for more information.
Virtual Machine Queues (VMQ) and SR-IOV cannot be enabled on a Hyper-V Virtual NIC interface bound to a VLAN
configured using the VLANs tab in Windows Device Manager.
Using an ANS Team or VLAN as a Virtual NIC
If you want to use a team or VLAN as a virtual NIC you must follow these steps:
NOTE:
This applies only to virtual NICs created on a team or VLAN. Virtual NICs created on a physical
adapter do not require these steps.
1. Use Intel® PROSet to create the team or VLAN.
2. Open the Network Control Panel.
3. Open the team or VLAN.
4. On the General Tab, uncheck all of the protocol bindings and click OK.
5. Create the virtual NIC. (If you check the "Allow management operating system to share the network adapter."
box you can do the following step in the parent partition.)
6. Open the Network Control Panel for the Virtual NIC.
7. On the General Tab, check the protocol bindings that you desire.
NOTE:
This step is not required for the team. When the Virtual NIC is created, its protocols are correctly
bound.
Command Line for Microsoft Windows Server* Core
Microsoft Windows Server* Core does not have a GUI interface. If you want to use an ANS Team or VLAN as a Virtual
NIC, you must use the prosetcl.exe utility, and may need the nvspbind.exe utility, to set up the configuration. Use the
prosetcl.exe utility to create the team or VLAN. See the prosetcl.txt file for installation and usage details. Use the nvsp-
bind.exe utility to unbind the protocols on the team or VLAN. The following is an example of the steps necessary to set
up the configuration.
NOTE:
The nvspbind.exe utility is not needed in Windows Server 2008 R2 or later.
1. Use prosetcl.exe to create a team.
prosetcl.exe Team_Create 1,2,3 TeamNew VMLB
(VMLB is a dedicated teaming mode for load balancing under Hyper-V.)
2. Use nvspbind to get the team’s GUID
nvspbind.exe -n
3. Use nvspbind to disable the team’s bindings
nvspbind.exe -d aaaaaaaa-bbbb-cccc-dddddddddddddddd *
4. Create the virtual NIC by running a remote Hyper-V manager on a different machine. Please see Microsoft's doc-
umentation for instructions on how to do this.
5. Use nvspbind to get the Virtual NIC’s GUID.
6. Use nvspbind to enable protocol bindings on the Virtual NIC.
nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_netbios
nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_tcpip
nvspbind.exe -e tttttttt-uuuu-wwww-xxxxxxxxxxxxxxxx ms_server
