Health checks for NSX-T on vLCM cluster fails with "Failed to run health checks for NSX-T on <NSXT_MP_NAME>" error.

Products

• VMware NSX

Issue/Introduction

Issue can be identify in VCenter server cluster updates

 

Log snippets or APIs to identify the issue:

1. vmware-vum-server logs from VC:
   
   2025-05-13T##:##:##:## error vmware-vum-server[15697] [Originator@6876 sub=EHP] NSX-T node with address UC-NSX.FQDN.### not found
   2025-05-13T##:##:##:## error vmware-vum-server[15697] [Originator@6876 sub=EHP] Caught exception while finding Nsxt Upgrade Coordinator: NSX-T node with address UC-NSX.FQDN.### not found
   2025-05-13T##:##:##:## info vmware-vum-server[12429] [Originator@6876 sub=EHP] [domain-c#####] [com.vmware.vcIntegrity.lifecycle.health.internal.external_provider] returned status: NOT_OK
   2025-05-13T##:##:##:## info vmware-vum-server[12429] [Originator@6876 sub=EHP] Entity [domain-c#####] health status is: NOT_OK
   
   
   
2. Follow below steps to check the uc-state configuration is correct or not.

• • 1. Get the uc-state details using "GET https://<MP_IP>/api/v1/uc-state" API. The "active_upgrade_coordinator_ip_address" field should show IP address and not FQDN. If FQDN is present, then we need to follow workaround to fix it.
       
       
    2. We can check the uc-state config using CLI as well. Execute "get service install-upgrade" CLI. The "enabled_on" field will should show IP address and not FQDN. If FQDN is present, then we need to follow workaround to fix it.
       
       
       

Environment

VMware NSX 

Resolution

Workaround steps to update the uc-state:

1. Get the IP corresponding to FQDN present in the uc-state configuration.
   •  To execute the below CLI, login to the NSX-T Manager node as a admin user.
       - CLI: set repository-ip
      
   • - We can update the uc-state using API as well. Execute below API to update the UC state.
       - API request: PUT https://<MP_IP>/api/v1/node/services/install-upgrade/uc-state
       - API Request body:
      {
   "update_uc_state_properties": true
 }
     
     
2. Verify that the uc-state is updated correctly using below CLI or API.
   • CLI: get service install-upgrade
   • API: GET https://<MP_IP>/api/v1/uc-state