The following sections discuss upgrade issues that you must resolve before upgrading to the Data ONTAP 6.5 release family:
The following sections discuss new behavior in systems that have been upgraded to the Data ONTAP 6.5 release family:
If you are upgrading Data ONTAP software in systems with DS14 or DS14Mk2 disk shelves, including FAS200 series systems, and you are currently running a version of Data ONTAP that does not include a fix for Bug ID 113823, do not update disk firmware before upgrading, or you could risk data loss. Instead, upgrade your Data ONTAP software to a release that contains a fix for Bug ID 113823 first, then update disk firmware.
For a list of Data ONTAP versions in which Bug ID 113823 has been fixed, see the following URL:
http://now.netapp.com/NOW/cgi-bin/bugrellist?bugno=113823
Disk firmware is automatically updated on reboot as part of the Data ONTAP upgrade whenever the disk drives are running firmware older than the firmware version that is included with the Data ONTAP release. As disk firmware is updated, it is possible (though unlikely) that all disk drives on a shelf will receive the update at the same time. This simultaneous update might cause the firmware update process to fail, rendering the disks unusable and causing loss of data if it happens to multiple disks in the same RAID group.
Data ONTAP 6.5.2 fixes Bug ID 113823 by preventing firmware from being concurrently updated on all disk drives. For more information about this issue, see the description for Bug ID 113823, on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=113823
Note
Bug ID 113823 occurs only when every disk drive on the shelf requires an update.
If you are upgrading Data ONTAP software in clustered systems with DS14 or DS14Mk2 disk shelves, and you are currently running a version of Data ONTAP that does not include a fix for Bug ID 113823, do not update disk firmware before attempting a nondisruptive upgrade. If you determine that upgrading to Data ONTAP 6.5.2 will load new disk firmware onto your systems, you must perform a standard upgrade, which is the safe and recommended method to correct the problem for clustered filers. For more information, see Planning for upgrading clusters.
If you have Autosupport enabled, you can use the Autosupport analysis tool, available on the NOW My Installed Products page, to verify your disk firmware version in advance and find out whether your system is vulnerable to Bug ID 113823. If the Autosupport analysis indicates that all disks on a disk shelf need firmware updates, failure to upgrade software before updating firmware could cause disk drive damage and data loss.
For instructions about using the Autosupport analysis tool to detect disk firmware requirements, see Detecting outdated disk firmware.
For NetApp filers that have CompactFlash cards and that run Open Firmware (OFW), you must upgrade the system firmware and diagnostics files to version 4.2.2 or later before upgrading to the Data ONTAP 6.5 release family. The Data ONTAP 6.5 image will not fit on the 32 MB CompactFlash cards as they are currently formatted. If you attempt to download Data ONTAP 6.5.x on your filer before upgrading to firmware version 4.2.2 or later, the download will stop and the filer will display a message similar to the following:
download: Failed to repartition the card.
download: The current firmware version does not support repartitioning of the boot device as required.
download: Please update your system firmware to 4.2.2 or later prior to upgrading to this OS. The System Firmware area on the NOW site has further information.
Review the following issues before upgrading system firmware.
The following filers must be running firmware version 4.2.2 or later before upgrading to the Data ONTAP 6.5 release family:
You can find filer system firmware on the NOW site at http://now.netapp.com/NOW/download/tools/serviceimage/. Follow the instructions there to download and install the latest filer system firmware.
If you are running Data ONTAP 6.4.1 on a filer that has a CompactFlash card and that runs Open Firmware (OFW), you must complete an additional procedure to manually format the service partition before upgrading the firmware to version 4.2.2 or later. If you do not complete this procedure, your filer will be unable to upgrade to 4.2.2 and future firmware releases. For more information, see the BURT 98952 public report on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=98952
This caution applies to the following filers running Data ONTAP 6.4.1 before upgrading to the Data ONTAP 6.5 release family:
You can find the NetApp OFW/Diagnostics Download Instructions for CompactFlash Units and firmware/diagnostics images on the NOW site at http://now.netapp.com/NOW/download/tools/serviceimage/30800128/.
If you are running a version of Data ONTAP earlier than 6.4.2 on filers that have a CompactFlash card, you must install Data ONTAP 6.4.2 or the latest Data ONTAP 6.4.x version, before upgrading to the Data ONTAP 6.5 release family. If you attempt to download Data ONTAP 6.5.x on your filer before installing the latest version of Data ONTAP 6.4.x, the download will stop and the filer will display a message similar to the following:
download: The boot image is larger than the primary boot device (23068672 bytes instead of 11534336).
download: Reformatting boot device.
download: Unable to reformat the boot device. download failed. Cannot boot off disks with latest image
The following filers must be running Data ONTAP 6.4.2 or later before upgrading to the Data ONTAP 6.5 release family:
You can download the latest release of Data ONTAP 6.4.x from the Download Software page (on the NOW site at http://now.netapp.com/NOW/cgi-bin/software/). Under Data ONTAP, select your platform, then select View & Download under the latest Data ONTAP 6.4.x release and follow the instructions.
To upgrade your filer software, follow the instructions specific to your filer in Upgrading Filer Software.
If you are upgrading a diskette-based filer from a version of Data ONTAP earlier than 6.2, NetApp recommends that you upgrade to Data ONTAP 6.3.3 or the latest 6.3.x release first before upgrading to the Data ONTAP 6.5 release family.
By upgrading in two steps, you reduce the number of Redundant Array of Independent Disks (RAID) and Write Anywhere File Layout (WAFL) changes. As a result, the upgrade from Data ONTAP 6.3.3 to 6.5 should finish sooner with less risk of problems.
NetApp recommends that the following filers upgrade to Data ONTAP 6.3.3 or the latest 6.3.x release before upgrading to the Data ONTAP 6.5 release family:
You can download Data ONTAP 6.3.3 from the Download Software page (on the NOW site at http://now.netapp.com/NOW/cgi-bin/software/). Under Data ONTAP, select your platform, then select View & Download under the Data ONTAP 6.3.3 release and follow the instructions.
When you upgrade to the Data ONTAP 6.5 release family, Network Appliance recommends that you configure your Fibre Channel-Arbitrated Loop (FC-AL) adapters to run in 1-Gb and 2-Gb mode by changing the jumpers on the adapter. During the mandatory firmware upgrade, Network Appliance also recommends that you upgrade system firmware to 4.2.3 or later in order to be compatible with the new 1-Gb and 2-Gb setting.
Note
Do not apply any configuration changes to FCP target-mode adapters.
FC-AL adapters configured for 1-Gb operations will continue to work in a Data ONTAP 6.5 or later environment without resetting the jumpers or upgrading firmware. However, Network Appliance recommends 1-Gb and 2-Gb mode for optimal operation of these adapters.
Complete this procedure if your FC-AL adapters have the following marketing and spare part numbers:
To reconfigure your FC-AL adapters and upgrade firmware, complete the following steps.
FC-AL adapters can be installed on the following filers:
Open Systems SnapVaultTM (OSSV) Agent 1.0 is incompatible with the Data ONTAP 6.5 release family. If you are upgrading to Data ONTAP 6.5.x and you are using OSSV Agent 1.0, you must upgrade OSSV Agent to version 1.1. You can find OSSV Agent 1.1 on the Download Software page on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/software
NetApp recommends that you upgrade the OSSV agent on your host platform before upgrading your filer to the Data ONTAP 6.5 release family.
SecureAdminTM 2.2.1 and earlier software is incompatible with Data ONTAP 6.4 and later. If your filer is licensed for SecureAdmin and you are upgrading to the Data ONTAP 6.5 release family, you must be running SecureAdmin 3.0 or later. If you need to upgrade SecureAdmin, you can find it on the Download Software page on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/software
NetApp recommends that you upgrade SecureAdmin on your host platform after upgrading your filer to the Data ONTAP 6.5 release family.
Caution
Failure to upgrade to SecureAdmin 3.0 will cause your filer to lose its SecureAdmin capabilities.
If you are upgrading to Data ONTAP 6.5.2 in a Storage Area Network (SAN) with Solaris Fibre Channel hosts and you are using the NetApp-supplied Array Support Library (ASL) 1.0, you must upgrade to version 2.0 of the ASL before upgrading to Data ONTAP 6.5.2.
For more information, see the SAN Host 1.3 for Fibre Channel on Solaris Release Notes.
The Data ONTAP 6.5 release family provides support for larger inodes. For the smoothest conversion to larger inodes, keep the following tips in mind before upgrading to Data ONTAP 6.5.x:
Note
Upgrading to the Data ONTAP 6.5 release family can take significantly longer to complete than upgrades to earlier releases. Depending on your system, the 6.5 upgrade can take several hours. During the upgrade, the filer will continue to serve data.
After upgrading to the Data ONTAP 6.5 release family, you might observe disk LEDs blinking on an apparently idle system. You might also observe some CPU activity even when there is no user workload present. This is due to a default "media scrub" background process that continuously finds and cleans media errors on the filer disks. This process is designed to work in self-throttling mode with negligible impact on filer performance.
In the Data ONTAP 6.5 release family, access rules in the /etc/exports file have changed. Rules that previously allowed read access to all hosts have been changed to allow no access. For example, this is a rule in pre-6.5 versions of Data ONTAP:
/vol/vol1 -rw=host1:host2
The rule meant that the hosts named host1 and host2 both had read-write access to vol1, while all other hosts had read access.
In the Data ONTAP 6.5 release family, however, the rule now means that host1 and host2 have read-write access and all other hosts have no access. In order to allow read access for all hosts in 6.5, you need to add -ro after vol1 to allow read access to all hosts:
/vol/vol1 -ro,rw=host1:host2
The first time you upgrade to Data ONTAP 6.5.x, the /etc/exports file is changed automatically to be sure your rules work the same way. The rule /vol/vol1 -rw=host1:host2 is converted to the form /vol/vol1 -ro,rw=host1:host2.
When subsequent upgrades are performed, Data ONTAP assumes that the rules in the /etc/exports file have already been converted and additional conversions do not take place.
Other changes to the /etc/exports file in the Data ONTAP 6.5 release family include the following:
The -access option was used to list hosts that could have any access. Instead, the -rw and -ro options are used together to enable the same privileges.
When you upgrade to the Data ONTAP 6.5 release family, your existing volumes will be configured with RAID 4 protection and the existing volume's raidsize option, which controls the size of new RAID groups that might be created in the volume, will be changed to the default RAID 4 group size for your model appliance.
These are the default and maximum RAID 4 group sizes for NetApp appliances:
The sizes of existing volumes' RAID groups will remain the same as before the Data ONTAP 6.5.x upgrade, even if the size exceeds the new limits; however, the raidsize option will change to the new, reduced limit, and any new RAID groups that are created as disks are added to the volumes will conform to the new raidsize option.
An R150 running Data ONTAP 6.4 has a volume RAID group size of 8. When the appliance is upgraded to Data ONTAP 6.5.x, raidsize is changed to 6, the new limit.
After the upgrade to the Data ONTAP 6.5 release family, if you have volumes with RAID 4 groups whose size exceeds the new RAID 4 limit, Network Appliance strongly recommends that you upgrade to RAID DP protection for those volumes. For volumes with oversized RAID groups, Data ONTAP issues a daily message similar to the following:
Wed Oct 1 03:44:51 GMT [raid.config.rg.size.reminder:warning]: vol1 has a raid group larger than the limit for raid4 raidtype (max. raid group size: 7, limit is 6). Convert the volume to raid_dp.
Note
Converting from RAID 4 to RAID DP could take one or more hours depending on the volume size and underlying RAID groups. During this time, performance might be degraded. Network Appliance therefore recommends that you schedule conversions from RAID 4 to RAID DP during non-peak hours.
To convert the RAID protection from RAID 4 to RAID DP, complete the following steps.
Default and maximum RAID DP group sizes for the Data ONTAP 6.5 release family are as follows:
For more information, see the Storage Management Guide.
If you upgrade from the Data ONTAP 6.4 release family and you have Challenge Handshake Authentication Protocol (CHAP) configured for iSCSI, the CHAP configuration from the previous release is not saved.
The CHAP configuration file in Data ONTAP 6.5 and later uses a new format that is not compatible with the CHAP configuration file format of previous releases. When you upgrade, you must use the iscsi security command to reconfigure CHAP settings.
For information about using the iscsi security command, see the Block Access Management Guide for iSCSI.
Data ONTAP 6.5.2 includes a fix for bug 129083, which made it possible for NFS exports to be improperly rendered inaccessible after Data ONTAP is restarted.
If you modified the value of the nfs.export.neg.timeout option as a workaround for this problem in an earlier Data ONTAP 6.5.x release, you can reset this option to its default value (1800), or any other value you used for this option before applying the workaround.
Leaving the lowered (workaround) option value may cause an increase in name-service traffic when many clients attempt to access resources for which they do not have permissions.
To restore the default option value for caching of denied NFS requests, complete the following step:
Copyright © 1994-2004, Network Appliance, Inc. All rights
reserved.
Part No. 215-01027
File: upgrade7.htm
Last updated: Mon Jul 12 17:06:05 2004