How to Configure Multi-NIC vMotion in vSphere 5 on a Standard vSwitch

Multi-NIC vMotion lets VMware vSphere use more than one network adapter for a single vMotion, so live migrations finish much faster. Here’s how to set it up in vSphere 5.x on a standard vSwitch using two VMkernel port groups with opposite failover order.

Create the First vMotion Port Group

  1. Log in to the vSphere Client and select the host in the inventory panel.
  2. Click the Configuration tab and select Networking.
  3. Click Add Networking, choose VMkernel as the connection type, and click Next.
  4. Add two or more NICs to a new or existing standard vSwitch. Note: all adapters must be on the same physical network; if they’re split across switches, those switches must be able to talk to each other.
  5. Name the VMkernel port group (for example, vMotion-01) and assign a VLAN ID if needed.
  6. Check Use this port group for vMotion and click Next.
  7. Enter the IP address and subnet mask and click Next.
  8. Open the vSwitch Properties, select vMotion-01, and click Edit.
  9. On the NIC Teaming tab, under Failover Order, select Override switch failover order.
  10. Set the first adapter (for example, vmnic1) as Active and move the second (for example, vmnic3) to Unused Adapters. Click OK.
vSphere standard vSwitch with two vMotion VMkernel port groups

Create the Second vMotion Port Group

  1. In the vSwitch Properties, click Add to create a second VMkernel port group.
  2. Name it (for example, vMotion-02) and assign a VLAN ID if needed. Note: both vMotion VMkernel interfaces must have IP addresses on the same subnet.
  3. Check Use this port group for vMotion, click Next, enter the IP address and subnet mask, and click Next.
  4. Edit vMotion-02, go to NIC Teaming, and select Override switch failover order.
  5. Set the second adapter (vmnic3) as Active and move the first (vmnic1) to Unused Adapters.
  6. Select each vMotion port group in turn and confirm their active and unused adapters are the reverse of each other.

Scaling to More NICs

I repeated these steps two more times because I had four NICs. Each one went to its own physical network card, which was also bound to the software iSCSI HBA. After the change, I migrated the same machines back out across both hosts using all the configured NICs.