How to Install Sun Cluster Software (scinstall) (Sun Cluster 3.0 U1 Installation Guide)

Sun Cluster 3.0 U1 Installation Guide

How to Install Sun Cluster Software (`scinstall`)

After you install the Solaris operating environment, perform this task on each node of the cluster to install Sun Cluster software and establish new cluster nodes. You can also use this procedure to add new nodes to an existing cluster.

Note -

If you used the scinstall(1M) custom JumpStart or SunPlex Manager installation method, the Sun Cluster software is already installed. Proceed to "How to Configure the Name Service Switch".

Have available the following completed configuration planning worksheets from the Sun Cluster 3.0 Release Notes.
- "Cluster and Node Names Worksheet"
- "Cluster Interconnect Worksheet"
See "Planning the Sun Cluster Environment" for planning guidelines.

Become superuser on the cluster node.

If you install from the CD-ROM, insert the Sun Cluster 3.0 7/01 CD-ROM into the CD-ROM drive of the node to install and configure.

If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_0u1 directory.

Change to the /cdrom/suncluster_3_0u1/SunCluster_3.0/Tools directory.
# cd /cdrom/suncluster_3_0u1/SunCluster_3.0/Tools

Are you installing a new node to an existing cluster?
- If yes, skip to Step 8.
- If no, go to Step 6.

Install the first node and establish the new cluster.

Follow the prompts to install Sun Cluster software, using the information from your configuration planning worksheets.

Start the scinstall(1M) utility.
# ./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.
- Your session answers are stored as defaults for the next time you run this menu option. Default answers display between brackets ([ ]) at the end of the prompt.
Tip -
Until the node is successfully booted in cluster mode, you can rerun scinstall and change the configuration information as needed. However, if bad configuration data for the node was pushed over to the established portion of the cluster, you might first need to remove the bad information. To do this, log in to one of the active cluster nodes, then use the scconf(1M) command to remove the bad adapter, junction, or cable information.

From the Main Menu, type 1 (Establish a new cluster).

 *** Main Menu ***
 
    Please select from one of the following (*) options:
 
      * 1) Establish a new cluster using this machine as the first node
      * 2) Add this machine as a node in an established cluster
        3) Configure a cluster to be JumpStarted from this install server
        4) Add support for new data services to this cluster node
        5) Print release information for this cluster node
 
      * ?) Help with menu options
      * q) Quit
 
    Option:  1
 
 *** Establishing a New Cluster ***
...
 Do you want to continue (yes/no) [yes]?  y

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 that will 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.

By default, Sun Cluster software permits a node to connect to the cluster only if the node is physically connected to the private interconnect and if the node name was specified in Step d. However, the node actually communicates with the sponsoring node over the public network, since the private interconnect is not yet fully configured. DES authentication provides an additional level of security at installation time by enabling the sponsoring node to more reliably authenticate nodes that attempt to contact it 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.

Note -

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

 >>> 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]?

If this is a two-node cluster, specify whether the cluster uses transport junctions.

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.
>>> Point-to-Point Cables <<< ... Does this two-node cluster use transport junctions (yes/no) [yes]?

If this cluster uses transport junctions, specify names for the transport junctions.

You must use transport junctions if a cluster contains three or more nodes. 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 cluster interconnect transport adapters and, if used, the names of the transport junctions they connect to.

You can configure up to two adapters by using the scinstall command. You can configure additional adapters after Sun Cluster software is installed by using the scsetup utility.

 >>> Cluster Transport Adapters and Cables <<<
 ...
    What is the name of the first cluster transport adapter?  adapter
 ...
    Name of the junction to which "adapter" is connected [switch1]? 
 ...
    What is the name of the second cluster transport adapter?  adapter
 ...
    Okay to use the default for the "qfe0" connection (yes/no) [yes]? 
  
    What is the name of the second cluster transport adapter?  adapter
 
    Name of the junction to which "adapter" is connected [switch2]? 
     Use the default port for the "adapter" connection [yes]?

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]?

