NSX transport node errors - The requested object : TransportZone/<> could not be found. Object identifiers are case sensitive.

Products

• VMware NSX

Issue/Introduction

Host transport node configuration may fail. The NSX Manager UI or API reports that a specific Transport Zone object identifier cannot be found, preventing the host from reaching a "Success" state.

 GET API '/api/v1/transport-nodes/state' 

  "/nsxapi/api/v1/transport-nodes/state": {
    "result_count": 8,
    "results": [
      {
        "details": [
          {
            "failure_code": 8804,
            "failure_message": " Host configuration: Failed to handle the HostConfig reply message from host. [TN=TransportNode/########################]. Reason: The requested object : TransportZone/<abc> could not be found. Object identifiers are case sensitive.",
            "state": "failed",
            "sub_system_id": "##############",
            "sub_system_type": "Host"

Environment

VMware NSX 4.2.x, VCF NSX 9.0

Cause

The issue is caused by the creation of duplicate security-only transport zones for a single vSphere Distributed Switch. This results in a mismatch where the internal key values in PolicyTransportZone entries do not align with the actual UUID of the transport zone referenced by the TransportNodeProfile (TNP). When the host attempts to acknowledge the configuration, it references an identifier that the NSX Manager cannot resolve due to this database inconsistency.

Resolution

Workaround:

A Python-based cleanup script is attached to this KB to reconcile duplicate entries and synchronize internal keys. Please refer to the instructions in the README file before running the script.

Note: This script is intended only for NSX 4.2.x environments. If you need to perform this workaround in a VCF NSX 9.x environment, please contact Broadcom Support. For more information, see Creating and managing Broadcom support cases.