SDDC Manager precheck is not running
search cancel

SDDC Manager precheck is not running

book

Article ID: 436456

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

  • While running a precheck prior to upgrading the management domain, the SDDC Manager precheck is started and is almost immediately getting failed with an error -

A problem has occurred on the server. Please retry or contact the service provider and provide the reference token

  • Reviewing the SDDC Manager log /var/log/vmware/vcf/operationsmanager/operationsmanager.log using the error token for reference, the entry below is identified - 

YYYY-MM-DDThh:mm:ss.sss+0000 ERROR [vcf_lcm, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, xxxx,auditId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,resourceType=NSX_T_MANAGER, resourceId=nsx_manager_vip_fqdn, name=nsx_manager_vip_fqdn] [c.v.e.s.l.p.i.nsxt.NsxtUpgradeUtil, Scheduled-x] Handling NSX Exception
com. vmware.evo. sddc. lcm.model.error. LcmException: Failed to load NSX Cluster from the Inventory

  • The SDDC Manager UI > Security > Password Management page shows that the admin account for the NSX Manager is in a disconnected state

 

Environment

VCF 5.1.0.0

Cause

The precheck is failing on the SDDC Manager because the admin account for the NSX Manager is in a disconnected state, the SDDC Manager is unable to properly communicate with the NSX Manager.

Resolution

  • Remediate the NSX Manager admin account on the SDDC Manager UI > Security > Password Management page
  • Retry the precheck workflow on the SDDC Manager, it is expected to be successful this time

Additional Information

The credentials were incorrect or the account specified has been locked

  • If an admin password has been set on the NSX Manager directly and it does not meet the password complexity requirements of SDDC Manager, a more complex password will need to be set on the NSX Manager first. Note that on occasion it is necessary to change the admin password on all three NSX Manager nodes at the same time, rather than just on the NSX Manager VIP due to how NSX replicates the password change between nodes, in order for the password change to persist.