Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Performing a Standard Upgrade of a Cluster

The following table lists the tasks to upgrade to Oracle Solaris Cluster 4.1 software or to a 4.1 SRU. By default, all Oracle Solaris packages are automatically upgraded.

Table 3-1 Task Map: Performing a Standard Upgrade for Oracle Solaris Cluster 4.1 Software

Task | Instructions
--- | ---
1. Read the upgrade requirements and restrictions. Determine the proper upgrade method for your configuration and needs. | Upgrade Requirements and Software Support Guidelines Choosing an Oracle Solaris Cluster Upgrade Method
2. If failover zones of brand type `solaris` are configured in the cluster, upgrade the failover zones. | Upgrading Failover Zones
3. If a quorum server is used, upgrade the Quorum Server software. | How to Upgrade Quorum Server Software
4. Remove the cluster from production and back up shared data. | How to Prepare the Cluster for Upgrade (Standard Upgrade)
5. Upgrade to Oracle Solaris Cluster 4.1 framework, data-service, and Geographic Edition software. If necessary, upgrade applications that support alternate boot environments. | How to Upgrade the Software (Standard Upgrade)
6. Use the `scversions` command to commit the cluster to the upgrade. | How to Commit the Upgraded Cluster
7. Verify successful completion of upgrade to Oracle Solaris Cluster 4.1 software. | How to Verify the Upgrade
8. Enable resources and bring resource groups online. Migrate existing resources to new resource types. If necessary, boot into noncluster mode and upgrade applications that do not support alternate boot environments. | How to Finish the Upgrade

## How to Upgrade Quorum Server Software

If the cluster uses a quorum server, upgrade the Quorum Server software on the quorum server before you upgrade the cluster.

Note - If more than one cluster uses the quorum server, perform on each cluster the steps to remove the quorum server and later the steps to add back the quorum server.

Perform all steps as the `root` role on the cluster and on the quorum server.

1. If the cluster has two nodes and the quorum server is the cluster's only quorum device, temporarily add a second quorum device.

   See Adding a Quorum Device in Oracle Solaris Cluster System Administration Guide.

   If you add another quorum server as a temporary quorum device, the quorum server can run the same software version as the quorum server that you are upgrading, or it can run the 4.1 version of Quorum Server software.

2. Unconfigure the quorum server from each cluster that uses the quorum server.

       phys-schost# clquorum remove quorumserver

3. From the quorum server to upgrade, verify that the quorum server no longer serves any cluster.

       quorumserver# clquorumserver show +

   If the output shows any cluster is still served by the quorum server, unconfigure the quorum server from that cluster. Then repeat this step to confirm that the quorum server is no longer configured with any cluster.

   Note - If you have unconfigured the quorum server from a cluster but the `clquorumserver show` command still reports that the quorum server is serving that cluster, the command might be reporting stale configuration information. See Cleaning Up Stale Quorum Server Cluster Information in Oracle Solaris Cluster System Administration Guide.

4. From the quorum server to upgrade, halt all quorum server instances.

       quorumserver# clquorumserver stop +

5. Uninstall the Quorum Server software from the quorum server to upgrade.

       quorumserver# pkg uninstall ha-cluster/*

6. (Optional) Clean up or remove the quorum server directories.

   By default, this directory is `/var/scqsd`.

7. Install the Oracle Solaris Cluster 4.1 Quorum Server software, reconfigure the quorum server, and start the quorum server daemon.

   Follow the steps in How to Install and Configure Oracle Solaris Cluster Quorum Server Software in Oracle Solaris Cluster Software Installation Guide for installing the Quorum Server software.

8. From a cluster node, configure the upgraded quorum server as a quorum device.

   Follow the steps in How to Configure Quorum Devices in Oracle Solaris Cluster Software Installation Guide.

9. If you configured a temporary quorum device, unconfigure it.

       phys-schost# clquorum remove tempquorum

## How to Prepare the Cluster for Upgrade (Standard Upgrade)

