Log in to the CLI (or CLI shell) and enter the commands shown in the following example.
Note:
Ensure that you enter the host IP addresses of the NSX Advanced Load Balancer Controller nodes instead of the IP addresses shown in the example.
configure cluster Updating an existing object. Currently, the object is: +---------------+----------------------------------------------+ | Field | Value | +---------------+----------------------------------------------+ | uuid | cluster-eb01bf05-7313-4a4f-91b6-21e46d3c237d | | name | cluster-0-1 | | nodes[1] | | | name | node-1 | | ip | 10.10.25.81 | | vm_ref | EB01BF05-7313-4A4F-91B6-21E46D3C237D | | vm_mor | | | vm_hostname | node1.controller.local | | nodes[2] | | | name | node-2 | | ip | 10.10.25.82 | | vm_ref | EC123A05-7313-4A4F-91B6-21E46D3D46AF | | vm_mor | | | vm_hostname | node2.controller.local | | nodes[3] | | | name | 10.10.25.83 | | ip | 10.10.25.83 | | vm_ref | EA12C05-7313-4A4F-91B6-21E46D3E256EA | | vm_mor | | | vm_hostname | node3.controller.local | | tenant_ref | admin | +---------------+----------------------------------------------+ : cluster> no nodes name node-3 Removed nodes with name=node-3 : cluster:nodes> save : cluster> nodes name node-4 ip 10.10.25.84 Removed nodes with name=node-4 : cluster:nodes> save : cluster> save
Configuring the cluster with the Controller nodes at [u’10.10.25.81’, ‘10.10.25.82’, ‘10.10.25.84’]. If you add or remove nodes from the cluster, you should bring down this Controller and back up with the new configuration.
Waiting for the cluster to be ready... Controller is ready.
After saving,
The removed follower node is sent an API request asking it to gracefully clear its state.
Since the old follower is not always expected to clear its state, the leader will forcibly remove it if necessary.
The new follower node is added.
