How to Commit the Upgraded Cluster to Sun Cluster 3.2 11/09 Software

Before You Begin

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

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

   phys-schost# scversions

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

   Output Message	Action
   Upgrade commit is needed.	Proceed to Step 3.
   Upgrade commit is NOT needed. All versions match.	Go to How to Verify Upgrade of Sun Cluster 3.2 11/09 Software.
   Upgrade commit cannot be performed until all cluster nodes are upgraded. Please run scinstall(1m) on cluster nodes to identify older versions.	Return to the Sun Cluster upgrade procedures that you used and 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 the Sun Cluster upgrade procedures that you used and upgrade the remaining cluster nodes.

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

   phys-schost# 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.

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

   phys-schost# scversions Upgrade commit is NOT needed. All versions match.

Next Steps

Go to How to Verify Upgrade of Sun Cluster 3.2 11/09 Software.