Shutting Down and Booting a Single Cluster Node

Note - Use the scswitch(1M) command in conjunction with the Solaris shutdown(1M) command to shut down an individual node. Use the scshutdown command only when shutting down an entire cluster.

Table 3-2 Task Map: Shutting Down and Booting a Cluster Node

How to Shut Down a Cluster Node

Caution - Do not use send brk on a cluster console to shut down a cluster node. The command is not supported within a cluster.

1. SPARC: If your cluster is running Oracle Parallel Server/Real Application Clusters, shut down all instances of the database.

   Refer to the Oracle Parallel Server/Real Application Clusters product documentation for shutdown procedures.

2. Become superuser on the cluster node to be shut down.

3. Switch all resource groups, resources, and device groups from the node being shut down to other cluster members.

   On the node to be shut down, type the following command.

   # scswitch -S -h node

   
   

   -S	Evacuates all device services and resource groups from the specified node.
   -h node	Specifies the node from which you are switching resource groups and device groups.

4. Shut down the cluster node.

   On the node to be shut down, type the following command.

   # shutdown -g0 -y -i0

   
   

5. Verify that the cluster node is showing the ok prompt or the Select (b)oot or (i)nterpreter prompt on the Current Boot Parameters screen.

6. If necessary, power off the node.

SPARC: Example--Shutting Down a Cluster Node

The following example shows the console output when shutting down node phys-schost-1. The -g0 option sets the grace period to zero, -y provides an automatic yes response to the confirmation question, and -i0 invokes run level 0 (zero). Shutdown messages for this node appear on the consoles of other nodes in the cluster.

# scswitch -S -h phys-schost-1
# shutdown -g0 -y -i0
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.
Notice: rgmd is being stopped.
Notice: rpc.pmfd is being stopped.
Notice: rpc.fed is being stopped.
umount: /global/.devices/node@1 busy
umount: /global/phys-schost-1 busy
The system is down.
syncing file systems... done
Program terminated
ok 

x86: Example--Shutting Down a Cluster Node

The following example shows the console output when shutting down node phys-schost-1. The -g0 option sets the grace period to zero, -y provides an automatic yes response to the confirmation question, and -i0 invokes run level 0 (zero). Shutdown messages for this node appear on the consoles of other nodes in the cluster.

# scswitch -S -h phys-schost-1
# shutdown -g0 -y -i0
Shutdown started.    Wed Mar 10 13:47:32 PST 2004

Changing to init state 0 - please wait
Broadcast Message from root (console) on phys-schost-1 Wed Mar 10 13:47:32... 
THE SYSTEM phys-schost-1 IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged

phys-schost-1#
INIT: New run level: 0
The system is coming down.  Please wait.
System services are now being stopped.
/etc/rc0.d/K05initrgm: Calling scswitch -S (evacuate)
failfasts disabled on node 1
Print services already stopped.
Mar 10 13:47:44 phys-schost-1 syslogd: going down on signal 15
umount: /global/.devices/node@2 busy
umount: /global/.devices/node@1 busy
The system is down.
syncing file systems... done
WARNING: CMM: Node being shut down.
Type any key to continue 

Where to Go From Here

See How to Boot a Cluster Node to restart a cluster node that has been shut down.

How to Boot a Cluster Node

Note - Starting a cluster node can be affected by the quorum configuration. In a two-node cluster, you must have a quorum device configured so that the total quorum count for the cluster is three. You should have one quorum count for each node and one quorum count for the quorum device. In this situation, if the first node is shut down, the second node continues to have quorum and runs as the sole cluster member. For the first node to come back in the cluster as a cluster node, the second node must be up and running. The required cluster quorum count (two) must be present.

1. To start a cluster node that has been shut down, boot the node.

   • SPARC:

     ok boot

     
     

   • x86:

     <<< Current Boot Parameters >>> Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/ sd@0,0:a Boot args: Type b [file-name] [boot-flags] <ENTER> to boot with options or i <ENTER> to enter boot interpreter or <ENTER> to boot with defaults <<< timeout in 5 seconds >>> Select (b)oot or (i)nterpreter: b

     
     

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

   ---

   Note - A cluster node must have a working connection to the cluster interconnect to attain cluster membership.

   ---

2. Verify that the node has booted without error, and is online.

   The scstat command reports the status of a node.

   # scstat -n

   
   

   ---

   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.

   ---