Log in to the CLI (or CLI shell) and enter the commands shown as below.
Ensure that you specify the host IP addresses of theAvi Load Balancer Controller nodes instead of the IP addresses shown as below.
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-2 Removed nodes with name=node-2 : cluster:nodes> save : cluster> no nodes name node-3 Removed nodes with name=node-3 : cluster:nodes> save : cluster> save
Configuring the cluster with the Controller nodes at [10.10.25.81’].
If you add or remove nodes from the cluster, you need to bring down this Controller and then spin up the Controller up with the new configuration.
Waiting for the cluster to be ready... Controller is ready.
After saving,
The cluster is dismantled and recovered into a single node.
Each follower is re-imaged into its default state with no configuration and no access to the leader.
The leader holds the configuration. The SEs continue to connect to the leader.
For more information about the transition process, including descriptions of the status messages that appear, see Clustering Patched Controllers.
During the transition from a cluster to a single node, the REST API will be unavailable for around two minutes.
