ONTAP 9.

Upgrade Express Guide

June 2016 | 215-11234_A0

[email protected]
Release Candidate Documentation - Contents Subject To Change

Table of Contents | 3

Contents
Deciding whether to use this guide ............................................................. 4
Cluster software update workflow .............................................................. 5
Performing manual checks before an automated cluster upgrade .......... 6
Reviewing pre-update resources .................................................................................. 6
Reviewing cluster upgrade requirements .................................................................... 7
Cluster upgrade requirements .......................................................................... 7
Guidelines for estimating the duration of the upgrade process ....................... 8
Upgrade considerations for root-data partitioning and root-data-data
partitioning ................................................................................................ 8
Verifying cluster upgrade limits .................................................................................. 8
Verifying the SAN configuration ................................................................................ 9
Ensuring that no jobs are running ............................................................................... 9
Disabling automatic LIF rebalancing ........................................................................ 10
Checking for back-end configuration errors before downgrading ............................ 11
Obtaining ONTAP software images .......................................................................... 12

Upgrading an ONTAP cluster nondisruptively by using the

automated method ................................................................................. 13
Copyright information ............................................................................... 17
Trademark information ............................................................................. 18
How to send comments about documentation and receive update
notifications ............................................................................................ 19
Index ............................................................................................................. 20

Release Candidate Documentation - Contents Subject To Change

Deciding whether to use this guide

This guide describes how to upgrade an ONTAP cluster using the automated nondisruptive upgrade
feature. It applies to all ONTAP configurations except for MetroCluster configurations.
You should use this guide if you want to use one of the following upgrade paths:

Upgrades to releases in the ONTAP 9.0 release family from any 8.3.0 or later release (major
upgrades), except for MetroCluster configurations.

Upgrades from 9.0.x to 9.0.z (minor upgrades), except for MetroCluster configurations.

Patch upgrades, including eight-node or four-node MetroCluster configurations.

For minor or major upgrades of MetroCluster configurations, or if you want to perform the upgrade
manually, use the procedures in the Clustered Data ONTAP Upgrade and Revert/Downgrade Guide.

ONTAP 9.0 Upgrade and Revert/Downgrade Guide

Release Candidate Documentation - Contents Subject To Change

Cluster software update workflow

You can use the cluster software update workflow to perform the entire process.

Perform the
upgrade.

Prepare for the upgrade.

Review pre-upgrade
resources.

Verify adequate
volume freespace.

Disable LIF
rebalancing.

Review upgrade
requirements.

Verify SAN
configuration.

Obtain ONTAP
image.

Verify cluster
upgrade limits.

Ensure no jobs
running.

Release Candidate Documentation - Contents Subject To Change

Performing manual checks before an automated

cluster upgrade
Before performing an upgrade or downgrade you must manually check that the cluster is ready, make
any required configuration changes, and obtain and install the target ONTAP images.
Steps

1. Reviewing pre-update resources on page 6

Before updating the ONTAP software, you should review resources to understand issues you must
resolve, understand new system behavior in the target release, and confirm hardware support.
2. Reviewing cluster upgrade requirements on page 7
Before updating the ONTAP software, you must verify that your cluster meets the general
requirements. Some configurations and features also have requirements that you should
understand.
3. Verifying cluster upgrade limits on page 8
Before upgrading the ONTAP software, you must verify that your cluster does not exceed the
platform system limits. SAN also has limits that you should verify in addition to the platform
system limits.
4. Verifying the SAN configuration on page 9
Upgrading in a SAN environment changes which paths are direct. Therefore, before performing an
upgrade, you should verify that each host is configured with the correct number of direct and
indirect paths, and that each host is connected to the correct LIFs.
5. Ensuring that no jobs are running on page 9
Before updating or downgrading the ONTAP software, you must verify the status of cluster jobs.
If any aggregate, volume, NDMP (dump or restore), or Snapshot jobs (such as create, delete,
move, modify, replicate, and mount jobs) are running or queued, you must allow the jobs to finish
successfully or stop the queued entries.
6. Disabling automatic LIF rebalancing on page 10
By disabling automatic LIF rebalancing before performing a batch upgrade, you can ensure that
the LIFs remain online during the entire upgrade procedure.
7. Checking for back-end configuration errors before downgrading on page 11
Before downgrading a storage system that uses array LUNs to an earlier release of ONTAP, you
need to run the storage errors show command to determine whether there are any back-end
configuration errors.
8. Obtaining ONTAP software images on page 12
You must copy a software image from the NetApp Support Site to an HTTP or FTP server on your
network so that nodes can access the image.

