Sun Cluster Upgrade Guide for Solaris OS

Performing a Standard Upgrade of a Cluster

The following table lists the tasks to perform to upgrade from Sun Cluster 3.1 8/05 or 3.2 software to Sun Cluster 3.2 11/09 software. You also perform these tasks to upgrade only the version of the Solaris OS. If you upgrade the Solaris OS to a new marketing release, such as from Solaris 9 to Solaris 10 software, you must also upgrade the Sun Cluster software and dependency software to the version that is compatible with the new version of the Solaris OS.

Table 2–1 Task Map: Performing a Standard Upgrade to Sun Cluster 3.2 11/09 Software


Task	Instructions
1. Read the upgrade requirements and restrictions. Determine the proper upgrade method for your configuration and needs.	Upgrade Requirements and Software Support Guidelines Choosing a Sun Cluster Upgrade Method
2. If a quorum server is used, upgrade the Quorum Server software.	How to Upgrade Quorum Server Software
3. Remove the cluster from production and back up shared data. If Sun Cluster Geographic Edition software is installed, uninstall it.	How to Prepare the Cluster for Upgrade (Standard)
4. Upgrade the Solaris software, if necessary, to a supported Solaris update. If the cluster uses dual-string mediators for Solaris Volume Manager software, unconfigure the mediators. As needed, upgrade Veritas Volume Manager (VxVM) and Veritas File System (VxFS). Solaris Volume Manager software is automatically upgraded with the Solaris OS.	How to Upgrade the Solaris OS and Volume Manager Software (Standard)
5. Upgrade to Sun Cluster 3.2 11/09 framework and data-service software. If necessary, upgrade applications. If the cluster uses dual-string mediators and you upgraded the Solaris OS, reconfigure the mediators. If you upgraded VxVM, upgrade disk groups.	How to Upgrade Sun Cluster 3.2 11/09 Software (Standard)
6. Use the `scversions` command to commit the cluster to the upgrade.	How to Commit the Upgraded Cluster to Sun Cluster 3.2 11/09 Software
7. Verify successful completion of upgrade to Sun Cluster 3.2 11/09 software.	How to Verify Upgrade of Sun Cluster 3.2 11/09 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 11/09 Software
9. (Optional) SPARC: Upgrade the Sun Cluster module for Sun Management Center, if needed.	SPARC: How to Upgrade Sun Cluster Module Software for Sun Management Center

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 on each cluster the steps to remove the quorum server and later the steps to add back the quorum server.

Perform all steps as superuser on the cluster and on the quorum server.

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 Sun Cluster System Administration Guide for Solaris OS.

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 3.2 11/09 version of Quorum Server software.

Unconfigure the quorum server from each cluster that uses the quorum server.
phys-schost# clquorum remove quorumserver

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 Sun Cluster System Administration Guide for Solaris OS.

From the quorum server to upgrade, halt all quorum server instances.
quorumserver# clquorumserver stop +

Uninstall the Quorum Server software from the quorum server to upgrade.
1. Navigate to the directory where the uninstaller is located.
  quorumserver# cd /var/sadm/prod/SUNWentsysver
  ver
  
  The version of Java Enterprise System that is installed on your system.
2. Start the uninstallation wizard.
  quorumserver# ./uninstall
3. Follow instructions on the screen to uninstall the Quorum Server software from the quorum-server host computer.
  
  After removal is finished, you can view any available log. See Chapter 8, Uninstalling, in Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX for additional information about using the uninstall program.
4. (Optional) Clean up or remove the quorum server directories.
  
  By default, this directory is /var/scqsd.

Install the Sun Cluster 3.2 11/09 Quorum Server software, reconfigure the quorum server, and start the quorum server daemon.

Follow the steps in How to Install and Configure Quorum Server Software in Sun Cluster Software Installation Guide for Solaris OS for installing the Quorum Server software.

From a cluster node, configure the upgraded quorum server as a quorum device.

Follow the steps in How to Configure Quorum Devices in Sun Cluster Software Installation Guide for Solaris OS.

If you configured a temporary quorum device, unconfigure it.
phys-schost# clquorum remove tempquorum

How to Prepare the Cluster for Upgrade (Standard)

Perform this procedure to remove the cluster from production before you perform a standard upgrade. Perform all steps from the global zone only.

Before You Begin

Perform the following tasks:

Ensure that the configuration meets the requirements for upgrade. See Upgrade Requirements and Software Support Guidelines.
Have available the installation media, documentation, and patches for all software products that you are upgrading, including the following software:
- Solaris OS
- Sun Cluster 3.2 11/09 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
- Solaris 10 OS p7zip patch
  - On SPARC – 137321–01 (minimum)
  - On x86 – 137322–01 (minimum)
