How to Install Sun Cluster Software on the First Cluster Node (scinstall) (Sun Cluster 3.1 Software Installation Guide)

Sun Cluster 3.1 Software Installation Guide

How to Install Sun Cluster Software on the First Cluster Node (`scinstall`)

After you install the Solaris operating environment, perform this task on one node of the cluster to install Sun Cluster software and establish the cluster.

Note –

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

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

You must install Solaris software as described in How to Install Solaris 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 you intend to install on the cluster.

Do you intend to use SunPlex Manager?
- If yes, ensure that the Apache software packages are installed on the node. If you installed the Solaris End User System Support software group, install the SUNWapch* packages from the Solaris CD-ROM.
  # pkgadd -d . SUNWapchr SUNWapchu
  The Apache software packages are automatically installed if you installed a higher-level Solaris software group.
- If no, go to Step 3.

Have available the following completed configuration planning worksheets:
- “Cluster and Node Names Worksheet” in Sun Cluster 3.1 Release Notes
- “Cluster Interconnect Worksheet” in Sun Cluster 3.1 Release Notes
See Planning the Sun Cluster Environment for planning guidelines.

Become superuser on the cluster node to install.

If you install from the CD-ROM, insert the Sun Cluster 3.1 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_1 directory.

Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
- If no, go to Step 7.
- If yes, install additional packages from the Packages directory of the Sun Cluster 3.1 CD-ROM. These packages are not automatically installed by scinstall(1M).
  # cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages # pkgadd -d . packages
  Note –
  In the CD-ROM path, replace ver with 8 (for Solaris 8) or 9 (for Solaris 9)
  
  The following table lists the Sun Cluster 3.1 packages required to support the RSMAPI or SCI-PCI adapters and the order in which you must install them.
  Table 2–2 Sun Cluster 3.1 Packages to Support the RSMAPI and SCI-PCI Adapters
  
  Feature
  
  Additional Sun Cluster 3.1 Packages to Install
  
  RSMAPI
  
  SUNWscrif
  
  SCI-PCI adapters
  
  SUNWsci SUNWscid SUNWscidx

Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9 ).

The following example uses the path to the Solaris 8 version of Sun Cluster software.
# cd /cdrom/suncluster_3_1/SunCluster_3.1/Sol_8/Tools

Start the scinstall(1M) utility.
# ./scinstall
Follow the prompts to install Sun Cluster software, using the information from your configuration planning worksheets.

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. If you press Control-D to abort the session after Sun Cluster software is installed, scinstall asks you whether you want it to de-install those packages.
- 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.

Feature	Additional Sun Cluster 3.1 Packages to Install
RSMAPI	`SUNWscrif`
SCI-PCI adapters	`SUNWsci` `SUNWscid` `SUNWscidx`

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

After you read the information in the Establishing a New Cluster screen, type yes to continue to the next screen.

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

When prompted whether to continue to install Sun Cluster software packages, type yes.

 >>> Software Package Installation <<<
  
    Installation of the Sun Cluster framework software packages will 
    take a few minutes to complete.
  
    Is it okay to continue (yes/no) [yes]?  yes
  
** Installing SunCluster 3.0 **
        SUNWscr.....done
...Hit ENTER to continue:

After all packages are installed, press Return to continue to the next screen.

Specify the cluster name.

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

Run the preinstallation check.

 >>> Check <<<
 
    This step runs sccheck(1M) to verify that certain basic hardware and
    software pre-configuration requirements have been met. If sccheck(1M)
    detects potential problems with configuring this machine as a cluster
    node, a list of warnings is printed.
 
Hit ENTER to continue:

If the sccheck(1M) command detects any problems, it displays information about the problems found and prompts you for your next action.

The sccheck utility has detected the following potential problems:
...  
Hit ENTER to continue:
...
 What would you like to do?
  
        1) Proceed with the installation anyway
        2) Retry sccheck
        q) Return to the main menu
  
    Option:

If you see this sccheck error message, type one of the following responses.

