How to Install Sun Cluster Software on All Nodes (Custom) (Sun Cluster 3.1 10/03 Software Installation Guide)

Sun Cluster 3.1 10/03 Software Installation Guide

How to Install Sun Cluster Software on All Nodes (Custom)

Perform this procedure to install Sun Cluster software on all nodes of the cluster and to specify all cluster configuration settings. To install Sun Cluster software with the default cluster configuration settings, instead go to How to Install Sun Cluster Software on All Nodes (Typical).

Ensure that the Solaris operating environment is installed to support Sun Cluster software.

If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

Did you preinstall Sun Cluster software?
- If yes, proceed to Step 3.
- If no, enable remote shell (rsh(1M)) or secure shell (ssh(1)) access for superuser . Doing this task enables the scinstall utility to install Sun Cluster software packages.

Have available the following completed configuration planning worksheets:
- Cluster and Node Names Worksheet
- Cluster Interconnect Worksheet
See Planning the Sun Cluster Environment for planning guidelines.

Become superuser on the cluster node from which you intend to install the cluster.

On one node of the cluster, start the scinstall utility.
- If you preinstalled Sun Cluster software, type the following command:
  # /usr/cluster/bin/scinstall
- If you did not preinstall Sun Cluster software, insert the Sun Cluster 3.1 10/03 CD-ROM and type the following commands, where ver is 8(for Solaris 8) or 9 (for Solaris 9):
  # cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_ver/Tools # ./scinstall
Follow these guidelines to use the interactive scinstall utility.
- Interactive scinstall enables you to type ahead. Therefore, do not press Return more than once if the next menu screen does not appear immediately.
- Unless otherwise noted, you can press Control-D to return to either the start of a series of related questions or to the Main Menu.

From the Main Menu, type 1 (Install a cluster or cluster node).

  *** Main Menu ***

    Please select from one of the following (*) options:

      * 1) Install a cluster or cluster node
        2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node

      * ?) Help with menu options
      * q) Quit

    Option:  1

From the Install Menu, type 1 (Install all nodes of a new cluster).

  *** Install Menu ***

    Please select from any one of the following options:

        1) Install all nodes of a new cluster
        2) Install just this machine as the first node of a new cluster
        3) Add this machine as a node in an existing cluster

        ?) Help with menu options
        q) Return to the Main Menu

    Option:  1
…
  *** Installing all Nodes of a New Cluster ***
…
    Do you want to continue (yes/no) [yes]?  y

Type 2 to specify the Custom installation option.

  >>> Type of Installation <<<
…
    Please select from one of the following options:

        1) Typical
        2) Custom

        ?) Help
        q) Return to the Main Menu

    Option [1]:  2

Specify the cluster name.

  >>> Cluster Name <<<
…
    What is the name of the cluster you want to establish?  clustername

Specify the names of the other nodes to become part of this cluster.

  >>> Cluster Nodes <<<
…
    Node name:  node2
    Node name (Ctrl-D to finish):  Control-D

    This is the complete list of nodes:
…
    Is it correct (yes/no) [yes]?

Specify whether to use Data Encryption Standard (DES) authentication.

DES authentication provides an additional level of security at installation time. DES authentication enables the sponsoring node to authenticate nodes that attempt to contact the sponsoring node to update the cluster configuration.

If you choose to use DES authentication for additional security, you must configure all necessary encryption keys before any node can join the cluster. See the keyserv(1M) and publickey(4) man pages for details.
>>> Authenticating Requests to Add Nodes <<< … Do you need to use DES authentication (yes/no) [no]?

Specify the private network address and netmask.

 >>> Network Address for the Cluster Transport <<<
…
    Is it okay to accept the default network address (yes/no) [yes]? 
    Is it okay to accept the default netmask (yes/no) [yes]?

Note –

You cannot change the private network address after the cluster is successfully formed.

Specify whether the cluster uses transport junctions.
- If this is a two-node cluster, specify whether you intend to use transport junctions.
  >>> Point-to-Point Cables <<< … Does this two-node cluster use transport junctions (yes/no) [yes]?
  Tip –
  You can specify that the cluster uses transport junctions, regardless of whether the nodes are directly connected to each other. If you specify that the cluster uses transport junctions, you can more easily add new nodes to the cluster in the future.
- If this cluster has three or more nodes, you must use transport junctions. Press Return to continue to the next screen.
  >>> Point-to-Point Cables <<< … Since this is not a two-node cluster, you will be asked to configure two transport junctions. Hit ENTER to continue:

Does this cluster use transport junctions?

If no, proceed to Step 15.

If yes, specify names for the transport junctions. You can use the default names switchN or create your own names.

 >>> Cluster Transport Junctions <<<
 …
    What is the name of the first junction in the cluster [switch1]? 
    What is the name of the second junction in the cluster [switch2]?

