How to manage Hyper-V 2016 configuration

In this issue, Xiaobian will bring you about how to carry out Hyper-V 2016 configuration management. The article is rich in content and analyzed and described from a professional perspective. After reading this article, I hope you can gain something.

1 Recommended hardware and software configuration

2 Hyper Host Prerequisites

Prerequisites:

64-bit processor with secondary address translation (SLAT). To install Hyper-V virtualization components, such as Windows Hypervisors, the processor must have SLAT

Enough memory-Plan for at least 4 GB of RAM. More memories are better. You need enough memory for the host and all the virtual machines you want to run simultaneously.

Virtualization support turned on in BIOS or UEFI

Network settings:

In a production environment, you need to combine adapters so that there is no single point of failure in any one network. A typical network configured in a Hyper-V cluster environment might include the following:

Management and VM traffic

Storage (iSCSI, NFS)

Private Cluster Traffic

Live Migration

Considering the network above, we want to assign IP addresses to each server within the subnet range we need. VLANs, so make sure you configure them correctly before installing.

Example reference:

1) Modify the network card name

netsh interface set interface name="NIC1" newname="PNIC1"netsh interface set interface name="SLOT 1 Port 1" newname="PNIC2"netsh interface set interface name="SLOT 1 Port 2" newname="PNIC3"netsh interface set interface name="SLOT 2 Port 1" newname="PNIC4"netsh interface set interface name="SLOT 2 Port 2" newname="PNIC5"

2) Creating NIC Teaming

New-NetLbfoTeam "PhysicalTeamMgMt" -TeamMembers "PNIC2","PNIC4" -TeamNicName "PhysicalTeamMgMt" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm DynamicNew-NetLbfoTeam "PhysicalTeamApp" -TeamMembers "PNIC3","PNIC5" -TeamNicName "PhysicalteamApp" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic

3) Configure virtual machine switches

Set-VMSwitch -Name "TeamSwitchMgMt" -DefaultFlowMinimumBandwidthWeight 0New-VMSwitch "TeamSwitchApp" -NetAdapterName "PhysicalTeamApp" -AllowManagementOS $false Set-VMSwitch -Name "TeamSwitchApp" -DefaultFlowMinimumBandwidthWeight 0

BIOS configuration:

BIOS is subject to change regarding manufacturer and motherboard. Perform the same operation on each server to make it the same configuration

Check if the server boots in UEFI

Enable virtualization technology support such as VT-d, VT-x, SLAT, etc.

Server high performance configuration (so CPU has maximum frequency available)

enable Hyper-Threading

Disable all unwanted hardware (audio cards, serial/ COM ports, etc.)

Disable PXE boot to accelerate booting of servers (optional)

set date/time

Functional component configuration:

Once configured, install the required roles and features. You can run the following cmdlets on two nodes:

Install-WindowsFeature Hyper-V, Data-Center-Bridging, Failover-Clustering, RSAT-Clustering-Powershell, Hyper-V-PowerShell, Storage-Replication Install Multipath-IO Components Install-WindowsFeature Multipath-IO The above is how to carry out Hyper-V 2016 configuration management shared by everyone. If you happen to have similar doubts, please refer to the above analysis for understanding. If you want to know more about it, please pay attention to the industry information channel.