Deleting a node from a system by using the CLI
You can use the command-line interface (CLI) to remove a node from a system.
Before you begin
By default, the rmnode command flushes the cache on the specified node before taking the node offline. When operating in a degraded state, the system ensures that data loss does not occur as a result of deleting the only node with the cache data.
Attention:
- If you are removing a single node and the remaining node in the I/O group is online, the data can be exposed to a single point of failure if the remaining node fails.
- If both nodes in the I/O group are online and the volumes are already degraded before deleting the node, redundancy to the volumes is already degraded. Removing a node might result in loss of access to data, and data loss might occur if the force option is used.
- Removing the last node destroys the system. Before you delete the last node in the system, ensure that you want to destroy the system.
- When you delete a node, you remove all redundancy
from the I/O group. As a result, new or existing failures can cause
I/O errors on the hosts. These failures can occur:
- Host configuration errors
- Zoning errors
- Multipathing software configuration errors
- If you are deleting the last node in an I/O group and volumes are assigned to the I/O group, you cannot delete the node from the system if the node is online. You must back up or migrate all data that you want to save before you delete the node. If the node is offline, you can delete the node.
- To take the specified node offline immediately without flushing the cache or ensuring that data loss does not occur, run the rmnode command with the force parameter. The force parameter forces continuation of the command even though any node-dependent volumes will be taken offline. Use the force parameter with caution; access to data on node-dependent volumes will be lost.