How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall) (Sun Cluster 3.1 Software Installation Guide)

Sun Cluster 3.1 Software Installation Guide

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

After you install Sun Cluster software on the first-installed node and establish the cluster, perform this task on each additional node to install in the cluster. 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. Go to How to Configure the Name Service Switch.

Ensure that the first-installed node is successfully installed with Sun Cluster software and that the cluster is established.

For installation procedures to establish a cluster, see How to Install Sun Cluster Software on the First Cluster Node (scinstall).

If you are adding a new node to an existing, fully installed cluster, ensure that you have performed the following tasks.
1. Prepare the cluster to accept a new node.
  
  Follow instructions in the procedure “How to Add a Cluster Node to the Authorized Node List” in “Adding and Removing a Cluster Node” in Sun Cluster 3.1 System Administration Guide.
2. Install Solaris software on the new node.
  
  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 4.

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 8.
- 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–3 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 utility.
# ./scinstall
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.

Caution –
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. If the cluster is still in install mode, you will cause a system panic because of lost quorum if you reboot or shut down the first-installed node.

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

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

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:  2
 
  *** Adding a Node to an Established Cluster ***
...
    Do you want to continue (yes/no) [yes]? yes

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

 >>> Software Installation <<<
  
    Installation of the Sun Cluster framework software packages will only
    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 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

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 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 9 and restart scinstall.

Specify whether to use autodiscovery to configure the cluster transport.

If your configuration does not use Ethernet adapters, answer no and go to Step 17.

 >>> Autodiscovery of Cluster Transport <<<
  
    If you are using ethernet adapters as your cluster transport
    adapters, autodiscovery is the best method for configuring the
    cluster transport.
  
    Do you want to use autodiscovery (yes/no) [yes]?
...
    The following connections were discovered:
  
        node1:adapter switch node2:adapter 
        node1:adapter switch node2:adapter 
  
    Is it okay to add these connections to the configuration (yes/no) [yes]?

Did you use autodiscovery in Step 15?
- If yes, skip to Step 24.
- If no, go to Step 17.

Specify whether this is a two-node cluster.

 >>> Point-to-Point Cables <<<
...
    Is this a two-node cluster (yes/no) [yes]?

Did you specify that this is a two-node cluster?

If yes, specify whether to use transport junctions.

    Does this two-node cluster use transport junctions (yes/no) [yes]?

If no, press Return to continue. You must use transport junctions if a cluster contains three or more nodes.

    Since this is not a two-node cluster, you will be asked to configure
    two transport junctions.
  
Hit ENTER to continue:

Did you specify that the cluster will use transport junctions?

If yes, specify the transport junctions.

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

Specify the first cluster interconnect transport adapter.

Type help to list all transport adapters available to the node.

 >>> Cluster Transport Adapters and Cables <<<
...
    What is the name of the first cluster transport adapter (help)?  adapter

Specify what the first transport adapter connects to.
- If the transport adapter uses a transport junction, specify the name of the junction and its port.
  Name of the junction to which "adapter" is connected [switch1]? ... Use the default port name for the "adapter" connection (yes/no) [yes]?
- If the transport adapter does not use a transport junction, specify the name of the other transport adapter it connects to.
  Name of adapter on "node1" to which "adapter" is connected? adapter

Specify the second cluster interconnect transport adapter.

Type help to list all transport adapters available to the node.
What is the name of the second cluster transport adapter (help)? adapter

Specify what the second transport adapter connects to.
- If the transport adapter uses a transport junction, specify the name of the junction and its port.
  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:
- If the transport adapter does not use a transport junction, specify the name of the other transport adapter it connects to.
  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?
>>> 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 -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 on the First Node 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.

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 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 2 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 27, you do not need to reboot the node a second time.

Caution –
Do not reboot or shut down the first-installed node while any other nodes are being installed, even if you use another node in the cluster 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. If the cluster is still in install mode, you will cause a system panic because of lost quorum if you reboot or shut down the first-installed node. 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.

Repeat this procedure 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 on the Second Node

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

 >>> Confirmation <<<
  
    Your responses indicate the following options to scinstall:
  
      scinstall -ik \
           -C sc-cluster \
           -N phys-schost-1 \
           -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
  
Adding node "phys-schost-2" to the cluster configuration ... done
Adding adapter "hme1" to the cluster configuration ... done
Adding adapter "hme3" to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Adding cable to the cluster configuration ... done
  
Copying the config from "phys-schost-1" ... done
Setting the node ID for "phys-schost-2" ... done (id=2)
  
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.61501001054
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.9853
  
  
Rebooting ...