Sun Cluster Software Installation Guide for Solaris OS

Installing the Software

This section provides information and procedures to install software on the cluster nodes.

Task Map: Installing the Software

The following task map lists the tasks that you perform to install software on multinode or single-node clusters. Complete the procedures in the order that is indicated.

Table 2–1 Task Map: Installing the Software


Task	Instructions
1. Plan the layout of your cluster configuration and prepare to install software.	How to Prepare for Cluster Software Installation
2. (Optional) Install Cluster Control Panel (CCP) software on the administrative console.	How to Install Cluster Control Panel Software on an Administrative Console
3. Install the Solaris operating environment and Sun Cluster software. Choose one of the following methods:
Method 1 – (New clusters only) Install Solaris software. Install Sun Cluster software on all nodes. Then use the `scinstall` utility to establish the cluster.	How to Install Solaris Software How to Install Sun Cluster Software Packages How to Configure Sun Cluster Software on All Nodes (`scinstall`)
Method 2 – (New clusters only) Install Solaris software. Then install SunPlex^TM Manager and use it to install 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)
Method 4 – (New single-node clusters) Install Solaris software and then install Sun Cluster software by using the `scinstall` `-iFo` command.	How to Install Solaris Software How to Install Sun Cluster Software on a Single-Node Cluster
Method 5 – (Added nodes only) Install Solaris software on the new nodes. Install Sun Cluster software on the new node. Then configure Sun Cluster software on the new node by using the `scinstall` utility.	How to Install Solaris Software How to Install Sun Cluster Software Packages How to Configure Sun Cluster Software on Additional Cluster Nodes (`scinstall`)
4. (Optional) SPARC: Install VERITAS File System software.	SPARC: How to Install VERITAS File System Software
5. Configure the name-service look-up order.	How to Configure the Name-Service Switch
6. Set up directory paths.	How to Set Up the Root Environment
7. Install data-service software packages.	How to Install Data-Service Software Packages (`installer`) or How to Install Data-Service Software Packages (`scinstall`)
8. Assign quorum votes and remove the cluster from installation mode, if not already performed during Sun Cluster installation.	How to Perform Postinstallation Setup and Configure Quorum Devices
9. Validate the quorum configuration.	How to Verify the Quorum Configuration and Installation Mode
10. 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
SPARC: Install and configure VERITAS Volume Manager software.	SPARC: Installing and Configuring VxVM Software VERITAS Volume Manager documentation
11. 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 can help you plan your cluster configuration and prepare your installation strategy.
- Sun Cluster Release Notes for Solaris OS – Restrictions, bug workarounds, and other late-breaking information.
- Sun Cluster 3.x Release Notes Supplement – Post-release documentation about additional restrictions, bug workarounds, new features, and other late-breaking information. This document is regularly updated and published online at the following Web site.
  
  http://docs.sun.com
- Sun Cluster Overview for Solaris OS and Sun Cluster Concepts Guide for Solaris OS – Overviews of the Sun Cluster product.
- Sun Cluster Software Installation Guide for Solaris OS (this manual) – Planning guidelines and procedures for installing and configuring Solaris, Sun Cluster, and volume-manager software.
- Sun Cluster Data Service Planning and Administration Guide for Solaris OS – Planning guidelines and procedures to install and configure 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 products whose documentation you might need to reference during cluster installation:
- Solaris software
- Solstice DiskSuite/Solaris Volume Manager software
- SPARC: VERITAS Volume Manager
- SPARC: Sun Management Center
- Third-party applications

Plan your cluster configuration.

Caution –
Plan your cluster installation completely. 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.Also note that both Oracle Parallel Server/Real Application Clusters and Sun Cluster HA for SAP are not supported for use in x86 based clusters.
- Use the planning guidelines in Chapter 1, Planning the Sun Cluster Configuration and in the Sun Cluster Data Service Planning and Administration Guide for Solaris OS to determine how to install and configure your cluster.
- Fill out the cluster framework and data-services configuration worksheets that are referenced in the planning guidelines. 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.
1. Copy the patches that are required for Sun Cluster into a single directory.
  
  The directory must be on a file system that is accessible by all nodes. The default patch directory is /var/cluster/patches.
  
  Tip –
  After you install Solaris software on a node, you can view the /etc/release file to see the exact version of Solaris software that is installed.
2. (Optional) If you are not using SunPlex Manager, you can create a patch list file.
  
  If you specify a patch list file, SunPlex Manager only installs the patches that are listed in the patch list file. For information about creating a patch-list file, refer to the patchadd(1M) man page.
3. Record the path to the patch directory.

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 an Administrative Console.
- If no, go to one of the following procedures.
  - To install Sun Cluster software by using either the scinstall(1M) utility (text-based method) or SunPlex Manager (GUI-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 an Administrative Console

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.

This procedure describes how to install the Cluster Control Panel (CCP) software on an 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, as well as a common window. You can use the common window to send 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 documentation server. If you are using Sun Cluster on a SPARC based system, you can use the administrative console as a Sun Management Center console or server as well. See Sun Management Center documentation for information on how to install Sun Management Center software. See the Sun Cluster Release Notes for Solaris OS for additional information on how to install Sun Cluster documentation.

Become superuser on the administrative console.

Ensure that a supported version of the Solaris operating environment and any Solaris patches are installed on the administrative console.

All platforms require at least the End User Solaris Software Group.

Insert the Sun Java Enterprise System 2004Q2 2 of 2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

From the /cdrom/cdrom0 directory, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Packages directory, where arch is sparc or x86, and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
# cd Solaris_arch/Product/sun_cluster/Solaris_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.

(Optional) Install the Sun Cluster documentation packages.

If you do not install the documentation on your administrative console, you can still view HTML or PDF documentation directly from the CD-ROM.
1. Start the pkgadd utility in interactive mode.
  # pkgadd -d .
2. Select the Documentation Navigation for Solaris 9 package, if it has not already been installed on the administrative console.
3. Select the Sun Cluster documentation packages to install.
  
  The following documentation collections are available in both HTML and PDF format:
  - Sun Cluster 3.1 4/04 Software Collection for Solaris OS (SPARC Platform Edition)
  - Sun Cluster 3.1 4/04 Software Collection for Solaris OS (x86 Platform Edition)
  - Sun Cluster 3.x Hardware Collection for Solaris OS (SPARC Platform Edition)
  - Sun Cluster 3.x Hardware Collection for Solaris OS (x86 Platform Edition)
  - Sun Cluster 3.1 4/04 Reference Collection for Solaris OS
4. Follow onscreen instructions to continue package installation.

Unload the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM from the CD-ROM drive.
1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.
2. Eject the CD-ROM.
  # eject cdrom

Create an /etc/clusters file on the administrative console.

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, and the port number. Examples of a console-access device are a terminal concentrator (TC), a System Service Processor (SSP), and a Sun Fire system controller.
# 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

Note these special instructions to create an /etc/serialports file:
- 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.

(Optional) For convenience, set the directory paths on the administrative console.
- Add the /opt/SUNWcluster/bin directory to the PATH.
- Add the /opt/SUNWcluster/man directory to the MANPATH.
- If you installed the SUNWscman package, also add the /usr/cluster/man directory to the MANPATH.

Start the CCP utility.
# /opt/SUNWcluster/bin/ccp &
Click the cconsole, crlogin, or ctelnet button in the CCP window to launch that tool. Alternately, you can start any of these tools directly. For example, to start ctelnet, type the following command:
# /opt/SUNWcluster/bin/ctelnet &
See the procedure “How to Remotely Log In to Sun Cluster” in “Beginning to Administer the Cluster” in Sun Cluster System Administration Guide for Solaris OS for additional information about how to use the CCP utility. Also see the ccp(1M) man page.

Is the Solaris operating environment already installed on each cluster node to meet Sun Cluster software requirements?
- If yes, go to How to Install Sun Cluster Software Packages.
- If no, install, reconfigure, or reinstall the Solaris operating environment as needed to meet Sun Cluster software requirements, such as required partitioning. See Planning the Solaris Operating Environment for information about Sun Cluster installation requirements for the Solaris operating environment.
  - To install only Solaris software, go to How to Install Solaris Software.
  - To install both 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. Follow these procedures to install the Solaris operating environment on each node in the cluster.

Tip –

To speed installation, you can install the Solaris operating environment on each node at the same time.

If your nodes are already installed with the Solaris operating environment but do not meet Sun Cluster installation requirements, you might need to reinstall the Solaris software. Follow the steps in this procedure to ensure subsequent successful installation of Sun Cluster software. See Planning the Solaris Operating Environment for information about required root-disk partitioning and other Sun Cluster installation requirements.

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

See the Sun Cluster Hardware Administration Collection 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 System Layout Worksheet.

If you use a naming service, add address-to-name mappings for all public hostnames and logical addresses to any naming services that clients use for access to cluster services. You set up local hostname information in Step 15.

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) software is installed and configured on your administrative console, you can use the cconsole(1M) utility to display the individual console screens. The cconsole utility also opens a master window from which you can send your input to all individual console windows at the same time. Use the following command to start cconsole:
  # /opt/SUNWcluster/bin/cconsole clustername &
