applysoftware
Use the applysoftware command to update the clustered system (system) to a new level of system code (code).
Syntax
>>- applysoftware -- --+----------+-- --------------------------> '- -force -' >--+- -file -- filename_arg --+------------+-+-- -- -- -------->< | '- -prepare -' | +- -abort --------------------------------+ +- -complete --+----------+---------------+ | '- -paced -' | +- -resume --+----------+-----------------+ | '- -paced -' | '- -pacednext ----------------------------'
Parameters
- -force
- (Optional) Specifies that the
update or abort should 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 your product support information.
- -file filename_arg
- (Required) Specifies the filename of the installation
update package. Copy the
update package onto the
configuration node before running the applysoftware command.Note: The file parameter cannot be used with the abort parameter.
- -prepare
- (Optional) Prepares the system for a manual code level
update. Note: You can:
- Use the prepare parameter with the file parameter
- Not use the prepare parameter with the abort parameter
- Not use the force parameter with the prepare parameter to go to prepared status
- -abort
- (Required for stopping an
update) Specifies that a stalled or
prepared update should be stopped,
returning the system to the original code level. Note: The abort parameter can be used with the force parameter, but not the file or prepare parameters.The abort parameter can also be used when the lsupdate command reports a status of:
- prepare_failed
- prepared (if all nodes are online)
- -complete
- (Optional) Start the update completion process. This is either automatic if the paced option is not set or paced if the paced option is set.
- -resume
- (Optional) Resumes a stalled automatic update, update cancel, or update completion process by retrying the step that stalled. The update completion process becomes paced (if that option is set).
- -paced
- (Optional) Specifies that the update completion should be paced. The system does not automatically take any nodes offline and waits for the user to use -pacednext.
- -pacednext
- (Optional) Updates the next node that is part of a paced update.
Description
This command starts the update process of the system to a new level of code. The applysoftware command applies a level of code to the node as a service action (Paced update) to update the specific node, or as an automatic update process that update all of the nodes on a system.
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 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.
- The given package fails an integrity check due to corruption.
- Any node in the system has a hardware type 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 any volumes that are dependent on the status of a node.Note: The force parameter can be used to override this 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.
The actual update completes asynchronously.
An invocation example
applysoftware –file filename_argThe resulting output:
No feedbackAn invocation example
applysoftware -prepare -file INSTALL_6.4.0.0The resulting output:
No feedbackAn invocation example
applysoftware -abortThe resulting output:
No feedbackAn invocation example
applysoftware -file softwareupdateThe resulting output:
No feedbackAn invocation example
applysoftware -complete -forceThe resulting output:
No feedbackAn invocation example
applysoftware -resume -pacedThe resulting output:
No feedbackAn invocation example
applysoftware -pacednext -forceThe resulting output:
No feedback