Error: "Failed to connect interface of edge gateway <edge_name> to organization VDC network <network_name>" when attempting to create an Organization VDC Network

Products

• VMware Cloud Director

Issue/Introduction

• Attempting to create an Organization VDC Network in the Cloud Director Tenant Portal fails with an error of the form:

"Failed to connect interface of edge gateway <edge_name> to organization VDC network <network_name> - Bad Request: Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone., error code 503108"

• The /opt/vmware/vcloud-director/logs/vcloud-container-debug.log files on the Cloud Director Cells show an error of the form:

<timestamp> | ERROR    | task-service-activity-pool-### | Interfaces                     | could not add interface  | requestId=########-####-####-####-############,request=POST https://<vcd_address>/cloudapi/1.0.0/orgVdcNetworks,requestTime=<request_time>,remoteAddress=<remote_address>,userAgent=<user_agent>,accept=application/json;version <vcd_api_version> vcd=########-####-####-####-############,task=########-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############)
com.vmware.vcloud.common.network.VsmException: Bad Request: Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone., error code 503108

• The /opt/vmware/vcloud-director/logs/networking-wire.log files on the Cloud Director Cells show a 400 Bad Request response from NSX Manager to Cloud Director of the form:

<timestamp> | TRACE    | task-service-activity-pool-107709 | VApiLoggingRequestExecutorFactory | Response Body: {
  "httpStatus" : "BAD_REQUEST",
  "error_code" : 503108,
  "module_name" : "Policy",
  "error_message" : "Tier0, Tier1 and connected overlay segments should belong to same overlay transport zone."
} | requestId=########-####-####-####-############,request=POST https://<vcd_address>/cloudapi/1.0.0/orgVdcNetworks,requestTime=<request_time>,remoteAddress=<remote_address>,userAgent=<user_agent>,accept=application/json;version <vcd_api_version> vcd=########-####-####-####-############,task=########-####-####-####-############ activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-############)

Environment

VMware Cloud Director 10.6.x

VMware NSX 4.x

Cause

This issue occurs when the Network Pool assigned to the Organization VDC is backed by a different NSX Overlay Transport Zone than the NSX Overlay Transport Zone used for Segments attached to the Tier-0 or VRF that backs the Provider Gateway to which the Tier-1 Organization Edge Gateway is connected.
NSX will not allow Cloud Director to request a mix of different Overlay Transport Zones between the Tier-0/VRF and the Tier-1.

Resolution

To resolve this issue ensure that the Network Pool used by the Organization VDC where the Edge Gateway is located is backed by the same Overlay Transport Zone as the NSX Segments connected to the Tier-0 or VRF that backs the Provider Gateway to which the Tier-1 Organization Edge Gateway is connected.

To review the connected Overlay type Segments log into the NSX Manager UI and navigate to Networking > Tier-0 Gateways > expand the Tier-0/VRF > expand Interfaces and GRE Tunnels > select External and Service Interfaces.

To review the Overlay Transport Zone of the Segments open the NSX Manager UI and navigate to Networking > Segments and review the Transport Zone column.

For details on how to create a Network Pool please see the documentation, Create a Network Pool Backed by an NSX
Transport Zone in Your VMware Cloud Director.

For details on how to assign a Network Pool to an Organization VDC see the documentation, Edit the Network Settings of a VMware Cloud Director
Organization Virtual Data Center.