Académique Documents
Professionnel Documents
Culture Documents
Nondisruptive Upgrade
FAQ OVERVIEW
®
This document answers frequently asked questions about nondisruptive upgrade (NDU) of NetApp Data
®
ONTAP and associated firmware. NDU provides system, shelf firmware, and disk firmware upgrade
capabilities for NetApp storage controllers, disk shelves, and disks.
TABLE OF CONTENTS
2.3 WHAT ARE THE HARDWARE REQUIREMENTS FOR SYSTEM NDU? .................................................... 6
2.4 WHAT ARE THE SOFTWARE REQUIREMENTS FOR SYSTEM NDU? ..................................................... 6
2.7 WHAT ARE THE STEPS FOR MAJOR VERSION NDU IN NAS AND SAN ENVIRONMENTS? ................ 9
2 SYSTEM NDU
System NDU is a process that takes advantage of HA pair controller technology to minimize client disruption
during an upgrade of Data ONTAP or controller firmware.
System NDU entails a series of takeover and giveback operations that allow the partner nodes to transfer
the data delivery service while the controllers are upgraded, thereby maintaining continuous data I/O for
clients/hosts.
Because the controller for each node in the HA pair configuration is connected to both its own storage
shelves and the storage shelves of its partner node, a single node provides access to all volumes and LUNs,
even when the partner node is shut down. This procedure not only allows each node of HA pair controllers
to be upgraded individually to a newer version of Data ONTAP or firmware; it also provides the ability to
transparently perform hardware upgrades and maintenance on the HA pair controller nodes.
Prior to an NDU, all customers should create an NDU plan. An upgrade plan can be developed by using
™ ™
Upgrade Advisor, available on the NOW (NetApp on the Web) site, as part of My AutoSupport . Upgrade
Advisor is available for all systems reporting on AutoSupport.
8.0, 8.0.1 YES YES Customers upgrading from 8.0 to 8.x will
(CLUSTER- experience upgrades with the same amount of
MODE) disruption as 10.0 upgrades. For example, the
procedure and amount of disruption for a
customer upgrading from 8.0.1 to 8.0.2 would
be the same as when a customer upgrades
from 10.0.1 to 10.0.2.
8.0, 8.0.1 NO NO
(CLUSTER-
MODE)
FAS2020*
100 150 N/A N/A 150 N/A N/A
N3300*
FAS2040
N/A 200 200 200 200 200 200
N3400
FAS2050
100 150 N/A N/A 150 N/A N/A
N3600
FAS3040
150 150 500 500 150 500 500
N5300
FAS3140
150 150 500 500 150 500 500
N6040
FAS3160
200 300 500 500 200 500 500
N6060
FAS3070 250 300 500 500 300 500 500
* Major NDU from Data ONTAP 7.2.2L1 to 7.3.1 is not supported on FAS2020/IBM N3300 systems that
contain aggregates larger than 8TB. Therefore, a disruptive upgrade is required. Aggregates larger than 8TB
prevent the ability to perform a minor version NDU from Data ONTAP 7.2.2L1 to 7.2.x.
** The 500 FlexVol volumes limit per controller matches the native Data ONTAP FlexVol volume limit. Fields
that contain N/A in this column indicate platforms that are not supported by Data ONTAP 8.0.
Note: Data ONTAP versions that are followed with an ―x‖ indicate that all versions of Data ONTAP in that
family have the same limitations. For example, the 7.3.x column in the preceding table defines the limitations
for 7.3.1, 7.3.2, and 7.3.3 up to 7.3.x.
2.7 WHAT ARE THE STEPS FOR MAJOR VERSION NDU IN NAS AND SAN
ENVIRONMENTS?
The following steps govern a major version NDU in a NAS and SAN environment:
1. For systems running Data ONTAP versions earlier than 7.2.4, create an AutoSupport notification by
entering the options autosupport.doit starting_NDU command at the console of each
storage system controller. This creates a record of the system status just before upgrade and
saves useful troubleshooting information in case there is a problem during the upgrade process.
2. Verify that controller failover is enabled on the HA pair partners by issuing the command cf
status. If the command output lists Cluster disabled, determine the cause, address it, and
then enable controller failover by issuing the cf enable command.
3. Determine whether automatic giveback is active by executing the command options
cf.giveback.auto.enable. If enabled, disable it with the command options
cf.giveback.auto.enable off.
4. Verify that CPU utilization and disk utilization are both below 50%. Enter the command sysstat -
c 10 -x 3 on each controller in the HA pair. Confirm that the values in the CPU and Disk Util
columns remain below 50% for all 10 measurements reported. Make sure that no additional load is
added to the system throughout the NDU process.
5. Perform the software installation operation of the new version of Data ONTAP on both storage
controllers.
6. Issue the download command on both controllers to update the compact flash boot media. You
can also use the software update -r command instead of software install followed by
the download command, but you must include the -r flag to control when the controller reboot
occurs.
7. Confirm that controller failover is enabled and that CPU utilization and disk I/O do not exceed 50%
per controller.
8. Issue the cf takeover command on controller A (do not use the -f parameter). Controller B
shuts down cleanly and reboots.
9. When controller B displays Waiting for giveback, issue the cf giveback command on
controller A to return controller B’s data service.
10. Controller B is now running the new version of Data ONTAP and controller A the old version.
11. Issue the cf takeover -n command on controller B. The -n parameter applies only to major
version NDU operations. The following message appears: ―Waiting for partner to be
cleanly shutdown using the 'halt' command. Press Ctrl-C to abort wait...‖.
12. Issue the halt command on controller A to shut it down cleanly. When controller B detects that
controller A is shut down cleanly, it initiates a takeover. System BIOS, RLM, or BMC firmware can
be upgraded while controller A is down. You can also use this opportunity to perform hardware
maintenance or upgrades, if necessary.
13. When takeover and any additional maintenance operations are completed, issue the boot_ontap
or bye command on controller A.
14. When controller A displays the message ―Waiting for giveback,‖ issue the cf giveback
command on controller B.
LRC, ESH, ESH2, and ESH4 controller module firmware upgrades are nondisruptive.
AT-FC and AT-FC2 module firmware upgrades are disruptive.
AT-FCx modules incur two 70-second pauses in I/O for all storage (FC or SATA) attached to the
system.*
IOM (SAS) modules in a FAS2000 incur two 40-second pauses in I/O if running firmware versions prior
to 5.0 for all storage (SAS, FC, or SATA) attached to the system. For firmware version 5.0 and later, the
pauses in I/O are greatly reduced but not completely eliminated.
IOM (SAS) modules in DS4243 firmware upgrades are nondisruptive.
* AT-FCX NDU functionality is available with the release of Data ONTAP 7.3.2 when using AT-FCx firmware
version 37 or later. For more information, refer to KB article 46668 on the NOW site.
ALTERNATE APPROACH
If your system is configured as multipath HA, the loss of either A or B loops does not affect the ability to
serve data. Therefore, by employing another (spare) storage controller, you can upgrade all your AT-FCx
modules out of band. You remove them from your production system and put them in your spare system in
order to conduct the upgrade there. The pause in I/O then occurs on the spare (nonproduction) storage
controller rather than on the production system.
This approach does not eliminate the risk of latent shelf module failure on the systems in which modules are
being swapped in or the risk of running different shelf controller firmware, even if only for a short time.
Nondisruptive upgrades are performed by downloading the most recent firmware from the NOW site to the
controller's /etc/acpp_fw directory. Updates start automatically for any ACP that is eligible for an update.
Data ONTAP polls approximately once every 10 minutes to detect new firmware in the /etc/acpp_fw
directory. An automatic NDU firmware update can occur from the new firmware being downloaded onto
either node in the /etc/acpp_fw directory.
To upgrade ACP firmware manually, you must download the most recent firmware from the NOW site to the
controller's /etc/acpp_fw directory. The storage download acp command is used to initiate the ACP
firmware upgrade. It downloads the firmware to all ACPs in an active state unless a specific ACP is identified
using the storage download acp command.
As with other firmware downloads, ACP firmware download does not require the cluster to be enabled. ACP
firmware download can be executed during a takeover in an HA pair.
The RLM is a remote management card that is installed in FAS3000 and FAS6000 series controllers to
provide remote platform management capabilities such as remote platform management, remote access,
monitoring, troubleshooting, and logging. The RLM is operational regardless of the state of the controller and
is available so long as the controller has input power. The RLM firmware can be updated by the Data
ONTAP command line interface or the RLM command line interface. Both procedures are nondisruptive
upgrades of the RLM firmware.
Nondisruptive upgrades are performed by downloading the latest RLM firmware from the NOW site to a Web
server on a network accessible by the controller. Once the firmware has been downloaded there are two
methods by which the firmware can be downloaded to the RLM. The first method uses the Data ONTAP
command line interface. From the controller console issue the command software install
http://web_server_name/path/RLM_FW.zip -f to install the firmware. The installation may take up
to 30 minutes to complete. To update the files after installation, use rlm update –f. The other method
for updating the RLM firmware is from the RLM command line interface. Log in to the RLM and update the
files on the RLM by accessing the saved firmware files on the Web server, RLM update
http://web_server_ip_address/path/RLM_FW.tar.gz -f, and then reboot the RLM, rlm
reboot.
NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any
information or recommendations provided in this publication, or with respect to any results that may be
obtained by the use of the information or observance of any recommendations provided herein. The
information in this document is distributed AS IS, and the use of this information or the implementation of
any recommendations or techniques herein is a customer’s responsibility and depends on the customer’s
ability to evaluate and integrate them into the customer’s operational environment. This document and
the information contained herein may be used solely in connection with the NetApp products discussed in
this document.
© 2011 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp,
Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, AutoSupport, Data ONTAP,
FilerView, FlexCache, FlexVol, MetroCluster, NOW, RAID-DP, SyncMirror, and WAFL are trademarks or registered trademarks of
www.netapp.com 14 NetApp,
Nondisruptive Inc. in
Upgrade the United States and/or other countries. All other brands or products are trademarks
FAQ or registered
NetApp Confidential trademarks
– Limited UseofOnly
their respective holders and should be treated as such.