Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Upgrade Guide Oracle Solaris Cluster 4.0 |
1. Preparing to Upgrade Oracle Solaris Cluster Software
2. Upgrading Zones Managed by HA for Oracle Solaris Zones
3. Performing a Standard Upgrade
4. Performing a Rolling Upgrade
Before You Begin
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
phys-schost# scversions
|
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.
phys-schost# scversions Upgrade commit is NOT needed. All versions match.
Next Steps
Go to How to Verify the Upgrade.
Perform this procedure to verify that the cluster is successfully upgraded to Oracle Solaris Cluster 4.0 software. Perform all steps from the global zone only.
Before You Begin
Ensure that all upgrade procedures are completed for all cluster nodes that you are upgrading.
Ensure that all steps in How to Commit the Upgraded Cluster are completed successfully.
phys-schost# clnode show-rev -v
The first line of output states which version of Oracle Solaris Cluster software the node is running. This version should match the version that you just upgraded to.
phys-schost# clnode status
See the clnode(1CL) man page for more information about displaying cluster status.
Example 5-1 Verifying Upgrade to Oracle Solaris Cluster 4.0 Software
The following example shows the commands used to verify upgrade of a two-node cluster to Oracle Solaris Cluster 4.0 software. The cluster node names are phys-schost-1 and phys-schost-2.
phys-schost# clnode show-rev -v 4.0 … 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 the Upgrade.
Perform this procedure to finish Oracle Solaris Cluster upgrade. Perform all steps from the global zone only.
Before You Begin
Ensure that all steps in How to Verify the Upgrade are completed.
This step ensures that security files for the common agent container are identical on all cluster nodes and that the copied files retain the correct file permissions.
phys-schost# /usr/sbin/cacaoadm stop
phys-schost-1# cd /etc/cacao/instances/default/
phys-schost-1# tar cf /tmp/SECURITY.tar security
Any security files that already exist in the /etc/cacao/instances/default/ directory are overwritten.
phys-schost-2# cd /etc/cacao/instances/default/ phys-schost-2# tar xf /tmp/SECURITY.tar
You must delete each copy of the tar file to avoid security risks.
phys-schost-1# rm /tmp/SECURITY.tar phys-schost-2# rm /tmp/SECURITY.tar
If you did not upgrade the Oracle Solaris software, omit this step.
During Oracle Solaris OS upgrade, the default restricted network profile is applied, which disables external access for certain network services. This includes the RPC communication service, which is required for cluster communication.
The following steps check whether external access to these services are available and, if necessary, restore the Oracle Solaris functionality.
External access is available if the output of the following command shows that the local_only property is set to false.
phys-schost# svcprop network/rpc/bind:default | grep local_only
If external access is enabled, skip to Step 3. Otherwise, continue to Step b
phys-schost# svccfg svc:> select network/rpc/bind svc:/network/rpc/bind> setprop config/local_only=false svc:/network/rpc/bind> quit phys-schost# svcadm refresh network/rpc/bind:default
phys-schost# /usr/sbin/cacaoadm start
Follow the documentation that accompanies the data services.
phys-schost# metaset -s setname
Specifies the disk set name.
phys-schost# cldevicegroup switch -n node devicegroup
Specifies the name of the node to become primary of the disk set.
Specifies the name of the disk set.
phys-schost# metaset -s setname -a -m mediator-host-list
Adds to the disk set.
Specifies the names of the nodes to add as mediator hosts for the disk set.
You must migrate all resources to the Oracle Solaris Cluster 4.0 resource-type version to use the new features and bug fixes that are provided in this release.
See Upgrading a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide, which contains procedures which use the command line. Alternatively, you can perform the same tasks by using the Resource Group menu of the clsetup utility. The process involves performing the following tasks:
Registering the new resource type.
Migrating the eligible resource to the new version of its resource type.
Modifying the extension properties of the resource type.
Note - The Oracle Solaris Cluster 4.0 release might introduce new default values for some extension properties. These changes affect the behavior of any existing resource that uses the default values of such properties. If you require the previous default value for a resource, modify the migrated resource to set the property to the previous default value.
The following example shows the httpd.conf file located on the /global cluster file system.
phys-schost# cat /usr/apache/bin/apchectl | grep HTTPD=/usr HTTPD="/usr/apache/bin/httpd -f /global/web/conf/httpd.conf"
phys-schost# vi /usr/apache/bin/apchectl #HTTPD=/usr/apache/bin/httpd HTTPD="/usr/apache/bin/httpd -f /global/web/conf/httpd.conf"
phys-schost# clsetup
The clsetup Main Menu is displayed.
The Resource Group Menu is displayed.
This step includes the bringing online of resource groups in non-global zones.
Type q to back out of each submenu, or press Ctrl-C.
Also perform this task if you want to configure automatic reboot for the first time.
phys-schost# clnode show
phys-schost# clnode set -p reboot_on_path_failure=enabled
Specifies the property to set
Specifies that the node will reboot if all monitored disk paths fail, provided that at least one of the disks is accessible from a different node in the cluster.
phys-schost# clnode show === Cluster Nodes === Node Name: node … reboot_on_path_failure: enabled …
See How to Validate the Cluster in Oracle Solaris Cluster Software Installation Guide.
phys-schost# prtvtoc /dev/rdsk/cNtXdYsZ > filename
Store the file in a location outside the cluster. If you make any disk configuration changes, run this command again to capture the changed configuration. If a disk fails and needs replacement, you can use this information to restore the disk partition configuration. For more information, see the prtvtoc(1M) man page.
An archived backup of your cluster configuration facilitates easier recovery of your cluster configuration.
For more information, see How to Back Up the Cluster Configuration in Oracle Solaris Cluster System Administration Guide.
Troubleshooting
Resource-type migration failure - Normally, you migrate resources to a new resource type while the resource is offline. However, some resources need to be online for a resource-type migration to succeed. If resource-type migration fails for this reason, error messages similar to the following are displayed:
phys-schost - Resource depends on a SUNW.HAStoragePlus type resource that is not online anywhere. (C189917) VALIDATE on resource nfsrs, resource group rg, exited with non-zero exit status. (C720144) Validation of resource nfsrs in resource group rg on node phys-schost failed.
If resource-type migration fails because the resource is offline, use the clsetup utility to re-enable the resource and then bring its related resource group online. Then repeat migration procedures for the resource.
Java binaries location change - If the location of the Java binaries changed during the upgrade of Oracle Solaris software, you might see error messages similar to the following when you attempt to run the cacaoadm start command:
phys-schost# /usr/sbin/cacaoadm startNo suitable Java runtime found. Java 1.5.0_06 or higher is required.Jan 3 17:10:26 ppups3 cacao: No suitable Java runtime found. Java 1.5.0_06 or higher is required.Cannot locate all the dependencies
This error is generated because the start command cannot locate the current location of the Java binaries. The JAVA_HOME property still points to the directory where the previous version of Java was located, but that previous version was removed during upgrade.
To correct this problem, change the setting of JAVA_HOME in the following configuration file to use the current Java directory:
/etc/opt/SUNWcacao/cacao.properties
Next Steps
The cluster upgrade is complete.