ESXi Transport Nodes in Partial Success state with HyperBus Interface Creation Error

Products

• VMware NSX

Issue/Introduction

NSX Precheck results connectivity issue found between manager and transport nodes.

Verifying transport nodes status from the NSX UI shows the partial success state with error as:

Host configuration: Failed to create HyperBus interface. error: not ready. reason: error: failed to connect to hostd: {'fault': '[Errno 24] Too many open files'}; error: not ready. reason: error: failed to connect to hostd: {'fault': '[Errno 24] Too many open files'}; LogicalSwitch full-sync: LogicalSwitch full-sync realization query skipped

Environment

VMware NSX-T Datacenter

VMware NSX

Cause

The transport nodes are in partial success state and unable to realize the HyperBus Interface configuration.

Resolution

1. Put Host in Maintenance Mode: In vCenter, place the ESXi host into Maintenance Mode.
2. Remove from Cluster: Move the host out of its current cluster, placing it directly under the Datacenter object.
3. Uninstall NSX: Select the host from NSX UI and remove NSX using Force option.
4. Re-Add to Cluster: Once the host's NSX status changes to "Not Configured," drag it back into its original cluster. This will trigger an automatic re-installation and configuration of NSX on the host using TNP.
5. Exit Maintenance Mode: After the host has been successfully re-prepared for NSX, take it out of Maintenance Mode.

Additional Information

ESXi host configuration in partial success state with error "VTEP vmk10 failed to be applied, the vnic vmk10 exists"