NSX Transport Node Installation Fails around 80%

Products

• VMware NSX

Issue/Introduction

• When adding an ESXi host Transport Node to an NSX cluster, the configuration process stalls or fails around 80%. 
• The error message at the time of failure is shown below.

[vmk1X.X.X.X,] failed to be applied: Failed to add VTEP: {'fault': 'PlatformConfigFault', 'msg': 'An error occurred during host configuration.', 'faultMessage': ['Operation failed  diagnostics report: Unable to get node:
Not implemented']); Setting TEPHA failed with code 2:VDS not found., on dvs <DVS-Name>; Failed sending the VTEP_HA Params to DataPath on dvs

Environment

VMware NSX

 

Cause

The issue is typically caused by a desynchronization between the ESXi host's local management agents and the NSX Controller plane.

• While the Management Plane connectivity may appear "UP," the Controller Plane remains "Disconnected."
• This prevent the host from correctly identifying the Virtual Distributed Switch (VDS) context required to instantiate the VTEP, even when physical network reachability (Ports 1234/1235) is functional.

To test the port connectivity status from ESXi host to the NSX management/controller, refer to the KB --> ESXi to NSX Port Connectivity Testing

Resolution

To resolve the issue, follow the steps below:

• Enter Maintenance Mode: Place the affected ESXi host into Maintenance Mode to ensure no production impact during service restarts.

• SSH to Host: Log into the affected ESXi host via Putty or SSH as the root user.

• Verify Status: Confirm the controller disconnect by running the following command

  • get controllers

• Restart NSX Services: Execute the following commands in sequence to restart the critical host agents on the ESXi host.

  • /etc/init.d/nsx-proxy restart

  • /etc/init.d/nsx-opsagent restart

  • /etc/init.d/nsx-cfgagent restart

  • /etc/init.d/nsx-nestdb restart

• Exit Maintenance Mode: Once services have initialized, take the host out of Maintenance Mode.

• Verify in UI: Check the NSX Manager GUI and initiate the reconfiguration of the Transport node again to confirm the Transport Node status has transitioned to "Success" or "Up."