Sun Cluster Software Installation Guide for Solaris OS

ProcedureHow to Configure Sun Cluster Software on Additional Cluster Nodes (XML)

Perform this procedure to configure a new cluster node by using an XML cluster configuration file. The new node can be a duplication of an existing cluster node that runs Sun Cluster 3.2 software.

This procedure configures the following cluster components on the new node:

Before You Begin

Perform the following tasks:

  1. Ensure that Sun Cluster 3.2 software is not yet configured on the potential node that you want to add to a cluster.

    1. Become superuser on the potential node.

    2. Determine whether Sun Cluster 3.2 software is configured on the potential node.


      phys-schost-new# /usr/sbin/clinfo -n
      
      • If the command fails, go to Step 2.

        Sun Cluster 3.2 software is not yet configured on the node. You can add the potential node to the cluster.

      • If the command returns a node ID number, proceed to Step c.

        Sun Cluster software is already a configured on the node. Before you can add the node to a different cluster, you must remove the existing cluster configuration information.

    3. Boot the potential node into noncluster mode.

      • On SPARC based systems, perform the following command:


        ok boot -x
        
      • On x86 based systems, perform the following commands:

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

          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.

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

        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 similar to the following:


          GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
          +----------------------------------------------------------------------+
          | root (hd0,0,a)                                                       |
          | kernel /platform/i86pc/multiboot                                     |
          | module /platform/i86pc/boot_archive                                  |
          +----------------------------------------------------------------------+
          Use the ^ and v keys to select which entry is highlighted.
          Press 'b' to boot, 'e' to edit the selected command in the
          boot sequence, 'c' for a command-line, 'o' to open a new line
          after ('O' for before) the selected line, 'd' to remove the
          selected line, or escape to go back to the main menu.
        3. Add -x to the command to specify that the system boot into 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/multiboot -x
          
        4. Press Enter to accept the change and return to the boot parameters screen.

          The screen displays the edited command.


          GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
          +----------------------------------------------------------------------+
          | root (hd0,0,a)                                                       |
          | kernel /platform/i86pc/multiboot -x                                  |
          | module /platform/i86pc/boot_archive                                  |
          +----------------------------------------------------------------------+
          Use the ^ and v keys to select which entry is highlighted.
          Press 'b' to boot, 'e' to edit the selected command in the
          boot sequence, 'c' for a command-line, 'o' to open a new line
          after ('O' for before) the selected line, 'd' to remove the
          selected line, or escape to go back to the main menu.-
        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 to again to add the -x option to the kernel boot parameter command.


    4. Unconfigure Sun Cluster software from the potential node.


      phys-schost-new# /usr/cluster/bin/clnode remove
      
  2. If you are duplicating a node that runs Sun Cluster 3.2 software, create a cluster configuration XML file.

    1. Become superuser on the cluster node that you want to duplicate.

    2. Export the existing node's configuration information to a file.


      phys-schost# clnode export -o clconfigfile
      
      -o

      Specifies the output destination.

      clconfigfile

      The name of the cluster configuration XML file. The specified file name can be an existing file or a new file that the command will create.

      For more information, see the clnode(1CL) man page.

    3. Copy the cluster configuration XML file to the potential node that you will configure as a new cluster node.

  3. Become superuser on the potential node.

  4. Modify the cluster configuration XML file as needed.

    1. Open your cluster configuration XML file for editing.

      • If you are duplicating an existing cluster node, open the file that you created with the clnode export command.

      • If you are not duplicating an existing cluster node, create a new file.

        Base the file on the element hierarchy that is shown in the clconfiguration(5CL) man page. You can store the file in any directory.

    2. Modify the values of the XML elements to reflect the node configuration that you want to create.

      See the clconfiguration(5CL) man page for details about the structure and content of the cluster configuration XML file.

  5. Validate the cluster configuration XML file.


    phys-schost-new# xmllint --valid --noout clconfigfile
    
  6. Configure the new cluster node.


    phys-schost-new# clnode add -n sponsornode -i clconfigfile
    
    -n sponsornode

    Specifies the name of an existing cluster member to act as the sponsor for the new node.

    -i clconfigfile

    Specifies the name of the cluster configuration XML file to use as the input source.

  7. (Optional) Enable automatic node reboot if all monitored disk paths fail.

    1. Enable the automatic reboot feature.


      phys-schost# clnode set -p reboot_on_path_failure=enabled
      
      -p

      Specifies the property to set

      reboot_on_path_failure=enable

      Specifies that the node will reboot if all monitored disk paths fail, provided that at least one of the disks is accessible from a different node in the cluster.

    2. Verify that automatic reboot on disk-path failure is enabled.


      phys-schost# clnode show
      === Cluster Nodes ===                          
      
      Node Name:                                      node
      …
        reboot_on_path_failure:                          enabled
      …
Troubleshooting

Unsuccessful configuration - If one or more nodes cannot join the cluster, or if the wrong configuration information was specified, first attempt to rerun this procedure. If that does not correct the problem, perform the procedure How to Unconfigure Sun Cluster Software to Correct Installation Problems on each misconfigured node to remove it from the cluster configuration. You do not need to uninstall the Sun Cluster software packages. Then rerun this procedure.

Next Steps

If you added a node to a cluster that uses a quorum device, go to How to Update Quorum Devices After Adding a Node to a Cluster.

Otherwise, go to How to Verify the Quorum Configuration and Installation Mode.