Getting error "TransportNode configuration has an invalid TransportZone Profile TransportZoneProfile/. Please update Transport Node with a valid profile ID. (Error code: 9779)" when trying to enable RTEP on an Edge cluster.

Products

• VMware NSX

Issue/Introduction

Symptoms

• NSX Transport Node (Host or Edge) status is Unknown or Not Available.

• NSX configuration shows **Validation Errors** in the NSX UI.
• Error message: 9779: TransportNode configuration has an invalid TransportZone Profile TransportZoneProfile/<UUID>. Please update TransportNode with a valid profile ID.
• NSX Manager logs (/var/log/proton/nsxapi.log) show: The requested object : TransportZoneProfile/<UUID> could not be found.

Environment

VMware NSX version prior to 4.2.2

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 in the database.

Resolution

Prerequisites:

1. Take a fresh SFTP/FTP-based backup of the NSX Manager.
2. Ensure you have root access to the NSX Manager nodes.

Automated Script Cleanup

This issue is resolved by running the cleanup_stale_tzp_references_v2.py script available in KB324194.

1. Copy the script to /root/script-based-cleanup/ on one NSX Manager node.

2. Stop the proton service on **all three** Manager nodes:
   service proton stop

3. Run the precheck to identify stale references:
   python cleanup_stale_tzp_references_v2.py --precheck

4. If stale references are found (e.g., in Edge Transport Nodes), apply the fix:
   python cleanup_stale_tzp_references_v2.py --apply

5. Start the proton service on **all three** Manager nodes:
   service proton start

6. Perform a search resync from the NSX CLI on all nodes:
   start search resync policy
   start search resync manager

This issue is a known defect. Fixed in release NSX 4.2.2 and higher. You can download the latest version from the [Broadcom Support Portal](https://support.broadcom.com/).