Unable to create uplinks and connected overlay segments on T0 gateway using the local manager.

Products

• VMware NSX

Issue/Introduction

The below error is observed when adding an uplink to any T0 gateways to overlay segment or when trying to edit an uplink:

Error: Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone. (Error code: 503108)


Logs can be found in Local manager in /var/log/proton/nsxapi.log:

2025-04-09T19:16:22.378Z ERROR http-nio-127.0.0.1-7440-exec-22 ProviderInterfaceServiceImpl 51996 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM503108" level="ERROR" reqId="5e581337-####-####-a380-42ac####9921" subcomp="manager" username="admin"] Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone /infra/sites/default/enforcement-points/default/transport-zones/1b3a2f36-####-####-a0f6-4de####c963e, but gatewat transport zone is /global-infra/sites/NSX-MGMT-NJ/enforcement-points/default/transport-zones/1b3a2f36-####-####-a0f6-4de####963e

2025-04-24T17:48:11.959Z INFO http-nio-127.0.0.1-7440-exec-387 NsxBaseRestController 88783 SYSTEM [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Error in API /nsxapi/api/v1/infra/tier-0s/####-BWI1-T0/locale-services/default/interfaces/####-BWI1-transit-1 caused by exception com.vmware.nsx.management.policy.connectivity.common.exceptions.ConnectivityIntentException: {"moduleName":"Policy","errorCode":503108,"errorMessage":"Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone."}

2025-04-24T17:48:11.960Z INFO http-nio-127.0.0.1-7440-exec-387 NsxBaseRestController 88783 SYSTEM [nsx@6876 audit="true" comp="nsx-manager" level="INFO" subcomp="manager"] UserName:'####' ModuleName:'Policy' Operation:'PUT@/api/v1/infra/tier-0s/#####-BWI1-T0/locale-services/default/interfaces/####-BWI1-transit-1' Operation status: 'failure' Error: Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone.

 

Environment

4.1.2.3 and prior
4.2.2.0 and prior
9.0

Cause

You will be unable to edit the uplinks because the transport zones do not match. This is because the two paths that are being
checked are infra and global-infra.

 

transportZonePath": "/infra/sites/default/enforcement-points/default/transport-zones/####

transport_zone_path": "/global-infra/sites/####/enforcement-points/default/transport-zones/###

Resolution

The issue is fixed in the below versions

• 4.1.2.4
• 4.2.2.1
• 4.2.3
• 9.0.1

 

Additional Information

Steps to reproduce the issue:

1. Deploy NSX, this will create system-created default overlay TZ.
2. Create TZ on NSX with SDDC Manager's domain creation workflow. This will change the default overlay TZ to a new one created by SDDC Manager.
3. Onboard the site to GM. GM will discover the site and recreate a /global-infra overlay TZ with a different path but same internal key as the TZ created in step 2.
4. Deploy edge nodes and edge cluster on LM
5. Add the new overlay default TZ (created by SDDC-M) to edge nodes in one of the clusters.
6. Create segment on LM with default TZ created by SDDC Manager
7. Create Tier 0 on the edge cluster
8. Create External interface on Tier 0 with one of the edge nodes in the cluster and connected to the segment created in step 5.

Step 8 will throw error:
Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone. (Error code: 503108)