Error: "Failed to run Health checks for NSX-T" during host remediation

Products

• VMware vSphere ESXi

Issue/Introduction

• When performing host remediation or compliance checks via vSphere Lifecycle Manager (vLCM) in an ESXi 8.x environment, the process fails with the error: "Remediation of cluster failed" or "Failed to run Health checks for NSX-T on '####'"

Environment

VMware vSphere ESXi 8.x

VMware Cloud Foundation 5.x / 9.x

Cause

• This issue is caused by a circular dependency between vLCM and NSX during cluster preparation. vLCM remediation is blocked by the NSX pre-check because NSX components are not yet installed on the host. Conversely, NSX host preparation fails because vLCM reports the cluster as non-compliant, halting the workflow. For more details on this circular dependency, see KB https://knowledge.broadcom.com/external/article?articleNumber=432684
  
  
• If a vCenter is registered with an NSX Manager, vLCM may attempt to validate NSX health even for clusters where NSX is not deployed. The remediation is blocked because the NSX pre-check fails to find active components.

Note: This occurs even if NSX-T is not installed, no NSX VIBs are present on the host, and NSX is not mentioned in the vLCM image components.

Resolution

To resolve this issue, temporarily disable the NSX pre-check in the vCenter Update Manager configuration.

1. Log in to the vCenter Server Appliance (VCSA) via SSH as the root user.

2. Stop the Update Manager service: 

   service-control --stop updatemgr

3. Create a backup of the configuration file: 

   cp /usr/lib/vmware-updatemgr/bin/vci-integrity.xml /usr/lib/vmware-updatemgr/bin/vci-integrity.bak

4. Open the file for editing: 

   vi /usr/lib/vmware-updatemgr/bin/vci-integrity.xml

5. Locate the <nsxt_rest> block and change the value to false 

   <nsxt_rest>
    <enabled>false</enabled>   <<<<<<<<<<
   </nsxt_rest>

   Save and exit the file (:wq!)

6. Start the Update Manager service: 

   service-control --start updatemgr

7. Perform the host remediation in the vSphere Client.

8. Once remediation is complete, revert the changes in vci-integrity.xml by setting the value back to true and restarting the service.

Additional Information

• If you encounter further issues, see Contact Broadcom support.
• For updates regarding fix status, please subscribe to this article: How to subscribe to Broadcom knowledge articles.