In case of an NSX Controller failure, you may still have two controllers that are working. The cluster majority is maintained, and the control plane continues to function. We recommend replace the controller when one of the controllers encounter catastrophic, unrecoverable errors or when one of the controller VMs become inaccessible and cannot be fixed. You must first delete the broken controller, and then deploy a new controller.
Before you begin
Verify if you can resolve the issue as described in Troubleshooting Controller Cluster.
About this task
- Log in to the vSphere Web Client.
- From Networking & Security, click Installation > Management.
- In the NSX Controller nodes section, click the affected controller and take screen shots/print-screens of the NSX Controller Details screen or write down the configuration information for later reference.
- Deploy a new NSX Controller node by clicking the Add Node (+) icon.
- In the Add Controller dialog box, select the datacenter on which you are adding the nodes, and configure the controller settings.
- Select the appropriate cluster.
- Select a Host in the cluster and storage.
- Select the distributed port-group.
- Select the IP pool from which IP addresses are to be assigned to the node.
- Click OK, wait for installation to complete, and ensure the node have a status of Normal.
- Resynchronize the controller state by clicking Actions > Update Controller State.
Update Controller State pushes the current VXLAN and Distributed Logical Router configuration (including Universal Objects in a Cross-vCenter NSX deployment) from NSX Manager to the controller cluster.
What to do next
For more information about deploying controller cluster, refer to the NSX Administration Guide.
For more information about how to delete the affected controller, refer to Delete an NSX Controller.