- The ESXi host NSX preparation status is stuck at 68% or 80% "Enabling Host Status in Controller.
- Under NSX MGR UI > System > Fabric > Clusters > Host Details, the Configuration State is stuck at "Enabling host status in controller".
- Despite the host preparation status, the VMs running on the impacted hosts and using NSX networking will continue to perform normally with no issues.
- This issue usually occurs after:
- In some cases, the logs may show failure codes, such as 8804 or 8814, indicating the root cause. The specific error code may vary based on the underlying issue. Below are some logs examples:
GET https://<nsx manager>/api/v1/transport-nodes/<transport-node-id>/state:
{ "details": [ { "failure_code": 8804, "failure_message": "Reconfiguring after last failure: LogicalSwitch full-sync: Status is in-progress on '1' transport nodes.", "state": "in_progress", "sub_system_id": "########-####-####-####-############", "sub_system_type": "Host" } ], "failure_code": 8804, "failure_message": "Host configuration failed. Number of retries : 3005. Next retry attempt will be between 2023-Sep-26 13.30.15 PM and 2023-Sep-26 13.33.15 PM (UTC).", "maintenance_mode_state": "DISABLED", "node_deployment_state": { "details": [], "state": "success" }, "state": "in_progress", "transport_node_id": "########-####-####-####-############"},
nsxapi.log: (Log full path : /var/log/proton/nsxapi.log)
2022-02-09T12:29:32.341Z INFO L2HostConfigTaskExecutor2 HostTNDeploymentProgressServiceImpl 11278 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] TN Operation: UPDATE. Host:########-####-####-####-############current progress percentage: 80, stateDescription: deployment.progress.tn.create.waiting_for_host_config_reply2022-02-09T12:29:32.365Z INFO L2HostConfigTaskExecutor2 TransportNodeAsyncServiceImpl 11278 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] TN TransportNode/########-####-####-####-############realization state : IN_PROGRESS, convergence state: IN_PROGRESS, realization message : Status is in-progress on '1' transport nodes.
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
VMware NSX
To avoid running into the issue, ensure reliable network connectivity between the host and the NSX Manager and make sure there is no resource contention by proper capacity planning and gradual preparation for the host clusters. The below actions could help to resolve the issue:
If the issue persists, please reach out to the Broadcom Support team to assist.
If you are contacting Broadcom support about this issue, please provide the following: Reference KB "Creating and managing Broadcom support cases"
Handling Log Bundles for offline review with Broadcom support