this example, four 1Gbps NICs are used together and then used by the virtual switch,
which now services virtual machines and the different vNICs in the management
partition for various types of communication. However, it would also be common to
now use two 10Gbps or higher NICs instead. I walk through the process in a video at
[http://www.youtube.com/watch?v=8mOuoIWzmdE, but here are some of the commands to](http://www.youtube.com/watch?v=8mOuoIWzmdE, but here are some of the commands to)
create two vNICs in the host in a new NIC team and virtual switch. I assign a
minimum bandwidth weight QoS policy. If required, each vNIC can be configured with
a separate VLAN ID.
Figure 3.43 A converged Hyper-V host configuration with a shared NIC team used
New-NetLbfoTeam -Name "HostSwitchTeam" -TeamMembers NICTeam3,NICTeam4 -TeamingMode Static -Confirm:$false New-VMSwitch "MgmtSwitch" -MinimumBandwidthMode weight
-NetAdapterName "HostSwitchTeam" –AllowManagement $false
Add-VMNetworkAdapter -ManagementOS -Name "LiveMigration" -SwitchName "MgmtSwitch" Set-VMNetworkAdapter -ManagementOS -Name "LiveMigration"
-MinimumBandwidthWeight 50
Add-VMNetworkAdapter -ManagementOS -Name "Cluster" -SwitchName "MgmtSwitch"
Set-VMNetworkAdapter -ManagementOS -Name "Cluster" -MinimumBandwidthWeight 50
I go into detail in an article at: http://windowsitpro.com/windows-server-
2012/quality-of-service-windows-server-2012
The article is definitely worth reading if you want to understand the details of QoS and
why minimum bandwidth is a better solution than the traditional maximum-
bandwidth caps that always limited the available bandwidth to the cap value, even if
more bandwidth was available. The exception to the use of maximum-bandwidth caps
tends to be hosters that charge customers based on a certain amount of bandwidth
being available and do not want to give any extra free bandwidth. No free bits! Using