To isolate vSphere vMotion traffic, it should be placed on its own dedicated TCP/IP stack. The vMotion TCP/IP stack provides a separate routing table, gateway, and DNS configuration specifically for live migration traffic. According to VMware documentation, the TCP/IP stack for an existing VMkernel adapter cannot be modified. Therefore, the correct procedure is to remove the existing VMkernel port (PROD01) that is on the default stack and create a new VMkernel port, explicitly assigning it to the vSphere vMotion TCP/IP stack during creation. This ensures vMotion traffic is routed independently from other traffic types like management or IP storage.

B. The provisioning TCP/IP stack is used for cold migration, cloning, and snapshot traffic, not for live vMotion migrations.

C. This option uses the incorrect stack (provisioning) and fails to remove the original VMkernel port, not achieving the goal of isolating vMotion traffic.

D. It is not possible to modify the TCP/IP stack of an existing VMkernel adapter. The adapter must be deleted and recreated on the desired stack.

1. VMware vSphere Documentation

"vSphere Networking" (for vSphere 7.0). In the section "TCP/IP Stacks and VMkernel Networking

" it states: "You can select a TCP/IP stack when you create a VMkernel adapter. You cannot change the TCP/IP stack for an existing VMkernel adapter." This directly refutes option D and supports the delete-and-recreate method in option A.

2. VMware vSphere Documentation

"vSphere Networking" (for vSphere 7.0). The subsection "vMotion TCP/IP Stack" explains its purpose: "The vMotion TCP/IP stack supports the traffic for live migration of virtual machines. Use the vMotion TCP/IP to provide better isolation for the vMotion traffic." This confirms that using the vMotion stack is the correct method for isolation.

3. VMware vSphere Documentation

"vSphere Networking" (for vSphere 7.0). The subsection "Provisioning TCP/IP Stack" clarifies its use: "The provisioning TCP/IP stack supports the traffic for virtual machine cold migration

cloning

and snapshot migration." This confirms that options B and C suggest using the incorrect stack for the stated goal.