Error "Cannot connect Edge Gateway urn:vcloud:gateway:" when enabling "Allow Non-Distributed Routing" on VMware Cloud Director
search cancel

Error "Cannot connect Edge Gateway urn:vcloud:gateway:" when enabling "Allow Non-Distributed Routing" on VMware Cloud Director

book

Article ID: 405368

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

When attempting to enable the Allow Non-Distributed Routing toggle on a VMware Cloud Director (VCD) Edge Gateway connected to an NSX-T Provider Gateway, the operation fails.

The following error message is displayed:

Error "Cannot connect Edge Gateway urn:vcloud:gateway:{{id}} with default Static Route CIDR 0.0.0.0/0 to Provider Gateway."

  • The affected VCD Edge Gateway is connected to an NSX-T Provider Gateway.

Environment

  • VMware Cloud Director 10.x

  • NSX-T Data Center

Cause

This error occurs because a default static route (with a destination CIDR of 0.0.0.0/0) is already configured on the Edge Gateway. This pre-existing manual route conflicts with the routing changes VCD attempts to make when enabling the "Allow Non-Distributed Routing" feature.

Resolution

To resolve this issue, you must remove the conflicting default static route before enabling the "Allow Non-Distributed Routing" option.

Part 1: Remove the Default Static Route

  1. Log in to the VMware Cloud Director Tenant Portal.

  2. From the top navigation bar, select Networking and then click Edge Gateways.

  3. Click the name of the affected Edge Gateway to open its configuration settings.

  4. Navigate to the Routing tab and then select the Static Routes sub-tab.

  5. Locate the static route in the list where the Network CIDR is 0.0.0.0/0.

  6. Select the checkbox next to this route and click DELETE.

  7. Confirm the deletion when prompted.

Part 2: Enable "Allow Non-Distributed Routing"

  1. While still on the configuration page for the same Edge Gateway, navigate back to the General tab.

  2. Locate the Allow Non-Distributed Routing option and click the toggle to set it to the "Enabled" position.

  3. Click SAVE CHANGES.

The setting should now be enabled successfully without any errors.