Upgrade PowerHA SystemMirror using the cl_ezupdate command

You can use the cl_ezupdate command to update the software for the entire cluster or a subset of nodes in the cluster, often without disrupting workloads.

Some updates require a system reboot after the update is installed. If you install an update that requires a reboot, you must plan to move any active workloads to a different node that is not being updated.

You must run the cl_ezupdate command from one of the nodes that is part of the cluster. When you run the cl_ezupdate command, you must specify the location of the update images or an interim fix that you want to install. The location of the update images or interim fix can be either be a file system directory or a Network Installation Management (NIM) lpp_source resource that is located on a NIM server. The cl_ezupdate command does not setup or configure the NIM environment. For more information about setting up NIM, see Network Installation Management.

You can complete the following tasks by using the cl_ezupdate command:
  • Query information about the cluster, nodes, NIM server, or service packs and interim fixes that are located in a specified installation location. The query can be run on the entire cluster or on a specific subset of nodes in the cluster.
  • Apply and reject updates for AIX® service packs or interim fixes. The cl_ezupdate command cannot be used to update the cluster to newer AIX technology levels.
  • Apply and reject updates for PowerHA SystemMirror service packs and technology levels, and interim fixes located in a specified installation location. This process is performed on the entire cluster or on a specific subset of nodes in the cluster. You can also apply updates in preview mode. When you use preview mode, all the prerequisites for installation process are checked, but the cluster updates are not installed on the system.
  • Reject AIX service packs, PowerHA service packs, and interim fixes that were already installed on the system. This task is performed on the entire cluster or on a specific subset of cluster nodes.

Limitations

The following are limitations and restrictions for cl_ezupdate command:
  • If you have previously installed any interim fixes, those fixes might be overwritten or removed when you apply a new service pack. If the previously installed interim fix has locked the fileset, you can override that lock and install the service page by using the -F flag.
  • You cannot install a new PowerHA SystemMirror technology level (TL) in the applied state. Filesets installed as part of new TL are automatically moved into committed state. This means that the installation image cannot be rejected. The cl_ezupdate tool cannot be used to uninstall technology levels.
  • If you want to update the software by using a NIM resource, the NIM client must be configured first and must be available to all nodes where you want to use the cl_ezupdate tool.
  • The cl_ezupdate tool requires an existing PowerHA SystemMirror and Cluster Aware AIX (CAA) cluster definition.
  • The Cluster Communications daemon (clcomd) must be enabled to communicate with all nodes in the cluster. The cl_ezupdate tool attempts to verify clcomd communications before installing any updates.
  • If a cluster node update operation fails, the cl_ezupdate script ends immediately and exits with an error. To troubleshoot the issue, an administrator must restart the update operation or undo the completed update operations.
  • You must place any interim fixes in the emgr/ppc directory of the NIM lpp_source resource.
  • The cl_ezupdate tool runs only on AIX version 7, or later.
  • The cl_ezupdate tool can be used only on PowerHA SystemMirror 7.1.3, or later.
  • The cl_ezupdate tool cannot be used with the AIX multibos utility.
  • If you are running the cl_ezupdate tool on a cluster node that is not included as an option of the –N flag and if the –S flag specifies the file system path as an option, the cluster node on which you are running the command is the source node for install image propagation. This cluster node must have the file system path specified in the –S option.