Installing Patches

You must run the same patch levels for Sun Cluster and common agent container on all nodes of both clusters.

The patch level for each node on which you have installed the Sun Cluster Geographic Edition software must meet the Sun Cluster patch-level requirements.

All nodes in one cluster must have the same version of the 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, for a limited amount of time. For example, if one cluster is running sun Cluster Geographic Edition 3.1 8/05 software that has been fully patched, and the partner cluster is running Sun Cluster Geographic Edition 3.1 2006Q4 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.1 2006Q4, 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.

Use the information in this section to install patches before you start the Sun Cluster Geographic Edition infrastructure.

For additional information about Sun Cluster Geographic Edition patches, see the patch README file.

See Required Patches in Sun Cluster Geographic Edition 3.1 2006Q4 Release Notes for a list of required patches.

How to Prepare the Cluster for Patch Installation

1. Ensure that the cluster is functioning properly.

   To view the current status of the cluster, run the following command from any node:

   % scstat

   See the scstat(1M) man page for more information.

   Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

   Check the volume manager status.

2. On a node of the cluster, become root.

   % su

3. Remove all application resource groups from protection groups.

   Highly available applications do not have downtime during the Sun Cluster Geographic Edition software patch installation.

   # geopg remove-resource-group resourcegroup protectiongroupname

   See the geopg(1M) man page for more information.

4. Perform the preceding steps on all clusters that have a partnership with this cluster.

5. Stop all protection groups that are active on the cluster.

   # geopg stop protectiongroupname -e local | global

   See the geopg(1M) man page for more information.

6. Stop the Sun Cluster Geographic Edition infrastructure.

   # geoadm stop

   See the geoadm(1M) man page for more information.

7. Stop the common agent container.

   # /opt/SUNWcacao/bin/cacaoadm stop

   ---

   Note –

   You must use common agent container 1.1, which is located in /opt/SUNWcacao/bin. Use the /opt/SUNWcacao/bin/cacaoadm -V command to check which version of common agent container you are using.

   ---

Next Steps

Install the required patches for the Sun Cluster Geographic Edition software. Go to How to Install Patches.

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.

Before You Begin

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.

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

   % scstat

   See the scstat(1M) man page for more information.

   Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.

2. Install any necessary patches to support Sun Cluster Geographic Edition software by using the patchadd command.

3. After you have installed all required patches on all the nodes of all clusters, start the common agent container.

   # /opt/SUNWcacao/bin/cacaoadm start

   ---

   Note –

   You must use common agent container 1.1, which is located in /opt/SUNWcacao/bin. Use the /opt/SUNWcacao/bin/cacaoadm -V command to check which version of common agent container you are using.

   ---

4. Enable the Sun Cluster Geographic Edition software.

   # geoadm start

5. Add all application resource groups you removed while you were preparing the cluster for a patch installation back to the protection group.

   # geopg add-resource-group resourcegroup protectiongroupname

   See the geopg(1M) man page for more information.

6. Start all the protection groups that you have added.

   # geopg start protectiongroupname -e local | global [-n]

   See the geopg(1M) man page for more information.

Next Steps

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 4, Enabling and Configuring the Sun Cluster Geographic Edition Software.