How to Upgrade Sun Cluster 3.2 Software (Standard) (Sun Cluster Software Installation Guide for Solaris OS)

Sun Cluster Software Installation Guide for Solaris OS

How to Upgrade Sun Cluster 3.2 Software (Standard)

Perform this procedure to upgrade each node of the cluster to Sun Cluster 3.2 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 8 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 at the same time.

Before You Begin

Perform the following tasks:

Ensure that all steps in How to Prepare the Cluster for Upgrade (Standard) are completed.
If you upgraded to a new marketing release of the Solaris OS, such as from Solaris 8 to Solaris 10 software, ensure that all steps in How to Upgrade the Solaris OS and Volume Manager Software (Standard) are completed.
Ensure that you have installed all required Solaris software patches and hardware-related patches.

Become superuser on a node of the cluster.

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 number that corresponds to the option 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 number that corresponds to the option 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.

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

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 number that corresponds to the option for Upgrade this cluster node and press the Return key.
  
  The Upgrade Menu is displayed.
3. Type the number that corresponds to the option 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.

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.

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

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

(Optional) Reconfigure the private-network address range.

Perform this step if you want to increase or decrease the size of the IP address range that is used by the private interconnect. The IP address range that you configure must minimally support the number of nodes and private networks in the cluster. See Private Network for more information.
1. From one node, start the clsetup utility.
  
  When run in noncluster mode, the clsetup utility displays the Main Menu for noncluster-mode operations.
2. Type the number that corresponds to the option for Change IP Address Range and press the Return key.
  
  The clsetup utility displays the current private-network configuration, then asks if you would like to change this configuration.
3. To change either the private-network IP address or the IP address range, type yes and press the Return key.
  
  The clsetup utility displays the default private-network IP address, 172.16.0.0, and asks if it is okay to accept this default.
4. Change or accept the private-network IP address.
  - To accept the default private-network IP address and proceed to changing the IP address range, type yes and press the Return key.
    
    The clsetup utility will ask if it is okay to accept the default netmask. Skip to the next step to enter your response.
  - To change the default private-network IP address, perform the following substeps.
    1. Type no in response to the clsetup utility question about whether it is okay to accept the default address, then press the Return key.
      
      The clsetup utility will prompt for the new private-network IP address.
    2. Type the new IP address and press the Return key.
      
      The clsetup utility displays the default netmask and then asks if it is okay to accept the default netmask.
5. Change or accept the default private-network IP address range.
  
  The default netmask is 255.255.248.0. This default IP address range supports up to 64 nodes and up to 10 private networks in the cluster.
  - To accept the default IP address range, type yes and press the Return key.
    
    Then skip to the next step.
  - To change the IP address range, perform the following substeps.
    1. Type no in response to the clsetup utility's question about whether it is okay to accept the default address range, then press the Return key.
      
      When you decline the default netmask, the clsetup utility prompts you for the number of nodes and private networks that you expect to configure in the cluster.
    2. Enter the number of nodes and private networks that you expect to configure in the cluster.
      
      From these numbers, the clsetup utility calculates two proposed netmasks:
      - The first netmask is the minimum netmask to support the number of nodes and private networks that you specified.
      - The second netmask supports twice the number of nodes and private networks that you specified, to accommodate possible future growth.
    3. Specify either of the calculated netmasks, or specify a different netmask that supports the expected number of nodes and private networks.
6. Type yes in response to the clsetup utility's question about proceeding with the update.
7. When finished, exit the clsetup utility.

After all nodes in the cluster are upgraded, reboot the upgraded nodes.

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

Boot each node into cluster mode.

On SPARC based systems, do the following:
ok boot

On x86 based systems, do the following:

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.

For more information about GRUB based booting, see Chapter 11, GRUB Based Booting (Tasks), in System Administration Guide: Basic Administration.

Next Steps

Go to How to Verify Upgrade of Sun Cluster 3.2 Software