<NSX-Manager-FQDN> - NSX manager has a common name that does not match its hostname. Ensure that NSX manager has a valid certificate with its common name matching the host name.
VMware VCF 9.0.x
In VCF 9.0.x, redeploying an NSX manager in NSX is out of band and not supported.
Ensure there is a backup of the NSX manager cluster.
SDDC does not sync back from NSX in current versions, in order to get the 3 node cluster back, we now need to reduce the cluster to a single node cluster, then scale out the cluster again in SDDC manager.
Ensure the repository is working and on the remaining node.
get service install-upgradeset repository-ipget service install-upgradeget cluster configdetach node <UUID>get cluster config and get cluster status and confirm the node is released and the now 2 node cluster is healthy.detach node <UUID> get cluster config and get cluster status and confirm the node is released and the now 1 node cluster is healthy.Note: Detailed steps on for detaching a manager node can be found here Resize an NSX Manager Node
Next on the SDDC manager, we need to reduce the cluster to one node and then scale it out to three nodes.
To get the SDDC manager UUID for the NSX cluster:
GET /v1/nsxt-clusters
PUT http://<sddc-manager-ip>/inventory/nsxt/########-2373-4c74-ba99-############
With the following data:
{"id": "########-2373-4c74-ba99-############", -> This is the NSX-T cluster domain ID as seen in SDDC from the GET API above."domainIds": ["########-4109-47b2-ae1c-############" -> This is the SDDC manager domain ID.],"status": "ACTIVE","version": "9.0.1.0.24952111", -> Replace with correct NSX-T version."clusterFqdn": "<NSX-VIP-FQDN>", -> Replace with NSX cluster VIP FQDN address."nsxtClusterDetails": [{"fqdn": "NSX-Manager-FQDN>", -> Replace with the FQDN of the remaining NSX manager."vmName": "<NSX-Manager-VMName", -> Replace with NSX manager VM name."id": "########-8bd0-01df-24b0-############" -> UUID of the remaining manager.}],"shared": false -> Update based on SDDC manager GET cluster response above.}
Locate the NSX-T Clusters section and select scale-out endpoint as below:
NSX-T Cluster
POST /v1/nsxt-clusters/{nsxt-cluster-id}/scale-out
Paste the nsxt-cluster-id
*EXAMPLE* In the request body field, enter YOUR NODE DETAILS the following JSON payload:
{
"nsxManagerSpecs": [
{
"name": "<NAME>",
"networkDetailsSpec": {
"ipAddress": "192.168.1.###",
"dnsName": "<FQDN>",
"gateway": "192.168.1.###",
"subnetMask": "255.255.255.0"
}
},
{
"name": "<NAME>",
"networkDetailsSpec": {
"ipAddress": "192.168.1.###",
"dnsName": "<FQDN>",
"gateway": "192.168.1.###",
"subnetMask": "255.255.255.0"
}
}
]
}
Click Execute
Note: Above, replace FQDN, NAME and IP addressing with the correct values for the two additional NSX manager node to add to the NSX manager cluster.