To add a new node to an existing cluster, do not use SunPlex Manager. Instead, use the procedure How to Install 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 installing 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.
The following table lists SunPlex Manager installation requirements for these additional software products.
Table 2–2 Requirements to Use SunPlex Manager to Install Software
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 has four shared disks connected, 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–3 Metasets Installed by SunPlex Manager
Shared Disks |
Metaset Name |
Cluster File System Mount Point |
Purpose |
---|---|---|---|
First pair of shared disks |
mirror-1 |
/global/mirror-1 |
Sun Cluster HA for NFS or Sun Cluster HA for Apache scalable data service, or both |
Second pair of shared disks |
mirror-2 |
/global/mirror-2 |
Unused |
Third pair of shared disks |
mirror-3 |
/global/mirror-3 |
Unused |
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.
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 Open Net Environment (Sun ONE) services – If the password contains unusual characters, these characters are stripped out, resulting in one of the following problems:
The resulting password has less than eight characters and therefore fails.
The application is configured with a different password than the user expects.
Localization – Alternative character sets, for example, accented characters or Asian characters, do not work for input.
This procedure describes how to install SunPlex Manager software on your cluster.
If you intend to install Sun Cluster software by using another method, you do not need to perform this procedure. The scinstall command automatically installs SunPlex Manager for you as part of the installation process.
Perform this procedure on each node of the cluster.
Ensure that Solaris software and patches are installed on each node of the cluster.
You must install Solaris software as described in How to Install Solaris Software.
If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster software. You must also ensure that the installation meets the requirements for any other software that you intend to install on the cluster.
Become superuser on a cluster node.
Are Apache software packages installed on the node?
If yes, proceed to Step 4.
If no, install Apache software packages.
Insert the Solaris 8 Software 2 of 2 CD-ROM into the CD-ROM drive of the node.
If the Volume Management daemon vold(1M) is running and is configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM.
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 |
Install the Apache software packages in the following order.
# pkgadd -d . SUNWapchr SUNWapchu SUNWapchd |
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.
Insert the Sun Cluster 3.1 10/03 CD-ROM into the CD-ROM drive of the node.
If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_1_u1 directory.
Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Packages directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
The following example uses the path to the Solaris 8 version of Sun Cluster software.
# cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_8/Packages |
Install the SunPlex Manager software packages. Answer yes for all prompts.
# pkgadd -d . SUNWscva SUNWscvr SUNWscvw |
Is the root password the same on every node of the cluster?
If yes, proceed to Step 7.
If no, set the root password to the same value on each node of the cluster. If necessary, also use the chkey(1) command to update the RPC key pair.
# passwd Enter new password # chkey -p |
The root password must be the same on all nodes in the cluster to use the root password to access SunPlex Manager.
Use SunPlex Manager to install Sun Cluster software.
Go to How to Install Sun Cluster Software (SunPlex Manager).
To add a new node to an existing cluster, do not use SunPlex Manager. Instead, go to How to Install Sun Cluster Software on Additional Cluster Nodes (scinstall).
Perform this procedure to use SunPlex Manager to install Sun Cluster software and patches on all nodes in the cluster in a single operation. In addition, you can use this procedure to install Solstice DiskSuite software and patches (Solaris 8) or to configure Solaris Volume Manager mirrored disksets (Solaris 9).
If you use SunPlex Manager to install Solstice DiskSuite software or to configure Solaris Volume Manager disksets, you can also install 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 cluster nodes, your choice of data services to install, and the number of disks 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.
Have available the following completed configuration planning worksheets:
See Chapter 1, Planning the Sun Cluster Configuration and the Sun Cluster 3.1 Data Service Planning and Administration Guide for planning guidelines.
Prepare file-system paths to a CD-ROM image of each software product that you intend to install.
Provide each CD-ROM image in a location that is available to each node.
The CD-ROM images must be accessible to all nodes of the cluster from the same file-system path. These paths can be one or more of the following locations:
CD-ROM drives 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.
Record the path to each CD-ROM image.
You specify this information in Step 17.
Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?
If no, proceed to Step 7.
If yes, install additional packages from the Sun Cluster 3.1 10/03 CD-ROM that are required to support the RSMAPI or SCI-PCI adapters. SunPlex Manager does not automatically install these packages. The following table lists the Sun Cluster 3.1 10/03 packages and the order in which you must install the packages.
Feature |
Additional Sun Cluster 3.1 10/03 Packages to Install |
---|---|
RSMAPI |
SUNWscrif |
SCI-PCI adapters |
SUNWsci SUNWscid SUNWscidx |
Use the following command to install these additional packages. Replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).
# cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_ver/Packages # pkgadd -d . packages |
Are there any patches that are required to support Sun Cluster or Solstice DiskSuite software?
Do you intend to use SunPlex Manager to install patches?
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.
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.
Ensure that the patches are uncompressed.
Record the path to the patch directory.
You specify this information in Step 17.
From the administrative console or any other machine outside the cluster, launch a browser.
Disable the browser's Web proxy.
SunPlex Manager installation functionality is incompatible with Web proxies.
Ensure that disk caching and memory caching is enabled.
The disk cache and memory cache size must be greater than 0.
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.
If SunPlex Manager displays the administration interface instead of the Sun Cluster Installation screen, Sun Cluster software is already installed on that node. Check that the name of the node in the URL is the correct name of the cluster node to install.
If the browser displays a New Site Certification window, follow the onscreen instructions to accept the certificate.
Log in as superuser.
In the Sun Cluster Installation screen, verify that the cluster meets the listed requirements for using SunPlex Manager.
The Solaris End User Software Group or higher is installed.
Root-disk partitions include the following:
At least 750 Mbytes for swap
A 512-Mbyte slice with the mount point /globaldevices
A 20-Mbyte slice with the mount point /sds for volume manager use
File system paths to all needed CD-ROM images and patches are set up, as described in Step 5 through Step 9.
If you meet all listed requirements, click Next to continue to the next screen.
Type a name for the cluster and select the number of nodes in your cluster.
The default number of nodes that are displayed might be higher than the number of nodes you intend to install in your cluster. If so, select the correct number of nodes you intend to install. This situation might occur if other nodes that are ready to be installed by SunPlex Manager use the same public network as the nodes that you intend to install.
You can use the Back button to return to a previous screen and change your information. However, SunPlex Manager does not save the information that you supplied in the later screens. When you click Next, you must again type or select your configuration information in those screens.
Type the name of each cluster node.
SunPlex Manager supplies as defaults the names of nodes that the GUI finds on the public network that are ready to be installed by SunPlex Manager. If you specify a larger number of nodes to install than exist on the network, SunPlex Manager supplies additional default names. These additional names follow the naming convention phys-clustername-N.
SunPlex Manager might list nodes other than the ones you intend to install in your cluster. This situation occurs under the following conditions:
The other nodes use the same public network as the nodes that you are installing.
The other nodes are installed with SunPlex Manager software but are not yet installed with Sun Cluster software.
If SunPlex Manager supplies the name of a node that you do not want in your cluster, type over the name with the correct node name.
From the pull-down lists for each node, select the names of the two adapters that are used for the private interconnects.
Refer to your completed “Cluster Interconnect Worksheet” for the appropriate adapter names for each node.
Choose whether to install Solstice DiskSuite software (Solaris 8) or to configure Solaris Volume Manager mirrored disksets (Solaris 9).
You must install Solstice DiskSuite software (Solaris 8) or configure Solaris Volume Manager mirrored disksets (Solaris 9) if you intend to install the Sun Cluster HA for NFS or Sun Cluster HA for Apache data service.
When SunPlex Manager installs Solstice DiskSuite software or configures Solaris Volume Manager disksets, any data on all shared disks is lost.
In Step 15, did you choose to install Solstice DiskSuite software or configure Solaris Volume Manager disksets?
If no, proceed to Step 17.
If yes, choose whether to install Sun Cluster HA for NFS, Sun Cluster HA for Apache, or both.
Refer to your completed “Network Resources” worksheet for the appropriate logical hostname or shared address.
For Sun Cluster HA for NFS, also specify the logical hostname that the data service is to use and a test IP address for each node.
For Sun Cluster HA for Apache, also specify the shared address that the data service is to use and a test IP address for each node.
Type the path for each CD-ROM image that is needed to install the packages you specified, and optionally the path for the patch directory.
Type each path in the appropriate path field for each software package, as shown in the following table. If you have already installed the required patches, leave the Patch Directory Path field blank.
Software Package to Install |
Name of CD-ROM Image Path Field |
---|---|
Solstice DiskSuite |
Solaris CD-ROM Path |
Sun Cluster |
Sun Cluster 3.1 10/03 CD-ROM Path |
Sun Cluster HA for NFS, Sun Cluster HA for Apache |
Sun Cluster 3.1 Agents CD-ROM Path |
Sun Cluster patches, Solstice DiskSuite patches |
Patch Directory Path |
Each specified path for a CD-ROM image must be the directory that contains the .cdtoc file for the CD-ROM.
Choose whether to validate the cluster configuration by using the sccheck(1M) utility.
If the sccheck utility detects no problems, SunPlex Manager displays the Confirm Information screen. Proceed to Step 19.
If the sccheck utility detects problems, SunPlex Manager displays information about the problems found and prompts you for your next action. If you must quit SunPlex Manager to correct the problem, return to Step 10 to restart SunPlex Manager. Otherwise, proceed to Step 19.
If the sccheck utility quits with an error message that a version of Sun Explorer software earlier than 3.5.1 is installed, click Cancel to stop installation. Remove the existing SUNWexplo package and install the SUNWexplo package that is supplied on the Sun Cluster 3.1 10/03 CD-ROM. Then restart SunPlex Manager.
Is the information that you supplied correct as displayed in the Confirm Information screen?
If yes, proceed to Step 20.
If no, perform the following steps to correct the configuration information.
Click Back until you return to the screen with the information to change.
When you click Back to back up to a previous screen, any information that you typed in the subsequent screens is lost.
Type the correct information and click Next.
Retype or reselect the information in each screen until you return to the Confirm Information screen.
Verify that the information in the Confirm Information screen is now correct.
Click Begin Installation to start the installation process.
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.
During installation, the screen displays brief messages about the status of the cluster installation process. When installation is complete, the browser displays the cluster monitoring and administration GUI.
SunPlex Manager installation output is logged in the /var/cluster/spm/messages file.
Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.
Log back into SunPlex Manager to verify quorum assignments and to modify the 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.
Set up the name-service look-up order.