vMotion of powered-on VMs is failing between clusters on different NSX transport zones

Products

• VMware NSX

Issue/Introduction

• Cross cluster vMotion of a powered-on VM from NSX transport-zone-A to transport-zone-B results in failure with an error similar to the message below after ~40%.
  

  Failed waiting for data. Error 195887107. Not found. 2023-07-18T17:11:13.670348Z The migration transfer failed during the receive operation to socket 73776445253552: received 0/36 bytes: Connection reset by peer. vMotion migration [-1407559628:1219240582921523858] failed to read stream keepalive: Connection reset by peer Migration to host <###.###.###.###> failed with error Connection reset by peer (195887179). 2023-07-18T17:11:13.862725Z vMotion migration [-1407559628:1219240582921523858] failed to get DVS state in the restore phase from the source host <###.###.###.###> Resources check fine when selecting them.

Environment

VMware NSX

Cause

This is an unsupported function in all NSX releases.

Resolution

No resolution. May be addressed in a future version of NSX.

Workaround:

Powered-off VM workloads can be migrated between NSX transport-zones.

 

Additional Information

Create Transport Zones

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