Part 40– Deploying Additional NSX Managers Using the VCF 9.1 SDDC Manager API

This guide walks through the exact workflow to bring an NSX environment from zero to functional using the VCF 9.1 SDDC Manager API and the new vCenter‑driven NSX networking workflow.

Since NSX Manager is now managed by VCF Operations, most lifecycle tasks must be performed from VCF Ops, not the NSX UI.

Log in to vCFOps > Developer Center → API & SDKs

Search for NSX and Open the GET section

Run GET NSXT Cluster.

This returns the NSX‑T cluster information. Copy the cluster ID — you’ll need it for scaling out the NSX Manager cluster.

In the same NNSX API section, go to: POST – NSXT Scale Out

Paste the cluster ID into the required field.

In the request body, provide the details of the new NSX Managers. Remove all IPv6 fields entirely — do not set them to empty values.

Example Request Body

JavaScript
{
  "nsxManagerSpecs": [
    {
      "name": "vcf9-nsx02",
      "networkDetailsSpec": {
        "dnsName": "vcf9-nsx02.ash.local",
        "gateway": "172.16.11.253",
        "ipAddress": "172.16.11.91",
        "subnetMask": "255.255.255.0"
      }
    },
    {
      "name": "vcf9-nsx03",
      "networkDetailsSpec": {
        "dnsName": "vcf9-nsx03.ash.local",
        "gateway": "172.16.11.253",
        "ipAddress": "172.16.11.92",
        "subnetMask": "255.255.255.0"
      }
    }
  ]
}

Click Execute and The task will show as In Progress


Monitor the Tasks pane

Deployment takes ~20 minutes

Once complete, all NSX Managers are online.

Configure NSX Networking via vCenter

Prior to VCF 9.1, this had to be done in the NSX UI. Now, NSX networking, transit gateways, and connectivity can be configured directly from vCenter.

Reference guide: https://vmanalyst.com/nsx-lab-in-5-minutes-the-lightning-setup-guide/

In vCenter, open Setup Network Connectivity

Set Span = Centralized (default is “All”)

Validate all prerequisites

Enter an Edge Cluster Name. Select Large deployment size (required for future Supervisor roles)

Deploy the first Edge Node (North‑South routing) Edge01 IP: 172.16.11.193

Uncheck Use host overlay network .. Ensure pNICs alternate Active/Standby (auto‑populated).. Add esx‑tep‑pool

Configure Edge TEP

Choose range: 172.16.34.101–172.16.34.130

Review → Apply

Choose the IP pool as give the tep vlan

Review and Click Apply

Click Next to Continue

Enter a T0 Gateway Name. Mode: Standby (Active/Active not supported for Supervisor + VPC) . Choose Routing: BGP and Local AS: 65000 .

Configure uplinks for each Edge Node:

Edge01

  • Right uplink → VLAN 2712
  • Left uplink → VLAN 2711

Edge02

  • Right uplink → VLAN 2712
  • Left uplink → VLAN 2711

Configure VPC IP Blocks

You will use /16 CIDRs for VPC connectivity:

PurposeBlock
VPC External Block 110.10.0.0/16
VPC External Block 210.20.0.0/16
Transit Gateway Block 110.30.0.0/16
Transit Gateway Block 210.40.0.0/16

Create VPC External IP Blocks

Click the three dots → Create New

Enter the CIDR

Create Transit Gateway IP Blocks

Repeat the same process

Enter the CIDR

Clck Next to Continue

Click Deploy

NSX is now fully configured.

(Visited 57 times, 1 visits today)

By Ash Thomas

Ash Thomas is a seasoned IT professional with extensive experience as a technical expert, complemented by a keen interest in blockchain technology.