applysoftware

Use the applysoftware command to update the system to a new level of code or install a patch on the system.

Syntax

Syntax to start and manage an automatic code level update

Read syntax diagramSkip visual syntax diagram applysoftware -filecode_package-purgepatches-abort-resume-pause-all-delayminutes-force-continue

Syntax to start a manual code level update

Read syntax diagramSkip visual syntax diagram applysoftware -filecode_package-prepare-purgepatches

Syntax to install a patch

Read syntax diagramSkip visual syntax diagram applysoftware-filepatch_name

Parameters

-file code_package
(Required) Specifies the file name of the installation update package. Copy the update package onto the configuration node before you run the applysoftware command.
Note:
  • Do not to specify a path if you use this parameter.
-purgepatches
When a code package is installed on a system, all the existing patches are reapplied. When you specify the -purgepatches parameter, all the existing patches on the node are removed.
-pause
(Optional) Specifies that the upgrade of a system is paused at the halfway point. This parameter must be specified with -file or -resume.
-all
(Optional) Specifies that the upgrade of a system is paused before each node goes offline for upgrade. This parameter must be specified with -pause, and -file or -resume.
-prepare
(Optional) Prepares the system for a manual code level update.
-delay minutes
(Optional) Specifies that you can overwrite the default 10-minutes delay at the half way point of a software update. This parameter must not be specified with the -pause.
-abort
(Required for stopping an update) Specifies that a stalled or prepared update is stopped, returning the system to the original code level.
The abort parameter can also be used when the lsupdate command reports a status of:
  • prepare_failed
  • prepared (if all nodes are online)
-resume
(Required for resuming an update) Resumes a stalled automatic update, update cancel, or update completion process by retrying the step that stalled.
-enclosure enclosure_id
(Optional) Specifies the enclosure to which to apply the software updates.
-force
(Optional) Specifies that the update or abort must proceed even if there is a lack of redundancy in the system. Disabling redundancy checking might cause loss of data, or loss of access to data. Use the force parameter with the abort parameter if one or more nodes are offline.
Important: Using the force parameter might result in a loss of access. Use it only under the direction of IBM® support personnel.
-continue
(Optional) Specifies that the concurrent upgrade continue.
patch_name

Specifies the name of the patch file that is uploaded on the configuration node.

Description

Note: The latest software upgrade test utility must be run before upgrading the software. To know more about this test, refer to Software Upgrade Test Utility.

The applysoftware command applies a new level of software or patches to the system. The command initiates the process that starts the installation of updated version and continues to the next stage of the upgrade that is automatic but pauses between nodes.

The applysoftware command cannot be used in service state, which means the system must be running for the command to be used and be successful. This command is synchronous and therefore reports success or failure. The actual update completes asynchronously.

The code package as specified by the file name must first be copied onto the current configuration node in the /home/admin/update directory; use the PuTTy secure copy (scp) application to copy the file.

If the applysoftware command is successful, the lsupdate command reports the status is prepared. If the applysoftware command fails, the lsupdate command reports the status is inactive.

If specified, the prepare parameter must succeed in order to successfully update. It is recommended to use the same package for the prepare as the actual update. The prepare parameter can be canceled by using the abort parameter (even after the system is prepared) as long as the lsupdate command reports the status as prepared.
Important: The prepare parameter might timeout. If a timeout occurs, the prepare parameter causes an asynchronous condition, and the lsupdate command reports the prepare status as preparing. If such scenario, wait until lsupdate reports the update as prepared before you proceed with the manual update process.
The command completes when the update process is successful. The command fails and the update package is deleted if:
  • The specified package fails an integrity check due to corruption.
  • Any node in the system has a hardware type that is not supported by the new code.
  • The new code level does not support updates from the currently installed code.
  • The code level of a remote system is incompatible with the new code.
  • There are volumes that are dependent on the status of a node.
    Note: The force parameter can be used to override these scenarios if you are prepared to lose access to data during the update. Before proceeding, use the lsdependentvdisks command with the node parameter to list the node-dependent volumes at the time the command is run. If the command returns an error, move the quorum disks to MDisks that are accessible through all nodes. Rerun the command until the errors stop.

You can use the lsdumps -prefix /home/admin/update command to view the contents of the /home/admin/update directory.

An invocation example

The following command initiates an upgrade that runs to completion with no user intervention. The upgrade pauses for 10 minutes at the halfway point.

applysoftware -file INSTALL_6.4.0.0

The resulting output:

No feedback.