Sun Cluster Upgrade Guide for Solaris OS

Chapter 5 Performing a Rolling Upgrade

This chapter provides procedures to perform a rolling upgrade from Sun Cluster 3.2 software to Sun Cluster 3.2 2/08 software. In a rolling upgrade, you upgrade one cluster node at a time, while the other cluster nodes remain in production. After all nodes are upgraded and have rejoined the cluster, you must commit the cluster to the new software version before you can use any new features.

This chapter provides the following information to upgrade from Sun Cluster 3.2 2/08 software to Sun Cluster 3.2 software by using the live upgrade method:

Performing a Rolling Upgrade of a Cluster

To upgrade from Sun Cluster 3.0 software, follow instead the procedures in Chapter 2, Performing a Standard Upgrade to Sun Cluster 3.2 2/08 Software.

Note –

Sun Cluster 3.2 2/08 software does not support rolling upgrade from Solaris 8 software to Solaris 9 or 10 software or from Solaris 9 software to Solaris 10 software. You can only upgrade Solaris software to an update of the same release during Sun Cluster rolling upgrade. To upgrade a Sun Cluster configuration from Solaris 8 software to Solaris 9 or 10 software or from Solaris 9 software to Solaris 10 software or compatible, perform instead the procedures in another upgrade method. See Choosing a Sun Cluster Upgrade Method to determine the best upgrade method for your configuration.

Table 5–1 Task Map: Performing a Rolling Upgrade to Sun Cluster 3.2 2/08 Software


Task	Instructions
1. Read the upgrade requirements and restrictions.	Upgrade Requirements and Software Support Guidelines
2. 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 Sun Cluster Geographic Edition software is installed, uninstall it. If the cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure the mediators. Then reboot the node into noncluster mode.	How to Prepare a Cluster Node for a Rolling Upgrade
3. Upgrade the Solaris OS on the cluster node, if necessary, to a supported Solaris update release.	How to Perform a Rolling Upgrade of a Solaris Maintenance Update
4. Upgrade the cluster node to Sun Cluster 3.2 2/08 framework software. Optionally, upgrade data-service software. If necessary, upgrade applications.	How to Perform a Rolling Upgrade of Sun Cluster 3.2 2/08 Software
5. Repeat Tasks 3 through 4 on each remaining node to upgrade.
6. Use the `scversions` command to commit the cluster to the upgrade.	How to Commit the Upgraded Cluster to Sun Cluster 3.2 2/08 Software
7. Verify successful completion of upgrade to Sun Cluster 3.2 2/08 software.	How to Verify Upgrade of Sun Cluster 3.2 2/08 Software
8. Enable resources and bring resource groups online. Migrate existing resources to new resource types.	How to Finish Upgrade to Sun Cluster 3.2 2/08 Software
9. (Optional) SPARC: Upgrade the Sun Cluster module to Sun Management Center.	SPARC: How to Upgrade Sun Cluster Module Software for Sun Management Center

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:

Ensure that the configuration meets requirements for upgrade. See Upgrade Requirements and Software Support Guidelines.
Have available the installation media, documentation, and patches for all the software products that you are upgrading, including the following software:
- Solaris OS
- Sun Cluster 3.2 2/08 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
- Sun Cluster 3.2 2/08 data services (agents)
- Applications that are managed by Sun Cluster 3.2 2/08 data-service agents
See Patches and Required Firmware Levels in Sun Cluster 3.2 2/08 Release Notes for Solaris OS for the location of patches and installation instructions.

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.

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.

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.

Become superuser on a node of the cluster.

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.

Verify that the move was completed successfully.

phys-schost# cluster status -t devicegroup,resourcegroup

Ensure that the system disk, applications, and all data are backed up.

If you will upgrade the Solaris OS and your cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure your mediators.

See Configuring Dual-String Mediators in Sun Cluster Software Installation Guide for Solaris OS 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 Fix Bad Mediator Data in Sun Cluster Software Installation Guide for Solaris OS.
2. List all mediators.
  
  Save this information for when you restore the mediators during the procedure How to Commit the Upgraded Cluster to Sun Cluster 3.2 2/08 Software.
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.

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:

In the GRUB menu, use the arrow keys to select the appropriate Solaris entry and type e to edit its commands.

The GRUB menu appears similar to the following:

GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-------------------------------------------------------------------------+
| Solaris 10 /sol_10_x86                                                  |
| Solaris failsafe                                                        |
|                                                                         |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

For more information about GRUB based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.

In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.

The GRUB boot parameters screen appears similar to the following:

GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+----------------------------------------------------------------------+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot                                     |
| module /platform/i86pc/boot_archive                                  |
+----------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press 'b' to boot, 'e' to edit the selected command in the
boot sequence, 'c' for a command-line, 'o' to open a new line
after ('O' for before) the selected line, 'd' to remove the
selected line, or escape to go back to the main menu.

Add -x to the command to specify that the system boot into noncluster mode.

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ESC at any time exits. ]

grub edit> kernel /platform/i86pc/multiboot -x

Press Enter to accept the change and return to the boot parameters screen.

