«

»

Jun 29 2017

Print this Post

Migrate from NIC Teaming to SET in Windows Server 2016 and VMM

So you just upgraded your Hyper-V hosts to Windows Server 2016 and read about the new Switch Embedded Teaming (SET) switches and how they make life all roses and butterflies. In this post, we will discuss how to migrate from the traditional teaming in previous versions of Windows Server to the amazing SET virtual switch introduced in Windows Server 2016.

What is SET? and why is it so cool?

I’m sure there are tons of places to read about SET in details but let us discuss it here briefly in few points,

  • You do not need to team NICs on a Hyper-V host. The virtual switch handles the teaming (Embedded teaming, you know?!)
  • Up to 8 NICs and all NICs must be identical.
  • In Windows Server 2012 R2 it did not support RDMA which is why it wasn’t so popular.
  • In Windows Server 2016 RDMA works over any virtual switch with or without SET. Yay!
  • SET + multiple host vNICs = complete abstraction between physical and virtual networking
  • With SET and converged networking, all network interfaces are highly available not just the VM networks without the need for more physical NICs.
  • Manageable through PowerShell, but really cannot be managed unless you use VMM

In summary, you will be able to have exactly the amount of NICs you desire on the host with high availability and granular control over their bandwidth.

The following two pictures illustrate the difference,

Before SET

How Hyper-V networking was done before Windows Server 2012 (Image Credit: Aidan Finn)

After SET

Switch Embedded Teaming and converged RDMA in Windows Server 2016 Hyper-V (Image Credit: Microsoft)

Excited?! Let’s migrate

So, to migrate without interrupting the VMs, we need to follow steps like the example below.

Example configuration

Before

  • Cluster with 3 Hyper-V hosts.
  • 4x10Gbps network ports per hosts.
  • Port 1 and 2 are teamed to create VMs’ virtual switch
  • Port 3 used for Management
  • Port 4 used for Live Migration and Cluster communication.

After

  • Cluster with 3 Hyper-V hosts.
  • 4x10Gbps network ports per hosts.
  • All ports are members in the SET switch
  • Two vNICs for Management and LM & Cluster Communication.
  • Optional- More vNICs can be added later to separate LM or SMB3 etc…

Migration steps,

  1. Create new logical switch configuration in VMM
    1. Uses Embedded Team for Uplink Mode
    2. Minimum bandwidth mode is Weight
    3. Add the following Virtual Port profiles (minimum)
      1. Host Management
      2. Live Migration Workload
    4. Configure the switch as below and to access required sites
    5. Add two New virtual network adapters and configure the Host Management to Inherit connection settings.
  2. On each host, create the SET switch
    1. Place the host in maintenance mode.
    2. Make sure all ports are set to trunk.
    3. Configure the port currently assigned for LM to use DHCP.
    4. Create the logical switch for SET using the Management NIC
    5. VMM will create the SET switch, two vNICs, and one will have the same IP as the Management.
    6. Double check the host is reachable and review IP addresses (now you can change the IP address from VMM)
    7. Add the second NIC – previously used for LM – to the new SET switch
    8. Stop the maintenance mode.
  3. Check that VMM understands that the new switch is highly available from the cluster properties.
  4. Move all VMs to use the new switch
    1. Test manually first on a VM to confirm the new switch works properly!
    2. Use this PowerShell snippet to move all VMs to the new switch. You can monitor progress using the Jobs Window in VMM.
  5. Optional – Confirm that all VMs are online using the steps in Ping all VMs in a Hyper-V Cluster post.
  6. Finishing up, on each host do the following from VMM
    1. In one step delete the old switch and add its NICs to the new SET switch

VMM will handle deleting the old switch and its team first then it will join the NICs to the SET switch

  1. Rename the NICs on Hyper-V host to be representative.

That’s it, no more teams, higher redundancy, and more control. This is my go to switch from now on!

Cheers!

About the author

Walid AlMoselhy

Permanent link to this article: http://almoselhy.azurewebsites.net/2017/06/migrate-from-nic-teaming-to-set-in-windows-server-2016-and-vmm/

Leave a Reply

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