Please follow these steps to upgrade your system(s): netapp2040-2: upgrade plan8.0.

1RC1

8.1

1.

Be sure to read the Release Notes as well as the Upgrade Guide of the Data ONTAP 8.1 for important information and technical detail before beginning your upgrade. Before upgrading Data ONTAP, monitor CPU and disk utilization for 30 seconds by entering the following command at the console of each storage controller:

sysstat -c 10 -x 3
The values in the CPU and Disk Util columns are strongly recommended not to exceed 50% for all ten measurements reported. Ensure that no additional load is added to the storage system until the upgrade completes. Download perfstat and run it on a client as follows:

perfstat -f filername -t 4 -i 5 > perfstatname.out

2. Save this output file for a couple of weeks after the upgrade is complete Ensure all SnapDrive for Windows clients are running one of the supported versions for 8.1: Download the system files for 8.1 (81_e_image.tgz) from the Support Site. Be sure to download the system files that match your node model. If you are performing a Data ONTAP NDU (or backout), you must perform this step on both nodes before performing the takeover and giveback steps. Verify the checksum of the image file with the value on the Support site. Connect to the console of the node and trigger an AutoSupport:

3.

4. 5. 6.

netapp2040-2> options autosupport.doit starting_NDU

Contact NetApp Support and check /etc/messages for any obvious errors; e.g. disk errors, firmware errors, etc. Using Windows: Map C$ to the Windows Host Browse theetcfolder Open file 'messages' using WordPad. If failed disks are found, it is recommended they be removed before upgrading. Back up theetc\hostsandetc\rcfiles in Windows to a temporary directory. Copy the system image file (81_e_image.tgz) to the /etc/softwaredirectory on the node. From a Windows box as an Administrator: o Map theC$share to a Windows drive letter (for example X:). o Copy the image file toX:\etc\software Install the system file via the software command:

7. 8.

9.

netapp2040-2> software update 81_e_image.tgz -r

If you are performing a Data ONTAP NDU (or backout), you must perform this step on both nodes before performing the takeover and giveback steps. 10. Check to see if the boot device has been properly updated:

netapp2040-2> version -b
The primary kernel should be 8.1. Download and install the latest disk firmware from the Support site. Instructions for installing the firmware files are included on the download page. When performing a nondisruptive upgrade, NetApp recommends upgrading disk firmware the day before upgrading Data ONTAP. 12. Terminate CIFS on the node to be taken over ( netapp2040-1 ):

11.

13.

netapp2040-1> cifs terminate

For each destination volume, enter the following command to allow existing SnapMirror relations to complete:

netapp2040-2> snapmirror quiesce Your Destination here

Example To quiesce relations to the destination volume fas270cl1-cn:vol1, enter the following command:

netapp2040-2> snapmirror quiesce fas270cl1-cn:vol1

Enter the following command on both source and destination systems to disable SnapMirror operations:

14.

netapp2040-2> snapmirror off

Takeover and giveback sequence between nodes Terminate CIFS on the node to be taken over (netapp2040-1): netapp2040-1>cifs terminate From netapp2040-2:, take over the data service from the partner node netapp2040-1:

netapp2040-2> cf takeover netapp2040-2> cf giveback

After netapp2040-1: reboots and displays "waiting for giveback", give back the data service: Terminate CIFS on the node to be taken over ( netapp2040-2 ):

netapp2040-2> cifs terminate

From the newly upgraded node netapp2040-1, take over the data service from netapp2040-2: netapp2040-1cf takeover -n Halt, and then restart the first node:

netapp2040-2> halt netapp2040-2> bye

After the first node reboots and displays "waiting for giveback", give back the data service:

netapp2040-1> cf giveback
For SAN environments, wait at least 10 minutes between takeover and giveback events. Attention: The giveback is not initiated and an error message is returned if any conditions such as the following are detected: - open client sessions (such as CIFS sessions) - long-running operations - operations that cannot be restarted (such as tape backup or SyncMirror resynchronization) - error conditions (such as disk connectivity mismatch between the nodes) If giveback is not initiated, complete the following steps: 1. Address the condition described in the error message, ensuring that any identifiedoperations are terminated gracefully. 2. Enter the cf giveback command with the -f option:

cf giveback -f

15.

For more information about the -f option, see the cf(1) man page. Enter the following command to re-enable SnapMirror:

netapp2040-2> snapmirror on
Enter the following command to resume existing SnapMirror relations:

16.

netapp2040-2> snapmirror resume Your Destination here

Verify the upgrade completed successfully to 8.1:

netapp2040-2> version

17.

18.

Upgrade netapp2040-1 (if not already done) Connect to the console of the node and trigger an AutoSupport

netapp2040-2> options autosupport.doit finishing_NDU

netapp2040-2: back-out plan8.1

8.0.1RC1

1.

2.

Ensure all SnapDrive for Windows clients are running one of the supported versions for 8.0.1RC1 7-Mode: Download the system files for 8.0.1RC1 7-Mode (801RC1_e_image.tgz) from the Support Site. Be sure to download the system files that match your node model. If you are performing a Data ONTAP NDU (or backout), you must perform this step on both nodes before performing the takeover and giveback steps. Verify the checksum of the image file with the value on the Support site. Connect to the console of the node and trigger an AutoSupport using the following command:

3. 4. 5.

netapp2040-2> options autosupport.doit "Reverting to 8.0.1RC1 7-Mode"

Contact NetApp Support and check /etc/messages for any obvious errors; e.g. disk errors, firmware errors, etc. Using Windows: Map C$ to the Windows Host Browse theetcfolder Open file 'messages' using WordPad. If failed disks are found, it is recommended they be removed before upgrading. Back up theetc\hostsandetc\rcfiles in Windows to a temporary directory. Copy the system image file (801RC1_e_image.tgz) to the /etc/softwaredirectory on the node. From a Windows box as an Administrator: o Map theC$share to a Windows drive letter (for example X:). o Copy the image file toX:\etc\software Install the system file via the software command:

6. 7.

8.

netapp2040-2> software update 801RC1_e_image.tgz -r

If you are performing a Data ONTAP NDU (or backout), you must perform this step on both nodes before performing the takeover and giveback steps. Check to see if the boot device has been properly updated:

9.

netapp2040-2> version -b
The primary kernel should be 8.0.1RC1 7-Mode. Download and install the latest disk firmware from the Support site. Instructions for installing the firmware files are included on the download page. When performing a nondisruptive upgrade, NetApp recommends upgrading disk firmware the day before upgrading Data ONTAP. 11. Disable the data service:

10.

12.

netapp2040-2> cf disable
Run the revert_to command:

netapp2040-2> revert_to 8.0.1RC1 7-Mode

At the end of revert, the system will automatically halt itself and drop to a loader prompt. Once at a loader prompt, you can issue eitherbyeorrebootto bring the system back up 13. Reboot the node:

14. 15.

netapp2040-2> reboot
Enable the cluster (if both sides are downgraded):

netapp2040-2> cf enable
Verify the upgrade completed successfully to 8.0.1RC1 7-Mode:

netapp2040-2> version