Bulk migration gets stuck at 0%, the app.log at /common/logs/admin for the migration ID shows 0 bytes transferred. Additionally, the VM shows a warning banner as "Unable to connect to the VR server: Network"
VMware HCX, VMC on AWS, VMware Cloud on Dell EMC
This issue occurs in HCX when the IX appliance on the Service Mesh is configured for both management and vSphere replication. However, on the on-prem ESXi host where the IX appliance is running, there are separate vmkernel adapters for vSphere replication and management traffic.
The user needs to create a new network profile with a separate IP on the same IX appliance. Once the management and vSphere replication traffic on the IX appliance are routed through different network profiles, the base sync will initiate, VM data replication will begin, and the error banner on the VM will be cleared.
Workaround:
As a workaround, the user can disable the vSphere replication for the ESXi that the IX appliance is residing on On-prem.
Impact/Risks:
The impact with this kind of setup is that the VM will contact the VR server to replicate over to the cloud side. The migration will fail with time out and 0 bytes transferred.