Use the vMotion TCP/IP stack to isolate traffic for vMotion and to assign a dedicated default gateway for vMotion traffic.

By using a separate TCP/IP stack, you can manage vMotion and cold migration traffic according to the topology of the network, and as required for your organization.

Route the traffic for the migration of virtual machines that are powered on or powered off by using a default gateway that is different from the gateway assigned to the default stack on the host.

Assign a separate set of buffers and sockets.

Avoid routing table conflicts that might otherwise appear when many features are using a common TCP/IP stack.

Isolate traffic to improve security.

Decision ID

Design Decision

Design Justification

Design Implication


Use the vMotion TCP/IP stack for vMotion traffic.

By leveraging the vMotion TCP/IP stack, vMotion traffic can utilize a default gateway on its own subnet, allowing for vMotion traffic to go over Layer 3 networks.

The vMotion TCP/IP stack is not available in the vDS VMkernel creation wizard, and as such the VMkernal adapter must be created directly on a host.