Do you have any Sun Cluster software patches to install?
- If yes, type no in the Automatic Reboot screen to decline automatic reboot.
- If no, type yes to accept automatic reboot.
>>> Automatic Reboot <<< ... Do you want scinstall to reboot for you (yes/no) [yes]?

Accept or decline the generated scinstall command.

The scinstall command generated from your input is displayed for confirmation.

 >>> Confirmation <<<
 
    Your responses indicate the following options to scinstall:
 
      scinstall -i  \
...
    Are these the options you want to use (yes/no) [yes]? 
    Do you want to continue with the install (yes/no) [yes]?

If you accept the command and continue the installation, scinstall processing continues. "Example--Installing Sun Cluster Software" shows an example of the output you might see during scinstall processing.
If you decline the command, the scinstall utility returns you to the Main Menu. From there you can rerun menu option 1 and provide different answers. Your previous answers display as the defaults.

Sun Cluster installation output is logged in the /var/cluster/logs/install/scinstall.log.pid file, where pid is the process ID number of the scinstall instance.

Note -

Unless you have installed your own /etc/inet/ntp.conf file, the scinstall command installs a default ntp.conf file for you. Because the default file is shipped with references to the maximum possible number of nodes, the xntpd(1M) daemon might issue error messages regarding some of these references at boot time. You can safely ignore these messages. See "How to Update Network Time Protocol (NTP)" for information on how to suppress these messages under otherwise normal cluster conditions.

Do you have any Sun Cluster software patches to install?
- If yes, install any Sun Cluster software patches on the node and reboot the node. See the Sun Cluster 3.0 U1 Release Notes for the location of patches and installation instructions.
- If no, and scinstall rebooted the node during installation, go to Step 8. If scinstall did not reboot the node, manually reboot the node to establish the cluster before you proceed to Step 8.
The first node reboot after Sun Cluster software installation forms the cluster and establishes this node as the first-installed node of the cluster.

Install the second node of the cluster.

Follow the prompts to install Sun Cluster software. Refer to the information from your configuration planning worksheets.

Note -

Do not reboot or shut down the first-installed node while any other nodes are being installed, even if you use another node as the sponsoring node. Until quorum votes are assigned to the cluster nodes and cluster install mode is disabled, the first-installed node, which established the cluster, is the only node that has a quorum vote. Rebooting or shutting down the first-installed node will therefore cause a system panic because of lost quorum.

Start the scinstall utility.

You can start this step while software is still being installed on the first-installed node. If necessary, the second node waits for the first node to complete installation.
# ./scinstall

From the Main Menu, type 2 (Add this machine as a node).

 *** Main Menu ***
 
    Please select from one of the following (*) options:
 
      * 1) Establish a new cluster using this machine as the first node
      * 2) Add this machine as a node in an established cluster
        3) Configure a cluster to be JumpStarted from this install server
        4) Add support for new data services to this cluster node
        5) Print release information for this cluster node
 
      * ?) Help with menu options
      * q) Quit
 
    Option:  2
 
  *** Adding a Node to an Established Cluster ***
...
    Do you want to continue (yes/no) [yes]? y

Specify the name of any existing cluster node, referred to as the sponsoring node.

 >>> Sponsoring Node <<<
...
    What is the name of the sponsoring node?  node1

Specify the cluster name.

 >>> Cluster Name <<<
...
    What is the name of the cluster you want to join?  clustername

Specify whether this is a two-node cluster and whether the cluster uses transport junctions.

You must use transport junctions if a cluster contains three or more nodes.
>>> Point-to-Point Cables <<< ... Is this a two-node cluster (yes/no) [yes]? Does this two-node cluster use transport junctions (yes/no) [yes]?

Specify the cluster interconnect transport adapters and transport junctions, if any.

 >>> Cluster Transport Adapters and Cables <<<
...
    What is the name of the first cluster transport adapter?  adapter
...
    Name of adapter on "node1" to which "adapter" is connected?  adapter
 
    What is the name of the second cluster transport adapter?  adapter
    Name of adapter on "node1" to which "adapter" is connected?  adapter

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]?

