How to Finish a Rolling Upgrade to Sun Cluster 3.1 9/04 Software

1. Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.

2. From one node, check the upgrade status of the cluster.

   # scversions

3. From the following table, perform the action that is listed for the output message from Step 2.

   Output Message	Action
   Upgrade commit is needed.	Go to Step 4.
   Upgrade commit is NOT needed. All versions match.	Skip to Step 6.
   Upgrade commit cannot be performed until all cluster nodes are upgraded. Please run scinstall(1m) on cluster nodes to identify older versions.	Return to How to Perform a Rolling Upgrade of Sun Cluster 3.1 9/04 Software to upgrade the remaining cluster nodes.
   Check upgrade cannot be performed until all cluster nodes are upgraded. Please run scinstall(1m) on cluster nodes to identify older versions.	Return to How to Perform a Rolling Upgrade of Sun Cluster 3.1 9/04 Software to upgrade the remaining cluster nodes.

4. After all nodes have rejoined the cluster, from one node commit the cluster to the upgrade.

   # scversions -c

   Committing the upgrade enables the cluster to utilize all features in the newer software. New features are available only after you perform the upgrade commitment.

5. From one node, verify that the cluster upgrade commitment has succeeded.

   # scversions Upgrade commit is NOT needed. All versions match.

6. If your configuration uses dual-string mediators for Solstice DiskSuite or Solaris Volume Manager software, restore the mediator configurations.

   1. Determine which node has ownership of a disk set to which you are adding the mediator hosts.

      # metaset -s setname

      -s setname

      Specifies the disk-set name

   2. If no node has ownership, take ownership of the disk set.

      # metaset -s setname -t

      -t

      Takes ownership of the disk set

   3. Re-create the mediators.

      # metaset -s setname -a -m mediator-host-list

      -a

      Adds to the disk set

      -m mediator-host-list

      Specifies the names of the nodes to add as mediator hosts for the disk set

   4. Repeat Step a through Step c for each disk set in the cluster that uses mediators.

7. If you upgraded any data services that are not supplied on the Sun Cluster 3.1 9/04 Agents CD-ROM, register the new resource types for those data services.

   Follow the documentation that accompanies the data services.

8. (Optional) Switch each resource group and device group back its original node.

   # scswitch -z -g resource-group -h node # scswitch -z -D disk-device-group -h node

   -z

   Performs the switch

   -g resource-group

   Specifies the resource group to switch

   -h node

   Specifies the name of the node to switch to

   -D disk-device-group

   Specifies the device group to switch

9. Restart any applications.

   Follow the instructions that are provided in your vendor documentation.

10. (Optional) Migrate resources to new resource type versions.

    See “Upgrading a Resource Type” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS, which contains procedures which use the command line. Alternatively, you can perform the same tasks by using the Resource Group menu of the scsetup utility. The process involves performing the following tasks:

    • Register the new resource type.

    • Migrate the eligible resource to the new version of its resource type.

    • Modify the extension properties of the resource type as specified in the manual for the related data service.

11. If you have a SPARC based system and use Sun Management Center to monitor the cluster, go to SPARC: How to Upgrade Sun Cluster-Module Software for Sun Management Center.

The cluster upgrade is complete.