NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors"
search cancel

NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors"

book

Article ID: 324194

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX may have been recently upgraded to 4.x.
  • NSX Transport Nodes (Host or Edge) status is 'Unknown' or NSX configuration shows 'Validation Errors' in the NSX UI or NSX API 

    To get a list of all Transport Nodes and their IDs:

    GET https://<NSX_MANAGER>/api/v1/transport-nodes/

    To get the status of a specific Transport Node:

    GET https://<NSX_MANAGER>/api/v1/transport-nodes/<tn-id>/status
  • Clicking on Transport Node 'Validation Errors' in the NSX UI shows errors similar to the below:

    600: The requested object: <TransportZoneProfile-UUID> could not be found. Object identifiers are case sensitive."
  • NSX Transport Nodes tunnel status may show 'Not Available' in the NSX UI.




  • No data plane impact has been reported.
  • NSX Manager log /var/log/proton/nsxapi.log has a log entry similar to the below:

    "The requested object : TransportZoneProfile/<TransportZoneProfile-UUID> could not be found."
  • The above Transport Zone Profile UUID is not present when queried via API:

    GET https://<NSX_MANAGER>/api/v1/transportzone-profiles?include_system_owned=true
  • The above Transport Zone Profile UUID cannot be found in NSX or VC global search.
  • The NSX manager log /var/log/search/elasticsearch_index_indexing_slowlog.log has a log similar to example:

    [{"resource_type":"BfdHealthMonitoringProfile","profile_id":"UUID_in_Validation_Error"}]}],"vmk_install_migration":[],"pnics_uninstall_migration":[],"vmk_uninstall_migration":[],"not_ready":false}],"resource_type":"StandardHost]

Environment

  • VMware NSX-T Data Center
  • VMware NSX

Cause

The status of the Transport Nodes (TNs) are unknown because the Transport-Zone Profile (TZP) which is being referenced does not exist. The reasons why the referenced Transport-Zone Profile (TZP) is not present in the system can be due to multiple reasons:

  • In previous versions of NSX, it was possible in policy mode to update or delete a Transport-Zone Profile (TZP), even if it was in use by a Transport Nodes(TN) or Transport-Node Profile(TNP).
  • In some cases, Aria Operations for Networks creates a Transport-Zone Profile (TZP) and when Aria Operations for Networks is removed, Transport-Zone Profile(TZP) are deleted.  Validation has been added in newer versions to avoid this issue.

Resolution

To resolve this issue for ESXi hosts and Edge nodes, open a support case with Broadcom support selecting NSX as the product.
For more information, see Creating and managing Broadcom support cases.

Attachments

cleanup_stale_tzp_references_v2.py get_app