Virtual Machine Manager 2016 and Teaming

In Windows Server 2012 R2 we used LBFO (Load Balancer Fail Over) teaming where multiple NICs are grouped together into a team and that resultant teamed adapter is used by a Hyper-V switch.

In Windows Server 2016 we can use SET ( Switch Embedded Teaming) is an alternative NIC Teaming solution that you can use in environments that include Hyper-V and the Software Defined Networking (SDN) stack in Windows Server 2016.

You can read detailed information from the Microsoft article Windows Server 2016 NIC and Switch Embedded Teaming User Guide.

In this post I will show the steps how to create teaming via VMM 2016.


I have already created basic network settings to the VMM configuration:

Now we can start to create logical switch:

Here you can see new option for the SET:
No Uplink Team: if you’re not using teaming.
Embedded Team: if you want to deploy the switch with SET-based teaming
Team: if you want to use NIC teaming

In Settings, select the minimum bandwidth mode. If you’ve deployed Microsoft network controller, you can specify that it should manage the switch. If you enable this setting you won’t be able to add extensions to the switch.
Enable SR-IOV if you need to. SR-IOV enables virtual machines to bypass the switch and directly address the physical network adapter.

And here is the new “thing” as well, you can create uplink port profile:

Select Logical networks which are available from the switch:

And create needed vNics:

Create switch:

And that´s it, you have created switch and now you can apply it to the Hyper-V host.
For detailed explanations for the all settings please refer Microsoft article Create logical switches.

When you are applying settings to host, it will automatically contain earlier created settings like vNics etc.


Leave a Reply

Your email address will not be published. Required fields are marked *