You can use the vSphere vMotion TCP/IP stack to isolate traffic for vMotion and the provisioning TCP/IP stack to isolate traffic for cold migration, VM clones, and snapshots.
How to Place vSphere vMotion Traffic on the vMotion TCP/IP Stack of Your ESXi Host
Learn how to use the vMotion TCP/IP stack to isolate traffic for vMotion and to assign a dedicated default gateway, routing table, and DNS configuration for this traffic. To enable the vMotion TCP/IP stack, assign a new VMkernel adapter to it.
By using a separate TCP/IP stack, you can handle vMotion traffic according to the topology of the network and as required for your organization:
-
Route the traffic for migration of powered on virtual machines by using a default gateway. The gateway may be 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.
Prerequisites
Verify that the host is running ESXi 6.0 or later
Procedure
Results
After you create a VMkernel adapter on the vMotion TCP/IP stack, you can use only this stack for vMotion on this host. The VMkernel adapters on the default TCP/IP stack are deactivated for the vMotion service. If a live migration uses the default TCP/IP stack while you are configuring VMkernel adapters with the vMotion TCP/IP stack, the migration completes successfully. However, the involved VMkernel adapters on the default TCP/IP stack are deactivated for future vMotion sessions.
What to do next
Assign a default gateway, and configure the DNS settings, congestion control, and maximum number of connections for the vMotion TCP/IP stack.
For more information on how to change the configuration of a TCP/IP stack on a host, see the vSphere Networking documentation.
How to Place Traffic for Cold Migration, Cloning, and Snapshots on the Provisioning TCP/IP Stack
Learn how to use the provisioning TCP/IP stack to isolate traffic for cold migration, VM clones, snapshots, and cold data in hot migration, and to assign a dedicated default gateway, routing table, and DNS configuration for this traffic. To enable the Provisioning TCP/IP stack, assign a new VMkernel adapter to it.
By using a separate TCP/IP stack, you can handle vMotion traffic according to the topology of the network and as required for your organization:
-
Route the traffic for migration of powered on virtual machines by using a default gateway. The gateway may be 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.
Prerequisites
Verify that the host is running ESXi 6.0 or later
Procedure
Results
After you create a VMkernel adapter on the provisioning TCP/IP stack, you can use only this stack for cold migration, cloning, and snapshots on this host. The VMkernel adapters on the default TCP/IP stack are deactivated for the provisioning service. If a live migration uses the default TCP/IP stack while you configure VMkernel adapters with the provisioning TCP/IP stack, the data transfer completes successfully. However, the involved VMkernel adapters on the default TCP/IP stack are deactivated for future cold migration, cross-host cloning, and snapshot sessions.