Reviewing pre-update resources

Before updating the ONTAP software, you should review resources to understand issues you must
resolve, understand new system behavior in the target release, and confirm hardware support.
Steps

1. Review the Release Notes for the target release.

ONTAP 9.0 Release Notes

Release Candidate Documentation - Contents Subject To Change

Performing manual checks before an automated cluster upgrade | 7

The Important cautions section describes potential issues that you should be aware of before
upgrading to the new release. The New and changed features and Known problems and
limitations sections describe new system behavior after upgrading to the new release.
2. Confirm that your hardware platform is supported in the target release.

NetApp Hardware Universe

3. Confirm that your cluster and management switches are supported in the target release.
You must verify that the NX-OS (cluster network switches), IOS (management network
switches), and reference configuration file (RCF) software versions are compatible with the
version of ONTAP to which you are upgrading. If your switches do not have the minimum
software versions for the target ONTAP release, then you must upgrade the switch software
before you can upgrade ONTAP.

NetApp Downloads: Cisco Ethernet Swtich

NetApp Downloads: NetApp Ethernet Switch
4. If your cluster is configured for SAN, confirm that the SAN configuration is fully supported.
All SAN componentsincluding the target ONTAP software version, host OS and patches,
required Host Utilities software, multipathing software, and adapter drivers and firmware
should be supported.

NetApp Interoperability Matrix Tool

Reviewing cluster upgrade requirements

Before updating the ONTAP software, you must verify that your cluster meets the general
requirements. Some configurations and features also have requirements that you should understand.

Cluster upgrade requirements

There are release and configuration requirements that your cluster should meet before you perform an
upgrade. Additionally, there are mixed version requirements that you should be aware of while you
are performing the upgrade.
Release requirements
You can upgrade clusters to the ONTAP 9.0 release family from any 8.3.0 or later release. Minor
upgrades within the ONTAP 9.0 release family are supported from all previous 9.0 releases. You can
determine the current version of ONTAP running on each node by using the system image show
command.
If you want to upgrade to a ONTAP 9.0 release from a release earlier than 8.3.0, you must perform an
intermediate upgrade (also known as a multi-hop upgrade) to ONTAP 8.3.0 or later before upgrading
to the target ONTAP 9.0 release.

Find the Upgrade and Revert/Downgrade Guide for your version of Data ONTAP 8
Configuration requirements
The cluster must meet the following configuration requirements before you upgrade it:

If your cluster serves NFS clients, you must use hard mounts.
You should not use soft mounts when there is a possibility of frequent NFS timeouts, which can
lead to disruptions during the upgrade process and possible data corruption.

Release Candidate Documentation - Contents Subject To Change

8 | Upgrade Express Guide

Mixed version requirements

ONTAP clusters can operate for a limited time in a mixed version state, in which nodes in a cluster
are running ONTAP versions from different release families. However, the upgrade is not complete
until all nodes are running the new target release.
When the cluster is in a mixed version state, you should not enter any commands that alter the cluster
operation or configuration except as necessary to satisfy upgrade requirements. You should complete
the upgrade as quickly as possible; do not allow the cluster to remain in a mixed version state longer
than necessary.

Guidelines for estimating the duration of the upgrade process

You should plan for at least 30 minutes to complete preparatory steps, at least 30 minutes to upgrade
the cluster (depending on the number of nodes), and at least 30 minutes to complete post-upgrade
steps.
The upgrade duration guidelines are based on typical configurations and workloads. You can use
these guidelines to estimate the time it will take to perform a nondisruptive upgrade in your
environment. However, the actual duration of your upgrade process will depend on your individual
environment and the number of nodes.

Upgrade considerations for root-data partitioning and root-data-data

