To set up Multi-NIC vMotion in vSphere on a Standard vSwitch:
- Log into the vSphere Client and select the host from the inventory panel.
- Click the Configuration tab and select Networking.
- Click Add Networking and choose VMkernel as the Connection Type.
- Click Next.
- Add two or more NICs to the required standard switch. Create a new vSphere standard switch or use an existing vSwitch.
Note: Ensure that all adapters are on the same network when connected to a physical Ethernet environment. If the adapters are split across switches, then all adapters must be able to communicate across those switches.
- Name the VMkernel portgroup (for example,
vMotion-01
), and assign a VLAN ID as required.
- Click Use this port group for vMotion, then click Next.
- Configure the IP address and subnet mask, then click Next..
- Click the Properties tab of the vSwitch, select the
vMotion-01
portgroup, and click Edit.
- Click the NIC Teaming tab.
- Under Failover Order, select Override switch failover order.
- Configure the first adapter (for example,
vmnic1
) as active
and move the second adapter (for example, vmnic3
) to standby
.
- Click OK.
- Under the vSwitch Properties, click Add to create a second VMkernel portgroup.
- Name the VMkernel portgroup (for example,
vMotion-02
), and assign a VLAN ID as required.
Note: Ensure that the both VMkernel interfaces participating in the vMotion have the IP address from the same IP subnet.
- Click Use this port group for vMotion, then click Next.
- Configure the IP address and subnet mask, then click Next.
- Click the Properties tab of the vSwitch, select the
vMotion-02
portgroup, and click Edit.
- Click the NIC Teaming tab.
- Under Failover Order, select Override switch failover order.
- Configure the second adapter (for example,
vmnic3
) as active
and move the first adapter (for example, vmnic1
) to standby
.
- Click the Properties tab of the vSwitch. Select each vMotion portgroup in turn and confirm that the active and standby adapters are the reverse of each other.
Setting up multi-NIC vMotion in vSphere on a distributed vSwitch
- Log into the vSphere Client and click the Networking inventory.
- Click New vSphere Distributed Switch and choose latest version
- Name the Distributed switch (for example,
Multi-NIC-vMotion
).
- Assign two or more uplink ports to the switch, then click Next.
- Select physical adapters to each of the hosts, then click Next and Finish.
Note: Ensure that all the adapters are on the same network when connected to a physical Ethernet environment. If the adapters are split across switches, then all adapters must be able to communicate across those switches.
- Expand the Distributed switch you just created, click the dvPortGroup and click Edit Settings.
- Name the dvPortgroup (for example,
vMotion-01
).
- Click VLAN and assign a VLAN ID as required.
- Click the Teaming and Failover tab, configure dvUplink1 as
Active Uplink
and move dvUplink2 to Standby Uplink
.
- Right-click the Distributed vswitch, then click New Port Group.
- Name the dvPortgroup (for example,
vMotion-02
).
- Click VLAN and assign a VLAN ID as required, then click Next and Finish.
- Select the second portgroup created, then click the Teaming and Failover tab.
- Configure dvUplink2 as
Active Uplink
and move dvUplink1 to Standby Uplink
.
- Click the Hosts and Clusters Inventory tab, select a host's Networking, and click vSphere Distributed Switch.
- Click Manage Virtual Adapters and then click Add.
- Select the New virtual adapter option.
- Choose VMkernel as the Virtual Adapter Type.
- Select the
vMotion-01
portgroup, click Use this port group for vMotion, then click Next.
- Configure the IP address and subnet mask, then click Next and Finish.
- Add another virtual adapter, then select the
vMotion-02
portgroup.
- On the Distributed vSwitch, select each dvportgroup on VMKernel Port
vmk1
and vmk2
in turn, and confirm that the active and standby uplinks are the reverse of each other.
Note: Ensure that the both VMkernel interfaces participating in the vMotion have the IP address from the same IP subnet.
After making these configuration changes, when you initiate a vMotion, multiple NIC ports are used. Even when performing a vMotion on just one virtual machine, both links are used.
If you do not have dedicated links for vMotion, consider using Network I/O Control. vMotion can saturate a link. When you set up Network I/O Control, and assigned the correct amount of shares, each type of traffic gets what it has been assigned.
Note: vMotion and IP-based storage traffic should not be routed, as this causes latency issues. Any internal/private subnet can work as long as it is unique and dedicated exclusively to that specific type of traffic. Routed IP storage is not supported. Follow the recommendations for IP-based storage configuration published by VMware.
Note: In a multi-NIC vMotion configuration, one VMkernel port group may be present on a standard switch and the other one on a distributed switch.