How to remove Intelligent Sandbox clusters

Primary node is active - When the primary node is active, administrator logs on to Load Balancing page of Intelligent Sandbox. The administrator then remove all other nodes such as Backup or Secondary nodes, one by one. Once all nodes are removed except the primary node, the administrator can remove the primary node.

Backup node is active (Active Primary) - In this case, the administrator first logs on to the Backup node, from the Load Balancing page of Intelligent Sandbox, then removes all node from the cluster in the following order:

If the administrator logs on to the configured primary node, the nodes cannot be removed directly from the Load Balancing page. This is because the configured primary node is not serving as Active Primary node and since a cluster cannot be created without a primary node configured. After removing Backup node from cluster if primary node is active, primary node takes the active role, since the Backup node is not active. Now, to remove a cluster, primary node is removed followed by removal of Backup node.

Remove Node from Active-Primary - This option facilitates removal of secondary or backup node from Active Primary. If the target node is up at the time of removal, the node changes itself to standalone state and Active Primary removes the entry of the node from the cluster. If the target node is down at the time of removal, the entry of the target node is removed from the cluster by Active Primary. Once that node comes up, the administrator needs to log on to the removed node and do a manual cluster withdraw in Load Balancing page of Intelligent Sandbox, using Withdraw from Cluster button. The role of removed node is then changed to standalone.

Withdraw from Cluster at Secondary or Backup Node - This option is active for all secondary or backup nodes to withdraw that particular node from Load Balancing.

CLI command: clearlbconfig - This command is used to remove a cluster using CLI command prompt. It is permitted to run at all nodes (Primary, Backup, or Secondary). It wipes out all cluster-related configurations from that node and makes it a standalone box. This command can be used in scenarios where a typical method of removing a node (Remove Node or Withdraw From Cluster) does not remove that node from cluster. When you execute the clearlbconfig command on Active or Primary nodes, you must also execute the command on all other nodes in the cluster.

If Backup is not serving as Active Primary - The administrator deletes the previously configured Backup node and adds a new one.

If Backup is serving as Active Primary - The administrator removes the cluster and reconfigures Intelligent Sandbox nodes with the new roles.