How to Prepare the Cluster for Upgrade (Live Upgrade)

Perform this procedure to prepare a cluster for live upgrade.

Before You Begin

Perform the following tasks:

• Ensure that the configuration meets the requirements for upgrade. See Upgrade Requirements and Software Support Guidelines.

• Have available the installation media, documentation, and patches for all software products that you are upgrading, including the following software:

  • Solaris OS

  • Sun Cluster 3.2 11/09 framework

  • Sun Cluster 3.2 Core Patch

    • Solaris 9 OS - 125510–02

    • Solaris 10 OS on SPARC - 125511–02

    • Solaris 10 OS on x86 - 125512–02

  • Solaris 10 OS p7zip patch

    • On SPARC – 137321–01 (minimum)

    • On x86 – 137322–01 (minimum)

  • Sun Cluster 3.2 11/09 data services (agents)

  • Applications that are managed by Sun Cluster 3.2 11/09 data-services

  • Veritas Volume Manager, if applicable

  See Patches and Required Firmware Levels in the Sun Cluster Release Notes for the location of patches and installation instructions.

• If you use role-based access control (RBAC) instead of superuser to access the cluster nodes, ensure that you can assume an RBAC role that provides authorization for all Sun Cluster commands. This series of upgrade procedures requires the following Sun Cluster RBAC authorizations if the user is not superuser:

  • solaris.cluster.modify

  • solaris.cluster.admin

  • solaris.cluster.read

  See Role-Based Access Control (Overview) in System Administration Guide: Security Services for more information about using RBAC roles. See the Sun Cluster man pages for the RBAC authorization that each Sun Cluster subcommand requires.

1. Ensure that the cluster is functioning normally.

   1. View the current status of the cluster by running the following command from any node.

      • On Sun Cluster 3.1 8/05 software, use the following command:

        phys-schost% scstat

      • On Sun Cluster 3.2 software, use the following command:

        phys-schost% cluster status

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

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

   3. Check the volume-manager status.

2. If necessary, notify users that cluster services will be temporarily interrupted during the upgrade.

   Service interruption will be approximately the amount of time that your cluster normally takes to switch services to another node.

3. If Sun Cluster Geographic Edition software is installed, uninstall it.

   For uninstallation procedures, see the documentation for your version of Sun Cluster Geographic Edition software.

4. Become superuser on a node of the cluster.

5. Ensure that all shared data is backed up.

6. Ensure that each system disk is backed up.

Next Steps

Perform a live upgrade of the Solaris OS, Sun Cluster 3.2 11/09 software, and other software. Go to How to Upgrade the Solaris OS and Sun Cluster 3.2 11/09 Software (Live Upgrade).