Use the command-line interface (CLI) to shut down a node.
Stop all FlashCopy, Metro Mirror, Global Mirror, or data
migration operations before shutting down a node.
Also ensure
that all asynchronous deletion operations have completed.
Also
quiesce all I/O operations for this node. Failure to do so can result
in failed I/O operations reported to your host operating systems.
Attention: You lose access to all I/O-group
volumes. Determine if any volumes are dependent on the node by issuing
the lsnodedependentvdisks command.
To shut down a node, follow these steps:
- To shut down a single node, issue the following command:
stopsystem -node node_name or node_ID
Where
node_name or node_ID specifies
the node name or the node ID that is assigned to the node.
- To shut down the last node in an I/O group, issue the following
command.
stopsystem -force -node node_name or node_ID
The -force parameter also overrides
the checks that this command runs. The parameter overrides the following
two checks:
- If the command results in volumes going offline, the command fails
unless the -force parameter is used.
- If the node being shut down is the last online node in the I/O
group, the command fails unless the -force parameter is used.
If you use the -force parameter as a result of an error about
volumes going offline, you force the node to shut down, even if it
is the last online node in the I/O group. The -force parameter should always be used with caution.
Issuing the stopsystem command
with no parameters shuts down the entire clustered system after flushing
all data to disk.