- If you do not use the cconsole utility, connect to the consoles of each node individually.

Install the Solaris operating environment as instructed in your 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 that is normally used to install Solaris software. During Solaris software installation, perform the following steps:
1. Install at least the End User Solaris Software Group.
  
  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-device 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 that is used by scinstall.
    
    Note –
    Sun Cluster software requires a global-devices file system for installation to succeed.
  - Specify that slice 7 is at least 20 Mbytes in size. If you intend to use SunPlex Manager to install Solstice DiskSuite software (Solaris 8) or configure Solaris Volume Manager software (Solaris 9), also make this file system mounted on /sds.
  - Create any other file-system partitions that you need, as described in System Disk Partitions.
    
    Note –
    If you intend to install Sun Cluster HA for NFS or Sun Cluster HA for Apache, you must also install Solstice DiskSuite software (Solaris 8) or configure Solaris Volume Manager software (Solaris 9).
3. For ease of administration, set the same root password on each node.

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

Have you added the new node to the cluster's authorized-node list?
- If yes, proceed to Step 9.
- If no, add the new node's name to the list of authorized cluster nodes.
1. On any active cluster member, start the scsetup(1M) utility.
  # scsetup
  The Main Menu is displayed.
2. Select New nodes.
3. Select Specify the name of a machine which may add itself.
4. Follow the prompts to add the node's name to the list of recognized machines.
5. Verify that the task has succeeded.
  
  The scsetup utility prints the message Command completed successfully if the task completes without error.

From another, active node of the cluster, display the names of all cluster file systems.
% mount | grep global | egrep -v node@ | awk '{print $1}'

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 no, proceed to Step 12.
- If yes, ensure that the same vxio number is used on the VxVM-installed nodes. Also ensure 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. Change the /etc/name_to_major entry to use a different number.

If you installed the End User Solaris Software Group, use the pkgadd command to manually install any additional Solaris software packages that you might need. The following Solaris packages are required to support some Sun Cluster functionality.

Feature	Required Solaris Software Packages (shown in installation order)
RSMAPISCI-PCI adapters (SPARC based clusters only)	`SUNWrsm SUNWrsmx SUNWrsmo SUNWrsmox`
RSMAPISCI-PCI adapters (SPARC based clusters only)	`SUNWrsm SUNWrsmx SUNWrsmo SUNWrsmox`
SunPlex Manager	`SUNWapchr SUNWapchu`

Install any hardware-related patches. Also download any needed firmware that is 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.

x86: Set the default boot file to kadb.
# eeprom boot-file=kadb
The setting of this value enables you to reboot the node if you are unable to access a login prompt.

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 no, proceed to Step 17.
- If yes, add the following entry to the /etc/system file on each node of the cluster:
  set kernel_cage_enable=1
  This entry becomes effective after the next system reboot.
  
  See the Sun Cluster System Administration Guide for Solaris OS for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.

Install Sun Cluster software packages.

Go to How to Install Sun Cluster Software Packages.

How to Install Sun Cluster Software Packages

Perform this procedure to install the Sun Cluster software packages.

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

If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

Become superuser on a cluster node to install.

Install Sun Cluster framework software packages and Sun Java System data service packages.

Follow procedures in the Sun Java Enterprise System Installation Guide.

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

Configure Sun Cluster software on the cluster nodes.
- To establish a new cluster, go to How to Configure Sun Cluster Software on All Nodes (scinstall).
- To add a new node to an existing cluster, go to How to Configure Sun Cluster Software on Additional Cluster Nodes (scinstall).

How to Configure Sun Cluster Software on All Nodes (`scinstall`)

Perform this procedure to configure Sun Cluster software on all nodes of the cluster.

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

If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

Did you disable remote configuration during Sun Cluster software installation?
- If no, proceed to Step 3.
- If yes, enable remote shell (rsh(1M)) or secure shell (ssh(1)) access for superuser to all cluster nodes.

Do you intend to use the scinstall utility to install patches?
- If no, proceed to Step 4.
- If yes, download patches to a patch directory.
  
  The scinstall command checks for patches in the /var/cluster/patches directory or the /var/patches directory. If neither of the directories exist, then no patches are added. If both directories exist, then only the patches in the /var/cluster/patches directory are added.
  
  You can include a patch-list file in the patch directory. The default patch-list file name is patchlist. For information about creating a patch-list file, refer to the patchadd(1M) man page.

Complete one of the following configuration worksheets:

See Planning the Sun Cluster Environment for planning guidelines.

Table 2–2 Interactive scinstall Configuration Worksheet (Typical)


Component	Description/Example	Enter Answers Here
Cluster Name	What is the name of the cluster that you want to establish?
Cluster Nodes	What are the names of the other cluster nodes planned for the initial cluster configuration?
Cluster-Transport Adapters and Cables	What are the names of the two cluster-transport adapters that attach the node to the private interconnect?
Validation Checks	Do you want to interrupt installation for `sccheck` errors?	Yes \| No

For the Typical configuration of Sun Cluster software, scinstall automatically specifies the following defaults.

Component	Default Value
Private-network address	`172.16.0.0`
Private-network netmask	`255.255.0.0`
Cluster-transport junctions	`switch1` and `switch2`
Global-devices file-system name	`/globaldevices`
Installation security (DES)	Limited
Solaris and Sun Cluster patch directory	`/var/cluster/patches`

Table 2–3 Interactive scinstall Configuration Worksheet (Custom)


Component	Description/Example	Enter Answers Here
Cluster Name	What is the name of the cluster that you want to establish?
Cluster Nodes	What are the names of the other cluster nodes planned for the initial cluster configuration?
DES Authentication	Do you need to use DES authentication?	No \| Yes
Network Address for the Cluster Transport	Do you want to accept the default network address (`172.16.0.0`)?	Yes \| No
	If no, supply your own network address:	_____ . _____`.0.0`
	Do you want to accept the default netmask (`255.255.0.0`)?	Yes \| No
	If no, supply your own netmask:	`255.255`. ___ . ___
Point-to-Point Cables	If this is a two-node cluster, does this cluster use transport junctions?	Yes \| No
Cluster-Transport Junctions	If used, what are the names of the two transport junctions? Defaults: `switch1` and `switch2`	First	Second
Cluster-Transport Adapters and Cables	Node name (the node from which you run scinstall):
	Transport adapters:	First	Second
	Where does each transport adapter connect to (a transport junction or another adapter)? Junction defaults: `switch1` and `switch2`
	For transport junctions, do you want to use the default port name?	Yes \| No	Yes \| No
	If no, what is the name of the port that you want to use?
	Do you want to use autodiscovery to list the available adapters for the other nodes? If no, supply the following information for each additional node:	Yes \| No
	Node name:
	Transport adapters:	First	Second
	Where does each transport adapter connect to (a transport junction or another adapter)? Defaults: `switch1` and `switch2`
	For transport junctions, do you want to use the default port name?	Yes \| No	Yes \| No
	If no, what is the name of the port that you want to use?
