Rawpixel - Fotolia
Hyper-V NIC teaming supports several other advanced technologies that administrators can use to improve network performance and reliability.
One example is network interface card support for a VM queue (VMQ), which provides hardware virtualization to enhance the transfer of network traffic to a virtualized host. Typical traffic types can include TCP/IP, iSCSI and Fibre Channel over Ethernet. The VMQ-compliant NIC is able to use direct-memory access to send incoming traffic directly to receive buffers -- rather than a receive queue -- in a VM's shared memory. VMQ can also scale to use multiple processors to handle different VMs on different processors -- allowing for faster handling of incoming network traffic for NIC team members. In actual practice, VMQ -- if available -- should be enabled whenever Hyper-V is enabled. The NIC team will then present the VMQ features to the Hyper-V switch.
To apply Hyper-V NIC teaming in a VM, the virtual network adapters allocated to the VM must be connected only to external Hyper-V switches, and every team member must be connected to a different external Hyper-V switch. This requires the NIC team to be configured in switch independent mode and to use address hash load balancing. Windows Server 2016 can support VM NIC teams with two members -- more members can be configured but aren't supported.
A second feature is Hyper-V network virtualization (HNV), which effectively creates virtual networks for VMs. HNV basically provides the hypervisor that abstracts the physical network infrastructure, eliminating the limitations of virtual LAN and IP address management in VM provisioning. NIC teaming works well with HNV, allowing the NIC teaming drivers to distribute traffic in a manner that is best suited for the HNV environment. Thus, NIC teaming and HNV can work together to manage complex infrastructures and facilitate integration and workload migrations with outside infrastructure-as-a-service providers.
It's also worth noting that Hyper-V NIC teaming is fully compatible with live migration technologies. NIC teaming provides the same benefits: greater bandwidth for faster migrations -- or more simultaneous migrations -- with network resilience to help prevent disruptions in the server/NIC or greater network. The use of NIC teaming -- or not -- has no impact on the way that live migration is set up or applied to VMs.
Perform a Hyper-V health check
Upgrade Hyper-V VM configuration version
Dig Deeper on Microsoft Hyper-V management
Related Q&A from Stephen J. Bigelow
Application load balancers and API gateways both manage network traffic, but in their own ways. Learn the differences between them and how to use ... Continue Reading
Developers don't have a lot of free time. Code reuse helps dev teams focus on the most value aspects of a project, so ensure everyone knows how to ... Continue Reading
Although there are a handful of tools to help run Firecracker more easily, admins might find issues with the lack of major tool integration for the ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.