Chapter 3: Virtual Networking
Architect the right network design for your Hyper-V hosts and virtual
machines by using the options available. There are many different networking
traffic types related to a Hyper-V host, including management, virtual machine,
cluster, Live Migration, and storage. While traditionally separate, network adapters
were used with each type of traffic; a preferred approach is to create multiple vNICs in
the management partition that connect to a shared virtual switch. This minimizes the
number of physical NICs required while providing resiliency from a NIC failure for all
workloads connected to the switch.
Master It Why are separate network adapters no longer required if SMB is
leveraged and the network adapters support RDMA?
Solution RDMA is not compatible with NIC Teaming, which would have been
used as the foundation for the connectivity of the virtual switch prior to Windows
Server 2016. However, in Windows Server 2016, a new teaming technology called
Switch Embedded Teaming (SET), which is implemented within the VMSwitch, is
utilized. This means that, unlike Windows Server 2012 R2, which required separate
adapters for RDMA traffic and those used with the VMSwitch, converged NICs can
now be used with the VMSwitch, avoiding the need for extra NICs dedicated to
RDMA traffic.Identify when to use the types of gateways. There are three types of gateways
supported by the SDNv2 multitenant gateway: basic layer 3 forwarding to connect
virtual networks to other networks, GRE tunneling to other GRE endpoints or MPLS,
and site-to-site VPN to connect different locations. The SDNv2 multitenant gateway
supports multiple active and multiple passive instances, and it is designed to support
multiple tenants using shared physical infrastructure.
Leverage SCVMM for many networking tasks. While Hyper-V Manager enables
many networking functions to be performed, each configuration is limited to a single
host and is hard to manage at scale. SCVMM is focused on enabling the network to be
modeled at a physical level, and then the types of network required by virtual
environments can be separately modeled with different classifications of connectivity
defined. While the initial work may seem daunting, the long-term management and
flexibility of a centralized networking environment is a huge benefit.
Master It Is SCVMM required for network virtualization?
Solution SCVMM is required for SDNv1, which was the only SDN solution in
Windows Server 2012 and Windows Server 2012 R2. It is still part of Windows
Server 2016 for backward-compatibility reasons. SDNv2 has a new controller plane,
the Network Controller, which is part of Windows Server 2016. Through the
Network Controller, different management solutions can interact and manage.
SCVMM is one possible management solution for SDNv2, but not the only solution.