- Sun Cluster 3.2 11/09 data services (agents)
- Applications that are managed by Sun Cluster 3.2 11/09 data-services
- Veritas Volume Manager, if applicable
See Patches and Required Firmware Levels in the Sun Cluster Release Notes for the location of patches and installation instructions.
If you use role-based access control (RBAC) instead of superuser to access the cluster nodes, ensure that you can assume an RBAC role that provides authorization for all Sun Cluster commands. This series of upgrade procedures requires the following Sun Cluster RBAC authorizations if the user is not superuser:
- solaris.cluster.modify
- solaris.cluster.admin
- solaris.cluster.read
See Role-Based Access Control (Overview) in System Administration Guide: Security Services for more information about using RBAC roles. See the Sun Cluster man pages for the RBAC authorization that each Sun Cluster subcommand requires.

Ensure that the cluster is functioning normally.
1. View the current status of the cluster by running the following command from any node.
  - On Sun Cluster 3.1 8/05 software, use the following command:
    phys-schost% scstat
  - On Sun Cluster 3.2 software, use the following command:
    phys-schost% cluster status
  See the scstat(1M) or 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.

Notify users that cluster services will be unavailable during the upgrade.

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.

Take each resource group offline and disable all resources.

Take offline all resource groups in the cluster, including those that are in non-global zones. Then disable all resources, to prevent the cluster from bringing the resources online automatically if a node is mistakenly rebooted into cluster mode.

If you are upgrading from Sun Cluster 3.1 8/05 or 3.2 software and want to use the scsetup or clsetup utility, perform the following steps:
1. Start the utility.
  - On Sun Cluster 3.1 8/05 software, use the following command:
    phys-schost# scsetup
  - On Sun Cluster 3.2 software, use the following command:
    phys-schost# clsetup
  The Main Menu is displayed.
2. Type the option number for Resource Groups and press the Return key.
  
  The Resource Group Menu is displayed.
3. Type the option number for Online/Offline or Switchover a Resource Group and press the Return key.
4. Follow the prompts to take offline all resource groups and to put them in the unmanaged state.
5. When all resource groups are offline, type q to return to the Resource Group Menu.
6. Exit the scsetup utility.
  
  Type q to back out of each submenu or press Ctrl-C.

To use the command line, perform the following steps:

Take each resource offline.
- On Sun Cluster 3.1 8/05 software, use the following command:
  phys-schost# scswitch -F -g resource-group
  -F
  
  Switches a resource group offline.
  
  -g resource-group
  
  Specifies the name of the resource group to take offline.
- On Sun Cluster 3.2 software, use the following command:
  phys-schost# clresource offline resource-group

From any node, list all enabled resources in the cluster.

On Sun Cluster 3.1 8/05 software, use the following command:

phys-schost# scrgadm -pv | grep "Res enabled"
(resource-group:resource) Res enabled: True

On Sun Cluster 3.2 software, use the following command:

phys-schost# clresource show -p Enabled
=== Resources ===

Resource:                                       resource
  Enabled{nodename1}:                               True
  Enabled{nodename2}:                               True
…

Identify those resources that depend on other resources.

phys-schost# clresource show -p resource_dependencies
=== Resources ===

Resource:                                       node
  Resource_dependencies:                           node
…

You must disable dependent resources first before you disable the resources that they depend on.

Disable each enabled resource in the cluster.
- On Sun Cluster 3.1 8/05 software, use the following command:
  phys-schost# scswitch -n -j resource
  -n
  
  Disables.
  
  -j resource
  
  Specifies the resource.
- On Sun Cluster 3.2 software, use the following command:
  phys-schost# clresource disable resource
See the scswitch(1M) or clresource(1CL) man page for more information.

Verify that all resources are disabled.

On Sun Cluster 3.1 8/05 software, use the following command:

phys-schost# scrgadm -pv | grep "Res enabled"
(resource-group:resource) Res enabled: False

On Sun Cluster 3.2 software, use the following command:

phys-schost# clresource show -p Enabled
=== Resources ===

Resource:                                       resource
  Enabled{nodename1}:                               False
  Enabled{nodename2}:                               False
…

Move each resource group to the unmanaged state.
- On Sun Cluster 3.1 8/05 software, use the following command:
  phys-schost# scswitch -u -g resource-group
  -u
  
  Moves the specified resource group to the unmanaged state.
  
  -g resource-group
  
  Specifies the name of the resource group to move into the unmanaged state.
- On Sun Cluster 3.2 software, use the following command:
  phys-schost# clresourcegroup unmanage resource-group

Verify that all resources on all nodes are Offline and that all resource groups are in the Unmanaged state.
- On Sun Cluster 3.1 8/05 software, use the following command:
  phys-schost# scstat -g
