Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster |
1. Preparing to Upgrade Oracle Solaris Cluster Software
2. Performing a Standard Upgrade to Oracle Solaris Cluster 3.3 Software
3. Performing a Dual-Partition Upgrade to Oracle Solaris Cluster 3.3 Software
4. Performing a Live Upgrade to Oracle Solaris Cluster 3.3 Software
5. Performing a Rolling Upgrade
Performing a Rolling Upgrade of a Cluster
How to Upgrade Quorum Server Software
How to Prepare a Cluster Node for a Rolling Upgrade
How to Perform a Rolling Upgrade of a Solaris Maintenance Update
How to Perform a Rolling Upgrade of Oracle Solaris Cluster 3.3 Software
7. Recovering From an Incomplete Upgrade
Table 5-1 Task Map: Performing a Rolling Upgrade to Oracle Solaris Cluster 3.3 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 these steps for each of those clusters.
Perform all steps as superuser on the cluster and on the quorum server.
See Adding a Quorum Device in Oracle Solaris Cluster System Administration Guide.
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.3 version of Quorum Server software.
phys-schost# clquorum remove quorumserver
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 Oracle Solaris Cluster System Administration Guide.
quorumserver# clquorumserver stop +
quorumserver# cd /var/sadm/prod/SUNWentsysver
The version that is installed on your system.
quorumserver# ./uninstall
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.
By default, this directory is /var/scqsd.
Follow the steps in How to Install and Configure Quorum Server Software in Oracle Solaris Cluster Software Installation Guide for installing the Quorum Server software.
Follow the steps in How to Configure Quorum Devices in Oracle Solaris Cluster Software Installation Guide.
phys-schost# clquorum remove tempquorum
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
Oracle Solaris Cluster 3.3 framework
Oracle Solaris Cluster 3.3 required patches
Oracle Solaris Cluster 3.3 data services (agents)
Applications that are managed by Oracle Solaris Cluster 3.3 data service agents
See Patches and Required Firmware Levels in the Oracle Solaris Cluster 3.3 Release Notes for the location of patches and installation instructions.
phys-schost% cluster status
See the cluster(1CL) man page for more information.
Service interruption will be approximately the amount of time that your cluster normally takes to switch services to another node.
For uninstallation procedures, see the documentation for your version of Oracle Solaris Cluster Geographic Edition software.
phys-schost# clnode evacuate node-to-evacuate
See the clnode(1CL) man page for more information.
phys-schost# cluster status -t devicegroup,resourcegroup
See Configuring Dual-String Mediators in Oracle Solaris Cluster Software Installation Guide for more information.
phys-schost# medstat -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 Oracle Solaris Cluster Software Installation Guide.
Save this information for when you restore the mediators during the procedure How to Commit the Upgraded Cluster to Oracle Solaris Cluster 3.3 Software.
phys-schost# cldevicegroup switch -n node devicegr
phys-schost# metaset -s setname -d -m mediator-host-list
Specifies the disk-set name
Deletes from the disk set
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.
phys-schost# shutdown -y -g0 ok boot -x
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.
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.
[ 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
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.-
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 Oracle Solaris Cluster 3.3 software. See the Oracle Solaris Cluster 3.3 Release Notes for information about supported releases of the Solaris OS.
Otherwise, if you do not intend to upgrade the Solaris OS, go to How to Perform a Rolling Upgrade of Oracle Solaris Cluster 3.3 Software.
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 9 to Oracle Solaris 10 software. Go to Choosing an Oracle Solaris 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.
Perform this step to prevent the Solaris upgrade from attempting to mount the global devices.
Note - Do not reboot the node when prompted to reboot at the end of installation processing.
phys-schost# shutdown -y -g0 ok boot -x
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.
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.
[ 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
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.-
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
Go to How to Perform a Rolling Upgrade of Oracle Solaris Cluster 3.3 Software.
Perform this procedure to upgrade a node that runs Oracle Solaris Cluster 3.3 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.
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.
phys-schost# cd /cdrom/cdrom0/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools
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 installation DVD-ROM.
The scinstall Main Menu is displayed.
*** 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.
Upgrade processing is finished when the system displays the message Completed Oracle Solaris Cluster framework upgrade and prompts you to press Enter to continue.
Note - For 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 Oracle Solaris Cluster Data Service for SAP Web Application Server Guide.
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.
The Upgrade Menu is displayed.
You can choose from the list of data services that are available to upgrade or choose to upgrade all installed data services.
The Upgrade Menu is displayed.
phys-schost# eject cdrom
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 Oracle Solaris Cluster Software Installation Guide.
As of the Sun Cluster 3.2 release, LOFS is no longer disabled by default during Oracle Solaris 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.
View the upgrade log file that is referenced at the end of the upgrade output messages.
If you want to upgrade VxVM and did not upgrade the Solaris OS, follow procedures in Veritas Storage Foundation installation documentation to upgrade VxVM without upgrading the operating system.
Note - If any upgrade procedure instruct you to perform a reboot, you must add the -x option to the boot command. This option boots the cluster into noncluster mode.
Ensure that application levels are compatible with the current versions of Oracle Solaris Cluster and Solaris software. See your application documentation for installation instructions.
phys-schost# shutdown -g0 -y
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.
Repeat this process until all nodes in the cluster are upgraded.
Next Steps
When all nodes in the cluster are upgraded, go to Chapter 6, Completing the Upgrade.