This chapter describes how to install Sun Cluster Geographic Edition software on a pair of clusters. This chapter also provides a procedure to uninstall Sun Cluster Geographic Edition software.
This chapter contains the following sections:
You can install Sun Cluster Geographic Edition software on a running cluster without disruption. Because the Sun Cluster Geographic Edition software installation process does not require you to restart Sun Cluster software, the cluster remains in production with services running.
The installer program offers two interactive installation modes, graphical user interface (GUI) and text-based interface. The graphical mode provides a wizard that guides you, step by step, through the tasks that you need to perform to install the Sun Cluster Geographic Edition components. The text-based mode provides the same functions that the GUI provides. However, this mode prompts you for responses on a line-by-line basis, rather than by means of a wizard.
Ensure that you have installed all the required patches for your cluster configuration on each node of every cluster before you start installing the software. See Required Patches in Sun Cluster Geographic Edition 3.2 2/08 Release Notes for the location of patches and installation instructions.
You must install Sun Cluster Geographic Edition software on all nodes of all clusters in a partnership.
You must install Sun Cluster Geographic Edition software on every node of each cluster in your geographically separated cluster by using the installer program.
This procedure explains how to install Sun Cluster Geographic Edition software.
Before you begin to install software, make the following preparations:
Ensure that the Solaris OS is installed to support Sun Cluster Geographic Edition software.
If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster Geographic Edition software and any other software that you intend to install on the cluster.
Read Chapter 1, Planning the Sun Cluster Geographic Edition Installation.
Read the following manuals, which contain information that can help you plan your configuration and prepare your installation strategy:
Sun Cluster Geographic Edition 3.2 2/08 Release Notes – Restrictions, bug workarounds, and other late-breaking information.
Documentation for all third-party software products.
To use the installer program with a GUI, ensure that the display environment of the cluster node to install is set to display the GUI.
% xhost + % setenv DISPLAY nodename:0.0 |
If the display environment is not set to display the GUI, the installer program instead displays in test-based mode.
Become superuser on a node where you intend to install the Sun Cluster Geographic Edition software.
Sun Cluster Geographic Edition software must be installed on all nodes of each cluster in the partnership.
Load the Sun Java Availability Suite installation DVD-ROM into the DVD-ROM drive.
If the volume management daemon vold(1M) is running and is configured to manage CD-ROM or DVD devices, the daemon automatically mounts the media on the /cdrom/cdrom0/ directory.
Change to the installation wizard directory of the DVD-ROM.
Start the installer program.
# ./installer |
The installer starts and displays the Welcome page. To exit the installer at any time, click Cancel. For more information about the installer program, see Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX.
Follow instructions on the screens to read and accept the Software License Agreement.
After you accept the license terms, the Choose Software Components menu is displayed.
Select Sun Cluster Geographic Edition 3.2 2/08 and press Return.
The Confirm Choices screen is displayed.
Press Return to confirm your choice.
The Sun Cluster Geographic Edition 3.2 2/08 submenu is displayed.
Follow onscreen instructions to select the following products from the Sun Cluster Geographic Edition submenu.
When prompted, choose whether to install multilingual packages.
If you choose to install multilingual packages, ensure that all nodes of the cluster have the same default locale.
When prompted, choose to upgrade shared components.
The installer begins to install the software packages. After the installation is finished, you can view any available installation log.
Unload the Sun Java Availability Suite installation DVD-ROM from the DVD-ROM drive.
Repeat this procedure on each node of each partner cluster.
Install required patches. Go to Installing Patches.
Configure Sun Cluster Geographic Edition software on the clusters. Go to Chapter 3, Enabling and Configuring the Sun Cluster Geographic Edition Software.
Observe the following guidelines and requirements to patch Sun Cluster Geographic Edition software:
You must run the same patch levels for Sun Cluster software and the common agent container software on all nodes of both clusters.
The patch level for each node on which you have installed Sun Cluster Geographic Edition software must meet the Sun Cluster patch-level requirements.
All nodes in one cluster must have the same version of Sun Cluster Geographic Edition software and the same patch level. However, primary and secondary clusters can run different versions of Sun Cluster Geographic Edition software, provided that each version is correctly patched and the versions are no more than one release different. For example, if one cluster is running Sun Cluster Geographic Edition 3.2 software that has been fully patched, and the partner cluster is running Sun Cluster Geographic Edition 3.2 2/08 software that has been fully patched, then both clusters should be brought to the same patch level as soon as possible. Also, if both partner clusters are running Sun Cluster Geographic Edition 3.2 2/08, then both partner clusters should be brought to the same patch level as soon as possible.
To ensure that the patches have been installed properly, install the patches on your secondary cluster before you install the patches on the primary cluster.
For additional information about Sun Cluster Geographic Edition patches, see the patch README file.
See Required Patches in Sun Cluster Geographic Edition 3.2 2/08 Release Notes for a list of required patches.
Ensure that the cluster is functioning properly.
To view the current status of the cluster, run the following command from any node:
% cluster status |
See the cluster(1CL) man page for more information.
Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
Become superuser on a node of the cluster.
Remove all application resource groups from protection groups.
This step ensures that resource groups are not stopped when you later stop the protection groups.
# geopg remove-resource-group resourcegroup protectiongroup |
See the geopg(1M) man page for more information.
Perform the preceding steps on all clusters that have a partnership with this cluster.
Stop all protection groups that are active on the cluster.
# geopg stop protectiongroup -e local |
See the geopg(1M) man page for more information.
Stop the Sun Cluster Geographic Edition infrastructure.
# geoadm stop |
Shutting down the infrastructure ensures that a patch installation on one cluster does not affect the other cluster in the partnership.
See the geoadm(1M) man page for more information.
On each node, stop the common agent container.
# /usr/sbin/cacaoadm stop |
You must use common agent container 2, which is located in the /usr/sbin directory. Use the /usr/sbin/cacaoadm -V command to check which version of common agent container you are using.
Install the required patches for the Sun Cluster Geographic Edition software. Go to How to Install Patches.
Perform this procedure on all nodes of the cluster.
Patch the secondary cluster before you patch the primary cluster, to permit testing.
Perform the following tasks:
Ensure that the Solaris OS is installed to support Sun Cluster Geographic Edition software.
If Solaris software is already installed on the node, you must ensure that the Solaris installation meets the requirements for Sun Cluster Geographic Edition software and any other software that you intend to install on the cluster.
Ensure that Sun Cluster Geographic Edition software packages are installed on the node.
Ensure that you completed all steps in How to Prepare the Cluster for Patch Installation.
Ensure that all the nodes are online and part of the cluster.
To view the current status of the cluster, run the following command from any node:
% cluster status |
See the cluster(1CL) man page for more information.
Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
Become superuser on each node.
On each node, install any necessary patches to support Sun Cluster Geographic Edition software by using the patchadd command.
If you are applying Sun Cluster patches, use the Sun Cluster methods on both clusters.
After you have installed all required patches on all nodes of the cluster, on each node start the common agent container.
# /usr/sbin/cacaoadm start |
You must use common agent container 2, which is located in the /usr/sbin directory. Use the /usr/sbin/cacaoadm -V command to check which version of common agent container you are using.
On one node, enable Sun Cluster Geographic Edition software.
# geoadm start |
Add all application resource groups that you removed while you were preparing the cluster for a patch installation back to the protection group.
# geopg add-resource-group resourcegroup protectiongroup |
See the geopg(1M) man page for more information.
Start all the protection groups that you have added.
# geopg start protectiongroup -e local [-n] |
See the geopg(1M) man page for more information.
After you patch the secondary cluster, perform a sanity test on the Sun Cluster Geographic Edition software, and then repeat this procedure on the primary cluster.
Configure Sun Cluster Geographic Edition software on the clusters. Go to Chapter 3, Enabling and Configuring the Sun Cluster Geographic Edition Software.