HCX Migration fails with "Could not find MA host at source/target side."

Products

• VMware HCX
• VMware Cloud on AWS
• VMware Cloud on Dell EMC

Issue/Introduction

HCX validation for a migration will fail with the error, "Could not find MA host at source/target side" as shown in the screenshots below:

Environment

VMware HCX

Cause

This is caused by the MA host not deployed on either ends of the HCX deployments. The MA host is used by the IX appliances to facilitate migrations. Without the MA host, all migrations will fail.

Resolution

Perform the following actions to resolve the "Could not find MA host at source/target side" error:

• Make sure HCX Manager & IX is on the latest version.
• Verify that the Mobility agent (MA) host is deployed at both the on-prem site and on the cloud site HCX.
• If an MA host is not deployed, redeploy the IX appliance(es) for the side that does not have the MA host deployed.
• Confirm the MA host has been deployed and re-attempt the migration validation.
• Another resolution: Edited the Service Mesh and added “Cross-Cloud vMotion Migration service”.

Additional Information

Impact/Risks:
Migrations will not be successful without an MA host deployed on both ends of the HCX Site Pair.

The MA is not deployed when only "Hybrid Interconnect" and "Bulk Migration" services selected as the vMotion service is not needed for these migration types.