This topic treats about disruptive Data ONTAP 7-Mode upgrade on single node instance.
Check another post with information What should we do before upgrade?
Data ONTAP 7-Mode disruptive upgrading on standalone system – upgrade step by step
Just before you start with below plan ensure that everything on filer are online (disks, volumes, aggregates, interfaces) and there are no maintenance jobs running like RAID scrubbing, reconstructions or disk wiping.
1) Monitor performance:
filer1> sysstat -c 30 -x 3
Even when we are upgrading Data ONTAP in single node we should care about CPU and Disk utilization. For example during my last minor upgrade on FAS3220 I had CPU utilization around 20% and disk utilization between 40-50%. After upgrade for few hours I had have experienced big load on disks, up to 100%. And that was nothing to do with disk fw upgrade, but probably with some changes/block reallocations in WAFL.
2) Trigger AutoSupport on both filers. Notification is send immediately and subject makes clear view on our actions
filer1> options autosupport.doit "starting_NDU 8.X.XPX"
3) Install the system files using the software command on both filers
filer1> software update 8XXPX_q_image.tgz –r
Output that you see should be similar:
software: You can cancel this operation by hitting Ctrl-C in the next 6 seconds. software: Depending on system load, it may take many minutes software: to complete this operation. Until it finishes, you will software: not be able to use the console. Software update started on node filer1. Updating image2 package: file://localhost/mroot/etc/software/8XXPX_q_image.tgz current image: image1 Listing package contents. Decompressing package contents. Invoking script (validation phase). INSTALL running in check only mode Mode of operation is UPDATE Current image is image1 Alternate image is image2 Available space on boot device is 1683 MB Required space on boot device is 317 MB Kernel binary matches install machine type Package MD5 checksums pass Versions are compatible Invoking script (install phase). This may take up to 30 minutes. Mode of operation is UPDATE Current image is image1 Alternate image is image2 Available space on boot device is 1683 MB Required space on boot device is 317 MB Kernel binary matches install machine type Package MD5 checksums pass Versions are compatible Getting ready to install image Syncing device... Extracting to /cfcard/x86_64/freebsd/image2... x BUILD x CHECKSUM x COMPAT.TXT x INSTALL x README.TXT x VERSION x cap.xml x diags.tgz x kernel x perl.tgz x platform.ko x platfs.img x rootfs.img Installed MD5 checksums pass Installing diagnostics and firmware files Installation complete. image2 updated on node filer1. image2 will be set as the default boot image after a clean shutdown. software: installation of 8XXPX_q_image.tgz completed. Mon May 13 09:57:46 CET [filer1:cmds.software.installDone:info]: Software: Installation of 8XXPX_q_image.tgz was completed. Please type "reboot" for the changes to take effect.
4) Take care of snapmirror if you have source and destination volumes on your system (optional step). Decide whether you want to wait until current transfers are finished.
4.1) Look for any ongoing transfers, nice to have some management server to use grep
unix-mgmt> ssh filer1 snapmirror status |grep Transferring
If you don’t care whether current update finish job then go with
filer1> snapmirror abort dest_vol
In other case use quiesce and wait for the whole update
filer1> snapmirror quiesce dest_vol
If you know that more relationships have scheduled for next hour then do quiesce to them as well.
4.2) Turn off snapmirror
filer1> snapmirror off
5) Terminate CIFS (optional step, also because during reboot services are anyway gracefully shutdown)
filer1> cifs terminate
6) Check the current version of ONTAP
7) Check performance statistics
filer1> sysstat -c 30 -x 3
And now probably you see high disk utilization. It means that your disk firmware is during update or some WAFL blocks reallocation has place. Anyway, it could take few hours before your system go back to fully operational status.
8) Turn on snapmirror
filer1> snapmirror on
and also quiesced SM has to be resumed
filer1> snapmirror resume dest_vol
9) Trigger post-upgrade AutoSupport
filer1> options autosupport.doit “finishing_NDU 8.X.XPX”
10) Confirm that all paths to disk are visible to the system by entering the following command
filer1> storage show disk -p
11) Confirm that there are no failed disks by entering the following command
filer1> vol status -f
12) Verify that all aggregates are online by entering the following command
filer1> aggr status
13) Confirm that network interfaces are online by entering the following command
filer1> ifconfig -a
What else is worth to know?
- Before you perform any implementation verify your plan with NetApp tool called Upgrade Advisor. In most cases it will help you determine the required steps. But be aware that you always have to think about your production environment to be not surprised in case of something goes wrong. That lead us to the next point, which is..
- Reverse plan – if you like your job, always ensure that you have backout plan. In terms of backout plan you have to turn off most of the features and make sure that the downgrade do not require any additional changes in system.
- Currently with firmware version of Data ONTAP, firmware for disks and disk shelves is bundled with system files. After filer reboot automatically firmware for disks and disk shelves is installed.