Removing a Node

This section describes how to remove a node from the cluster.

Prerequisites

If the node to be removed is used in a storage pool, VBS, DR service, DPC, management cluster, or service network, you need to remove the node from all related modules first, ensuring that all services on the node have been cleared.

Procedure

On the menu bar, click and select Remove Node.
The Remove Node page is displayed.
Authenticate the nodes to be removed.
1. Select the desired nodes and click Authenticate.
  The Authentication dialog box is displayed.
2. Set Username, Password, and Password of root as required.
  
  The user name, password, and root password must be the same as those for authentication when you add a node.
3. Click OK.
  When removing a pre-installed DPC compute node, you can choose not to perform authentication. If authentication is not required, you are advised to perform the following operations to clear the DPC node:
  
  Log in to a compute node through the management IP address as user root. If you have logged in as another user, run the su - root command to switch to user root.
  
  Run the following command to check whether the clear_all_for_fs_manual.sh script exists. The following example indicates that the script exists. If the script exists, go to 3. Otherwise, go to 4.
  [root@localhost ~]# ls -l /opt/fusionstorage/deploymanager/clouda/clear_all_for_fs_manual.sh -r-x------. 1 root root 258 Apr 21 10:46 /opt/fusionstorage/deploymanager/clouda/clear_all_for_fs_manual.sh
  
  Run the following command to uninstall the node.
  cd /opt/fusionstorage/deploymanager/clouda bash clear_all_for_fs_manual.sh
  
  Run the following command to uninstall the node.
  cd /opt/fusionstorage/deploymanager/clouda bash clear_all_for_fs_node.sh all
Click Remove.
Confirm your operation as prompted.

If the duration for removing multiple nodes exceeds the session timeout duration set in the security policy and the user does not perform any operation (for example, moving the mouse) on DeviceManager, the security policy is triggered and DeviceManager automatically exits to the login page. In this case, log in to DeviceManager and remove the nodes that are not removed.