How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall) (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 Additional Cluster Nodes (`scinstall`)

Perform this procedure to add new nodes to an existing cluster.

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.

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 10/03 System Administration Guide.

Did you preinstall Sun Cluster software?
- If yes, proceed to Step 4.
- 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.

Become superuser on the cluster node to install.

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. Then 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 3 (Add this machine as a node in an existing 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:  3
…
  *** Adding a Node to an Existing Cluster ***
…
    Do you want to continue (yes/no) [yes]?  y

If 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]?  y
  
** Installing SunCluster 3.0 **
        SUNWscr.....done
…
Hit ENTER to continue:

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

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 name of any existing cluster node to be considered 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 installation should stop if the sccheck utility detects errors.
>>> Check <<< … Do you want to run sccheck (yes/no) [yes]? y
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.

When the node passes sccheck validation checks, proceed to the next step.

Specify whether to use autodiscovery to configure the cluster transport.

If your configuration does not use Ethernet adapters, answer no and skip to Step 15.

 >>> 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:adapter1 switch1 node2:adapter1 
        node1:adapter2 switch2 node2:adapter2 
  
    Is it okay to add these connections to the configuration (yes/no) [yes]?

Did you choose to use autodiscovery in Step 13?
- If yes, skip to Step 22.
- If no, proceed to Step 15.

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 cluster 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 is to use transport junctions?

If no, proceed to Step 18.

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

Specify the first cluster-interconnect transport adapter.

Type help to list all transport adapters that are 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 that the first transport adapter 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 that are 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 that the first transport adapter 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]?

Specify automatic reboot.

 >>> Automatic Reboot <<<
…
    Do you want scinstall to reboot for you (yes/no) [yes]? y

Accept or decline the generated scinstall command.

The scinstall command that is 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.

Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

Note –
Unless you have installed your own /etc/inet/ntp.conf file, the scinstall command installs a default ntp.conf file for you. The default file is shipped with references to the maximum possible number of nodes. Therefore, 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, the scinstall utility asks if you want to deinstall 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.

Repeat this procedure on any additional node to install until all nodes are fully configured.

From an active cluster member, prevent any nodes from joining the cluster.
# /usr/cluster/bin/scconf -a -T node=.
-a

Add

-T

Specifies authentication options

node=.

Specifies the node name of dot (.) to add to the authentication list, to prevent any other node from adding itself to the cluster

Alternately, you can use the scsetup(1M) utility. See “How to Add a Cluster Node to the Authorized Node List” in “Adding and Removing a Cluster Node” in Sun Cluster 3.1 10/03 System Administration Guide for procedures.

Set up the name-service look-up order.

Go to How to Configure the Name-Service Switch.

Example – Installing Sun Cluster Software on an Additional Node

The following example shows the scinstall command executed and the messages that the utility logs as scinstall completes installation tasks on the node phys-schost-3. The sponsoring node is phys-schost-1.

 >>> 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 \
           -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-3" 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-3" ... done (id=3)
 
Verifying the major number for the "did" driver with "phys-schost-1" ...done
  
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 that the EEPROM parameter "local-mac-address?" is set to "true" ...done
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 ...