"Preparing hosts is failed" error in NSX Manager while ESX cluster shows Compliant

Products

• VMware vCenter Server

Issue/Introduction

• Navigating to the System > Fabric > Hosts > Clusters tab in VMware NSX Manager displays a "Preparing hosts is failed" error.
• Checking the cluster object under the Configure tab > Desired State > Configuration in the vSphere Client shows the ESX cluster is in a Compliant status.

Environment

VMware vCenter 9.0
VMware NSX 9.0
VMware Cloud Foundation 9.0

Cause

A status synchronization mismatch occurs between NSX and the ESX cluster when deploying a Transport Node Profile. As a result, NSX Manager displays a status error, while the ESX cluster is shown as Compliant in the vSphere Client.

Resolution

Phase 1: Attempt Status Remediation If a status mismatch occurs between NSX and the ESX cluster, it may be resolved by re-executing the remediation process.

1. In the vSphere Client, navigate to the cluster's Configure tab > Desired State > Configuration > Compliance tab.

2. Execute CHECK COMPLIANCE, RUN PRE-CHECK, and REMEDIATE in order.

3. Verify if the ESX cluster status becomes Compliant and the NSX status error is resolved. (If the error is resolved, you do not need to proceed to Phase 2).

Phase 2: Perform ESX Cluster Reconfiguration
If the status mismatch continues to occur after performing Phase 1, perform a cluster reconfiguration using the following steps:

1. In the vSphere Client, place any one ESX host into Maintenance Mode, and evacuate all virtual machines from this host.

2. Move the host that is in Maintenance Mode from under the cluster to the datacenter layer (drag and drop the target ESX from under the cluster to under the datacenter in the object tree).

3. Access NSX Manager and navigate to System > Fabric > Hosts > Standalone or Other Nodes.
   Wait until the Transport Node uninstallation completes. The host is expected to display "NSX Configuration - Not Configured".

4. Once the previous step is complete, return to the vSphere Client and move the target ESX host turn back under the cluster.

5. Navigate to the cluster's Configure tab > Desired State > Configuration > Compliance tab.

6. Execute CHECK COMPLIANCE against the cluster. (This operation is expected to make the target ESX non-compliant).

7. Click RUN PRE-CHECK to perform the pre-check.

8. Execute REMEDIATE and confirm that the ESX state switches to compliant.

9. Once complete, confirm that the cluster state returns to healthy in NSX Manager under System > Fabric > Hosts > Clusters.