Do you have any Sun Cluster software patches to install?
- If yes, type no in the Automatic Reboot screen to decline automatic reboot.
- If no, type yes to accept automatic reboot.
>>> Automatic Reboot <<< ... Do you want scinstall to reboot for you (yes/no) [yes]?

Accept or decline the generated scinstall command.

The scinstall command generated from your input is displayed for confirmation.

 >>> Confirmation <<<
 
    Your responses indicate the following options to scinstall:
 
      scinstall -i  \
...
    Are these the options you want to use (yes/no) [yes]? 
    Do you want to continue with the install (yes/no) [yes]?

If you accept the command and continue the installation, scinstall processing continues. "Example--Installing Sun Cluster Software" shows an example of the output you might see during scinstall processing. If the sponsoring node is not yet established in the cluster, scinstall waits for the sponsoring node to become available.
If you decline the command, the scinstall utility returns you to the Main Menu. From there you can rerun menu option 2 and provide different answers. Your previous answers display as the defaults.

Sun Cluster installation output is logged in the /var/cluster/logs/install/scinstall.log.pid file, where pid is the process ID number of the scinstall instance.

Note -

Unless you have installed your own /etc/inet/ntp.conf file, the scinstall command installs a default ntp.conf file for you. Because the default file is shipped with references to eight nodes, the xntpd(1M) daemon might issue error messages regarding some of these references at boot time. You can safely ignore these messages. See "How to Update Network Time Protocol (NTP)" for information on how to suppress these messages under otherwise normal cluster conditions.

Do you have any Sun Cluster software patches to install?
- If yes, install the Sun Cluster software patches on the node and reboot the node. See the Sun Cluster 3.0 U1 Release Notes for the location of patches and installation instructions.
  
  Note -
  Do not reboot or shut down the first-installed node while any other nodes are being installed, even if you use another node as the sponsoring node. Until quorum votes are assigned to the cluster nodes and cluster install mode is disabled, the first-installed node, which established the cluster, is the only node that has a quorum vote. Rebooting or shutting down the first-installed node will therefore cause a system panic because of lost quorum. Cluster nodes remain in install mode until the first time you run the scsetup(1M) command, during the procedure "How to Perform Post-Installation Setup".
- If no, and scinstall rebooted the node during installation, go to Step 10. If scinstall did not reboot the node, manually reboot the node to establish the cluster before you proceed to Step 10.

Repeat Step 8 and Step 9 on each additional node until all nodes are fully configured.

You do not need to wait for the second node to complete installation and reboot into the node before you begin installation on additional nodes.

Set up the name service look-up order.

Go to "How to Configure the Name Service Switch".

Example--Installing Sun Cluster Software

The following example shows the progress messages displayed as scinstall installation tasks are completed on the node phys-schost-1, which is the first node to be installed in the cluster.

** Installing SunCluster 3.0 **
        SUNWscr.....done.
        SUNWscdev...done.
        SUNWscu.....done.
        SUNWscman...done.
        SUNWscsal...done.
        SUNWscsam...done.
        SUNWscrsmop.done.
        SUNWsci.....done.
        SUNWscid....done.
        SUNWscidx...done.
        SUNWscvm....done.
        SUNWmdm.....done.
 
Initializing cluster name to "sccluster" ... done
Initializing authentication options ... done
Initializing configuration for adapter "hme2" ... done
Initializing configuration for adapter "hme4" ... done
Initializing configuration for junction "switch1" ... done
Initializing configuration for junction "switch2" ... done
Initializing configuration for cable ... done
Initializing configuration for cable ... done
Setting the node ID for "phys-schost-1" ... done (id=1)
 
Checking for global devices global file system ... done
Checking device to use for global devices file system ... done
Updating vfstab ... done
 
Verifying that NTP is configured ... done
Installing a default NTP configuration ... done
Please complete the NTP configuration after scinstall has finished.
 
Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done
 
Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done
 
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.060199105132
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
 
Ensure routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.
 
Log file - /var/cluster/logs/install/scinstall.log.276
 
Rebooting ...