HCX Mobility Agent Host Not Responding in vCenter

Products

• VMware HCX

Issue/Introduction

The HCX Mobility Agent, which appears as a host object in vCenter Server, may sometimes show as "Not Responding". The Mobility Agent is a critical service deployed by the HCX Interconnect (IX) appliance to facilitate vMotion, Cold, and Replication Assisted vMotion (RAV) migrations. When this host object appears as not responding, it can impact migration capabilities and associated services.

Common symptoms include

• Mobility Agent host showing as "Not Responding" in vCenter
• Inaccessible datastores created by the Interconnect
• Failed Interconnect deployment or redeployment attempts
• Interconnect appliance stuck in "Deploying" status
• Unable to perform vMotion, Cold, or RAV migrations through the affected Interconnect

Understanding the Mobility Agent

The Mobility Agent is a specialized service that

• Appears as a host object in vCenter Server
• Is automatically deployed by the HCX-IX appliance
• Facilitates critical migration functions (vMotion, Cold, RAV migrations)
• Does not represent actual resource consumption on the physical hypervisor
• Is essential for HCX migration operations

For detailed information about the Mobility Agent, refer to the VMware documentation: Mobility Agent vSphere Host for HCX Migrations

 

Environment

• HCX
• vSphere environments with HCX Interconnect configured
• HCX Mobility Agent deployments

Cause

• Interrupted or failed Interconnect deployment
• Configuration inconsistencies in the Interconnect service
• Failed redeployment attempts of the Interconnect appliance
• Storage issues with the Interconnect appliance's datastore
• Full or inaccessible Interconnect storage affecting service operations

Resolution

Immediate Diagnostic Steps

1. Check the status of the Interconnect appliance in HCX Manager
2. Verify the availability of associated datastores
3. Review any failed deployment or redeployment tasks

Resolution Steps

1. Resync Service Mesh if applicable
2. Force Redeploy the Interconnect
   • Access the HCX Manager interface
   • Locate the affected Interconnect service
   • Initiate a force redeploy operation
   • Monitor the redeployment process to completion
   • If the redeploy fails resolve any errors before attempting redeploy again
3. Verification
   • Confirm the Mobility Agent host returns to a responding state
   • Verify datastore accessibility
   • Check the Interconnect service status

If issues persist after following these steps, contact Broadcom Support for additional assistance. Upload HCX logs including the Interconnect logs to the case if possible.