Tag Archives: teaming

Create a SET Team in Server 2016 – HowTo…

SET (Switch Embedded Teaming) is a new technology in Windows Server 2016 and the successor to the “standard” teaming technology in Server 2012R2 (LBFO Team) – read more: https://technet.microsoft.com/en-us/library/mt403349.aspx

HINT: only available if you have added the Hyper-V role in Windows, because otherwise no PS-CMDLets are available to configure…

Create a vSwitch

First you have to create a new virtual switch and add the physical NICs:

…a vswitch with the name “TeamedvSwitch” is created – the physical adapters will be connected to this vswitch and a vNIC with the default name “vEthernet (TeamedvSwitch)” are created:

HINT: like in 2012R teaming, it is possible to create a SET team with a single physical NIC and add additional NICs later – so my recommendation is to create always a SET team even if you have only a single NIC.

Rename vNIC(s)

We want to rename the default vNIC for better administration:

HINT: you see that i have two physical NICs from different vendors – it work´s in my vLab but for production environment it is not supported to have a SET team with NICs from different vendors, with different firmware or drivers…

Add vNIC(s)

…and we want to add another vNIC for LiveMigration traffic:

…and additional vNICs for CSV/ClusterHB and Storage Traffic:

Show all “Management” adapters in powershell:

Set VLANid on vNIC(s)

I have different VLANs for the traffic:

VLANid Description
0(native/untagged) Management/RDP/PXE/DHCP….
400 LiveMigration
300 SMB-Storage Traffic
250 ClusterHB

HINT: many switch vendors won´t pass traffic class information on untagged networks. Best practice if using RDMA, DCB and PFC is that the “untagged” network are on VLAN 0 (tagged) – i.e. “Set-VMNetworkAdapterVlan -VMNetworkadapter $NIC -Access -VlanId 0” for the management interface. This set all vNICs in a VLAN, class information can be inserted into the VLAN header of IP packets and the physical switch pass this type of traffic.

Enable JumboFrames

Dont forget to enable Jumbo Frames, this can significant speed up your network.

To enable Jumbo Frames you have to configure it on the switch side with the appropriate tools WebGUI,CLI,.. – i always use 9KB – on most NICs it exist a value of 9014 bits, but this is depending on your NIC vendor and driver. Check the Advanced Properties on the NIC in windows – if you dont see settings for Jumbo Frames and/or 9KB (sometimes if you using original windows drivers for nic) update to the latest vendor driver.

The following is a example of a Realtek NIC with the shipped windows driver in server 2016:

(the max value in JumboPacket is 4k and fixed size, no bigger values available…)

AFTER updating the driver to realtek driver version 10.2.703.2015:

(now 9KB is available in advanced properties…)

Set the value on all physical NICs:

(regarding 9014 bits: i prefer this little smaller value than in the switch port setting (9216) but realtek does not allow 9014 like intel and other vendors, you have to use 9216 if you have realtek nic)

HINT: in Windows 2012R2 the vNICs inherit the settings from the LBFO-Team, so if you set all physical NICs to JumboFrame with i.e. 9014 bits – all the vNICs have automatically 9014 bits in their settings – in Windows 2016 with SET teaming this is different (!) – you have to set explicit ALL physical AND vNICs to JumboFrame.

Set all vNICs to Jumbo Frames:



Now we have divided the traffic into several VLANs, but every kind of traffic using all of the available bandwith and have no priority of each other – we have two options to deal with that:

  • QoS
  • PFC and DCB