Applies To: Windows Server 2016
This topic describes the Hyper-V Network Virtualization (HNV) functionality that is new or changed in Windows Server 2016.
HNV offers enhanced support in the following areas:
|Feature/Functionality||New or improved||Description|
|Programmable Hyper-V switch||New||HNV policy is programmable through the Microsoft Network Controller.|
|VXLAN encapsulation support||New||HNV now supports VXLAN encapsulation.|
|Software Load Balancer (SLB) interoperability||New||HNV is fully integrated with the Microsoft Software Load Balancer.|
|Compliant IEEE Ethernet headers||Improved||Compliant with IEEE Ethernet standards|
HNV is a fundamental building block of Microsoft's updated Software Defined Networking (SDN) solution, and is fully integrated into the SDN stack.
Microsoft's new Network Controller pushes HNV policies down to a Host Agent running on each host using Open vSwitch Database Management Protocol (OVSDB) as the SouthBound Interface (SBI). The Host Agent stores this policy using a customization of the VTEP schema and programs complex flow rules into a performant flow engine in the Hyper-V switch.
The flow engine inside the Hyper-V switch is the same engine used in Microsoft Azure™, which has been proven at hyper-scale in the Microsoft Azure public cloud. Additionally, the entire SDN stack up through the Network Controller, and Network Resource Provider (details coming soon) is consistent with Microsoft Azure, thus bringing the power of the Microsoft Azure public cloud to our enterprise and hosting service provider customers.
For more information about OVSDB, see RFC 7047.
The Hyper-V switch supports both stateless and stateful flow rules based on simple 'match action' within Microsoft's flow engine.
The Virtual eXtensible Local Area Network (VXLAN - RFC 7348) protocol has been widely adopted in the market place, with support from vendors like Cisco, Brocade, Dell, HP and others. HNV also now supports this encapsulation scheme using MAC distribution mode through the Microsoft Network Controller to program mappings for tenant overlay network IP addresses (Customer Address, or CA) to the physical underlay network IP addresses (Provider Address, or PA). Both NVGRE and VXLAN Task Offloads are supported for improved performance through third-party drivers.
Windows Server 2016 includes a software load balancer (SLB) with full support for virtual network traffic and seamless interaction with HNV. The SLB is implemented through the performant flow engine in the data plane v-Switch and controlled by the Network Controller for Virtual IP (VIP) / Dynamic IP (DIP) mappings.
HNV implements correct L2 Ethernet headers to ensure interoperability with third-party virtual and physical appliances that depend on industry-standard protocols. Microsoft ensures that all transmitted packets have compliant values in all fields to ensure this interoperability. In addition, support for Jumbo Frames (MTU > 1780) in the physical L2 network will be required to account for packet overhead introduced by encapsulation protocols (NVGRE, VXLAN) while ensuring guest Virtual Machines attached to an HNV Virtual Network maintain a 1514 MTU.