cluster image show-update-progress
Suggest changes
PDFs
Display the update progress
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The cluster image show-update-progress command displays information about the current state of an update. By default, the command displays the following information:
-
Update phase
-
Status
-
Estimated Duration
-
Elapsed Duration
Parameters
- {
[-fields <fieldname>,…] -
If you specify the
-fields <fieldname>, …parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify. - |
[-instance ]} -
If you specify the
-instanceparameter, the command displays detailed information about all fields. [-ndu-phase {validation|prereq-updates|ontap-updates|package-management|default-phase|post-update-checks}]- Update Phase-
Displays information about the specified update phase.
[-phase-status {in-progress|waiting|paused-by-user|paused-on-error|completed|canceled|failed|pause-pending|cancel-pending}]- Phase Status-
Displays information about progress matching the specified phase status.
[-phase-duration <text>]- Phase Duration-
Displays information about progress matching the specified phase duration.
[-phase-comments <text>]- Phase Comments-
Displays information about progress matching the specified phase comments.
[-elapsed-duration {<seconds>|[<d> days] <hh>:<mm>[:<ss>]}]- Elapsed duration of the phase-
Displays information about progress matching the specified elapsed duration.
[-estimated-duration {<seconds>|[<d> days] <hh>:<mm>[:<ss>]}]- Estimated duration of the phase-
Displays information about progress matching the specified estimated duration.
[-phase-description <text>]- Phase Description-
Displays information about progress matching the specified phase description.
[-subsystem-name <text>]- Subsystem Name-
Displays information about progress matching the specified subsystem name.
[-subsystem-status <text>]- Subsystem Status-
Displays information about progress matching the specified subsystem status.
[-subsystem-details <text>]- Subsystem Details-
Displays information about progress matching the specified subsystem details.The "firmware update" status is reflected in the following states: - not started: The firmware update process has not been initiated. - no change: The firmware update was completed without any changes. - pending: The firmware update is pending. - in progress: The firmware update is currently in progress. - completed: The firmware update is completed with changes. - error: An error occurred during the firmware update process. - aborted: The firmware update process was aborted.
[-subsystem-action <text>]- Subsystem Action-
Displays information about progress matching the specified subsystem action.
Examples
The following example shows the cluster image validate progress of two nodes, nodeA and nodeB after executing the cluster image validation command. On the first screen it shows when the pre-update check status is in-progress and on the second screen it shows the pre-update checks status changed to completed .
cluster1::> cluster image show-update-progress
Estimated Elapsed
pdate Phase Status Duration Duration
------------------- ----------------- --------------- ---------------
re-update checks in-progress 00:10:00 00:00:13
etails:
re-update Check Status Error-Action
------------------- ----------------- -------------------------------
cluster1::> cluster image show-update-progress
pdate Phase Status Duration Duration
------------------- ----------------- --------------- ---------------
re-update checks completed 00:10:00 00:01:09
etails:
re-update Check Status Error-Action
------------------- ----------- --------------------------
oot Menu Status Warning Warning: bootarg.init.bootmenu is
enabled on nodes: nodeA,
nodeB. The boot process
of the nodes will be delayed.
Action: Set the bootarg.init.bootmenu
bootarg to false before proceeding
with the upgrade.
anual checks Warning Warning: Manual validation checks
need to be performed. Refer to the
Upgrade Advisor Plan or the "What
should I verify before I upgrade with
or without Upgrade Advisor" section
in the "Upgrade ONTAP" documentation
for the remaining validation checks
that need to be performed before
update. Failing to do so can result
in an update failure or an I/O
disruption.
Action: Refer to the Upgrade Advisor
Plan or the "What should I verify
before I upgrade with or without
Upgrade Advisor" section in the
"Upgrade ONTAP" documentation for the
remaining validation checks that need
to be performed before update.
FS mounts Warning Warning: This cluster is serving NFS
clients. If NFS soft mounts are used,
there is a possibility of frequent
NFS timeouts and race conditions that
can lead to data corruption during
the upgrade.
Action: Use NFS hard mounts, if
possible. To list Vservers running
NFS, run the following command:
vserver nfs show
odes to update list Warning Warning: List of nodes to be
upgraded: "nodeA,
nodeB."
Action: To upgrade all selected nodes,
regardless of their current version,
set the (privilege: advanced)
"-skip-nodes-at-target-version"
parameter to "false".
entries were displayed.
The following example shows the cluster image validate progress of two nodes, nodeA and nodeB after executing the cluster image validation command along with option show-validation-details. On the first screen it shows when the pre-update check status is in-progress . On the second screen it shows the pre-update checks status changed to completed .
cluster1::> cluster image show-update-progress
Estimated Elapsed
pdate Phase Status Duration Duration
------------------- ----------------- --------------- ---------------
re-update checks in-progress 00:10:00 00:00:13
etails:
re-update Check Status Error-Action
------------------- ----------------- -------------------------------
cluster1::> cluster image show-update-progress
stimated Elapsed
pdate Phase Status Duration Duration
------------------- ----------------- --------------- ---------------
re-update checks completed 00:10:00 00:01:08
etails:
re-update Check Status Error-Action
------------------- ----------------- --------------------------------
MPQ Router and OK N/A
roker Config
leanup
ggregate online OK N/A
tatus and parity
heck
ggregate plex OK N/A
esync status check
pplication OK N/A
rovisioning Cleanup
utoboot Bootargs OK N/A
tatus
ackend OK N/A
onfiguration Status
oot Menu Status Warning Warning: bootarg.init.bootmenu is
enabled on nodes: nodeA,
nodeB. The boot process
of the nodes will be delayed.
Action: Set the
bootarg.init.bootmenu
bootarg to false before
proceeding with the upgrade.
roadcast Domain OK N/A
vailability and
niqueness for HA
air status
IFS compatibility OK N/A
tatus check
LAM quorum online OK N/A
tatus check
PU Utilization OK N/A
tatus
apacity licenses OK N/A
nstall status check
heck For SP/BMC OK N/A
onnectivity To
odes
heck LDAP fastbind OK N/A
sers using
nsecure connection.
heck for unsecure OK N/A
ex algorithm
onfigurations.
heck for unsecure OK N/A
ac configurations.
loud keymanager OK N/A
onnectivity check
luster health and OK N/A
ligibility status
luster quorum OK N/A
tatus check
luster/management OK N/A
witch check
ompatible New OK N/A
mage Check
urrent system OK N/A
ersion check if it
s susceptible to
ossible outage
uring NDU
ata ONTAP Version OK N/A
nd Previous
pgrade Status
ata aggregates HA OK N/A
olicy check
isk status check OK N/A
or failed, broken
r non-compatibility
uplicate Initiator OK N/A
heck
ncryption key OK N/A
igration status
heck
xternal OK N/A
ey-manager with
egacy KMIP client
heck
xternal keymanager OK N/A
ey server status
heck
abricpool Object OK N/A
tore Availability
igh Availability OK N/A
onfiguration
tatus check
nfinite Volume OK N/A
vailibility check
IF failover OK N/A
apability status
heck
IF health check OK N/A
IF load balancing OK N/A
tatus check
IFs is on home OK N/A
ode status
ogically over OK N/A
llocated DP
olumes check
anual checks that Warning Warning: Manual validation checks
an be done using need to be performed. Refer to the
pgrade ONTAP Upgrade Advisor Plan or the "What
ocumentation should I verify before I
upgrade with or without Upgrade
Advisor" section in the
"Upgrade ONTAP" documentation
for the remaining validation checks
that need to be performed before
update. Failing to do so can result
in an update failure or an I/O
disruption.
Action: Refer to the Upgrade
Advisor Plan or the "What should
I verify before I upgrade with
or without Upgrade Advisor"
section in the "Upgrade ONTAP"
documentation for the remaining
validation checks that need
to be performed before update.
etroCluster OK N/A
onfiguration
tatus check for
ompatibility
inimum number of OK N/A
ggregate disks
heck
ulti-Admin upgrade OK N/A
alidation checks
AE Aggregate and OK N/A
VE Volume
ncryption Check
DMP sessions check OK N/A
FS mounts status Warning Warning: This cluster is serving
heck NFS clients. If NFS soft mounts
are used, there is a possibility
of frequent NFS timeouts and race
conditions that can lead to data
corruption during the upgrade.
Action: Use NFS hard mounts, if
possible. To list Vservers running
NFS, run the following command:
vserver nfs show
ame Service OK N/A
onfiguration DNS
heck
ame Service OK N/A
onfiguration LDAP
heck
etwork port OK N/A
eachability check
ode to SP/BMC OK N/A
onnectivity check
odes to update list Warning Warning: List of nodes to be
upgraded: "nodeA,
nodeB."
Action: To upgrade all selected
nodes, regardless of their
current version, set the
(privilege: advanced)
"-skip-nodes-at-target-version"
parameter to "false".
KM/KMIP enabled OK N/A
ystems - Missing
eys check
NTAP API to REST OK N/A
ransition warning
NTAP Image OK N/A
apability Status
penSSL 3.0.x OK N/A
pgrade validation
heck
penssh 7.2 upgrade OK N/A
alidation check
latform Health OK N/A
onitor check
re-Update OK N/A
onfiguration
erification
DB Replica Health OK N/A
heck
eplicated database OK N/A
chema consistency
heck
unning Jobs Status OK N/A
AN LIF association OK N/A
tatus check
AN compatibility OK N/A
or manual
onfigurability
heck
AN kernel agent OK N/A
tatus check
ecure Purge OK N/A
peration Check
helves and Sensors OK N/A
heck
napLock Version OK N/A
heck
napMirror OK N/A
ynchronous
elationship status
heck
napMirror OK N/A
ompatibility
tatus check
upported platform OK N/A
heck
arget ONTAP OK N/A
elease support for
iberBridge 7500N
heck
pgrade Version OK N/A
ompatibility Status
erify all bgp OK N/A
eer-groups are in
he up state
erify if a cluster OK N/A
anagement LIF
xists
erify that e0M is OK N/A
ome to no LIFs
ith high speed
ervices.
olume Conversion OK N/A
n Progress Check
olume move OK N/A
rogress status
heck
olume online OK N/A
tatus check
SCSI target portal OK N/A
roups status check
verall Status Warning Warning
8 entries were displayed.
The following example shows the automated nondisruptive update of two nodes, nodeA and nodeB. In this case, nodeA's update is waiting, nodeB's update is in progress. nodeB's giveback operation is in progress.
cluster1::> cluster image show-update-progress Estimated Elapsed Update Phase Status Duration Duration -------------------- ----------------- --------------- --------------- Pre-update checks completed 00:10:00 00:00:02 Data ONTAP updates in-progress 01:23:00 00:32:07 Details: Node name Status Status Description -------------------- ----------------- --------------------------------- nodeA waiting nodeB in-progress Performing giveback operation. 3 entries were displayed. cluster1::>
The following example shows the automated nondisruptive update of two nodes, nodeA and nodeB. In this case, automated nondisruptive update is paused-on-error in "Data ONTAP updates" phase. nodeA's update is waiting, nodeB's update is failed. "Status Description" show nodeB's error and action.
cluster1:> cluster image show-update-progress
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- ----------------- --------------- ---------------
Pre-update checks completed 00:10:00 00:00:02
Data ONTAP updates paused-on-error 00:49:00 00:05:21
Details:
Node name Status Status Description
-------------------- ----------------- ----------------------------------
nodeA waiting
nodeB failed Error: Takeover of node
"nodeB" is not possible.
Action: Use the "storage failover
show" command to view the cause of
the failure.
2 entries were displayed.
Status: Paused - An error occurred in "Data ONTAP updates" phase. The
non-disruptive update cannot continue until the error has been resolved.
Resolve all issues, then use the "cluster image resume-update" command to
resume the update.
cluster1:>
The following example shows that the automated nondisruptive update is paused-on-error in "Post-update checks" update phase and "Status Description" shows the error and action.
cluster1::> cluster image show-update-progress
Estimated Elapsed
Update Phase Status Duration Duration
-------------------- --------------- --------------- ---------------
Data ONTAP updates completed 02:19:00 00:00:03
Post-update checks paused-on-error 00:10:00 00:00:02
Details:
Post-update Check Status Error-Action
-------------------- -------------- -------------------------------------
Cluster Quorum Error Error: Cluster is not in quorum.
Status
Action: Use the (privilege: advanced)
"cluster ring show" command to verify
all replication unit details.
5 entries were displayed.
Status: Paused - An error occurred in "Post-update checks" phase. The
non-disruptive update cannot continue until the error has been resolved.
Resolve all issues, then use the "cluster image resume-update" command
to resume the update.
cluster1::>
The following example shows that the automated nondisruptive update is completed on nodeA and nodeB.
cluster1::> cluster image show-update-progress Estimated Elapsed Update Phase Status Duration Duration -------------------- ----------------- --------------- --------------- Pre-update checks completed 00:10:00 00:00:13 Data ONTAP updates completed 01:23:00 01:15:11 Post-update checks completed 00:10:00 00:00:02 3 entries were displayed. Updated nodes: nodeA, nodeB. cluster1:>
The following example shows the automated update of two-node MetroCluster configuration having clusters cluster_A and cluster_B. In this case, cluster_A's update is waiting and cluster_B's update is in progress. cluster_B's switchback operation is in progress.
cluster_A::> cluster image show-update-progress Estimated Elapsed Cluster Duration Duration Status ------------------------------ --------------- --------------- ---------------- cluster_A 00:00:00 00:00:00 waiting cluster_B 00:00:00 00:06:42 in-progress Details: Switchback in progress. Waiting for partner cluster "sti60-vsim-ucs134f_siteB" to be up. cluster_A::>
The following example shows that the automated update is completed on both cluster_A and cluster_B in two-node MetroCluster configuration.
cluster_A::> cluster image show-update-progress Estimated Elapsed Cluster Duration Duration Status ------------------------------ --------------- --------------- ---------------- cluster_A 00:00:00 00:20:44 completed cluster_B 00:00:00 00:10:43 completed Details: MetroCluster updated successfully. cluster_A::>