Procedure for stopping cluster services

Edit online

This topic describes the procedure for stopping cluster services on a single node or on all nodes in a cluster by using the C-SPOC utility on one of the cluster nodes.

About this task

To stop cluster services:

Procedure

  1. Enter the fastpath smit cl_admin.
  2. Select PowerHA® SystemMirror® Services > Stop Cluster Services and press Enter.
  3. Enter field values in the SMIT panel as follows:
    Table 1. Stop Cluster Services fields
    Field Value
    Select an Action on resource groups Indicate the type of shutdown:
    • Bring resource groups Offline. PowerHA SystemMirror stops all managed resources currently ONLINE on the node being stopped. PowerHA SystemMirror will not activate these resources on any other nodes, that is, no fallover.

      This option is equivalent to the option to stopping cluster services gracefully in previous releases.

      After successfully stopping all managed resources, PowerHA SystemMirror stops RSCT services and goes into ST_INIT state.

    • Move resource groups. PowerHA SystemMirror stops all managed resources currently ONLINE on the node being stopped. The resource groups will be moved to a takeover node according to the configured resource group policies (if defined), dependency configurations (if defined) and available resources.

      This option is equivalent to the graceful with takeover option in previous releases.

      After successfully stopping all managed resources PowerHA SystemMirror, stops RSCT services and the Cluster Manager daemon goes into ST_INIT state.

    • Unmanage resource groups. The cluster services are stopped immediately. Resources that are online on the node are not stopped. Applications continue to run. This option is equivalent to the forced down option in previous releases.

      For more information, see Stopping PowerHA SystemMirror cluster services without stopping applications.

      PowerHA SystemMirror will not stop the managed resources; applications remain functional.

      PowerHA SystemMirror does not manage the resources on these nodes.

      PowerHA SystemMirror continues to run and RSCT remains functional.

    Note: On a node that has Enhanced concurrent (ECM) volume groups, cluster services can be stopped with the resource groups placed in an unmanaged state. RSCT services will continue to run so that ECM remains functional.

    If you stop cluster services with this option, the resource groups that are active on this node go into unmanaged state. Once the resource group is in the unmanaged state, PowerHA SystemMirror does not process any resource failures. This applies to hardware resources such as disks and adapters as well as any managed applications.

    Refer to Procedure for starting cluster services for information on reintegrating a node on which the cluster services were stopped back into the cluster.
    Stop now, on system restart or both Indicate whether you want the cluster services to stop now, at restart (when the operating system reboots), or on both occasions. If you select restart or both, the entry in the /etc/inittab file that starts cluster services is removed. Cluster services will no longer come up automatically after a reboot.
    BROADCAST cluster shutdown? Indicate whether you want to send a broadcast message to users before the cluster services stop. If you specify true, a message is broadcast on all cluster nodes.
  4. Press Enter. The system stops the cluster services on the nodes specified.

    If the stop operation fails, check the /var/hacmp/log/cspoc.log file for error messages. This file contains the command execution status of the C-SPOC command executed on each cluster node.

    Note: After stopping cluster services, you must wait a minimum of two minutes for the RSCT to quiesce before starting cluster services.