>>- svctask -- -- stopcluster -- --+----------+-- --------------> '- -force -' >--+--------------------------+-------------------------------->< '- -node --+- node_name -+-' '- node_id ---'
When you enter this command without any arguments, the entire cluster is shut down. All data is flushed to disk before the power is removed.
| Attention: Ensure that you have stopped all FlashCopy, Remote Copy, and data migration operations before you attempt a node or cluster shutdown. You should also ensure that all asynchronous deletion operations have completed prior to a shutdown operation. |
When you enter this command either a node ID or node name argument, the node in question is shut down. After the command completes, the other node in the I/O group destages the contents of its cache and goes into write-through mode until the power to the node is returned and the node rejoins the cluster.
If all input power to a SAN Volume Controller cluster is to be removed for more than a few minutes, (for example, if the machine room power is to be shutdown for maintenance), it is important that the cluster is shutdown before the power is removed. The reason for this is that if the input power is removed from the uninterruptible power supply units without first shutting down the cluster and the uninterruptible power supplies, the uninterruptible power supply units will remain operational and eventually become drained of power.
When input power is restored to the uninterruptible power supplies they will start to recharge but the SAN Volume Controllers will not permit any I/O activity to be performed to the virtual disks until the uninterruptible power supply is charged enough to enable all the data on the SAN Volume Controller nodes to be saved in the event of an unexpected power loss. This might take as long as three hours. Shutting down the cluster prior to removing input power to the uninterruptible power supply units will prevent the battery power being drained and will make it possible for I/O activity to be resumed as soon as input power is restored.
| Attention: Before shutting down a node or the cluster you should quiesce all I/O operations that are destined for this node or cluster. Failure to do so may result in failed I/O operations being reported to your host operating systems. |
Begin the process of quiescing all I/O to the cluster by stopping the applications on your hosts that are using the VDisks provided by the cluster.
| Attention: If you are shutting down the entire cluster, you will lose access to all VDisks being provided by this cluster. |
When all I/O has been stopped, issue the svctask stopcluster to shut down a single node or the entire cluster in a controller manner. If you specify the node ID or node name, you can shut down a single node. When you enter this command either a node ID or node name argument, the node in question is shut down. After the command completes, the other node in the I/O group destages the contents of its cache and goes into write-through mode until the power to the node is returned and the node rejoins the cluster. You must then close the SSH session if you are using ssh in interactive mode.
| Attention: If this is the last node in an I/O group, you will lose all access to the virtual disks in the I/O group. Before you enter this command, ensure that this is what you want to do. You must specify the force flag. |
If a shutdown command has been sent to the cluster and both cluster and uninterruptible power supply units have powered off, when input power is restored it will be necessary to restart the uninterruptible power supply units by pressing the power button on the uninterruptible power supply front panel.
| Attention: If you are shutting down a single node, and the other node in the I/O group is online, be aware that the cache on the partner node will go into write-through mode and that you are exposed to a single point of failure should the partner node fail while this node is shut down. Proceed to . |
| Attention: If you are shutting down a single node, and this is the last node in the I/O group, you will lose access to all VDisks being served by this I/O group. |
Perform the following steps to shut down a single node:
svcinfo lsvdisk -filtervalue IO_group_name=<name>where <name> is the name of the I/O group in question.
svctask stopcluster <nodename/ID>where <nodename/ID> is the name or ID of the node that you want to shut down.
Note: If this is the last node in the I/O group you also
need to specify the -force parameter. For example to force the shutdown of
node1:
svctask stopcluster -force node1 |
An invocation example
svctask stopcluster
The resulting output You will be presented with the following warning:
Are you sure that you want to continue with the shut down?
Ensure that you have stopped all FlashCopy mappings, Remote Copy relationships, data migration operations and forced deletions before continuing. Entering y to this will execute the command. No feedback is then displayed. Entering anything other than y or Y will result in the command not executing. No feedback is displayed.