HCX Mobility Agent virtual host showing outdated Hypervisor version within vCenter inventory

Products

• VMware HCX

Issue/Introduction

HCX uses the Mobility Agent host service to perform vMotion, Cold, and Replication Assisted vMotion (RAV) migrations. When viewing the Mobility Agent host in the vCenter inventory, it shows an outdated Hypervisor version.

Environment

vCenter
HCX

Cause

This behavior is observed because HCX was initially deployed on an earlier version of vCenter (e.g., 7.0), during which certain HCX services were enabled that uses Mobility Agent vSphere Host. Following the subsequent vCenter upgrade, the virtual host continues to display the earlier version, as it retains the version information from the original deployment.

Resolution

Remove all vMotion Services:
Edit the service mesh and remove all vMotion services that use the Mobility Agent (MA) virtual host as shown below,

• Cross-cloud vMotion Migration
• Replication Assisted vMotion Migration
• HCX Assisted vMotion Migration

Update Service Mesh:

• Allow the service mesh to update the task successfully 
• Verify that the Mobility Agent host is removed from the vCenter inventory.

Re-enable IX Services:

• Edit the service mesh and add back any necessary IX-associated services.

Final Check:

• Allow the service mesh to update the task successfully 
• Verify that the Mobility Agent host is seen in the vCenter inventory and matches the vCenter version.

Note:

• Bulk Migration, Disaster Recovery, and OS Assisted Migration do not use vMotion or the MA virtual host, so they can remain enabled if in use.
• Hybrid Interconnect and Network Extension services can also stay enabled.
• If you believe you are experiencing this issue and the steps outlined above did not resolve it, please open a support case with Broadcom Support and refer to this KB article. For more information, see Creating and managing Broadcom support cases.

Additional Information

Mobility Agent vSphere Host for HCX Migrations