Use the lsupdate command to display a system's machine code (code)
upgrade status.
Syntax
lsupdate [ -nohdr ] [ -delimdelimiter ]
Parameters
- -nohdr
- (Optional) By default, headings are displayed for each column of data in a concise style
view, and for each item of data in a detailed style view. The -nohdr
parameter suppresses the display of these headings.
Note: If there is no data to be displayed,
headings are not displayed.
- -delim delimiter
- (Optional) By default in a concise view, all columns of data are space-separated. The
width of each column is set to the maximum width of each item of data. In a detailed view,
each item of data has its own row, and if the headers are displayed, the data is separated
from the header by a space. The -delim parameter overrides this
behavior. Valid input for the -delim parameter is a 1-byte character. If
you enter -delim : on the command line, the colon character
(:) separates all items of data in a concise view; for example, the spacing
of columns does not occur. In a detailed view, the data is separated from its header by the
specified delimiter.
Description
The
applysoftware command is used to update the system code. The following
are the upgrade status states reported by the
lsupdate command:
- status
- Indicates the overall update-related status of the system. The values are:
- success, which indicates that all updating activity is complete.
- system_preparing, which indicates that the system is preparing a manual
update.
- system_prepared, which indicates that the system is ready to starting a
manual update.
- system_prepare_failed, which indicates that the system could not start
a manual update.
Note: Check the event log.
- system_initializing, which indicates that the system is readying nodes
for an update.
- system_updating, which indicates that the nodes are being updated.
- system_updating_pausing, which indicates that the system is pausing
before it continues to update the nodes.
Note: If you specify
applysoftware -continue the status changes to
system_updating.
- system_committing, which indicates that all nodes are updated and the
system is readying the new code.
- system_stalled, which indicates that an update is stalled because of
unexpected node problems.
- system_stalled_non_redundant, which indicates that an update is stalled
because of dependent volumes.
- system_restoring, which indicates that a stalled update is canceled by
the user.
Note: The previous code version is being restored.
- system_restoring_pausing, which indicates that the system is pausing
before it continues to restore the nodes.
Note: If you specify
applysoftware -continue the status changes to
system_updating_restoring.
- system_restoring_stalled_non_redundant, which indicates that an update
is canceled and then stalled because of dependent volumes.
- system_manual_update, which indicates that a manual update is in
progress.
- system_completion_required, which indicates that all nodes are updated
and management functions are available, but further system changes are necessary to
complete the update.
Note: Check the event log.
- system_completing, which indicates that an automatic update completion
is in progress.
- system_completing_pausing, which indicates that automatic update
completion is paused.
- system_completing_paced, which indicates that a paced update completion
is in progress.
- system_completing_stalled, which indicates that an automatic update
completion stalled because of an unexpected problem.
- enclosures, which indicates that enclosure firmware is being
updated.
- enclosures_stalled, which indicates that an enclosure firmware update
stalled because of an unexpected problem or the enclosure has a lack of redundancy.
- enclosures_restoring, which indicates a stalled update has been
canceled by the user. The previous code version is being restored to the enclosure
canisters.
- drives, which indicates that drive firmware is being updated.
- event_sequence_number
- Indicates an event that describes any current problem with the code update. The value must
be a numeric string in decimal format (or blank).
- progress
- Indicates the completion percentage of the current update activity in terms of number of
objects updated (rather than time elapsed). The value must be a numeric string (decimal) in
the range 0 - 100.
- estimated_completion_time
- Indicates estimated completion time of current update activity. It is valid only if the
current update activity is automatic and is not stalled. The value must be in the format
YYMMDDHHMMSS (or blank).
- suggested_action
- Indicates the actions that help the update progress. The value must be:
- complete, which indicates the system update is complete and update
completion must be issued. Nodes are online.
- continue, which indicates that the concurrent
upgrade is paused and you must applysoftware -continue to continue the
concurrent upgrade.
- fix, which indicates that an update cannot continue because of a
problem. Check the event log, specifically the event_sequence_number
output. Nodes are offline.
- manual, which indicates that a manual update is in progress.
- pacednext, which indicates that the paced update is in progress and the
next node must be scheduled for updating. Nodes are online.
- resume_cancel, which indicates that the update is stalled but can be
resumed or canceled. Nodes are online.
- resume, which indicates that the update completion is stalled but can
be resumed. Nodes are online.
- start, which indicates that the system is ready for a new update to
start. No update is in progress or prepared and all nodes are online.
- wait, which indicates that the system is busy (no action is required)
because an update is in progress.
- system_new_code_level
- Indicates that a new level of code is being updated. The value must be the build version
(or blank if not updating or restoring the system).
- system_forced
- Indicates any current node-related activity in forced mode (ignoring dependent volumes).
The values are yes or no.
- system_next_node_status
- Indicates the status of the next node in the current node-related update activity. The
values are:
- none, which indicates that there is no node to update.
- paused, which indicates that the current node is
paused during a concurrent upgrade, and you must applysoftware -continue
to continue the concurrent upgrade.
- waiting, which indicates that the node is ready for updating and that
the system is waiting (typically for multipathing failover).
- ready, which indicates that the node is ready for updating, and the
update activity is paced. You must start the update manually.
- updating, which indicates that the node is updating.
- stalled, which indicates that the node is going to be updated next, but
the update is stalled.
- system_next_node_time
- Indicates the time that the next node update will start. It is valid only if the
system_next_node_status is waiting. The value must
be in the format YYMMDDHHMMSS x (or blank).
- system_next_node_id
- Indicates the ID of the next node in the current node-related update. The value must be a
numeric string (or blank).
- system_next_node_name
- Indicates the name of the next node in the current node-related update. The value must be
an alphanumeric string (or blank).
An invocation example of an update
lsupdate
The
resulting output:
status system_updating
event_sequence_number
progress 50
estimated_completion_time 140522093020
suggested_action wait
system_new_code_level 7.4.0.1 (build 99.2.141022001)
system_forced no
system_next_node_status updating
system_next_node_time
system_next_node_id 2
system_next_node_name node2
An invocation example of a paced
update
lsupdate
The resulting output:
status system_completing_paced
event_sequence_number
progress 75
estimated_completion_time
suggested_action pacednext
system_new_code_level
system_forced no
system_next_node_status ready
system_next_node_time
system_next_node_id 4
system_next_node_name node4