Specify the first cluster-interconnect transport adapter for the node from which you are installing the cluster.
>>> Cluster Transport Adapters and Cables <<< Select the first cluster transport adapter for "node": 1) adapter 2) adapter … N) Other Option: N
The scinstall utility lists all Ethernet adapters that are found on the node. To configure adapters that are not listed, such as SCI-PCI adapters, type the number for the Other menu option. Then specify the adapter information that is requested in the subsequent prompts.

Note –
If your configuration uses SCI–PCI adapters, do not accept the default when you are prompted for the adapter connection (the port name). Instead, provide the port name (0, 1, 2, or 3) that is on the SCI Dolphin switch itself, to which the node is physically cabled. The following example shows the prompts and responses for declining the default port name and specifying the switch port name 0.
… Use the default port name for the "adapter" connection (yes/no) [yes]? n What is the name of the port you want to use? 0

Specify the second cluster-interconnect transport adapter for the node from which you are installing the cluster.
>>> Cluster Transport Adapters and Cables <<< Select the second cluster transport adapter for "node": 1) adapter 2) adapter … N) Other Option: N
You configure two adapters by using the scinstall command. You can configure additional adapters after Sun Cluster software is installed by using the scsetup utility.

Specify whether to use autodiscovery to automatically choose the transport adapters for the other nodes of the cluster.
Is it okay to use autodiscovery for the other nodes (yes/no) [yes]?
- If you type yes to choose to use autodiscovery, proceed to Step 18. The scinstall utility chooses transport adapters, junctions, and ports to configure for the remaining nodes.
- If you type no to decline autodiscovery, answer the subsequent prompts. Specify the transport adapter names, junction names, and port names that you want to configure for each of the remaining nodes.

Confirm that the scinstall utility should install patches.

See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

  >>> Software Patch Installation <<<
…
    Do you want scinstall to install patches for you (yes/no) [yes]?  y
    What is the name of the patch directory? /var/cluster/patches
    Do you want scinstall to use a patch list file (yes/no) [no]?  n
…

Specify the global-devices file-system name.

 >>> Global Devices File System <<<
…
    The default is to use /globaldevices.
…
    Is it okay to use this default (yes/no) [yes]?

Confirm that the scinstall utility should begin installation.

    Is it okay to begin the installation (yes/no) [yes]?  y

Specify whether installation should stop if the sccheck utility detects errors.
Interrupt the installation for sccheck errors (yes/no) [no]?
If you choose to interrupt installation and the sccheck utility detects any problems, the utility displays information about the problems and prompts you for your next action. Log files are placed in the /var/cluster/logs/install/sccheck/ directory.

If the sccheck utility quits with an error message because a version Sun Explorer software earlier than 3.5.1 is installed, remove the existing SUNWexplo package. Install the SUNWexplo package that is supplied on the Sun Cluster 3.1 10/03 CD-ROM. Then restart the scinstall utility.

The scinstall utility continues installation of all cluster nodes and reboots the cluster. Sun Cluster installation output is logged in the /var/cluster/logs/install/scinstall.log.N file.

Set up the name-service look-up order.

Go to How to Configure the Name-Service Switch.

Example – Installing Sun Cluster Software on All Nodes (Custom)

The following example shows the scinstall progress messages that are logged as scinstall completes Custom installation tasks on a two-node cluster. The cluster node names are phys-schost-1 and phys-schost-2. The specified adapter names are qfe2 and hme2. The Sun Cluster software is already installed by the Web Start program.

  Installation and Configuration

    Log file - /var/cluster/logs/install/scinstall.log.834

    Testing for "/globaldevices" on "phys-schost-1" ... done
    Testing for "/globaldevices" on "phys-schost-2" ... done

    Checking installation status ... done

    The Sun Cluster software is already installed on "phys-schost-1".
    The Sun Cluster software is already installed on "phys-schost-2".

    Starting discovery of the cluster transport configuration.

    Probing ..

    The following connections were discovered:

        phys-schost-1:qfe2  switch1  phys-schost-2:qfe2
        phys-schost-1:hme2  switch2  phys-schost-2:hme2

    Completed discovery of the cluster transport configuration.

    Started sccheck on "phys-schost-1".
    Started sccheck on "phys-schost-2".

    sccheck completed with no errors or warnings for "phys-schost-1".
    sccheck completed with no errors or warnings for "phys-schost-2".

    Configuring "phys-schost-2" ... done
    Rebooting "phys-schost-2" ... done

    Configuring "phys-schost-1" ... done
    Rebooting "phys-schost-1" ... 

Log file - /var/cluster/logs/install/scinstall.log.834

Rebooting ...