partitioning
Root-data partitioning and, starting with ONTAP 9.0, root-data-data-partitioning is supported for
some platform models and configurations. This partitioning capability is enabled during system
initialization; it cannot be applied to existing aggregates.
For information about migrating your data to a node that is configured for root-data partitioning or
root-data-data partitioning, contact your account team or partner organization.
Related information

ONTAP 9.0 Disks and Aggregates Power Guide

Verifying cluster upgrade limits

Before upgrading the ONTAP software, you must verify that your cluster does not exceed the
platform system limits. SAN also has limits that you should verify in addition to the platform system
limits.
Steps

1. Verify that the cluster does not exceed the system limits for your platform.

NetApp Hardware Universe

2. If your cluster is configured for SAN, verify that it does not exceed the configuration limits for
FC, FCoE, and iSCSI.

ONTAP 9.0 SAN Configuration Guide

3. Determine the CPU and disk utilization:
node run -node node_name -command sysstat -c 10 -x 3

You should monitor CPU and disk utilization for 30 seconds. The values in the CPU and Disk
Util columns should not exceed 50% for all 10 measurements reported. No additional load
should be added to the cluster until the upgrade is complete.

Release Candidate Documentation - Contents Subject To Change

Performing manual checks before an automated cluster upgrade | 9

Verifying the SAN configuration

Upgrading in a SAN environment changes which paths are direct. Therefore, before performing an
upgrade, you should verify that each host is configured with the correct number of direct and indirect
paths, and that each host is connected to the correct LIFs.
Steps

1. On each host, verify that a sufficient number of direct and indirect paths are configured, and that
each path is active.
Each host must have a path to each node in the cluster.
2. Verify that each host is connected to a LIF on each node.
You should record the list of initiators for comparison after the upgrade.
For...

Enter...

iSCSI

iscsi initiator show -fields igroup,initiatorname,tpgroup

FC

fcp initiator show -fields igroup,wwpn,lif

Ensuring that no jobs are running

Before updating or downgrading the ONTAP software, you must verify the status of cluster jobs. If
any aggregate, volume, NDMP (dump or restore), or Snapshot jobs (such as create, delete, move,
modify, replicate, and mount jobs) are running or queued, you must allow the jobs to finish
successfully or stop the queued entries.
Steps

1. Review the list of any running or queued aggregate, volume, or Snapshot jobs:
job show
Example
cluster1::> job show
Owning
Job ID Name
Vserver
------ -------------------- ---------8629
Vol Reaper
cluster1
Description: Vol Reaper Job
8630
Certificate Expiry Check
cluster1
Description: Certificate Expiry
.
.
.

Node
State
-------------- ---------Queued
Check

Queued

2. Delete any running or queued aggregate, volume, or Snapshot copy jobs:

job delete -id job_id
Example
cluster1::> job delete -id 8629

3. Verify that no aggregate, volume, or Snapshot jobs are running or queued:

job show
Release Candidate Documentation - Contents Subject To Change

10 | Upgrade Express Guide

Example

In this example, all running and queued jobs have been deleted:
cluster1::> job show
Owning
Job ID Name
Vserver
Node
State
------ -------------------- ---------- -------------- ---------9944
SnapMirrorDaemon_7_2147484678
cluster1
node1
Dormant
Description: Snapmirror Daemon for 7_2147484678
18377 SnapMirror Service Job
cluster1
node0
Dormant
Description: SnapMirror Service Job
2 entries were displayed

Disabling automatic LIF rebalancing

By disabling automatic LIF rebalancing before performing a batch upgrade, you can ensure that the
LIFs remain online during the entire upgrade procedure.
About this task

When automatic LIF rebalancing is enabled, LIFs can be migrated to a less-utilized port on another
node based on the LIF failover configuration. However, because a batch upgrade enables you to
upgrade multiple nodes concurrently, automatic LIF rebalancing could cause the LIFs to migrate to a
node that is rebooting.
Steps

1. Set the privilege level to advanced:

set -privilege advanced

