vCD Network Advertisement Fails with NSX Error 10202: Static Route Next Hop IP is LRPort

Products

• VMware NSX
• VMware Cloud Director

Issue/Introduction

When configuring VMware Cloud Director (vCD) networks with route advertisement enabled, you encounter the following symptoms:

• One or more VDC networks fail to be advertised to the transit gateway or upstream routers.
• The associated segment in NSX-T Manager shows a **Failed** state.
• NSX realization error logs (`/var/log/proton/nsxapi.log`) contain the following error code:
      `[error_code=10202, module_name=ROUTING, error_message='[Routing] Static route [UUID] next hop IP is LRPort [UUID] IP.']`.
• On NSX UI, the status of the segment and associated Tier-1 is showing in Failed state.
• In the vCD Tenant Portal, a static route exists on the Edge Gateway where the next-hop IP is assigned to the gateway's own interface or a Logical Router Port (LRPort).

Environment

VMware Cloud Director 10.6.x

VMware NSX

Cause

The issue is caused by an "invalid static route configuration" on the Tier-1 (T1) Gateway. Specifically, a static route has been created where the "next-hop IP address" matches the IP address of a Logical Router Port (LRPort) on the same gateway. This creates a routing loop or a realization conflict, preventing the NSX management plane from successfully pushing the configuration to the data plane.

Resolution

To resolve the realization error and enable route advertisement, you must remove or correct the conflicting static route.

Identify the Conflicting Route

1.  Log in to the **NSX Manager UI**.
2.  Navigate to **Networking** > **Connectivity** > **Tier-1 Gateways**.
3.  Select the Tier-1 Gateway associated with the failing vCD network.
4.  Expand **Static Routes** and identify any routes where the next-hop IP belongs to the local gateway interfaces (e.g., the gateway IP of one of your VDC networks).

Remove the Invalid Configuration

This command will make changes to your environment. Review it carefully before running.

1.  In the **vCD Tenant Portal** (or NSX Manager), navigate to the **Static Routes** section of the Edge Gateway.
2.  **Delete** the static route that uses the gateway's own interface IP as the next hop.
3.  Alternatively, if the route is required, update the **Next Hop** to a valid IP address that exists behind a virtual appliance (e.g., a Fortigate or other NVA) within the VDC, rather than the gateway itself.

Verify Realization

1.  Return to the **NSX Manager UI**.
2.  Navigate to **Networking** > **Segments**.
3.  Verify that the status for the affected segment has changed from **Failed** to **Success** or **Realized**.
4.  Confirm that the network is now being advertised to the transit gateway.