If you are using space reservations with Data ONTAP 6.3 when you upgrade to Data ONTAP 6.4, space reservations on volumes will be ignored. Space reservations will be turned on for all logical unit numbers (LUNs) and virtual local disks (VLDs) and space reservations will be left off for all other files.
Load-balancing algorithms for vifs were introduced in Data ONTAP 6.2. If you are using vifs, and you upgrade to Data ONTAP 6.2 or later from a pre-6.2 release, the network traffic flow out of the system may change. This could be because the vifs follow the default IP-based load-balancing policy. However, since the default load-balancing policy for most of the switches is IP-based, traffic flow is usually not disturbed. If the outbound flow of the network is not sufficiently balanced, you can change the load-balancing policy on the vif.
If you are upgrading Data ONTAP on clustered filers, you might have to disable the cluster before performing the upgrade. For information about when to disable the cluster, see Downloading Data ONTAP to clustered filers and rebooting.
If you are upgrading from a release that has the raid.reconstruct_speed knob, you should be aware that the options and settings for this feature changed in Data ONTAP 6.2. The raid.reconstruct_speed option can still be set but only affects the value of raid.reconstruct.perf_impact, which is one of four new options. The ten settings previously used for the raid.reconstruct_speed knob translate to three settings for the new options, as follows:
For more information about the new options for the raid.reconstruct_speed knob, see the Storage Management Guide.
In Data ONTAP 6.1 or later, both UNIX and Windows IDs can be specified in the etc/quotas file to track user quotas. If you previously specified a quota based on a user's UNIX IDs, and then after upgrading you specify a quota for the same user based on the Windows ID, these will be treated as separate quotas for the user. To apply the same quota whether the user logs in with the UNIX ID or Windows ID, add the following line to the etc/quotas file:
QUOTA _PERFORM_USER_MAPPING on
For more details, see the Storage Management Guide.
Because of the addition of Security ID (SID)-based quotas in Data ONTAP 6.1, there are some instances when you might see a warning message about correcting quotas if you upgrade from a pre-6.1 version to Data ONTAP 6.1 or later.
If you see a warning message, restart quotas by completing the following steps.
| 1 | Turn quotas off using the following command: quota off volume |
| 2 | Turn quotas back on using the following command: quota on volume |
If you are upgrading to Data ONTAP 6.1 or later, you should delete any pre-6.1 snapshots due to changes made to snapmirror in Data ONTAP 6.1.
This release might not contain all the bug fixes in a preceding D or P patch release.
Caution
If your filer is running a patch release, compare the bug fixes for this release to the bug fixes for your patch release to determine whether you should upgrade. For information about these bug fixes, see Bugs Online at http://now.netapp.com/cgi-bin/bol.
After you upgrade to Data ONTAP 6.1.1 or later, you may see a message that the builtin\administrator account does not exist when you reboot with CIFS enabled. Add a local user named "administrator" to resolve this issue. See the File Access Management Guide for information about adding a local user.
SecureAdminTM 1.0 software is incompatible with Data ONTAP 6.0 or later. If your filer is licensed for SecureAdmin, you must obtain the SecureAdmin 2.1.1 upgrade and be prepared to install it when you install the Data ONTAP 6.1 or later upgrade.
Caution
Failure to upgrade to SecureAdmin 2.1.1 when you upgrade to Data ONTAP 6.1 or later causes your filer to lose its SecureAdmin capabilities.
Data ONTAP 6.1.1 or later is compatible with Appliance WatchTM 1.1 software for HP® OpenView®, and ApplianceWatch 1.0 for Tivoli® EnterpriseTM.
If you purchased ApplianceWatch 1.0 for HP OpenView, you need to obtain and install ApplianceWatch 1.1.
If your filer is accessed by Macintosh computers using the DAVETM client from Thursby Systems, the DAVE client starts using the new streams feature when Data ONTAP 6.4 is installed. Information that was stored in special resource.frk files is lost. To solve this problem, you should run the na_macstream conversion utility from a Windows client after the upgrade to Data ONTAP 6.4 is completed and before DAVE clients access any files. For instructions about obtaining, installing, and running the na_macstream utility, see Appendix B, DAVE Macintosh Client resource.frk Conversion.
You must upgrade the filer system firmware to version 2.3_a2 before upgrading the filers in your cluster configuration to Data ONTAP 5.3.5 or later releases. Data ONTAP 5.3.5 and later releases check the filers to ensure that filer system firmware 2.3_a2 is running. If earlier versions of filer system firmware are running, Data ONTAP forces the filers in the cluster configuration to halt.
You can find filer system firmware 2.3_a2 on the NOW site at http://now.netapp.com. Follow the instructions given there to download and install filer system firmware 2.3_a2.
Data ONTAP 6.1.1 or later changes the procedure for updating the disk firmware for a cluster. To update the disk firmware on clustered filers, follow the disk firmware updating procedure in the Cluster Guide for your filer model.
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 215-00070
File: upgrade6.htm
Last updated: 01/09/03 18:09:40