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 typeinfo 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."
vMotion (hot migration with VM power-on) between NSX logical switches/segments between 2 different transport zone is not officially supported.
This is a condition that may occur in a VMware NSX environment and may be addressed in a future version of NSX.
Workaround: Powered-off VM workloads can be migrated between NSX transport-zones.
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.