Configuring Advanced Hyper-V Networking Features
The "Configuring Advanced Hyper-V Networking Features" module provides you with the instruction and server hardware to develop your hands-on skills in the defined topics. This module includes the following exercises: Managing a Hyper-V Virtual Network, Enabling a DHCP Guard, Configuring NIC Teaming, Enabling SR-IOV.
The Configuring Advanced Hyper-V Networking Features module provides you with the instruction and server hardware to develop your hands-on skills in the defined topics. This module includes the following exercises:
- Managing a Hyper-V Virtual Network
- Enabling a DHCP Guard
- Configuring NIC Teaming
- Enabling SR-IOV
Lab time: It will take approximately 1 hour to complete this lab.
The following exam objectives are covered in this lab:
- Configure Hyper-V network switches
- Implement NIC switch teaming
- Enable and configure Single-Root I/O Virtualization (SR-IOV) on a network adapter
Exercise 1 - Managing a Hyper-V Virtual Network
A virtual network works like a physical network switch, except that the switch is software-based and is referred to as a virtual network switch. Ports are added or removed when virtual machines are connected to or disconnected from a virtual network.
Hyper-V’s Virtual Network Manager offers three types of virtual networks that you can use:
External virtual networks. You can use this type when you want to provide virtual machines with access to a physical network and communicate with externally located servers and clients.
Internal virtual networks. You can use this type when you want to allow network communication between virtual machines on the same virtualization server, and between virtual machines and the management operating system.
Private virtual network. You can use this type when you want to allow network communication between virtual machines on the same virtualization server. A private virtual network is not bound to a physical network adapter. This type of network is useful if you want to create an isolated network environment.
Exercise 2 - Enabling a DHCP Guard
Installing and configuring more than one DHCP server will potentially cause connectivity issues among devices in a network. A client computer configured to use a dynamic IP address will detect multiple IP address offers, and will lease an IP address from the first DHCP server it detects on the network segment.
A DHCP guard is a feature that can be enabled on the network interface of a guest virtual machine that is running the DHCP service. This feature prevents the proliferation of DHCP servers that offer IP addresses to computers in the network. When enabled, a guest virtual machine running the DHCP service will not offer an IP address lease to requesting clients in the network, even if an activated IP address pool is available on that virtual machine.
Exercise 3 - Configuring NIC Teaming
Load Balancing/Failover, or NIC Teaming, allows the aggregation of multiple network adapters to be placed into a team. This increases bandwidth throughput, and maintains network connectivity in the event that a network interface card fails on a computer system.
The NIC Teaming feature is supported on Windows Server 2012 R2 and on later Windows Server versions. Windows clients, such as Windows 8.1 and higher, have the NIC Teaming Windows PowerShell commandlets, which allow the remote management of servers that have NIC Teaming enabled.
Exercise 4 - Enabling SR-IOV
When a virtual machine is created in Hyper-V, it will use an emulated device such as vEthernet (Intel Gigabit 825745L), which is considered to be a software-based device, to work with virtualized devices. The physical NIC (a real network adapter) is bound to the emulated device of the Hyper-V host, which then uses the virtual machine bus (VMBus) to connect to the virtual NIC of another virtual machine.
Although software-based devices work efficiently, they still have the inevitable overhead to the I/O path. For instance, there may be times when data buffers need to be copied between the parent partition hosting the Hyper-V service and its guest virtual machines.
Single-Root Input-Output (I/O) Virtualization (SR-IOV), developed by the PCI Special Interest Group, is a standard which explains how a PCI express networking device works with modern virtualization solutions like Hyper-V. When SR-IOV is enabled on a guest virtual machine, it will use the physical NIC of the Hyper-V host as additional network interface, thereby increasing its I/O throughput.
This exercise will demonstrate how to enable SR-IOV on a guest virtual machine on a Hyper-V host.
IT & Cybersecurity certification hands on practice labs and practice exams for certifications and skill development.
See the full benefits of our immersive learning experience with interactive courses and guided career paths.