2. View and record any LIFs that have automatic LIF rebalancing enabled:
network interface show -allow-lb-migrate true
Example
cluster1::*> network interface show -allow-lb-migrate true
Logical
Status
Network
Current
Vserver
Interface Admin/Oper Address/Mask
Node
----------- ---------- ---------- ------------------ ------------vs0
data1
up/up
192.0.2.120/24
node0
data2
up/up
192.0.2.121/24
node0
data3
up/up
192.0.2.122/24
node1
data4
up/up
192.0.2.123/24
node1
data5
up/up
192.0.2.124/24
node2
data6
up/up
192.0.2.125/24
node2
data7
up/up
192.0.2.126/24
node3
data8
up/up
192.0.2.127/24
node3
8 entries were displayed.

Current Is
Port
Home
------- ---e0e
e0f
e0e
e0f
e0e
e0f
e0e
e0f

true
true
true
true
true
true
true
true

You should record which LIFs have automatic rebalancing enabled so that you can reenable it
after the batch upgrade is completed.
3. Disable automatic LIF rebalancing for each LIF that you identified:
network interface modify * -allow-lb-migrate false

4. Return to the admin privilege level:

set -privilege admin

Release Candidate Documentation - Contents Subject To Change

Performing manual checks before an automated cluster upgrade | 11

Checking for back-end configuration errors before

downgrading
Before downgrading a storage system that uses array LUNs to an earlier release of ONTAP, you need
to run the storage errors show command to determine whether there are any back-end
configuration errors.
Steps

1. Enter the following command:

storage array config show

2. Based on the result of the previous step, proceed with one of the following options:
If...

Then...

If the storage array

config show output does
not instruct you to run
storage errors show

Proceed with downgrading

If the storage array

config show output does
instruct you to run storage
errors show

Continue to the next step

You are instructed to run the storage errors show command if ONTAP detects a back-end
configuration error that would prevent ONTAP and the back-end storage array from operating
together properly.
3. Enter the following command:
storage errors show

The storage errors show command provides details about the error at the array LUN level.
Example

