How to Upgrade Sun Cluster 3.2 1/09 Software (Dual-Partition) (Sun Cluster Upgrade Guide for Solaris OS)

Sun Cluster Upgrade Guide for Solaris OS

Previous: How to Upgrade the Solaris OS and Volume Manager Software (Dual-Partition)
Next: Chapter 4 Performing a Live Upgrade to Sun Cluster 3.2 1/09 Software

How to Upgrade Sun Cluster 3.2 1/09 Software (Dual-Partition)

Perform this procedure to upgrade each node of the cluster to Sun Cluster 3.2 1/09 software. This procedure also upgrades required Sun Java Enterprise System shared components. You must also perform this procedure after you upgrade to a different marketing release of the Solaris OS, such as from Solaris 9 to Solaris 10 software.

On the Solaris 10 OS, perform all steps from the global zone only.

Tip –

You can perform this procedure on more than one node of the partition at the same time.

Before You Begin

Perform the following tasks:

Ensure that all steps in How to Prepare the Cluster for Upgrade (Dual-Partition) are completed.
Ensure that the node you are upgrading belongs to the partition that is not active in the cluster and that the node is in noncluster mode.
If you upgraded to a new marketing release of the Solaris OS, such as from Solaris 9 to Solaris 10 software, ensure that all steps in How to Upgrade the Solaris OS and Volume Manager Software (Dual-Partition) are completed.
Ensure that you have installed all required Solaris software patches and hardware-related patches.

Become superuser on a node that is a member of the partition that is in noncluster mode.

Ensure that the /usr/java/ directory is a symbolic link to the minimum or latest version of Java software.

Sun Cluster software requires at least version 1.5.0_06 of Java software. If you upgraded to a version of Solaris that installs an earlier version of Java, the upgrade might have changed the symbolic link to point to a version of Java that does not meet the minimum requirement for Sun Cluster 3.2 software.
1. Determine what directory the /usr/java/ directory is symbolically linked to.
  phys-schost# ls -l /usr/java lrwxrwxrwx 1 root other 9 Apr 19 14:05 /usr/java -> /usr/j2se/
2. Determine what version or versions of Java software are installed.
  
  The following are examples of commands that you can use to display the version of their related releases of Java software.
  phys-schost# /usr/j2se/bin/java -version phys-schost# /usr/java1.2/bin/java -version phys-schost# /usr/jdk/jdk1.5.0_06/bin/java -version
3. If the /usr/java/ directory is not symbolically linked to a supported version of Java software, recreate the symbolic link to link to a supported version of Java software.
  
  The following example shows the creation of a symbolic link to the /usr/j2se/ directory, which contains Java 1.5.0_06 software.
  phys-schost# rm /usr/java phys-schost# ln -s /usr/j2se /usr/java

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 /Solaris_arch/Product/sun_cluster/Solaris_ver/Tools/ 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/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools

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.

During the Sun Cluster upgrade, scinstall might make one or more of the following configuration changes:
- Convert NAFO groups to IPMP groups but keep the original NAFO-group name.
  
  See one of the following manuals for information about test addresses for IPMP:
  - Configuring Test Addresses in Administering Multipathing Groups With Multiple Physical Interfaces in System Administration Guide: IP Services (Solaris 9)
  - Test Addresses in System Administration Guide: IP Services (Solaris 10)
  See the scinstall(1M) man page for more information about the conversion of NAFO groups to IPMP during Sun Cluster software upgrade.
- Rename the ntp.conf file to ntp.conf.cluster, if ntp.conf.cluster does not already exist on the node.
- Set the local-mac-address? variable to true, if the variable is not already set to that value.
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.

Upgrade data service packages.

You must upgrade all data services to the Sun Cluster 3.2 version.

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 1/09 framework and data-service software patches.

See Patches and Required Firmware Levels in the Sun Cluster Release Notes 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.

Repeat all steps in this procedure up to this point on all remaining nodes that you need to upgrade in the partition.

After all nodes in a partition are upgraded, apply the upgrade changes.

From one node in the partition that you are upgrading, start the interactive scinstall utility.
phys-schost# /usr/cluster/bin/scinstall
Note –
Do not use the scinstall command that is located on the installation media. Only use the scinstall command that is located on the cluster node.

The scinstall Main Menu is displayed.

Type option number for Apply Dual-Partition Upgrade Changes to the Partition and press the Return key.

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 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.
- 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.

Exit the scinstall utility, if it is still running.

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 How to Verify Upgrade of Sun Cluster 3.2 1/09 Software.

Boot each node in the second partition into noncluster mode.

On SPARC based systems, perform the following command:
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.

Upgrade the nodes in the second partition.

To upgrade Solaris software before you perform Sun Cluster software upgrade, go to How to Upgrade the Solaris OS and Volume Manager Software (Dual-Partition).

Otherwise, upgrade Sun Cluster software on the second partition. Return to Step 1.

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.

Troubleshooting

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