Tier-1 Gateway Status Failed With Unknown Runtime Issues

Products

• VMware NSX

Issue/Introduction

Tier-1 (T1) Gateways may report a "Failed" status in the NSX UI despite the associated Transport Nodes appearing healthy (Green).
The error message typically displays "There are some unknown runtime issues." This issue commonly arises due to DHCP realization inconsistencies within the NSX management plane.

• T1 Gateway status shows "Failed".
• "There are some unknown runtime issues" error displayed in the UI.
• Transport Nodes associated with the gateway appear healthy.
• API calls to the realized-state entity for the T1 Gateway show realizationState: ERROR for the associated DHCP service.

 

Environment

VMware NSX

Cause

The T1 Gateway failure is caused by an inconsistent realization state in the Corfu database (GenericPolicyRealizedResource table), typically triggered by DHCP configuration mismatches during upgrades or segment migrations.

Resolution

Perform the following steps to trigger a re-realization of the gateway configuration:

1. Identify the affected DHCP server path using the API: GET https://<nsx-mgr>/policy/api/v1/infra/realized-state/realized-entities?intent_path=/infra/tier-1s/<T1-ID>
2. Navigate to the associated DHCP profile or segment in the NSX UI.
3. Perform a non-disruptive update (e.g., modify the Description field or adjust a DHCP range slightly).
4. Save the changes and wait 5 minutes for the management plane to re-realize the configuration.
5. If the status remains "Failed," manual intervention in the Corfu database may be required to set realizationState to REALIZED. Refer to internal runbooks for "Remediate CGW status from GPRR table" before attempting manual database edits.

Additional Information

• If the issue persists after these steps, create a new Broadcom Support Case.
• For more information on creating or managing cases, visit: Creating and Managing Broadcom