applysoftware
Use the applysoftware command to update the system to a new level of code.
Syntax to start and manage an automatic code level update
Syntax to start a manual code level update
Parameters
- -file filename_arg
- (Required) Specifies the file name of the installation update package. Copy the update package onto the configuration node before you run the applysoftware command.
- -pause
- (Optional) Specifies that the concurrent upgrade of a node is paused at the halfway point. This parameter must be specified with -file.
- -all
- (Optional) Specifies that the concurrent upgrade of a node is paused before the node is offline for an upgrade. This parameter must be specified with -file.
- -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 parameter.
- -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.
- -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.
Description
The applysoftware command applies a new level of software to the system. The command initiates the process that starts the installation of updated version and continues to the next stage of the upgrade which is automatic but pauses between nodes.
The applysoftware command cannot be used in service state, which means the system must be running in order 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.
preparing
. If
this happens, wait until lsupdate reports the update as prepared before you
proceed with the manual update process.- 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-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 no errors are returned.
An invocation example
applysoftware -file INSTALL_6.4.0.0
The resulting output:
No feedback.
An invocation example
applysoftware -abort
The resulting output:
No feedback.
An invocation example
applysoftware -file INSTALL_6.4.0.0 -pause
The resulting output:
No feedback.
An invocation example
applysoftware -continue
The resulting output:
No feedback.