JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Upgrade Guide     Oracle Solaris Cluster 4.0
search filter icon
search icon

Document Information

Preface

1.  Preparing to Upgrade Oracle Solaris Cluster Software

2.  Upgrading Zones Managed by HA for Oracle Solaris Zones

3.  Performing a Standard Upgrade

4.  Performing a Rolling Upgrade

Performing a Rolling Upgrade of a Cluster

How to Upgrade Quorum Server Software

How to Prepare a Cluster Node for a Rolling Upgrade

How to Perform a Rolling Upgrade of the Solaris OS

How to Perform a Rolling Upgrade

5.  Completing the Upgrade

6.  Recovering From an Incomplete Upgrade

Index

Performing a Rolling Upgrade of a Cluster

Table 4-1 Task Map: Performing a Rolling Upgrade to Oracle Solaris Cluster 4.0 Software

Task
Instructions
1. Read the upgrade requirements and restrictions.
2. If failover zones of brand type solaris are configured in the cluster, upgrade the failover zones.
2. If a quorum server is used, upgrade the Quorum Server software.
3. On one node of the cluster, move resource groups and device groups to another cluster node, and ensure that shared data and system disks are backed up. If the cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure the mediators. Then reboot the node into noncluster mode.
4. Upgrade the Oracle Solaris OS on the cluster node, if necessary, to a supported Oracle Solaris update release.
5. Upgrade the cluster node to Oracle Solaris Cluster 4.0 framework software. Optionally, upgrade data-service software. If necessary, upgrade applications.
6. Repeat Tasks 3 through 4 on each remaining node to upgrade.
7. Use the scversions command to commit the cluster to the upgrade.
8. Verify successful completion of upgrade to Oracle Solaris Cluster 4.0 software.
9. Enable resources and bring resource groups online. Migrate existing resources to new resource types. Upgrade to the Oracle Solaris Cluster Geographic Edition 4.0 software, if used.

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 these steps for each of those clusters.


Perform all steps as superuser 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.0 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 file is /var/scqsd.

  7. Install the Oracle Solaris Cluster 4.0 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 a Cluster Node for a Rolling Upgrade

Perform this procedure on one node at a time. You will take the upgraded node out of the cluster while the remaining nodes continue to function as active cluster members.

Before You Begin

Perform the following tasks:

  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. If necessary, notify users that cluster services might 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. Become superuser on a node of the cluster.
  4. Move all resource groups and device groups that are running on the node to upgrade.
    phys-schost# clnode evacuate node-to-evacuate

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

  5. Move any resource groups that are running in a zone cluster node on the node to upgrade.
    phys-schost# clresourcegroup evacuate -n zone-cluster-node \
    -Z zone-cluster-name resource-group
  6. Verify that the move was completed successfully.
    phys-schost# cluster status -t devicegroup,resourcegroup
  7. Ensure that the system disk, applications, and all data are backed up.
  8. If you will upgrade the Oracle Solaris OS and your cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure your mediators.

    See Configuring Dual-String Mediators in Oracle Solaris Cluster Software Installation Guide for more information.

    1. Run the following command to verify that no mediator data problems exist.
      phys-schost# medstat -s setname
      -s setname

      Specifies the disk set name

      If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Check For and Fix Bad Mediator Data in Oracle Solaris Cluster Software Installation Guide.

    2. List all mediators.

      Save this information for when you restore the mediators during the procedure How to Commit the Upgraded Cluster.

    3. For a disk set that uses mediators, take ownership of the disk set if no node already has ownership.
      phys-schost# cldevicegroup switch -n node devicegr
    4. Unconfigure all mediators for the disk set.
      phys-schost# metaset -s setname -d -m mediator-host-list
      -s setname

      Specifies the disk-set name

      -d

      Deletes from the disk set

      -m mediator-host-list

      Specifies the name of the node to remove as a mediator host for the disk set

      See the mediator(7D) man page for further information about mediator-specific options to the metaset command.

    5. Repeat these steps for each remaining disk set that uses mediators.
  9. Shut down the node that you want to upgrade and boot it into noncluster mode.
    • On SPARC based systems, perform the following commands:
      phys-schost# shutdown -y -g0
      ok boot -x
    • On x86 based systems, perform the following commands:
      1. In the GRUB menu, use the arrow keys to select the appropriate Oracle Solaris entry and type e to edit its commands.

        For more information about GRUB based booting, see Booting and Shutting Down Oracle Solaris on x86 Platforms.

      2. In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
      3. Add -x to the command to specify that the system boot into noncluster mode.
        grub edit> kernel /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS -x
      4. Press Enter to accept the change and return to the boot parameters screen.

        The screen displays the edited command.

      5. Type b to boot the node into noncluster mode.

        Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps to again to add the -x option to the kernel boot parameter command.


    The other nodes of the cluster continue to function as active cluster members.

