T1 gateway status is down but all status for transport nodes shows successful after NSX Edge maintenance mode
search cancel

T1 gateway status is down but all status for transport nodes shows successful after NSX Edge maintenance mode

book

Article ID: 416487

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

When the status of the T1 gateway shows down, and status of other components are Successful/green, check the realization status of the Edges using the process below.

  • From NSX Manager logs nsxapi.log will show 

Updated GPRR /infra/realized-state/enforcement-points/default/tier-0-logical-routers/<Tier1> with operational status: RealizedOperationalStatus{ msgOrBuilder=operation_status: STATUS_RED

 

  • From an API call to the NSX Manager

curl -l -k -u 'admin' -H 'Content-Type:application/json' -X GET https://localhost/policy/api/v1/infra/realized-state/realized-entities?intent_path=<path_to_T1_object_copied_from_NSX_UI>

    • Then look for:
      "runtime_status": "DOWN"
      "operational_status": "STATUS_RED",

Environment

VMware NSX

Cause

The realization status of the Edges can be out of sync between the nodes after a maintenance mode operation.

To check the realization status run the below commands from the NSX Manager CLI

  1. Run the below command and take note of the <UUID of TN>
    get nodes
  2. Run
    get data with receiver <UUID of TN>

Verify the status of the node, If status of node is 

status: unknown 

The T1 gateway will show as status "Down"

Resolution

Once a node is in this state an update can be done to the configuration to force realization. Edit the settings of the T1 and change the affected setting for a non disruptive setting. 

This can be a description change or change to the affected setting. After the "realization_api": it will show where the change needs to be made.

/routing/advertisement

In this example routing was the unknown. So changing a routing setting that was non disruptive and saving will realize the Edge.