HCX Mobility Agent fails to deploy with error "Failed to configure the VIM account on the host. Fault case: vim.fault.InvalidName"
search cancel

HCX Mobility Agent fails to deploy with error "Failed to configure the VIM account on the host. Fault case: vim.fault.InvalidName"

book

Article ID: 417238

calendar_today

Updated On:

Products

VMware HCX VMware Cloud Foundation

Issue/Introduction

  • HCX Interconnect (IX) appliance deployment fails on adding Mobility Agent task.

  • Navigating to the HCX Manager UI https://<HCX-Manager-FQDN> → Interconnect →Tasks, shows the error below

    ApplianceLifecycleJob Failed. Reason: Interconnect Service Workflow interconnectConfigureMA failed. Error: Adding Mobility Agent Host failed. A general system error occurred: internal error Failed to configure the VIM account on the host: Fault cause: vim.faultInvalidName. Adding Mobility Agent Host failed. A general system error occurred: internal error Failed to configure the VIM account on the host: Fault cause: vim.fault.InvalidName

  • Login to the HCX Manager as user admin and navigate to the log location /common/logs/admin/app.log 

    A general system error occurred: internal error Failed to configure the VIM account on the host: Fault cause: vim.fault.InvalidName
  • Navigating to the HCX IX log location shows the error below : /var/log/vmware/mobilityagent.log

    Failed to read advanced option subtree Security.PasswordQualityControl: N3Vim5Fault11InvalidName9ExceptionE(Fault cause: vim.fault.InvalidName
    Or
    Failed to read advanced option subtree Misc.MaximumHardwareVersion: N3Vim5Fault11InvalidName9ExceptionE(Fault cause: vim.fault.InvalidName)
  • Service Mesh deployment task fails with the error:

    Adding Mobility Agent Host failed. A general system error occurred: internal error 
    Failed to configure tne VIM account on tne host: Fault cause: vim.fault.InvalidName

Environment

VCF 9.0
VMware HCX 9.0

Cause

  1. HCX versions earlier than 9.0 are not supported with vCenter 9.0 within the same HCX site.
  2. For example, HCX 4.11.x must not be paired or connected to a vCenter 9.x instance at the same site.

For additional details, please refer to the Product Interoperability Matrix.

Resolution

  1. Ensure that HCX is upgraded to version 9.x.
  2. Use Bulk Migration, as this does not have the Mobility Agent dependency.

Additional Information

VMware Product Compatibility Matrix

Configuring VCF Operations HCX