NSX Cluster Status Degraded Due to Stale Entries After NSX Manager Removal
search cancel

NSX Cluster Status Degraded Due to Stale Entries After NSX Manager Removal

book

Article ID: 451887

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • After removing an NSX manager from the NSX UI, and redeploying the NSX managers from the SDDC manager by following the KB article (NSX Manager nodes added out-of-band do not sync in SDDC Manager (VCF) 9.0.x) the NSX cluster may display a "Degraded" status in the NSX UI.
  • From the NSX UI all available NSX managers services are up.
  • CLI output for the command "get cluster status" shows the cluster is "STABLE".
  • This behavior occurs when stale entries for the deleted manager remain in the cluster database.

Environment

VMware NSX 9.x

Cause

The cluster reports "Degraded" because stale configuration entries for a removed NSX manager persist in the ShaMetric record within the Corfu database.

Resolution

Gather the following information and open a support case with Broadcom.

  1. Log in to the NSX manager via SSH as root.
  2. Run the following API command using the any API tool to identify the stale entries:
    curl -k -u admin https://localhost/api/v1/systemhealth-extended/management-cluster
  3. Collect the support bundle.

Additional Information

Collect Support Bundles
Creating and managing Broadcom cases