Tire-1 gateways in a failed state in NSX Federation with error "federationConfig"
search cancel

Tire-1 gateways in a failed state in NSX Federation with error "federationConfig"

book

Article ID: 413542

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • The T1 gateways are in a failed state on both GM and LM NSX UI with error "federationConfig"



  • If the path for these gateways is copied from "Copy to Clipboard" option on NSX UI, the UUID of the gateway gets copied instead of the user-friendly name configured on UI.
  • If any config change is made on these gateways, the status changes to "In Progress" and remains stuck.
  • Below logs can be observed on the NSX Manager:

    2025-09-01T08:41:50.005Z INFO INTENT-PROCESSOR-CONSOLIDATED-SERVICE-1 ConsolidatedRealizedStateServiceImpl 5175 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated consolidated state for intentPath:/global-infra/tier-1s/######-####-4768-####-###### to:ERROR
    2025-09-01T08:41:50.085Z INFO UfoDelayedIndexer-0 DirtyObjectMarkerService 5175 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Intent version and GPRR intent version dont match: setting publish status to unrealized

Environment

VMware NSX

Cause

The Tier1 span entry in Corfu database has a “service” property, but the corresponding federation config span entry does not have “service” or not the same value with the Tier1 span.

Resolution

Collect the below details and open a case with Broadcom Support Team:

  1. Output of the below command from Global Manager and Local manager CLI:
    /opt/vmware/bin/corfu_tool_runner.py -n nsx -o showTable -t Span > Span.txt
  2. Global and Local manager support bundles