How to Reboot a Cluster

Run the cluster(1CL) shutdown command to shut down the cluster, then boot the cluster with the boot(1M) command on each node.

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands.

1. SPARC: If your cluster is running Oracle Parallel Server or Oracle RAC, shut down all instances of the database.

   Refer to the Oracle Parallel Server or Oracle RAC product documentation for shutdown procedures.

2. Become superuser or assume a role that provides solaris.cluster.admin RBAC authorization on any node in the cluster.

3. Shut down the cluster.

   From a single node in the cluster, type the following command.

   # cluster shutdown -g0 -y

   Each node is shut down.

   ---

   Note –

   Cluster nodes must have a working connection to the cluster interconnect to attain cluster membership.

   ---

4. Boot each node.

   The order in which the nodes are booted is irrelevant unless you make configuration changes between shutdowns. If you make configuration changes between shutdowns, start the node with the most current configuration first.

   • On SPARC based systems, do the following:

     ok boot

   • On x86 based systems, do the following:

     When the GRUB menu is displayed, select the appropriate Solaris entry and press Enter. The GRUB menu appears similar to the following:

     GNU GRUB version 0.95 (631K lower / 2095488K upper memory) +-------------------------------------------------------------------------+ | Solaris 10 /sol_10_x86 | | Solaris failsafe | | | +-------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line.

   ---

   Note –

   Cluster nodes must have a working connection to the cluster interconnect to attain cluster membership.

   ---

   For more information about GRUB based booting, see Chapter 11, GRUB Based Booting (Tasks), in System Administration Guide: Basic Administration.

   Messages appear on the booted nodes' consoles as cluster components are activated.

5. Verify that the nodes booted without error and are online.

   The scstat command reports the nodes' status.

   # cluster status -t node

   ---

   Note –

   If a cluster node's /var file system fills up, Sun Cluster might not be able to restart on that node. If this problem arises, see How to Repair a Full /var File System.

   ---

Example 3–4 SPARC: Rebooting a Cluster

The following example shows the console output when normal cluster operation is stopped, all nodes are shut down to the ok prompt, and the cluster is restarted. The -g 0 option sets the grace period to zero, and -y provides an automatic yes response to the confirmation question. Shutdown messages also appear on the consoles of other nodes in the cluster.

# cluster shutdown -g0 -y
Wed Mar 10 13:47:32 phys-schost-1 cl_runtime: 
WARNING: CMM monitoring disabled.
phys-schost-1# 
INIT: New run level: 0
The system is coming down.  Please wait.
...
The system is down.
syncing file systems... done
Program terminated
ok boot
Rebooting with command: boot 
...
Hostname: phys-schost-1
Booting as part of a cluster
...
NOTICE: Node phys-schost-1: attempting to join cluster
...
NOTICE: Node phys-schost-2 (incarnation # 937690106) has become reachable.
NOTICE: Node phys-schost-3 (incarnation # 937690290) has become reachable.
NOTICE: cluster has reached quorum.
...
NOTICE: Cluster members: phys-schost-1 phys-schost-2 phys-schost-3.
...
NOTICE: Node phys-schost-1: joined cluster
...
The system is coming up.  Please wait.
checking ufs filesystems
...
reservation program successfully exiting
Print services started.
volume management starting.
The system is ready.
phys-schost-1 console login:
NOTICE: Node phys-schost-1: joined cluster
...
The system is coming up.  Please wait.
checking ufs filesystems
...
reservation program successfully exiting
Print services started.
volume management starting.
The system is ready.
phys-schost-1 console login: