| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster |
| 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
Performing a Live Upgrade of a Cluster
How to Upgrade Quorum Server Software
How to Prepare the Cluster for Upgrade (Live Upgrade)
How to Upgrade the Solaris OS and Oracle Solaris Cluster 3.3 Software (Live Upgrade)
5. Performing a Rolling Upgrade
7. Recovering From an Incomplete Upgrade
The following table lists the tasks to perform to upgrade to Oracle Solaris Cluster 3.3 software. You also perform these tasks to upgrade only the Solaris OS.
Note - If you upgrade the Solaris OS to a new marketing release, such as from Solaris 9 to Oracle Solaris 10 software, you must also upgrade the Oracle Solaris Cluster software and dependency software to the version that is compatible with the new OS version.
Table 4-1 Task Map: Performing a Live 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 to prepare a cluster for live upgrade.
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
Oracle Solaris Cluster 3.3 framework
Oracle Solaris Cluster 3.3 patches
Oracle Solaris Cluster 3.3 data services (agents)
Applications that are managed by Oracle Solaris Cluster 3.3 data services
Veritas Volume Manager, if applicable
See Patches and Required Firmware Levels in the Oracle Solaris Cluster 3.3 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 Oracle Solaris Cluster commands. This series of upgrade procedures requires the following Oracle Solaris 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 Oracle Solaris Cluster man pages for the RBAC authorization that each Oracle Solaris Cluster subcommand requires.
On Sun Cluster 3.1 8/05 software, use the following command:
phys-schost% scstat
On Sun Cluster 3.2 or Oracle Solaris Cluster 3.3 software, use the following command:
phys-schost% cluster status
See the scstat(1M) or 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 Geographic Edition software.
Next Steps
Perform a live upgrade of the Solaris OS, Oracle Solaris Cluster 3.3 software, and other software. Go to How to Upgrade the Solaris OS and Oracle Solaris Cluster 3.3 Software (Live Upgrade).
Perform this procedure to upgrade the Solaris OS, volume-manager software, and Oracle Solaris Cluster software by using the live upgrade method. The Oracle Solaris Cluster live upgrade method uses the Solaris Live Upgrade feature. For information about live upgrade of the Solaris OS, refer to the following Solaris documentation:
Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning
If non-global zones are installed on the cluster, see Chapter 8, Upgrading the Solaris OS on a System With Non-Global Zones Installed, in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
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 Oracle Solaris Cluster 3.3 software. See Supported Products in Oracle Solaris Cluster 3.3 Release Notes for more information.
Perform this procedure on each node in the cluster.
Tip - You can use the cconsole utility to perform this procedure on multiple nodes simultaneously. See How to Install Cluster Control Panel Software on an Administrative Console in Oracle Solaris Cluster Software Installation Guide for more information.
Before You Begin
Ensure that all steps in How to Prepare the Cluster for Upgrade (Live Upgrade) are completed.
Follow instructions in Solaris Live Upgrade System Requirements in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning and Installing Solaris Live Upgrade in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
See Configuring Dual-String Mediators in Oracle Solaris Cluster Software Installation Guide for more information about mediators.
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 Finish Upgrade to Oracle Solaris Cluster 3.3 Software.
On Sun Cluster 3.1 8/05 software, use the following command:
phys-schost# scswitch -z -D setname -h node
Changes mastery.
Specifies the name of the disk set.
Specifies the name of the node to become primary of the disk set.
On Sun Cluster 3.2 or Oracle Solaris Cluster 3.3 software, use the following command:
phys-schost# cldevicegroup switch -n node devicegroup
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.
This name change is necessary for live upgrade software to recognize the global-devices file system. You will restore the DID names after the live upgrade is completed.
phys-schost# cp /etc/vfstab /etc/vfstab.old
Change the DID names to the physical names by changing /dev/did/{r}dsk/dYsZ to /dev/{r}dsk/cNtXdYsZ.
Remove global from the entry.
The following example shows the names of DID device d3s3, which corresponds to /global/.devices/node@2, changed to its physical device names and the global entry removed:
Original: /dev/did/dsk/d3s3 /dev/did/rdsk/d3s3 /global/.devices/node@2 ufs 2 no global Changed: dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /global/.devices/node@2 ufs 2 no -
phys-schost# lucreate options-n BE-name
Specifies the name of the boot environment that is to be upgraded.
For information about important options to the lucreate command, see Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning and the lucreate(1M) man page.
If the cluster already runs on a properly patched version of the Solaris OS that supports Oracle Solaris Cluster 3.3 software, this step is optional.
phys-schost# luupgrade -u -n BE-name -s os-image-path
Upgrades an operating system image on a boot environment.
Specifies the path name of a directory that contains an operating system image.
phys-schost# lumount -n BE-name -m BE-mount-point
Specifies the mount point of BE-name.
For more information, see Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning and the lumount(1M) man page.
You might need to patch your Solaris software to use Solaris Live Upgrade. For details about the patches that the Solaris OS requires and where to download them, see Managing Packages and Patches With Solaris Live Upgrade in Solaris 9 9/04 Installation Guide or Upgrading a System With Packages or Patches in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
Refer to your Veritas Storage Foundation installation documentation for procedures to use the live upgrade method.
Follow procedures that are provided in your VxFS documentation.
However, if some software applications to upgrade cannot use Solaris Live Upgrade, such as Sun QFS software, upgrade the applications in Step 25.
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 -u update -R BE-mount-point
Specifies that you are performing an upgrade of Oracle Solaris Cluster software.
Specifies the mount point for your alternate boot environment.
For more information, see the scinstall(1M) man page.
phys-schost# BE-mount-point/usr/cluster/bin/scinstall -u update -s all \ -d /cdrom/cdrom0/Solaris_arch/Product/sun_cluster_agents -R BE-mount-point
phys-schost# eject cdrom
Note - Do not reboot any node until all nodes in the cluster are upgraded on their inactive BE.
phys-schost# cp /etc/vstab.old /etc/vfstab
/dev/dsk/cNtXdYsZ /dev/rdsk/cNtXdYsZ /global/.devices/node@N ufs 2 no global
When the node is rebooted into the upgraded alternate BE, the DID names are substituted in the /etc/vfstab file automatically.
phys-schost# luumount -n BE-name
phys-schost# luactivate BE-name
The name of the alternate BE that you built in Step 4.
Note - Do not use the reboot or halt command. These commands do not activate a new BE.
phys-schost# shutdown -y -g0 -i0
You upgraded from Sun Cluster 3.1 8/05 software and you want to configure zone clusters.
Your cluster hosts software applications that require upgrade and for which you cannot use Solaris Live Upgrade.
(Optional) You want to change the private-network IP address range.
Ensure that all nodes in the cluster are shut down before you boot nodes into cluster mode.
ok boot
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.
The nodes reboot into cluster mode using the new, upgraded BE. The cluster upgrade is completed.
Ensure that all nodes in the cluster are shut down before you boot nodes into noncluster mode.
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.
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.
The upgraded BE now runs in noncluster mode.
Perform this step 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 Oracle Solaris Cluster Software Installation Guide for more information.
If you also expect to configure zone clusters, you specify that number in How to Finish Upgrade to Oracle Solaris Cluster 3.3 Software, after all nodes are back in cluster mode.
When run in noncluster mode, the clsetup utility displays the Main Menu for noncluster-mode operations.
The clsetup utility displays the current private-network configuration, then asks if you would like to change this configuration.
The clsetup utility displays the default private-network IP address, 172.16.0.0, and asks if it is okay to accept this default.
The clsetup utility will ask if it is okay to accept the default netmask. Skip to the next step to enter your response.
The clsetup utility will prompt for the new private-network IP address.
The clsetup utility displays the default netmask and then asks if it is okay to accept the default netmask.
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. If you choose to change the netmask, you specify in the following substeps the number of nodes and private networks that you expect in the cluster.
If you also expect to configure zone clusters, you specify that number in How to Finish Upgrade to Oracle Solaris Cluster 3.3 Software, after all nodes are back in cluster mode.
Then skip to the next step.
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.
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.
Note - If an upgrade process directs you to reboot, always reboot into noncluster mode, as described in Step 23, until all upgrades are complete.
phys-schost# shutdown -g0 -y -i0
ok boot
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.
The cluster upgrade is completed.
Example 4-1 Live Upgrade to Oracle Solaris Cluster 3.3 Software
This example shows a live upgrade of a cluster node. The example upgrades the SPARC based node to the Oracle Solaris 10 OS, Oracle Solaris Cluster 3.3 framework, and all Oracle Solaris Cluster data services that support the live upgrade method. In this example, sc31u4 is the original boot environment (BE). The new BE that is upgraded is named sc33 and uses the mount point /sc33. The directory /net/installmachine/export/solaris10/OS_image/ contains an image of the Oracle Solaris 10 OS. The installer state file is named sc33state.
The following commands typically produce copious output. This output is shown only where necessary for clarity.
phys-schost# lucreate sc31u4 -m /:/dev/dsk/c0t4d0s0:ufs -n sc33 … lucreate: Creation of Boot Environment sc33 successful. phys-schost# luupgrade -u -n sc33 -s /net/installmachine/export/solaris10/OS_image/ The Solaris upgrade of the boot environment sc33 is complete. Apply Oracle Solaris patches phys-schost# lumount sc33 /sc33 Insert the installation DVD-ROM. phys-schost# cd /cdrom/cdrom0/Solaris_sparc phys-schost# ./installer -no -saveState sc33state phys-schost# ./installer -nodisplay -noconsole -state sc33state -altroot /sc33 phys-schost# cd /cdrom/cdrom0/Solaris_sparc/sun_cluster/Sol_9/Tools phys-schost# ./scinstall -u update -R /sc33 phys-schost# /sc33/usr/cluster/bin/scinstall -u update -s all \ -d /cdrom/cdrom0 -R /sc33 phys-schost# cd / phys-schost# eject cdrom phys-schost# luumount sc33 phys-schost# luactivate sc33 Activation of boot environment sc33 successful. Upgrade all other nodes Shut down all nodes phys-schost# shutdown -y -g0 -i0 When all nodes are shut down, boot each node into cluster mode ok boot
At this point, you might upgrade data-service applications that cannot use the live upgrade method, before you reboot into cluster mode.
Troubleshooting
DID device name errors - During the creation of the inactive BE, if you receive an error that a file system that you specified with its DID device name, /dev/dsk/did/dNsX, does not exist, but the device name does exist, you must specify the device by its physical device name. Then change the vfstab entry on the alternate BE to use the DID device name instead. Perform the following steps:
1) For all unrecognized DID devices, specify the corresponding physical device names as arguments to the -m or -M option in the lucreate command. For example, if /global/.devices/node@nodeid is mounted on a DID device, use lucreate -m /global/.devices/node@nodeid:/dev/dsk/cNtXdYsZ:ufs [-m…] -n BE-name to create the BE.
2) Mount the inactive BE by using the lumount -n BE-name -m BE-mount-point command.
3) Edit the /BE-name/etc/vfstab file to convert the physical device name, /dev/dsk/cNtXdYsZ, to its DID device name, /dev/dsk/did/dNsX.
Mount point errors - During creation of the inactive boot environment, if you receive an error that the mount point that you supplied is not mounted, mount the mount point and rerun the lucreate command.
New BE boot errors - If you experience problems when you boot the newly upgraded environment, you can revert to your original BE. For specific information, see Failure Recovery: Falling Back to the Original Boot Environment (Command-Line Interface) in Solaris 9 9/04 Installation Guide or Chapter 6, Failure Recovery: Falling Back to the Original Boot Environment (Tasks), in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.
Global-devices file-system errors - After you upgrade a cluster on which the root disk is encapsulated, you might see one of the following error messages on the cluster console during the first reboot of the upgraded BE:
|
These messages indicate that the vxio minor number is the same on each cluster node. Reminor the root disk group on each node so that each number is unique in the cluster. See How to Assign a New Minor Number to a Device Group in Oracle Solaris Cluster Software Installation Guide.
Next Steps
Go to Chapter 6, Completing the Upgrade.
See Also
You can choose to keep your original, and now inactive, boot environment for as long as you need to. When you are satisfied that your upgrade is acceptable, you can then choose to remove the old environment or to keep and maintain it.
If you used an unmirrored volume for your inactive BE, delete the old BE files. For specific information, see the appropriate procedure for your original Solaris OS version.
If you detached a plex to use as the inactive BE, reattach the plex and synchronize the mirrors. For more information about working with a plex, see the appropriate procedure for your original Solaris OS versions.
You can also maintain the inactive BE. For information about how to maintain the environment, see the appropriate procedure for your original Solaris OS versions.
|