SDDC Manager 9.0.x Fails to Sync or Detect Out-of-Band NSX Manager Nodes Added via NSX GUI
search cancel

SDDC Manager 9.0.x Fails to Sync or Detect Out-of-Band NSX Manager Nodes Added via NSX GUI

book

Article ID: 421778

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

Additional NSX Manager nodes were successfully provisioned via the NSX GUI, yet the SDDC inventory has not updated to include the new nodes.

  1. NSX Managers may show the scaled out nodes as 'Up' and 'Active' in the NSX UI 

Environment

SDDC Manager 9.x

Cause

The synchronization support for manually scaled out NSX Manager nodes would be available in future VCF release.

Resolution

Note: To ensure inventory synchronization, NSX Manager scale-out must be performed exclusively via SDDC Manager; Broadcom is currently updating technical documentation to formalize this limitation.

Step 1 — Deactivate the existing NSX Manager Cluster

  1. SSH into the primary NSX manager with the admin creds (The NSX Manager deployed via SDDC)
  2. From the NSX Manager console, run the following command:
    • deactivate cluster
      • The NSX Manager cluster enters a deactivated state.
      • All NSX control plane services are stopped
      • Cluster membership is dissolved in preparation for removal
  3. Power off and delete the NSX Manager VMs from vCenter
    • ONLY POWER OFF AND DELETE THE NSX MANGERS DEPLOYED OOB

 

 

Step 2 — Scaling out the NSX Manager Cluster via SDDC API (Use the GUI or CLI API)

Procedure to Scale Out NSX Manager Nodes via SDDC Manager API:

    1. Log in to the SDDC Manager UI.

    2. Navigate to the Developer Center via the home dashboard or sidebar.

    3. Select the API Categories

      1. NSX-T Cluster
        • GET /v1/nsxt-clusters
        • Copy the UUID of the NSX-T that needs to scale out.
    4. Locate the NSX-T Clusters section and select scale-out endpoint as below:

      1. NSX-T Cluster

      2. POST /v1/nsxt-clusters/{nsxt-cluster-id}/scale-out

        1. Paste the nsxt-cluster-id

        2. *EXAMPLE* In the request body field, enter YOUR NODE DETAILS the following JSON payload:
          {
            "nsxManagerSpecs": [
              {
                "name": "nsx-mgmt-2",
                "networkDetailsSpec": {
                  "ipAddress": "192.168.1.42",
                  "dnsName": "nsx-mgmt-2.gslabs.local",
                  "gateway": "192.168.1.254",
                  "subnetMask": "255.255.255.0"
                }
              },
              {
                "name": "nsx-mgmt-3",
                "networkDetailsSpec": {
                  "ipAddress": "192.168.1.43",
                  "dnsName": "nsx-mgmt-3.gslabs.local",
                  "gateway": "192.168.1.254",
                  "subnetMask": "255.255.255.0"
                }
              }
            ]
          }
          Click Execute



 

Post-validation (Full Synchronization may take up to an hour.)

  1. SDDC Manager UI
    1. NSX shows as healthy
      • Inventory now reflects 3 NSX Managers
    2. NSX UI
      • System > Appliances: 3 managers, stable cluster
         

Additional Information

Refer to: https://developer.broadcom.com/xapis/sddc-manager-api/latest/v1/nsxt-clusters/nsxt-cluster-id/scale-out/post/