Go to main content

Administering an Oracle® Solaris Cluster 4.4 Configuration

Exit Print View

Updated: March 2019
 
 

How to Boot a Node in Noncluster Mode

You can boot a global-cluster node in noncluster mode, where the node does not participate in the cluster membership. Noncluster mode is useful when installing the cluster software or performing certain administrative procedures, such as updating a node. A zone-cluster node cannot be in a boot state that is different from the state of the underlying global-cluster node. If the global-cluster node is booted in noncluster mode, the zone-cluster node is automatically in noncluster mode.

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

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

  1. Assume the root role or a role that provides solaris.cluster.admin authorization on the cluster to be started in noncluster mode.

    Perform all steps in this procedure from a node of the global cluster.

  2. Shut down the zone-cluster node or the global-cluster node.

    The clnode evacuate command switches over all device groups from the specified node to the next-preferred node. The command also switches all resource groups from global zones on the specified node to the next-preferred global zones on other nodes.

    • Shut down a specific global cluster node.
      phys-schost# clnode evacuate node
      phys-schost# shutdown -g0 -y
    • Shut down a specific zone-cluster node from a global-cluster node.
      phys-schost# clzonecluster halt –n node zone-cluster-name

      You can also use the clnode evacuate and shutdown commands within a zone cluster.

  3. Verify that the global-cluster node is showing the ok prompt on an Oracle Solaris-based system or the Press any key to continue message on a GRUB menu on an x86 based system.
  4. Boot the global-cluster node in noncluster mode.
    • On SPARC based systems, run the following command.

      ok boot -xs
    • On x86 based systems, run the following commands.

    1. In the GRUB menu, use the arrow keys to select the appropriate Oracle Solaris entry and type e to edit its commands.

      The GRUB menu appears.

      For more information about GRUB based booting, see About Run Level Booting in Booting and Shutting Down Oracle Solaris 11.4 Systems.

    2. In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.

      The GRUB boot parameters screen appears.

    3. Add -x to the command to specify system boot in noncluster mode.
      [ Minimal BASH-like line editing is supported. For the first word, TAB
      lists possible command completions. Anywhere else TAB lists the possible
      completions of a device/filename. ESC at any time exits. ]
      
      grub edit> kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS -x
    4. Press the Enter key to accept the change and return to the boot parameters screen.

      The screen displays the edited command.

    5. Type b to boot the node into noncluster mode.

      Note -  This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps again to add the -x option to the kernel boot parameter command.
Example 29  SPARC: Booting a Global-Cluster Node in Noncluster Mode

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

phys-schost# clnode evacuate phys-schost-1
phys-schost# cluster shutdown -g0 -y
Shutdown started.    Wed Mar 10 13:47:32 phys-schost-1 cl_runtime:

WARNING: CMM monitoring disabled.
phys-schost-1#
...
rg_name = schost-sa-1 ...
offline node = phys-schost-2 ...
num of node = 0 ...
phys-schost-1#
INIT: New run level: 0
The system is coming down.  Please wait.
System services are now being stopped.
Print services stopped.
syslogd: going down on signal 15
...
The system is down.
syncing file systems... done
WARNING: node phys-schost-1 is being shut down.
Program terminated

ok boot -x
...
Not booting as part of cluster
...
The system is ready.
phys-schost-1 console login: