test

Sun Cluster 3.2 Release Notes for Solaris OS

Patches and Required Firmware Levels

This section provides information about patches for Sun Cluster configurations. If you are upgrading to Sun Cluster 3.2 software, see Chapter 8, Upgrading Sun Cluster Software, in Sun Cluster Software Installation Guide for Solaris OS. Applying a Sun Cluster 3.2 Core patch does not provide the same result as upgrading the software to the Sun Cluster 3.2 release.

Note –

Read the patch README before applying or removing any patch.

If you are using the rebooting patch (node) method to install the Sun Cluster core patch, 125510 (S9/SPARC), 125511 (S10/SPARC), or 125512 (S19/x64), you must have the -02 version of the patch installed before you can install higher versions of the patch. If you do not have the -02 patch installed and wish to install -03 or higher (when available) you must use the rebooting cluster method.

See the following list for examples of patching scenarios:

Note –

You must be a registered SunSolveTM user to view and download the required patches for the Sun Cluster product. If you do not have a SunSolve account, contact your Sun service representative or sales engineer, or register online at http://sunsolve.sun.com.

Applying the Sun Cluster 3.2 Core Patch

Complete the following procedure to apply the Sun Cluster 3.2 core patch.

ProcedureHow to Apply the Sun Cluster 3.2 Core Patch

  1. Install the patch using the usual rebooting patch procedure for a core patch.

  2. Verify that the patch has been installed correctly on all nodes and is functioning properly.

  3. Register the new version of resource types SUNW.HAStoragePlus, SUNW.ScalDeviceGroup, and SUNW.ScalMountPoint that are being updated in this patch. Perform resource type upgrade on any existing resources of these types to the new versions.

    For information about registering a resource type, see Registering a Resource Type in Sun Cluster Data Services Planning and Administration Guide for Solaris OS in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

    Caution – Caution –

    If the Sun Cluster 3.2 core patch is removed, any resources that were upgraded in step 3 must be downgraded to the earlier resource type versions. The procedure for downgrading will require planned downtime of these services. Therefore, do not perform step 3 until you are ready to commit the Sun Cluster 3.2 core patch permanently to your cluster.

Removing the Sun Cluster 3.2 Core Patch

Complete the following procedure to remove the Sun Cluster 3.2 core patch.

ProcedureHow to Remove the Sun Cluster 3.2 Core Patch

  1. List the resource types on the cluster.


    # clrt list

  2. If the list returns SUNW.HAStoragePlus:5, SUNW.ScalDeviceGroup:2, or SUNW.ScalMountPoint:2, you must remove these resource types. For instructions on removing a resource type, see How to Remove a Resource Type in Sun Cluster Data Services Planning and Administration Guide for Solaris OS in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

  3. Reboot all nodes of the cluster into noncluster, single user mode.

    For instructions on rebooting cluster nodes into noncluster, single user mode, see How to Boot a Cluster Node in Noncluster Mode in Sun Cluster System Administration Guide for Solaris OS in Sun Cluster System Administration Guide for Solaris OS.

  4. Remove the Sun Cluster 3.2 core patch from each node on which you installed the patch.


    # patchrm patch-id

  5. Reboot into cluster mode all of the nodes from which you removed the Sun Cluster 3.2 core patch.

    Rebooting all of the nodes from which you removed the Sun Cluster 3.2 core patch before rebooting any unaffected nodes ensures that the cluster is formed with the correct information in the CCR. If all nodes on the cluster were patched with the core patch, you can reboot the nodes into cluster mode in any order.

    For instructions on rebooting nodes into cluster mode, see How to Reboot a Cluster Node in Sun Cluster System Administration Guide for Solaris OS in Sun Cluster System Administration Guide for Solaris OS.

  6. Reboot any remaining nodes into cluster mode.

Patch Management Tools

The PatchPro patch management technology is now available as Patch Manager 2.0 for Solaris 9 OS and as Sun Update Connection 1.0 for Solaris 10 OS.

If some patches must be applied when the node is in noncluster mode, you can apply them in a rolling fashion, one node at a time, unless a patch's instructions require that you shut down the entire cluster. Follow procedures in How to Apply a Rebooting Patch (Node) in Sun Cluster System Administration Guide for Solaris OS to prepare the node and boot it into noncluster mode. For ease of installation, consider applying all patches at once to a node that you place in noncluster mode.

SunSolve Online

The SunSolve Online Web site provides 24-hour access to the most up-to-date information regarding patches, software, and firmware for Sun products. Access the SunSolve Online site at http://sunsolve.sun.com for the most current matrixes of supported software, firmware, and patch revisions.

Sun Cluster 3.2 third-party patch information is provided through a SunSolve Info Doc. This Info Doc page provides any third-party patch information for specific hardware that you intend to use in a Sun Cluster 3.2 environment. To locate this Info Doc, log on to SunSolve. From the SunSolve home page, type Sun Cluster 3.x Third-Party Patches in the search criteria box.

Before you install Sun Cluster 3.2 software and apply patches to a cluster component (Solaris OS, Sun Cluster software, volume manager software, data services software, or disk hardware), review each README file that accompanies the patches that you retrieved. All cluster nodes must have the same patch level for proper cluster operation.

For specific patch procedures and tips on administering patches, see Chapter 10, Patching Sun Cluster Software and Firmware, in Sun Cluster System Administration Guide for Solaris OS.