Rnote

Data ONTAP 8.
0 7-Mode
Release Notes
NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 USA Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP Documentation comments: doccomments@netapp.com Information Web: http://www.netapp.com Part number: 215-05448_A0 25 May 2010
Table of Contents | 3
Contents
Copyright information...................................................................................9 Trademark information...............................................................................11 Data ONTAP 8.0 7-Mode Release Notes.....................................................13 New and changed features in the Data ONTAP 8.0 7-Mode release family..............................................................................15
New platform and hardware support...........................................................................16 Support for 2-TB SATA disks..........................................................................16 Changes in disk shelf support......................................................................................16 Support for DS4243 disk shelf........................................................................16 Systems including DS14 shelves, ESH modules or LRC modules are not supported.........................................................................16 Manageability enhancements......................................................................................17 SSL security improvements.............................................................................17 The default security settings............................................................................17 Setup for root account password .....................................................................18 The diagnostic account and the systemshell....................................................19 Boot menu enhancements and changes...........................................................19 Read reallocation of data.................................................................................19 Extents for FlexVol volumes............................................................................20 Partner recipients for AutoSupport email notifications ..................................20 AutoSupport message file attachments............................................................20 New disk drive AutoSupport message sent weekly.........................................20 Storage resource management enhancements.............................................................21 Support for 64-bit aggregates..........................................................................21 Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system....................................................................21 Networking and security protocols enhancements......................................................21 64-bit SNMP object identifiers (OIDs) are supported.....................................22 Configuration for receiving untagged traffic on VLAN tagged interfaces........................................................................................22 Vifs are now known as interface groups..........................................................22 File access protocol enhancements..............................................................................22
4 | Data ONTAP 8.0 7-Mode Release Notes Maximum number of auxiliary UNIX groups supported for a user....................................................................................................23 Support for multiple open instances of the SMB named pipe on an FPolicy server ..........................................................................23 Block protocol enhancements......................................................................................23 iSCSI RADIUS support...................................................................................23 Data protection enhancements.....................................................................................24 If volumes with deduplication exceed the maximum supported size.............................................................................................24 NearStore license is not required for deduplication........................................24 Maximum concurrent deduplication operations supported.............................24 Prerequisite for backing up data to tape using NDMP services......................25 Snapshot copy schedules.................................................................................25 SnapMirror support for 64-bit volumes...........................................................25 SnapVault support for 64-bit volumes.............................................................25 High availability pair (formerly active/active configuration) enhancements..............26 High-availability configuration and high-availability configuration terminology changes............................................................26 Changes to MultiStore support....................................................................................26 Data Motion is not supported..........................................................................26 Changes to the Data ONTAP and V-Series libraries....................................................26
New and changed commands and options in the Data ONTAP 8.0 7-Mode release.....................................................................29
New commands in Data ONTAP 8.0 7-mode..............................................................29 Changed commands in Data ONTAP 8.0 7-Mode......................................................31 Replaced or removed commands in Data ONTAP 8.0 7-Mode...................................33 New options in Data ONTAP 8.0 7-Mode...................................................................34 Changed options in Data ONTAP 8.0 7-Mode............................................................35
Requirements for running Data ONTAP 8.0 7-Mode................................39

Supported systems.......................................................................................................39 Unsupported systems...................................................................................................40 Storage system firmware ............................................................................................40 Storage systems that support Multipath Storage ........................................................41 V-Series requirements and support information..........................................................42 Requirements for V-Series fabric-attached MetroCluster configurations............................................................................................42
Table of Contents | 5
Important cautions.......................................................................................43
Unsupported features...................................................................................................43 Upgrade and revert cautions........................................................................................44 If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later..........................................................................................45 If you are updating a system with AT-FCX disk shelves attached...................46 If your system includes DS14 shelves, ESH modules, or LRC modules.............................................................................................46 If you are upgrading a FAS3140/FAS3170 system from Data ONTAP version 7.3 or earlier to version 8.0 in an iSCSI environment................................................................................46 Do not remove the special system files that are for restoring LUNs in snapshot copies............................................................47 If you are upgrading to Data ONTAP 8.0 7-Mode or later from a release earlier than Data ONTAP 7.3.............................................47 If your root FlexVol volume does not meet the new size requirements ..............................................................................................48 If you are performing a nondisruptive upgrade on a system with VMware ESX Server hosts....................................................48 If you are upgrading a system that includes FlexVol volumes .....................................................................................................49 If you are upgrading a system that includes deduplicated volumes................49 If your system uses rtc or rdate as the protocol for time synchronization..........................................................................................50 If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7-Mode.................................................50 If you have been using the flex_cache license.................................................50 If you revert from Data ONTAP 8.0 7-Mode and attempt to access LUN data in a Snapshot copy.....................................................51 If you are reverting to a Data ONTAP release with a lower maximum capacity.....................................................................................52 If you are reverting to a previous release and you use deduplication..............52 Block access protocol cautions....................................................................................53 Identical WWPNs can occur on both nodes in a cluster..................................53 If you deploy ALUA on storage systems with FCP or iSCSI..........................53
6 | Data ONTAP 8.0 7-Mode Release Notes If you use Solaris 10 and the emlxs Fibre Channel Adapter driver .........................................................................................................54 Only single_image cfmode is supported in Data ONTAP 8.0 7-Mode.................................................................................................54 Data protection cautions..............................................................................................54 NetApp SnapValidator for Oracle not supported.............................................54 512-GB and 256-GB Performance Acceleration modules not supported..............................................................................................55 Upgrade issues if you have SnapLock.............................................................55 Compression for SnapMirror transfers not supported.....................................55 Manageability cautions................................................................................................56 If you need to boot the storage system from a Data ONTAP image stored on a remote server..................................................56 TLS is not supported in Data ONTAP 8.0 7-Mode.........................................56 RLM over IPv6 not supported in Data ONTAP 8.0.........................................56 New RLM firmware and its upgrade requirements.........................................57 Network protocol cautions...........................................................................................57 IPv6 is not supported.......................................................................................57 IPsec is not supported......................................................................................58 TOE is not supported.......................................................................................58 File access and protocols cautions...............................................................................58 SMB 2.0 is not supported................................................................................58 Storage management cautions.....................................................................................58 Using ACP can cause system panic.................................................................58
Known problems and limitations................................................................61

Manageability issues....................................................................................................61 RLM configuration is not saved if the RLM's Ethernet cable is not connected................................................................................61 Issues regarding the EMS timed log ...............................................................61 Network protocol issues..............................................................................................62 Enable caching with NIS lookup.....................................................................62 Entries in the NIS group file should not exceed 1024 characters....................62 File access protocol issues...........................................................................................62 Client notification messages in Windows domains require NetBIOS.............63 Configuration issue for clients that mount NFS shares using a non-reserved port...........................................................................63
Table of Contents | 7 Block access protocol issues........................................................................................63 Brocade 200E switch speed must be set manually..........................................63 Disks offline in Windows 2008 after a standard upgrade................................64 iSCSI Target HBA support..............................................................................65 If an iSCSI target HBA fails............................................................................65 If you use the automatic sizing feature on thinly provisioned LUNs when snap reserve is set to a non-zero value............................................................................................65 Data protection issues..................................................................................................66 Limitations when using SnapVault with nondefault vFiler units.....................66 Restore engine does not honor any mandatory or advisory locks on files .............................................................................................67 Restore operation to a non-existent volume restores data to the root volume......................................................................................67 Shutting down a storage system when SMTape operations are active might results in a panic..............................................................68 Suboptimal space savings with deduplication when 16 GB Performance Acceleration Module is installed..........................................68 If you use DataFabric Manager to manage SnapMirror or SnapVault relationships between vFiler units............................................68 Possible effect of creating more than 64 mirrored aggregates preventing disaster recovery from functioning correctly..................................................................................69 Storage resource management issues..........................................................................69 The -m option for the disk replace start command is not recognized..............69 Attempting to assign more than 500 disks or array LUNs with a single disk assign command causes a system panic........................70 Down nodes in a cluster containing a FlexCache origin volume can prevent the FlexCache volume from connecting to the origin.............................................................................70 Moving disks to a system running an earlier version of Data ONTAP could cause disk identification issues .................................70 Data ONTAP can silently select varying disk or array LUN sizes when creating an aggregate......................................................70 Qtree quotas might prevent explicit quotas from overriding the default.................................................................................72
8 | Data ONTAP 8.0 7-Mode Release Notes Third-party storage issues (V-Series systems only) ....................................................72 Exceeding the maximum number of assigned devices results in a panic....................73 Limitation on EMC CX storage array LUN numbering..............................................73 High-availability configuration issues.........................................................................73 The ifconfig command and the FAS2040 e0P port.........................................74 If takeover is enabled for network interface failure, automatic giveback should be disabled......................................................74
Changes to published documentation.........................................................75

Changes to the Storage Management Guide ...............................................................75 Maximum size of volume without deduplication ...........................................75 Disk sanitization limitations............................................................................75 FlexCache limitations......................................................................................76 Changes to the V-Series Implementation Guide for IBM Storage...............................76 Array LUN sizing with 2 TB disks is not documented in all V-Series Implementation Guides ..........................................................................76 Changes to the File Access and Protocols Management Guide...................................76 SMB 2.0 Support.............................................................................................77 Unsupported Windows features in the file serving environment.....................77 NFSv4 client compatibility..............................................................................77 The file fingerprint command can be used for all data files in Data ONTAP 8.0 7-Mode......................................................................78
Where to find product documentation and other information.................79