The screen displays the edited command.

GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+----------------------------------------------------------------------+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot -x                                  |
| module /platform/i86pc/boot_archive                                  |
+----------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press 'b' to boot, 'e' to edit the selected command in the
boot sequence, 'c' for a command-line, 'o' to open a new line
after ('O' for before) the selected line, 'd' to remove the
selected line, or escape to go back to the main menu.-

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 Solaris software to a Maintenance Update release, go to How to Perform a Rolling Upgrade of a Solaris Maintenance Update.

Note –

The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris OS to support Sun Cluster 3.2 2/08 software. See the Sun Cluster 3.2 2/08 Release Notes for Solaris OS for information about supported releases of the Solaris OS.

If you do not intend to upgrade the Solaris OS, go to How to Perform a Rolling Upgrade of Sun Cluster 3.2 2/08 Software.

How to Perform a Rolling Upgrade of a Solaris Maintenance Update

Perform this procedure to upgrade the Solaris OS to a supported Maintenance Update release.

Note –

You cannot perform a rolling upgrade to upgrade a cluster from Solaris 8 to Solaris 9 or 10 software or from Solaris 9 to Solaris 10 software. Go to Choosing a Sun Cluster Upgrade Method to identify the appropriate upgrade method to use.

Before You Begin

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

Temporarily comment out all entries for globally mounted file systems in the node's /etc/vfstab file.

Perform this step to prevent the Solaris upgrade from attempting to mount the global devices.

Follow the instructions in the Solaris maintenance update installation guide to install the Maintenance Update release.

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

Uncomment all entries in the /a/etc/vfstab file for globally mounted file systems that you commented out in Step 1.

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

Note –
Do not reboot the node until Step 5.

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:

In the GRUB menu, use the arrow keys to select the appropriate Solaris entry and type e to edit its commands.

The GRUB menu appears similar to the following:

GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-------------------------------------------------------------------------+
| Solaris 10 /sol_10_x86                                                  |
| Solaris failsafe                                                        |
|                                                                         |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

For more information about GRUB based booting, see Booting an x86 Based System by Using GRUB (Task Map) in System Administration Guide: Basic Administration.

In the boot parameters screen, use the arrow keys to select the kernel entry and type e to edit the entry.

The GRUB boot parameters screen appears similar to the following:

GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+----------------------------------------------------------------------+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot                                     |
| module /platform/i86pc/boot_archive                                  |
+----------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press 'b' to boot, 'e' to edit the selected command in the
boot sequence, 'c' for a command-line, 'o' to open a new line
after ('O' for before) the selected line, 'd' to remove the
selected line, or escape to go back to the main menu.

Add -x to the command to specify that the system boot into noncluster mode.

[ Minimal BASH-like line editing is supported. For the first word, TAB
lists possible command completions. Anywhere else TAB lists the possible
completions of a device/filename. ESC at any time exits. ]

grub edit> kernel /platform/i86pc/multiboot -x

Press Enter to accept the change and return to the boot parameters screen.

The screen displays the edited command.

GNU GRUB version 0.95 (615K lower / 2095552K upper memory)
+----------------------------------------------------------------------+
| root (hd0,0,a)                                                       |
| kernel /platform/i86pc/multiboot -x                                  |
| module /platform/i86pc/boot_archive                                  |
+----------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press 'b' to boot, 'e' to edit the selected command in the
boot sequence, 'c' for a command-line, 'o' to open a new line
after ('O' for before) the selected line, 'd' to remove the
selected line, or escape to go back to the main menu.-

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

Upgrade Sun Cluster software. Go to How to Perform a Rolling Upgrade of Sun Cluster 3.2 2/08 Software.

How to Perform a Rolling Upgrade of Sun Cluster 3.2 2/08 Software

Perform this procedure to upgrade a node that runs Sun Cluster 3.2 software to Sun Cluster 3.2 2/08 software while the remaining cluster nodes are in cluster mode.

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.

Become superuser on the node of the cluster.

Ensure that the applicable Sun Cluster 3.2 Core Patch is installed before you begin to upgrade to Sun Cluster software.
- Solaris 9 OS - 125510–02
- Solaris 10 OS on SPARC - 125511–02
- Solaris 10 OS on x86 - 125512–02
This patch contains the versioning functionality that is needed to support coexistence of different Sun Cluster software versions during the rolling upgrade process.

Load the Sun Java Availability Suite DVD-ROM into the DVD-ROM drive.

If the volume management daemon vold(1M) is running and is configured to manage CD-ROM or DVD devices, the daemon automatically mounts the media on the /cdrom/cdrom0/ directory.

Change to the installation wizard directory of the DVD-ROM.
- If you are installing the software packages on the SPARC platform, type the following command:
  phys-schost# cd /cdrom/cdrom0//Solaris_sparc
- If you are installing the software packages on the x86 platform, type the following command:
  phys-schost# cd /cdrom/cdrom0//Solaris_x86

Start the installation wizard program.
phys-schost# ./installer

Follow the instructions on the screen to select and upgrade Shared Components software packages on the node.

