Sun Cluster 3.1 Software Installation Guide

Installing the Software

The following table lists the tasks you perform to install the software.

Table 2–1 Task Map: Installing the Software


Task	For Instructions, Go To …
Plan the layout of your cluster configuration and prepare to install software.	How to Prepare for Cluster Software Installation
(Optional) Install the Cluster Control Panel (CCP) software on the administrative console.	How to Install Cluster Control Panel Software on the Administrative Console
Install the Solaris operating environment and Sun Cluster software to establish new cluster nodes. Choose one of the following three methods:
Method 1 – (New clusters or added nodes) Install Solaris software, then install the Sun Cluster software by using the `scinstall` utility.	How to Install Solaris Software How to Install Sun Cluster Software on the First Cluster Node (`scinstall`) How to Install Sun Cluster Software on Additional Cluster Nodes (`scinstall`)
Method 2 – (New clusters only) Install Solaris software, then install SunPlex^TM Manager and use it to install the Sun Cluster software.	How to Install Solaris Software Using SunPlex Manager to Install Sun Cluster Software
Method 3 – (New clusters or added nodes) Install Solaris software and Sun Cluster software in one operation by using the `scinstall` utility's custom JumpStart option.	How to Install Solaris and Sun Cluster Software (JumpStart)
Configure the name service look-up order.	How to Configure the Name Service Switch
Set up directory paths.	How to Set Up the Root Environment
Install data service software packages.	How to Install Data Service Software Packages
Perform post-installation setup and assign quorum votes.	How to Perform Post-Installation Setup
Install and configure volume manager software:
Install and configure Solstice DiskSuite/Solaris Volume Manager software.	Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software Solstice DiskSuite/Solaris Volume Manager documentation
Install and configure VERITAS Volume Manager software.	Installing and Configuring VxVM Software VERITAS Volume Manager documentation
Configure the cluster.	Configuring the Cluster

How to Prepare for Cluster Software Installation

Before you begin to install software, make the following preparations.

Read the following manuals for information that will help you plan your cluster configuration and prepare your installation strategy.
- Sun Cluster 3.1 Release Notes—Restrictions, bug workarounds, and other late-breaking information.
- Sun Cluster 3.1 Release Notes Supplement—Post-release documentation about additional restrictions, bug workarounds, new features, and other late-breaking information. This document is regularly updated and is published online at the following Web site.
  
  http://docs.sun.com
- Sun Cluster 3.1 Concepts Guide—Overview of the Sun Cluster product.
- Sun Cluster 3.1 Software Installation Guide (this manual)—Planning guidelines and procedures for installing and configuring Solaris, Sun Cluster, and volume manager software.
- Sun Cluster 3.1 Data Service Planning and Administration Guide—Planning guidelines and procedures for installing and configuring data services.
- Documentation for all third-party software products.

Have available all related documentation, including third-party documents.

The following is a partial list of product documentation you might need for reference during cluster installation.
- Solaris software
- Solstice DiskSuite/Solaris Volume Manager software
- VERITAS Volume Manager
- Sun Management Center
- Third-party applications such as ORACLE

Plan your cluster configuration.

Caution –
Plan your cluster installation completely and identify requirements for all data services and third-party products before you begin Solaris and Sun Cluster software installation. Failure to do so might result in installation errors that require that you completely reinstall the Solaris and Sun Cluster software. For example, the Oracle Parallel Fail Safe/Real Application Clusters Guard option of Oracle Parallel Server/Real Application Clusters has special requirements for the hostnames that you use in the cluster. Another example with special requirements is Sun Cluster HA for SAP. You must accommodate these requirements before you install Sun Cluster software because you cannot change hostnames after you install Sun Cluster software.
- Use the planning guidelines in Chapter 1, Planning the Sun Cluster Configuration and in the Sun Cluster 3.1 Data Service Planning and Administration Guide to determine how you will install and configure your cluster.
- Fill out the cluster framework configuration worksheets in the Sun Cluster 3.1 Release Notes and the data services configuration worksheets in the Sun Cluster 3.1 Data Service Release Notes. Use your completed worksheets for reference during the installation and configuration tasks.

Get all necessary patches for your cluster configuration.

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

Do you intend to use Cluster Control Panel software to connect from an administrative console to your cluster nodes?
- If yes, go to How to Install Cluster Control Panel Software on the Administrative Console.
- If no, go to one of the following procedures.
  - If you intend to install Sun Cluster software by using either SunPlex Manager (GUI-based method) or the scinstall(1M) utility (text-based method), go to How to Install Solaris Software to first install Solaris software.
  - To install Solaris and Sun Cluster software in the same operation (JumpStart-based method), go to How to Install Solaris and Sun Cluster Software (JumpStart).

How to Install Cluster Control Panel Software on the Administrative Console

This procedure describes how to install the Cluster Control Panel (CCP) software on the administrative console. The CCP provides a launchpad for the cconsole(1M), ctelnet(1M), and crlogin(1M) tools. Each of these tools provides a multiple-window connection to a set of nodes, plus a common window that sends input to all nodes at one time.

You can use any desktop machine that runs the Solaris 8 or Solaris 9 operating environment as an administrative console. In addition, you can also use the administrative console as a Sun Management Center console and/or server, and as an AnswerBook server. See Sun Management Center documentation for information on how to install Sun Management Center software. See “Sun Cluster AnswerBooks Installation” in Sun Cluster 3.1 Release Notes for information on how to install an AnswerBook server.

Note –

You are not required to use an administrative console. If you do not use an administrative console, perform administrative tasks from one designated node in the cluster.

Ensure that the Solaris 8 or Solaris 9 operating environment and any Solaris patches are installed on the administrative console.

All platforms require Solaris 8 with at least the End User System Support software group.

If you install from the CD-ROM, insert the Sun Cluster 3.1 CD-ROM into the CD-ROM drive of the administrative console.

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.

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

Install the SUNWccon package.
# pkgadd -d . SUNWccon

(Optional) Install the SUNWscman package.
# pkgadd -d . SUNWscman
When you install the SUNWscman package on the administrative console, you can view Sun Cluster man pages from the administrative console before you install Sun Cluster software on the cluster nodes.

If you installed from a CD-ROM, eject the CD-ROM.

Create an /etc/clusters file.

Add your cluster name and the physical node name of each cluster node to the file.
# vi /etc/clusters clustername node1 node2
See the /opt/SUNWcluster/bin/clusters(4) man page for details.

Create an /etc/serialports file.

Add an entry for each node in the cluster to the file. Specify the physical node name, the hostname of the console-access device (such as a terminal concentrator (TC), System Service Processor (SSP), or Sun Fire system controller), and the port number.
- For a Sun Fire 15000 system controller, use telnet(1) port number 23 for the serial port number of each entry.
- For all other console-access devices, use the telnet serial port number, not the physical port number. To determine the telnet serial port number, add 5000 to the physical port number. For example, if a physical port number is 6, the telnet serial port number is 5006.
- For Sun Enterprise 10000 servers, also see the /opt/SUNWcluster/bin/serialports(4) man page for details and special considerations.
# vi /etc/serialports node1 ca-dev-hostname port node2 ca-dev-hostname port
node1, node2

Physical names of the cluster nodes

ca-dev-hostname

Hostname of the console-access device

port

Serial port number

For convenience, add the /opt/SUNWcluster/bin directory to the PATH and the /opt/SUNWcluster/man directory to the MANPATH on the administrative console.

If you installed the SUNWscman package, also add the /usr/cluster/man directory to the MANPATH.

Start the CCP utility.
# /opt/SUNWcluster/bin/ccp clustername
See the procedure “How to Remotely Log In to Sun Cluster” in “Beginning to Administer the Cluster” in Sun Cluster 3.1 System Administration Guide for information about how to use the CCP utility. Also see the ccp(1M) man page.

Install the Solaris operating environment.
- To install Solaris software, go to How to Install Solaris Software.
- To install Solaris and Sun Cluster software by using the scinstall JumpStart option, go to How to Install Solaris and Sun Cluster Software (JumpStart).

How to Install Solaris Software

If you do not use the scinstall(1M) custom JumpStart installation method to install software, perform this task to install the Solaris operating environment on each node in the cluster.

Note –

If your nodes are already installed with the Solaris operating environment, you must still reinstall the Solaris software as described in this procedure to ensure successful installation of Sun Cluster software.

Ensure that the hardware setup is complete and connections are verified before you install Solaris software.

See the Sun Cluster 3.x Hardware Administration Manual and your server and storage device documentation for details.

Ensure that your cluster configuration planning is complete.

See How to Prepare for Cluster Software Installation for requirements and guidelines.

Have available your completed “Local File Systems With Mirrored Root Worksheet” in Sun Cluster 3.1 Release Notes or “Local File Systems with Non-Mirrored Root Worksheet” in Sun Cluster 3.1 Release Notes.

Are you using a naming service?
- If no, go to Step 5. You will set up local hostname information in Step 16.
- If yes, add address-to-name mappings for all public hostnames and logical addresses to any naming services (such as NIS or DNS) used by clients for access to cluster services. See IP Addresses for planning guidelines. See your Solaris system administrator documentation for information about using Solaris naming services.

If you are using a cluster administrative console, display a console screen for each node in the cluster.

If Cluster Control Panel (CCP) is installed and configured on your administrative console, you can use the cconsole(1M) utility to display the individual console screens. CCP also opens a master window from which you can send your input to all individual console windows at the same time.

If you do not use CCP, connect to the consoles of each node individually.

Tip –
To save time, you can install the Solaris operating environment on each node at the same time.

Do the nodes in the cluster use Ethernet adapters?
- If no, go to Step 7.
- If yes, ensure that the local-mac-address? variable is correctly set to true for Ethernet adapters.
  
  Sun Cluster 3.1 software does not support the local-mac-address? variable set to false for Ethernet adapters. This is a change from the requirement for Sun Cluster 3.0 software.
1. Display the value of the local-mac-address? variable.
  - If the node is preinstalled with Solaris software, as superuser run the following command.
    # /usr/sbin/eeprom local-mac-address?
  - If the node is not yet installed with Solaris software, run the following command from the ok prompt.
    ok printenv local-mac-address?
2. Does the command return local-mac-address?=true on each node?
  - If yes, the variable settings are correct. Go to Step 7.
  - If no, change the variable setting on any node that is not set to true.
    - If the node is preinstalled with Solaris software, as superuser run the following command.
      # /usr/sbin/eeprom local-mac-address?=true
    - If the node is not yet installed with Solaris software, run the following command from the ok prompt.
      ok setenv local-mac-address? true
3. Repeat Step a to verify any changes you made in Step b.
  
  The new setting becomes effective at the next system reboot.

Install the Solaris operating environment as instructed in the Solaris installation documentation.

Note –
You must install all nodes in a cluster with the same version of the Solaris operating environment.

You can use any method normally used to install the Solaris operating environment to install the software on new nodes to be installed into a clustered environment. These methods include the Solaris interactive installation program, Solaris JumpStart, and Solaris Web Start.

During Solaris software installation, do the following.
1. Install at least the End User System Support software group.
  - If you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport, the required RSMAPI software packages (SUNWrsm, SUNWrsmx, SUNWrsmo, and SUNWrsmox) are included with the higher-level software groups. If you install the End User System Support software group, you must install the SUNWrsm* packages manually from the Solaris CD-ROM at Step 12.
  - If you intend to use SunPlex Manager, the required Apache software packages (SUNWapchr and SUNWapchu) are included with the higher-level software groups. If you install the End User System Support software group, you must install the SUNWapch* packages manually from the Solaris CD-ROM at Step 13.
  See Solaris Software Group Considerations for information about additional Solaris software requirements.
2. Choose Manual Layout to set up the file systems.
  - Create a file system of at least 512 MBytes for use by the global-devices subsystem. If you intend to use SunPlex Manager to install Sun Cluster software, you must create the file system with a mount-point name of /globaldevices. The /globaldevices mount-point name is the default used by scinstall.
    
    Note –
    Sun Cluster software requires a global-devices file system for installation to succeed.
  - If you intend to use SunPlex Manager to install Solstice DiskSuite software (Solaris 8), configure Solaris Volume Manager software (Solaris 9), or install Sun Cluster HA for NFS or Sun Cluster HA for Apache in addition to installing Sun Cluster software, create a 20–Mbyte file system on slice 7 with a mount-point name of /sds.
    
    Otherwise, create any file system partitions needed to support your volume manager software as described in System Disk Partitions.
3. Choose auto reboot.
  
  Note –
  The Solaris installation tool installs Solaris software and reboots the node before it displays the next prompts.
4. For ease of administration, set the same root password on each node.
5. Answer no when asked whether to enable automatic power-saving shutdown.
  
  You must disable automatic shutdown in Sun Cluster configurations. See the pmconfig(1M) and power.conf(4) man pages for more information.
Note –
The Solaris interface groups feature is disabled by default during Solaris software installation. Interface groups are not supported in a Sun Cluster configuration and should not be enabled. See the ifconfig(1M) man page for more information about Solaris interface groups.

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

Have you added the new node to the cluster's authorized-node list?
- If yes, go to Step 10.
- If no, run scsetup(1M) from another, active cluster node to add the new node's name to the list of authorized cluster nodes. See “Task Map: Adding a Cluster Node to an Existing Cluster” in Sun Cluster 3.1 System Administration Guide for procedures.

Create a mount point on the new node for each cluster file system in the cluster.
1. From another, active node of the cluster, display the names of all cluster file systems.
  % mount | grep global | egrep -v node@ | awk `{print $1}'
2. On the new node, create a mount point for each cluster file system in the cluster.
  % mkdir -p mountpoint
  For example, if the mount command returned the file system name /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the new node you are adding to the cluster.

Is VERITAS Volume Manager (VxVM) installed on any nodes that are already in the cluster?
- If yes, ensure that the same vxio number is used on the VxVM-installed nodes and that the vxio number is available for use on each of the nodes that do not have VxVM installed.
  # grep vxio /etc/name_to_major vxio NNN
  If the vxio number is already in use on a node that does not have VxVM installed, free the number on that node by changing the /etc/name_to_major entry to use a different number.
- If no, go to Step 12.

Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
- If yes and you installed the End User System Support software group, install the SUNWrsm* packages from the Solaris CD-ROM.
  # pkgadd -d . SUNWrsm SUNWrsmx SUNWrsmo SUNWrsmox
- If no, or if you installed a higher-level software group, go to Step 13.

Do you intend to use SunPlex Manager?
- If yes and you installed the End User System Support software group, install the SUNWapch* packages from the Solaris CD-ROM.
  # pkgadd -d . SUNWapchr SUNWapchu
- If no, or if you installed a higher-level software group, go to Step 14.
Apache software packages must already be installed before SunPlex Manager is installed.

Install any Solaris software patches.

See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions. If necessary, view the /etc/release file to see the exact version of Solaris software that is installed on a node.

Install any hardware-related patches and download any needed firmware contained in the hardware patches.

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

Update the /etc/inet/hosts file on each node with all public hostnames and logical addresses for the cluster.

Perform this step regardless of whether you are using a naming service.

Do you intend to use dynamic reconfiguration on Sun Enterprise 10000 servers?
- If yes, on each node add the following entry to the /etc/system file.
  set kernel_cage_enable=1
  This entry becomes effective after the next system reboot. See the Sun Cluster 3.1 System Administration Guide for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.
- If no, go to Step 18.

Install Sun Cluster software on your cluster nodes.
- To use SunPlex Manager, go to Using SunPlex Manager to Install Sun Cluster Software.
- To use scinstall, go to How to Install Sun Cluster Software on the First Cluster Node (scinstall).

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

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

Using SunPlex Manager to Install Sun Cluster Software

Note –

To add a new node to an existing cluster, do not use SunPlex Manager. Instead, go to How to Install Sun Cluster Software on the First Cluster Node (scinstall).

This section describes how to install SunPlex Manager and use it to install Sun Cluster software and establish new cluster nodes. You can also use SunPlex Manager to install one or more of the following additional software products.

(Solaris 8 only) Solstice DiskSuite software—Also configures up to three metasets and associated metadevices, and creates and mounts cluster file systems for each.
Sun Cluster HA for NFS data service
Sun Cluster HA for Apache scalable data service

For Solaris 9, Solaris Volume Manager software is already installed as part of Solaris software installation. You can use SunPlex Manager to configure up to three metasets and associated Solstice DiskSuite metadevices or Solaris Volume Manager volumes, and to create and mount cluster file systems for each.

The following table lists SunPlex Manager installation requirements for these additional software products.

Table 2–4 Requirements to Use SunPlex Manager to Install Software


Software Package	Installation Requirements
Solstice DiskSuite/Solaris Volume Manager	A partition that uses `/sds` as the mount–point name. The partition must be at least 20 Mbytes.
Sun Cluster HA for NFS data service	At least two shared disks of the same size which are connected to the same set of nodes. Solstice DiskSuite software installed, or Solaris Volume Manager software configured, by SunPlex Manager. A logical hostname for use by Sun Cluster HA for NFS. The logical hostname must have a valid IP address that is accessible by all cluster nodes and is on the same subnet as the base hostnames of the cluster nodes.
Sun Cluster HA for Apache scalable data service	At least two shared disks of the same size which are connected to the same set of nodes. Solstice DiskSuite software installed, or Solaris Volume Manager software configured, by SunPlex Manager. A shared address for use by Sun Cluster HA for Apache. The shared address must have a valid IP address that is accessible by all cluster nodes and is on the same subnet as the base hostnames of the cluster nodes.

The following table lists each metaset name and cluster file system mount point created by SunPlex Manager, depending on the number of shared disks connected to the node. For example, if a node has four shared disks connected to it, SunPlex Manager creates the mirror-1 and mirror-2 metasets, but does not create the mirror-3 metaset because the node does not have enough shared disks to create a third metaset.

Table 2–5 Metasets Installed by SunPlex Manager


Shared Disks	Metaset Name	Cluster File System Mount Point	Purpose
First pair of shared disks	`mirror-1`	`/global/mirror-1`	Sun Cluster HA for NFS or Sun Cluster HA for Apache scalable data service, or both
Second pair of shared disks	`mirror-2`	`/global/mirror-2`	unused
Third pair of shared disks	`mirror-3`	`/global/mirror-3`	unused

Note –

If the cluster does not meet the minimum shared disk requirement, SunPlex Manager still installs the Solstice DiskSuite packages. But without sufficient shared disks, SunPlex Manager cannot configure the metasets, metadevices or volumes, or cluster file systems needed to create instances of the data service.

SunPlex Manager recognizes a limited character set to increase security. Characters that are not a part of the set are silently filtered out when HTML forms are submitted to the SunPlex Manager server. The following characters are accepted by SunPlex Manager.

()+,-./0-9:=@A-Z^_a-z{|}~

This filter will potentially cause problems in the following two areas:

Password entry for Sun Open Net Environment (Sun ONE) services – If the password contains unusual characters, these characters will be stripped out resulting in two problems. Either the resulting password will be under 8 characters and will fail, or the application will be configured with a different password than the user expects.
Localization – Alternative character sets (for example: accented characters or Asian characters) will not work for input.

How to Install SunPlex Manager Software

The SunPlex Manager graphical user interface (GUI) provides an easy way to install and administer Sun Cluster software. Follow this procedure to install SunPlex Manager software on your cluster.

Note –

If you intend to install Sun Cluster software by using another method, you do not need to perform this procedure. The scinstall command installs SunPlex Manager for you as part of the installation process.

Perform this procedure on each node of the cluster.

Ensure that Solaris software and patches are installed on each node of the cluster.

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.

Become superuser on a cluster node.

Are Apache software packages installed on the node?
- If yes, go to Step 4.
  
  The Apache software packages are included in the Solaris Entire Distribution software group and all higher-level software groups. If you installed a lower-level software group, use the pkginfo(1) command to determine whether the software packages in Step c are already installed.
- If no, install Apache software packages.
1. If you install from the CD-ROM, insert the Solaris 8 Software 2 of 2 CD-ROM into the CD-ROM drive of the node.
  
  If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM.
2. Change to the /cdrom/sol_8_sparc/Solaris_8/Product directory.
  # cd /cdrom/sol_8_sparc/Solaris_8/Product
  For Solaris 9, change to the /cdrom/cdrom0/Solaris_9/Product directory.
  # cd /cdrom/cdrom0/Solaris_9/Product
3. Install the Apache software packages in the following order.
  # pkgadd -d . SUNWapchr SUNWapchu SUNWapchd
4. Eject the Solaris CD-ROM.
5. Install any Apache software patches.
  
  See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.

Install the SunPlex Manager software packages.
1. If you install from the CD-ROM, insert the Sun Cluster 3.1 CD-ROM into the CD-ROM drive of the node.
  
  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.
2. Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages 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/Packages
3. Install the SunPlex Manager software packages and answer yes for all prompts.
  # pkgadd -d . SUNWscva SUNWscvr SUNWscvw
4. Eject the Sun Cluster CD-ROM.

Repeat Step 2 through Step 4 on each node of the cluster.

Is the root password the same on every node of the cluster?
- If yes, go to Step 7.
- If no, set the root password to the same value on each node of the cluster. If necessary, also use chkey(1) to update the RPC key pair.
  # passwd Enter new password # chkey -p
The root password must be the same on all nodes in the cluster to use the root password to access SunPlex Manager.

Do you intend to set up additional user accounts to access SunPlex Manager?
- If yes, go to Step 8.
- If no, go to How to Install Sun Cluster Software (SunPlex Manager) to install Sun Cluster software on your cluster nodes.
Users who do not use the root system account nor have a user account set up on a particular node cannot access the cluster through SunPlex Manager from that node. Also, users cannot manage that node through another cluster node to which the users do have access.

Determine how to set up user accounts to access SunPlex Manager.

In addition to root-user access, users can log in to SunPlex Manager with a user account that has role-based access control (RBAC). Go to one of the procedures listed in the following table to set up user accounts.

Table 2–6 Methods to Set Up SunPlex Manager User Accounts


Method	Go to This Procedure
Add RBAC authorization to an existing user account.	How to Add RBAC Authorization to an Existing User Account
Create a new user account that has RBAC authorization.	How to Create a New User Account

Note –

If you assign RBAC authorization to a non-root user account, that user account can perform administrative actions usually performed only by root.

See “Role-Based Access Control” in System Administration Guide, Volume 2 or “Using the Solaris Management Tools With RBAC (Task Map)” in System Administration Guide: Basic Administration for more information.

How to Add RBAC Authorization to an Existing User Account

Add RBAC authorization to an existing user account. This enables the user to log in to SunPlex Manager by using the user's regular system password and have access to full SunPlex Manager functionality.

Note –

If you assign RBAC authorization to a non-root user account, that user account can perform a set of administrative actions usually performed only by root.

Become superuser on a node of the cluster.

Add the following entry to the /etc/user_attr file.

# vi /etc/user_attr
username::::type=normal;auths=solaris.cluster.admin

Repeat on each remaining node of the cluster.

Use SunPlex Manager to install Sun Cluster software.

Go to How to Install Sun Cluster Software (SunPlex Manager).

How to Create a New User Account

Create a new user account on all nodes the cluster.

Note –

If you assign RBAC authorization to a non-root user account, that user account can perform a set of administrative actions usually performed only by root.

Become superuser on a node of the cluster.

Create the new user account.
# useradd -d dir -A solaris.cluster.admin login
-d dir

Specifies the home directory of the new user

-A solaris.cluster.admin

Assigns solaris.cluster.admin authorization to the new user account

login

Name of the new user account

Note –
The user name must be unique and must not already exist either on the local machine or in the network name service.

See the useradd(1M) man page for more information about creating user accounts.

Set the password.
# passwd login

Repeat on each remaining node of the cluster.

Ensure that the password for the user account is the same on all nodes of the cluster.

Use SunPlex Manager to install Sun Cluster software.

Go to How to Install Sun Cluster Software (SunPlex Manager).

How to Install Sun Cluster Software (SunPlex Manager)

Note –

To add a new node to an existing cluster, do not use SunPlex Manager. Instead, go to How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall).

Perform this procedure to use SunPlex Manager to install Sun Cluster software and patches on all nodes in the cluster in a single operation. In addition, you can use this procedure to install Solstice DiskSuite software and patches (Solaris 8) or to configure Solaris Volume Manager mirrored disksets (Solaris 9). If you use SunPlex Manager to install Solstice DiskSuite software or to configure Solaris Volume Manager disksets, you can also install the Sun Cluster HA for NFS data service or the scalable Sun Cluster HA for Apache data service or both.

The installation process might take from 30 minutes to two or more hours, depending on the number of cluster nodes, choice of data services, and number of disks in your cluster configuration.

Ensure that SunPlex Manager software is installed on each node of the cluster.

See the installation procedures in How to Install SunPlex Manager Software.

Ensure that the cluster configuration meets the requirements to use SunPlex Manager to install software.

See Using SunPlex Manager to Install Sun Cluster Software for installation requirements and restrictions.

Do you intend to install Sun Cluster HA for NFS or Sun Cluster HA for Apache?
- If no, go to Step 4.
- If yes, ensure that the cluster configuration meets all applicable requirements. See Using SunPlex Manager to Install Sun Cluster Software.

Prepare file system paths to a CD-ROM image of each software product you intend to install.
1. Provide each CD-ROM image in a location that is available to each node.
  
  The CD-ROM images must be accessible to all nodes of the cluster from the same file system path. These paths can be one or more of the following locations.
  - CD-ROM drives exported to the network from machines outside the cluster.
  - Exported file systems on machines outside the cluster.
  - CD-ROM images copied to local file systems on each node of the cluster. The local file system must use the same name on each node.
2. Record the path to each CD-ROM image.
  
  You will provide this information to SunPlex Manager in Step 17.

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 6.
- 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–7 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

Are there any patches required to support Sun Cluster or Solstice DiskSuite software?
- If yes, go to Step 7.
- If no, go to Step 9.

Do you intend to use SunPlex Manager to install patches?
- If yes, go to Step 8.
- If no, manually install all patches required to support Sun Cluster or Solstice DiskSuite software before you use SunPlex Manager, then go to Step 9.

Copy patches required for Sun Cluster or Solstice DiskSuite software into a single directory on a file system that is available to each node.
1. Ensure that only one version of each patch is present in this patch directory.
  
  If the patch directory contains multiple versions of the same patch, SunPlex Manager cannot determine the correct patch dependency order.
2. Ensure that the patches are uncompressed.
3. Record the path to the patch directory.
  
  You will provide this information to SunPlex Manager in Step 17.

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
- “Network Resources Worksheet” in Sun Cluster 3.1 Release Notes
See Chapter 1, Planning the Sun Cluster Configuration and the Sun Cluster 3.1 Data Service Planning and Administration Guide for planning guidelines.

Start SunPlex Manager.
1. From the administrative console or any other machine outside the cluster, launch a browser.
2. Disable the browser's Web proxy.
  
  SunPlex Manager installation functionality is incompatible with Web proxies.
3. Ensure that disk caching and memory caching is enabled.
  
  The disk cache and memory cache size must be greater than 0.
4. From the browser, connect to port 3000 on a node of the cluster.
  https://node:3000/
  The Sun Cluster Installation screen displays in the browser window.
  
  Note –
  If SunPlex Manager displays the administration interface instead of the Sun Cluster Installation screen, Sun Cluster software is already installed on that node. Check that the name of the node in the URL is the correct name of the cluster node to install.
5. If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.

In the Sun Cluster Installation screen, verify that the cluster meets the listed requirements for using SunPlex Manager.
- The Solaris End User Software Group or higher is installed.
- Root disk partitions include a 512-MByte slice with the mount point /globaldevices.
- Root disk partitions include a 20-MByte slice with the mount point /sds.
- File system paths to all needed CD-ROM images and patches are set up, as described in Step 4 through Step 8.
If you meet all listed requirements, click Next to continue to the next screen.

Type a name for the cluster and select the number of nodes in your cluster.

The default number of nodes displayed might be higher than the number of nodes you intend to install in your cluster. If this happens, select the correct number of nodes you will install. This might occur if other nodes that are ready to be installed by SunPlex Manager use the same public network as the nodes you intend to install.

Click Next to continue.

Tip –
You can use the Back button to return to a previous screen and change your information. However, SunPlex Manager does not save the information you supplied in the later screens. When you click Next, you must again type or select your configuration information in those screens.

Type the name of each cluster node.

SunPlex Manager supplies as defaults the names of nodes it finds on the public network which are ready to be installed by SunPlex Manager. If you specify a larger number of nodes to install than exist on the network, SunPlex Manager supplies additional default names. These additional names follow the naming convention phys-clustername-N.

Note –
SunPlex Manager might list nodes other than the ones you intend to install in your cluster. This would happen if those other nodes use the same public network as the nodes you are installing, and if those nodes are installed with SunPlex Manager software but not yet installed with Sun Cluster software. If SunPlex Manager supplies the name of a node that you do not want to install in your cluster, type over it with the correct node name.

Click Next to continue.

From the pull-down lists for each node, select the names of the two adapters used for the private interconnects.

Refer to your completed “Cluster Interconnect Worksheet” for the appropriate adapter names for each node.

Click Next to continue.

Choose whether to install Solstice DiskSuite software (Solaris 8) or to configure Solaris Volume Manager mirrored disksets (Solaris 9).

You must install Solstice DiskSuite software (Solaris 8) or configure Solaris Volume Manager mirrored disksets (Solaris 9) if you intend to install the Sun Cluster HA for NFS or Sun Cluster HA for Apache data service.

Caution –
When SunPlex Manager installs Solstice DiskSuite software or configures Solaris Volume Manager software, any data on all shared disks will be lost.

Click Next to continue.

Choose whether to install Sun Cluster HA for NFS, Sun Cluster HA for Apache, or both.

Refer to your completed “Network Resources” worksheet for the appropriate logical hostname or shared address.
- For Sun Cluster HA for NFS, also specify the logical hostname the data service will use.
- For Sun Cluster HA for Apache, also specify the shared address the data service will use.
Click Next to continue.

Type the path for each CD-ROM image needed to install the packages you specified, and optionally the path for the patch directory.

Type each path in the appropriate path field for each software package, as shown in Table 2–8.
Each specified path for a CD-ROM image must be the directory which contains the .cdtoc file for the CD-ROM.
For any software package you do not install, leave the relevant path field blank.
If you have already installed the required patches, leave the Patch Directory Path field blank.

Table 2–8 CD-ROM Image Path Fields for Software Packages


Software Package to Install	Name of CD-ROM Image Path Field
Solstice DiskSuite	Solaris CD-ROM Path
Sun Cluster	Sun Cluster 3.1 CD-ROM Path
Sun Cluster HA for NFS, Sun Cluster HA for Apache	Sun Cluster 3.1 Agents CD-ROM Path
Sun Cluster patches, Solstice DiskSuite patches	Patch Directory Path

Click Next to continue.

Is the information you supplied correct as displayed in the Confirm Information screen?
- If yes, go to Step 19.
- If no, perform the following steps to correct the configuration information.
1. Click Back until you return to the screen with the information to change.
  
  Note –
  When you click Back to back up to a previous screen, any information you typed in the subsequent screens is lost.
2. Type the correct information and click Next.
3. Retype or reselect the information in each screen until you return to the Confirm Information screen.
4. Verify that the information in the Confirm Information screen is now correct.

Click Begin Installation to start the installation process.

Note –
Do not close the browser window or change the URL during the installation process.
1. If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.
2. If the browser prompts for login information, type the appropriate user ID and password for the node you connect to.
During installation, the screen displays brief messages about the status of the cluster installation process. When installation is complete, the browser displays the cluster monitoring and administration GUI.

SunPlex Manager installation output is logged in the /var/cluster/spm directory. 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.

If during installation the sccheck utility detects any problems, it displays information about the problems found and prompts you for your next action.
- Click Cancel to stop installation, correct the problem detected by sccheck, then return to Step d and restart SunPlex Manager.
- Alternately, if you can correct the problem without quitting SunPlex Manager, correct the problem and click Retry Validation to run sccheck again.
- 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, click Continue Installation.

Use SunPlex Manager to verify quorum assignments and modify them, if necessary.

For clusters with three or more nodes, using shared quorum devices is optional. SunPlex Manager might or might not have assigned quorum votes to any quorum devices, depending on whether appropriate shared disks were available. You can use SunPlex Manager to designate quorum devices and reassign quorum votes in the cluster.

Set up the name service look-up order.

Go to How to Configure the Name Service Switch.

How to Install Solaris and Sun Cluster Software (JumpStart)

This procedure describes how to set up and use the scinstall(1M) custom JumpStart installation method. This method installs both Solaris and Sun Cluster software on all cluster nodes in a single operation and establish the cluster. You can also use this procedure to add new nodes to an existing cluster.

Ensure that the hardware setup is complete and connections are verified before you install Solaris software.

See the Sun Cluster 3.x Hardware Administration Manual and your server and storage device documentation for details on how to set up the hardware.

Ensure that your cluster configuration planning is complete.

See How to Prepare for Cluster Software Installation for requirements and guidelines.

Have available the following information.
- The Ethernet address of each cluster node
- The following completed configuration planning worksheets:
  - “Local File Systems With Mirrored Root” in Sun Cluster 3.1 Release Notes or “Local File Systems with Non-Mirrored Root” in Sun Cluster 3.1 Release Notes
  - “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 Solaris Operating Environment and Planning the Sun Cluster Environment for planning guidelines.

Are you using a naming service?
- If no, go to Step 5. You will set up the necessary hostname information in Step 31.
- If yes, add address-to-name mappings for all public hostnames and logical addresses, as well as the IP address and hostname of the JumpStart server, to any naming services (such as NIS or DNS) used by clients for access to cluster services. See IP Addresses for planning guidelines. See your Solaris system administrator documentation for information about using Solaris naming services.

Are you installing a new node to an existing cluster?
- If yes, run scsetup(1M) from another, active cluster node to add the new node's name to the list of authorized cluster nodes. See “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.
- If no, go to Step 6.

As superuser, set up the JumpStart install server for Solaris operating environment installation.

See the setup_install_server(1M) and add_install_client(1M) man pages and “Preparing Custom JumpStart Installations” in Solaris 8 Advanced Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide for instructions on how to set up a JumpStart install server.

When you set up the install server, ensure that the following requirements are met.
- The install server is on the same subnet as the cluster nodes, but is not itself a cluster node.
- The install server installs the release of the Solaris operating environment required by the Sun Cluster software.
- A custom JumpStart directory exists for JumpStart installation of Sun Cluster. This jumpstart-dir directory must contain a copy of the check(1M) utility and be NFS exported for reading by the JumpStart install server.
- Each new cluster node is configured as a custom JumpStart install client that uses the custom JumpStart directory set up for Sun Cluster installation.

Create a directory on the JumpStart install server to hold your copy of the Sun Cluster 3.1 CD-ROM, if one does not already exist.

In the following example, the /export/suncluster directory is created for this purpose.
# mkdir -m 755 /export/suncluster

Copy the Sun Cluster CD-ROM to the JumpStart install server.
1. Insert the Sun Cluster 3.1 CD-ROM into the CD-ROM drive on the JumpStart install server.
  
  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.
2. 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
3. Copy the CD-ROM to a new directory on the JumpStart install server.
  
  The scinstall command creates the new installation directory as it copies the CD-ROM files. The installation directory name /export/suncluster/sc31 is used here as an example.
  # ./scinstall -a /export/suncluster/sc31
4. Eject the CD-ROM.
  # cd / # eject cdrom
5. Ensure that the Sun Cluster 3.1 CD-ROM image on the JumpStart install server is NFS exported for reading by the JumpStart install server.
  
  See “Solaris NFS Environment” in System Administration Guide, Volume 3 or “Managing Network File Systems (Overview)” in System Administration Guide: Resource Management and Network Services and the share(1M) and dfstab(4) man pages for more information about automatic file sharing.

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

Have you added the node to the cluster's authorized-node list?
- If yes, go to Step 11.
- If no, run scsetup(1M) from any existing cluster node to add the new node's name to the list of authorized cluster nodes. See “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.

From the JumpStart install server, start the scinstall(1M) utility.

The path /export/suncluster/sc31 is used here as an example of the installation directory you created.
# cd /export/suncluster/sc30/SunCluster_3.1/Sol_ver/Tools # ./scinstall
Note –
In the CD-ROM path, replace ver with 8 (for Solaris 8) or 9 (for Solaris 9)

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.

From the Main Menu, type 3 (Configure a cluster to be JumpStarted from this install server).

This option is used to configure customer JumpStart finish scripts. JumpStart uses these finish scripts to install the Sun Cluster software.

 *** 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:  3
 
 *** Custom JumpStart ***
...
    Do you want to continue (yes/no) [yes]?

Note –

If option 3 does not have an asterisk in front, the option is disabled because JumpStart setup is not complete or has an error. Exit the scinstall utility, repeat Step 6 through Step 8 to correct JumpStart setup, then restart the scinstall utility.

Specify the JumpStart directory name.

 >>> Custom JumpStart Directory <<<
....
    What is your JumpStart directory name?  jumpstart-dir

Specify the name of the cluster.

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

Specify the names of all cluster nodes.

 >>> Cluster Nodes <<<
...
    Please list the names of all cluster nodes planned for the initial
    cluster configuration. You must enter at least two nodes. List one
    node name per line. When finished, type Control-D:
 
    Node name:  node1
    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 15. 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, go to Step 20.

Specify the first cluster interconnect transport adapter of the first node.

 >>> Cluster Transport Adapters and Cables <<<
...
 For node "node1",
    What is the name of the first cluster transport adapter?  adapter

Specify the connection endpoint of the first adapter.
- If the cluster does not use transport junctions, specify the name of the adapter on the second node to which this adapter connects.
  ... Name of adapter on "node2" to which "adapter" is connected? adapter
- If the cluster uses transport junctions, specify the name of the first transport junction and its port.
  ... For node "node1", Name of the junction to which "adapter" is connected? switch ... For node "node1", Use the default port name for the "adapter" connection (yes/no) [yes]?
  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

Specify the second cluster interconnect transport adapter of the first node.

...
 For node "node1",
    What is the name of the second cluster transport adapter?  adapter

Specify the connection endpoint of the second adapter.
- If the cluster does not use transport junctions, specify the name of the adapter on the second node to which this adapter connects.
  ... Name of adapter on "node2" to which "adapter" is connected? adapter
- If the cluster uses transport junctions, specify the name of the second transport junction and its port.
  ... For node "node1", Name of the junction to which "adapter" is connected? switch ... For node "node1", Use the default port name for the "adapter" connection (yes/no) [yes]?
  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

Does this cluster use transport junctions?
- If yes, repeat Step 20 through Step 23 for each additional cluster node.
- If no, go to Step 25.

Specify the global devices file system name for each cluster node.

 >>> Global Devices File System <<<
...
    The default is to use /globaldevices.
 
 For node "node1",
    Is it okay to use this default (yes/no) [yes]? 
 
 For node "node2",
    Is it okay to use this default (yes/no) [yes]?

Accept or decline the generated scinstall commands.

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

 >>> Confirmation <<<
 
    Your responses indicate the following options to scinstall:
-----------------------------------------
 For node "node1",
      scinstall -c jumpstart-dir -h node1  \
...
    Are these the options you want to use (yes/no) [yes]? 
-----------------------------------------
 For node "node2",
      scinstall -c jumpstart-dir -h node2  \
...
    Are these the options you want to use (yes/no) [yes]? 
-----------------------------------------
    Do you want to continue with JumpStart set up (yes/no) [yes]?

If you do not accept the generated commands, the scinstall utility returns you to the Main Menu. From there you can rerun menu option 3 and provide different answers. Your previous answers display as the defaults.

If necessary, make adjustments to the default class file, or profile, created by scinstall.

The scinstall command creates the following autoscinstall.class default class file in the jumpstart-dir/autoscinstall.d/3.1 directory.

install_type    initial_install
system_type     standalone
partitioning    explicit
filesys         rootdisk.s0 free /
filesys         rootdisk.s1 750  swap
filesys         rootdisk.s3 512  /globaldevices
filesys         rootdisk.s7 20
cluster         SUNWCuser        add
package         SUNWman          add

The default class file installs the End User System Support software group (SUNWCuser) of Solaris software. If your configuration has additional Solaris software requirements, change the class file accordingly. See Solaris Software Group Considerations for more information.

You can change the profile in one of the following ways.

Edit the autoscinstall.class file directly. These changes are applied to all nodes in all clusters that use this custom JumpStart directory.
Update the rules file to point to other profiles, then run the check utility to validate the rules file.

As long as the Solaris operating environment install profile meets minimum Sun Cluster file system allocation requirements, there are no restrictions on other changes to the install profile. See System Disk Partitions for partitioning guidelines and requirements to support Sun Cluster 3.1 software. For more information about JumpStart profiles, see “Preparing Custom JumpStart Installations” in Solaris 8 Advanced Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide.

Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
- If yes and you install the End User System Support software group, add the following entries to the default class file as described in Step 27.
  package SUNWrsm add package SUNWrsmx add package SUNWrsmo add package SUNWrsmox add
  In addition, you must create or modify a post-installation finish script at Step 33 to install the Sun Cluster packages to support the RSMAPI and SCI-PCI adapters.
  
  If you install a higher software group than End User System Support, the SUNWrsm* packages are installed with the Solaris software and do not need to be added to the class file.
- If no, go to Step 29.

Do you intend to use SunPlex Manager?
- If yes and you install the End User System Support software group, add the following entries to the default class file as described in Step 27.
  package SUNWapchr add package SUNWapchu add
  If you install a higher software group than End User System Support, the SUNWrsm* packages are installed with the Solaris software and do not need to be added to the class file.
- If no, go to Step 30.

Set up Solaris patch directories.
1. Create jumpstart-dir/autoscinstall.d/nodes/node/patches directories on the JumpStart install server.
  
  Create one directory for each node in the cluster, where node is the name of a cluster node. Alternately, use this naming convention to create symbolic links to a shared patch directory.
  # mkdir jumpstart-dir/autoscinstall.d/nodes/node/patches
2. Place copies of any Solaris patches into each of these directories.
  
  Also place copies of any hardware-related patches that must be installed after Solaris software is installed into each of these directories.

Set up files to contain the necessary hostname information locally on each node.
1. On the JumpStart install server, create files named jumpstart-dir/autoscinstall.d/nodes/node/archive/etc/inet/hosts.
  
  Create one file for each node, where node is the name of a cluster node. Alternately, use this naming convention to create symbolic links to a shared hosts file.
2. Add the following entries into each file.
  - IP address and hostname of the NFS server that holds a copy of the Sun Cluster CD-ROM image. This could be the JumpStart install server or another machine.
  - IP address and hostname of each node in the cluster.

Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
- If yes, follow instructions in Step 33 to set up a post-installation finish script to install the following additional packages. Install the appropriate packages from the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages directory of the Sun Cluster 3.1 CD-ROM in the order given in the following table.
  
  Note –
  In the CD-ROM path, replace ver with 8 (for Solaris 8) or 9 (for Solaris 9)
  
  Table 2–9 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
- If no, go to Step 33 if you intend to add your own post-installation finish script. Otherwise, skip to Step 34.

(Optional) Add your own post-installation finish script.

Note –
If you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport, you must modify the finish script into install the Sun Cluster SUNWscrif software package. This package is not automatically installed by scinstall.

You can add your own finish script, which is run after the standard finish script installed by the scinstall command. See “Preparing Custom JumpStart Installations” in Solaris 8 Advanced Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide for information about creating a JumpStart finish script.
1. Name your finish script finish.
2. Copy your finish script to the jumpstart-dir/autoscinstall.d/nodes/node directory, one directory for each node in the cluster.
  
  Alternately, use this naming convention to create symbolic links to a shared finish script.

If you use an administrative console, display a console screen for each node in the cluster.

If cconsole(1M) is installed and configured on your administrative console, you can use it to display the individual console screens. Otherwise, you must connect to the consoles of each node individually.

From the ok PROM prompt on the console of each node, type the boot net - install command to begin the network JumpStart installation of each node.
ok boot net - install
Note –
The dash (-) in the command must be surrounded by a space on each side.

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.

When the installation is successfully completed, each node is fully installed as a new cluster node.

Note –
The Solaris interface groups feature is disabled by default during Solaris software installation. Interface groups are not supported in a Sun Cluster configuration and should not be reenabled. See the ifconfig(1M) man page for more information about Solaris interface groups.

Are you installing a new node to an existing cluster?
- If no, go to Step 37.
- If yes, create mount points on the new node for all existing cluster file systems.
1. From another, active node of the cluster, display the names of all cluster file systems.
  % mount | grep global | egrep -v node@ | awk '{print $1}'
2. On the node you added to the cluster, create a mount point for each cluster file system in the cluster.
  % mkdir -p mountpoint
  For example, if a file system name returned by the mount command is /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the node being added to the cluster.
  
  Note –
  The mount points become active after you reboot the cluster in Step 39.
3. Is VERITAS Volume Manager (VxVM) installed on any nodes that are already in the cluster?
  - If yes, ensure that the same vxio number is used on the VxVM-installed nodes and that the vxio number is available for use on each of the nodes that do not have VxVM installed.
    # grep vxio /etc/name_to_major vxio NNN
    If the vxio number is already in use on a node that does not have VxVM installed, free the number on that node by changing the /etc/name_to_major entry to use a different number.
  - If no, go to Step 37.

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.

Do you intend to use dynamic reconfiguration on Sun Enterprise 10000 servers?
- If yes, on each node add the following entry to the /etc/system file.
  set kernel_cage_enable=1
  This entry becomes effective after the next system reboot. See the Sun Cluster 3.1 System Administration Guide for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.
- If no, go to Step 39.

Did you add a new node to an existing cluster, or install Sun Cluster software patches that require you to reboot the entire cluster, or both?
- If no, reboot the individual node if any patches you installed require a node reboot or if any other changes you made require a reboot to become active.
- If yes, perform a reconfiguration reboot as instructed in the following steps.
1. From one node, shut down the cluster.
  # scshutdown
  Note –
  Do not reboot the first-installed node of the cluster until after the cluster is shut down.
2. Reboot each node in the cluster.
  ok boot
Until cluster install mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster that is still in install mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum and the entire cluster shuts down. 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.

Set up the name service look-up order.

Go to How to Configure the Name Service Switch.

How to Configure the Name Service Switch

Perform this task on each node in the cluster.

Become superuser on the cluster node.

Edit the /etc/nsswitch.conf file.
1. Verify that cluster is the first source look-up for the hosts and netmasks database entries.
  
  This order is necessary for Sun Cluster software to function properly. The scinstall(1M) command adds cluster to these entries during installation.
2. (Optional) To increase availability to data services if the naming service becomes unavailable, change the lookup order of the following entries.
  - For the hosts and netmasks database entries, place files after cluster.
    
    For Sun Cluster HA for NFS, insert [SUCCESS=return] after files and before name services. This ensures that, if the node succeeds in resolving a name locally, it does not contact the listed name service(s) but instead returns success immediately.
    hosts: cluster files [SUCCESS=return] nis
  - For all other database entries, place files first in look-up order.
  If the [NOTFOUND=return] criterion becomes the last item of an entry after you modify the lookup order, the criterion is no longer necessary. You can either delete the [NOTFOUND=return] criterion from the entry or leave it in, in which case it is ignored.
The following example shows partial contents of an /etc/nsswitch.conf file. The look-up order for the hosts and netmasks database entries is first cluster, then files. The look-up order for other entries begins with files. The [NOTFOUND=return] criterion is removed from the entries.
# vi /etc/nsswitch.conf ... passwd: files nis group: files nis ... hosts: cluster files nis ... netmasks: cluster files nis ...
See the nsswitch.conf(4) man page for more information about nsswitch.conf file entries.

Set up your root user's environment.

Go to How to Set Up the Root Environment.

How to Set Up the Root Environment

Perform these tasks on each node in the cluster.

Note –

In a Sun Cluster configuration, user initialization files for the various shells must verify that they are run from an interactive shell before they attempt to output to the terminal. Otherwise, unexpected behavior or interference with data services might occur. See “Customizing a User's Work Environment” in System Administration Guide, Volume 1 (Solaris 8) or “Customizing a User's Work Environment” in System Administration Guide: Basic Administration (Solaris 9) for more information.

Become superuser on a cluster node.

Modify the .cshrc file PATH and MANPATH entries.
1. Set the PATH to include /usr/sbin and /usr/cluster/bin.
  - For VERITAS Volume Manager (VxVM), also set your PATH to include /etc/vx/bin.
  - If you will install the VRTSvmsa package, also add /opt/VRTSvmsa/bin to your PATH for VxVM 3.2 or earlier, or add /opt/VRTSob/bin to your PATH for VxVM 3.5.
  - For VERITAS File System (VxFS), also set your PATH to include /opt/VRTSvxfs/sbin, /usr/lib/fs/vxfs/bin, and /etc/fs/vxfs.
2. Set the setting the MANPATH to include /usr/cluster/man. Also include the volume manager-specific paths:
  - For Solstice DiskSuite/Solaris Volume Manager software, set your MANPATH to include /usr/share/man.
  - For VxVM, set your MANPATH to include the following path.
    - For VxVM 3.1 and earlier, use /opt/VRTSvxvm/man.
    - For VxVM 3.1.1 and later, use /opt/VRTS/man.
  - For VxVM 3.2 or earlier, if you will install the VRTSvmsa package, also add /opt/VRTSvmsa/man to your MANPATH.
  - For VxFS, also set your MANPATH to include /opt/VRTS/man.

(Optional) For ease of administration, set the same root password on each node, if you have not already done so.

Repeat Step 1 through Step 3 on each remaining cluster node.

Install data service software packages.

Go to How to Install Data Service Software Packages.

How to Install Data Service Software Packages

Perform this task on each cluster node.

Note –

If you used SunPlex Manager to install Sun Cluster HA for NFS or Sun Cluster HA for Apache, or both, and you do not intend to install any other data services, you do not need to perform this procedure. Instead, go to How to Perform Post-Installation Setup.

Become superuser on a cluster node.

If you install from the CD-ROM, insert the Sun Cluster 3.1 Agents CD-ROM into the CD-ROM drive on the node.

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.

To add data services, type 4 (Add support for a new data service to this cluster node).

Follow the prompts to select all data services to install.

Note –
You must install the same set of data service packages on each node, even if a node is not expected to host resources for an installed data service.

If you installed from a CD-ROM, eject the CD-ROM.

Install any Sun Cluster data service patches.

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

You do not have to reboot after you install Sun Cluster data service patches unless a reboot is specified by the patch special instructions. If a patch instruction requires that you reboot, first shut down the cluster by using the scshutdown(1M) command, then reboot the each node in the cluster.

Note –
Until cluster install mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster which is still in install mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum and the entire cluster shuts down. 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 Step 1 through Step 6 on each remaining cluster node.

Perform post-installation setup and assign quorum votes.

Go to How to Perform Post-Installation Setup.

How to Perform Post-Installation Setup

Perform this procedure one time only, after the cluster is fully formed.

Verify that all nodes have joined the cluster.

From one node, verify that all nodes have joined the cluster.

Run the scstat(1M) command to display a list of the cluster nodes. You do not need to be logged in as superuser to run this command.

% scstat -n

Output resembles the following.

-- Cluster Nodes --
                   Node name      Status
                   ---------      ------
  Cluster node:    phys-schost-1  Online
  Cluster node:    phys-schost-2  Online

On each node, verify device connectivity to the cluster nodes.

Run the scdidadm(1M) command to display a list of all the devices that the system checks. You do not need to be logged in as superuser to run this command.

% scdidadm -L

The list on each node should be the same. Output resembles the following.

1       phys-schost-1:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1
2       phys-schost-1:/dev/rdsk/c1t1d0 /dev/did/rdsk/d2
2       phys-schost-2:/dev/rdsk/c1t1d0 /dev/did/rdsk/d2
3       phys-schost-1:/dev/rdsk/c1t2d0 /dev/did/rdsk/d3
3       phys-schost-2:/dev/rdsk/c1t2d0 /dev/did/rdsk/d3
...

Determine the global device ID (DID) of each shared disk you will configure as a quorum device.

Use the scdidadm output from Step 2 to identify the DID name of each shared disk you will configure as a quorum device. For example, the output in the previous substep shows that global device d2 is shared by phys-schost-1 and phys-schost-2. You will use this information in Step 8. See Quorum Devices for further information about planning quorum devices.

Are you adding a new node to an existing cluster?
- If yes, you might need to update the quorum configuration to accommodate your cluster's new configuration. See the Sun Cluster 3.1 Concepts Guide for information about quorum. To change the quorum configuration, follow procedures in “Administering Quorum” in Sun Cluster 3.1 System Administration Guide. When the quorum configuration is satisfactory, go to Step 12.
- If no, go to Step 6.

Did you use SunPlex Manager to install Sun Cluster software?
- If yes, skip to Step 11. During Sun Cluster installation, SunPlex Manager assigns quorum votes and removes the cluster from install mode for you.
- If no, go to Step 6.

Become superuser on one node of the cluster.

Start the scsetup(1M) utility.
# scsetup
The Initial Cluster Setup screen is displayed.

Note –
If the Main Menu is displayed instead, initial cluster setup was already successfully performed. Skip to Step 11.

If the quorum setup process is interrupted or fails to complete successfully, rerun scsetup.

At the prompt Do you want to add any quorum disks?, configure at least one shared quorum device if your cluster is a two-node cluster.

A two-node cluster remains in install mode until a shared quorum device is configured. After the scsetup utility configures the quorum device, the message Command completed successfully is displayed. If your cluster has three or more nodes, quorum device configuration is optional.

At the prompt Is it okay to reset "installmode"?, answer Yes.

After the scsetup utility sets quorum configurations and vote counts for the cluster, the message Cluster initialization is complete is displayed and the utility returns you to the Main Menu.

From any node, verify the device and node quorum configurations.
% scstat -q

From any node, verify that cluster install mode is disabled.

You do not need to be superuser to run this command.

% scconf -p | grep "Cluster install mode:"
Cluster install mode:                                  disabled

Install volume management software.
- To install Solstice DiskSuite software or configure Solaris Volume Manager software, go to Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software.
- To install VERITAS Volume Manager software, go to Installing and Configuring VxVM Software.

How to Uninstall Sun Cluster Software To Correct Installation Problems

Perform this procedure if the installed node cannot join the cluster or if you need to correct configuration information, for example, the transport adapters.

Note –

If the node has already joined the cluster and is no longer in install mode (see Step 11 of How to Perform Post-Installation Setup), do not perform this procedure. Instead, go to “How to Uninstall Sun Cluster Software From a Cluster Node” in “Adding and Removing a Cluster Node” in Sun Cluster 3.1 System Administration Guide.

Attempt to reinstall the node.

Certain failed installations can be corrected simply by repeating the Sun Cluster software installation on the node. If you have already tried to reinstall the node without success, proceed to Step 2 to uninstall Sun Cluster software from the node.

Become superuser on an active cluster member other than the node you will uninstall.

From the active cluster member, add the node you intend to uninstall to the cluster's node authentication list.
# /usr/cluster/bin/scconf -a -T node=nodename
-a

Add

-T

Specifies authentication options

node=nodename

Specifies the name of the node to add to the authentication list

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 System Administration Guide for procedures.

Become superuser on the node you intend to uninstall.

Reboot the node into non-cluster mode.
# shutdown -g0 -y -i0 ok boot -x

Uninstall the node.

Run the scinstall command from a directory that does not contain any files delivered by the Sun Cluster packages.
# cd / # /usr/cluster/bin/scinstall -r
See the scinstall(1M) man page for more information.

Reinstall Sun Cluster software on the node.

Refer to Table 2–1 for the list of all installation tasks and the order in which to perform them.

Installing the Software

How to Prepare for Cluster Software Installation

How to Install Cluster Control Panel Software on the Administrative Console

How to Install Solaris Software

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

Example—Installing Sun Cluster Software on the First Node

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

Example—Installing Sun Cluster Software on the Second Node

Using SunPlex Manager to Install Sun Cluster Software

How to Install SunPlex Manager Software

How to Add RBAC Authorization to an Existing User Account

How to Create a New User Account

How to Install Sun Cluster Software (SunPlex Manager)

How to Install Solaris and Sun Cluster Software (JumpStart)

How to Configure the Name Service Switch

How to Set Up the Root Environment

How to Install Data Service Software Packages

How to Perform Post-Installation Setup

How to Uninstall Sun Cluster Software To Correct Installation Problems

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

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