Next Steps

To upgrade the nodes of an Oracle Solaris Cluster cluster to a new SRU release, go to How to Perform a Rolling Upgrade. To upgrade your Oracle Solaris software, go to How to Perform a Rolling Upgrade of the Solaris OS.


Note - The cluster must already run on, or be upgraded to, at least the minimum required level of the Oracle Solaris OS to support Oracle Solaris Cluster 4.0 software. See Supported Products in Oracle Solaris Cluster 4.0 Release Notes.


How to Perform a Rolling Upgrade of the Solaris OS

Perform this procedure to upgrade the Oracle Solaris OS to a supported SRU release.

Before You Begin

Ensure that all steps in How to Prepare a Cluster Node for a Rolling Upgrade are completed.

  1. Follow the instructions in the Oracle Solaris installation guide to install the SRU.

    Note - Do not reboot the node when prompted to reboot at the end of installation processing.


  2. Install any required Oracle Solaris software updates and hardware-related updates, and download any needed firmware that is contained in the hardware updates.

    Note - Do not reboot the node until Step 3.


  3. Reboot the node into noncluster mode.
    • On SPARC based systems, perform the following commands:
      phys-schost# shutdown -y -g0
      ok boot -x
    • On x86 based systems, perform the following commands:
      1. In the GRUB menu, use the arrow keys to select the appropriate Oracle Solaris entry and type e to edit its commands.

        For more information about GRUB based booting, see Booting and Shutting Down Oracle Solaris on x86 Platforms.

      2. In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.
      3. Add -x to the command to specify that the system boot into noncluster mode.
        grub edit> kernel /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS -x
      4. Press Enter to accept the change and return to the boot parameters screen.

        The screen displays the edited command.

      5. Type b to boot the node into noncluster mode.

        Note - This change to the kernel boot parameter command does not persist over the system boot. The next time you reboot the node, it will boot into cluster mode. To boot into noncluster mode instead, perform these steps to again to add the -x option to the kernel boot parameter command.


Next Steps

Go to How to Perform a Rolling Upgrade.

How to Perform a Rolling Upgrade

Perform this procedure to upgrade an SRU on a node that runs Oracle Solaris Cluster 4.0 software while the remaining cluster nodes are in cluster mode.

If you performed a rolling upgrade and you have failover zones of brand type solaris configured on the cluster, you must perform additional steps. Follow the instructions in How to Upgrade Failover Zones.


Note - Until all nodes of the cluster are upgraded and the upgrade is committed, new features that are introduced by the new release might not be available.


  1. Become superuser or assume a role that provides solaris.cluster.admin RBAC authorization on the node of the cluster you want to upgrade.
  2. Subscribe to the ha-cluster publisher which you want to upgrade.
    # pkg unset-publisher ha-cluster
    # pkg set-publisher -g FMRI for cluster ha-cluster
  3. Run the upgrade on the node you want to upgrade.
    # scinstall - u update [-b bename] 

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

  4. Follow the prompts to boot the node into the new boot environment.

    Perform these stepson each remaining node, one at a time, that you want to upgrade. After you have completed the upgrade, you must perform additional steps to commit the upgrade. See Chapter 5, Completing the Upgrade.

Next Steps

When all nodes in the cluster are upgraded, go to Chapter 5, Completing the Upgrade.