Oracle® Solaris Cluster Upgrade Guide

Exit Print View

Updated: July 2014, E39644–01

How to Upgrade the Software (Dual-Partition)

Perform this procedure to upgrade each node of the cluster to Oracle Solaris Cluster 4.2 software and, if necessary, upgrade the Oracle Solaris software.

Note -  If you intend to upgrade failover zones, do not use the dual-partition upgrade method. Instead, use the standard upgrade or rolling upgrade method.

Perform all steps from the global zone only.

Before You Begin

Perform the following tasks:

Tip  - You can use the pconsole utility to perform this procedure on multiple nodes simultaneously. See the pconsole(1) man page that is installed with the terminal/pconsole package for more information.
  1. Assume the root role on a node that is a member of the partition that is in noncluster mode.
  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   P  LOCATION
    solaris                             origin   online   F  solaris-repository

    For information about setting the solaris publisher, see Adding, Modifying, or Removing Package Publishers in Adding and Updating Software in Oracle Solaris 11.2 .

  4. Start the scinstall utility.
    phys-schost# /usr/cluster/bin/scinstall

    The scinstall Main Menu is displayed.

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

    The Upgrade Menu is displayed.

  6. Follow the menu prompts to upgrade the cluster framework.

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

  7. Quit the scinstall utility.
  8. If you have HA for NFS configured on a highly available local file system, ensure that the loopback file system (LOFS) is disabled.

    Note -  If you have non-global zones configured, LOFS must remain enabled. For guidelines about using LOFS and alternatives to disabling it, see Planning Cluster File Systems in Oracle Solaris Cluster Software Installation Guide .

    To disable LOFS, ensure that the /etc/system file contains the following entry:


    This change becomes effective at the next system reboot.

  9. As needed, manually upgrade any custom data services that are not supplied on the product media.
  10. Verify that each data-service update is installed successfully.

    View the upgrade log file that is referenced at the end of the upgrade output messages.

  11. Install any Oracle Solaris Cluster 4.2 framework and data-service software updates.

    For instructions on updating your software, see Chapter 11, Updating Your Software, in Oracle Solaris Cluster System Administration Guide .

  12. Upgrade software applications that are installed on the cluster.

    Ensure that application levels are compatible with the current versions of Oracle Solaris Cluster and Oracle Solaris software. See your application documentation for installation instructions.

    Note -  If any upgrade procedure instructs you to perform a reboot, you must add the –x option to the boot command. This option boots the cluster into noncluster mode.
  13. Repeat all steps in this procedure up to this point on all remaining nodes that you need to upgrade in the partition.
  14. After all nodes in a partition are upgraded, apply the upgrade changes.
    1. From one node in the partition that you are upgrading, start the interactive scinstall utility.
      phys-schost# /usr/cluster/bin/scinstall

      The scinstall Main Menu is displayed.

    2. Type option number for Apply Dual-Partition Upgrade Changes to the Partition.
    3. Follow the prompts to continue each stage of the upgrade processing.

      The command performs the following tasks, depending on which partition the command is run from:

      • First partition - The command halts each node in the second partition, one node at a time. When a node in the second partition is halted, any services on that node are automatically switched over to a node in the first partition, provided that the node list of the related resource group contains a node in the first partition. After all nodes in the second partition are halted, the nodes in the first partition are booted into cluster mode and take over providing cluster services.


        Caution  -  Do not reboot any node of the first partition again until after the upgrade is completed on all nodes. If you again reboot a node of the first partition before the second partition is upgraded and rebooted into the cluster, the upgrade might fail in an unrecoverable state.

      • Second partition - The command boots the nodes in the second partition into cluster mode, to join the active cluster that was formed by the first partition. After all nodes have rejoined the cluster, the command performs final processing and reports on the status of the upgrade.

    4. Exit the scinstall utility, if it is still running.
  15. If you are finishing upgrade of the first partition, perform the following substeps to prepare the second partition for upgrade.

    Otherwise, if you are finishing upgrade of the second partition, proceed to Step 16.

    1. Boot each node in the second partition into noncluster mode.
      • SPARC:
        ok boot -x
      • x86:
        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 a System in Booting and Shutting Down Oracle Solaris 11.2 Systems .

        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 multiboot command to specify that the system boot into noncluster mode.
        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 add the –x option to the kernel boot parameter command.
    2. Upgrade the nodes in the second partition.

      Return to Step 1.

  16. If you changed the RG_system property of any resource groups to FALSE, change the settings back to TRUE.
    phys-schost# clresourcegroup set -p RG_system=TRUE resourcegroup

Next Steps

Go to Chapter 6, Completing the Upgrade.


If you experience an unrecoverable error during dual-partition upgrade, perform recovery procedures in How to Recover from a Failed Dual-Partition Upgrade.