- On Sun Cluster 3.2 software, use the following command:
  phys-schost# cluster status -t resource,resourcegroup

Stop all applications that are running on each node of the cluster.

Ensure that all shared data is 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 about mediators.
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 Finish Upgrade to Sun Cluster 3.2 11/09 Software.
3. For a disk set that uses mediators, take ownership of the disk set if no node already has ownership.
  - On Sun Cluster 3.1 8/05 software, use the following command:
    phys-schost# scswitch -z -D setname -h node
    -z
    
    Changes mastery.
    
    -D devicegroup
    
    Specifies the name of the disk set.
    
    -h node
    
    Specifies the name of the node to become primary of the disk set.
  - On Sun Cluster 3.2 software, use the following command:
    phys-schost# cldevicegroup switch -n node devicegroup
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 Step c through Step d for each remaining disk set that uses mediators.

From one node, shut down the cluster.
- On Sun Cluster 3.1 8/05 software, use the following command:
  phys-schost# scshutdown -g0 -y
- On Sun Cluster 3.2 software, use the following command:
  phys-schost# cluster shutdown -g0 -y
See the scshutdown(1M)man page for more information.

Boot each node 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.97 (639K lower / 1047488K 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.97 (639K lower / 1047488K 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.97 (639K lower / 1047488K 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 add the -x option to the kernel boot parameter command.

Ensure that each system disk is backed up.

Next Steps

Upgrade software on each node.

To upgrade Solaris software before you perform Sun Cluster software upgrade, go to How to Upgrade the Solaris OS and Volume Manager Software (Standard).
- You must upgrade the Solaris software to a supported release if Sun Cluster 3.2 11/09 software does not support the release of the Solaris OS that your cluster currently runs . See Supported Products inSun Cluster Release Notes for more information.
- If Sun Cluster 3.2 11/09 software supports the release of the Solaris OS that you currently run on your cluster, further Solaris software upgrade is optional.
Otherwise, upgrade to Sun Cluster 3.2 11/09 software. Go to How to Upgrade Sun Cluster 3.2 11/09 Software (Standard).

How to Upgrade the Solaris OS and Volume Manager Software (Standard)

Perform this procedure on each node in the cluster to upgrade the Solaris OS. Perform all steps from the global zone only. If the cluster already runs on a version of the Solaris OS that supports Sun Cluster 3.2 11/09 software, further upgrade of the Solaris OS is optional. If you do not intend to upgrade the Solaris OS, proceed to How to Upgrade Sun Cluster 3.2 11/09 Software (Standard).

Note –

The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris OS to support upgrade to Sun Cluster 3.2 11/09 software. See Supported Products in Sun Cluster Release Notes for more information.

Before You Begin

Ensure that all steps in How to Prepare the Cluster for Upgrade (Standard) are completed.

Become superuser on the cluster node to upgrade.

If you are performing a dual-partition upgrade, the node must be a member of the partition that is in noncluster mode.

Determine whether the following Apache run-control scripts exist and are enabled or disabled:
/etc/rc0.d/K16apache /etc/rc1.d/K16apache /etc/rc2.d/K16apache /etc/rc3.d/S50apache /etc/rcS.d/K16apache
Some applications, such as Sun Cluster HA for Apache, require that Apache run control scripts be disabled.
- If these scripts exist and contain an uppercase K or S in the file name, the scripts are enabled. No further action is necessary for these scripts.
- If these scripts do not exist, in Step 7 you must ensure that any Apache run control scripts that are installed during the Solaris OS upgrade are disabled.
- If these scripts exist but the file names contain a lowercase k or s, the scripts are disabled. In Step 7 you must ensure that any Apache run control scripts that are installed during the Solaris OS upgrade are disabled.

Comment out all entries for globally mounted file systems in the node's /etc/vfstab file.
1. For later reference, make a record of all entries that are already commented out.
2. Temporarily comment out all entries for globally mounted file systems in the /etc/vfstab file.
  
  Entries for globally mounted file systems contain the global mount option. Comment out these entries to prevent the Solaris upgrade from attempting to mount the global devices.

Determine which procedure to follow to upgrade the Solaris OS.

Volume Manager	Procedure	Location of Instructions
Solaris Volume Manager	Any Solaris upgrade method except the Live Upgrade method. To use Live Upgrade, go instead to Chapter 4, Performing a Live Upgrade to Sun Cluster 3.2 11/09 Software.	Solaris installation documentation
Veritas Volume Manager	“Upgrading VxVM and Solaris”	Veritas Volume Manager installation documentation

Note –

If your cluster has VxVM installed, you must reinstall the existing VxVM software or upgrade to the Solaris 9 or 10 version of VxVM software as part of the Solaris upgrade process.

Upgrade the Solaris software, following the procedure that you selected in Step 4.

Note –

Do not perform the final reboot instruction in the Solaris software upgrade. Instead, do the following:

Return to this procedure to perform Step 6 and Step 7.
Reboot into noncluster mode in Step 8 to complete Solaris software upgrade.

When prompted, choose the manual reboot option.
When you are instructed to reboot a node during the upgrade process, always reboot into noncluster mode. For the boot and reboot commands, add the -x option to the command. The -x option ensures that the node reboots into noncluster mode. For example, either of the following two commands boot a node into single-user noncluster mode:

On SPARC based systems, perform either of the following commands:
phys-schost# reboot -- -xs or ok boot -xs
If the instruction says to run the init S command, use the reboot -- -xs command instead.

On x86 based systems, perform the following command:

phys-schost# shutdown -g -y -i0
Press any key to continue

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.

If the instruction says to run the init S command, shut down the system then change the GRUB kernel boot command to /platform/i86pc/multiboot -sx instead.

In the /a/etc/vfstab file, uncomment those entries for globally mounted file systems that you commented out in Step 3.

If Apache run control scripts were disabled or did not exist before you upgraded the Solaris OS, ensure that any scripts that were installed during Solaris upgrade are disabled.

To disable Apache run control scripts, use the following commands to rename the files with a lowercase k or s.

phys-schost# mv /a/etc/rc0.d/K16apache /a/etc/rc0.d/k16apache 
phys-schost# mv /a/etc/rc1.d/K16apache /a/etc/rc1.d/k16apache
phys-schost# mv /a/etc/rc2.d/K16apache /a/etc/rc2.d/k16apache
phys-schost# mv /a/etc/rc3.d/S50apache /a/etc/rc3.d/s50apache
phys-schost# mv /a/etc/rcS.d/K16apache /a/etc/rcS.d/k16apache

Alternatively, you can rename the scripts to be consistent with your normal administration practices.

Reboot the node into noncluster mode.

Include the double dashes (--) in the following command:
phys-schost# reboot -- -x

If your cluster runs VxVM, perform the remaining steps in the procedure “Upgrading VxVM and Solaris” to reinstall or upgrade VxVM.

Make the following changes to the procedure:

After VxVM upgrade is complete but before you reboot, verify the entries in the /etc/vfstab file.

If any of the entries that you uncommented in Step 6 were commented out, make those entries uncommented again.

When the VxVM procedures instruct you to perform a final reconfiguration reboot, do not use the -r option alone. Instead, reboot into noncluster mode by using the -rx options.
- On SPARC based systems, perform the following command:
  phys-schost# reboot -- -rx
- On x86 based systems, perform the shutdown and boot procedures that are described in Step 5 except add -rx to the kernel boot command instead of -sx.

Note –

If you see a message similar to the following, type the root password to continue upgrade processing. Do not run the fsck command nor type Ctrl-D.

WARNING - Unable to repair the /global/.devices/node@1 filesystem. 
Run fsck manually (fsck -F ufs /dev/vx/rdsk/rootdisk_13vol). Exit the 
shell when done to continue the boot process.

Type control-d to proceed with normal startup,
(or give root password for system maintenance):  Type the root password

(Optional) SPARC: Upgrade VxFS.

Follow procedures that are provided in your VxFS documentation.

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 after you add patches. Wait to reboot the node until after you upgrade the Sun Cluster software.

See Patches and Required Firmware Levels in the Sun Cluster Release Notes for the location of patches and installation instructions.

Next Steps

Upgrade to Sun Cluster 3.2 11/09 software. Go to How to Upgrade Sun Cluster 3.2 11/09 Software (Standard).

Note –

To complete the upgrade to a new marketing release of the Solaris OS, such as from Solaris 9 to Solaris 10 software, you must also upgrade the Sun Cluster software and dependency software to the version that is compatible with the new version of the Solaris OS.

How to Upgrade Sun Cluster 3.2 11/09 Software (Standard)

Perform this procedure to upgrade each node of the cluster to Sun Cluster 3.2 11/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.

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 9 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 11/09 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:
- 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.

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

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 in Sun Cluster Software Installation Guide for Solaris OS for more information.

Note –
This step is required if you upgraded from Sun Cluster 3.1 8/05 software and want to configure zone clusters (on Solaris 10 OS only).

This step is optional if you upgraded from Sun Cluster 3.1 8/05 and do not want to configure zone clusters, or if you upgraded from Sun Cluster 3.2 software.
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 option number 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.
  - On the Solaris 10 OS, the default netmask is 255.255.240.0. This default IP address range supports up to 64 nodes, up to 10 private networks, and up to 12 zone clusters in the cluster.
  - On the Solaris 9 OS, 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 Chapter 6, Completing the Upgrade.