test

Sun Cluster System Administration Guide for Solaris OS

ProcedureHow to Boot a Node

If you intend to shut down or reboot other active nodes in the global cluster or zone cluster, wait until the node you are booting has reached at least the following status:

Otherwise, the node will not be available to take over services from other nodes in the cluster that you shut down or reboot. For information about booting a non-global zone, see Chapter 20, Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

Note –

Starting a 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.

The phys-schost# prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

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 B, Sun Cluster Object-Oriented Commands.

Note –

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

  1. To start a global-cluster node or zone-cluster node that has been shut down, boot the node. Perform all steps in this procedure from a node of the global cluster.

    • On SPARC based systems, run the following command.


      ok boot

    • On x86 based systems, run the following commands.

      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.

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

    • If you have a zone cluster, you can specify a node to boot.


      phys-schost# clzonecluster boot -n node zoneclustername

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

    • Running the cluster status command reports the status of a global-cluster node.


      phys-schost# cluster status -t node

    • Running the clzonecluster status command from a node on the global cluster reports the status of all zone-cluster nodes.


      phys-schost# clzonecluster status

      A zone-cluster node can only be booted in cluster mode when the node hosting the node is booted in cluster mode.

      Note –

      If a 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–10 SPARC: Booting a Global-Cluster Node

The following example shows the console output when node phys-schost-1 is booted into the global cluster.


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-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: