cluster image update
Suggest changes
PDFs
Manage an update
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The cluster image update command is used to initiate a ONTAP update. The update is preceded by a validation of the cluster to ensure that any issues that might affect the update are identified. There are two types of updates of a cluster. A rolling update updates ONTAP one HA pair at a time. This type of update is performed for clusters with fewer than eight nodes or when the -force-rolling option is specified for clusters with eight or more nodes. A batch update is used for clusters of eight or more nodes, and performs updates of multiple HA pairs at the same time.
There are predefined points in the update when the update can be paused (either by the user or by an error). These pause points occur after validation, after download to the boot device, after takeover has completed, and after giveback has completed.
Parameters
-version <text>- Update Version-
Specifies the ONTAP version to use to update the cluster.
[-nodes {<nodename>|local}]- Node-
Specifies the nodes that are to be updated. This parameter is not supported for MetroCluster configurations updates or two-stage upgrades. The node upgrade sequence does not follow the node order entered in
cluster image updatecommand [-estimate-only <true>]- Estimate Only-
Creates a report of the steps that occur during the update without performing them precisely.
[-pause-after {none|takeover-giveback|all}]- Update Pause-
Specifies that the update should pause at each predefined pause points (for example, after validation, after download to the boot device, after takeover, and after giveback) during the update.
[-ignore-validation-warning {true|false}]- Ignore Validation-
Specifies that the update should proceed even if the validation reports warnings.
[-skip-confirmation {true|false}]- Skip Confirmation-
Specifies that a validation that does not detect any error issues should not ask the user to confirm the update but simply proceed with the update.
[-force-rolling <true>]- Force Rolling Update-
This option is used for clusters with eight or more nodes to specify that a rolling update (one HA pair at a time) should be done. This parameter is not supported for single-node cluster and two-node MetroCluster.
[-stabilize-minutes <integer>]- Minutes to stabilize-
Specifies the number of minutes that the update should wait after a takeover or giveback is completed. This allows time for the clients to recover from the pause in I/O that occurs during takeover and giveback. This parameter is not supported for single-node cluster.
[-show-validation-details <true>]- Shows All Validation Details-
Specify to display all validation details. Default: do not display all details.
[-skip-nodes-at-target-version <true>]- Skip Nodes at Target Version (privilege: advanced)-
When this parameter is
true, only the nodes which are not running the target version are upgraded. Nodes which are currently running the target version are skipped. The default value istrue. This parameter cannot be set to true in MetroCluster configurations.
Examples
The following example shows the cluster image update operation. configuration having node nodeA and nodeB.
cluster1::> cluster image update -version 9.16.1
Starting validation for this update...
It can take several minutes to complete validation...
WARNING: There are additional manual upgrade validation checks that must
be performed after these automated validation checks have completed
successfully.
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 manual validation checks that need to be
performed before update.
Upgrade ONTAP documentation available at: https://docs.netapp.com/us-en/ontap/upgrade/index.html
The list of checks are available at: https://docs.netapp.com/us-en/ontap/upgrade/task_what_to_check_before_upgrade.html
Failing to do so can result in an update failure or an I/O disruption.
Please use Interoperability Matrix Tool (IMT http://mysupport.netapp.com/matrix)
to verify host system supportability configuration information.
Pre-update Check Status Error-Action
----------------------- -------- ————————————————-----------------
Boot 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.
Manual checks Warning Warning: Manual validation
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.
NFS 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
Nodes 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".
Overall Status Warning
5 entries were displayed.
Warning: Validation has reported warnings.
Do you want to continue? {y|n}:
Starting update...
Info: Run the "cluster image show-update-progress" command to check update status.