The Documentation Roadmap.....................................................................................79 Searching online information .....................................................................................80 Finding documentation on NOW ................................................................................80
Copyright information | 9
Copyright information
Copyright 1994-2010 NetApp, Inc. All rights reserved. Printed in the U.S.A. No part of this document covered by copyright may be reproduced in any form or by any meansgraphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval systemwithout prior written permission of the copyright owner. Software derived from copyrighted NetApp material is subject to the following license and disclaimer: THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. NetApp reserves the right to change any products described herein at any time, and without notice. NetApp assumes no responsibility or liability arising from the use of products described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp. The product described in this manual may be protected by one or more U.S.A. patents, foreign patents, or pending applications. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark information | 11
Trademark information
NetApp; the NetApp logo; the Network Appliance logo; Cryptainer; Cryptoshred; DataFabric; Data ONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone; FlexShare; FlexVol; FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore; NetCache; NOW (NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; Simulate ONTAP; SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore; SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess; SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StoreVault; SyncMirror; Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. Network Appliance, Snapshot, and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries. The StoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport, ComplianceClock, DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management, LockVault, NOW, MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape, SnapDirector, SnapFilter, SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy, and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful and Select are service marks of NetApp, Inc. in the U.S.A. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. A complete and current list of other IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml. Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks. NetApp, Inc. NetCache is certified RealSystem compatible.
Data ONTAP 8.0 7-Mode Release Notes | 13
Data ONTAP 8.0 7-Mode Release Notes

These Release Notes describe new features, enhancements, and known issues for Data ONTAP 8.0 7-Mode, as well as additional information related to running this release on specific storage systems. About the Data ONTAP 8.0 7-Mode release Data ONTAP 8.0 7-Mode is a General Availability (GA) release and is the first release in the Data ONTAP 8.0 7-Mode release family. For more information about Data ONTAP releases, see the "Data ONTAP Release Model" on the NOW site. The Data ONTAP 8.0 7-Mode release provides a new aggregate type, 64-bit aggregates, with a larger maximum aggregate and FlexVol sizes as well as new platform and hardware support. Additional features include support for 2-TB SATA disks, SSL security improvements, additional capabilities using iSCSI and FCP protocols for NetApp SAN environments, and enhanced data protection technologies such as SnapMirror and SnapVault. For a complete description of these and other new features, see New and changed features in the Data ONTAP 8.0 7-Mode release family on page 15.
Attention:
If you are upgrading to this Data ONTAP 8.0 7-Mode or reverting from this release to an earlier release, see the Data ONTAP 8.0 7-Mode Upgrade Guide. Data ONTAP 8.0 7-Mode supports all of the features in earlier versions of Data ONTAP 7.x releases with some exceptions, including the following: SnapLock NetApp SnapValidator for Oracle IPv6 SMB 2.0 256-GB and 512-GB Performance Acceleration Module (PAM II)
Do not upgrade your storage system to Data ONTAP 8.0 7-Mode if you have configured any of these features. For more information, see Unsupported features on page 43. About these release notes All the information in this document applies to the Data ONTAP 8.0 7-Mode release for NetApp storage systems (FAS systems, NearStore systems, and V-Series systems), unless noted. FAS systems and NearStore systems are sometimes called filers or appliances. Some of the information in this document applies to SA systems.
14 | Data ONTAP 8.0 7-Mode Release Notes These release notes are available in .html and .pdf formats. They are optimized for .html viewing and linking.
Related information
Data ONTAP Release Model -- now.netapp.com/NOW/products/ontap_releasemodel/post70.shtml
New and changed features in the Data ONTAP 8.0 7-Mode release family | 15
New and changed features in the Data ONTAP 8.0 7-Mode release family
This section covers features that were added or changed in the Data ONTAP 8.0 7-Mode release family.
Note: Some new and changed features in this release might also be introduced in a maintenance
release of an earlier 7G release family. Before upgrading, be sure to consult with your NetApp representative about new Data ONTAP functionality to determine the best solution for your business needs. Data ONTAP 8.0 7-Mode and later releases provide a new aggregate type, 64-bit aggregates, with a larger maximum aggregate and FlexVol sizes, as well as improved performance, resiliency, and management capabilities for storage resources. For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 21. Data ONTAP 8.0 7-Mode and later releases also provide new platform and hardware support as described in New platform and hardware support on page 16 , additional management capabilities such as SSL security improvements, additional capabilities using iSCSI and FCP protocols for NetApp SAN environments, and enhanced data protection technologies such as SnapMirror and SnapVault. Additional major changes made in Data ONTAP 8.0 7-Mode are described here. For other important information in these release notes about changes to the product made by these releases, see the summary of all new and changed commands and options in the release family. For a comparison of bugs fixed in different releases, see Bugs Online - Release Comparison on the NOW site.
Next topics
New platform and hardware support on page 16 Changes in disk shelf support on page 16 Manageability enhancements on page 17 Storage resource management enhancements on page 21 Networking and security protocols enhancements on page 21 File access protocol enhancements on page 22 Block protocol enhancements on page 23 Data protection enhancements on page 24 High availability pair (formerly active/active configuration) enhancements on page 26 Changes to MultiStore support on page 26 Changes to the Data ONTAP and V-Series libraries on page 26
Related concepts
New and changed commands and options in the Data ONTAP 8.0 7-Mode release on page 29
16 | Data ONTAP 8.0 7-Mode Release Notes

Related information
Bugs Online: now.netapp.com/NOW/cgi-bin/bol/
New platform and hardware support

The Data ONTAP 8.0 release family supports new hardware as listed . The new platform and hardware are listed in the order of most recently introduced beginning with Data ONTAP 8.0. For information about supported systems, see Supported systems on page 39.
Support for 2-TB SATA disks

In Data ONTAP 8.0 and later releases, 2-TB SATA disks are supported for both the SAS and FC disk connection architectures. With these larger disks and 64-bit aggregates, you can create larger aggregates before being affected by spindle and aggregate size limits. For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 21.
Changes in disk shelf support

Data ONTAP 8.0 7-Mode includes some changes to disk shelf support.
Next topics
Support for DS4243 disk shelf on page 16 Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 16
Support for DS4243 disk shelf

Data ONTAP 8.0 and later releases support the DS4243 disk shelf.
Systems including DS14 shelves, ESH modules or LRC modules are not supported
Beginning with Data ONTAP 7.3, DS14 disk shelves, LRC storage I/O modules, and ESH storage I/O modules are no longer supported. Upgrading a system with any of these devices attached to it will result in an unsupported configuration. If even one of these devices is attached to your storage system, you should not upgrade to Data ONTAP 7.3 or later. Some models of the DS14 shelves, LRC modules, and ESH modules are no longer supported. This means that the following disk shelf configurations are no longer supported: ESH2 modules with DS14 disk shelves
New and changed features in the Data ONTAP 8.0 7-Mode release family | 17 ESH modules with DS14 or DS14mk2 FC disk shelves LRC modules with DS14 or DS14mk2 FC disk shelves
The following disk shelf configurations, which do not include any obsolete hardware, continue to be supported: ESH4 modules with DS14mk4 FC or DS14mk2 FC disk shelves ESH2 modules with DS14mk2 FC disk shelves
If you want to upgrade to Data ONTAP 7.3 or a later release and your storage environment includes the obsolete DS14mk1, ESH, or LRC storage hardware, you should contact your NetApp representative to discuss upgrading to the latest DS14mk4 disk shelf with ESH4 storage I/O modules.
Manageability enhancements
Data ONTAP 8.0 7-Mode and later releases provide additional management capabilities using MultiStore, FilerView, and other tools.
Next topics
SSL security improvements on page 17 The default security settings on page 17 Setup for root account password on page 18 The diagnostic account and the systemshell on page 19 Boot menu enhancements and changes on page 19 Read reallocation of data on page 19 Extents for FlexVol volumes on page 20 Partner recipients for AutoSupport email notifications on page 20 AutoSupport message file attachments on page 20 New disk drive AutoSupport message sent weekly on page 20
SSL security improvements

As a precautionary measure due to security vulnerability CVE-2009-3555, the SSL renegotiation feature is disabled in Data ONTAP.
The default security settings

On storage systems shipped with Data ONTAP 8.0 7-Mode or later, secure protocols are enabled and nonsecure protocols are disabled by default. SecureAdmin is set up automatically on storage systems shipped with Data ONTAP 8.0 7-Mode or later. For these systems, the following are the default security settings:
18 | Data ONTAP 8.0 7-Mode Release Notes Secure protocols (including SSH, SSL, and HTTPS) are enabled by default. Nonsecure protocols (including RSH, Telnet, FTP, and HTTP) are disabled by default.
On storage systems shipped with Data ONTAP 8.0 7-Mode or later, the following are the default option settings for SSH and SSL:
options ssh.enable on options ssh2.enable on options ssh1.enable off options ssh.passwd_auth.enable on options ssh.pubkey_auth.enable on options httpd.admin.ssl.enable on
Also on storage systems shipped with Data ONTAP 8.0 7-Mode or later, the following are the default option settings for the nonsecure protocols:
options ftpd.enable off options httpd.admin.enable off options httpd.enable off options rsh.enable off options telnet.distinct.enable on options telnet.enable off Note: These default settings apply only to storage systems shipped with Data ONTAP 8.0 7-Mode
or later. For storage systems upgraded from an earlier version to Data ONTAP 8.0 7-Mode or later, the above default settings do not apply. Instead, for those upgraded systems, the settings remain unchanged after the upgrade. Also, if you make security setting modifications after upgrading to Data ONTAP 8.0 7-Mode or later, the modifications are preserved even if the system reverts back to the previous Data ONTAP version. For more information about the default security settings, see the Data ONTAP 8.0 7-Mode System Administration Guide.
Setup for root account password

During the initial setup of a storage system shipped with Data ONTAP 8.0 7-Mode or later, you are prompted to set up a password for the root account. The following are the default password rules for all accounts when security.passwd.rules.enable is set to on (the default): The password must be at least eight characters long. The password must contain at least one number. The password must contain at least two alphabetic characters.
Note: Subsequent invocations of the setup command do not prompt you to set up a password for
the root account. For more information about setting up the storage system, see the Data ONTAP 8.0 7-Mode Software Setup Guide.
The diagnostic account and the systemshell

A diagnostic account, named diag, is provided with your storage system. You can enable the diagnostic account to perform troubleshooting tasks in the systemshell. The diagnostic account and the systemshell are intended only for low-level diagnostic purposes and should be used only with guidance from technical support. The diagnostic account is the only account that can be used to access the systemshell, through the advanced command systemshell. The diagnostic account is disabled by default. You must enable the account and set up its password before using it. Neither the diagnostic account nor the systemshell is intended for general administrative purposes. For information about the diagnostic account and the systemshell, see the Data ONTAP 8.0 7-Mode System Administration Guide.
Boot menu enhancements and changes

The boot menu includes new menu options that allow you to restore the configuration information from the root volume to the boot device, to install new software, or to reboot the storage system. Data ONTAP 8.0 7-Mode and later versions allow you to create a new root FlexVol volume but not a new traditional root volume from the boot menu. However, preexisting traditional root volumes are still supported. For information about the boot menu, see the na_floppyboot(1) man page and the Data ONTAP 8.0 7-Mode System Administration Guide.
Read reallocation of data

For workloads that perform a mixture of random writes and large and multiple sequential reads, the read reallocation function improves the file's layout and sequential read performance. When you enable read reallocation by using the vol options read_realloc command, Data ONTAP analyzes the parts of the file that are read sequentially. If the associated blocks are not already largely contiguous, Data ONTAP updates the file's layout by rewriting those blocks to another location on the disk. The rewrite improves the file's layout, thus improving the sequential read performance the next time that section of the file is read. For more information about the vol options read_realloc command, see the na_vol(1) man page and the Data ONTAP 8.0 7-Mode System Administration Guide.
Extents for FlexVol volumes

Enabling extents by setting the vol options extent command to on might improve performance of Exchange database validation. However, to enable extents when storage space is a concern, you should set the vol options extent command to space_optimized instead of on. The space_optimized option conserves space. However, it results in degraded read performance through the Snapshot copies. Therefore, if fast read performance through Snapshot copies is a higher priority to you than storage space, do not use the space_optimized option. For more information about the vol options extent command, see the na_vol(1) man page and the Data ONTAP 8.0 7-Mode System Administration Guide.
Partner recipients for AutoSupport email notifications

The new option autosupport.partner.to allows you to define the list of partner recipients for AutoSupport email notifications. Whereas the autosupport.support.to option is read-only and displays where email-based AutoSupport notifications are sent to technical support when the autosupport.support.enable option is set to on (the default), the autosupport.partner.to option allows you to define a list of partner recipients who will receive all AutoSupport notifications regardless of the severity level or the setting of the autosupport.support.enable option. Using the autosupport.partner.to option, you can specify up to five email addresses for partner recipients to receive AutoSupport notifications. The email addresses should be entered as a comma-separated list with no spaces between them. By default, the autosupport.partner.to option is not defined and has an empty list. To receive any email-based AutoSupport notifications, you must also define a mail host by using the autosupport.mailhost option.
AutoSupport message file attachments

Beginning with Data ONTAP 8.0 7-Mode, the contents of /etc/messages and /etc/log/ems are no longer sent in the body of AutoSupport messages. Instead, they are sent as .gz attachments to AutoSupport messages.
New disk drive AutoSupport message sent weekly

A weekly NetApp Health Trigger (NHT) AutoSupport message provides information about any failed disk drives. The message is sent each Sunday between 12:00 a.m. and 1 a.m. local time. If no drives failed during the past week, no weekly drive NHT message is sent. By default, the NHT message is sent only to technical support.
Storage resource management enhancements

Data ONTAP 8.0 7-Mode and later releases provide improved performance, resiliency, and management capabilities for storage resources.
Next topics
Support for 64-bit aggregates on page 21 Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system on page 21
Support for 64-bit aggregates

In Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports a new type of aggregate, the 64-bit aggregate. 64-bit aggregates have a larger maximum size than aggregates created with earlier versions of Data ONTAP. In addition, volumes contained by 64-bit aggregates have a larger maximum size than volumes contained by aggregates created with earlier versions of Data ONTAP. The maximum size of a 64-bit aggregate and the volumes it contains depends on the model of your storage system. To determine the maximum 64-bit aggregate size for your storage system model, see the System Configuration Guide. The maximum size of a volume contained by a 64-bit aggregate corresponds to the maximum size of its containing aggregate. The maximum size for legacy aggregates, now called 32-bit aggregates, remains 16 TB. For more information, see the Data ONTAP 8.0 7-Mode Storage Management Guide and the na_aggr(1) man page.
Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system
Starting with Data ONTAP 8.0 7-Mode, you can simultaneously run a maximum of 500 FlexClone file or FlexClone LUN operations on a storage system. For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP 8.0 7-Mode Storage Management Guide.
Networking and security protocols enhancements

Data ONTAP 8.0 7-Mode and later releases provide enhanced network performance and security features.
Next topics
64-bit SNMP object identifiers (OIDs) are supported on page 22
22 | Data ONTAP 8.0 7-Mode Release Notes Configuration for receiving untagged traffic on VLAN tagged interfaces on page 22 Vifs are now known as interface groups on page 22
64-bit SNMP object identifiers (OIDs) are supported

In Data ONTAP 7.2 and 7.3 release families, some OIDs in the netapp.mib file have low and high 32-bit values. In Data ONTAP 8.0 7-Mode, these OIDs are replaced with 64-bit values. You should use the 64-bit OIDs to query your storage system by using SNMP. For example, the miscHighNfsOps and miscLowNfsOps OIDs have been replaced with the 64-bit OID misc64NfsOps. In the netapp.mib file, miscHighNfsOps and miscLowNfsOps are marked as deprecated. For more information, see the latest netapp.mib file on the NOW site.
Related information
MIB file: http://now.netapp.com/NOW/download/tools/mib/
Configuration for receiving untagged traffic on VLAN tagged interfaces

In Data ONTAP 8.0 7-Mode, you can configure an IP address for a network interface with VLANs. Any untagged traffic goes to the base interface, and the tagged traffic goes to the respective VLAN. For more information about this feature, see the Data ONTAP 8.0 7-Mode Network Management Guide. For information about reverting with a configuration for receiving tagged and untagged frames on the same network interface, see the Data ONTAP 8.0 7-Mode Upgrade Guide.
Vifs are now known as interface groups

Starting with Data ONTAP 8.0 7-Mode, vifs are known as interface groups. An interface group refers to a single virtual interface that is created by grouping together multiple physical interfaces. In the Data ONTAP 7.2 and 7.3 release families, this functionality is referred to as a vif. You can use the ifgrp command to create and configure interface groups. For more information about interface groups and the ifgrp command, see the Data ONTAP 8.0 7-Mode Network Management Guide.
File access protocol enhancements

Data ONTAP 8.0 7-Mode and later releases provide new features of NFSv4 and FPolicy, new commands for debugging CIFS file access control problems, a new option for specifying the minimum levels of authentication and session security that clients must use, and compatibility with Windows Vista and Windows Server 2008.
New and changed features in the Data ONTAP 8.0 7-Mode release family | 23 For more information about these features, see the Data ONTAP 8.0 7-Mode File Access and Protocols Management Guide.
Next topics
Maximum number of auxiliary UNIX groups supported for a user on page 23 Support for multiple open instances of the SMB named pipe on an FPolicy server on page 23
Maximum number of auxiliary UNIX groups supported for a user

If you use Kerberos V5 authentication, the maximum number of auxiliary UNIX groups that a user can be a member of is 32 by default. You can increase the maximum to 256 groups by setting the nfs.max_num_aux_groups option to 256. However, in FlexCache setups, Data ONTAP supports a maximum of 32 auxiliary UNIX groups for FlexCache volumes, regardless of the value set for this option. If you do not use Kerberos V5 authentication, the maximum number of auxiliary UNIX groups that a user can be a member of is 16. For more information about the nfs.max_num_aux_groups option, see the na_options(1) man page.
Support for multiple open instances of the SMB named pipe on an FPolicy server
In Data ONTAP 8.0 7-Mode you can enable multiple open instances of the SMB named pipe on an FPolicy server by using the fpolicy.multiple_pipes option. For more information, see the Data ONTAP 8.0 7-Mode File Access and Protocols Management Guide.
Block protocol enhancements

Data ONTAP 8.0 7-Mode and later releases provide additional capabilities using iSCSI and FCP protocols for NetApp SAN environments. For more information about these features, see the Data ONTAP 8.0 7-Mode Block Access Management Guide for iSCSI and FC.
iSCSI RADIUS support

Data ONTAP 8.0 7-Mode introduces support for iSCSI RADIUS, which allows you to centrally manage iSCSI initiator authentication. RADIUS still uses CHAP to authenticate iSCSI initiators, but it allows you to manage the authentication process from a central RADIUS server, rather than manage them manually on each storage system. In larger SAN environments, this can greatly simplify iSCSI initiator management and provide added security.
24 | Data ONTAP 8.0 7-Mode Release Notes In addition to simplifying CHAP password management, RADIUS also reduces the load on your storage system. The RADIUS client service runs on the storage system and communicates with the RADIUS server and initiators, but most of the authentication processing is handled by the RADIUS server. For more information, see the Data ONTAP 8.0 7-Mode Block Access Management Guide for iSCSI and FC.
Data protection enhancements

Data ONTAP 8.0 7-Mode and later releases provide enhanced data protection technologies (such as SnapMirror and SnapVault), SMTape operations, and security administration. For more information about these features, see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide and the Data ONTAP 8.0 7-Mode Data Protection Tape Backup and Recovery Guide.
Next topics
If volumes with deduplication exceed the maximum supported size on page 24 NearStore license is not required for deduplication on page 24 Maximum concurrent deduplication operations supported on page 24 Prerequisite for backing up data to tape using NDMP services on page 25 Snapshot copy schedules on page 25 SnapMirror support for 64-bit volumes on page 25 SnapVault support for 64-bit volumes on page 25
If volumes with deduplication exceed the maximum supported size

Volumes continue to be online when they exceed the maximum supported size. For more information about the maximum volume size allowed for different storage systems, with and without deduplication, see the Data ONTAP 8.0 7-Mode Storage Management Guide.
NearStore license is not required for deduplication

Starting with Data ONTAP 8.0 7-Mode, you do not have to enable the NearStore personality license to use deduplication.
Maximum concurrent deduplication operations supported

You can run a maximum of eight concurrent deduplication operations on all storage systems.
Prerequisite for backing up data to tape using NDMP services

Starting from Data ONTAP 8.0 7-Mode, NDMP users must have the login-ndmp capability for successfully authenticating NDMP sessions. A predefined role named backup has the login-ndmp capability, by default. To provide a user with the login-ndmp capability, the backup role can be assigned to the group to which the user belongs. However, when a group is assigned the backup role, all users within the group get the login-ndmp capability. Therefore, it is best to group all NDMP users into a single group that has the 'backup role.
Snapshot copy schedules

Scheduled Snapshot copy creation might fail for various reasons, such as a volume being unavailable. In such cases, a Snapshot copy might be created when possible, outside the schedule. This feature is available in Data ONTAP 8.0 7-Mode and later releases in the Data ONTAP 8.0 7-Mode release family. For more information about this feature, see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide.
SnapMirror support for 64-bit volumes

Data ONTAP 8.0 7-Mode and later releases in this release family support 64-bit volumes in addition to 32-bit volumes. SnapMirror supports replication between 64-bit volumes and also between 32-bit volumes. However, there are certain considerations when replicating volumes and qtrees using SnapMirror. When replicating volumes by using SnapMirror, synchronously or asynchronously, the source and destination volumes must be of the same type. Both the source and destination volumes must be 64-bit volumes or they must both be 32-bit volumes. When replicating qtrees by using SnapMirror, the source and destination volumes can be of different types. Either the source and or destination volume can be 64-bit or 32-bit. For more information about SnapMirror support for 64-bit volumes and see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide.
SnapVault support for 64-bit volumes

Data ONTAP 8.0 7-Mode and later releases in this release family support 64-bit volumes. SnapVault supports replication between 64-bit volumes, in addition to supporting replication between 32-bit volumes. When replicating qtrees by using SnapVault, the source and destination volumes can be of different types. The source and destination volumes can be either 64-bit or 32-bit. For more information about SnapVault replication, see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide.
High availability pair (formerly active/active configuration) enhancements

Data ONTAP 8.0 7-Mode and later releases include the new cf.takeover.on_reboot, cf.takeover.on_panic, and cf.giveback.auto.delay.seconds options. Also, the term HA pair has replaced active/active configuration. For more information about these features, see the Data ONTAP 8.0 7-Mode High-Availability Configuration Guide.
High-availability configuration and high-availability configuration terminology changes

The high-availability (HA) functionality referred to as an HA pair in Data ONTAP 8.0 7-Mode was called an active/active configuration in the Data ONTAP 7.2 and 7.3 release families. In the Data ONTAP 7.1 release family and earlier releases, an HA pair was called a cluster. HA functionality is a distinct, separate feature from Data ONTAP 8.0 Cluster-Mode clustering. For more information about these features, see the Data ONTAP 8.0 7-Mode High-Availability Configuration Guide.
Changes to MultiStore support

Data ONTAP provides MultiStore capabilities and changes. Although Data Motion is a feature in MultiStore, Data Motion will not be supported until a future release.
Data Motion is not supported

Data Motion was introduced in a previous release, but it is not supported in Data ONTAP 8.0 7-Mode. The Data Motion feature integrates virtual storage, mirroring, and provisioning software technologies so that you can perform data migrations nondisruptively in both physical and virtual environments.
Changes to the Data ONTAP and V-Series libraries

The Data ONTAP 8.0 7-Mode Software Setup Guide now provides information for basic setup of all systems that run Data ONTAP, including V-series systems. Data ONTAP guides and V-Series guides are now available on the same Documentation Web page. Starting in Data ONTAP 7.3.2, much of the information about using Data ONTAP features with V-Series systems was integrated into the general Data ONTAP guides. This effort continued in Data ONTAP
New and changed features in the Data ONTAP 8.0 7-Mode release family | 27 8.0 7-Mode with the integration of V-Series system setup instructions into the Data ONTAP 8.0 7-Mode Software Setup Guide. As of Data ONTAP 8.0 7-Mode, there is no longer a separate setup guide for V-Series. The V-Series documents now focus primarily on information about implementation with the back-end storage arrays. The Data ONTAP 8.0 7-Mode Documentation page is also integrated. You can find both the general Data ONTAP 8.0 7-Mode guides and the V-Series specific guides on the same Documentation web page; there is no longer a separate Documentation page for the V-Series guides. You can access the integrated Data ONTAP 8.0 7-Mode Documentation page from the Data ONTAP Information Library page.
Related information
Data ONTAP Information Library page: now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml
New and changed commands and options in the Data ONTAP 8.0 7-Mode release | 29
New and changed commands and options in the Data ONTAP 8.0 7-Mode release
This section provides information about the commands, options, and configuration files that have been changed in or added to the Data ONTAP 8.0 7-Mode release family.
Next topics
New commands in Data ONTAP 8.0 7-mode on page 29 Changed commands in Data ONTAP 8.0 7-Mode on page 31 Replaced or removed commands in Data ONTAP 8.0 7-Mode on page 33 New options in Data ONTAP 8.0 7-Mode on page 34 Changed options in Data ONTAP 8.0 7-Mode on page 35
New commands in Data ONTAP 8.0 7-mode

Commands have been added to back up blocks of data to tape and to restore blocks of data from tape. Additional commands display the status of SMTape-initiated backup and restore operations and list all array LUNs exported from a named storage array. For each command family and each command, the following table gives this information: The purpose of the command The location of documentation about the feature The Data ONTAP 8.0 7-mode release in which the command was introduced
Purpose Document Release Introduced 8.0
Command acpadmin list_all
Displays information about Data ONTAP 8.0 7-Mode the ACP (Alternate Control Storage Management Path) storage subsystem. Guide na_acpadmin(1) man page
ifgrp
Data ONTAP 8.0 7-Mode Manages interface groups Network Management on your storage system. Guide This command replaces the vif command. However, the options remain the same.
8.0
Command smtape abort
Purpose
Document
Release Introduced 8.0
Data ONTAP 8.0 7-Mode Aborts a backup or restore Data Protection Tape job initiated by the Backup and Recovery SMTape engine. Guide na_smtape manpage
smtape backup
Data ONTAP 8.0 7-Mode Backs up blocks of data to Data Protection Tape tape. Backup and Recovery Guide na_smtape manpage
8.0
smtape continue
Continues an SMTape-initiated backup or restore operation after it has reached the end of current tape and is in the wait state to write output to or accept input from a new tape Restores blocks of data from tape.
Data ONTAP 8.0 7-Mode Data Protection Tape Backup and Recovery Guide na_smtape manpage
8.0
smtape restore
8.0
smtape status
Display the status of SMTape-initiated backup and restore operations
8.0
storage array modify storage array purge-database
Modifies attributes of array na_storage(1) man page profile records. Removes all records from na_storage(1) man page the controllers array profile database.
8.0 8.0
Command storage array remove
Purpose Removes records for the specified array from the controllers array profile database. Removes ports associated with an array profile.
Document na_storage(1) man page
Release Introduced 8.0
storage array remove-port
na_storage(1) man page na_storage(1) man page
8.0 8.0
storage array show Lists all array profile records known to the controller. storage array show-config Provides a summary of the connectivity to SAN-attached arrays connected to the V-Series systems FC initiator ports. Lists all array LUNs exported from a named storage array.
V-Series Installation Requirements and Reference Guide na_storage(1) man page
8.0
storage array show-luns array-name storage array show-ports
na_storage(1) man page
8.0
Lists all target ports for all na_storage(1) man page storage arrays known to the V-Series system. Displays information about Data ONTAP 8.0 7-Mode the ACP (Alternate Control Storage Management Path) storage subsystem. Guide na_acpadmin(1) man page
8.0
storage show acp
8.0
Changed commands in Data ONTAP 8.0 7-Mode

This table lists changed commands. For each command family and each command, the following table gives this information: Change in the command Location of documentation about the feature The Data ONTAP 8.0 7-Mode release in which the change was introduced.
Command
Change
Documentation
Release command changed in 8.0
aggr create
na_aggr(1) man page The -B option has been added. This option is used Data ONTAP 8.0 7-Mode to create a 64-bit Storage Management Guide aggregate. The -x option has been added. This option surpresses the display of the .snapshot lines. na_df(1) man page
df
8.0
disk assign
You can no longer use this na_disk(1) man page command to change the ownership of a disk or array LUN that is already owned unless you are running the command on the system that owns the disk already. The Complex Programmable Logic Devide (CPLD) version has been added to the output.
8.0
environment shelf
na_environment(1) man page 8.0
storage show expander
The system interconnect na_storage(1) man page link (SIL) ports (the last four rows of output) are now shown as [SIL0] through [SIL3]. Previously they were shown as [DIS0] through [DIS3]. The DS4243 disk shelf ports are now listed as [SQR0]-[SQR3] for the square ports and [CIR4]-[CIR7] for the circle ports. Previously these ports were listed as [IO 0]-[IO7]. na_storage(1) man page
8.0
storage show expander
8.0
Command
Change
Documentation
Release command changed in 8.0
sysconfig
na_sysconfig(1) man page When the -r option is used to display disk information for SAS-connected disks, the CHAN (channel) column now displays the port as "A" or "B", just as it does for FC-connected disks. Previously, "1" and "2" were used. This command has been replaced by the ifgrp command. The extent option enables extents but can only be used on FlexVol volumes. The read_realloc option enables read reallocation but can only be used on FlexVol volumes. Data ONTAP 8.0 7-Mode Network Management Guide
vif
8.0
vol options
na_vol(1) man page and the 8.0 Data ONTAP 8.0 7-Mode System Administration Guide na_vol(1) man page and the 8.0 Data ONTAP 8.0 7-Mode System Administration Guide
vol options
vol status
na_vol(1) man page When the -r option is used to display disk information for SAS-connected disks, the CHAN (channel) column now displays the port as "A" or "B", just as it does for FC-connected disks. Previously, "1" and "2" were used.
8.0
Replaced or removed commands in Data ONTAP 8.0 7-Mode

The following information lists replaced or removed commands in Data ONTAP 8.0 7-Mode.
34 | Data ONTAP 8.0 7-Mode Release Notes Support for the following commands will be discontinued in a future version of Data ONTAP. To perform the equivalent operation, use the aggr command.
vol add vol media_scrub vol migrate vol mirror vol scrub vol split vol verify vol wafliron
These commands are removed in Data ONTAP 8.0 7-mode.

snapmirror store snapmirror use snapmirror retrieve
In Data ONTAP 8.0 7-Mode the vif command has been replaced by the ifgrp command. For more information, see the Data ONTAP 8.0 7-Mode Network Management Guide.
New options in Data ONTAP 8.0 7-Mode

Options that can be used with the options command are included in this table. For each new option that can be used with the options command, the following table gives this information: Description of the option's purpose Name of the new option Default value for the option Data ONTAP release in which the option was introduced
For more information about the options command and individual options, see the na_options(1) man page.
Option Purpose Default Value Release added 8.0
NA autosupport.performance_data.doit Triggers a performance snapshot AutoSupport message when any string is any_string added.
Option
Purpose Triggers a takeover if the partner mode panics. Triggers a takeover if the partner node reboots.
Default Value Release added On 8.0
cf.takeover.on_panic
cf.takeover.on_reboot
The default is 8.0 on, unless FCP or iSCSI is licensed, in which case the default is off. 300 seconds 8.0 8.0
cf.givegack.auto.delay.seconds Adjusts the giveback delay time for automatic giveback. nfs.max_num_aux_groups
Specifies the maximum number of 32 auxiliary UNIX groups that a user can be a member of. Enables multiple open instances of the SMB named pipe on an FPolicy server. on
fpolicy.multiple_pipes
8.0
Changed options in Data ONTAP 8.0 7-Mode

This table lists options that have changed or become obsolete. For each option, the following table gives this information: The name of the changed option The nature of the change The Data ONTAP 8.0 7-Mode release in which the change was introduced.
For more information about the options command and individual options, see the na_options(1) man page.
Option flexscale.max_io_qdepth httpd.admin.enable Change This option has become obsolete. Release changed 8.0
The default for this option has been 8.0 changed to off for systems shipped with Data ONTAP 8.0 7-Mode or later.
Option httpd.admin.ssl.enable
Change
Release changed
The default for this option has been 8.0 changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been 8.0 changed to off for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been 8.0 changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been 8.0 changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later.
rsh.enable
ssh.enable
ssh2.enable
security.passwd.rules.everyone The default for this option has been 8.0 changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. security.passwd.rules.history The default for this option has been 8.0 changed to 6 for systems shipped with Data ONTAP 8.0 7-Mode or later. telnet.distinct.enable The default for this option has been 8.0 changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been 8.0 changed to off for systems shipped with Data ONTAP 8.0 7-Mode or later. This option has become obsolete. The rtc and the rdate parameters of this option have become obsolete. The default has been changed to ntp . This option has become obsolete. 8.0 8.0
telnet.enable
timed.max_skew timed.proto
timed.sched
8.0
Option timed.window
Change This option has become obsolete.
Release changed 8.0
Requirements for running Data ONTAP 8.0 7-Mode | 39
Requirements for running Data ONTAP 8.0 7-Mode

You can use this information to verify that you have the storage systems and firmware needed to run Data ONTAP 8.0 7-Mode and later, and in particular, to create high-availability configurations formerly known as clusters. To find out your storage system model's system capacity and maximum volume size, see the System Configuration Guide.
Next topics
Supported systems on page 39 Unsupported systems on page 40 Storage system firmware on page 40 Storage systems that support Multipath Storage on page 41 V-Series requirements and support information on page 42
Related information
System Configuration Guide: now.netapp.com/NOW/knowledge/docs/hardware/NetApp/syscfg/
Supported systems
You need one of the supported storage systems listed in this section to run Data ONTAP 8.0 7-Mode. The following models of storage systems are supported: 60xx 3140 3160 3170 3040 3070 2040 SA600 SA300
All systems supported by Data ONTAP 8.0 7-Mode can be configured in a high-availability configuration. Data ONTAP 8.0 7-Mode also supports the DS4243 disk shelf, 2 TB disk drives, and the 10GbE Chelsio X1107 network adapter. For more information, see the System Configuration Guide.
Unsupported systems
There are some storage systems that are not supported in Data ONTAP 8.0 7-Mode. The following NetApp storage systems models are not supported in Data ONTAP 8.0 7-Mode: 9xx GF900 2xx GF270c R200 2020 2050 3020 3050 SA200
Storage system firmware

You need to confirm that you have the latest firmware for your storage system, disks, and disk shelves. The following storage system components have firmware that sometimes requires upgrading: Motherboards (their firmware is also known as system or storage system firmware) Disk drives Disk shelves
Storage system firmware It is best to upgrade to the latest version of storage system firmware. For a list of available system firmware, see the "System Firmware Release Table" on the NOW site.
Note: The latest system firmware is included with Data ONTAP upgrade packages. For more
information, see the Data ONTAP 8.0 7-Mode Upgrade Guide. Disk firmware For information about the latest disk firmware, see the "Disk Drive & Firmware Matrix" on the NOW site.
Requirements for running Data ONTAP 8.0 7-Mode | 41

Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For more
information, see the Data ONTAP 8.0 7-Mode Upgrade Guide. Disk shelf firmware For information about the latest disk shelf and ESH (Embedded Switched Hub) firmware, see the "Disk Shelf & ESH Firmware Matrix" on the NOW site.
Related information
System Firmware Release Table: now.netapp.com/NOW/cgi-bin/fw Disk Drive & Firmware Matrix: now.netapp.com/NOW/download/tools/diskfw/ Disk Shelf & ESH Firmware Matrix: now.netapp.com/NOW/download/tools/diskshelf/
Storage systems that support Multipath Storage

To configure Multipath Storage, which provides redundancy for the path from each controller to every disk shelf in the configuration and is the preferred cabling method, you need to have a supported storage system, disk shelves and modules. Multipath Storage is supported on the following NetApp storage systems and disk shelves: All FAS systems All SA systems V60xx,V30xx, and V31xx storage systems All disk shelves except the following disk shelves and modules: Non-RoHS-compliant ESH2 modules Non-RoHS-compliant AT-FCX modules
Note: While Multipath adds value to a stretch MetroCluster environment, it is not necessary in a
fabric-attached MetroCluster configuration because multiple paths already exist. The only V-series systems that support native disk shelves are V60xx, V30xx, and V31xx . Therefore, they are the only V-series models for which Multipath Storage applies on V-Series systems. On each node in an active/active configuration of V-Series systems using native disk shelves, you must configure the fc-non-array-adapter list environment variable for the first disk shelf on a new loop to the V-Series system.
Note: Setting the fc-non-array-adapter list environment variable is not required on
V-Series systems configured with DS4243 disk shelves.
V-Series requirements and support information

Not all Data ONTAP releases support the same features, configurations, storage system models, and storage array models for V-Series systems. The V-Series Support Matrix is the final authority on supported configurations, storage array firmware and microcode versions, switches, and so on. See the V-Series Support Matrix for complete information about supported V-Series models and storage arrays, as well as supported microcode, license code, and storage array firmware versions. The V-Series Support Matrix also identifies switch connectivity and topology that can be used with V-Series systems. You can access the V-Series Support Matrix on the NOW site.
Requirements for V-Series fabric-attached MetroCluster configurations

V-Series fabric-attached configurations require in-order delivery of FC-VI traffic. If the FC-VI traffic is not delivered in order, there are problems with cluster takeover. For example, each node might be up and running but the results of the cf status command might show "cluster takeover disabled" or might be cycling "cluster takeover disabled" and "cluster takeover enabled." See the V-Series MetroCluster Guide for information about the circumstances when you need to configure switches, hardware, or both to support in-order delivery of FC-VI traffic.
Important cautions | 43
Important cautions
Before deploying this release of Data ONTAP, make sure that you read the following items to identify and resolve issues that might affect the operation of your storage systems. To request more information about an individual bug and to explore other bug-related tools, see Bugs Online on the NOW site.
Next topics
Unsupported features on page 43 Upgrade and revert cautions on page 44 Block access protocol cautions on page 53 Data protection cautions on page 54 Manageability cautions on page 56 Network protocol cautions on page 57 File access and protocols cautions on page 58 Storage management cautions on page 58
Related information
Unsupported features
Some Data ONTAP features are not supported in the Data ONTAP 8.0 7-Mode release. Features not available in Data ONTAP 8.0 7-Mode If you have configured any of the following features, do not upgrade to Data ONTAP 8.0 7-Mode: NetApp SnapValidator for Oracle not supported on page 54 Upgrade issues if you have SnapLock on page 55 SMB 2.0 is not supported on page 58 IPv6 is not supported on page 57 512-GB and 256-GB Performance Acceleration modules not supported on page 55
Doing so might cause your system to halt or make storage data unavailable to your clients. If you require these features in your business environment, contact your NetApp representative to evaluate the best upgrade path.
44 | Data ONTAP 8.0 7-Mode Release Notes If you have configured any of the following features in an earlier Data ONTAP release, they are disabled during the upgrade to Data ONTAP 8.0 7-Mode: Data Motion is not supported on page 26 TLS is not supported in Data ONTAP 8.0 7-Mode on page 56 If you need to boot the storage system from a Data ONTAP image stored on a remote server on page 56 IPsec is not supported on page 58 TOE is not supported on page 58 Compression for SnapMirror transfers not supported on page 55
The storage system will continue to function but without the services provided by these features. Features discontinued in Data ONTAP 8.0 7-Mode Beginning in Data ONTAP 8.0 7-Mode, the following features are discontinued: Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 16 If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later on page 45 Hardware-based disk ownership Media kits SnapVault for NetBackup
Upgrade and revert cautions

If you are upgrading to this Data ONTAP release or reverting from this release to an earlier release, you should review these issues, and if any apply in your environment, take appropriate action. For more information about these cautions, see the Data ONTAP 8.0 7-Mode Upgrade Guide.
Next topics
If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later on page 45 If you are updating a system with AT-FCX disk shelves attached on page 46 If your system includes DS14 shelves, ESH modules, or LRC modules on page 46 If you are upgrading a FAS3140/FAS3170 system from Data ONTAP version 7.3 or earlier to version 8.0 in an iSCSI environment on page 46 Do not remove the special system files that are for restoring LUNs in snapshot copies on page 47 If you are upgrading to Data ONTAP 8.0 7-Mode or later from a release earlier than Data ONTAP 7.3 on page 47 If your root FlexVol volume does not meet the new size requirements on page 48
Important cautions | 45 If you are performing a nondisruptive upgrade on a system with VMware ESX Server hosts on page 48 If you are upgrading a system that includes FlexVol volumes on page 49 If you are upgrading a system that includes deduplicated volumes on page 49 If your system uses rtc or rdate as the protocol for time synchronization on page 50 If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7-Mode on page 50 If you have been using the flex_cache license on page 50 If you revert from Data ONTAP 8.0 7-Mode and attempt to access LUN data in a Snapshot copy on page 51 If you are reverting to a Data ONTAP release with a lower maximum capacity on page 52 If you are reverting to a previous release and you use deduplication on page 52
If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later
You must obtain Data ONTAP upgrade images from the NOW site and copy them to your storage system. Media kits, including CD-ROMs with upgrade images, are no longer available, and the process of installing upgrade images from UNIX or Windows clients is no longer supported. Beginning with Data ONTAP 8.0 7-Mode, media kits including CD-ROMs are no longer available. You must obtain upgrade images from the NOW site and copy them to your storage system or to an HTTP server in your environment. Beginning with Data ONTAP 8.0 7-Mode, the following processes are no longer supported for extracting and installing Data ONTAP upgrade images: Using the tar command from UNIX clients Using the setup.exe file and WinZip from Windows clients
For the upgrade to Data ONTAP 8.0 7-Mode and later releases, .exe images are no longer available. You must use one of the following image types depending on the upgrade you are performing: .zip images, for upgrades from an earlier release family to Data ONTAP 8.0 7-Mode .tgz images, for upgrades from any Data ONTAP 8.0 7-Mode release to a later release
Once you have upgraded to Data ONTAP 8.0 7-Mode or later, you can only use .tgz images for further upgrades. Once you have copied the .zip or .tgz image to your storage system, you can install it with the software update command. Alternatively, you can make the .zip or .tgz image available from an HTTP server in your environment, then use the software update command to copy the upgrade image from the HTTP server, extract and install the system files, and download the files to the boot device with one command. For more information about upgrade images, see the Data ONTAP 8.0 7-Mode Upgrade Guide.
If you are updating a system with AT-FCX disk shelves attached

If your AT-FCX disk shelf is running firmware version 37 or later, you can perform firmware updates to that shelf without causing a pause in I/O operations from that shelf. However, the shelf.fw.ndu.enable option must be set to on. In some earlier Data ONTAP versions before nondisruptive AT-FCX firmware upgrades were supported, the shelf.fw.ndu.enable option was set to off by default. Because of a known problem in later releases, the option is not automatically set to on during Data ONTAP upgrades, even when nondisruptive shelf firmware upgrades are supported in the later version. Therefore, before performing a nondisruptive upgrade to your AT-FCX shelf firmware, you should ensure that the shelf.fw.ndu.enable option is set to on.
Note: If you are planning to use the nondisruptive method (NDU) to upgrade Data ONTAP software,
you must update shelf firmware to the latest version before upgrading Data ONTAP.
Related information
Bug ID 396599: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=396599
If your system includes DS14 shelves, ESH modules, or LRC modules

Beginning with Data ONTAP 7.3, DS14 disk shelves (sometimes referred to as DS14mk1), LRC storage I/O modules, and ESH storage I/O modules are no longer supported. Upgrading a system with any of these devices attached to it will result in an unsupported configuration. If even one of these devices is attached to your storage system, you should not upgrade to Data ONTAP 7.3 or later. For more information, see Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 16 .
If you are upgrading a FAS3140/FAS3170 system from Data ONTAP version 7.3 or earlier to version 8.0 in an iSCSI environment
If you are running iSCSI traffic on your FAS3140/FAS3170 system and you are upgrading from Data ONTAP version 7.3 or earlier to version 8.0, you will no longer be able to run iSCSI traffic on the e0m interface.
Considerations
In addition, if you revert from Data ONTAP version 8.0, the e0m interface remains disabled for iSCSI traffic by default. Finally, if you revert from Data ONTAP version 8.0, the following changes will occur: Target portal group configuration related to e0m may change. e0m may be removed from the iSCSI access list configuration.
After You Finish
For additional technical details on this issue, see bug 379056 in Bugs Online. If changes do occur to target portal group configurations after upgrade, refer to the Public Report in bug 379056 for information about how to solve the problems.
Do not remove the special system files that are for restoring LUNs in snapshot copies
For storage systems upgraded from a release earlier than Data ONTAP 8.0, some system files are automatically added to every volume of the system. You must not remove or modify these files unless technical support directs you to do so. These files enable you to restore LUNs in Snapshot copies if you revert to a release earlier than Data ONTAP 8.0. The following system files are added to the root level of every volume, including the root volume:
.vtoc_internal .bplusvtoc_internal
If you are upgrading to Data ONTAP 8.0 7-Mode or later from a release earlier than Data ONTAP 7.3
Upgrading to Data ONTAP 8.0 7-Mode or later from a release earlier than Data ONTAP 7.3 will cause existing FlexVol volumes to require more free space from their containing aggregate. Data ONTAP 7.3 includes an improvement to free space accounting. As a result, existing FlexVol volumes reserve additional space, resulting in a loss of 0.5% of free space.
Attention: You should ensure that all systems upgrading to Data ONTAP 7.3 or later have at most
96 percent used space in their aggregates. If there is insufficient free space in an aggregate to satisfy the increased requirement from its FlexVol volumes, the space guarantee for one or more volumes in that aggregate could be disabled. For more information, see the Data ONTAP 8.0 7-Mode Upgrade Guide. Determining system capacity and space guarantees If you suspect that your system has almost used all of its free space, or if you use thin provisioning, you should check the amount of space in use by each aggregate. If any aggregate is 97 percent full or more, do not proceed with the upgrade until you have used the Upgrade Advisor or aggrSpaceCheck tools to determine your system capacity and plan your upgrade.
Steps
1. Check your system's capacity by entering the following command:

df -A
If the capacity field shows ... 96% or less for all aggregates 97% or more for any aggregate
Then ... You can proceed with your upgrade to Data ONTAP 7.3; no further action is required. Continue with step 2.
2. Use a Web browser to go to the NOW Web site and select the appropriate upgrade tool for your environment.
If your system ... Is configured to send AutoSupport messages to NetApp Then ... Continue to plan your upgrade with the Upgrade Advisor tool.
Is not configured to send AutoSupport messages to Continue to plan your upgrade with the NetApp aggrSpaceCheck tool.
These tools can assess the free space requirements for your system in Data ONTAP 7.3 and later releases. If you do not have sufficient free space, the tools will recommend a course of action to ensure a successful upgrade.
Note: The Upgrade Advisor can also assess other upgrade requirements and recommend solutions.
Using it is the recommended upgrade methodology. After using these tools and completing the upgrade, make sure that your space guarantees are configured according to your requirements.
If your root FlexVol volume does not meet the new size requirements
The minimum required size for root FlexVol volumes has been increased for every system running Data ONTAP 8.0 7-Mode and later. If your root FlexVol volume does not meet the new requirements, you should increase its size as soon as you complete the upgrade procedure. The root volume must have enough space to contain system files, log files, and core files. If a system problem occurs, these files are needed to provide technical support. For more information about root volumes and the root FlexVol volume requirements for your platform, see the Data ONTAP 8.0 7-Mode System Administration Guide.
If you are performing a nondisruptive upgrade on a system with VMware ESX Server hosts
Before performing a nondisruptive upgrade on storage systems exporting data over NFS to VMware ESX Server hosts, you should verify that your clients' NAS components are correctly configured. This verification will help ensure that VMware guest operating systems do not experience service disruption during the upgrade.
Important cautions | 49 In particular, the following parameters should be set correctly: NFS Heartbeat parameters on the ESX Server Timeout values for SCSI disks on guest operating systems
It is also highly recommended that the file systems using virtual machine disk format (VMDK) on Windows be correctly aligned with the storage systems' WAFL file system. For more information about verifying and updating these configurations, see the Data ONTAP 8.0 7-Mode Upgrade Guide.
If you are upgrading a system that includes FlexVol volumes

You must confirm that you have no offline FlexVol volumes on your system. If your storage system includes FlexVol volumes and you are planning to upgrade to Data ONTAP 8.0 7-Mode from an earlier release family, confirm that no FlexVol volumes on your system are offline. If you do upgrade your system with offline FlexVol volumes, ensure that they are brought online before you use these volumes as destination volumes in any vol copy operations.
Related information
Bug ID 332448: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=332448 Determining whether your system includes inconsistent FlexVol volumes Use the vol status command to verify the status of your FlexVol volumes.
Steps
1. Enter the following command:

vol status
2. If you find any volumes are marked flex and wafl inconsistent in the Status column, contact technical support immediately and correct the problem before beginning the upgrade process.
If you are upgrading a system that includes deduplicated volumes

You can perform major and minor nondisruptive upgrades when deduplication is enabled provided that no more than 100 FlexVol volumes have deduplication enabled, and that no deduplication operations are running during the Data ONTAP upgrade. For information about deduplication, see the Data ONTAP 8.0 7-Mode Storage Management Guide and the sis(1) man page.
If your system uses rtc or rdate as the protocol for time synchronization
Starting with Data ONTAP 8.0 7-Mode, the Network Time Protocol (NTP) protocol is the only supported protocol for time synchronization. The rtc and the rdate protocols of the timed.proto option are obsolete and no longer take effect after you upgrade to Data ONTAP 8.0 7-Mode or later. If your system does not already use NTP as the time-synchronization protocol, it will not keep accurate time after you upgrade it to Data ONTAP 8.0 7-Mode or later. Problems can occur when the storage system clock is inaccurate. If your system does not use NTP as the protocol for time synchronization, immediately after upgrading to Data ONTAP 8.0 7-Mode or later you must set timed.proto to ntp, set timed.servers to use time servers that support NTP, and ensure that timed.enable is set to on.
Note: After you set timed.proto to ntp, the setting remains in effect even if you revert back to a
release prior to Data ONTAP 8.0 7-Mode. For information about how to synchronize the system time, see the Data ONTAP 8.0 7-Mode System Administration Guide.
If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7-Mode
Starting with Data ONTAP 8.0, several timed options are obsolete although they remain visible in the CLI and can be modified. The following timed options have no effect in Data ONTAP 8.0 7-Mode or later: The timed.max_skew option The timed.sched option The timed.window option The rtc and the rdate protocols of the timed.proto option
If you attempt to set the above options when the system is running Data ONTAP 8.0 7-Mode or later, they will have no effect. However, these settings will take effect after the system is reverted back to a release that supports the options.
If you have been using the flex_cache license

You should install the flexcache_nfs license before upgrading to this release of Data ONTAP. If you do not install the flexcache_nfs license, your FlexCache volumes will not work until you install the license.
If you revert from Data ONTAP 8.0 7-Mode and attempt to access LUN data in a Snapshot copy
Various problems, including a system panic, may result if you attempt to access LUN data in a Snapshot copy when reverting from Data ONTAP 8.0 7-Mode to a prior release. The nature of the problem and its resolution depends on which Release Candidate (RC) you are reverting from, as described in the following table.
Version of Data ONTAP Problem description from which you are reverting 8.0 RC1 You will not be able to access LUNs and LUN clones contained in Snapshot copies created before upgrading to Data ONTAP 8.0. Performing a single file snap restore (SFSR) on one of these LUNs or LUN clones will result in a system panic. Resolution Contact NetApp Global Support.
8.0RC2, 8.0RC3, or 8.0
At some point in the revert Contact NetApp Global Support. process, messages similar to the following may display: Inode 99 in volume vol0 is used by file /vol/vol0/.vtoc_internal. Delete it or make a copy before deleting, then retry "revert_to" command. Inode 98 in volume vol0 is used by file / v o l / v o l 0 / . b p l u s v t o c _ i n t e r n a l . Delete it or make a copy before deleting, then retry "revert_to" command.
52 | Data ONTAP 8.0 7-Mode Release Notes For more information about this issue, refer to bug 371872 in Bugs Online.
If you are reverting to a Data ONTAP release with a lower maximum capacity
When you revert to an earlier Data ONTAP release, your storage system must conform to the maximum capacity limitations of the earlier release. If you upgraded your system to a release that supports greater capacities and you configured storage to utilize the new capacities, you must reconfigure your system to the lower capacity limits before you revert. If you don't reconfigure in this way, the storage system will not boot up following the revert process until the excess capacity has been disconnected. To access any storage in excess of system limits, you must disconnect it from the system you are reverting. Excess capacity must be disconnected for relocation to a different storage system in a way that allows aggregates to remain intact. The system to which storage is relocated must meet the following requirements: It has spare capacity room to accommodate the relocated storage. It is running the same or a later Data ONTAP release as the system where the disks are currently installed. It is running a Data ONTAP release that supports the relocated disks.
For more information about physically moving aggregates, see the Data ONTAP 8.0 7-Mode Storage Management Guide. For more information about maximum capacity limits for a given Data ONTAP release, see the System Configuration Guide entries for that release.
Related information
System Configuration Guide: now.netapp.com/NOW/knowledge/docs/hardware/NetApp/syscfg/
If you are reverting to a previous release and you use deduplication

In Data ONTAP 7.3 and later, the deduplication metadata for a volume is located outside the volume, in the aggregate. Therefore, when you revert from the Data ONTAP 8.0 release family to a previous release that supports deduplication, the deduplication metadata is lost during the revert process. The existing data in the volume will retain the space savings from the deduplication operations performed earlier. However, the new data written to the volume after the revert process will obtain space savings through deduplication within the new data only, and not from the data that existed before the revert process. To use deduplication for all the data within the volume, and thus obtain higher space savings, use the sis start -s command. This command rebuilds the deduplication metadata for all the data in the volume. This process can take several days, depending on the size of the logical data in the volume.
Attention: Before using the sis start -s command, ensure that the volume has sufficient free
space to accommodate the addition of the deduplication metadata. The deduplication metadata uses between 4 and 6 percent of the logical data size in the volume.
Block access protocol cautions

If your storage system is deployed in a SAN environment, you should review these issues and take appropriate action before upgrading or reinstalling. For more information about these issues, see the Data ONTAP 8.0 7-Mode Block Access Management Guide for iSCSI and FC.
Next topics
Identical WWPNs can occur on both nodes in a cluster on page 53 If you deploy ALUA on storage systems with FCP or iSCSI on page 53 If you use Solaris 10 and the emlxs Fibre Channel Adapter driver on page 54 Only single_image cfmode is supported in Data ONTAP 8.0 7-Mode on page 54
Identical WWPNs can occur on both nodes in a cluster

If a system and its disks are disconnected from its partner and then connected to a different partner, it is possible (though rare) that both systems can end up with the same WWPN. This problem exists only with systems in single_image cfmode. If this situation occurs, the systems can behave as if they are both primary systems or both secondary systems, causing each system to compute identical WWPNs for its target ports. As a result, hosts will experience problems trying to access these duplicate ports in the fabric. For detailed information on this problem, including instructions on how to solve it, see bug 268320 in Bugs Online, or see KB 35532.
If you deploy ALUA on storage systems with FCP or iSCSI

If you deploy the T10 Asymmetric Logical Unit Access (ALUA) standard for SCSI on Fibre Channel-enabled storage systems or iSCSI-enabled storage systems, ensure that your hosts support ALUA before enabling ALUA. Enabling ALUA for a host that does not support ALUA can cause host failures during cluster failover. Check the appropriate host compatibility matrix on the Compatibility and Configuration Guide for NetApp FCP and iSCSI Products page on the NOW site to see if ALUA is supported on your host system.
Related information
Compatibility and Configuration Guide for NetApp FCP and iSCSI Products: now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/
If you use Solaris 10 and the emlxs Fibre Channel Adapter driver
If you are using Solaris 10 and the emlxs Fibre Channel Adapter driver, you need to upgrade to the 2.30j version driver or later before you upgrade to Data ONTAP 7.3 or later. For more information, see the Sun solution 231581 at http://sunsolve.sun.com/search/document.do?assetkey=1-66-231581-1.
Only single_image cfmode is supported in Data ONTAP 8.0 7-Mode

For Fibre Channel SAN configurations in Data ONTAP 8.0 7-Mode and later releases, only single_image cfmode (cluster failover mode) is supported. If you are upgrading high availability FC SAN systems from an earlier release and they are configured for any other cfmode, you must migrate them to single_image mode before upgrading to Data ONTAP 8.0 7-Mode or later. For detailed instructions about migrating to single_image cfmode, see Changing the Cluster cfmode Setting in Fibre Channel SAN Configuration.
Related information
Changing the cluster cfmode setting in Fibre Channel SAN configurations http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/
Data protection cautions

If your storage system is configured with licenses for data protection technologies, you should review these issues and take appropriate action before upgrading or reinstalling. For more information about these issues, see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide.
Next topics
NetApp SnapValidator for Oracle not supported on page 54 512-GB and 256-GB Performance Acceleration modules not supported on page 55 Upgrade issues if you have SnapLock on page 55 Compression for SnapMirror transfers not supported on page 55
NetApp SnapValidator for Oracle not supported

NetApp SnapValidator for Oracle is not supported in Data ONTAP 8.0 7-Mode. For more information, contact NetApp technical support.
512-GB and 256-GB Performance Acceleration modules not supported

512-GB and 256-GB Performance Acceleration modules are not supported in Data ONTAP 8.0 7-Mode. Contact technical support for additional information.
Upgrade issues if you have SnapLock

SnapLock is not supported in Data ONTAP 8.0 7-Mode. A storage system will halt if it contains SnapLock volumes and is upgraded to Data ONTAP 8.0 7-Mode. Therefore, if you are running SnapLock on your current release of Data ONTAP, you should not upgrade to Data ONTAP 8.0 7-Mode. For more information, see the Data ONTAP 8.0 7-Mode Upgrade Guide. If you run the following commands with options related to SnapLock, they will not work and you will see a snaplock license is required message: vol create -L aggr create -L date -c date -c initialize
Download of Data ONTAP 8.0 7-Mode on a storage system with SnapLock volume fails If you attempt to download Data ONTAP 8.0 7-Mode on a storage system running Data ONTAP 7.3.2 or later with SnapLock volumes, the storage system displays the following error message.
download: Cannot download 8.0 because SnapLock Compliance volumes exist on the system and the target release does not support SnapLock Compliance volumes.
However, if you attempt to download Data ONTAP 8.0 7-Mode on a storage system running Data ONTAP 7.3.1 or previous releases with SnapLock volumes, it displays the following error message.
download: Cannot download unpromoted version 0 on a system running promoted kernel with snaplock volumes
Compression for SnapMirror transfers not supported

Compression for SnapMirror transfers is not supported in Data ONTAP 8.0 7-Mode. Although you can enable compression for a SnapMirror relationship by specifying the option in the snapmirror.conf file, this feature is not supported in Data ONTAP 8.0 7-Mode.
Manageability cautions
If you are a storage system administrator, you should familiarize yourself with these manageability issues. For more information about these cautions, see the Data ONTAP 8.0 7-Mode System Administration Guide.
Next topics
If you need to boot the storage system from a Data ONTAP image stored on a remote server on page 56 TLS is not supported in Data ONTAP 8.0 7-Mode on page 56 RLM over IPv6 not supported in Data ONTAP 8.0 on page 56 New RLM firmware and its upgrade requirements on page 57
If you need to boot the storage system from a Data ONTAP image stored on a remote server
In Data ONTAP 8.0 7-Mode, netboot is not a supported function, unless you are restoring the Data ONTAP image on the boot device, such as a PC CompactFlash card. If you need to boot the storage system from a Data ONTAP image stored on a remote server, contact technical support. For information about how to replace a PC CompactFlash card or restore the Data ONTAP image on the card, see the Replacing a CompactFlash Card flyer that is applicable to your version of Data ONTAP.
TLS is not supported in Data ONTAP 8.0 7-Mode

Transport Layer Security version 1.0 (TLSv1.0) was introduced in a previous Data ONTAP release, but it is not a supported function in Data ONTAP 8.0 7-Mode. If you enabled TLS in a previous Data ONTAP release, it is no longer available when you run Data ONTAP 8.0 7-Mode , and SSL is used instead for communication.
RLM over IPv6 not supported in Data ONTAP 8.0

If you upgrade from the Data ONTAP 7.3 release family and your RLM is configured with IPv6, existing IPv6 configuration is automatically removed during the upgrade because IPv6 is not supported in Data ONTAP 8.0. If your RLM configuration does not include static IPv4 or DHCP IPv4 , you need to reconfigure the RLM after upgrading to Data ONTAP 8.0 using the rlm setup command. For information about the RLM, see the Data ONTAP 8.0 7-Mode System Administration Guide.
New RLM firmware and its upgrade requirements

RLM firmware versions 4.0 and later require a different layout on flash media. You must ensure that you are running the latest 3.1.x RLM firmware to enable the transition to the new layout, then update to the 4.0 or later firmware. You must be running the latest 3.1.x to update to 4.0. If you are running a firmware version earlier than 3.1, you must first perform an intermediate update to the latest 3.1.x firmware, then update from 3.1 to 4.0 in a separate operation.
Attention: Regardless of whether you update RLM firmware from the Data ONTAP CLI or the
RLM CLI, do not update directly from a firmware version earlier than 3.1 to 4.0 or later. Doing so will corrupt the RLM flash device. If you are updating to version 4.0 or later from the Data ONTAP CLI, you must run the rlm update command with the -f advanced option. Further updates do not require the advanced option. If you are updating RLM firmware from the RLM CLI, you can use the normal procedure. For information about installing and updating the RLM firmware, see the Data ONTAP 8.0 7-Mode Upgrade Guide. For information about configuring the RLM, see the Data ONTAP 8.0 7-Mode System Administration Guide.
Network protocol cautions

If you use FilerView to manage network interfaces or if your network configuration includes a vif, you should review these issues and take appropriate action before upgrading. For more information about these issues, see the Data ONTAP 8.0 7-Mode Network Management Guide.
Next topics
IPv6 is not supported on page 57 IPsec is not supported on page 58 TOE is not supported on page 58
IPv6 is not supported

IPv6 is not supported in Data ONTAP 8.0 7-Mode. If you want to upgrade from a Data ONTAP version that supports IPv6 to Data ONTAP 8.0 7-Mode, see the Data ONTAP 8.0 7-Mode Upgrade Guide.
IPsec is not supported

IPsec is not supported in Data ONTAP 8.0 7-Mode. If IPsec is enabled on your storage system, be aware that it will be disabled automatically during the upgrade to the Data ONTAP 8.0 7-Mode release family.
TOE is not supported

In Data ONTAP 8.0 7-Mode, the TOE functionality is not supported. There is no adverse effect on the performance of your storage system because TOE is disabled.
File access and protocols cautions

This information addresses file access and protocols cautions. Review the following section for important information regarding file access and protocols management. For more information about these cautions, see the Data ONTAP 8.0 7-Mode File Access and Protocols Management Guide
SMB 2.0 is not supported

SMB 2.0 is not supported in Data ONTAP 8.0 7-Mode. Although Data ONTAP continues support for the original SMB protocol, the SMB 2.0 protocol is not supported in Data ONTAP 8.0 7-Mode. Support for the SMB 2.0 protocol is planned for a future release.
Storage management cautions

If you have DS2342 disk shelves attached to your storage system, you should review DS2342 disk shelves issues and take appropriate action. For more information about these issues, see the Data ONTAP 8.0 7-Mode Storage Management Guide.
Using ACP can cause system panic

If you have DS4243 disk shelves attached to your storage system, you should disable ACP by setting the acp.enabled option to off. Failure to do so could result in a system panic. You can use your DS4243 disk shelves without enabling ACP. For more information about this issue or to determine when a fix is available, see bug 403446 in Bugs Online.
Important cautions | 59 For more information about the DS4243 disk shelf, see the DS4243 Installation and Service Guide.
Known problems and limitations | 61
Known problems and limitations

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds to avoid these behaviors, have been identified in this release. To request more information about an individual bug and to explore other bug-related tools, see Bugs Online on the NOW site.
Next topics
Manageability issues on page 61 Network protocol issues on page 62 File access protocol issues on page 62 Block access protocol issues on page 63 Data protection issues on page 66 Storage resource management issues on page 69 Third-party storage issues (V-Series systems only) on page 72 High-availability configuration issues on page 73
Related information
Manageability issues
You might have to familiarize yourself with some issues related to manageability in this release.
Next topics
RLM configuration is not saved if the RLM's Ethernet cable is not connected on page 61 Issues regarding the EMS timed log on page 61
RLM configuration is not saved if the RLM's Ethernet cable is not connected
If the RLM's Ethernet cable is not connected when you use the rlm setup command to configure the RLM, after connecting the cable you must rerun rlm setup.
Issues regarding the EMS timed log

The NTP Daemon automatically adjusts the storage system time to keep the system clock in sync with the specified NTP server. However, due to a regression effect, EMS does not log the time adjustments even when the timed.log option is set to on.
Network protocol issues

If your storage systems are configured for Brocade switches, TOE devices, VLANs, NIS, or IPSec, you might need to familiarize yourself with current network protocol issues. For more information about these issues, see the Data ONTAP 8.0 7-Mode Network Management Guide.
Next topics
Enable caching with NIS lookup on page 62 Entries in the NIS group file should not exceed 1024 characters on page 62
Enable caching with NIS lookup

If you use NIS for group lookup services, disabling NIS group caching can severely degrade performance. Whenever you enable NIS lookups (with the nis.enable option), make sure to also enable caching (with the nis.group_update.enable option). Failure to enable these two options together could lead to timeouts as CIFS clients attempt authentication.
Entries in the NIS group file should not exceed 1024 characters
Data ONTAP supports a maximum of 1024 characters per line in the /etc/group file on the NIS server. NIS group file entries with more than 1024 characters can result in denials for logins. To avoid login denials, you must reorganize NIS group entries such that each line does not exceed 1024 characters. For more information, see Bug ID 19563 in Bugs Online.
Related information
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=19563
File access protocol issues

If your storage systems provide CIFS, NFS, or FTP client services, you might need to familiarize yourself with file access protocol issues. For more information about these issues, see the Data ONTAP 8.0 7-Mode File Access and Protocols Management Guide.
Next topics
Client notification messages in Windows domains require NetBIOS on page 63 Configuration issue for clients that mount NFS shares using a non-reserved port on page 63
Client notification messages in Windows domains require NetBIOS

The Windows client notification feature used for client messaging, shutdown notices, and vscan alerts requires NetBIOS over TCP to be enabled in Data ONTAP. Similarly, NetBIOS over TCP must be enabled on Windows clients and the Windows Messenger service must be running. By default, the Windows Messenger service is disabled on Windows 2003 and Windows XP SP2 clients.
Configuration issue for clients that mount NFS shares using a non-reserved port
The nfs.mount_rootonly option should be set to off on a storage system that must support clients that mount NFS shares using a non-reserved port even when the user is logged in as root. Such clients include Hummingbird clients and Solaris NFS/IPv6 clients. If the nfs.mount_rootonly option is set to on, Data ONTAP allows only clients that use reserved ports (that is, ports with numbers lower than 1024) to mount the NFS shares.
Block access protocol issues

If your storage systems are part of a SAN environment, you might need to familiarize yourself with block access protocol issues in this release. For more information about these issues, see the Data ONTAP 8.0 7-Mode Block Access Management Guide for iSCSI and FC.
Next topics
Brocade 200E switch speed must be set manually on page 63 Disks offline in Windows 2008 after a standard upgrade on page 64 iSCSI Target HBA support on page 65 If an iSCSI target HBA fails on page 65 If you use the automatic sizing feature on thinly provisioned LUNs when snap reserve is set to a non-zero value on page 65
Brocade 200E switch speed must be set manually

When set with link speed auto-negotiation, Brocade 200E switches do not always attain maximum expected connection speeds with attached devices. By default, both Brocade 200E (4 Gbps) switch ports and QLogic host bus adapters (HBAs) are set to negotiate connection link speeds automatically. However, link speed auto-negotiation between 200E
64 | Data ONTAP 8.0 7-Mode Release Notes Switch ports and QLogic HBAs might not always result in the maximum expected connection speed, thus degrading performance. As an example, an expected 4-Gbps link might only carry traffic at 2 Gbps. To avoid this problem, do not use the link speed auto-negotiation feature on the Brocade 200E switch. Instead, manually set individual 200E switch ports at the desired maximum link speed that matches the speed capability of the connected device.
Note: This problem might also affect connections between Brocade 200E switches and other devices,
such as Fibre Channel adapters and disk shelves. For this reason, you should manually set the Brocade 200E switch speed for connections to all devices.
Related information
Bug ID 245884: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=245884 Setting Brocade 200E switch speed manually You can use the Brocade switch console interface to configure link speed settings.
Steps
1. Enter the following command at the switch console to manually set the speed:
portCfgSpeed port_number speed_level
2. Enter the following command at the switch console to verify the link speed:
switchshow
Disks offline in Windows 2008 after a standard upgrade

During a standard upgrade to Data ONTAP 7.3.3, LUNs are assigned new revision numbers. Windows Server 2008 software interprets the LUNs with new revision numbers as new disks and sets them offline; this status is shown in Windows 2008 management interfaces after the upgrade. Windows Server 2003 ignores the LUN revision number. You can work around this problem using the nondisruptive upgrade method, which allows the LUN revision numbers to retain their previous version. You can also bring the disks online after the upgrade using Windows disk management tools or SnapDrive functionality. For more information, see the knowledgebase article Disks show as offline in Windows 2008 after Data ONTAP upgrade on the NOW site.
Related information
Disks show as offline in Windows 2008 after Data ONTAP upgrade: now.netapp.com/Knowledgebase/solutionarea.asp?id=kb54672
iSCSI Target HBA support

Some storage systems support the use of an iSCSI target HBA, which contains special network interfaces that offload part of the iSCSI protocol processing. You cannot combine these iSCSI hardware-accelerated interfaces with standard iSCSI storage system interfaces in the same target portal group. If you attempt to combine these interfaces, an error message is displayed.
If an iSCSI target HBA fails

If your iSCSI target HBA fails, the iSCSI initiators connected to this HBA might time out, prompting the following error message on the storage system: iSNAP.fw.Crashed. The timeout on the iSCSI initiators might be caused by HBA firmware defects, hardware failure, or device driver defects.
Note: If MPIO is configured on the hosts, I/O should be re-routed as expected, preventing any
disruption in service. For more details, including a workaround for this problem, see the Knowledgebase article What do "iSNAP.fw.Crashed" and "iSNAP.fw.GetCrash.Error" messages mean?.
Related information
What do "iSNAP.fw.Crashed" and "iSNAP.fw.GetCrash.Error" messages mean? http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb42930
If you use the automatic sizing feature on thinly provisioned LUNs when snap reserve is set to a non-zero value
Generally, before you thinly provision LUNs, you should set snap reserve to zero. However, there are rare exceptions that require you to set snap reserve to a value other than zero. In these instances, you must use the automatic sizing feature for thinly provisioned LUNs in FlexVol volumes to work properly.
Considerations
Using the automatic sizing feature is required because the space from deleted Snapshot copies can only be used to fulfill Snapshot space requests. Furthermore, the automatic deletion process will not begin until the snap reserve value is exceeded.
Step
1. Enter the following command:

vol autosize vol_name [-m size] [-I size] on -m size is the maximum size to which the volume will grow. Specify a size in k (KB), m (MB), g (GB), or t (TB).

-I size is the increment by which the volume's size increases. Specify a size in k (KB), m (MB), g (GB) or t (TB).
If the specified FlexVol volume is about to run out of free space and is smaller than its maximum size, and if there is space available in its containing aggregate, the FlexVol volume's size will increase by the specified increment.
Data protection issues

If you use data protection products that include Snapshot technology (such as SnapRestore, SnapVault, SnapMirror, and SnapManager), you might have to familiarize yourself with relevant data protection issues. For more information about these issues, see the Data ONTAP 8.0 7-Mode Data Protection Online Backup and Recovery Guide and the Data ONTAP 8.0 7-Mode Data Protection Tape Backup and Recovery Guide.
Next topics
Limitations when using SnapVault with nondefault vFiler units on page 66 Restore engine does not honor any mandatory or advisory locks on files on page 67 Restore operation to a non-existent volume restores data to the root volume on page 67 Shutting down a storage system when SMTape operations are active might results in a panic on page 68 Suboptimal space savings with deduplication when 16 GB Performance Acceleration Module is installed on page 68 If you use DataFabric Manager to manage SnapMirror or SnapVault relationships between vFiler units on page 68 Possible effect of creating more than 64 mirrored aggregates preventing disaster recovery from functioning correctly on page 69
Limitations when using SnapVault with nondefault vFiler units

There are certain limitations when using SnapVault with nondefault vFiler units. These limitations apply to all Data ONTAP releases that support nondefault vFiler units. The management of SnapVault secondary (creation or modification of SnapVault relationships and schedules at the SnapVault secondary) is only supported from the default vFiler unit (vfiler0). The management of SnapVault secondary is not supported from a nondefault vFiler context. If the volume containing the SnapVault destination qtree is owned by a nondefault vFiler unit, the SnapVault secondary needs to be managed through the default vFiler unit (vfiler0).
Table 1: vFiler unit support with SnapVault secondary volumes The following table shows vFiler unit support with SnapVault secondary volumes for different combinations.
Management of SnapVault secondary volume
Ownership of SnapVault secondary volume Default vFiler unit (vfiler0) Nondefault vFiler unit Yes No
Default vFiler unit (vfiler0) Nondefault vFiler unit
Yes No
The management of SnapVault primary in a vfiler context is supported.

Table 2: vFiler unit support with SnapVault primary volumes The following table shows vFiler unit support with SnapVault primary volumes for different combinations. Management of SnapVault primary volume Ownership of SnapVault primary volume Default vFiler unit (vfiler0) Default vFiler unit (vfiler0) Yes No Nondefault vFiler unit Nondefault vFiler unit Yes Yes (From a nondefault vFiler context, you can only manage volumes owned by that nondefault vFiler unit.)
DataFabric Manager support for the management of SnapVault relationships DataFabric Manager supports the management of SnapVault relationships for volumes through the default vFiler (vFiler0) context only. When using DataFabric Manager, the following limitations apply for SnapVault relationships involving nondefault vFiler units. You can only view SnapVault relationships configured through the default vFiler unit (vfiler0). You cannot view any SnapVault relationships configured through nondefault vFiler units. You can configure new SnapVault relationships for a volume only through the default vFiler unit (vfiler0), even if the volume belongs to a nondefault vFiler unit.
Restore engine does not honor any mandatory or advisory locks on files
The destination volume for a restore operation might have files with mandatory or advisory locks. When you initiate a restore operation to such a volume, the restore engine does not honor these locks. It ignores these locks and overwrites the files.
Restore operation to a non-existent volume restores data to the root volume

If the destination of your restore operation is a non-existent volume, data is restored to the root volume. Starting from the next Data ONTAP release, this behavior will be changed and the restore operation will abort if you attempt to restore to a non-existent volume.
Shutting down a storage system when SMTape operations are active might results in a panic
If you shut down a storage system that has currently active SMTape operations, it might result in a panic. You must ensure to abort all the active SMTape operations using the smtape abort command before shutting down the storage system.
Suboptimal space savings with deduplication when 16 GB Performance Acceleration Module is installed
When you run a deduplication scan by using the sis start -s command on a volume with existing data and with the 16-GB Performance Acceleration Module installed, you obtain suboptimal space savings.
If you use DataFabric Manager to manage SnapMirror or SnapVault relationships between vFiler units
For Data ONTAP 7.2 and later, SnapMirror and SnapVault relationships can be created using vFiler units. However, DataFabric Manager 3.4 and earlier releases cannot use vFiler units for managing SnapMirror and SnapVault relationships. As a result, you might encounter the following issues: If the snapvault.access and snapmirror.access options on the source system allow access only to the destination vFiler unit, then the relationship creation, scheduled backups, on-demand backups, SnapMirror updates, and SnapMirror resync processes from DataFabric Manager fail, and you receive an error message:
request denied by source filer, check access permissions on source Workaround: To allow access to the destination hosting storage system, set the snapmirror.access and snapvault.access options on the source system.
If the ndmpd.preferred_interfaces option is not specified on the source hosting system, then the backups from DataFabric Manager might not use the correct network interface. Workaround: Enable the ndmpd.preferred_interfaces option on the source hosting system. The backups and SnapMirror updates from DataFabric Manager fail and you receive the error message source unknown. This occurs when both of these conditions are met: A relationship between two vFiler units is imported into DataFabric Manager by auto-discovery or is added manually. The destination hosting system is not able to contact the source vFiler IP address.
Workaround: Ensure that the host name or IP address of the source system that is used to create relationships can be reached from the destination hosting system.

Related information
Possible effect of creating more than 64 mirrored aggregates preventing disaster recovery from functioning correctly
If you create more than 64 mirrored or SyncMirror aggregates per storage system (or per node in a mirrored cluster or MetroCluster), an out-of-date plex might be brought back online after some types of failures. To avoid bringing an out-of-date plex back online, do not create more than 64 mirrored aggregates per system, even though Data ONTAP does not prevent you from doing so.
Storage resource management issues

If you have more than one size of disk installed in your storage system, if you have configured quotas, if you use FlexCache volumes, or if you are using FlexVol volumes on FAS250 systems, you should familiarize yourself with these storage resource management issues.
Next topics
The -m option for the disk replace start command is not recognized on page 69 Attempting to assign more than 500 disks or array LUNs with a single disk assign command causes a system panic on page 70 Down nodes in a cluster containing a FlexCache origin volume can prevent the FlexCache volume from connecting to the origin on page 70 Moving disks to a system running an earlier version of Data ONTAP could cause disk identification issues on page 70 Data ONTAP can silently select varying disk or array LUN sizes when creating an aggregate on page 70 Qtree quotas might prevent explicit quotas from overriding the default on page 72
The -m option for the disk replace start command is not recognized
The Data ONTAP command help and man pages state that you can use the -m option of the disk replace start command to replace a file system disk with a spare disk that has a different rotational speed or pool. In fact, the -m option is not recognized by the disk replace start command. The disk fail command can be used to take the file system disk out of service, but you cannot specify which spare disk Data ONTAP will use to replace the file system disk.
Attempting to assign more than 500 disks or array LUNs with a single disk assign command causes a system panic
You can use the all keyword or wildcards to operate on multiple disks or array LUNs when you use the disk assign command. However, if the disk assign command designates more than 500 disks or array LUNs, the system will panic.
Down nodes in a cluster containing a FlexCache origin volume can prevent the FlexCache volume from connecting to the origin
If your origin volume is on a node running a version of the Data ONTAP 10.0 release family, or is a data-striped volume on a node running a version of the Data ONTAP 8.0 7-Mode release family, and any node in the cluster containing the origin node is down, the FlexCache volume will not be able to establish a connection with that origin.
Moving disks to a system running an earlier version of Data ONTAP could cause disk identification issues
If you remove a disk from a storage system running Data ONTAP 7.3 or later and place it into a storage system running a version of Data ONTAP earlier than 7.3, the software disk ownership information will be incorrect for the earlier version and might prevent Data ONTAP from identifying or correctly assigning the disk. The disk identification issues cannot be solved except by returning the disk to the original storage system and removing the software disk ownership information using the more recent version of Data ONTAP. To avoid causing disk identification issues, always use the recommended procedure for removing a data disk, which includes removing the software disk ownership information from the disk before removing it. For more information, see the Data ONTAP 8.0 7-Mode Storage Management Guide.
Note: V-Series systems support disks starting with Data ONTAP 7.3. Therefore, you cannot move
a disk from a V-Series system to a V-Series system running a version of Data ONTAP earlier than 7.3.
Data ONTAP can silently select varying disk or array LUN sizes when creating an aggregate
If disks or array LUNs of varying size are present in your storage system, relying on automatic disk selection can result in unexpected sizes being selected by Data ONTAP. When you create a new aggregate using automatic disk or array LUN selection, Data ONTAP selects disks or array LUNs based on various criteria including size, speed, and checksum type. To ensure that
Known problems and limitations | 71 the disks or array LUNs selected are the size you want, specify the disk or array LUN size when creating an aggregate. For more information, see Bug ID 264122 in Bugs Online and the na_aggr(1) man page.
Next topics
Adding disks when varying sized disks are in use on page 71 Discovering what disks Data ONTAP will automatically select on page 71
Related information
Bug ID 264122 : now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=264122 Adding disks when varying sized disks are in use When you have disks of different sizes available, always specify the disk size when creating or adding to an aggregate.
Step
1. To specify the disk size when you add a disk to an aggregate, enter the following command:
aggr add aggr_name num_disks@size Example
For example, to add four 635-GB disks to aggr1, enter the following command:
aggr add aggr1 4@635G
Discovering what disks Data ONTAP will automatically select To list which disks would be selected, use the -n option for the aggr create or aggr add command. When you use the -n option, the disks that would be selected automatically, if you created an aggregate or added to an aggregate, are displayed. The creation or addition is not performed. If the selected disks are not what you intended, you can specify a disk list when you enter the aggr create or aggr add command.
Step
1. To list the disks that would be selected for an aggr create command, enter the following command:
aggr create aggr_name -n disk_list Example
For example, to list the disks that would be used for the creation of the newaggr aggregate using eight automatically selected disks, enter the following command:
aggr create newaggr -n 8
Qtree quotas might prevent explicit quotas from overriding the default
If you are overriding a default user or group quota in a volume that has qtrees with quotas applied, the override will not apply within those qtrees unless you also apply the override explicitly to those qtrees. If you have a default user or group quota on a volume, and you want to override that default quota for a particular user or group, note this issue: If you also have one or more qtree quotas on that volume, the explicit quota might not take precedence over the default quota within those qtrees as expected. Overriding default qtree quotas To avoid quota precedence problems, you can override the default quota on the qtrees that have a quota. Suppose you have the following /etc/quotas file:
#Quota target #----------* 14717 /vol/vol1/mytree type ---user@/vol/vol1 user@/vol/vol1 tree disk files thold sdisk sfile ---- ----- ----- ----- ----16K 1M 10M
The presence of the qtree quota causes all users, including user 14717, to be limited to 16 KB of space in the mytree qtree.
Step
1. Add the following line to the quota file to enable overriding the qtree quota with an volume-wide quota of 1 MB:
14717 user@/vol/vol1/mytree 1M
User 14717 is now able to use 1 MB of space anywhere in vol1.
Third-party storage issues (V-Series systems only)

When Data ONTAP uses third-party storage, issues can occur with the switches and storage arrays in the configuration.
Next topics
Exceeding the maximum number of assigned devices results in a panic on page 73 Limitation on EMC CX storage array LUN numbering on page 73
Exceeding the maximum number of assigned devices results in a panic

If more than 256 array LUNs from a specific storage array target port to a specific V-Series FC initiator port are assigned to a V-Series system, the V-Series system panics when you try to boot it. No more than 256 array LUNs from a specific storage array port to a specific V-Series FC initiator port should be assigned (in the Data ONTAP configuration) to a V-Series system. This is a Data ONTAP limitation. If more than 256 LUNs from the same storage array port to the same V-Series FC initiator port are assigned to the V-Series system, the V-Series system panics if you try to boot it and issues a message similar to the following:
PANIC: ../common/raidv2/pool_sort.c:2359: Assertion failure. in SK process config_thread on release NetApp Release 7.3.2
If you assigned more than 256 LUNs from the same storage array target port to the V-Series system, you must remove ownership of enough of the array LUNs so that no more than 256 array LUNs from the same target port to the same V-Series FC initiator are assigned to the V-Series system.
Limitation on EMC CX storage array LUN numbering

If you are not using Storage Groups on your CX storage array, do not assign LUN numbers greater than 254 to array LUNs for V-Series. If you are not using Storage Groups, the CX storage array might not present internal LUNs numbers greater than 254 to your V-Series system. If this occurred, V-Series would not be able to see those array LUNs. If you are using Storage Groups, the CX storage array automatically assigns internal LUN numbers lower than 255.
High-availability configuration issues

If you are using the cf.takeover.on_network_interface_failure option, you might need to familiarize yourself with this high-availability configuration issues. For more information about these issues, see the Data ONTAP 8.0 7-Mode High-Availability Configuration Guide.
Next topics
The ifconfig command and the FAS2040 e0P port on page 74
74 | Data ONTAP 8.0 7-Mode Release Notes If takeover is enabled for network interface failure, automatic giveback should be disabled on page 74
The ifconfig command and the FAS2040 e0P port

Do not use the ifconfig command to configure the e0P port on a FAS2040 system. This port is used to implement the Disk Shelf Alternate Control Path network only and is configured automatically.
If takeover is enabled for network interface failure, automatic giveback should be disabled
If you set the cf.takeover.on_network_interface_failure option to on to enable automatic failover on network interface failures, ensure that you have the cf.giveback.auto.enable option set to off. If the cf.giveback.auto.enable option is set to on, a network interface failure could result in a continuous series of takeovers and givebacks until the network interface problem is resolved.
Changes to published documentation | 75
Changes to published documentation

Some information about this release has become available after the set of guides provided with this release were published. The information should be used in conjunction with the guides provided with this release of Data ONTAP.
Next topics
Changes to the Storage Management Guide on page 75 Changes to the V-Series Implementation Guide for IBM Storage on page 76 Array LUN sizing with 2 TB disks is not documented in all V-Series Implementation Guides on page 76 Changes to the File Access and Protocols Management Guide on page 76
Changes to the Storage Management Guide

New information has become available since the previous revision of the Storage Management Guide.
Next topics
Maximum size of volume without deduplication on page 75 Disk sanitization limitations on page 75 FlexCache limitations on page 76
Maximum size of volume without deduplication

The topic titled "Maximum volume size for different systems" includes incorrect information about the maximum volume sizes without deduplication. The second column titled "Maximum size of volume without deduplication (TB)" in Table 1 contains incorrect information. Non-deduplicated volume sizes can vary based on the platform and aggregate type.
Disk sanitization limitations

The topic titled "Disk sanitization limitations" incorrectly states that disk sanitization cannot be performed on more than one SES disk at the same time. In fact, you can sanitize both SES disks in the same ESH shelf at the same time. However, if you do so, you will see errors on the console about access to that shelf. While the SES disks are being sanitized, shelf warnings (e.g., temperature) will not be reported.
FlexCache limitations
The topic titled "Limitations of FlexCache volumes" should state that if your origin volume is larger than 16 TB, the output of the df command on the caching system shows "----" for the size of the origin volume. To determine the size of the origin volume, run the df command on the origin system.
Changes to the V-Series Implementation Guide for IBM Storage

The V-Series Implementation Guide for IBM Storage dated July 2009, part number 210-04510_A0 contains a statement on page 28 warning about using a specific layout with a DS4xxx storage array. This statement should also warn against using this layout with a DS5xxx storage array. The information on this page should read as follows:
Attention: Do not use this layout if your configuration includes a DS4xxx storage array, DS5xxx
storage array, or any other storage array that implements standby paths to storage. The reason is that if a switch fails, the V-Series systems can only access the array LUNs through opposite storage array controllers. Performance can degrade to the point where the data is unavailable because every access to an array LUN requires Data ONTAP to first change the LUNs affinity.
Array LUN sizing with 2 TB disks is not documented in all V-Series Implementation Guides
Starting with Data ONTAP versions 7.3.3 and 8.0, 2 TB drives are supported on arrays configured with V-Series systems. These larger drives increase the maximum usable size supported for array LUNs. Not all of the V-Series Implementation Guides have been updated to include the supported maximum array LUN sizes. To calculate the maximum array LUN sizes supported with the 2 TB drives, double the maximum usable value that is provided for array LUNs with Data ONTAP 7.3.2. The maximum usable values are provided in the Guidelines for array LUN sizing section of the Implementation Guides.
Changes to the File Access and Protocols Management Guide

The Data ONTAP 8.0 7-Mode File Access and Protocols Management Guide should have included the following topics.
Changes to published documentation | 77

Next topics
SMB 2.0 Support on page 77 Unsupported Windows features in the file serving environment on page 77 NFSv4 client compatibility on page 77 The file fingerprint command can be used for all data files in Data ONTAP 8.0 7-Mode on page 78
SMB 2.0 Support

The SMB 2.0 protocol is not supported in the Data ONTAP 8.0 release. Ignore the SMB 2.0 information in the Configuring SMB section of the "File Access using CIFS" chapter in the File Access and Protocols Management Guide.
Unsupported Windows features in the file serving environment

This release does not support every available Windows feature. For example, this release does not support the following Windows features: Encrypted File System (EFS) Logging of NT File System (NTFS) events in the change journal Microsoft File Replication Service (FRS) Microsoft Windows Indexing Service Remote storage through Hierarchical Storage Management (HSM) Local user account creation from the User Manager or Microsoft Manager Console Quota management from Windows clients Windows quota semantics The LMHOSTS file NT File System (NTFS) native compression
NFSv4 client compatibility

When your NFSv4 clients are in a different domain than your NetApp device is in, you might need to enter the client domain name as the value for the Data ONTAP option nfs.v4.id.domain in order to provide mapping for file ownership and group membership. For more information about mapping options, see RFC 3530 and your client operating system documentation. If you have any client using NFSv4 that needs to access a storage system, ensure that the Data ONTAP option nfs.v4.enable is set to on. In new installations, this option is set to off by default.
Next topics
Unicode character 0x0080 is not supported on page 78
78 | Data ONTAP 8.0 7-Mode Release Notes The FTP server does not support Unicode characters on page 78 Unicode character 0x0080 is not supported If you attempt to create or rename a file or directory from a CIFS client with a name that contains the Unicode character 0x0080, an error will appear. The FTP server does not support Unicode characters The FTP server does not support Unicode characters; thus, file names containing Unicode characters, including Japanese characters, will be displayed in FTP clients with alternate characters used in place of Unicode characters.
Related information
The file fingerprint command can be used for all data files in Data ONTAP 8.0 7-Mode
A fingerprint enables you to check data integrity. You can create fingerprints for all data files by using the file fingerprint command. The fingerprint operation generates a fingerprint on a per-file basis by using the hashing algorithms, MD5 or SHA-256. For more information about the file fingerprint command, see the na_file(1) man page.
Where to find product documentation and other information | 79
Where to find product documentation and other information

You can access documentation for all NetApp products on the NetApp on the Web (NOW) site at now.netapp.com. You can also find other product information resources, such as technical reports and white papers, in the NetApp Library at www.netapp.com.
Next topics
The Documentation Roadmap on page 79 Searching online information on page 80 Finding documentation on NOW on page 80
Related information
NetApp on the Web (NOW) site: now.netapp.com Access & Order Product Documentation: now.netapp.com/knowledge/docs/docs.shtml NetApp Library: Technical Reports: www.netapp.com/library/tr
The Documentation Roadmap

The Documentation Roadmap lists NetApp documents and other information that can help you configure and administer your storage system. The Documentation Roadmap, which you can find on the Data ONTAP Documentation page for this release on the NOW site, lists NetApp documents and NOW pages (including such things as tools and technical reports) that can help you complete the following major tasks: Installing new NetApp systems Configuring new NetApp systems Upgrading Data ONTAP software on NetApp systems Managing NetApp systems Diagnosing and troubleshooting problems Customizing or automating processes
Note: V-Series documents are not included in the Documentation Roadmap. See the V-Series
documents on the NOW site.
Searching online information

The NOW site includes a natural language search tool. The NOW Natural Language PowerSearch tool on the Service and Support page on the NOW site allows you to search the following sources of information: Product manuals Knowledgebase solutions Bugs online Tools/other documentation Partner knowledgebases
Related information
Service and Support: now.netapp.com/eservice/SupportHome.jsp
Finding documentation on NOW

The NOW home page includes links to the current Data ONTAP documentation library. To find the documentation roadmap and the latest documentation for this Data ONTAP release, follow the Documentation links on the NOW site to the Information Library page. You can use this path of links from the NOW home page: Technical Assistance and Documentation Access and Order Product Documentation Data ONTAP Data ONTAP 7-Mode and later: Filer and V-Series systems

Rnote

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Rnote

Загружено:

Авторское право:

Доступные форматы

Data ONTAP 8.

Requirements for running Data ONTAP 8.0 7-Mode................................39

Known problems and limitations................................................................61

Changes to published documentation.........................................................75

Where to find product documentation and other information.................79

Data ONTAP 8.0 7-Mode Release Notes | 13

Data ONTAP 8.0 7-Mode Release Notes

Data ONTAP Release Model -- now.netapp.com/NOW/products/ontap_releasemodel/post70.shtml

16 | Data ONTAP 8.0 7-Mode Release Notes

Bugs Online: now.netapp.com/NOW/cgi-bin/bol/

New platform and hardware support

Support for 2-TB SATA disks

Changes in disk shelf support

Support for DS4243 disk shelf

SSL security improvements

The default security settings

Setup for root account password

The diagnostic account and the systemshell

Boot menu enhancements and changes

Read reallocation of data

20 | Data ONTAP 8.0 7-Mode Release Notes

Extents for FlexVol volumes

Partner recipients for AutoSupport email notifications

AutoSupport message file attachments

New disk drive AutoSupport message sent weekly

Storage resource management enhancements

Support for 64-bit aggregates

Networking and security protocols enhancements

64-bit SNMP object identifiers (OIDs) are supported on page 22

64-bit SNMP object identifiers (OIDs) are supported

MIB file: http://now.netapp.com/NOW/download/tools/mib/

Configuration for receiving untagged traffic on VLAN tagged interfaces

Vifs are now known as interface groups

File access protocol enhancements

Maximum number of auxiliary UNIX groups supported for a user

Block protocol enhancements

iSCSI RADIUS support

Data protection enhancements

If volumes with deduplication exceed the maximum supported size

NearStore license is not required for deduplication

Maximum concurrent deduplication operations supported

Prerequisite for backing up data to tape using NDMP services

Snapshot copy schedules

SnapMirror support for 64-bit volumes

SnapVault support for 64-bit volumes

26 | Data ONTAP 8.0 7-Mode Release Notes

High availability pair (formerly active/active configuration) enhancements

High-availability configuration and high-availability configuration terminology changes

Changes to MultiStore support

Data Motion is not supported

Changes to the Data ONTAP and V-Series libraries

Data ONTAP Information Library page: now.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml

New commands in Data ONTAP 8.0 7-mode

Command acpadmin list_all

30 | Data ONTAP 8.0 7-Mode Release Notes

Command smtape abort

Release Introduced 8.0

Display the status of SMTape-initiated backup and restore operations

storage array modify storage array purge-database

Command storage array remove

Document na_storage(1) man page

Release Introduced 8.0

storage array remove-port