the interface (for example, setting LAA on the interface, changing the primary adapter on a team, etc.), will
cause the VNIC to lose connectivity. In order to prevent this loss of connectivity, Intel® PROSet will not allow
you to change settings that change the MAC address.
NOTES:
l
If Fibre Channel over Ethernet (FCoE)/Data Center Bridging (DCB) is present on the port,
configuring the device in Virtual Machine Queue (VMQ) + DCB mode reduces the number of
VMQ VPorts available for guest OSes. This does not apply to Intel® Ethernet Controller
X710 based devices.
l
When sent from inside a virtual machine, LLDP and LACP packets may be a security risk.
The Intel® Virtual Function driver blocks the transmission of such packets.
l
The Virtualization setting on the Advanced tab of the adapter's Device Manager property
sheet is not available if the Hyper-V role is not installed.
l
While Microsoft supports Hyper-V on the Windows* 8 client OS, Intel® Ethernet adapters do
not support virtualization settings (VMQ, SR-IOV) on Windows 8 client.
l
ANS teaming of VF devices inside a Windows 2008 R2 guest running on an open source
hypervisor is supported.
The Virtual Machine Switch
The virtual machine switch is part of the network I/O data path. It sits between the physical NIC and the
virtual machine NICs and routes packets to the correct MAC address. Enabling Virtual Machine Queue (VMQ)
offloading in Intel® PROSet will automatically enable VMQ in the virtual machine switch. For driver-only
installations, you must manually enable VMQ in the virtual machine switch.
Using ANS VLANs
If you create ANS VLANs in the parent partition, and you then create a Hyper-V Virtual NIC interface on an
ANS VLAN, then the Virtual NIC interface *
must
* have the same VLAN ID as the ANS VLAN. Using a
different VLAN ID or not setting a VLAN ID on the Virtual NIC interface will result in loss of communication on
that interface.
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:
Содержание 10 Gigabit AT Ethernet Server Adapter
Страница 1: ...Intel Ethernet Adapters and Devices User Guide ...
Страница 107: ...FCoE Target Selection Menu ...