Perform this procedure to verify that the cluster is successfully upgraded to Sun Cluster Geographic Edition 3.2 software. On the Solaris 10 OS, perform all steps from the global zone only.
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
Become superuser on each node.
# geoadm -V
The last line of output states which version of Sun Cluster Geographic Edition software the node is running. This version should match the version to which you just upgraded.
The version number that the geoadm -v command returns does not coincide with the marketing release version numbers. The version number for Sun Cluster Geographic Edition 3.2 software should be 1.2.
# geoadm status
# geopg switchover remotecluster protectiongroup
You must test your geographically separated cluster properly, so that no problems prevent a switchover. Upgrading the secondary cluster first and switching over to it enables you to verify that switchover still works. If the switchover fails, the primary site is untouched and you can switch back. If switchover works on the secondary site, then after a certain 'soak time' you can upgrade the primary site as well.
A switchover might interrupt the services that are running on the cluster. You should carefully plan the required tasks and resources before you perform a switchover.
If you have added your application resource groups back into the protection groups, performing a switchover shuts down the applications on the original primary cluster and migrates the applications to the secondary cluster.