Perform this procedure to remove the cluster from production before you perform a standard upgrade. Performing a standard upgrade also upgrades the Oracle Solaris OS to the latest compatible version. Perform all steps from the global zone only.

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 software updates for all software products that you are upgrading, including the following software:

  - Oracle Solaris OS

  - Oracle Solaris Cluster

  - Applications that are managed by Oracle Solaris Cluster data services

  - Any other third-party applications to upgrade

  For instructions on updating single or multiple packages, see Chapter 11, Updating Your Software, in Oracle Solaris Cluster System Administration Guide.

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

  - `solaris.cluster.modify`

  - `solaris.cluster.admin`

  - `solaris.cluster.read`

  See Role-Based Access Control (Overview) in Oracle Solaris 11.1 Administration: Security Services for more information about using RBAC roles. See the Oracle Solaris Cluster man pages for the RBAC authorization that each Oracle Solaris 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.

          phys-schost% cluster status

      See the `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. Assume the `root` role on a node of the cluster.
3. If the cluster is configured with zone clusters, take offline each resource group and disable all resources in each zone cluster.

       # clresourcegroup offline -Z zonecluster resource-group
       # clresource disable -Z zonecluster resource
       # clresourcegroup unmanage -Z zonecluster resource-group

4. In the global zone, take offline each resource group and disable all resources.

   Take offline all resource groups in the cluster, including those that are in non-global zones. Then disable all resources, to prevent the cluster from bringing the resources online automatically if a node is mistakenly rebooted into cluster mode.

   - To use the `clsetup` utility, perform the following steps:
     1. Start the utility.

            phys-schost# clsetup

        The Main Menu is displayed.

     2. Choose the menu item, Resource Groups.

        The Resource Group Menu is displayed.

     3. Choose the menu item, Online/Offline or Switchover a Resource Group.
     4. Follow the prompts to take offline all resource groups and to put them in the unmanaged state.
     5. When all resource groups are offline, type `q` to return to the Resource Group Menu.
     6. Exit the `clsetup` utility.

        Type `q` to back out of each submenu or press `Ctrl-C`.

   - To use the command line, perform the following steps:
     1. Take each resource group offline.

            phys-schost# clresourcegroup offline resource-group

     2. From any node, list all enabled resources in the cluster.

            phys-schost# clresource show -p Enabled
            === Resources ===

            Resource:                                       resource
              Enabled{nodename1}:                               True
              Enabled{nodename2}:                               True
            …

     3. Identify those resources that depend on other resources.

            phys-schost# clresource show -p resource_dependencies
            === Resources ===

            Resource:                                       node
              Resource_dependencies:                           node
            …

        You must disable dependent resources first before you disable the resources that they depend on.

     4. Disable each enabled resource in the cluster.

            phys-schost# clresource disable resource

        See the `clresource`(1CL) man page for more information.

     5. Verify that all resources are disabled.

            phys-schost# clresource show -p Enabled
            === Resources ===

            Resource:                                       resource
              Enabled{nodename1}:                               False
              Enabled{nodename2}:                               False
            …

     6. Move each resource group to the unmanaged state.

            phys-schost# clresourcegroup unmanage resource-group

5. Verify that all resources on all nodes are `Offline` and that all resource groups are in the `Unmanaged` state.

       phys-schost# cluster status -t resource,resourcegroup

6. Stop all applications that are running on each node of the cluster.
7. Ensure that all shared data is backed up.
8. Ensure that each system disk is backed up.

Next Steps

Upgrade the cluster and OS software. Go to How to Upgrade the Software (Standard Upgrade).

## How to Upgrade the Software (Standard Upgrade)

A standard upgrade upgrades a cluster to a new release, including installed data service software, and upgrades the Oracles Solaris OS to the latest compatible version. You do not need to place the cluster in noncluster mode before performing this upgrade because the upgrade always occurs in the new boot environment and the existing boot environment remains unchanged. You can specify a name for the new boot environment or you can use the auto-generated name.

If you do not want to upgrade all of your software to the latest available version, you can prevent certain components from being upgraded. You can do this by freezing individual packages or incorporations, or by disabling the appropriate publisher. For instructions, see Chapter 5, Configuring Installed Images, in Adding and Updating Oracle Solaris 11.1 Software Packages or the `pkg`(1) man page.

Any time you upgrade the Oracle Solaris Cluster software, by default you also upgrade the data services and Geographic Edition software.

Note - If you want to install any individual Oracle Solaris Cluster SRUs, instead see How to Update a Specific Package in Oracle Solaris Cluster System Administration Guide.

Oracle Solaris 11.2 software requires Oracle Solaris Cluster 4.1 SRU 8.

Before You Begin

If you have failover zones of brand type `solaris` configured on the cluster, you must perform additional steps. Follow the instructions in How to Upgrade a Failover Zone before you begin this procedure. If you have a `solaris10` brand zone in a zone cluster, follow the instructions in Upgrading a `solaris10` Brand Zone in a Zone Cluster.

1. Assume the `root` role or assume a role that provides `solaris.cluster.admin` RBAC authorization.
2. Subscribe to the `ha-cluster` publisher that contains the software you want to upgrade to.

       # pkg set-publisher -G '*' -g URL_for_ha-cluster_publisher ha-cluster

3. Ensure that the `solaris` publisher is valid.

       # pkg publisher
       PUBLISHER                           TYPE     STATUS   URI
       solaris                             origin   online   solaris-repository

   For information about setting the `solaris` publisher, see Adding and Updating Oracle Solaris 11.1 Software Packages.

4. Run the upgrade.

   If you are upgrading a failover zone, follow the instructions in How to Upgrade a Failover Zone.

   - To use the command line, perform the following:

         # scinstall -u update [-b bename]

     You can choose to specify a name for the new boot environment with the `-b bename` option.

   - To use the interactive `scinstall` utility, perform the following:

     Note - The cluster nodes must be installed with at least 4.0 SRU 2.

     1. Start the `scinstall` utility.

            phys-schost# scinstall

        The `scinstall` Main Menu is displayed.

     2. Choose the menu item, Upgrade This Cluster Node.

              *** Main Menu ***

                Please select from one of the following (*) options:

                    1) Create a new cluster or add a cluster node
                  * 2) Upgrade this cluster node
                  * 3) Print release information for this cluster node

                  * ?) Help with menu options
                  * q) Quit

                Option:  2

        The Upgrade Menu is displayed.

     3. Choose the menu item, Upgrade This Cluster Node.
     4. Follow the menu prompts to upgrade the cluster framework, data service agents, and underlying OS.

        Upgrade processing is finished when the system displays the message `Completed Oracle Solaris Cluster framework upgrade` and prompts you to press Enter to continue.

     5. Quit the `scinstall` utility.
5. As needed, upgrade other applications that support alternate boot environments.
6. Boot the machine into the new boot environment.
   - If you need to upgrade any applications that do not support alternate boot environments, boot into the new boot environment in noncluster mode.

     Add the `-x` option to the boot command to boot into noncluster mode.

   - Otherwise, follow the prompts to boot the machine into the new boot environment.

Next Steps

Go to Chapter 5, Completing the Upgrade.

Copyright © 2000, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |