Windows 2012 & Hyper-V: Converged Network and QoS
With Windows 2012, we are now able to create vNICs in the parent partition. This plays major role in building fabrics by providing us with bandwidth management, classifications, flow control based on priority with the help of new QoS settings and functionality.
TechNet has a a common configuration guide published. I will go over the basics of one of the scenarios presented which I think will be common configuration among all implementations, 2-NIC Configuration with Teaming.
If you are planning to create Hyper-V cluster with 2 NICs, you can team both physical NICs, create a Virtual Switch and then create vNICs for Management, Live Migration, Storage and Clustering and apply QoS.
NICs:
Get-NetAdapter Name InterfaceDescription ifIndex Status MacAddress LinkSpeed ---- -------------------- ------- ------ ---------- --------- NIC2 Intel(R) 82574L Gigabit Network Co...#2 16 Up 00-0C-29-45-06-6E 1 GbpsNIC1 Intel(R) 82574L Gigabit Network Conn... 13 Up 00-0C-29-45-06-641 Gbps
To Create Team:
New-NetLbfoTeam“Team2Gb“ -TeamMembers nic1,nic2 -TeamingMode SwitchIndependent -LoadBalancingAlgorithm TransportPorts -TeamNicName “TeamNic2Gb“
Name : Team2Gb
Members : {NIC1, NIC2}
TeamNics : TeamNic2Gb
TeamingMode : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status : Down
Virtual Switch and Virtual NICs:
New-VMSwitch-Name“2GbSwitch“ -NetAdapterName TeamNic2Gb -MinimumBandwidthMode Weight -AllowManagementOS $false
Add-VMNetworkAdapter -ManagementOS -NameManagementOS –SwitchName 2GbSw.
Add-VMNetworkAdapter -ManagementOS -NameSMB -SwitchName 2GbSwitch
Add-VMNetworkAdapter -ManagementOS -NameLM -SwitchName 2GbSwitch
Add-VMNetworkAdapter -ManagementOS -NameCluster -SwitchName 2GbSwitch
Set-VMNetworkAdapter -ManagementOS -NameSMB -MinimumBandwidthWeight 40
Set-VMNetworkAdapter -ManagementOS -NameLM -MinimumBandwidthWeight 20
Set-VMNetworkAdapter -ManagementOS -NameCluster -MinimumBandwidthWeight 5
Now you can set IP though GUI or Powershell:
New-NetIPAddress -InterfaceAlias “vEthernet (ManagementOS)“ -IPAddress 192.168.1.180 -PrefixLength 24 -DefaultGateway 192.168.1.1
Set-DnsClientServerAddress -InterfaceAlias “vEthernet (ManagementOS)“ -ServerAddresses 192.168.1.100,192.168.1.1
Once the Virtual Switch is setup, you will see that some of the settings are no longer manageable by the GUI:
And the Network panel shows the new vNICs:
Note: When there is a problem with storage connection and access to the CSV is lost by a host, all traffic is routed via CSV network to another Hyper-V cluster node. So, keep its weight relatively higher than the others.
If you have VLANs:
Set-VMNetworkAdapterVlan –ManagementOS –VMNetworkAdapterName SMB –Access –VlanId 100
Also, classification and traffic tagging can be used to prioritize the traffic based on type, subnet etc.:
New-NetQosPolicy“LM“ -LiveMigration -PriorityValue 5
Name : LM
Owner :GroupPolicy (Machine)
NetworkProfile : All
Precedence :127
Template : LiveMigration
PriorityValue :5
New-NetQosPolicy“SMB“ -SMB -PriorityValue 3
New-NetQosPolicy“Cluster“ -IPDstPort 3343 -PriorityValue 6
To enable priority tagged traffic on the Virtual Switch:
Set-VMNetworkAdapter –ManagementOS –IeeePriorityTag On
- Veeam Surebackup – PART 3: Surebackup Görevi - 26 September 2020
- Veeam Surebackup – PART 2: Application Group - 26 September 2020
- Veeam SureBackup – PART 1: Virtual LAB - 22 September 2020