|
| |
| Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX | |
Chapter 3
Sun Cluster SoftwareThis chapter describes how to upgrade Sun Cluster software to Java ES 5 Update 1 (Release 5U1): Sun Cluster 3.1 8/05 software.
The version of Sun Cluster software included in Java ES 5 Update 1 is the same as that included in Java ES 5. Therefore, this chapter covers feature upgrades to Release 5U1 from previous Java ES release families, but there is no maintenance upgrade from Java ES 5.
The chapter provides an overview of upgrade considerations for upgrading Sun Cluster software to Release 5U1.
Sun Cluster software is supported only on Solaris platforms.
The upgrade of Sun Cluster software described in this chapter includes both Sun Cluster framework software and Sun Cluster data-service software, or agents.
Overview of Sun Cluster Software UpgradesThis section describes the following general aspects of Sun Cluster software that impact upgrading to Java ES 5 Update 1 (Release 5U1):
About Release 5U1 Sun Cluster Software
Release 5U1 Sun Cluster is the same as Release 5 Sun Cluster. Release 5 Sun Cluster software represented a minor upgrade with respect to Release 4 Sun Cluster software (see the Sun Cluster Release Notes, http://docs.sun.com/doc/819-1405/6n3p13hac?a=view). Release 5 Sun Cluster was essentially the same as Release 4, except that Release 5 does not support Solaris 8 operating system.
For changes and additions to the Sun Cluster 3.1 8/05 documentation set, see the Sun Cluster 3.1 8/05 With Java Enterprise System 5 Special Instructions, http://docs.sun.com/doc/819-4351. Otherwise, procedures in the Sun Cluster 3.1 8/05 documentation set are valid for Release 5 Sun Cluster software.
Sun Cluster Software Upgrade Roadmap
Table 3-1 shows the supported Sun Cluster upgrade paths to Java ES 5 Update 1 (Release 5U1). The table applies to the Solaris operating system only.
Sun Cluster versions do not map one-to-one to Java ES releases. In the past Sun Cluster software's interim feature releases (IFRs) were incorporated into Java ES between formal Java ES releases. For this reason, the upgrade of Java ES Release 2, Release 3 and Release 4 Sun Cluster to Release 5U1 Sun Cluster, as shown in Table 3-1, includes the upgrade of Sun Cluster 3.1 4/04, Sun Cluster 3.1 9/04, and Sun Cluster 3.1 8/05 software to Release 5U1.
Table 3-1 Upgrade Paths to Java ES 5 Update 1 (Release 5U1): Sun Cluster 3.1 8/05 Software
Java ES Release
Sun Cluster
Software VersionGeneral Approach
Reconfiguration Required
Release 5
Sun Cluster 3.1 8/05
No upgrade needed.
None
Release 4
Sun Cluster 3.1 8/05
(2005Q4)Direct upgrade1:
Performed using the Sun Cluster scinstall utility.None.
Release 3
Sun Cluster 3.1 9/04
or
Sun Cluster 3.1 8/05 (IFR)Direct upgrade:
Performed using the Sun Cluster scinstall utility.Cluster configuration migrated to upgraded version automatically.
No Reconfiguration is required in upgrading the IFR to Release 5U1.
Release 2
Sun Cluster 3.1 4/04
or
Sun Cluster 3.1 9/04 (IFR)Direct upgrade:
Performed using the Sun Cluster scinstall utility.Cluster configuration migrated to upgraded version automatically
Release 1
Sun Cluster 3.1
Direct upgrade not certified:
But it can be performed using the scinstall utility.Cluster configuration migrated to upgraded version automatically
Pre-dates Java ES releases
Sun Cluster 3.0
Direct upgrade not certified:
But it can be performed using the scinstall utility.Cluster configuration migrated to upgraded version automatically
1Upgrade from Release 4 to Release 5U1 is not necessary unless shared components that are used by Sun Cluster software are have been upgraded to Release 5U1.
Sun Cluster Data
The following table shows the type of data that could be impacted by an upgrade of Sun Cluster software.
Sun Cluster Upgrade Strategy
Your strategy for upgrading Sun Cluster generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.
This section is to particularize that general discussion to Sun Cluster by presenting issues that might influence your Sun Cluster upgrade plan.
Compatibility Issues
Release 5U1 Sun Cluster software includes new graphical administration interfaces, but is backwardly compatible with earlier releases of Sun Cluster agents.
Sun Cluster Dependencies
Sun Cluster dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Sun Cluster software. Changes in Sun Cluster interfaces or functions, for example, could require upgraded versions of components upon which Sun Cluster software depends. The need to upgrade such components depends upon the specific upgrade path.
Sun Cluster has dependencies on the following Java ES components:
- Shared components. Sun Cluster software has dependencies on specific Java ES shared components (see Table 1-10).
- Data services. Sun Cluster software requires specific data services (or agents) to make Java ES product components highly available. For each product component running in a Sun Cluster environment there must be a corresponding data service to manage the corresponding cluster resources. Agent packages are typically upgraded as part of the Sun Cluster upgrade process.
Dual Upgrade
Dual upgrades, in which both Sun Cluster software and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) can be performed in the context of a Sun Cluster nonrolling upgrade, but not as part of a rolling upgrade.
The details of the procedure can be found in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnnd1?a=view. Modifications for Release 5U1 Sun Cluster are documented in the Sun Cluster 3.1 8/05 With Jave Enterprise System 5 Special Instructions, http://docs.sun.com/doc/819-4351.
The procedure applies to upgrade of Solaris operating system from Solaris 8 or Solaris 9 to Solaris 10.
Upgrading Sun Cluster Software to Java ES Release 5U1This section includes information about upgrading Sun Cluster software from Java ES 2005Q4 (Release 4), Java ES 2005Q1 (Release 3), and Java ES 2004Q2 (Release 2) to Java ES 5 Update 1 (Release 5U1). The upgrade procedure is the same for the three Sun Cluster versions found in these Java ES releases: Sun Cluster 3.1 4/04, Sun Cluster 3.1 9/04, and Sun Cluster 3.1 8/05 software.
If you already have Sun Cluster 3.1 8/05 (Release 3 or Release 4) software installed, you do not need to upgrade to Release 5U1 unless shared components that are used by Sun Cluster software have been upgraded to Release 5U1.
The section covers the following topics:
Introduction
When upgrading Sun Cluster software to Release 5U1, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is performed by running the scinstall script which upgrades Sun Cluster software and applies the previous Sun Cluster configuration after the software upgrade is complete. However all nodes in a cluster environment must be upgraded to the same version, either by shutting down the cluster and upgrading all nodes, or through a rolling upgrade in which the nodes are successively upgraded one at a time without shutting down the cluster.
- Upgrade Dependencies. While Sun Cluster software has dependencies on a number of Java ES shared components (see Table 1-10), these represent soft upgrade dependencies: Release 5U1 Sun Cluster software is compatible with the Release 4 versions of these components.
- Backward Compatibility. Release 5U1 Sun Cluster (framework) software is backwardly compatible with earlier cluster agents, and Release 5U1 Sun Cluster agent software is backwardly compatible with Java ES Release 4 components. However all nodes in a cluster must run the same version of framework and agent software.
- Upgrade Rollback. Rollback of the Release 5U1 upgrade of Sun Cluster software to earlier versions is not supported.
- Platform Issues. The approach for upgrading Sun Cluster software is the same on all Solaris platforms and hardware architectures, however Sun Cluster software is not supported on Linux platforms.
Sun Cluster Upgrade
This section provides an overview of how to perform an upgrade of Sun Cluster software from previous Java ES releases to Release 5U1:
The section covers the case of a nonrolling Sun Cluster upgrade. The case of a rolling upgrade is a bit different, in that the cluster is not shut down. However both cases involve the same general procedures, as described below, for a given cluster node. The specific procedures can be found in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view. Modifications for Release 5U1 Sun Cluster are documented in the Sun Cluster 3.1 8/05 With Jave Enterprise System 5 Special Instructions, http://docs.sun.com/doc/819-4351.
Pre-Upgrade Tasks
Before you upgrade Sun Cluster software you should perform the following tasks:
Verify Current Version Information
You can verify the current version of Sun Cluster software by entering the following command:
scinstall -pv
The command returns the Sun Cluster version and the version of each software package installed. If this command returns the 3.1 8/05 version, 3.1u4, then check the patch revision numbers to see which software you have installed, as indicated in the following table.
Table 3-3 Sun Cluster Version Verification Outputs
Java ES Release
Sun Cluster Version Number
Patch Revision Numbers
Release 1 (Sun Cluster 3.1)
3.1
Release 2 (Sun Cluster 3.1 4/04)
3.1u2
Release 2 or 3 (Sun Cluster 3.1 9/04)
3.1u3
Release 3 or 4 (Sun Cluster 3.1 8/05)
3.1u4
Solaris 9 sparc: 117949-15
Solaris 8 sparc: 117950-15
Solaris 9 x86: 117909-15Release 5 & 5U1
(Sun Cluster 3.1 8/05)3.1u4
Solaris 10 sparc: 120500-081
Solaris 9 sparc: 117949-23
Solaris 8 sparc: 117950-23
Solaris 10 x86: 120501-08
Solaris 9 x86: 117909-23
1Patch revision numbers are the minimum required for upgrade to Release 5U1 for the different platforms. If newer revisions become available, use the newer ones instead of those shown in the table.
Shut Down Sun Cluster Geographic Edition Infrastructure
If you are upgrading a cluster that runs Sun Cluster Geographic Edition software, you must first shut down the Sun Cluster Geographic Edition infrastructure and perform other steps to prepare the cluster for upgrade. Follow the upgrade procedures in the Sun Cluster Geographic Edition Installation Guide, http://docs.sun.com/doc/819-8004/6n9tmd19d?=view. These procedures include steps to upgrade Sun Cluster software at the appropriate stage of the upgrade.
Prepare the Cluster Node for Upgrade
The cluster node must be removed from the cluster environment before Sun Cluster software can be upgraded:
- Nonrolling upgrades. Removing the node from the cluster environment means shutting down the environment: switching resource groups offline, disabling them, shutting down applications running in the environment, backing up shared data, shutting down the cluster, backing up the system disk, and rebooting the node into non-cluster mode.
- Rolling upgrades. Removing the node from the cluster environment means moving all resource groups and device groups from the node, backing up shared data and the system disk, and rebooting the node into non-cluster mode.
The details of these operations and others that might need to be performed in specific situations are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Upgrade the Operating System
You might wish to make use of any upgrade downtime to upgrade your operating system to its most current version, and also upgrade the version of volume manager that you are using.
The details of these operations are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Upgrade Sun Cluster Dependencies
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Upgrade of Release 4 shared components upon which Sun Cluster software depends is optional and can be performed as described in Chapter 2, "Upgrading Java ES Shared Components." (Upgrade of Release 2 shared components to Release 5U1 is mandatory.)
Obtain Required Configuration Information and Passwords
No special information about your currently installed version is needed. However you will have to log in as superuser to perform the upgrade.
Upgrading Sun Cluster Software
This section discusses considerations that impact the upgrade procedure for Sun Cluster software followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of Sun Cluster software to Release 5U1 takes into account the following considerations:
- When upgrading Sun Cluster framework software it is a good idea to upgrade the data services needed to manage highly available Java ES components and other applications that run in your cluster environment.
- Upgrading Sun Cluster software also provides an opportunity to upgrade Java ES components or other applications that run in your cluster environment.
Upgrade Procedure
The procedure below applies to upgrading Sun Cluster software on each cluster node. The steps that follow are very general; details on how to perform these steps are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view. Modifications for Release 5U1 Sun Cluster are documented in the Sun Cluster 3.1 8/05 With Java Enterprise System 5 Special Instructions, http://docs.sun.com/doc/819-4351.
- Boot into non-cluster mode.
- Log in as root or become superuser.
su -
- Change to the following directory on the Java ES 5 Update 1 distribution:
cd /os_arch/Product/sun_cluster/os-ver/Tools
where os_arch matches your platform, such as Solaris_sparc, and os-ver is Solaris 9 or Solaris 10.
- Run the scinstall utility.
./scinstall
A main menu is displayed for performing cluster installation, configuration, and upgrade tasks.
- Upgrade Sun Cluster framework software and any desired data services.
Upgraded data services need to be configured by migrating the corresponding resources to the upgraded resource types (see Post-Upgrade Tasks).
- Apply any necessary patches to Sun Cluster framework software and to data services.
Information on accessing and applying the relevant patches is provided in the Sun Cluster 3.0-3.1 Release Notes Supplement, http://docs.sun.com/app/docs/doc/816-3381/6m9lratq9?a=view#gcpom.
- Reboot the node into the cluster.
Verifying the Upgrade
You can verify successful upgrade of Sun Cluster software as follows:
- Enter the following command.
scinstall -pv
The command returns the Sun Cluster version and the version of each software package installed. If this command returns the 3.1 8/05 version, 3.1u4, then check the patch revision numbers to see if you have Release 4 or Release 5U1 software, as indicated in Table 3-3.
- Check the data service upgrade log file.
The log file is referenced at the end of upgrade output messages.
Post-Upgrade Tasks
After you perform the upgrade of Sun Cluster software, you might need to perform a number of additional tasks, depending on whether you performed a nonrolling or a rolling upgrade. Among the tasks required to fully restore your cluster environment are:
Details for these post-installation steps are provided in the upgrade chapter of the Sun Cluster Installation Guide, http://docs.sun.com/doc/819-0420/6n2rlnncr?a=view.
Rolling Back the Upgrade
Rollback of Sun Cluster software is not supported. Changes made during the upgrade procedure cannot easily be backed out.