This article provides information on performing a vMotion across multiple NICs.
vMotion-01
), and assign a VLAN ID as required.vMotion-01
portgroup, and click Edit.vmnic1
) as active
and move the second adapter (for example, vmnic3
) to standby
.vMotion-02
), and assign a VLAN ID as required.vMotion-02
portgroup, and click Edit.vmnic3
) as active
and move the first adapter (for example, vmnic1
) to standby
.
Multi-NIC-vMotion
).vMotion-01
).Active Uplink
and move dvUplink2 to Standby Uplink
.vMotion-02
).Active Uplink
and move dvUplink1 to Standby Uplink
.vMotion-01
portgroup, click Use this port group for vMotion, then click Next.vMotion-02
portgroup.vmk1
and vmk2
in turn, and confirm that the active and standby uplinks are the reverse of each other.
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 don't 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.
It's not supported to utilize the same VMkernel adapters for Multi-NIC vMotion as you use for iSCSI with Port Binding, as the Teaming and Failover options needed for each are contradictory. See Considerations for using software iSCSI port binding in ESXi for details.