How to Upgrade the Solaris Operating Environment (Nonrolling)
Perform this procedure on each node in the cluster to upgrade the Solaris operating environment. If the cluster already runs on a version of the Solaris environment that supports Sun Cluster 3.1 10/03 software, this procedure is optional.
Note - The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris 8 or Solaris 9 environment to support Sun Cluster 3.1 10/03 software. See "Supported Products" in Sun Cluster 3.1 10/03 Release Notes for more information.
Ensure that all steps in How to Prepare the Cluster for Upgrade (Nonrolling) are completed.
Become superuser on the cluster node to upgrade.
Determine whether the following Apache links already exist, and if so, whether the file names contain an uppercase K or S:
/etc/rc0.d/K16apache /etc/rc1.d/K16apache /etc/rc2.d/K16apache /etc/rc3.d/S50apache /etc/rcS.d/K16apache
If these links already exist and do contain an uppercase K or S in the file name, no further action is necessary for these links.
If these links do not exist, or if these links exist but instead contain a lowercase k or s in the file name, you move aside these links in Step 8.
Comment out all entries for globally mounted file systems in the /etc/vfstab file.
Make a record of all entries that are already commented out for later reference.
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 operating environment.
Volume Manager
Procedure to Use
Location of Instructions
Solstice DiskSuite/Solaris Volume Manager
Upgrading Solaris software
Solaris 8 or Solaris 9 installation documentation
VERITAS Volume Manager
Upgrading VxVM and Solaris software
VERITAS Volume Manager installation documentation
Upgrade the Solaris software, following the procedure you selected in Step 5.
Note - Ignore the instruction to reboot at the end of the Solaris software upgrade process. You must first perform Step 7 and Step 8, then reboot into noncluster mode in Step 9 to complete Solaris software upgrade.
If you are instructed to reboot a node at other times during the upgrade process, always add the -x option to the command. This 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:
# reboot -- -xs ok boot -xs
In the /a/etc/vfstab file, uncomment those entries for globally mounted file systems that you commented out in Step 4.
If the Apache links in Step 3 did not already exist or if they contained a lowercase k or s in the file names before you upgraded the Solaris software, move aside the restored Apache links.
Use the following commands to rename the files with a lowercase k or s:
# mv /a/etc/rc0.d/K16apache /a/etc/rc0.d/k16apache # mv /a/etc/rc1.d/K16apache /a/etc/rc1.d/k16apache # mv /a/etc/rc2.d/K16apache /a/etc/rc2.d/k16apache # mv /a/etc/rc3.d/S50apache /a/etc/rc3.d/s50apache # mv /a/etc/rcS.d/K16apache /a/etc/rcS.d/k16apache
Reboot the node into noncluster mode.
Include the double dashes (--) in the following command:
# reboot -- -x
Install any required Solaris software patches and hardware-related patches, and download any needed firmware that is contained in the hardware patches.
For Solstice DiskSuite software (Solaris 8), also install any Solstice DiskSuite software patches.
Note - Do not reboot after you add patches. You reboot the node after you upgrade the Sun Cluster software.
See "Patches and Required Firmware Levels" in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
Upgrade to Sun Cluster 3.1 10/03 software.
Go to How to Upgrade to Sun Cluster 3.1 10/03 Software (Nonrolling).
Note - To complete upgrade from Solaris 8 to Solaris 9 software, you must also upgrade to the Solaris 9 version of Sun Cluster 3.1 10/03 software, even if the cluster already runs on Sun Cluster 3.1 10/03 software.
How to Upgrade to Sun Cluster 3.1 10/03 Software (Nonrolling)
This procedure describes how to upgrade the cluster to Sun Cluster 3.1 10/03 software. You must also perform this procedure to complete cluster upgrade from Solaris 8 to Solaris 9 software.
Tip - You can perform this procedure on more than one node at the same time.
Ensure that all steps in How to Prepare the Cluster for Upgrade (Nonrolling) are completed.
If you upgraded from Solaris 8 to Solaris 9 software, also ensure that all steps in How to Upgrade the Solaris Operating Environment (Nonrolling) are completed.
Become superuser on a node of the cluster.
Ensure that you have installed all required Solaris software patches and hardware-related patches.
For Solstice DiskSuite software (Solaris 8), also ensure that you have installed all required Solstice DiskSuite software patches.
Insert the Sun Cluster 3.1 10/03 CD-ROM into the CD-ROM drive on the node.
If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_1_u1 directory.
Upgrade the node to Sun Cluster 3.1 10/03 software.
Change to the /cdrom/suncluster_3_1/SunCluster_3.1/Sol_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
# cd /cdrom/suncluster_3_1_u1/SunCluster_3.1/Sol_ver/Tools
Upgrade the cluster framework software.
To upgrade from Sun Cluster 3.0 software, run the following command:
# ./scinstall -u update -S interact -M patchdir=dirname
- -S
Specifies the test IP addresses to use to convert NAFO groups to IP Network Multipathing groups
- interact
Specifies that scinstall prompts the user for each test IP address needed
- -M patchdir=dirname[,patchlistfile=filename]
Specifies the path to patch information so that the specified patches can be installed using the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname, including tarred, jarred, and zipped patches.
The -M option is not required. You can use any method you prefer for installing patches.
To upgrade from Sun Cluster 3.1 software, run the following command:
# ./scinstall -u update -M patchdir=dirname
- -M patchdir=dirname[,patchlistfile=filename]
Specifies the path to patch information so that the specified patches can be installed using the scinstall command. If you do not specify a patch-list file, the scinstall command installs all the patches in the directory dirname, including tarred, jarred, and zipped patches.
The -M option is not required. You can use any method you prefer for installing patches.
See "Patches and Required Firmware Levels" in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
Tip - If upgrade processing is interrupted, use the scstat(1M) command to ensure that the node is in noncluster mode (Offline), then restart the scinstall command.
# scstat -n -- Cluster Nodes -- Node name Status --------- ------ Cluster node: nodename Offline Cluster node: nodename Offline
See the scinstall(1M) man page for more information. See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for information about test addresses for IP Network Multipathing.
Note - Sun Cluster 3.1 software requires at least version 3.5.1 of Sun Explorer software. Upgrade to Sun Cluster software includes installing Sun Explorer data collector software, to be used in conjunction with the sccheck utility. If another version of Sun Explorer software was already installed before Sun Cluster upgrade, it is replaced by the version that is provided with Sun Cluster software. Options such as user identity and data delivery are preserved, but crontab entries must be manually recreated.
During Sun Cluster upgrade, scinstall might make one or more of the following configuration changes:
Change to the CD-ROM root directory and eject the CD-ROM.
Upgrade software applications that are installed on the cluster.
Ensure that application levels are compatible with the current version of Sun Cluster and Solaris software. See your application documentation for installation instructions. In addition, follow these guidelines to upgrade applications in a Sun Cluster 3.1 10/03 configuration:
If the applications are stored on shared disks, you must master the relevant disk groups and manually mount the relevant file systems before you upgrade the application.
If you are instructed to reboot a node during the upgrade process, always add the -x option to the command. This 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:
# reboot -- -xs ok boot -xs
(Optional) Upgrade Sun Cluster data services to the Sun Cluster 3.1 10/03 software versions.
Note - You must upgrade the Sun Cluster HA for Oracle 3.0 64-bit for Solaris 9 data service to the Sun Cluster 3.1 10/03 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 10/03 software.
Only those data services that are provided on the Sun Cluster 3.1 Agents CD-ROM are automatically upgraded by scinstall(1M). You must manually upgrade any custom or third-party data services.
Insert the Sun Cluster 3.1 Agents CD-ROM into the CD-ROM drive on the node to upgrade.
Upgrade the data-service software.
# scinstall -u update -s all -d /cdrom/cdrom0
-u update Specifies upgrade
-s all Updates all Sun Cluster data services that are installed on the node
Tip - If upgrade processing is interrupted, use the scstat(1M) command to ensure that the node is in noncluster mode (Offline), then restart the scinstall command.
# scstat -n -- Cluster Nodes -- Node name Status --------- ------ Cluster node: nodename Offline Cluster node: nodename Offline
Change to the CD-ROM root directory and eject the CD-ROM.
As needed, manually upgrade any custom data services that are not supplied on the Sun Cluster 3.1 Agents CD-ROM.
Install any Sun Cluster 3.1 10/03 data-service patches.
See "Patches and Required Firmware Levels" in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
After all nodes are upgraded, reboot each node into the cluster.# reboot
Verify that all upgraded software is at the same version on all upgraded nodes.
Did you upgrade from Solaris 8 to Solaris 9 software?
On
each node, run the following command to verify the consistency of the storage configuration: Perform a consistency check# scdidadm -c
-c
Caution - Do not proceed to Step 12 until your configuration passes this consistency check. Failure to do so might result in errors in device identification and cause data corruption.
The following table lists the possible output from the scdidadm -c command and the action you must take, if any.
Example Message | Action to Take |
|---|---|
device id for 'phys-schost-1:/dev/rdsk/c1t3d0' does not match physical device's id, device may have been replaced | Go to Recovering From Storage Configuration Changes During Upgrade and perform the appropriate repair procedure. |
device id for 'phys-schost-1:/dev/rdsk/c0t0d0' needs to be updated, run scdidadm -R to update | None. You update this device ID in Step 12. |
No output message | None |
See the scdidadm(1M) man page for more information.
On each node,
migrate the Sun Cluster storage database to Solaris 9 device IDs. Perform repair procedures Specify all devices# scdidadm -R all
-R all
On each node, run the
following command to verify that storage database migration to Solaris 9 device IDs is successful: If the scdidadm command displays a message, return to Step 11 to make further corrections to the storage configuration or the storage database. If the scdidadm command displays no messages, the device-ID migration is successful. If device-ID migration is verified on all cluster nodes, proceed to Step 14.# scdidadm -c
Did you upgrade VxVM? If no, proceed to Step 15. If yes, upgrade all disk groups. To upgrade a disk group to the highest version supported by the VxVM release you installed, run the following command from the primary node of the disk group:# vxdg upgrade dgname
See your VxVM administration documentation for more information about upgrading disk groups.
Do you intend to use Sun Management Center to monitor the cluster?