Sun Cluster Software Installation Guide for Solaris OS

ProcedureHow to Verify Upgrade of Sun Cluster 3.2 Software

Perform this procedure to verify that the cluster is successfully upgraded to Sun Cluster 3.2 software. On the Solaris 10 OS, perform all steps from the global zone only.

Note –

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands, in Sun Cluster System Administration Guide for Solaris OS.

Before You Begin

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

  1. On each node, become superuser.

  2. On each upgraded node, view the installed levels of Sun Cluster software.

    phys-schost# clnode show-rev -v

    The first line of output states which version of Sun Cluster software the node is running. This version should match the version that you just upgraded to.

  3. From any node, verify that all upgraded cluster nodes are running in cluster mode (Online).

    phys-schost# clnode status

    See the clnode(1CL) man page for more information about displaying cluster status.

  4. SPARC: If you upgraded from Solaris 8 to Solaris 9 software, verify the consistency of the storage configuration.

    1. On each node, run the following command to verify the consistency of the storage configuration.

      phys-schost# cldevice check

      Caution – Caution –

      Do not proceed to Step b until your configuration passes this consistency check. Failure to pass this check might result in errors in device identification and cause data corruption.

      The following table lists the possible output from the cldevice check command and the action you must take, if any.

      Example Message 


      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 an Incomplete Upgrade and perform the appropriate repair procedure.

      device id for 'phys-schost-1:/dev/rdsk/c0t0d0' needs to be updated, run cldevice repair to update

      None. You update this device ID in Step b.

      No output message 


      See the cldevice(1CL) man page for more information.

    2. On each node, migrate the Sun Cluster storage database to Solaris 9 device IDs.

      phys-schost# cldevice repair
    3. On each node, run the following command to verify that storage database migration to Solaris 9 device IDs is successful.

      phys-schost# cldevice check
      • If the cldevice command displays a message, return to Step a to make further corrections to the storage configuration or the storage database.

      • If the cldevice command displays no messages, the device-ID migration is successful. When device-ID migration is verified on all cluster nodes, proceed to How to Finish Upgrade to Sun Cluster 3.2 Software.

Example 8–2 Verifying Upgrade to Sun Cluster 3.2 Software

The following example shows the commands used to verify upgrade of a two-node cluster to Sun Cluster 3.2 software. The cluster node names are phys-schost-1 and phys-schost-2.

phys-schost# clnode show-rev -v
phys-schost# clnode status
=== Cluster Nodes ===

--- Node Status ---

Node Name                                          Status
---------                                          ------
phys-schost-1                                      Online
phys-schost-2                                      Online

Next Steps

Go to How to Finish Upgrade to Sun Cluster 3.2 Software.