4.2 Stopping the Cluster and Cluster Nodes

Putting a node in any mode other than multiuser, or halting or rebooting the node, requires stopping the Sun Cluster membership monitor. Then your site's preferred method can be used for further node maintenance.

Stopping the cluster requires stopping the membership monitor on all cluster nodes by running the scadmin stopnode command on all nodes simultaneously.

• You can stop the membership monitor only when no logical hosts are owned by the local Sun Cluster node.

• To stop the membership monitor on one node, switch over the logical host(s) to another node using the haswitch(1M) command and stop the membership monitor by typing the following command:

phys-hahost1# haswitch ...
 phys-hahost1# scadmin stopnode

If a logical host is owned by the node when the scadmin stopnode command is run, ownership will be transferred to another node that can master the logical host before the membership monitor is stopped. If the other possible master of the logical host is down, the scadmin stopnode command will shut down the data services in addition to stopping the membership monitor.

After the scadmin stopnode command runs, Sun Cluster will remain stopped, even across system reboots, until the scadmin startnode command is run.

The scadmin stopnode command removes the node from the cluster. In the absence of other simultaneous failures, you may shut down as many nodes as you choose without losing quorum among the remaining nodes. (If quorum is lost, the entire cluster shuts down.)

If you shut down a node for disk maintenance, you also must prepare the boot disk or data disk using the procedures described in Chapter 10, Administering Sun Cluster Local Disks for boot disks, or those described in your volume manager documentation for data disks.

You might have to shut down one or more Sun Cluster nodes to perform hardware maintenance procedures such as adding or removing SBus cards. The following sections describe the procedure for shutting down a single node or the entire cluster.

4.2.1 How to Stop Sun Cluster on a Cluster Node

1. If it is not necessary to have the data remain available, place the logical hosts (disk groups) into maintenance mode.

   phys-hahost2# haswitch -m logicalhost

   Refer to the haswitch(1M) man page for details.

   ---

   Note -

   It is possible to halt a Sun Cluster node by using the halt(1M) command, allowing a failover to restore the logical host services on the backup node. However, the halt(1M) operation might cause the node to panic. The haswitch(1M) command offers a more reliable method of switching ownership of the logical hosts.

   ---

2. Stop Sun Cluster on one node without stopping services running on the other nodes in the cluster.

   phys-hahost1# scadmin stopnode

3. Halt the node.

   phys-hahost1# halt

   The node is now ready for maintenance work.

4.2.2 How to Stop Sun Cluster on All Nodes

You might want to shut down all nodes in a Sun Cluster configuration if a hazardous environmental condition exists, such as a cooling failure or a severe lightning storm.

1. Stop the membership monitor on all nodes simultaneously by using the scadmin(1M) command.

   You can do this in one step using the Cluster Console.

   phys-hahost1# scadmin stopnode ...

2. Halt all nodes using halt(1M).

   phys-hahost1# halt ...

4.2.3 How to Halt a Sun Cluster Node

Shut down any Sun Cluster node by using the halt(1M) command or the uadmin(1M) command.

If the membership monitor is running when a node is shut down, the node will most likely take a "Failfast timeout" and display the following message:

panic[cpu9]/thread=0x50f939e0: Failfast timeout - unit 

You can avoid this by stopping the membership monitor before shutting down the node. Refer to the procedure, "4.2.2 How to Stop Sun Cluster on All Nodes", for additional information.

4.2.4 Stopping the Membership Monitor While Running RDBMS Instances

Database server instances can run on a node only after you have invoked the startnode option and the node has successfully joined the cluster. All database instances should be shut down before the stopnode option is invoked.

If you are running Oracle7 Parallel Server, Oracle8 Parallel Server, or Informix XPS, refer to your product documentation for shutdown procedures.

If the stopnode command is executed while the Oracle7 or Oracle8 instance is still running on the node, stopnode will hang and the following message is displayed on the console:

ID[vxclust]: stop: waiting for applications to end

The Oracle7 or Oracle8 instance must be shut down for the stopnode command to terminate successfully.

If the stopnode command is executed while the Informix-Online XPS instance is still running on the node, the database hangs and becomes unusable.