Transport Nodes showing Validation errors "601: The object HostTransportNode//infra/sites/default/enforcement-points/default/host-transport-nodes/UUID is already present in the system"
search cancel

Transport Nodes showing Validation errors "601: The object HostTransportNode//infra/sites/default/enforcement-points/default/host-transport-nodes/UUID is already present in the system"

book

Article ID: 424857

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

ESXi host appears in a Validation Error state in NSX UI with the following error:

Validation errors "601: The object HostTransportNode//infra/sites/default/enforcement-points/default/host-transport-nodes/UUID is already present in the system"


When attempting to reconfigure NSX on the affected host, the operation fails with the same validation error.

This validation error may be encountered after removing stale host entries using the prepare_host_transport_nodes_delete_data.py script in environments where hosts are added through SDDC.

Environment

VMware NSX 4.2.3.1

Cause

When an ESXi host is removed directly from vCenter without first removing NSX, it can result in entries for that host to remain in the NSX database.

Resolution

Workaround:

  • Put the host in MM
  • Move the host outside of the cluster to the Datacenter Level
  • Open Other Nodes in NSX UI and confirm the host shows "Not Configured" status
  • Move the host back into cluster
  • NSX configuration will initialize again and configure NSX successfully.

Additional Information

Similar issue: Adding host to NSX prepared cluster through SDDC manager gets stuck at "Prepare Transport Node Collection"