If you know that you can safely ignore the sccheck messages, for example from notification in the Sun Cluster 3.1 Release Notes that a recent qualification will trigger a harmless error message, type 1 to continue installation.
If you can correct the problem without quitting the scinstall utility, correct the problem and type 2 to run sccheck again.
Type q to stop installation. Correct the problem detected by sccheck, then return to Step 8 and restart scinstall.

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 13. 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.

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

If no, skip to Step 18.

Specify the first cluster interconnect transport adapter.
>>> Cluster Transport Adapters and Cables <<< ... Select the first cluster transport adapter to use: 1) adapter 2) adapter ... N) Other Option:
The scinstall utility lists all Ethernet adapters found through autodiscovery. To configure adapters that are not listed, such as SCI-PCI adapters, type the number for Other, then specify the adapter information requested in the subsequent menus.

If your cluster uses transport junctions, specify the name of the first transport junction and its port.

Otherwise, skip to Step 20.
Name of the junction to which "adapter" is connected [switch1]? Use the default port name for the "adapter" connection (yes/no) [yes]? Hit ENTER to continue:
Note –
If your configuration uses SCI 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) found on the 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 Dolphin switch port name 0.
Use the default port name for the "adapter" connection (yes/no) [yes]? no What is the name of the port you want to use? 0

Choose the second cluster interconnect transport adapter.
Select the second cluster transport adapter to use: 1) adapter 2) adapter ... N) Other Option:
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.

If your cluster uses transport junctions, specify the name of the second transport junction and its port.

Otherwise, skip to Step 22.
Name of the junction to which "adapter" is connected [switch2]? Use the default port name for the "adapter" connection (yes/no) [yes]? Hit ENTER to continue:
Note –
If your configuration uses SCI adapters, do not accept the default when you are prompted for the adapter port name. Instead, provide the port name (0, 1, 2, or 3) found on the 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 Dolphin switch port name 0.
Use the default port name for the "adapter" connection (yes/no) [yes]? no What is the name of the port you want to use? 0

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?
>>> Automatic Reboot <<< ... Do you want scinstall to reboot for you (yes/no) [yes]?
- If yes, type no in the Automatic Reboot screen to decline automatic reboot.
- If no, type yes to accept automatic reboot.

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 -ik  \
...
    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 on the First Node shows an example of the output you might see during scinstall processing.

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 Configure Network Time Protocol (NTP) for information on how to suppress these messages under otherwise normal cluster conditions.
If you decline the command, scinstall asks if you want to de-install the Sun Cluster software.
Do you want to de-install the Sun Cluster software (yes/no) [no]?
After scinstall returns you to the Main Menu, you can rerun menu option 1 and provide different answers. Your previous session answers display as the defaults.

Install any Sun Cluster software patches.

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

Reboot the node to establish the cluster.

If you rebooted the node after you installed patches in Step 25, you do not need to reboot the node a second time.

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 additional nodes in the cluster.

Go to How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall).

Example—Installing Sun Cluster Software on the First Node

The following example shows the scinstall command executed and 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. The cluster will have four nodes and uses Ethernet adapters and transport junctions.

 >>> Confirmation <<<
  
    Your responses indicate the following options to scinstall:
  
      scinstall -ik \
           -C sc-cluster \
           -F \
           -T node=phys-schost-1,node=phys-schost-2,node=phys-schost-3,node=phys
-schost-4,authtype=sys \
           -A trtype=dlpi,name=hme1 -A trtype=dlpi,name=hme3 \
           -B type=switch,name=switch1 -B type=switch,name=switch2 \
           -m endpoint=:hme1,endpoint=switch1 \
           -m endpoint=:hme3,endpoint=switch2
  
    Are these the options you want to use (yes/no) [yes]?
  
    Do you want to continue with the install (yes/no) [yes]?
  
Checking device to use for global devices file system ... done
  
Initializing cluster name to "sc-cluster" ... done
Initializing authentication options ... done
Initializing configuration for adapter "hme1" ... done
Initializing configuration for adapter "hme3" ... 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
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.061401232831
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
  
Ensure network 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.10559
  
  
Rebooting ...