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 3.1 10/03 Release Notes - 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.
Sun Cluster 3.1 10/03 Concepts Guide - Overview of the Sun Cluster product.
Sun Cluster 3.1 10/03 Software Installation Guide (this manual) - Planning guidelines and procedures for installing and configuring Solaris, Sun Cluster, and volume-manager software.
Sun Cluster 3.1 Data Service Planning and Administration Guide - Planning guidelines and procedures 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 product documentation that you might need for reference during cluster installation.
Solaris software
Solstice DiskSuite/Solaris Volume Manager software
VERITAS Volume Manager
Sun Management Center
Third-party applications such as ORACLE
Plan your cluster configuration.
Caution - Plan your cluster installation completely. Identify requirements for all data services and third-party products before you begin Solaris and Sun Cluster software installation. Failure to do so might result in installation errors
that require that you completely reinstall the Solaris and Sun Cluster software. For example, the Oracle Parallel Fail Safe/Real Application Clusters Guard option of Oracle Parallel Server/Real Application Clusters has special requirements for the hostnames that you use in the cluster. Another example with special requirements is Sun Cluster HA for SAP. You must accommodate these requirements before you install Sun Cluster software because you cannot change hostnames after you install Sun Cluster software.
Use the planning guidelines in Chapter 1, Planning the Sun Cluster Configuration and in the Sun Cluster 3.1 Data Service Planning and Administration Guide to determine how to install and configure your cluster.
Fill out the cluster framework and data-services configuration worksheets. 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.
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.
(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.
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 the Administrative Console.
If no, go to one of the following procedures.
To install Sun Cluster software by using either the scinstall(1 M) 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 the 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 the administrative console. The CCP provides a launchpad for the cconsole(1M), ctelnet(1M), and crlogin(1M) tools. Each of these tools provides a multiple-window connection to a set of nodes. These tools also provide a common window that sends input to all nodes at one time.
You can use any desktop machine that runs the Solaris 8 or Solaris 9 operating environment as an administrative console. In addition, you can also use the administrative console as a Sun Management Center console or server as well as a documentation server. See Sun Management Center documentation for information on how to install Sun Management Center software. See the Sun Cluster 3.1 10/03 Release Notes for information on how to install Sun Cluster documentation.
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 Solaris End User System Support software group.
(Optional) If you intend to use the Web Start program with a GUI, ensure that the DISPLAY environment variable is set.
Insert the Sun Cluster 3.1 10/03 CD-ROM into the CD-ROM drive of the administrative console.
If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_1_u1 directory.
Become superuser on the administrative console.
Change to the /cdrom/suncluster_3_1_u1 directory.
# cd /cdrom/suncluster_3_1_u1
Start the Web Start program.
# ./installer
Choose Custom installation.
The utility displays a list of software packages.
Deselect the Sun Cluster Framework package.
Select the Sun Cluster cconsole package.
(Optional) Select the Sun Cluster Documentation package.
If you do not install the documentation on your administrative console, you can still view an HTML or PDF collection directly from the CD-ROM.
Follow onscreen instructions to continue package installation.
After installation is finished, you can view any available installation log.
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.
For a Sun Fire 15000 system controller, use telnet(1) port number 23 for the serial port number of each entry.
For all other console-access devices, use the telnet serial port number, not the physical port number. To determine the telnet serial port number, add 5000 to the physical port number. For example, if a physical port number is 6, the telnet serial port number is 5006.
For Sun Enterprise 10000 servers, also see the /opt/SUNWcluster/bin/serialports(4) man page for details and special considerations.
# vi /etc/serialports node1 ca-dev-hostname port node2 ca-dev-hostname port
node1, node2 Physical names of the cluster nodes
ca-dev-hostname Hostname of the console-access device
port Serial port number
(Optional) For convenience, add the PATH to the /opt/SUNWcluster/bin directory and the /opt/SUNWcluster/man directory to the MANPATH on the administrative console.
If you installed the SUNWscman package, also add the /usr/cluster/man directory to the MANPATH.
Start the CCP utility.
# /opt/SUNWcluster/bin/ccp &
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 3.1 10/03 System Administration Guide for 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 Preinstall 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).