NSX host validation error "9779: TransportNode configuration has an invalid TransportZone Profile TransportZoneProfile/<UUID>. Please update TransportNode with a valid profile ID".
search cancel

NSX host validation error "9779: TransportNode configuration has an invalid TransportZone Profile TransportZoneProfile/<UUID>. Please update TransportNode with a valid profile ID".

book

Article ID: 432202

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • NSX may have been recently upgraded to 4.x.
  • NSX Transport Node (Host or Edge) status is 'Unknown' or NSX configuration shows 'Validation Errors' in the NSX UI.
  • Clicking on 'Validation Errors' for a Transport Node in the NSX UI displays an error similar to the following:
    "9779: TransportNode configuration has an invalid TransportZone Profile TransportZoneProfile/<UUID>. Please update TransportNode with a valid profile ID".   

Environment

VMware NSX 4.x

Cause

The status of the Transport Nodes (TNs) is unknown because the referenced Transport Zone Profile (TZP) does not exist, yet a stale reference to the profile remains on the Transport Nodes.

Resolution

If an ESXi host displays a Failed or Sync Error status, manually trigger a Re-sync of the Transport Node directly from the NSX Manager UI. This action bypasses the default Auto-Rectifier wait time and forces an immediate synchronization.

If an ESXi host encounters a Validation Error during re-addition to a cluster, perform a "No-Operation" update on the associated Transport Node Profile (TNP). To do this, edit the TNP and click Save without making any configuration changes. This action forces a global refresh of the profile across all associated hosts.

You can apply the above steps after executing the remediation script as detailed in KB: NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors".

If the issue persists after performing these steps, open a support case with Broadcom support and select NSX as the product.
For more information, see Creating and managing Broadcom support cases.

Additional Information

Reference similar KB: NSX Host or Edge Transport Nodes have a status of "Unknown" and Tunnels are "Not Available" or "Validation Errors".

If you are contacting Broadcom support about this issue, please provide the following:

  • NSX Manager support bundles.
  • ESXi host support bundles for hosts that are getting validation errors.
  • Provide the corfu table dumps as shown below:
    1. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t PolicyTransportZoneProfile -o showTable > /image/PolicyTransportZoneProfile.txt
2. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t InternalTransportZoneProfile -o showTable > /image/InternalTransportZoneProfile.txt
3. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t PolicyTransportZone -o showTable > /image/PolicyTransportZone.txt
4. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t InternalTransportZone -o showTable > /image/InternalTransportZone.txt
5. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t TransportNodeProfile -o showTable > /image/TransportNodeProfile.txt
6. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t HostTransportNode -o showTable > /image/HostTransportNode.txt
7. /opt/vmware/bin/corfu_tool_runner.py --tool corfu-editor -n nsx -t EdgeTransportNode -o showTable > /image/EdgeTransportNode.txt
  • Text of any error messages seen in NSX GUI or command lines pertinent to the investigation.

Handling Log Bundles for offline review with Broadcom support:

Powered by Wolken Software