Table of ContentsView in Frames

Upgrading a Data ONTAP cluster nondisruptively by using the automated method (minor NDU only)

The automated NDU method validates the cluster components to ensure that the cluster can be upgraded nondisruptively, installs the target Data ONTAP image on each node, and then, based on the number of nodes in the cluster, executes either a rolling or batch upgrade in the background.

Before you begin

Steps

  1. Download the target Data ONTAP software package: cluster image package get -url location
    The software package contains the target Data ONTAP image and firmware, and the set of upgrade validation rules. This package is downloaded to the cluster package repository on the root volume of one of the nodes in the cluster.
    Example
    cluster1::> cluster image package get -url http://www.example.com/software/8.3/image.tgz
    
    Software get http://www.example.com/software/8.3/image.tgz started on node node0
    Downloading package. This may take up to 10 minutes.
    98% downloaded
    There is no update/install in progress
    Status of most recent operation:
            Run Status:     Working
            Exit Status:    Success
            Phase:          Download
            Exit Message:
    Processing Package.
    Process package Complete
    
  2. Verify that the software package is available in the cluster package repository: cluster image package show-repository
    Example
    cluster1::> cluster image package show-repository
    Package Version
    ----------------
    8.3.0
    
  3. Verify that the cluster is ready to be upgraded nondisruptively: cluster image validate -version package_version_number
    This command checks the cluster components to validate that the upgrade can be completed nondisruptively, and then provides the status of each check and any required action you must take before performing the software upgrade.

    You can proceed to the next step after completing all identified required actions.

    Example
    cluster1::> cluster image validate -version 8.3.0
    
    It can take several minutes to complete validation...
    Pre-update Check       Status      Error-Action
    ---------------------  ---------   -------------------------------------------
    Aggregate status       OK
    CIFS status            OK
    Cluster health         OK
    status
    Disk status            OK
    High Availability      OK
    status
    LIF status             OK
    LIFs on home node      OK
    MetroCluster           OK
    configuration status
    SnapMirror status      OK
    Volume status          OK
    mgmt epoch status      OK
    mgmt RDB ring status   OK
    vifmgr epoch status    OK
    vifmgr RDB ring        OK
    status
    vldb epoch status      OK
    vldb RDB ring status   OK
    Overall Status         OK
    17 entries were displayed.
    
  4. Optional: If desired, generate a software upgrade estimate: cluster image update -version package_version_number -estimate-only
    The software upgrade estimate displays details about each component to be updated, and the estimated duration of the upgrade.
  5. Perform the software upgrade: cluster image update -version package_version_number
    This command validates that each cluster component is ready to be upgraded, installs the target Data ONTAP image on each node in the cluster, and then performs a nondisruptive upgrade in the background. If an issue is encountered, the update will pause and prompt you to take corrective action. You can use the cluster image show-update-progress command to view details about the issue. After correcting the issue, you can resume the update by using the cluster image resume-update command.

    If the cluster consists of 2 through 6 nodes, a rolling upgrade will be performed.

    If the cluster consists of 8 or more nodes, a batch upgrade will be performed by default. If desired, you can use the -force-rolling parameter to specify a rolling upgrade instead.

    After completing each takeover and each giveback, the upgrade will wait for 8 minutes to enable client applications to recover from the pause in I/O that occurs during the takeover and giveback. If your environment requires more or less time for client stabilization, you can use the -stabilize-minutes parameter to specify a different amount of stabilization time.

    Example
    cluster1::> cluster image update -version 8.3.0
    
    Starting validation for this update. Please wait..
    
    It can take several minutes to complete validation...
    Non-Disruptive Check   Status      Error-Action
    ---------------------  ---------   -------------------------------------------
    Aggregate status       OK
    CIFS status            OK
    Cluster health         OK
    status
    Disk status            OK
    High Availability      OK
    status
    LIF status             OK
    LIFs on home node      OK
    MetroCluster           OK
    configuration status
    SnapMirror status      OK
    Volume status          OK
    mgmt epoch status      OK
    mgmt RDB ring status   OK
    vifmgr epoch status    OK
    vifmgr RDB ring        OK
    status
    vldb epoch status      OK
    vldb RDB ring status   OK
    Overall Status         OK
    17 entries were displayed.
    
    
    Would you like to proceed with update ? {y|n}: y
    Starting update...
    
  6. Optional: If necessary, manage the upgrade process by using the applicable command:
    To do this... Enter this command...
    Monitor the status and estimated duration of the upgrade cluster image show-update-progress
    View the log of each task that has executed during the upgrade cluster image show-update-log
    Pause the upgrade cluster image pause-update
    Resume a paused upgrade cluster image resume-update
    Cancel the upgrade
    Note: You can only cancel an upgrade if it is currently paused.
    cluster image cancel-update
  7. Display the cluster update history to verify that the upgrade was completed successfully for each node: cluster image show-update-history
    Example
    The Data ONTAP version numbers in the following example are provided for example purposes only:
    cluster1::> cluster image show-update-history 
               Package    Start       Completion                Previous  Updated
    Status     Version    Time        Time        Component ID  Version   Version
    ---------- ---------  ----------  ----------  ------------  --------- ---------
    successful 8.3.y      11/18/2014  11/18/2014  node0         8.3.x     8.3.y
                          15:20:51    15:44:13
    successful 8.3.y      11/18/2014  11/18/2014  node1         8.3.x     8.3.y
                          15:20:51    16:03:20
    2 entries were displayed.