This chapter provides the following information and procedures to upgrade a Sun Cluster 3.x configuration to Sun Cluster 3.1 4/04 software:
Task Map: Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling)
How to Upgrade the Solaris Operating Environment (Nonrolling)
How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling)
How to Upgrade Sun Cluster-Module Software for Sun Management Center (Nonrolling)
How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling)
Task Map: Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)
How to Upgrade to a Solaris Maintenance Update Release (Rolling)
How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling)
This section provides the following guidelines to upgrade a Sun Cluster configuration:
Observe the following requirements and restrictions when you upgrade to Sun Cluster 3.1 4/04 software:
The cluster must run on or be upgraded to at least Solaris 8 2/02 software, including the most current required patches.
The cluster hardware must be a supported configuration for Sun Cluster 3.1 4/04 software. Contact your Sun representative for information about current supported Sun Cluster configurations.
You must upgrade all software to a version that is supported by Sun Cluster 3.1 4/04 software. For example, if a data service is supported on Sun Cluster 3.0 software but is not supported on Sun Cluster 3.1 4/04 software, you must upgrade that data service to the version of that data service that is supported on Sun Cluster 3.1 4/04 software. If the related application of that data service is not supported on Sun Cluster 3.1 4/04 software, you must also upgrade that application to a supported release.
The scinstall upgrade utility only upgrades those data services that are provided with Sun Cluster 3.1 4/04 software. You must manually upgrade any custom or third-party data services.
For upgrade from a Sun Cluster 3.0 release, have available the test IP addresses to use with your public-network adapters when NAFO groups are converted to Internet Protocol (IP) Network Multipathing groups. The scinstall upgrade utility prompts you for a test IP address for each public-network adapter in the cluster. A test IP address must be on the same subnet as the primary IP address for the adapter.
See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for information about test IP addresses for IP Network Multipathing groups.
Sun Cluster 3.1 4/04 software supports only nonrolling upgrade from Solaris 8 software to Solaris 9 software.
Sun Cluster 3.1 4/04 software supports direct upgrade only from Sun Cluster 3.x software.
Sun Cluster 3.1 4/04 software does not support any downgrade of Sun Cluster software.
Sun Cluster 3.1 4/04 software does not support upgrade between architectures.
Sun Cluster 3.1 4/04 software does not support the Live Upgrade method to upgrade Solaris software in a Sun Cluster configuration.
Choose one of the following methods to upgrade your cluster to Sun Cluster 3.1 4/04 software:
Nonrolling upgrade – In a nonrolling upgrade, you shut down the cluster before you upgrade the cluster nodes. You return the cluster to production after all nodes are fully upgraded. You must use the nonrolling-upgrade method if one or more of the following conditions apply:
You are upgrading from Sun Cluster 3.0 software.
You are upgrading from Solaris 8 software to Solaris 9 software.
Any software products that you are upgrading, such as applications or databases, require that the same version of the software is running on all cluster nodes at the same time.
You are also upgrading VxVM.
Rolling upgrade – In a rolling upgrade, you upgrade one node of the cluster at a time. The cluster remains in production with services running on the other nodes. You can use the rolling-upgrade method only if all of the following conditions apply:
You are upgrading from Sun Cluster 3.1 software.
You are upgrading Solaris software only to a Solaris Update release, if at all.
For any applications or databases you must upgrade, the current version of the software can coexist in a running cluster with the upgrade version of that software.
If your cluster configuration meets the requirements to perform a rolling upgrade, you can still choose to perform a nonrolling upgrade instead.
For overview information about planning your Sun Cluster 3.1 4/04 configuration, see Chapter 1, Planning the Sun Cluster Configuration.
Follow the tasks in this section to perform a nonrolling upgrade from Sun Cluster 3.x software to Sun Cluster 3.1 4/04 software. In a nonrolling upgrade, you shut down the entire cluster before you upgrade the cluster nodes. This procedure also enables you to upgrade the cluster from Solaris 8 software to Solaris 9 software.
To perform a rolling upgrade to Sun Cluster 3.1 4/04 software, instead follow the procedures in Upgrading to Sun Cluster 3.1 4/04 Software (Rolling).
Task |
Instructions |
---|---|
1. Read the upgrade requirements and restrictions. | |
2. Take the cluster out of production, disable resources, and back up shared data and system disks. If the cluster uses dual-string mediators for Solstice DiskSuite/Solaris Volume Manager, unconfigure the mediators. | |
3. Upgrade the Solaris software, if necessary, to a supported Solaris update release. Optionally, upgrade VERITAS Volume Manager (VxVM). |
How to Upgrade the Solaris Operating Environment (Nonrolling) |
4. Upgrade to Sun Cluster 3.1 4/04 framework and data-service software. If necessary, upgrade applications. If the cluster uses dual-string mediators, reconfigure the mediators. If you upgraded VxVM, upgrade disk groups. |
How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling) |
5. (Optional) Upgrade the Sun Cluster module to Sun Management Center, if needed. |
How to Upgrade Sun Cluster-Module Software for Sun Management Center (Nonrolling) |
6. Register new resource types, migrate existing resources to new resource types, modify resource type extension properties as needed, enable resources, and bring resource groups online. |
How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling) |
Before you upgrade the software, perform the following steps to take the cluster out of production:
Ensure that the configuration meets requirements for upgrade.
Have available the CD-ROMs, documentation, and patches for all software products you are upgrading.
Solaris 8 or Solaris 9 operating environment
Sun Cluster 3.1 4/04 framework
Sun Cluster 3.1 4/04 data services (agents)
Applications that are managed by Sun Cluster 3.1 4/04 data-service agents
VERITAS Volume Manager
See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
(Optional) Install Sun Cluster 3.1 4/04 documentation.
Install the documentation packages on your preferred location, such as an administrative console or a documentation server. See the index.html file at the top level of the Java Enterprise System Accessory CD 3 CD-ROM to access installation instructions.
Are you upgrading from Sun Cluster 3.0 software?
If no, proceed to Step 5.
If yes, have available your list of test IP addresses, one for each public-network adapter in the cluster.
A test IP address is required for each public-network adapter in the cluster, regardless of whether the adapter is the active adapter or the backup adapter in the group. The test IP addresses will be used to reconfigure the adapters to use IP Network Multipathing.
Each test IP address must be on the same subnet as the existing IP address that is used by the public-network adapter.
To list the public-network adapters on a node, run the following command:
% pnmstat |
See the IP Network Multipathing Administration Guide (Solaris 8) or System Administration Guide: IP Services (Solaris 9) for more information about test IP addresses for IP Network Multipathing.
Notify users that cluster services will be unavailable during upgrade.
Ensure that the cluster is functioning normally.
To view the current status of the cluster, run the following command from any node:
% scstat |
See the scstat(1M) man page for more information.
Search the /var/adm/messages log on the same node for unresolved error messages or warning messages.
Check volume-manager status.
Become superuser on a node of the cluster.
Switch each resource group offline.
# scswitch -F -g resource-group |
Switches a resource group offline
Specifies the name of the resource group to take offline
Disable all resources in the cluster.
The disabling of resources before upgrade prevents the cluster from bringing the resources online automatically if a node is mistakenly rebooted into cluster mode.
If you are upgrading from a Sun Cluster 3.1 release, you can use the scsetup(1M) utility instead of the command line. From the Main Menu, choose Resource Groups, then choose Enable/Disable Resources.
From any node, list all enabled resources in the cluster.
# scrgadm -pv | grep "Res enabled" (resource-group:resource) Res enabled: True |
Identify those resources that depend on other resources.
You must disable dependent resources first before you disable the resources that they depend on.
Disable each enabled resource in the cluster.
scswitch -n -j resource |
Disables
Specifies the resource
See the scswitch(1M) man page for more information.
Verify that all resources are disabled.
# scrgadm -pv | grep "Res enabled" (resource-group:resource) Res enabled: False |
Move each resource group to the unmanaged state.
# scswitch -u -g resource-group |
Moves the specified resource group to the unmanaged state
Specifies the name of the resource group to move into the unmanaged state
Verify that all resources on all nodes are Offline and that all resource groups are in the Unmanaged state.
# scstat -g |
Does your cluster use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
If no, proceed to Step 13.
If yes, unconfigure your mediators.
See Configuring Dual-String Mediators for more information.
Run the following command to verify that no mediator data problems exist.
# medstat -s setname |
Specifies the diskset name
If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Fix Bad Mediator Data.
List all mediators.
Use this information for when you restore the mediators during the procedure How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).
For a diskset that uses mediators, take ownership of the diskset if no node already has ownership.
# metaset -s setname -t |
Takes ownership of the diskset
Unconfigure all mediators for the diskset.
# metaset -s setname -d -m mediator-host-list |
Specifies the diskset name
Deletes from the diskset
Specifies the name of the node to remove as a mediator host for the diskset
See the mediator(7D) man page for further information about mediator-specific options to the metaset command.
Repeat Step c through Step d for each remaining diskset that uses mediators.
Stop all applications that are running on each node of the cluster.
Ensure that all shared data is backed up.
From one node, shut down the cluster.
# scshutdown -g -y |
See the scshutdown(1M) man page for more information.
Boot each node into noncluster mode.
ok boot -x |
Ensure that each system disk is backed up.
Determine whether to upgrade the Solaris operating environment.
If Sun Cluster 3.1 4/04 software does not support the release of the Solaris environment that you currently run on your cluster, you must upgrade the Solaris software to a supported release. Go to How to Upgrade the Solaris Operating Environment (Nonrolling).
If your cluster configuration already runs on a release of the Solaris environment that supports Sun Cluster 3.1 4/04 software, further Solaris software upgrade is optional.
To upgrade Sun Cluster software, go to How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).
To upgrade Solaris software, go to How to Upgrade the Solaris Operating Environment (Nonrolling).
See “Supported Products” in Sun Cluster Release Notes for Solaris OS for more information.
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 4/04 software, this procedure is optional.
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 4/04 software. See “Supported Products” in Sun Cluster Release Notes for Solaris OS 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 |
Any Solaris upgrade method except the Live Upgrade method. |
Solaris 8 or Solaris 9 installation documentation |
VERITAS Volume Manager |
“Upgrading VxVM and Solaris” |
VERITAS Volume Manager installation documentation |
If your cluster has VxVM installed, you must reinstall the existing VxVM software or upgrade to the Solaris 9 version of VxVM software as part of the Solaris upgrade process.
Upgrade the Solaris software, following the procedure that you selected in Step 5.
Note the following special instructions:
Do not perform the final reboot instruction in the Solaris software upgrade. Instead, return to this procedure to perform Step 7 and Step 8, then reboot into noncluster mode in Step 9 to complete Solaris software upgrade.
When you are instructed to reboot a node during the upgrade process, always 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:
# 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.
Move aside restored Apache links if either of the following conditions was true before you upgraded the Solaris software:
The Apache links listed in Step 3 did not exist.
The Apache links listed in Step 3 existed and contained a lowercase k or s in the file names.
To move aside restored Apache links, which contain an uppercase K or S in the name, 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 |
If your cluster runs VxVM, perform the remaining steps in the procedure “Upgrading VxVM and Solaris” to reinstall or upgrade VxVM.
Note the following special instructions:
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 |
When the VxVM procedures instruct you to perform a final reconfiguration reboot by using the -r option, reboot into noncluster mode by using the -x option instead.
# reboot -- -x |
After VxVM upgrade is complete, verify the entries in the /etc/vfstab file. If any of the entries that you uncommented in Step 7 were commented out, make those entries uncommented again.
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.
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 Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
Upgrade to Sun Cluster 3.1 4/04 software.
Go to How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).
To complete upgrade from Solaris 8 to Solaris 9 software, you must also upgrade to the Solaris 9 version of Sun Cluster 3.1 4/04 software, even if the cluster already runs on Sun Cluster 3.1 4/04 software.
This procedure describes how to upgrade the cluster to Sun Cluster 3.1 4/04 software. You must also perform this procedure to complete cluster upgrade from Solaris 8 to Solaris 9 software.
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 Java Enterprise System 2004Q2 2 of 2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.
Upgrade the node to Sun Cluster 3.1 4/04 software.
From the /cdrom/cdrom0 directory, change to the Solaris_sparc/Product/sun_cluster/Solaris_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
The following example uses the path to the Solaris 8 version of Sun Cluster software.
# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/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 |
Specifies the test IP addresses to use to convert NAFO groups to IP Network Multipathing groups
Specifies that scinstall prompts the user for each test IP address needed
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 |
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.
Upgrade processing is finished when the system displays the message Completed Sun Cluster framework upgrade and the path to the upgrade log.
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.
Sun Cluster 3.1 4/04 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 4/04 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.
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:
# reboot -- -xs ok boot -xs |
(Optional) Upgrade Sun Cluster data services to the Sun Cluster 3.1 4/04 software versions.
You must upgrade the Sun Cluster HA for Oracle 3.0 64–bit for Solaris 9 data service to the Sun Cluster 3.1 4/04 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 4/04 software.
Only those data services that are delivered on the Java Enterprise System Accessory CD 3 CD-ROM are automatically upgraded by the scinstall(1M) utility. You must manually upgrade any custom or third-party data services. Follow the procedures provided with those data services.
Insert the Java Enterprise System Accessory CD 3 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 |
Specifies upgrade
Updates all Sun Cluster data services that are installed on the node
Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and the path to the upgrade log.
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 Java Enterprise System Accessory CD 3 CD-ROM.
Install any Sun Cluster 3.1 4/04 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.
On each upgraded node, view the installed levels of Sun Cluster software.
# scinstall -pv |
From one node, verify that all upgraded cluster nodes are running in cluster mode (Online).
# scstat -n |
See the scstat(1M) man page for more information about displaying cluster status.
On each node, run the following command to verify the consistency of the storage configuration:
# scdidadm -c |
Perform a consistency check
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.
# scdidadm -R all |
Perform repair procedures
Specify all devices
On each node, run the following command to verify that storage database migration to Solaris 9 device IDs is successful:
# scdidadm -c |
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.
Does your configuration use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
If no, proceed to Step 15.
If yes, restore the mediator configurations.
Determine which node has ownership of a diskset to which you will add the mediator hosts.
# metaset -s setname |
Specifies the diskset name
If no node has ownership, take ownership of the diskset.
# metaset -s setname -t |
Takes ownership of the diskset
Recreate the mediators.
# metaset -s setname -a -m mediator-host-list |
Adds to the diskset
Specifies the names of the nodes to add as mediator hosts for the diskset
Repeat Step a through Step c for each diskset in the cluster that uses mediators.
If no, proceed to Step 16.
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.
The following example shows the process of a nonrolling upgrade of a two-node cluster from Sun Cluster 3.0 to Sun Cluster 3.1 4/04 software on the Solaris 8 operating environment. The cluster node names are phys-schost-1 and phys-schost-2.
(On the first node, upgrade framework software from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM) phys-schost-1# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \ Solaris_8/Tools phys-schost-1# ./scinstall -u update -S interact (On the first node, upgrade data services from the Java Enterprise System Accessory CD 3 CD-ROM) phys-schost-1# ./scinstall -u update -s all -d /cdrom/cdrom0 (On the second node, upgrade framework software from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM) phys-schost-2# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/ \ Solaris_8/Tools phys-schost-2# ./scinstall -u update -S interact (On the second node, upgrade data services from the Java Enterprise System Accessory CD 3 CD-ROM) phys-schost-2# ./scinstall -u update -s all -d /cdrom/cdrom0 (Reboot each node into the cluster) phys-schost-1# reboot phys-schost-2# reboot (Verify cluster membership) # scstat -- Cluster Nodes -- Node name Status --------- ------ Cluster node: phys-schost-1 Online Cluster node: phys-schost-2 Online |
Perform the following steps to upgrade Sun Cluster-module software on the Sun Management Center server machine, help-server machine, and console machine.
If you intend to upgrade the Sun Management Center software itself, do not perform this procedure. Instead, proceed to How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling) to finish Sun Cluster software upgrade. Then go to How to Upgrade Sun Management Center Software to upgrade Sun Management Center software and the Sun Cluster module.
As superuser, remove the existing Sun Cluster–module packages.
Use the pkgrm(1M) command to remove all Sun Cluster–module packages from all locations listed in the following table.
# pkgrm module-package |
Location |
Module Package to Remove |
---|---|
Sun Management Center console machine |
SUNWscscn |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center help-server machine |
SUNWscshl |
Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.
As superuser, reinstall Sun Cluster–module packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to the locations listed in the following table.
In the CD-ROM path, the value of ver is 8 (for Solaris 8) or 9 (for Solaris 9).
# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_ver/Packages/ # pkgadd module-package |
Location |
Module Package to Install |
---|---|
Sun Management Center console machine |
SUNWscshl |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center help-server machine |
SUNWscshl |
You install the help-server package SUNWscshl on both the console machine and the help-server machine. You do not upgrade to a new SUNWscscn package on the console machine.
Finish the upgrade.
Go to How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).
Perform this procedure to reregister all resource types that received a new version from the upgrade, to modify eligible resources to use the new version of its resource type, then to re-enable resources and bring resource groups back online.
To upgrade future versions of resource types, see “Upgrading a Resource Type” in Sun Cluster Data Service Planning and Administration Guide for Solaris OS.
Ensure that all steps in How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling) are completed.
If you upgraded any data services that are not supplied on the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM or the Java Enterprise System Accessory CD 3 CD-ROM, register the new resource types for those data services.
Follow the documentation that comes with the data services.
From any node, start the scsetup(1M) utility.
# scsetup |
Register the new resource types.
Migrate all eligible resources to the new version of its resource type.
From the Resource Group menu, choose Change properties of a resource
.
Choose Manage resource versioning
.
Choose Show versioning status
.
The scsetup utility displays all resources for which a new version of its resource type was installed during the upgrade. Make note of which new resource types you will upgrade the resources to.
Choose Re-version all eligible resources
.
Follow the prompts to upgrade eligible resources to the new version of its resource type.
Return to the Change properties of a resource menu.
Modify extension properties for new resource type versions.
For each new resource type that you migrated existing resources to, determine whether the new resource type requires additional modifications to its extension properties.
Refer to each related data service manual for the requirements of each new resource type.
You do not need to change the Type_version property of a new resource type. That property was modified when you migrated resources to their new resource types in Step 5.
From the Change properties of a resource menu, choose Change extension resource properties
.
Follow the prompts to modify the necessary extension properties.
Refer to your data service documentation for the names of extension properties and values to modify.
Repeat for each resource type that requires modifications.
Return to the Resource Groups menu.
Re-enable all disabled resources.
From the Resource Group Menu, choose Enable/Disable a resource
.
Choose a resource to enable and follow the prompts.
Repeat Step b for each disabled resource.
When all resources are re-enabled, type q to return to the Resource Group Menu.
Bring each resource group back online.
When all resource groups are back online, exit the scsetup utility.
Type q to back out of each submenu, or press Ctrl-C.
The cluster upgrade is complete. You can now return the cluster to production.
This section provides procedures to perform a rolling upgrade from Sun Cluster 3.1 software to Sun Cluster 3.1 4/04 software. In a rolling upgrade, you upgrade one cluster node at a time, while the other cluster nodes remain in production.
To upgrade from Sun Cluster 3.0 software, follow the procedures in Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).
Sun Cluster 3.1 4/04 software does not support rolling upgrade from Solaris 8 software to Solaris 9 software. You can upgrade Solaris software to an update release during Sun Cluster rolling upgrade. To upgrade a Sun Cluster configuration from Solaris 8 software to Solaris 9 software, perform the procedures in Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).
Task |
Instructions |
---|---|
1. Read the upgrade requirements and restrictions. | |
2. Take the cluster out of production, disable resources, and ensure that shared data and system disks are backed up. If the cluster uses dual-string mediators for Solstice DiskSuite/Solaris Volume Manager, unconfigure the mediators. | |
3. Upgrade the Solaris software, if necessary, to a supported Solaris update release. Optionally, upgrade VERITAS Volume Manager (VxVM). |
How to Upgrade to a Solaris Maintenance Update Release (Rolling) |
4. Upgrade to Sun Cluster 3.1 4/04 framework and data-service software. If necessary, upgrade applications. If you upgraded VxVM, upgrade disk groups. | |
5. If the cluster uses dual-string mediators, reconfigure the mediators. Register new resource types, migrate existing resources to new resource types, modify resource type extension properties as needed, enable resources, and bring resource groups online. Upgrade the Sun Cluster module to Sun Management Center, if needed. |
How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling) |
Perform this procedure on one node at a time. The upgraded node is taken out of the cluster, while the remaining nodes continue to function as active cluster members.
Do not use any new features of the update release, install new data services, or issue any administrative configuration commands until all nodes of the cluster are successfully upgraded.
Ensure that the configuration meets requirements for upgrade.
Have available the CD-ROMs, documentation, and patches for all the software products you are upgrading before you begin to upgrade the cluster.
Solaris 8 or Solaris 9 operating environment
Sun Cluster 3.1 4/04 framework
Sun Cluster 3.1 4/04 data services (agents)
Applications that are managed by Sun Cluster 3.1 4/04 data-service agents
See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
(Optional) Install Sun Cluster 3.1 4/04 documentation.
Install the documentation packages on your preferred location, such as an administrative console or a documentation server. See the index.html file at the top level of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to access installation instructions.
From any node, view the current status of the cluster.
Save the output as a baseline for later comparison.
% scstat % scrgadm -pv[v] |
See the scstat(1M) and scrgadm(1M) man pages for more information.
Become superuser on one node of the cluster to upgrade.
Move all resource groups and device groups that are running on the node to upgrade.
# scswitch -S -h from-node |
Moves all resource groups and device groups
Specifies the name of the node from which to move resource groups and device groups
See the scswitch(1M) man page for more information.
Verify that the move completed successfully.
# scstat -g -D |
Show status for all resource groups
Show status for all disk device groups
Ensure that the system disk and data is backed up.
Does your cluster use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
If no, proceed to Step 10.
If yes, unconfigure your mediators.
See Configuring Dual-String Mediators for more information.
Run the following command to verify that no mediator data problems exist.
# medstat -s setname |
Specifies the diskset name
If the value in the Status field is Bad, repair the affected mediator host. Follow the procedure How to Fix Bad Mediator Data.
List all mediators.
Use this information for when you restore the mediators during the procedure How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling).
For a diskset that uses mediators, take ownership of the diskset if no node already has ownership.
# metaset -s setname -t |
Takes ownership of the diskset
Unconfigure all mediators for the diskset.
# metaset -s setname -d -m mediator-host-list |
Specifies the diskset name
Deletes from the diskset
Specifies the name of the node ot remove as a mediator host for the diskset
See the mediator(7D) man page for further information about mediator-specific options to the metaset command.
Repeat Step c through Step d for each remaining diskset that uses mediators.
Shut down the node that you want to upgrade and boot it into noncluster mode.
# shutdown -y -g0 ok boot -x |
The other nodes of the cluster continue to function as active cluster members.
Do you intend to upgrade the Solaris software to a Maintenance Update release?
The cluster must already run on, or be upgraded to, at least the minimum required level of the Solaris operating environment to support Sun Cluster 3.1 4/04 software. See the Sun Cluster Release Notes for Solaris OS for information about supported releases of the Solaris operating environment.
Perform this procedure to upgrade the Solaris 8 or Solaris 9 operating environment to a supported Maintenance Update release.
To upgrade a cluster from Solaris 8 to Solaris 9 software, with or without upgrading Sun Cluster software as well, you must perform a nonrolling upgrade. Go to Upgrading to Sun Cluster 3.1 4/04 Software (Nonrolling).
Ensure that all steps in How to Prepare the Cluster for Upgrade (Rolling) are completed.
Temporarily comment out all entries for globally mounted file systems in the /etc/vfstab file.
Perform this step to prevent the Solaris upgrade from attempting to mount the global devices.
Follow instructions in the Solaris maintenance update installation guide to install the Maintenance Update release.
Do not reboot the node when prompted to reboot at the end of installation processing.
Uncomment all entries in the /a/etc/vfstab file for globally mounted file systems that you commented out in Step 2.
Install any required Solaris software patches and hardware-related patches, and download any needed firmware that is contained in the hardware patches.
Do not reboot the node until Step 6.
Reboot the node into noncluster mode.
Include the double dashes (--) in the following command:
# reboot -- -x |
Upgrade the Sun Cluster software.
Go to How to Upgrade to Sun Cluster 3.1 4/04 Software (Rolling).
Perform this procedure to upgrade a node to Sun Cluster 3.1 4/04 software while the remaining cluster nodes are in cluster mode.
Do not use any new features provided in the Sun Cluster 3.1 4/04 software until all nodes of the cluster are upgraded.
Ensure that all steps in How to Prepare the Cluster for Upgrade (Rolling) are completed.
If you upgraded the Solaris operating environment to a Maintenance Update release, also ensure that all steps in How to Upgrade to a Solaris Maintenance Update Release (Rolling) are completed.
Upgrade to Sun Cluster 3.1 4/04 software.
Insert the Sun Java Enterprise System 2004Q2 2 of 2 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, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.
From the /cdrom/cdrom0 directory, change to the Solaris_sparc/Product/sun_cluster/Solaris_ver/Tools directory, where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .
The following example uses the path to the Solaris 8 version of Sun Cluster software.
# cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools |
Install the Sun Cluster 3.1 4/04 software.
Do not use the /usr/cluster/bin/scinstall command that is already installed on the node. You must use the scinstall command on the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM.
# ./scinstall -u update -M patchdir=dirname |
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.
Upgrade processing is finished when the system displays the message Completed Sun Cluster framework upgrade and the path to the upgrade log.
See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
See the scinstall(1M) man page for more information.
Sun Cluster 3.1 4/04 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.
Change to the CD-ROM root directory and eject the CD-ROM.
Install any Sun Cluster 3.1 4/04 software patches.
Do you intend to upgrade any data services?
Upgrade applications as needed.
Do not upgrade an application if the newer version cannot coexist in the cluster with the older version.
Follow the instructions that are provided in your third-party documentation.
(Optional) For each node on which data services are installed, upgrade to the Sun Cluster 3.1 4/04 data-service update software.
You must upgrade the Sun Cluster HA for Oracle 3.0 64–bit for Solaris 9 data service to the Sun Cluster 3.1 4/04 version. Otherwise, you can continue to use Sun Cluster 3.0 data services after upgrade to Sun Cluster 3.1 4/04 software.
Insert the Java Enterprise System Accessory CD 3 CD-ROM into the CD-ROM drive on the node.
Install the Sun Cluster 3.1 4/04 data-service–update patches.
Use one of the following methods:
To upgrade one or more specified data services, type the following command.
# scinstall -u update -s srvc[,srvc,…] -d cdrom-image |
Upgrades a cluster node to a later Sun Cluster software release
Upgrades the specified data service
Specifies an alternate directory location for the CD-ROM image
To upgrade all data services present on the node, type the following command.
# scinstall -u update -s all -d cdrom-image |
Upgrades all data services
This command assumes that updates for all installed data services exist on the update release. If an update for a particular data service does not exist in the update release, that data service is not upgraded.
Upgrade processing is finished when the system displays the message Completed upgrade of Sun Cluster data services agents and the path to the upgrade log.
Change to the CD-ROM root directory and eject the CD-ROM.
Install any Sun Cluster 3.1 4/04 data-service software patches.
Verify that each data-service update patch is installed successfully.
View the upgrade log file that is referenced at the end of the upgrade output messages.
Reboot the node into the cluster.
# reboot |
Run the following command on the upgraded node to verify that Sun Cluster 3.1 4/04 software is installed successfully.
# scinstall -pv |
From any node, verify the status of the cluster configuration.
% scstat % scrgadm -pv[v] |
Output should be the same as for Step 4 in How to Prepare the Cluster for Upgrade (Rolling).
Do you have another node to upgrade?
If yes, return to How to Prepare the Cluster for Upgrade (Rolling) and repeat all upgrade procedures on the next node to upgrade.
If no, go to How to Finish Upgrading to Sun Cluster 3.1 4/04 Software (Rolling).
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
Does your configuration use dual-string mediators for Solstice DiskSuite/Solaris Volume Manager?
If no, proceed to Step 3.
If yes, restore the mediator configurations.
Determine which node has ownership of a diskset to which you will add the mediator hosts.
# metaset -s setname |
Specifies the diskset name
If no node has ownership, take ownership of the diskset.
# metaset -s setname -t |
Takes ownership of the diskset
Recreate the mediators.
# metaset -s setname -a -m mediator-host-list |
Adds to the diskset
Specifies the names of the nodes to add as mediator hosts for the diskset
Repeat Step a through Step c for each diskset in the cluster that uses mediators.
Are you using Sun Management Center to monitor your Sun Cluster configuration?
If no, proceed to Step 4.
If yes, perform the following steps to upgrade the Sun Cluster-module software on the Sun Management Center server machine, help-server machine, and console machine.
Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.
If you intend to upgrade the Sun Management Center software itself, do not perform this step. Instead, proceed to Step 4 to finish Sun Cluster software upgrade. Then go to How to Upgrade Sun Management Center Software to upgrade Sun Management Center software and the Sun Cluster module.
As superuser, remove the existing Sun Cluster–module packages.
Use the pkgrm(1M) command to remove all Sun Cluster–module packages from all locations listed in the following table.
# pkgrm module-package |
Location |
Module Package to Remove |
---|---|
Sun Management Center console machine |
SUNWscscn |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center help-server machine |
SUNWscshl |
Sun Cluster-module software on the cluster nodes was already upgraded during the cluster-framework upgrade.
As superuser, reinstall Sun Cluster–module packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to the locations listed in the following table.
In the CD-ROM path, the value for ver is 8 (for Solaris 8) or 9 (for Solaris 9).
# cd Solaris_sparc/Product/sun_cluster/Solaris_ver/Packages/ # pkgadd -d . module-package |
Location |
Module Package to Install |
---|---|
Sun Management Center console machine |
SUNWscshl |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center help-server machine |
SUNWscshl |
You install the help-server package SUNWscshl on both the console machine and the help-server machine. You do not upgrade to a new SUNWscscn package on the console machine.
If you upgraded any data services that are not supplied on the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM or the Java Enterprise System Accessory CD 3 CD-ROM, register the new resource types for those data services.
Follow the documentation that comes with the data services.
From any node, start the scsetup(1M) utility.
# scsetup |
Register the new resource types.
Migrate all eligible resources to the new version of its resource type.
From the Resource Group menu, choose Change properties of a resource
.
Choose Manage resource versioning
.
Choose Show versioning status
.
The scsetup utility displays all resources for which a new version of its resource type was installed during the upgrade. Make note of which new resource types you will upgrade the resources to.
Choose Re-version all eligible resources
.
Follow the prompts to upgrade eligible resources to the new version of its resource type.
Return to the Change properties of a resource menu.
Modify extension properties for new resource type versions.
For each new resource type that you migrated existing resources to, determine whether the new resource type requires additional modifications to its extension properties.
Refer to each related data service manual for the requirements of each new resource type.
You do not need to change the Type_version property of a new resource type. That property was modified when you migrated resources to their new resource types in Step 7.
From the Change properties of a resource menu, choose Change extension resource properties
.
Follow the prompts to modify the necessary extension properties.
Refer to your data service documentation for the names of extension properties and values to modify.
Repeat for each resource type that requires modifications.
Return to the Resource Groups menu.
Re-enable all disabled resources.
From the Resource Group Menu, choose Enable/Disable a resource
.
Choose a resource to enable and follow the prompts.
Repeat Step b for each disabled resource.
When all resources are re-enabled, type q to return to the Resource Group Menu.
Bring each resource group back online.
When all resource groups are back online, exit the scsetup utility.
Type q to back out of each submenu, or press Ctrl-C.
The cluster upgrade is complete. You can now return the cluster to production.
Restart any applications.
Follow the instructions that are provided in your third-party documentation.
The cluster upgrade is complete.
This section provides the following repair procedures to follow if changes were inadvertently made to the storage configuration during upgrade:
Any changes to the storage topology, including running Sun Cluster commands, should be completed before you upgrade the cluster to Solaris 9 software. If, however, changes were made to the storage topology during the upgrade, perform the following procedure. This procedure ensures that the new storage configuration is correct and that existing storage that was not reconfigured is not mistakenly altered.
Ensure that the storage topology is correct.
Check whether the devices that were flagged as possibly being replaced map to devices that actually were replaced. If the devices were not replaced, check for and correct possible accidental configuration changes, such as incorrect cabling.
Become superuser on a node that is attached to the unverified device.
Manually update the unverified device.
# scdidadm -R device |
Performs repair procedures on the specified device
See the scdidadm(1M) man page for more information.
Update the DID driver.
# scdidadm -ui # scdidadm -r |
Loads the device ID configuration table into the kernel
Initializes the DID driver
Reconfigures the database
Repeat Step 2 through Step 4 on all other nodes that are attached to the unverified device.
Return to the remaining upgrade tasks.
For nonrolling upgrade, go to Step 11 in How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).
For rolling upgrade, go to Step 12 in How to Prepare the Cluster for Upgrade (Rolling).
If accidental changes are made to the storage cabling during the upgrade, perform the following procedure to change the storage configuration back to the correct state.
This procedure assumes that no physical storage was actually changed. If physical or logical storage devices were changed or replaced, instead follow procedures in How to Handle Storage Reconfiguration During an Upgrade.
Change the storage topology back to its original configuration.
Check the configuration of the devices that were flagged as possibly being replaced, including the cabling.
As superuser, update the DID driver on each node of the cluster.
# scdidadm -ui # scdidadm -r |
Loads the device–ID configuration table into the kernel
Initializes the DID driver
Reconfigures the database
See the scdidadm(1M) man page for more information.
Did the scdidadm command return any error messages in Step 2?
Return to the remaining upgrade tasks.
For nonrolling upgrade, go to Step 11 in How to Upgrade to Sun Cluster 3.1 4/04 Software (Nonrolling).
For rolling upgrade, go to Step 12 in How to Prepare the Cluster for Upgrade (Rolling).
This section describes how to upgrade from Sun Management Center 2.1.1 to either Sun Management Center 3.0 software or Sun Management Center 3.5 software on a Sun Cluster 3.1 4/04 configuration.
Have available the following items:
Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM or the path to the CD-ROM image. You use the CD-ROM to reinstall the Sun Cluster 3.1 4/04 version of the Sun Cluster–module packages after you upgrade Sun Management Center software.
Sun Management Center documentation.
Sun Management Center patches and Sun Cluster–module patches, if any.
See “Patches and Required Firmware Levels” in Sun Cluster 3.1 Release Notes for the location of patches and installation instructions.
Stop any Sun Management Center processes.
If the Sun Management Center console is running, exit the console.
In the console window, choose File⇒Exit from the menu bar.
On each Sun Management Center agent machine (cluster node), stop the Sun Management Center agent process.
# /opt/SUNWsymon/sbin/es-stop -a |
On the Sun Management Center server machine, stop the Sun Management Center server process.
# /opt/SUNWsymon/sbin/es-stop -S |
As superuser, remove Sun Cluster–module packages.
Use the pkgrm(1M) command to remove all Sun Cluster–module packages from all locations listed in the following table.
# pkgrm module-package |
Location |
Module Package to Remove |
---|---|
Each cluster node |
SUNWscsam, SUNWscsal |
Sun Management Center console machine |
SUNWscscn |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center help-server machine |
SUNWscshl |
If you do not remove the listed packages, the Sun Management Center software upgrade might fail because of package dependency problems. You reinstall these packages in Step 5, after you upgrade Sun Management Center software.
Upgrade the Sun Management Center software.
Follow the upgrade procedures in your Sun Management Center documentation.
As superuser, reinstall Sun Cluster–module packages from the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM to the locations listed in the table below.
In the CD-ROM path, the value of ver is 8 (for Solaris 8) or 9 (for Solaris 9)
# cd Solaris_sparc/Product/sun_cluster/Solaris_ver/Packages/ # pkgadd -d . module-package |
Location |
Module Package to Install |
---|---|
Each cluster node |
SUNWscsam, SUNWscsal |
Sun Management Center server machine |
SUNWscssv |
Sun Management Center console machine |
SUNWscshl |
Sun Management Center help-server machine |
SUNWscshl |
You install the help-server package SUNWscshl on both the console machine and the help-server machine.
Apply any Sun Management Center patches and any Sun Cluster–module patches to each node of the cluster.
Restart Sun Management Center agent, server, and console processes.
Follow procedures in SPARC: How to Start Sun Management Center.
Load the Sun Cluster module.
Follow procedures in SPARC: How to Load the Sun Cluster Module.
If the Sun Cluster module was previously loaded, unload the module and then reload it to clear all cached alarm definitions on the server. To unload the module, choose Module⇒Unload Module from the console's Details window.