DGC_RAID5_1
---------NAME (Serial #): This Array LUN is only available on one path.
Proper configuration requires two paths.

4. Fix the problems indicated by the storage errors show command, and then downgrade your
system.
The FlexArray Virtualization Installation Requirements and Reference Guide contains
explanations about errors shown in the storage errors show output and provides information
about how to fix them.

Release Candidate Documentation - Contents Subject To Change

12 | Upgrade Express Guide

Obtaining ONTAP software images

You must copy a software image from the NetApp Support Site to an HTTP or FTP server on your
network so that nodes can access the image.
About this task

To upgrade the cluster to the target release of ONTAP, you need access to software images. Software
images, firmware version information, and the latest firmware for your platform model are available
on the NetApp Support Site. Note the following important information:

Software images are specific to platform models.

Be sure to obtain the correct image for your cluster.

Software images include the latest version of system firmware that was available when a given
version of ONTAP was released.

Steps

1. Locate the target ONTAP software in the Software Downloads area of the NetApp Support Site.

NetApp Downloads
2. Copy the software image (for example, 900_q_image.tgz) from the NetApp Support Site to the
directory on the HTTP or FTP server from which the image will be served.
Related information

NetApp Downloads: Software

Release Candidate Documentation - Contents Subject To Change

13

Upgrading an ONTAP cluster nondisruptively by

using the automated method
The automated NDU method validates the cluster components to verify that the cluster can be
upgraded nondisruptively, installs the target 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

You must have satisfied upgrade preparation requirements.

For each HA pair, each node should have one or more ports on the same broadcast domain.
When a set of nodes is upgraded during a batch upgrade, the LIFs are migrated to the HA partner
nodes. If the partners do not have any ports in the same broadcast domain, then the LIF migration
fails.

Steps

1. If you do not plan to monitor the progress of the upgrade process, use the event route adddestinations command to send a notification if the upgrade encounters an error and requires
manual intervention.

Find more information about configuring the Event Management System.

Example

In this example, if the upgrade pauses due to an error, a notification will be sent to the test_dest
event destination:
cluster1::> event route add-destinations -messagename
upgrademgr.update.pausedErr -destinations test_dest

Alternatively, you can configure an AutoSupport message to send your internal support
organization. An AutoSupport message with the title AUTOMATED NDU PAUSED will be
sent in case of upgrade errors.

Find more information about configuring AutoSupport.

2. Trigger an AutoSupport notification:
autosupport invoke -node * -type all -message "Starting_NDU"

This AutoSupport notification includes a record of the system status just prior to upgrade. It saves
useful troubleshooting information in case there is a problem with the upgrade process.
If your cluster is not configured to send AutoSupport messages, a copy of the notification is saved
locally.
3. Download the target ONTAP software package:
cluster image package get -url location

The software package contains the target 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.

Release Candidate Documentation - Contents Subject To Change

14 | Upgrade Express Guide

Example
cluster1::> cluster image package get http://www.example.com/software/9.0/
image.tgz
Package download completed.
Package processing completed.

4. 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 Package Build Time
---------------- -----------------9.0
2/25/2016 10:32:15

5. 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 9.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
.
.
.

6. 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.
7. 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
ONTAP image on each node in the cluster, and then performs a nondisruptive upgrade in the
background. If an issue is encountered, the update pauses and prompts you to take corrective
action. You can use the cluster image show-update-progress command to view details
about any issues and the progress of the update. 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 is performed.
If the cluster consists of 8 or more nodes, a batch upgrade is performed by default. If desired, you
can use the -force-rolling parameter to specify a rolling upgrade instead.
Release Candidate Documentation - Contents Subject To Change

Upgrading an ONTAP cluster nondisruptively by using the automated method | 15

After completing each takeover and each giveback, the upgrade waits 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 9.0
Starting validation for this update. Please wait..
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 "Performing manual checks before an
automated cluster upgrade" section in the "Clustered Data ONTAP Upgrade
Express Guide" for the remaining manual validation checks that need to be
performed before update.
Failing to do so can result in an update failure or an I/O disruption.
Pre-update Check
--------------------Aggregate plex
resync status
Aggregate status
Broadcast Domain
status
CIFS status
Cluster health status
Cluster quorum status
Disk status
High Availability
status
LIF failover
LIFs not hosted
LIFs on home node
status
Manual checks

Status
Error-Action
---------- -------------------------------------------OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
OK
Warning

Warning: Manual validation checks need to

be performed. Refer to the Upgrade Advisor
Plan or "Performing manual checks before an
automated cluster upgrade" section in the
"Clustered Data ONTAP Upgrade Express
Guide" 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 "Performing manual checks before an
automated cluster upgrade" section in the
"Clustered Data ONTAP Upgrade Express
Guide" for the remaining validation checks
that need to be performed before update.

MetroCluster
OK
configuration status
NDMP status
OK
NFS netgroup check
OK
Platform status
OK
SAN status
OK
SnapMirror status
OK
Volume status
OK
Overall Status
Warning
20 entries were displayed
Would you like to proceed with update ? {y|n}: y
Starting update...
cluster-1::>

8. Optional: If necessary, manage the upgrade process:

Release Candidate Documentation - Contents Subject To Change

16 | Upgrade Express Guide

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

cluster image cancel-update

Note: You can only cancel

an upgrade if it is currently
paused.

9. Display the cluster update history to verify that the upgrade was completed successfully for each
node:
cluster image show-update-history
Example

The ONTAP version numbers in the following example are provided for example purposes only:
cluster1::> cluster image show-update-history
Package
Start
Completion
Status
Version
Time
Time
---------- --------- ---------- ---------successful 9.0.y
03/21/2016 03/21/2016
15:20:51
15:44:13
successful 9.0.y
03/21/2016 03/21/2016
15:20:51
16:03:20
2 entries were displayed.

Component ID
-----------node0

Previous
Version
--------8.3.x

Updated
Version
--------9.0.y

node1

8.3.x

9.0.y

10. Trigger an AutoSupport notification:

autosupport invoke -node * -type all -message "Finishing_NDU"

If your cluster is not configured to send AutoSupport messages, a copy of the notification is saved
locally.
Related information

ONTAP 9.0 Commands: Manual Page Reference

Release Candidate Documentation - Contents Subject To Change

17

Copyright information
Copyright 19942016 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval systemwithout prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Release Candidate Documentation - Contents Subject To Change

18

Trademark information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express,
Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash
Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale,
FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster,
MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,
SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive,
SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,
Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL and
other names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or
other countries. All other brands or products are trademarks or registered trademarks of their
respective holders and should be treated as such. A current list of NetApp trademarks is available on
the web.

http://www.netapp.com/us/legal/netapptmlist.aspx

Release Candidate Documentation - Contents Subject To Change

19

How to send comments about documentation and

receive update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can
receive automatic notification when production-level (GA/FCS) documentation is initially released or
important changes are made to existing production-level documents.
If you have suggestions for improving this document, send us your comments by email.

[email protected]
To help us direct your comments to the correct division, include in the subject line the product name,
version, and operating system.
If you want to be notified automatically when production-level documentation is released or
important changes are made to existing production-level documents, follow Twitter account
@NetAppDoc.
You can also contact us in the following ways:

NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.

Telephone: +1 (408) 822-6000

Fax: +1 (408) 822-4501

Support telephone: +1 (888) 463-8277

Release Candidate Documentation - Contents Subject To Change

20 | Upgrade Express Guide

Index
A

array LUNs, storage systems using

checking for back-end configuration errors before
downgrading 11
automated upgrades
performing nondisruptive cluster 13

feedback
how to send comments about documentation 19

B
back-end configurations
checking for errors before downgrading 11
batch upgrades
disabling automatic LIF rebalancing before 10

I
images, ONTAP software
obtaining 12
information
how to send feedback about improving
documentation 19

J
jobs

verifying status before upgrading or downgrading 9

cluster upgrades
performing nondisruptive, using automated method

13
requirements for 7
clusters
ensuring that no jobs are running before upgrading
or downgrading 9
introduction to upgrade requirements for 7
performing manual checks on before upgrade 6
update workflow for 5
verifying upgrade limits before upgrading 8
comments
how to send feedback about documentation 19
configuration requirements
for cluster upgrades 7
configurations
SAN, verifying prior to upgrade 9
configurations, back-end
checking for errors before downgrading 11

D
documentation
how to receive automatic notification of changes to

19
how to send feedback about 19
downgrades
checking for back-end configuration errors before
downgrading 11
reviewing resources before performing 6
dump operations
verifying job status before upgrading or
downgrading 9

E
errors, back-end configuration
checking for, before downgrading 11
express guides
requirements for using the Upgrade Express Guide 4

L
LIFs
disabling automatic rebalancing for 10
limits
verifying before a cluster upgrade 8

M
MetroCluster configurations
where to find procedures for upgrading 4
mixed version requirements
for cluster upgrades 7

N
NetApp Support Site
obtaining ONTAP software images 12
nondisruptive upgrades
guidelines for estimating the duration of 8
using automated method for cluster 13

O
ONTAP software images
obtaining 12

P
partitioning, root-data
upgrade considerations for 8
partitioning, root-data-data
upgrade considerations for 8
pre-downgrades
reviewing resources for 6
pre-upgrades
reviewing resources for 6

Release Candidate Documentation - Contents Subject To Change

Index | 21

how to receive automatic notification of

documentation changes 19

R
release requirements
for cluster upgrades 7
requirements
for cluster upgrades 7
verifying job status before upgrading or
downgrading 9
resources
reviewing before upgrading or downgrading 6
restore operations
verifying job status before upgrading or
downgrading 9
reversions
obtaining ONTAP software images 12
root-data partitioning
upgrade considerations for 8
root-data-data partitioning
upgrade considerations for 8

S
SAN
verifying configuration prior to upgrade 9
software images, ONTAP
obtaining 12
storage systems using array LUNs
checking for back-end configuration errors before
downgrading 11
suggestions
how to send feedback about documentation 19
system limits
verifying before a cluster upgrade 8

U
updates, cluster software
workflow for 5
upgrades
considerations for root-data partitioning and rootdata-data partitioning 8
guidelines for estimating the duration of 8
introduction to requirements for cluster 7
manual checks before an automated cluster update 6
obtaining ONTAP software images 12
performing nondisruptive cluster, using automated
method 13
requirements for cluster 7
reviewing resources before performing 6
verifying limits for cluster 8
verifying SAN configuration prior to 9
where to find procedures for upgrading manually 4

V
volumes
verifying volume status before upgrading or
downgrading 9

W
workflows
for cluster software updates 5

T
Twitter

Release Candidate Documentation - Contents Subject To Change