Unable to Migrate VM (vMotion) if a different NSX-T segment is selected on the destination host

Products

• VMware NSX
• VMware vSphere ESXi

Issue/Introduction

• When attempting to migrate a Virtual Machine using vMotion, the vMotion compatibility check fails if a different NSX segment (e.g: based on an N-VDS host switch or between two segments or logical switches on different VLAN transport zones) is selected on the destination host, displaying the following error:
  Currently connected network interface" 'Network adapter #' cannot use network '########-####-####-####-############', because "the type of the destination network is not supported for vMotion based on the source network type
  
  
  
• Source vCenter logs /var/log/vmware/vpxd/vpxd.log shows the following error for the vMotion attempt:

info vpxd[07847] [Originator@6876 sub=VmCheck opID=########-3528980-auto-23mz9-h5:########-a9] CompatCheck results: (vim.vm.check.Result) [
-->    (vim.vm.check.Result) {
-->       vm = 'vim.VirtualMachine:########-c397-4696-8a1b-############:vm-######',
-->       host = 'vim.HostSystem:########-1381-44fe-9cca-############:host-##',
-->       error = (vmodl.MethodFault) [
-->          (vim.fault.CannotUseNetwork) {
-->             faultMessage = (vmodl.LocalizableMessage) [
-->                (vmodl.LocalizableMessage) {
-->                   key = "com.vmware.net.feature.cap.supportVmotionBetweenOpaqueNetwork",
-->                   message = "See KB article 56991 for more details.",
-->                }
-->             ],
-->             device = "Network adapter 2",
-->             backing = "########-72ac-4a64-b963-############",
-->             connected = true,
-->             reason = "VMotionToUnsupportedNetworkType",
-->             network = 'vim.dvs.DistributedVirtualPortgroup:########-1381-44fe-9cca-############:dvportgroup-14347',
-->             msg = "Currently connected network interface 'Network adapter 2' cannot use network '########-72ac-4a64-b963-############', because the type of the destination network is not supported for vMotion based on the source network type."

Environment

VMware NSX
VMware NSX-T
VMware vSphere 8.0.x
VMware vSphere 7.0.x
VMware vSphere 6.7.x
VMware vSphere 6.5.x

Cause

vMotion (hot migration with VM power-on) between NSX logical switches/segments is not officially supported.

Resolution

This is a condition that may occur in a VMware NSX environment and may be addressed in a future version of NSX.

Workaround:

Option 1 (recommended). Powered-off VM workloads can be migrated between NSX transport-zones.
Option 2 (not recommended): This compatibility check can be bypassed via an advance vCenter config option "vpxd.network.allowVmotionBetweenLogicalSwitches"

WARNING:
Network downtime may occur during the vMotion process.

1. Browse to the Advanced Setting in vCenter.
2. Add the parameter "config.vpxd.network.allowVmotionBetweenLogicalSwitches" and set the value to "TRUE".

Additional Information

vMotions of powered-on VM's are failing between clusters on different NSX transport-zones.
Create Transport Zones

Note: vMotion is not supported between two segments or logical switches on different VLAN transport zones.