Note –
Do not use the installation wizard program to upgrade Sun Cluster software packages.

The installation wizard program displays the status of the installation. When the installation is complete, the program displays an installation summary and the installation logs.

Exit the installation wizard program.

Change to the /cdrom/suncluster_3_0Tools/ directory, where arch is sparc or x86 (Solaris 10 only) and where ver is 9 for Solaris 9 or 10 for Solaris 10 .
phys-schost# cd /cdrom/cdrom0//cdrom/suncluster_3_0Tools

Start the scinstall utility.
phys-schost# ./scinstall
Note –
Do not use the /usr/cluster/bin/scinstall command that is already installed on the node. You must use the scinstall command that is located on the Sun Java Availability Suite DVD-ROM.

The scinstall Main Menu is displayed.

Type the option number for Upgrade This Cluster Node and press the Return key.

  *** Main Menu ***

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

        1) Create a new cluster or add a cluster node
        2) Configure a cluster to be JumpStarted from this install server
      * 3) Manage a dual-partition upgrade
      * 4) Upgrade this cluster node
      * 5) Print release information for this cluster node
 
      * ?) Help with menu options
      * q) Quit

    Option:  4

The Upgrade Menu is displayed.

Type the option number for Upgrade Sun Cluster Framework On This Cluster Node and press the Return key.

Follow the menu prompts to upgrade the cluster framework.

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

Quit the scinstall utility.

(Optional) Upgrade data service packages.

Note –
For Sun Cluster HA for SAP Web Application Server, if you are using a J2EE engine resource or a web application server component resource or both, you must delete the resource and recreate it with the new web application server component resource. Changes in the new web application server component resource includes integration of the J2EE functionality. For more information, see Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS.
1. Start the upgraded interactive scinstall utility.
  phys-schost# /usr/cluster/bin/scinstall
  Note –
  Do not use the scinstall utility that is on the installation media to upgrade data service packages.
  
  The scinstall Main Menu is displayed.
2. Type the option number for Upgrade This Cluster Node and press the Return key.
  
  The Upgrade Menu is displayed.
3. Type the option number for Upgrade Sun Cluster Data Service Agents On This Node and press the Return key.
4. Follow the menu prompts to upgrade Sun Cluster data service agents that are installed on the node.
  
  You can choose from the list of data services that are available to upgrade or choose to upgrade all installed data services.
  
  Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and prompts you to press Enter to continue.
5. Press Enter.
  
  The Upgrade Menu is displayed.

Quit the scinstall utility.

Unload the Sun Java Availability Suite DVD-ROM from the DVD-ROM drive.
1. To ensure that the DVD-ROM is not being used, change to a directory that does not reside on the DVD-ROM.
2. Eject the DVD-ROM.
  phys-schost# eject cdrom

If you have Sun Cluster 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 Cluster File Systems in Sun Cluster Software Installation Guide for Solaris OS.

As of the Sun Cluster 3.2 release, LOFS is no longer disabled by default during Sun Cluster software installation or upgrade. To disable LOFS, ensure that the /etc/system file contains the following entry:
exclude:lofs
This change becomes effective at the next system reboot.

As needed, manually upgrade any custom data services that are not supplied on the product media.

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.

Install any Sun Cluster 3.2 2/08 framework and software patches.

See Patches and Required Firmware Levels in Sun Cluster 3.2 2/08 Release Notes for Solaris OS for the location of patches and installation instructions.

Upgrade software applications that are installed on the cluster.

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

Shut down the node.
phys-schost# shutdown -g0 -y

Reboot the node into the cluster.

On SPARC based systems, perform the following command:
ok boot

On x86 based systems, perform the following commands:

When the GRUB menu is displayed, select the appropriate Solaris entry and press Enter. The GRUB menu appears similar to the following:

GNU GRUB version 0.95 (631K lower / 2095488K upper memory)
+-------------------------------------------------------------------------+
| Solaris 10 /sol_10_x86                                                  |
| Solaris failsafe                                                        |
|                                                                         |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.

Return to How to Prepare a Cluster Node for a Rolling Upgrade and repeat all upgrade procedures on the next node to upgrade.

Repeat this process until all nodes in the cluster are upgraded.

Example 5–1 Rolling Upgrade From Sun Cluster 3.2 to Sun Cluster 3.2 2/08 Software

The following example shows the process of a rolling upgrade of a cluster node from Sun Cluster 3.2 to Sun Cluster 3.2 2/08 software on a SPARC based system that runs the Solaris 9 OS. The example includes the upgrade of all installed data services that have new versions in the Sun Cluster 3.2 2/08 release. The cluster node name is phys-schost-1.

(Upgrade framework software)
phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_9/Tools/
phys-schost-1# ./scinstall
(Follow menu prompts to upgrade Sun Cluster framework on this node)
 
(Upgrade data services)
phys-schost-1# scinstall
(Follow menu prompts to upgrade Sun Cluster data services on this node)

(Reboot the node into the cluster)
phys-schost-1# shutdown -g0 -y
ok> boot

Next Steps

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