Perform this procedure on each cluster node where you want Geographic Edition software to run. Upgrade or update the secondary cluster before you upgrade the primary cluster, to permit testing. You can perform this procedure on more than one node at the same time.
Caution - The cluster in a partnership with the cluster you are upgrading or updating must also be installed with Geographic Edition 4.1 or 4.2 software before you can restart the Geographic Edition 4.2 infrastructure on the upgraded or updated cluster. |
Before You Begin
Ensure that the cluster is prepared for upgrade or software update. See How to Prepare the Cluster for an Upgrade or Software Update.
If you are upgrading or updating a zone cluster, log in to a node of the zone cluster.
# pkg set-publisher -G '*' -g URL_for_ha-cluster_publisher ha-cluster
# pkg publisher PUBLISHER TYPE STATUS P LOCATION solaris origin online F solaris-repository
For information about setting the solaris publisher, see Adding, Modifying, or Removing Package Publishers in Adding and Updating Software in Oracle Solaris 11.2 .
% cluster status
See the cluster (1CL) man page for more information.
# pkg update ha-cluster-geo-incorporation
Ensure that Geographic Edition software upgrade is completed on all cluster nodes before you continue to the next step.
# geoadm -V
Do not start the Geographic Edition software until all cluster nodes in the partnership are installed with a supported version of Geographic Edition software. Then proceed to Step 8 of this procedure.
Perform this step on each node of the global cluster or zone cluster that you are configuring with Geographic Edition software.
# /usr/sbin/cacaoadm start
# geoadm start
# geopg add-resource-group resource-group protection-group
See the geopg (1M) man page for more information.
# geopg start protection-group -e local [-n]
See the geopg (1M) man page for more information.
Troubleshooting
If, after upgrade, you experience problems with certificates between the cluster nodes, update the public keys on both partner clusters.
1. On each node in the local cluster, remove the public keys.
localnode# geops remove-trust -c remote-cluster
2. On each node in the remote cluster, remove the public keys.
remotenode# geops remove-trust -c local-cluster
3. On one node of the local cluster, import the public keys from the remote cluster.
localnode# geops add-trust -c remote-cluster
4. On one node of the remote cluster, import the public keys from the local cluster.
remotenode# geops add-trust -c local-cluster
5. On each node of each cluster, verify trust.
# geops verify-trust -c partner-cluster
Next Steps
Go to How to Verify Upgrade or Update of Geographic Edition Software.