This section discusses upgrade issues that you should be aware of if you are upgrading from releases earlier than Data ONTAP 6.5.
The following sections discuss upgrade issues that you must resolve before upgrading to the Data ONTAP 7.1 release family from releases earlier than Data ONTAP 6.5:
The following sections discuss new behavior in systems that have been upgraded to the Data ONTAP 7.1 release family from releases earlier than Data ONTAP 6.5:
For storage systems 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 7.0 release family. Data ONTAP images for release later than 6.5 will not fit on the 32-MB CompactFlash cards as they are currently formatted. If you attempt to download Data ONTAP 6.5 or later on your storage system before upgrading to firmware version 4.2.2 or later, the download will stop and the storage system 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.
Note
If you are running an OFW release earlier than 4.2.2, make sure that you upgrade to firmware version 4.3 or later. Do not install firmware version 4.2.2 or 4.2.3.
If you are running OFW release 4.2.2 or 4.2.3, make sure that you upgrade to firmware version 4.3 or later to correct Bug ID 105365. This bug can prevent the system from booting after running the update-flash command. For more information, see Bug ID 105365 (on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=105365).
Review the following issues before upgrading system firmware.
The following storage systems must be running firmware version 4.2.2 or later before upgrading to the Data ONTAP 7.0 release family:
You can find 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 system firmware.
If you are running Data ONTAP 6.4.1 on a storage system that has a CompactFlash card and that runs OFW, you must complete an additional procedure to manually format the service partition before upgrading the system firmware to version 4.3 or later. If you do not complete this procedure, your storage system will be unable to upgrade to 4.3 and future firmware releases. For more information, see Bug ID 98952 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 storage systems running Data ONTAP 6.4.1 before upgrading to the Data ONTAP 7.0 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 storage systems that have a CompactFlash card, you must install Data ONTAP 6.4.2 or the latest Data ONTAP release in the 6.4 family, before upgrading to the Data ONTAP 7.0 release family. If you attempt to download Data ONTAP 6.5 or later on your storage system before installing the latest version in the Data ONTAP 6.4 family, the download will stop and the storage system 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 storage systems must be running Data ONTAP 6.4.2 or later before upgrading to the Data ONTAP 7.0 release family:
You can download the latest release in the Data ONTAP 6.4 family 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 family release and follow the instructions.
To upgrade your storage system software, follow the instructions specific to your storage system in Chapter 4, Upgrading Data ONTAP Software.
Open Systems SnapVault Agent 1.0 is incompatible with Data ONTAP 6.5 and higher. If you are upgrading to the Data ONTAP 7.0 release family and you are using Open Systems SnapVault Agent 1.0, you must upgrade Open Systems SnapVault Agent to version 1.1 or higher.
You are advised to upgrade the Open Systems SnapVault agent on your host platform before upgrading your storage system to the Data ONTAP 7.0 release family.
To download Open Systems SnapVault agent software from the NOW site to your host platform, complete the following steps.
The Data ONTAP 6.5 release family introduced support for larger inodes. For the smoothest conversion to larger inodes, keep the following tips in mind before upgrading to the Data ONTAP 7.0 release family from a release earlier than 6.5:
Because of large inode support, upgrading to Data ONTAP 6.5 or later can take significantly longer to complete than upgrades to releases earlier than 6.5. Depending on a number of factors--particularly hardware platform, total number of inodes, and percentage of inodes in use--such an upgrade can take anywhere from a few minutes to several hours. For example, upgrading a FAS980 system with 95.6 million inodes, 73% of which are in use, takes around 67 minutes to complete. (These figures represent guidelines based on NetApp customer configurations. Your system upgrade time could differ based on system load and other factors in your environment.)
Note
During the upgrade, the storage system will continue to serve data. Data ONTAP upgrades takes place in the background, so the system is completely available during the upgrade.
After upgrading to the Data ONTAP 7.0 release family from a release earlier than 6.5, 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 storage system disks. This process is designed to work in self-throttling mode with negligible impact on storage system performance.
Beginning with the Data ONTAP 6.5 release family, access rules in the /etc/exports file were changed. Rules that previously allowed read access to all hosts have been changed to allow no access. For example, this is a rule in versions of Data ONTAP earlier than 6.5:
/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 Data ONTAP 6.5 and later releases, 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 Data ONTAP 6.5 and later, 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 the Data ONTAP 7.0 release family from a release earlier than 6.5, 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 Data ONTAP 6.5 and later releases 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.
For more information about changes to the /etc/export file upon upgrade, see the exports(5) man page.
In Data ONTAP 6.5 and later releases, the following operations cause the /etc/exports file to be modified according to the new rules described in New access rules for /etc/exports file:
New volumes are automatically entered in /etc/exports.
Note
When new volumes are created using the vol create command, access rules for the new volumes are set by default to -rw,nosuid (read-write permissions, setuid and setgid not allowed) in /etc/exports. If you want different access permissions, you must edit /etc/exports after the vol create operation is complete.
Volume listings are removed from /etc/exports when the volume is destroyed.
When a volume is renamed, the new volume name is automatically entered in /etc/exports.
The maximum size limits for RAID4 groups changed in the Data ONTAP 6.5 release family. The raidsize option of the vol command controls the size of new RAID groups that might be created in the volume. When new volumes are configured with RAID4 protection, they are created according to the raidsize settings for your platform.
If you upgrade to Data ONTAP 6.5 or later from a release earlier than 6.5 on a system with RAID4 protection, and if the settings for existing volumes are higher than the new limits, the raidsize option for those volumes is changed to the new RAID4 group size limit for your model appliance. If the existing volume's raidsize option is already set below the new limits, it is not changed.
These are the default and maximum RAID4 group sizes for NetApp® appliances affected by this change:
The sizes of existing volumes' RAID4 groups remain the same as before the upgrade, even if the size exceeds the new limits. However, if the raidsize option changes to the new, reduced limit, any new RAID4 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 or later, raidsize is changed to 6, the new limit. Existing RAID groups can have up to 8 disks, but any new RAID groups created in that volume will have up to 6 disks, which is also the default.
Note
Default and maximum raidsize values might change in future Data ONTAP releases. For a listing of current values, see the Storage Management Guide.
After the upgrade to the Data ONTAP 7.0 release family from a release earlier than 6.5, if you have volumes with RAID4 groups whose size exceeds the new RAID4 limit, you are strongly advised to 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 RAID4 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. You are therefore advised to schedule conversions from RAID4 to RAID-DP during non-peak hours.
To convert the RAID protection from RAID4 to RAID-DP, complete the following steps.
Default and maximum RAID-DP group sizes for the Data ONTAP 7.0 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 Internet SCSI (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.
Data ONTAP 6.5.2 and later releases include 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 family release, you can reset this option to its default value (3600), or any other value you used for this option before applying the workaround, after you upgrade to the Data ONTAP 7.0 release family.
Leaving the lowered (workaround) option value may cause an increase in name-service traffic when several 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:
An FTP security enhancement option (ftp.3way.enable) was added that changes the default behavior of Data ONTAP beginning with the 6.5 release family. This option prevents clients from redirecting FTP operations to a third-party client or server.
Standard FTP commands allow FTP communications to be redirected to third-party FTP servers. However, this functionality can be exploited using "bounce attacks" to circumvent network security and redirect FTP output (or FTP commands stored in a file) to unauthenticated machines.
In earlier versions, standard FTP redirect features were enabled. This functionality raises security issues and has been removed from the default behavior of Data ONTAP.
In this version, FTP redirects have been disabled by default. You need to modify the value of the ftp.3way.enable option to permit FTP redirects.
To enable one client to use FTP to send a file directly from a storage system to another client, complete the following step.
| 1 |
From the Data ONTAP command line, enter following command: options ftp.3way.enable on Result:Redirecting of FTP files to third-party clients is immediately enabled. |
Note
This option is persistent across storage system reboots. Valid values for ftp.3way.enable are on (allowing FTP redirects) and off (not allowing FTP redirects).
Beginning with Data ONTAP 6.5, there is a per-vFiler unit pseudo-root directory structure that allows all of a vFiler unit's storage to be shared under a single share. However, that change eliminated special handling for /vol/volname for the C$ share, which previously enabled the Microsoft Management Console (MMC) Computer Management tool to create the shares.
If you want to continue using the MMC Computer Management tool to create vFiler shares after upgrading to Data ONTAP 6.5 and later releases, you must delete any existing C$ vFiler share and re-create it to point to the vFiler pseudo-root. For more information, see Bug ID 112857 (on the NOW site at the following URL:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=112857).
Copyright © 1994-2005, Network Appliance, Inc. All rights
reserved.
Part No. 210-01083_B0
File: 2upgrad9.htm
Last updated: 16-Dec-2005 18:19:09