Preparing ESXi host with NSX fails with an error "Failed to install software on host. Failed to install software on host. Time out waiting for host to join NSX Manager"

Products

• VMware NSX

Issue/Introduction

• You're running NSX-T Data Center 4.x or later.
• Preparing ESXi host with NSX fails with an error "Failed to install software on host. Failed to install software on host. Time out waiting for host to join NSX Manager".
• Attempting to resolve the installation from NSX UI and it fails with error "Failed to install software on host. Time out waiting for host to join NSX Manager".
• Host will have all the NSX VIBs but still the preparation fails.
• You may observe certificate related error logs in /var/run/log/nsx-syslog.log:
  2026-01-09T08:40:30.971Z In (182) nsx-proxy [5287691] : NSX 5287691 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="5xxxxx" level="INFO"] RpcConnection [248 Negotiating to ssl://10.x.x.x: 1235 0] Sending connection
settings version: 2 endpoint_id: "123##########" service: "vmware.nsx. cli.MetricsCliService" service: "vmware.nsx. cli. ProxyConfigCliService" service: "vmware.nsx.messaging. MessagingClientService" service: "vmware
nsx.rpc. RpcCliService" service: "vmware.nsx. daemon. DaemonHealth" supported_version: 1 supported_version: 2 supported_version: 3 flow_control_support: 1 trace_support: 1
2026-01-09T08:40:30.971Z In(182) nsx-proxy[5287691] : NSX 5287691 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="5xxxxx" level="INFO"] RpcConnection [248 Negotiating to ssl://10.x.x.x:1235 0] ReadStart
2026-01-09T08:40:30.972Z Wa (180) nsx-proxy[5287691]: NSX 5287691 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-net" tid="5xxxxxx" level="WARNING"] StreamConnection [248 Connected to ssl://10.x.x.x:1235 sid: 248]
  
  
  
  

Environment

VMware NSX-T Data Center 3.x
VMware NSX 4.x

Cause

• Transport node UUID on the Host and NSX manager is different , it's mainly because of the execution of the deleting the nsx vibs is not done properly.
• CLI validation confirms a mismatch between the Host's local UUID and the UUID recorded for that host within the NSX Manager:
  Example from Host :

host-1> get node-uuid
uuid: 123########
  
  From NSX manager UI :
  Fabric > hosts> select the issue host > click on 3 dots and copy the id to clipboard.
UUID : fdc#####
• This difference in the UUID locally and on the NSX manager is causing the issue and both controller and Manager connectivity is down on the Host.

Resolution

• Steps to resolve the issue 
  

  Preparation: Place the affected host into Maintenance Mode.

  Local VIB Removal: Since connectivity issues prevent removal via the NSX Manager UI, log into the host CLI and execute: del nsx

  Verification: Confirm the VIBs have been successfully removed by running: esxcli software vib list | grep nsx Note: The command should return no output.

  Troubleshooting: If you encounter errors during uninstallation, refer to Broadcom NSX VIBs are not removed from an ESXi host

  Manager Cleanup: From the NSX Manager UI, perform a Force Remove on the host. Wait for the host to appear in the "Standalone" or "Other Hosts" section.

  Reinstallation: Re-install NSX on the host or move the host back into the prepared cluster to trigger an automated VIB push.

  Final Validation: Once the installation is complete, verify connectivity by running the following commands in the host CLI: nsxcli -c get controllers / nsxcli -c get managers

  Completion: Exit Maintenance Mode.

Additional Information

• If the above errors are not there and UUID is same in local host and NSX manager please refer to the below kb's to troubleshoot the error with similar error code:
  
   Preparing ESXi host with NSX fails with an error "Waiting for connection to Managers"
  
  NSX Transport Nodes ( Edge/ESXi host) show "Down/Degraded" due to DNS issue
  
  
• Impact/Risks:
  
  Inability to prepare ESXi host as NSX-T Transport Node.