Software Patch Installation	Do you want `scinstall` to install patches for you?	Yes \| No
	If yes, what is the name of the patch directory?
	Do you want to use a patch list?	Yes \| No
Global-Devices File System (specify for each node)	Do you want to use the default name of the global-devices file system (`/globaldevices`)?	Yes \| No
	If no, do you want to use an already-existing file system?	Yes \| No
	What is the name of the file system that you want to use?
Validation Checks	Do you want to run the `sccheck` utility to validate the cluster?	Yes \| No

Note –

You cannot change the private-network address and netmask after scinstall processing is finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then perform the procedures in How to Install Sun Cluster Software Packages and in this procedure to reinstall the software and configure the node with the correct information.

Become superuser on the cluster node from which you intend to configure the cluster.

Start the scinstall utility.
# /usr/cluster/bin/scinstall

Follow these guidelines to use the interactive scinstall utility:
- Interactive scinstall enables you to type ahead. Therefore, do not press the Return key 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.
- Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

From the Main Menu, choose Install a cluster or cluster node.

 *** Main Menu ***

    Please select from one of the following (*) options:

      * 1) Install a cluster or cluster node
        2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node

      * ?) Help with menu options
      * q) Quit

    Option:  1

From the Install Menu, choose Install all nodes of a new cluster.

From the Type of Installation menu, choose either Typical or Custom.

Follow the menu prompts to supply your answers to Table 2–2 or Table 2–3, which you completed in Step 4.

The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

SPARC: Do you intend to install VERITAS File System?
- If yes, go to SPARC: How to Install VERITAS File System Software.
- If no, set up the name-service look-up order. Go to How to Configure the Name-Service Switch.

Example – Configuring Sun Cluster Software on All Nodes

The following example shows the scinstall progress messages that are logged as scinstall completes configuration tasks on a two-node cluster. The cluster node names are phys-schost-1 and phys-schost-2. The specified adapter names are qfe2 and hme2.

  Installation and Configuration

    Log file - /var/cluster/logs/install/scinstall.log.834

    Testing for "/globaldevices" on "phys-schost-1" ... done
    Testing for "/globaldevices" on "phys-schost-2" ... done

    Checking installation status ... done

    The Sun Cluster software is already installed on "phys-schost-1".
    The Sun Cluster software is already installed on "phys-schost-2".

    Starting discovery of the cluster transport configuration.

    Probing ..

    The following connections were discovered:

        phys-schost-1:qfe2  switch1  phys-schost-2:qfe2
        phys-schost-1:hme2  switch2  phys-schost-2:hme2

    Completed discovery of the cluster transport configuration.

    Started sccheck on "phys-schost-1".
    Started sccheck on "phys-schost-2".

    sccheck completed with no errors or warnings for "phys-schost-1".
    sccheck completed with no errors or warnings for "phys-schost-2".

    Configuring "phys-schost-2" ... done
    Rebooting "phys-schost-2" ... done

    Configuring "phys-schost-1" ... done
    Rebooting "phys-schost-1" ... 

Log file - /var/cluster/logs/install/scinstall.log.834

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, follow the procedures How to Configure Sun Cluster Software on Additional Cluster Nodes (scinstall).

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

(On Solaris 8 only) Solstice DiskSuite software – After it installs Solstice DiskSuite software, SunPlex Manager configures up to three metasets and associated metadevices. SunPlex Manager also creates and mounts cluster file systems for each metaset.
(On Solaris 9 only) Solaris Volume Manager software – SunPlex Manager configures up to three Solaris Volume Manager volumes. SunPlex Manager also creates and mounts cluster file systems for each volume. Solaris Volume Manager software is already installed as part of Solaris software installation.
Sun Cluster HA for NFS data service.
Sun Cluster HA for Apache scalable data service.

Installation Requirements

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 in size.
Sun Cluster HA for NFS data service	At least two shared disks, of the same size, that 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. The IP address must be on the same subnet as the base hostnames of the cluster nodes. A test IP address for each node of the cluster. SunPlex Manager uses these test IP addresses to create Internet Protocol (IP) Network Multipathing (IP Network Multipathing) groups for use by Sun Cluster HA for NFS.
Sun Cluster HA for Apache scalable data service	At least two shared disks of the same size that 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. The IP address must be on the same subnet as the base hostnames of the cluster nodes. A test IP address for each node of the cluster. SunPlex Manager uses these test IP addresses to create Internet Protocol (IP) Network Multipathing (IP Network Multipathing) groups for use by Sun Cluster HA for Apache.

Test IP Addresses

The test IP addresses that you supply must meet the following requirements:

Test IP addresses for all adapters in the same multipathing group must belong to a single IP subnet.
Test IP addresses must not be used by normal applications because the test IP addresses are not highly available.

The following table lists each metaset name and cluster-file-system mount point that is created by SunPlex Manager. The number of metasets and mount points that SunPlex Manager creates depends on the number of shared disks that are connected to the node. For example, if a node is connected to four shared disks, SunPlex Manager creates the mirror-1 and mirror-2 metasets. However, SunPlex Manager 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	`mirror-1`	`/global/mirror-1`	Sun Cluster HA for NFS or Sun Cluster HA for Apache scalable data service, or both
Second pair	`mirror-2`	`/global/mirror-2`	Unused
Third pair	`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. However, without sufficient shared disks, SunPlex Manager cannot configure the metasets, metadevices, or volumes. SunPlex Manager then cannot configure the cluster file systems that are needed to create instances of the data service.

Character-Set Limitations

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 can cause problems in the following two areas:

Password entry for Sun Java^TM System services – If the password contains unusual characters, these characters are stripped out, resulting in one of the following problems:
- The resulting password therefore fails because it has less than eight characters.
- The application is configured with a different password than the user expects.
Localization – Alternative character sets, such as accented characters or Asian characters, do not work for input.

How to Install SunPlex Manager Software

This procedure describes how to install SunPlex Manager software on your cluster.

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. Or, if Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software. You must also ensure that the installation meets the requirements for any other software that you intend to install on the cluster.

Review the requirements and guidelines in Using SunPlex Manager to Install Sun Cluster Software.

x86: Determine whether you are using the Netscape Navigator^TM browser or the Microsoft Internet Explorer browser on your administrative console.
- If you are using Netscape Navigator, go to Step 4.
- If you are using Internet Explorer, go to Step 5.

x86: Ensure that the Java plug-in is installed and working on your administrative console.
1. Start the Netscape Navigator browser on the administrative console that you use to connect to the cluster.
2. From the Help menu, choose About Plug-ins.
3. Determine whether the Java plug-in is listed.
  - If yes, skip to Step 6.
  - If no, proceed to Step d.
4. Download the latest Java plug-in from http://java.sun.com/products/plugin.
5. Install the plug-in on your administrative console.
6. Create a symbolic link to the plug-in.
  % cd ~/.netscape/plugins % ln -s /usr/j2se/plugin/i386/ns4/javaplugin.so .
7. Skip to Step 6.

x86: Ensure that Java 2 Platform, Standard Edition (J2SE) for Windows is installed and working on your administrative console.
1. On your Microsoft Windows desktop, click Start, point to Settings, and then select Control Panel.
  
  The Control Panel window appears.
2. Determine whether the Java Plug-in is listed.
  - If no, proceed to Step c.
  - If yes, double-click the Java Plug-in control panel. When the control panel window opens, click the About tab.
    - If version 1.4.1 or a later version is shown, skip to Step 6.
    - If an earlier version is shown, proceed to Step c.
3. Download the latest version of J2SE for Windows from http://java.sun.com/j2se/downloads.html.
4. Install the J2SE for Windows software on your administrative console.
5. Restart the system on which your administrative console runs.
  
  The J2SE for Windows control panel is activated.

Become superuser on a cluster node.

Ensure that Apache software packages are installed on the node.
# pkginfo SUNWapchr SUNWapchu SUNWapchd
If necessary, install any missing Apache software packages by performing the following steps.
1. Insert the Solaris 8 or Solaris 9 Software 2 of 2 CD-ROM into the CD-ROM drive of the node.
  
  If the volume management daemon vold(1M) is running and is configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM.
2. Change to the Product directory.
  - For Solaris 8, 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 order that is shown in this step.
  # pkgadd -d . SUNWapchr SUNWapchu SUNWapchd
4. 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. Insert the Sun Java Enterprise System 2004Q2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.
2. From the /cdrom/cdrom0 directory, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Packages directory, where arch is sparc or x86, and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
  
  The following example shows the path to the SPARC Solaris 8 version of Sun Cluster software.
  # cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Packages
3. Install the SunPlex Manager software packages.
  # pkgadd -d . SUNWscva SUNWscvr SUNWscvw

Repeat Step 6 through Step 8 on each node of the cluster.

Determine whether the root password is the same on every node of the cluster.
- If yes, proceed to Step 11.
- If no, set the root password to the same value on each node of the cluster. If necessary, also use the chkey command to update the RPC key pair. See the chkey(1) man page.
  # passwd Enter new password # chkey -p
To use the root password to access SunPlex Manager, the root password must be the same on all nodes in the cluster.

Use SunPlex Manager to configure Sun Cluster software.

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

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

Perform this procedure to use SunPlex Manager to install and configure 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 one or both of the following data services:

Sun Cluster HA for NFS data service
Scalable Sun Cluster HA for Apache data service

The installation process might take from 30 minutes to two or more hours. The actual length of time depends on the number of nodes that are in the cluster, your choice of data services to install, and the number of disks that are in your cluster configuration.

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, proceed to Step 3.
- If yes, ensure that the cluster configuration meets all applicable requirements. See Using SunPlex Manager to Install Sun Cluster Software.

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

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

Prepare file-system paths to a CD-ROM image of each software product that you intend to install.

Follow these guidelines to prepare the file-system paths:
- Provide each CD-ROM image in a location that is available to each node.
- Ensure that the CD-ROM images are 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 that are exported to the network from machines outside the cluster.
  - Exported file systems on machines outside the cluster.
  - CD-ROM images that are copied to local file systems on each node of the cluster. The local file system must use the same name on each node.

Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
- If no, proceed to Step 6.
- If yes, install the additional packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM that are required to support the RSMAPI or SCI-PCI adapters. SunPlex Manager does not automatically install these packages.
1. Determine which packages you must install.
  
  The following table lists the Sun Cluster 3.1 4/04 packages that each feature requires and the order in which you must install each group of packages.
  
  Feature
  
  Additional Sun Cluster 3.1 4/04 Packages to Install
  
  RSMAPI
  
  SUNWscrif
  
  SCI-PCI adapters
  
  SUNWsci SUNWscid SUNWscidx
2. Use the following command to install the additional packages.
  
  Replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).
  # cd Solaris_arch/Product/sun_cluster/Solaris_ver/Packages # pkgadd -d . packages

Are there any patches that are required to support Sun Cluster or Solstice DiskSuite software?
- If yes, proceed to Step 7.
- If no, skip to Step 10.

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

Copy patches that are required for Sun Cluster or Solstice DiskSuite software into a single directory. This directory must reside 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.

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

Complete the following installation worksheet.

Table 2–6 SunPlex Manager Installation and Configuration Worksheet


Component	Description/Example	Enter Answers Here
Cluster Name	What is the name of the cluster that you want to establish?
Cluster Name	How many nodes are you installing in the cluster?
Node Names	What are the names of the cluster nodes?
Cluster-Transport Adapters and Cables	What are the names of the two transport adapters to use, two adapters per node?
Solstice DiskSuite or Solaris Volume Manager	Solaris 8: Do you want to install Solstice DiskSuite? Solaris 9: Do you want to configure Solaris Volume Manager?	Yes \| No
Sun Cluster HA for NFS Requires Solstice DiskSuite or Solaris Volume Manager	Do you want to install Sun Cluster HA for NFS? If yes, also specify the following:	Yes \| No
	What is the logical hostname that the data service is to use?
	What are the test IP addresses to use? Supply one test IP address for each node in the cluster.
Sun Cluster HA for Apache (scalable) Requires Solstice DiskSuite or Solaris Volume Manager	Do you want to install scalable Sun Cluster HA for Apache? If yes, also specify the following:	Yes \| No
	What is the logical hostname that the data service is to use?
	What are the test IP addresses to use? Supply one test IP address for each node in the cluster.
CD-ROM Paths	What is the path for each of the following components that you want to install? The CD-ROM path must end with the directory that contains the `.cdtoc` file.
	Solstice DiskSuite:
	Sun Cluster (base):
	Sun Cluster data services (agents):
	Patches:
Validation Checks	Do you want to run the `sccheck` utility to validate the cluster?	Yes \| No

Note –

SunPlex Manager installation automatically specifies the default private-network address (172.16.0.0) and netmask (255.255.0.0). If you need to use a different address, do not use SunPlex Manager to install Sun Cluster software. Instead, follow procedures in How to Install Sun Cluster Software Packages and in How to Configure Sun Cluster Software on All Nodes (scinstall) to install and configure the cluster.

You cannot change the private-network address and netmask after scinstall processing has finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then repeat this procedure to reinstall and configure the node with the correct information.

See Planning the Solaris Operating Environment and Planning the Sun Cluster Environment for planning guidelines. See the Sun Cluster Data Service Planning and Administration Guide for Solaris OS for data-service 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 is displayed 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 and configured 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.

If you meet all listed requirements, click Next to continue to the next screen.

Follow the menu prompts to supply your answers to Table 2–6, which you completed in Step 9.

Click Begin Installation to start the installation process.

Follow these guidelines:
- Do not close the browser window nor change the URL during the installation process.
- If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.
- If the browser prompts for login information, type the appropriate superuser ID and password for the node that you connect to.
The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

During installation, the screen displays brief messages about the status of the cluster installation process. When installation and configuration is complete, the browser displays the cluster monitoring and administration GUI.

SunPlex Manager installation output is logged in the /var/cluster/spm/messages file.

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

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

For clusters with three or more nodes, the use of 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 to reassign quorum votes in the cluster.

SPARC: Do you intend to install VERITAS File System?
- If yes, go to SPARC: How to Install VERITAS File System Software.
- If no, 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 establishes the cluster. You can also use this procedure to add new nodes to an existing cluster.

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

See the Sun Cluster Hardware Administration Collection 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 installation worksheet

Table 2–7 JumpStart Installation and Configuration Worksheet


Component	Description/Example	Enter Answers Here
JumpStart Directory	What is the name of the JumpStart directory to use?
Cluster Name	What is the name of the cluster that you want to establish?
Cluster Nodes	What are the names of the cluster nodes that are planned for the initial cluster configuration?
DES Authentication	Do you need to use DES authentication?	No \| Yes
Network Address for the Cluster Transport	Do you want to accept the default network address (`172.16.0.0`)?	Yes \| No
	If no, supply your own network address:	_____ . _____`.0.0`
	Do you want to accept the default netmask (`255.255.0.0`)?	Yes \| No
	If no, supply your own netmask:	`255.255`.___ . ___
Point-to-Point Cables	Does this cluster use transport junctions (two-node clusters only)?	Yes \| No
Cluster-Transport Junctions	If used, what are the names of the two transport junctions? Defaults: `switch1` and `switch2`	First	Second
Cluster-Transport Adapters and Cables	First node name:
	Transport adapters:	First	Second
	Where does each transport adapter connect to (a transport junction or another adapter)? Junction defaults: `switch1` and `switch2`
	For transport junctions, do you want to use the default port name?	Yes \| No	Yes \| No
	If no, what is the name of the port that you want to use?
	Do you want to use autodiscovery to list the available adapters for the other nodes? If no, supply the following information for each additional node:	Yes \| No
	Node name:
	Transport adapters:	First	Second
	Where does each transport adapter connect to (a transport junction or another adapter)? Junction defaults: `switch1` and `switch2`
	For transport junctions, do you want to use the default port name?	Yes \| No	Yes \| No
	If no, what is the name of the port that you want to use?
Global-Devices File System	Do you want to use the default name of the global-devices file system (`/globaldevices`)?	Yes \| No
	If no, do you want to use an already-existing file system?	Yes \| No
	What is the name of the file system?
Software Patch Installation	Do you want `scinstall` to install patches for you?	Yes \| No
	If yes, what is the name of the patch directory?
	Do you want to use a patch list?	Yes \| No

See Planning the Solaris Operating Environment and Planning the Sun Cluster Environment for planning guidelines.

Note –

Do you use a naming service?
- If no, proceed to Step 5. You set up the necessary hostname information in Step 15.
- If yes, add the following information to any naming services that clients use to access cluster services:
  - Address-to-name mappings for all public hostnames and logical addresses
  - The IP address and hostname of the JumpStart server
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 no, proceed to Step 6.
- If yes, run scsetup(1M) from another cluster node that is active. Use the scsetup utility to add the new node's name to the list of authorized cluster nodes. For more information, see “How to Add a Cluster Node to the Authorized Node List” in “Adding and Removing a Cluster Node” in Sun Cluster System Administration Guide for Solaris OS.

Set up your JumpStart installation server for Solaris operating-environment installation.
- SPARC: As superuser, set up your JumpStart installation server.
- x86: Set up and configure your JumpStart Dynamic Host Configuration Protocol (DHCP) server and your Solaris network for Preboot Execution Environment (PXE) installations.
  
  The Sun Fire V60x and Sun Fire V65x Server Solaris Operating Environment Installation Guide contains instructions about how to set up a DHCP server and Solaris network for PXE installations.
  
  x86 only –
  You must use a DHCP server and PXE to install Sun Cluster software with JumpStart over a network.
See “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide for instructions on how to set up a JumpStart installation server. See also the setup_install_server(1M) and add_install_client(1M) man pages.

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

Create a directory on the JumpStart installation server to hold your copy of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM.

Skip this step if a directory already exists.

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 installation server.
1. Insert the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM into the CD-ROM drive on the JumpStart installation server.
  
  If the volume management daemon vold(1M) is running and configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.
2. From the /cdrom/cdrom0 directory, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Tools directory, where arch is sparc or x86 and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
  
  The following example uses the path to the SPARC Solaris 8 version of Sun Cluster software.
  # cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools
3. Copy the CD-ROM to a new directory on the JumpStart installation server.
  
  The scinstall command creates the new installation directory when the command copies the CD-ROM files. The following example uses the installation directory name /export/suncluster/sc31.
  # ./scinstall -a /export/suncluster/sc31
4. Unload the CD-ROM from the CD-ROM drive.
  1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.
  2. Eject the CD-ROM.
    # eject cdrom
5. Ensure that the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM image on the JumpStart installation server is NFS exported for reading by the JumpStart installation 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 for more information about automatic file sharing. See also the share(1M) and dfstab(4) man pages.

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

The path /export/suncluster/sc31 is used here as an example of the installation directory that you created. In the CD-ROM path, replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).
# cd /export/suncluster/sc31/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools # ./scinstall

Follow these guidelines to use the interactive scinstall utility:
- Interactive scinstall enables you to type ahead. Therefore, do not press the Return key 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.
- Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

From the Main Menu, choose Configure a cluster to be JumpStarted from this installation server.

This option is used to configure custom 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) Install a cluster or cluster node
      * 2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node
 
      * ?) Help with menu options
      * q) Quit
 
    Option:  2

Note –

If the JumpStart option does not have an asterisk in front, the option is disabled. This condition indicates that JumpStart setup is not complete or that the setup has an error. To correct this condition, do the following:

Exit the scinstall utility.
Repeat Step 6 through Step 8 to correct JumpStart setup.
Restart the scinstall utility.

Follow the menu prompts to supply your answers to Table 2–7, which you completed in Step 3.

If necessary, make adjustments to the default class file, or profile, that scinstall creates.

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 Solaris Software Group (SUNWCuser). If your configuration has additional Solaris software requirements, change the class file accordingly. See Solaris Software Group Considerations for more information.

If you installed the End User Solaris Software Group, add to the default class file any additional Solaris software packages that you might need. The following table lists Solaris packages that are required to support some Sun Cluster functionality.

Table 2–8 Solaris Software Package Dependencies


Feature	Required Solaris Software Packages (shown in installation order)
RSMAPI,SCI-PCI adapters (SPARC based clusters only)	`SUNWrsm SUNWrsmx SUNWrsmo SUNWrsmox`
SunPlex Manager	`SUNWapchr SUNWapchu`

You can change the default class file 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 installation profile meets minimum Sun Cluster file-system allocation requirements, Sun Cluster software places no restrictions on other changes to the installation profile. See System Disk Partitions for partitioning guidelines and requirements to support Sun Cluster software.

For more information about JumpStart profiles, see “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide.

Set up Solaris patch directories.

Note –
If you specified a patch directory to the scinstall utility, patches that are located in Solaris patch directories are not installed.
1. Create jumpstart-dir/autoscinstall.d/nodes/node/patches directories on the JumpStart installation 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.
3. Place copies of any hardware-related patches that you must install 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 installation server, create files that are 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. The NFS server could be the JumpStart installation 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 no, proceed to Step 17 if you intend to add your own postinstallation finish script. Otherwise, skip to Step 18.
- If yes, follow instructions in Step 17 to set up a postinstallation finish script to install the following additional packages. Install the appropriate packages from the Solaris_arch/Product/sun_cluster/Solaris_ver/Packages directory of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM in the order that is given in the following table.
  
  Note –
  In the CD-ROM path, replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).
  
  Feature
  
  Additional Sun Cluster 3.1 4/04 Packages to Install
  
  RSMAPI
  
  SUNWscrif
  
  SCI-PCI adapters
  
  SUNWsci SUNWscid SUNWscidx

(Optional) Add your own postinstallation 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 to 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.
  
  Create one directory for each node in the cluster. Alternately, use this naming convention to create symbolic links to a shared finish script.

If you are using a cluster administrative console, display a console screen for each node in the cluster.
- If Cluster Control Panel (CCP) software is installed and configured on your administrative console, you can use the cconsole(1M) utility to display the individual console screens. The cconsole utility also opens a master window from which you can send your input to all individual console windows at the same time. Use the following command to start cconsole:
  # /opt/SUNWcluster/bin/cconsole clustername &
- If you do not use the cconsole utility, connect to the consoles of each node individually.

Shut down each node.
# shutdown -g0 -y -i0

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

Boot each node to start the JumpStart installation.

On SPARC based systems, do the following:
ok boot net - install
Note –
Surround the dash (-) in the second command with a space on each side.

On x86 based systems, do the following:

When the BIOS information screen appears, press the Esc key.

The Select Boot Device screen appears.
On the Select Boot Device screen, choose the listed IBA that is connected to the same network as the JumpStart DHCP installation server.

The lowest number to the right of the IBA boot choices corresponds to the lower Ethernet port number. The higher number to the right of the IBA boot choices corresponds to the higher Ethernet port number.

The node reboots and the Device Configuration Assistant appears.
On the Boot Solaris screen, choose Net.

At the following prompt, choose Custom JumpStart and press Enter:

Select the type of installation you want to perform:

         1 Solaris Interactive
         2 Custom JumpStart

Enter the number of your choice followed by the <ENTER> key.

If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.

When prompted, answer the questions and follow the instructions on the screen.

JumpStart installs the Solaris software and Sun Cluster software on each node.

Note –

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

When the installation is successfully completed, each node is fully installed as a new cluster node. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

Are you installing a new node to an existing cluster?
- If no, proceed to Step 22.
- If yes, create mount points on the new node for all existing cluster file systems.
1. From another cluster node that is active, display the names of all cluster file systems.
  % mount | grep global | egrep -v node@ | awk '{print $1}'
2. On the node that 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 that is returned by the mount command is /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the node that is being added to the cluster.
  
  Note –
  The mount points become active after you reboot the cluster in Step 24.
3. Is VERITAS Volume Manager (VxVM) installed on any nodes that are already in the cluster?
  - If no, proceed to Step 22.
  - If yes, ensure that the same vxio number is used on each of the VxVM-installed nodes. Also ensure 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. Change the /etc/name_to_major entry to use a different number.

(Optional) To use dynamic reconfiguration on Sun Enterprise 10000 servers, add the following entry to the /etc/system file. Add this entry on each node in the cluster.
set kernel_cage_enable=1
This entry becomes effective after the next system reboot. See the Sun Cluster System Administration Guide for Solaris OS for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.

x86: Set the default boot file to kadb.
# eeprom boot-file=kadb
The setting of this value enables you to reboot the node if you are unable to access a login prompt.

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 that you installed require a node reboot. Also reboot if any other changes that you made require a reboot to become active, then proceed to Step 25.
If yes, perform a reconfiguration reboot of the cluster as instructed in the following steps.

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.

Reboot each node in the cluster.

On SPARC based systems, do the following:
ok boot

On x86 based systems, do the following:

                     <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b
Boot args:

Type   b [file-name] [boot-flags] <ENTER>  to boot with options
or     i <ENTER>                           to enter boot interpreter
or     <ENTER>                             to boot with defaults

                 <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b

Note –

Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster that is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. The entire cluster then shuts down. Cluster nodes remain in installation mode until the first time you run the scsetup(1M) command, during the procedure How to Perform Postinstallation Setup and Configure Quorum Devices.

The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

SPARC: Do you intend to install VERITAS File System?
- If yes, go to SPARC: How to Install VERITAS File System Software.
- If no, set up the name-service look-up order. Go to How to Configure the Name-Service Switch.

How to Install Sun Cluster Software on a Single-Node Cluster

Perform this task to install Sun Cluster software and establish the cluster on a single node by using the scinstall command. See the scinstall(1M) man page for details.

Note –

You cannot use SunPlex Manager or the interactive form of the scinstall utility to install Sun Cluster software on a single-node cluster.

The scinstall -iFo command establishes the following defaults during installation:

Creates the required device IDs
Uses the default /globaldevices file system, unless the global-devices file system is specified with the -G option
Establishes a default cluster name, which is the same as the name of the node being installed, unless the clustername is specified with the -C option

Some steps that are required for multinode cluster installations are not necessary for single-node cluster installations. When you install a single-node cluster, you do not need to perform the following steps:

You do not need to configure quorum.
You do not need to configure interconnect adapters or junctions.

Tip –

If you anticipate eventually adding a second node to your cluster, you can configure the transport interconnect during initial cluster installation. The transport interconnect is then available for later use. See the scinstall(1M) man page for details.

You can later expand a single-node cluster into a multinode cluster by following the appropriate procedures provided in How to Configure Sun Cluster Software on Additional Cluster Nodes (scinstall).

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

If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

Become superuser on the cluster node to install.

Insert the Sun Java Enterprise System 2004Q2 2 of 2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

From the /cdrom/cdrom0 directory, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Tools directory, where arch is sparc or x86 and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .

The following example uses the path to the SPARC Solaris 8 version of Sun Cluster software.
# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools

Install the Sun Cluster software and necessary patches by using the scinstall command.
# ./scinstall -iFo [-M patchdir=dirname]
-i

Specifies the install form of the scinstall command. The scinstall command installs Sun Cluster software and initializes the node as a new cluster.

-F

Establishes the node as the first node in a new cluster. All -F options can be used when installing a single-node cluster.

-o

Specifies that only one node is being installed for a single-node cluster. The -o option is only legal when used with both the -i and the -F forms of the command. When the -o option is used, cluster installation mode is preset to the disabled state.

-M patchdir=dirname[[,patchlistfile=filename]]

Specifies the path to patch information so that the specified patches can be installed by using the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname. This includes tarred, jarred, and zipped patches.

The -M option is not required with the scinstall -iFo command. The -M option is shown in this procedure because the use of this option is the most efficient method of installing patches during a single-node cluster installation. However, you can use any method that you prefer to install patches.

Reboot the node.

This reboot after Sun Cluster software installation establishes the node as the cluster.

(Optional) Change the cluster name.

A single-node cluster is created with the same name as the cluster node. If you prefer, you can change the cluster name. Use either the scsetup utility or use the following scconf command:
# /usr/cluster/bin/scconf -c -C cluster=newclustername

Verify the installation by using the scstat command.
# /usr/cluster/bin/scstat -n
See the scstat(1M) man page for details.

Ensure that cluster installation mode is disabled.

# /usr/cluster/bin/scconf -pv | grep "install mode"

SPARC: Do you intend to install VERITAS File System?
- If yes, go to SPARC: How to Install VERITAS File System Software.
- If no, set up the name-service look-up order. Go to How to Configure the Name-Service Switch.

Example—Installing Sun Cluster Software on a Single-Node Cluster

The following example shows how to use the scinstall and scstat commands to install and verify a single-node cluster. The example includes installation of all patches. See the scinstall(1M) and scstat(1M) man pages for details.

# scinstall -iFo -M patchdir=/var/cluster/patches 

Checking device to use for global devices file system ... done
** Installing SunCluster 3.1 framework **
...
Installing patches ... done

Initializing cluster name to "phys-schost-1" ... done
Initializing authentication options ... 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 "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

Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

Ensure network routing is disabled ... done

Please reboot this machine.

# reboot
# scstat -n
-- Cluster Nodes --

                    Node name           Status
                    ---------           ------
  Cluster node:     phys-schost-1       Online
# scconf -pv | grep "install mode"
Cluster install mode:                   disabled

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

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

Install the hardware on the new cluster node.
1. Install the host adapter on the new node and verify that any existing cluster interconnects can support the new node.
  
  See the Sun Cluster Hardware Administration Manual for Solaris OS.
2. Install any additional storage.
  
  See the appropriate manual from the Sun Cluster 3.x Hardware Administration Collection.

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

If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software and any other software that you intend to install on the cluster. See How to Install Solaris Software for more information about installing Solaris software to meet Sun Cluster software requirements.

Ensure that Sun Cluster software packages are installed on the node.

See How to Install Sun Cluster Software Packages.

Complete the following configuration worksheet.

Table 2–9 Added Node Configuration Worksheet


Component	Description/Example	Enter Answers Here
Software Patch Installation	Do you want `scinstall` to install patches for you?	Yes \| No
	If yes, what is the patch directory?
	Do you want to use a patch list?	Yes \| No
Sponsoring Node	What is the name of the sponsoring node? Choose any node that is active in the cluster.
Cluster Name	What is the name of the cluster that you want the node to join?
Check	Do you want to run the `sccheck` validation utility?	Yes \| No
Autodiscovery of Cluster Transport	Do you want to use autodiscovery to configure the cluster transport? If no, supply the following additional information:	Yes \| No
Point-to-Point Cables	Does the node that you are adding to the cluster make this a two-node cluster?	Yes \| No
Point-to-Point Cables	Does the cluster use transport junctions?	Yes \| No
Cluster–Transport Junctions	If used, what are the names of the two transport junctions? Defaults: `switch1` and `switch2`	First	Second
Cluster-Transport Adapters and Cables	What are the names of the two transport adapters?
	Where does each transport adapter connect to (a transport junction or another adapter)? Junction defaults: `switch1` and `switch2`
	For transport junctions, do you want to use the default port name?	Yes \| No	Yes \| No
	If no, what is the name of the port that you want to use?
Global-Devices File System	What is the name of the global-devices file system? Default: `/globaldevices`
Automatic Reboot	Do you want `scinstall` to automatically reboot the node after installation?	Yes \| No

See Planning the Solaris Operating Environment and Planning the Sun Cluster Environment for planning guidelines.

Are you adding this node to a single-node cluster?
- If yes, go to Step 6.
- If no, skip to Step 8.

From the existing cluster node, determine whether two cluster interconnects already exist.

You must have at least two cables or two adapters configured.
# scconf -p | grep cable # scconf -p | grep adapter
- If the output shows configuration information for two cables or for two adapters, skip to Step 8.
- If the output shows no configuration information for either cables or adapters, or shows configuration information for only one cable or adapter, proceed to Step 7.

Configure new cluster interconnects.
1. On the existing cluster node, start the scsetup(1M) utility.
  # scsetup
  The Main Menu displays.
2. Select Cluster interconnect.
3. Select Add a transport cable.
  
  Follow the instructions to specify the name of the node to add to the cluster, the name of a transport adapter, and whether to use a transport junction.
4. If necessary, repeat Step c to configure a second cluster interconnect.
  
  When finished, quit the scsetup utility.
5. Verify that the cluster now has two cluster interconnects configured.
  # scconf -p | grep cable # scconf -p | grep adapter
  The command output should show configuration information for at least two cluster interconnects.

Add the new node to the cluster authorized–nodes list.
1. On any active cluster member, start the scsetup(1M) utility.
  # scsetup
  The Main Menu is displayed.
2. Select New nodes.
3. Select Specify the name of a machine which may add itself.
4. Follow the prompts to add the node's name to the list of recognized machines.
5. Verify that the task has succeeded.
  
  The scsetup utility prints the message Command completed successfully if the task completes without error.
6. Quit the scsetup utility.

Become superuser on the cluster node to configure.

Start the scinstall utility.
# /usr/cluster/bin/scinstall

Follow these guidelines to use the interactive scinstall utility:
- Interactive scinstall enables you to type ahead. Therefore, do not press the Return key 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.
- Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

From the Main Menu, choose Install a cluster or cluster node.

  *** Main Menu ***

    Please select from one of the following (*) options:

      * 1) Install a cluster or cluster node
        2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node

      * ?) Help with menu options
      * q) Quit

    Option:  1

From the Install Menu, choose Add this machine as a node in an existing cluster.

Follow the menu prompts to supply your answers to Table 2–9, which you completed in Step 4.

The scinstall utility configures the node and boots the node into the cluster.

Repeat this procedure on any other node to add to the cluster until all additional nodes are fully configured.

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

Add

-T

Specifies authentication options

node=.

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

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

SPARC: Do you intend to install VERITAS File System?
- If yes, go to SPARC: How to Install VERITAS File System Software.
- If no, set up the name-service look-up order. Go to How to Configure the Name-Service Switch.

Example – Configuring Sun Cluster Software on an Additional Node

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

 >>> Confirmation <<<
  
    Your responses indicate the following options to scinstall:
  
      scinstall -ik \
           -C sc-cluster \
           -N phys-schost-1 \
           -A trtype=dlpi,name=hme1 -A trtype=dlpi,name=hme3 \
           -m endpoint=:hme1,endpoint=switch1 \
           -m endpoint=:hme3,endpoint=switch2
  
    Are these the options you want to use (yes/no) [yes]?
  
    Do you want to continue with the install (yes/no) [yes]?
  
Checking device to use for global devices file system ... done
  
Adding node "phys-schost-3" to the cluster configuration ... done
Adding adapter "hme1" to the cluster configuration ... done
Adding adapter "hme3" to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Adding cable to the cluster configuration ... done
  
Copying the config from "phys-schost-1" ... done
Setting the node ID for "phys-schost-3" ... done (id=3)
 
Verifying the major number for the "did" driver with "phys-schost-1" ...done
  
Checking for global devices global file system ... done
Updating vfstab ... done
  
Verifying that NTP is configured ... done
Installing a default NTP configuration ... done
Please complete the NTP configuration after scinstall has finished.
  
Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done
  
Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done
  
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.61501001054
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
  
Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ...done
Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.
  
Log file - /var/cluster/logs/install/scinstall.log.9853
  
  
Rebooting ...

SPARC: How to Install VERITAS File System Software

Perform this procedure on each node of the cluster.

Follow the procedures in your VxFS installation documentation to install VxFS software on each node of the cluster.

Install any Sun Cluster patches that are required to support VxFS.

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

In the /etc/system file on each node, set the value for the rpcmod:svc_default_stksize variable to 0x8000 and set the value of the lwp_default_stksize variable to 0x6000.
set rpcmod:svc_default_stksize=0x8000 set lwp_default_stksize=0x6000
Sun Cluster software requires a minimum rpcmod:svc_default_stksize setting of 0x8000. Because VxFS installation sets the value of the rpcmod:svc_default_stksize variable to 0x4000, you must manually set the value to 0x8000 after VxFS installation is complete.

Also, you must set the lwp_default_stksize variable in the /etc/system file to override the VxFS default value of 0x4000.

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 look-up order of the following entries:
  - For the hosts and netmasks database entries, follow cluster with files.
  - For Sun Cluster HA for NFS, also insert [SUCCESS=return] after cluster files and before name services.
    hosts: cluster files [SUCCESS=return] nis
    This look-up order ensures that, if the node resolves a name locally, the node does not contact the listed name service(s). Instead, the node returns success immediately.
  - For all other database entries, place files first in the 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 the criterion in the entry. A [NOTFOUND=return] criterion at the end of an entry is ignored.
3. Make any other changes that are required by specific data services.
  
  See each manual for the data services that you installed.
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 this procedure 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. The files must verify this 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 PATH and MANPATH entries in the .cshrc or .profile file.

Set the PATH to include /usr/sbin and /usr/cluster/bin.

SPARC: If you are using VERITAS Volume Manager and VERITAS File System, also include the following paths that apply to your configuration:

Software Product	`PATH`
VERITAS Volume Manager (VxVM)	`/etc/vx/bin`
VxVM 3.2 GUI	`/opt/VRTSvmsa/bin`
VxVM 3.5 GUI	`/opt/VRTSob/bin`
VERITAS File System (VxFS)	`/opt/VRTSvxfs/sbin`, `/usr/lib/fs/vxfs/bin`, and `/etc/fs/vxfs`

Set the MANPATH to include /usr/cluster/man.

If you are using Solstice DiskSuite/Solaris Volume Manager, VERITAS Volume Manager, or VERITAS File System, also include the paths that apply to your configuration:

Software Product	`MANPATH`
Solstice DiskSuite/Solaris Volume Manager	`/usr/share/man`
SPARC: VxVM	`/opt/VRTS/man`
SPARC: VxVM GUI	`/opt/VRTSvmsa/man`
SPARC: VxFS	`/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.
- To use the scinstall utility, go to How to Install Data-Service Software Packages (scinstall).
- To use the installer program to install data services from the Sun Cluster 3.1 4/04 Data Services release, go to How to Install Data-Service Software Packages (installer).

How to Install Data-Service Software Packages (`installer`)

If you install data services from the Sun Cluster 3.1 4/04 release, you can use the installer program to install the packages. To install data services from an earlier release, follow the procedures in How to Install Data-Service Software Packages (scinstall).

You can run the installer program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the installer program, see the installer(1M) man page.

Become superuser on a cluster node.

(Optional) If you intend to use the installer program with a GUI, ensure that the DISPLAY environment variable is set.

Load the Java Enterprise System Accessory CD 3 CD-ROM into the CD-ROM drive.

If the volume management daemon vold(1M) is running and configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

Change to the directory where the CD-ROM is mounted.
# cd /cdrom/cdrom0

Start the installer program.
# ./installer

When you are prompted, select the type of installation.
- To install all data services on the CD-ROM, select Typical.
- To install only a subset of the data services on the CD-ROM, select Custom.

When you are prompted, select the locale to install.
- To install only the C locale, select Typical.
- To install other locales, select Custom.

Follow instructions on the screen to install the data-service packages on the node.

After the installation is finished, the installer program provides an installation summary. This summary enables you to view logs that the program created during the installation. These logs are located in the /var/sadm/install/logs directory.

Exit the installer program.

Unload the CD–ROM from the CD-ROM drive.
1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.
2. Eject the CD-ROM.
  # eject cdrom

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

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, perform the following steps:
1. Shut down the cluster by using the scshutdown(1M) command.
2. Reboot each node in the cluster.
Note –
Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster which is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. The entire cluster then shuts down. Cluster nodes remain in installation mode until the first time that you run the scsetup(1M) command, during the procedure How to Perform Postinstallation Setup and Configure Quorum Devices.

Is this a single-node cluster?
- If no, perform postinstallation setup and assign quorum votes.
  
  Go to How to Perform Postinstallation Setup and Configure Quorum Devices.
- If yes, cluster installation is complete. You are now ready to install volume management software and to configure the cluster.
  - To install Solstice DiskSuite software or configure Solaris Volume Manager software, go to Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software.
  - SPARC: To install VERITAS Volume Manager software, go to SPARC: Installing and Configuring VxVM Software.

How to Install Data-Service Software Packages (`scinstall`)

Perform this task on each cluster node to install data services. If you install data services from the Sun Cluster 3.1 4/04 release, you can instead use the installer program to install the packages. See How to Install Data-Service Software Packages (installer).

Note –

You do not need to perform this procedure if you used SunPlex Manager to install Sun Cluster HA for NFS or Sun Cluster HA for Apache or both and if you do not intend to install any other data services. Instead, go to How to Perform Postinstallation Setup and Configure Quorum Devices.

Become superuser on a cluster node.

Load the Java Enterprise System Accessory CD 3 CD-ROM into the CD-ROM drive on the node.

If the volume management daemon vold(1M) is running and configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

Change to the directory where the CD-ROM is mounted.
# cd /cdrom/cdrom0

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 the Return key 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.
- Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

From the Main Menu, choose Add support for new data services to this cluster node.

Follow the prompts to select the data services to install.

You must install the same set of data-service packages on each node. This requirement applies even if a node is not expected to host resources for an installed data service.

After the data services are installed, quit the scinstall utility.

Unload the Java Enterprise System Accessory CD 3 CD-ROM from the CD-ROM drive.
1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.
2. Eject the CD-ROM.
  # eject cdrom

Repeat Step 1 through Step 9 on each cluster node where you are installing data services.

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, perform the following steps:
1. Shut down the cluster by using the scshutdown(1M) command.
2. Reboot each node in the cluster.
Note –
Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster which is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. This inability to obtain quorum causes the entire cluster to shut down.

Cluster nodes remain in installation mode until the first time that you run the scsetup(1M) command, during the procedure How to Perform Postinstallation Setup and Configure Quorum Devices.

Is this a single-node cluster?
- If no, perform postinstallation setup and assign quorum votes.
  
  Go to How to Perform Postinstallation Setup and Configure Quorum Devices.
- If yes, cluster installation is complete. You are now ready to install volume management software and to configure the cluster.
  - To install Solstice DiskSuite software or configure Solaris Volume Manager software, go to Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software.
  - SPARC: To install VERITAS Volume Manager software, go to SPARC: Installing and Configuring VxVM Software.

How to Perform Postinstallation Setup and Configure Quorum Devices

Perform this procedure one time only, after the cluster is fully formed. Use this procedure to assign quorum votes and then to remove the cluster from installation mode.

Note –

You do not need to configure quorum devices in the following circumstances:

You chose automatic quorum configuration during Sun Cluster software configuration.
You used SunPlex Manager to install the cluster. SunPlex Manager assigns quorum votes and removes the cluster from installation mode for you.
You installed a single-node cluster.
You added a node to an existing cluster and already have sufficient quorum votes assigned.

Instead, proceed to How to Verify the Quorum Configuration and Installation Mode.

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
…

Are you adding a new node to an existing cluster?
- If no, proceed to Step 4.
- If yes, you might need to update the quorum configuration to accommodate your cluster's new configuration.
  
  See “Quorum Devices” in Sun Cluster Overview for Solaris OS and Sun Cluster Concepts Guide for Solaris OS for information about quorum. To change the quorum configuration, follow procedures in “Administering Quorum” in Sun Cluster System Administration Guide for Solaris OS. When the quorum configuration is satisfactory, go to How to Verify the Quorum Configuration and Installation Mode.

Determine the global device-ID name of each shared disk that you are configuring as a quorum device.

Use the scdidadm output from Step 2 to identify the device–ID name of each shared disk that you are configuring as a quorum device. For example, the output in Step 2 shows that global device d2 is shared by phys-schost-1 and phys-schost-2. You use this information in Step 7.

See Quorum Devices for further information about choosing quorum devices.

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

Tip –
If the quorum setup process is interrupted or fails to be completed successfully, rerun scsetup.

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

If your cluster has three or more nodes, quorum device configuration is optional.

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

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

Quit the scsetup utility.

Verify the quorum configuration and that installation mode is disabled.

Go to How to Verify the Quorum Configuration and Installation Mode.

How to Verify the Quorum Configuration and Installation Mode

Perform this procedure to verify that quorum configuration completed successfully and that cluster installation mode is disabled.

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

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

You do not need to be superuser to run this command.
% scconf -p | grep "install mode" Cluster install mode: disabled
Cluster installation is complete. You are now ready to install volume management software and to configure the cluster.
- To install Solstice DiskSuite software or configure Solaris Volume Manager software, go to Installing and Configuring Solstice DiskSuite/Solaris Volume Manager Software.
- SPARC: To install VERITAS Volume Manager software, go to SPARC: 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, perform this procedure to reconfigure the transport adapters or the private-network address.

Note –

If the node has already joined the cluster and is no longer in installation mode (see Step 2 of How to Verify the Quorum Configuration and Installation Mode), 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 System Administration Guide for Solaris OS.

Attempt to reinstall the node.

You can correct certain failed installations by repeating 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 that you are uninstalling.

From an active cluster member, add the node that you intend to uninstall to the cluster node-authentication list.

Skip this step if you are uninstalling a single-node cluster.
# /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 System Administration Guide for Solaris OS for procedures.

Become superuser on the node that you intend to uninstall.

Shut down the node that you intend to uninstall.
# shutdown -g0 -y -i0

Reboot the node into noncluster mode.

On SPARC based systems, do the following:
ok boot -x

On x86 based systems, do the following:

                    <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b
Boot args:

Type   b [file-name] [boot-flags] <ENTER>  to boot with options
or     i <ENTER>                           to enter boot interpreter
or     <ENTER>                             to boot with defaults

                 <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b -x

Change to a directory, such as the root (/) directory, that does not contain any files that are delivered by the Sun Cluster packages.
# cd /

Uninstall Sun Cluster software from the node.
# /usr/cluster/bin/scinstall -r
See the scinstall(1M) man page for more information.

Reinstall and reconfigure 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 the tasks.

Installing the Software

Task Map: Installing the Software

How to Prepare for Cluster Software Installation

How to Install Cluster Control Panel Software on an Administrative Console

How to Install Solaris Software

How to Install Sun Cluster Software Packages

How to Configure Sun Cluster Software on All Nodes (scinstall)

Example – Configuring Sun Cluster Software on All Nodes

Using SunPlex Manager to Install Sun Cluster Software

Installation Requirements

Test IP Addresses

Character-Set Limitations

How to Install SunPlex Manager Software

How to Install and Configure Sun Cluster Software (SunPlex Manager)

How to Install Solaris and Sun Cluster Software (JumpStart)

How to Install Sun Cluster Software on a Single-Node Cluster

Example—Installing Sun Cluster Software on a Single-Node Cluster

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

Example – Configuring Sun Cluster Software on an Additional Node

SPARC: How to Install VERITAS File System Software

How to Configure the Name-Service Switch

How to Set Up the Root Environment

How to Install Data-Service Software Packages (installer)

How to Install Data-Service Software Packages (scinstall)

How to Perform Postinstallation Setup and Configure Quorum Devices

How to Verify the Quorum Configuration and Installation Mode

How to Uninstall Sun Cluster Software to Correct Installation Problems

How to Configure Sun Cluster Software on All Nodes (`scinstall`)

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

How to Install Data-Service Software Packages (`installer`)

How to Install Data-Service Software Packages (`scinstall`)