HCX RAV migration failure during switchover "Currently connected network interface 'Network adapter 1' uses network '<VM network name> (nsx.LogicalSwitch:)', which is not accessible."

Products

• VMware HCX

Issue/Introduction

• HCX RAV migration fails during switchover with the following error in the UI. 
  
  The source VM is running on NSX-T segment ( ie There is NSX-T on the source as well). The network name in the error is the network source VM is attached.
  
  
• ESXi Task - failed to relocate the VM to the MA host. 
  • 
• The app.log is located at /common/logs/admin/ shows the following errors
  <timestamp> UTC [VmotionService_SvcThread-#####, Ent: HybridityAdmin, , TxId: #########-####-####-####-############] ERROR c.v.h.s.v.j.StartSourceSideRelocateVmWorkflow- [migId=#########-####-####-####-############] Source side relocate failed for the virtual machine. error is Currently connected network interface 'Network adapter 1' uses network '<VM network name> (nsx.LogicalSwitch:#########-####-####-####-############)', which is not accessible.
com.vmware.vim.binding.vim.fault.CannotAccessNetwork: Currently connected network interface 'Network adapter 1' uses network '<VM network name> (nsx.LogicalSwitch:#########-####-####-####-############)', which is not accessible.

Environment

VMware HCX

Cause

The failure is due to HCX's inability to access the VM's NSX-T segment due to an invalid NSX-T registration with HCX. 

Resolution

Login to the HCX admin page via https://<HCX FQDN/IP>:9443, 

Confirm the NSX-T connection status shows as connected & green, else reconnect and restart the Web and App services. 

If NSX-T is successfully connected,

• • Edit the affected service mesh.
  • Remove the RAV and vMotion services from the servicemesh.
  • Complete and apply the changes, which will trigger the removal of the Mobility agent. 
  • Re-add the RAV/vMotion services to recreate the MA host.