Ontap Release Note

Data ONTAP 8.
0 7-Mode Release Notes
NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S.A. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP Documentation comments: doccomments@netapp.com Information Web: www.netapp.com Part number: 215-05524_A0 3 March 2011
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 Manageability enhancements .................................................................................... 17 SSL security improvements .......................................................................... 17 The default security settings .......................................................................... 17 Setup for root account password ................................................................... 18 The diagnostic account and the systemshell ................................................. 18 Boot menu enhancements and changes ......................................................... 19 Read reallocation of data ............................................................................... 19 Extents for FlexVol volumes ......................................................................... 19 Partner recipients for AutoSupport email notifications ................................. 19 AutoSupport message file attachments ......................................................... 20 New disk drive AutoSupport message sent weekly ...................................... 20 Storage resource management enhancements ........................................................... 20 Support for 64-bit aggregates ........................................................................ 20 Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system ................................................................................... 21 Ability to decrease maxfiles .......................................................................... 21 Networking and security protocols enhancements .................................................... 21 64-bit SNMP object identifiers (OIDs) are supported .................................. 21 Configuration for receiving untagged traffic on VLAN tagged interfaces ... 22 Vifs are now known as interface groups ....................................................... 22 File access protocol enhancements ........................................................................... 22 Maximum number of auxiliary UNIX groups supported for a user .............. 22
4 | Data ONTAP 8.0 7-Mode Release Notes 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 .................................................................................. 23 If volumes with deduplication exceed the maximum supported size ............ 24 Maximum concurrent deduplication operations supported ........................... 24 Prerequisite for backing up data to tape using NDMP services .................... 24 Snapshot copy schedules ............................................................................... 24 SnapMirror support for 64-bit volumes ........................................................ 24 SnapVault support for 64-bit volumes .......................................................... 25 High-availability pair (formerly active/active configuration) enhancements ........... 25 HA pair terminology changes ....................................................................... 25 Changes to MultiStore support .................................................................................. 25 Data Motion is not supported in the Data ONTAP 8.0 7-Mode release family ....................................................................................................... 25 Changes to the Data ONTAP and V-Series libraries ................................................ 26
New and changed commands and options in the Data ONTAP 8.0 7Mode release family ............................................................................... 27
New commands in Data ONTAP 8.0 7-Mode release family ................................... 27 Changed commands in Data ONTAP 8.0 7-Mode release family ............................ 30 Replaced or removed commands in Data ONTAP 8.0 7-Mode release family ........ 32 New options in Data ONTAP 8.0 7-Mode release family ........................................ 33 Changed options in Data ONTAP 8.0 7-Mode release family .................................. 34
Requirements for running Data ONTAP 8.0 7-Mode ............................. 37

Supported systems ..................................................................................................... 37 Unsupported systems ................................................................................................. 38 Storage system firmware ........................................................................................... 38 Storage systems that support Multipath Storage ....................................................... 39 V-Series requirements and support information ....................................................... 40 Requirements for V-Series fabric-attached MetroCluster configurations ..... 40
Important cautions ..................................................................................... 41

Unsupported features ................................................................................................. 41 Upgrade and revert cautions ...................................................................................... 42 If you are upgrading to Data ONTAP 8.0 or later from Data ONTAP 7.x and you use quotas ................................................................................... 43
Table of Contents | 5 Upgrade process changes with Data ONTAP 7-Mode software images ...... 43 Systems including DS14 shelves, ESH modules, or LRC modules .............. 44 Upgrading FAS3140/FAS3170 systems ....................................................... 45 Do not remove the special system files that are for restoring LUNs in snapshot copies ........................................................................................ 45 New FlexVol volume space requirements when upgrading from a release earlier than Data ONTAP 7.3 ...................................................... 45 If your root FlexVol volume does not meet the new size requirements ....... 47 If you are performing a nondisruptive upgrade on a system with VMware ESX Server hosts ...................................................................... 47 If you are upgrading a system that includes FlexVol volumes ..................... 47 If you are upgrading a system that includes deduplicated volumes .............. 48 If your system uses rtc or rdate as the protocol for time synchronization .... 48 If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7-Mode ................................................................................ 48 If you have been using the flex_cache license .............................................. 49 If you are reverting to a Data ONTAP release with a lower maximum capacity .................................................................................................... 49 If you are reverting to a previous release and you use deduplication ........... 50 Block access protocol cautions ................................................................................. 50 Identical WWPNs can occur on both nodes in a cluster ............................... 50 If you deploy ALUA on storage systems with FCP or iSCSI ....................... 50 If you use Solaris 10 and the emlxs Fibre Channel Adapter driver .............. 51 cfmode support change in Data ONTAP 8.0 ................................................. 51 Data protection cautions ............................................................................................ 51 NetApp SnapValidator for Oracle not supported .......................................... 52 512-GB and 256-GB Performance Acceleration modules not supported ..... 52 Upgrade issues if you have SnapLock .......................................................... 52 Compression for SnapMirror transfers not supported ................................... 52 Manageability cautions ............................................................................................. 53 Issues in certificate MD5 signature collision vulnerability ........................... 53 If you need to boot the storage system from a Data ONTAP image stored on a remote server ......................................................................... 53 TLS is not supported in the Data ONTAP 8.0 release family ....................... 53 RLM over IPv6 not supported in the Data ONTAP 8.0 release family ........ 54 Network protocol cautions ........................................................................................ 54
6 | Data ONTAP 8.0 7-Mode Release Notes IPv6 is not supported ..................................................................................... 55 IPsec is not supported .................................................................................... 55 TOE is not supported ..................................................................................... 55 File access and protocols cautions ............................................................................ 55 FTPS is not supported ................................................................................... 55 SFTP is not supported ................................................................................... 55 SMB 2.0 is not supported .............................................................................. 56 New RLM firmware and its upgrade requirements ................................................... 56
Known problems and limitations .............................................................. 57

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

Changes to the Block Access Management Guide for iSCSI and FC ....................... 73 Setting volume options for the autodelete configuration .............................. 73 Correction to configure onboard adapters for target mode ........................... 74 Changes to the File Access and Protocols Management Guide ................................ 75 Correction for disabling virus scanning ........................................................ 75 SMB 2.0 Support ........................................................................................... 76
8 | Data ONTAP 8.0 7-Mode Release Notes Unsupported Windows features in the file serving environment .................. 76 NFSv4 client compatibility ........................................................................... 76 The file fingerprint command can be used for all data files in Data ONTAP 8.0 and later ............................................................................... 77 Changes to the MultiStore Management Guide ........................................................ 77 Corrections to the List of RSH and SSH commands .................................... 77 Corrections to the SnapVault support on vFiler units ................................... 78 Changes to the Data ONTAP Upgrade Guide ........................................................... 79 Additional requirement for AT-FCX disk shelf firmware updates ............... 79
Where to find product documentation and other information .............. 81

Searching online information .................................................................................... 81 Finding documentation on NOW .............................................................................. 82
Copyright information | 9
Copyright information
Copyright 19942011 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 means graphic, 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, Network Appliance, the Network Appliance logo, Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign Express, ComplianceClock, Cryptainer, CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, FAServer, FilerView, FlexCache, FlexClone, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web), ONTAPI, OpenKey, RAID-DP, ReplicatorX, SANscreen, SecureAdmin, SecureShare, Select, Shadow Tape, Simulate ONTAP, SnapCopy, SnapDirector, SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL, and Web Filer are trademarks or registered trademarks of NetApp, Inc. in the United States, other countries, or both. 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 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 7Mode, 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 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: FTPS SFTP SnapLock 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 41. 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 Data ONTAP 8.0.x 7-Mode 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 20. Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode 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 the Data ONTAP 8.0 7-Mode release family 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 at New and changed commands and options in the Data ONTAP 8.0 release family on page 27. 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 20 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 23 High-availability pair (formerly active/active configuration) enhancements on page 25 Changes to MultiStore support on page 25 Changes to the Data ONTAP and V-Series libraries on page 26
16 | Data ONTAP 8.0 7-Mode Release Notes

Related concepts
New and changed commands and options in the Data ONTAP 8.0 7-Mode release family on page 27
Related information
Bugs Online: now.netapp.com/NOW/cgi-bin/bol/
New platform and hardware support

The Data ONTAP 8.0 7-Mode release family supports new hardware as listed. The new platform and hardware are listed in the order of most recently introduced first. For information about supported systems, see Supported systems on page 37.
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 types. 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 20.
Changes in disk shelf support

The Data ONTAP 8.0 7-Mode release family includes some changes to disk shelf support.
Support for DS4243 disk shelf

Data ONTAP 8.0P1 and later releases support the DS4243 disk shelf. The DS4243 disk shelf contains external SAS disk drives and 3Gb I/O modules. The DS4243 disk shelf is also supported on Data ONTAP 7.3.3P2 and later releases. For more information about which disk drives and storage system models are supported with the DS4243 disk shelf, see the System Configuration Guide. For more information about the DS4243 disk shelf, see the DS4243 Disk Shelf Installation and Service Guide.
Related information
System Configuration Guide
Manageability enhancements
Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode 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 18 Boot menu enhancements and changes on page 19 Read reallocation of data on page 19 Extents for FlexVol volumes on page 19 Partner recipients for AutoSupport email notifications on page 19 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: 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
18 | Data ONTAP 8.0 7-Mode Release Notes 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 the Data ONTAP 8.0 release family, 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 the Data ONTAP 8.0 release family, 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 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.
security.passwd.rules.enable is set to on (the default):
The following are the default password rules for all accounts when 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 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.
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. The Data ONTAP 8.0 7-Mode release family allows 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 7Mode 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 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 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.
20 | Data ONTAP 8.0 7-Mode Release Notes 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.
autosupport.mailhost option.
To receive any email-based AutoSupport notifications, you must also define a mail host by using the
AutoSupport message file attachments

In Data ONTAP 8.0 7-Mode and later releases, 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:00 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 20 Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system on page 21 Ability to decrease maxfiles 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.
New and changed features in the Data ONTAP 8.0 7-Mode release family | 21 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.
Ability to decrease maxfiles

Starting in Data ONTAP 8.0, you can decrease the value of the maxfiles parameter for a volume, as long as you do not decrease it below the current number of files stored in the volume. In previous versions of Data ONTAP, you could increase the value of the maxfiles parameter, but not decrease it.
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 21 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 and later, 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 and later, 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 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 7-Mode Upgrade Guide.
Vifs are now known as interface groups

Starting with Data ONTAP 8.0 7-Mode and later, 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 7-Mode Network Management Guide.
File access protocol enhancements

Data ONTAP 8.0 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. For more information about these features, see the Data ONTAP 7-Mode File Access and Protocols Management Guide.
Next topics
Maximum number of auxiliary UNIX groups supported for a user on page 22 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.
New and changed features in the Data ONTAP 8.0 7-Mode release family | 23 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 , 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 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 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. 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 7-Mode Block Access Management Guide for iSCSI and FC.
Data protection enhancements

Data ONTAP 8.0 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 7-Mode Data Protection Online Backup and Recovery Guide and the Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide.

Next topics
If volumes with deduplication exceed the maximum supported size on page 24 Maximum concurrent deduplication operations supported on page 24 Prerequisite for backing up data to tape using NDMP services on page 24 Snapshot copy schedules on page 24 SnapMirror support for 64-bit volumes on page 24 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 7-Mode Storage Management Guide.
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 offline. When the volume becomes online again, Data ONTAP detects the scheduled Snapshot copy creation that has failed and automatically creates a Snapshot copy for that 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 7-Mode Data Protection Online Backup and Recovery Guide.
SnapMirror support for 64-bit volumes

Data ONTAP 8.0 and later releases 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 64bit volumes or they must both be 32-bit volumes.
New and changed features in the Data ONTAP 8.0 7-Mode release family | 25 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 7Mode Data Protection Online Backup and Recovery Guide.
SnapVault support for 64-bit volumes

Data ONTAP 8.0 and later releases 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 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 7-Mode High-Availability Configuration Guide.
HA pair terminology changes

The high-availability (HA) functionality referred to as an HA pair in Data ONTAP 8.0 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 High-Availability Configuration Guide.
Changes to MultiStore support

Data ONTAP provides MultiStore capabilities and changes.
Data Motion is not supported in the Data ONTAP 8.0 7-Mode release family
The Data Motion feature that enables users to migrate vFiler units between storage systems was introduced in a previous release, but it is not supported in Data ONTAP 8.0 7-Mode release family. 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 7-Mode Software Setup Guide now provides information for basic setup of all systems that run Data ONTAP, including a V-Series system. 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 VSeries systems was integrated into the general Data ONTAP guides. This effort was continued in Data ONTAP with the integration of V-Series system setup instructions into the Data ONTAP 7Mode Software Setup Guide. As of Data ONTAP 8.0 7-Mode, there is no longer a separate setup guide for V-Series. 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 now provides 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 family | 27
New and changed commands and options in the Data ONTAP 8.0 7-Mode release family
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 release family on page 27 Changed commands in Data ONTAP 8.0 7-Mode release family on page 30 Replaced or removed commands in Data ONTAP 8.0 7-Mode release family on page 32 New options in Data ONTAP 8.0 7-Mode release family on page 33 Changed options in Data ONTAP 8.0 7-Mode release family on page 34
New commands in Data ONTAP 8.0 7-Mode release family

Many new commands have been added in the Data ONTAP 8.0 7-Mode release family. 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 Command
acpadmin configure
Purpose Configures the ACP subsystem.
Document
Release Introduced 8.0
Data ONTAP 7-Mode Storage Management Guide na_acpadmin(1) man page Data ONTAP 7-Mode Storage Management Guide na_acpadmin(1) man page
acpadmin list_all
Displays information about the ACP (Alternate Control Path) storage subsystem.
8.0
Command
ifgrp
Purpose
Document
Data ONTAP 7-Mode Manages interface groups on your storage Network Management Guide system. This command replaces the vif command. However, the options remain the same.
Aborts a backup or restore job initiated by the SMTape engine.
smtape abort
Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide na_smtape manpage Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide na_smtape manpage Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide na_smtape manpage
8.0
smtape backup
Backs up blocks of data to tape.
8.0
smtape continue
Continues an SMTapeinitiated 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
8.0
smtape restore
Restores blocks of data Data ONTAP 7-Mode from tape. Data Protection Tape
8.0
Backup and Recovery Guide na_smtape manpage
smtape status
Displays the status of SMTape-initiated backup and restore operations Modifies attributes of array profile records.
Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide na_smtape manpage
na_storage(1) man page
8.0
storage array modify
8.0
Command
storage array purge-database
Purpose Removes all records from the controllers array profile database. Removes records for the specified array from the controllers array profile database. Removes ports associated with an array profile. Lists all array profile records known to the controller. Provides a summary of the connectivity to SAN-attached arrays connected to the VSeries systems FC initiator ports.
Document na_storage(1) man page na_storage(1) man page
storage array remove
8.0
storage array remove-port
na_storage(1) man page na_storage(1) man page
8.0
storage array show
8.0
storage array show-config
V-Series Installation Requirements and Reference Guide na_storage(1) man page
8.0
storage array show-luns arrayname storage array show-ports
Lists all array LUNs na_storage(1) man exported from a named page storage array. Lists all target ports for na_storage(1) man all storage arrays page known to the V-Series system. Displays information about the ACP (Alternate Control Path) storage subsystem.
8.0
8.0
storage show acp
Data ONTAP 7-Mode Storage Management Guide na_acpadmin(1) man page
8.0
Changed commands in Data ONTAP 8.0 7-Mode release family

This table lists the commands that have been changed in the Data ONTAP 8.0 7-Mode release family. 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
aggr create
Change The -B option has been added. This option is used to create a 64-bit aggregate. The -x option has been added. This option suppresses the display of the .snapshot lines.
Documentation na_aggr(1) man page
Release command changed in 8.0
Data ONTAP 7-Mode Storage Management Guide

na_df(1) man page 8.0
df
disk assign
You can no longer use na_disk(1) man page this 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 na_environment(1) man Programmable Logic page Device (CPLD) version has been added to the output.
8.0
environment shelf
8.0
Command
storage show expander
Change
Documentation
The system na_storage(1) man page interconnect 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 na_storage(1) man page 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].
storage show expander
8.0
sysconfig
When the -r option is na_sysconfig(1) man page 8.0 used to display disk information for SASconnected disks, the CHAN (channel) column now displays the port as "A" or "B", just as it does for FCconnected 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.
vif
Data ONTAP 7-Mode Network Management Guide

na_vol(1) man page and the Data ONTAP 7-Mode
8.0
vol options
8.0
System Administration Guide
Command
vol options
Change The read_realloc option enables read reallocation but can only be used on FlexVol volumes.
Documentation na_vol(1) man page and the Data ONTAP 7-Mode
System Administration Guide
vol status
When the -r option is na_vol(1) man page used to display disk information for SASconnected disks, the CHAN (channel) column now displays the port as "A" or "B", just as it does for FCconnected disks. Previously, "1" and "2" were used.
8.0
Replaced or removed commands in Data ONTAP 8.0 7-Mode release family

The following information lists replaced or removed commands in Data ONTAP 8.0 7-Mode. 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
New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 33 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 release family

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 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
autosupport.performance_ data.doit any_string
Purpose Triggers a performance snapshot AutoSupport message when any string is added. Triggers a takeover if the partner mode panics. Triggers a takeover if the partner node reboots.
Default Value NA
Release added 8.0
cf.takeover.on_panic
on
8.0
cf.takeover.on_reboot
The default 8.0 is on, unless FCP or iSCSI is licensed, in which case the default is off.
cf.givegack.auto.delay.s econds nfs.max_num_aux_groups
Adjusts the giveback delay time for 300 seconds 8.0 automatic giveback. Specifies the maximum number of auxiliary UNIX groups that a user can be a member of. 32 8.0
fpolicy.multiple_pipes
Enables multiple open instances of on the SMB named pipe on an FPolicy server.
8.0
Changed options in Data ONTAP 8.0 7-Mode release family

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
Change This option has become obsolete. The default for this option has been changed to off for systems shipped with Data ONTAP 8.0 7-Mode or later.
Release changed 8.0 8.0
httpd.admin.enable
httpd.admin.ssl.enable
The default for this option has 8.0 been changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been changed to off for systems shipped with Data ONTAP 8.0 7-Mode or later. 8.0
rsh.enable
ssh.enable
The default for this option has 8.0 been changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has 8.0 been changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has 8.0 been changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later.
ssh2.enable
security.passwd.rules.e veryone
Option
security.passwd.rules.h istory
Change The default for this option has been changed to 6 for systems shipped with Data ONTAP 8.0 7-Mode or later.
Release changed 8.0
telnet.distinct.enable
The default for this option has 8.0 been changed to on for systems shipped with Data ONTAP 8.0 7-Mode or later. The default for this option has been 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. This option has become obsolete. 8.0
telnet.enable
timed.max_skew
8.0 8.0
timed.proto
timed.sched
8.0 8.0
timed.window
Requirements for running Data ONTAP 8.0 7-Mode | 37
Requirements for running Data ONTAP 8.0 7-Mode

You can use the information in this section to verify that you have the storage systems and firmware needed to run Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases, and in particular, to create high-availability configurations. 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 37 Unsupported systems on page 38 Storage system firmware on page 38 Storage systems that support Multipath Storage on page 39 V-Series requirements and support information on page 40
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 a Data ONTAP release in the 8.0 7-Mode family. The following FAS and V-Series storage systems are supported: 6280 6240 6210 60xx 3270 3240 3210 3170 3160 3140 3070 3040 2040
38 | Data ONTAP 8.0 7-Mode Release Notes The following FlexCache storage systems are supported: SA600 SA320 SA300
All systems supported by the Data ONTAP 8.0 7-Mode release family can be configured as an HA pair. For additional information about supported storage systems in the Data ONTAP 8.0 7-Mode release family, see the System Configuration Guide.
Unsupported systems
There are some storage systems that are not supported in the Data ONTAP 8.0 7-Mode release family. The following storage system models are not supported in Data ONTAP 8.0 7-Mode and later releases: FAS3050 3020 2020 2050 9xx GF900 GF270c 2xx R200 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
Requirements for running Data ONTAP 8.0 7-Mode | 39 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 7-Mode Upgrade Guide.
Disk firmware For information about the latest disk firmware, see the "Disk Drive & Firmware Matrix" on the NOW site.
Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For more information, see the Data ONTAP 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 and V-Series systems All SA 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.
40 | Data ONTAP 8.0 7-Mode Release Notes On each node in an HA pair 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 | 41
Important cautions
Before upgrading to 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 41 Upgrade and revert cautions on page 42 Block access protocol cautions on page 50 Data protection cautions on page 51 Manageability cautions on page 53 Network protocol cautions on page 54 File access and protocols cautions on page 55 New RLM firmware and its upgrade requirements on page 56
Related information
Unsupported features
Some Data ONTAP features are not supported in the Data ONTAP 8.0 7-Mode release family. Features not available in the Data ONTAP 8.0 7-Mode release family If you have configured any of the following features, do not upgrade to any releases of Data ONTAP 7-Mode release family:
NetApp SnapValidator for Oracle not supported on page 52 SnapLock is not supported on page 52 512-GB and 256-GB Performance Acceleration modules not supported on page 52 IPv6 is not supported on page 55 SMB 2.0 is not supported on page 56
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.
42 | Data ONTAP 8.0 7-Mode Release Notes If you have configured any of the following features, do not upgrade to any releases of Data ONTAP 7-Mode release family:
FTPS is not supported on page 55 SFTP is not supported on page 55 Data Motion is not supported on page 25 TLS is not supported on page 53 If you need to boot the storage system from a Data ONTAP image stored on a remote server on page 53 IPsec is not supported on page 55 TOE is not supported on page 55 Compression for SnapMirror transfers not supported on page 52
The storage system will continue to function but without the services provided by these features. Features discontinued in the Data ONTAP 8.0 7-Mode release family Beginning in Data ONTAP 8.0 7-Mode, the following features are discontinued:
Systems including DS14 shelves, ESH modules or LRC modules on page 44 If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later on page 43 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 7-Mode Upgrade Guide.
Next topics
If you are upgrading to Data ONTAP 8.0 or later from Data ONTAP 7.x and you use quotas on page 43 Upgrade process changes with Data ONTAP 7-Mode software images on page 43 Systems including DS14 shelves, ESH modules or LRC modules on page 44 Upgrading FAS3140/FAS3170 systems on page 45 Do not remove the special system files that are for restoring LUNs in snapshot copies on page 45 New FlexVol volume space requirements when upgrading from a release earlier than Data ONTAP 7.3 on page 45 If your root FlexVol volume does not meet the new size requirements on page 47
If you are performing a nondisruptive upgrade on a system with VMware ESX Server hosts on page 47 If you are upgrading a system that includes FlexVol volumes on page 47 If you are upgrading a system that includes deduplicated volumes on page 48 If your system uses rtc or rdate as the protocol for time synchronization on page 48 If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7Mode on page 48 If you have been using the flex_cache license on page 49 If you are reverting to a Data ONTAP release with a lower maximum capacity on page 49 If you are reverting to a previous release and you use deduplication on page 50
If you are upgrading to Data ONTAP 8.0 or later from Data ONTAP 7.x and you use quotas
If you are upgrading to the Data ONTAP 8.0 release family from any Data ONTAP version in the 7.0, 7.1, 7.2, and 7.3 release families, after the upgrade is complete you must reinitialize quotas for every volume that has a default user quota or a default group quota. Failure to reinitialize quotas on the affected volumes could result in a system panic later. You reinitialize quotas by using the quota off and quota on commands for each affected volume. Default user and group quotas have an asterisk ("*") as the quota target, such as the following example: #Quota target type disk #----------- ------* user@/vol/vol1 50M files ----thold ----sdisk ----sfile -----
For more information about this issue, see bug 472552 in Bugs Online on the NOW site.
Upgrade process changes with Data ONTAP 7-Mode software images

When you upgrade to Data ONTAP 8.0 and later releases, you must obtain Data ONTAP software images from the NOW site and copy them to your storage system. Media kits, including CD-ROMs with Data ONTAP software 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, media kits including CD-ROMs are no longer available. You must obtain software 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, 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
44 | Data ONTAP 8.0 7-Mode Release Notes For the upgrade to Data ONTAP 8.0 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 .tgz images, for upgrades from any Data ONTAP 8.0 release to a later release
After you have upgraded to Data ONTAP 8.0 or later, you can only use .tgz images for further upgrades. After 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.
Systems including DS14 shelves, ESH modules or LRC modules

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 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.
Upgrading FAS3140/FAS3170 systems

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 and e0P interfaces.
About this task
In addition, if you revert from Data ONTAP version 8.0, the e0M and e0P interfaces remain disabled for iSCSI traffic by default as follows: Target portal group configuration related to e0M and e0P may change. e0M and e0P may be removed from the iSCSI access list configuration.
For additional technical details about this issue, see Bug ID 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.
Related information
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 exist in 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 in the root level of every volume, including the root volume:
.vtoc_internal .bplusvtoc_internal
New FlexVol volume space requirements when upgrading from a release earlier than Data ONTAP 7.3
Upgrading to Data ONTAP 8.0 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.
46 | Data ONTAP 8.0 7-Mode Release Notes For more information, see the Data ONTAP 8.0 7-Mode Upgrade Guide. Determining system capacity and space guarantees before upgrading to Data ONTAP 7.3 or later 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 Then... You can proceed with your upgrade to Data ONTAP 7.3; no further action is required.
97% or more for any aggregate 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. aggrSpaceCheck tool.
Not configured to send AutoSupport messages to NetApp
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 you finish
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 the Data ONTAP 8.0 release family. 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 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. 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 7Mode 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-Mode7.3.2 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 300 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 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 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 already 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 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:
Important cautions | 49 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 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. You can reduce the total capacity of your system by destroying aggregates or by moving aggregates to a different system. The system to which storage is relocated must meet the following requirements: It has spare capacity 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 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.
sis start -s command. This command rebuilds the deduplication metadata for all the data in the
To use deduplication for all the data within the volume, and thus obtain higher space savings, use the
volume. This process can take several days, depending on the size of the logical data in the volume. 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.
Attention: Before using the sis start -s command, ensure that the volume has sufficient free
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 7-Mode Block Access Management Guide for iSCSI and FC.
Next topics
Identical WWPNs can occur on both nodes in a cluster on page 50 If you deploy ALUA on storage systems with FCP or iSCSI on page 50 If you use Solaris 10 and the emlxs Fibre Channel Adapter driver on page 51 cfmode support change in Data ONTAP 8.0 on page 51
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. 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
Important cautions | 51 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.
cfmode support change in Data ONTAP 8.0

For Fibre Channel SAN configurations in Data ONTAP 8.0 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 or later. For detailed instructions about migrating to single_image mode, see Changing the Cluster cfmode Setting in Fibre Channel SAN Configuration on the NOW site.
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 7-Mode Data Protection Online Backup and Recovery Guide.
Next topics
NetApp SnapValidator for Oracle not supported on page 52 512-GB and 256-GB Performance Acceleration modules not supported on page 52 Upgrade issues if you have SnapLock on page 52
Compression for SnapMirror transfers not supported on page 52
NetApp SnapValidator for Oracle not supported

NetApp SnapValidator for Oracle is not supported in Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases. 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 7Mode. 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 halts 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 7Mode. For more information, see the Data ONTAP 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 7-Mode System Administration Guide.
Next topics
Issues in certificate MD5 signature collision vulnerability on page 53 If you need to boot the storage system from a Data ONTAP image stored on a remote server on page 53 TLS is not supported in the Data ONTAP 8.0 release family on page 53 RLM over IPv6 not supported in the Data ONTAP 8.0 release family on page 54
Issues in certificate MD5 signature collision vulnerability

In Data ONTAP 8.0, the storage system uses the MD5 message-digest algorithm to generate digital certificates. Due to the CVE-2004-2761-IETF X.509 certificate MD5 signature collision vulnerability, you should have the certificate signing requests (CSRs) further signed by a certificate authority (CA) using SHA256 or SHA1.
If you need to boot the storage system from a Data ONTAP image stored on a remote server
In the Data ONTAP 8.0 release family, 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 the Data ONTAP 8.0 release family

Transport Layer Security version 1.0 (TLSv1.0) was introduced in a previous Data ONTAP release, but it is not a supported function in the Data ONTAP 8.0 release family. If you enabled TLS in a previous Data ONTAP release family, it is no longer available when you run the Data ONTAP 8.0 release family. The system uses SSL instead of TLS for communication.
RLM over IPv6 not supported in the Data ONTAP 8.0 release family
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 the Data ONTAP 8.0 release family. If your RLM configuration does not include static IPv4 or DHCP IPv4 , you need to reconfigure the RLM by using the rlm setup command after upgrading to the Data ONTAP 8.0 release family. For information about the RLM, see the Data ONTAP 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 7-Mode Network Management Guide.
Next topics
IPv6 is not supported on page 55 IPsec is not supported on page 55 TOE is not supported on page 55
IPv6 is not supported

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

IPsec is not supported in Data ONTAP 8.0 and later. 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 release family.
TOE is not supported

In Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases, 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 7-Mode File Access and Protocols
Management Guide
Next topics
FTPS is not supported on page 55 SFTP is not supported on page 55 SMB 2.0 is not supported on page 56
FTPS is not supported

File Transfer Protocol over Secure Socket Layer (FTPS) was introduced in a previous Data ONTAP release, but it is not supported in the Data ONTAP 8.0 release family. If you enabled FTPS in a previous Data ONTAP release family, it is no longer available as an option for file access when you run the Data ONTAP 8.0 release family.
SFTP is not supported

Secure File Transfer Protocol (SFTP) was introduced in a previous Data ONTAP release, but it is not supported in the Data ONTAP 8.0 release family. If you enabled SFTP in a previous Data ONTAP release family, it is no longer available as an option for file access when you run the Data ONTAP 8.0 release family.
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.
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 either the Data ONTAP CLI or the RLM CLI, you must run the rlm update command with the -f option for a full image update. Further updates do not require the -f 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 7-Mode Upgrade Guide. For information about configuring the RLM, see the Data ONTAP 7-Mode System Administration Guide.
Known problems and limitations | 57
Known problems and limitations

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds to avoid these behaviors, have been identified after upgrading to 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 57 Network protocol issues on page 58 File access protocol issues on page 59 Block access protocol issues on page 60 Data protection issues on page 63 Storage resource management issues on page 66 Third-party storage issues (V-Series systems only) on page 70 HA pair issues on page 71
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 57 Issues regarding the EMS timed log on page 58
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 7-Mode Network Management Guide.
Next topics
Enable caching with NIS lookup on page 58 Entries in the NIS group file should not exceed 1024 characters on page 58
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 7-Mode File Access and Protocols Management Guide.
Next topics
Configuring user mapping for a default user quota with CIFS not enabled could severely degrade performance on page 59 Client notification messages in Windows domains require NetBIOS on page 59 Configuration issue for clients that mount NFS shares using a non-reserved port on page 60
Configuring user mapping for a default user quota with CIFS not enabled could severely degrade performance
If you configure user mapping for a default user quota on a storage system for which CIFS is not enabled, a later attempt to delete a qtree could result in significantly degraded performance. This could happen whether CIFS was never enabled on that storage system or CIFS was enabled but later disabled. You are at risk for this issue if your /etc/quotas file contains lines like these: QUOTA_PERFORM_USER_MAPPING ON ... * user@/vol/vol1 50G ... QUOTA_PERFORM_USER_MAPPING OFF In this case, you must remove or comment out these user mapping directives from your /etc/quotas file and reinitialize quotas before disabling CIFS. After you reenable CIFS, you can reinstate the user mapping directives and reinitialize quotas again. Temporarily disabling and then reenabling CIFS for a brief maintenance window is unlikely to cause this issue.
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 nonreserved 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 7-Mode Block Access Management Guide for iSCSI and FC.
Next topics
Brocade 200E switch speed must be set manually on page 60 Disks offline in Windows 2008 after a standard upgrade on page 61 iSCSI Target HBA support on page 61 If an iSCSI target HBA fails on page 62 If you use the automatic sizing feature on thinly provisioned LUNs when snap reserve is set to a non-zero value on page 62
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 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

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 and later releases, 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 LUNs to maintain their revision numbers. 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.
About this task
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).

Result
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 7-Mode Data Protection Online Backup and Recovery Guide and the Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide.
Next topics
If you establish a volume SnapMirror relationship between a source system with Data ONTAP 7.x and a destination system with Data ONTAP 8.0 on page 63 Limitations when using SnapVault with nondefault vFiler units on page 64 Restore engine does not honor any mandatory or advisory locks on files on page 65 Restore operation to a non-existent volume restores data to the root volume on page 65 Shutting down a storage system when SMTape operations are active might result in a panic on page 65 Suboptimal space savings with deduplication when 16 GB Performance Acceleration Module is installed on page 65 If you use DataFabric Manager to manage SnapMirror or SnapVault relationships between vFiler units on page 65 Creating more than 64 mirrored aggregates might impair disaster recovery on page 66
If you establish a volume SnapMirror relationship between a source system with Data ONTAP 7.x and a destination system with Data ONTAP 8.0
Using volume SnapMirror to replicate data between a source system with Data ONTAP 7.x and a destination system with Data ONTAP 8.0 might result in a service disruption on the destination system. To avoid this issue, deploy Data ONTAP 8.0P1 or later on the destination system before configuring a volume SnapMirror relationship. For detailed technical information on this issue, see bug 422655 in Bugs Online.
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) Default vFiler unit (vfiler0) Nondefault vFiler unit Yes No 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.)
Known problems and limitations | 65 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.
Shutting down a storage system when SMTape operations are active might result 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
66 | Data ONTAP 8.0 7-Mode Release Notes 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 autodiscovery 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
Creating more than 64 mirrored aggregates might impair disaster recovery

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

You should familiarize yourself with these storage resource management issues in this release.
Next topics
Configuring user mapping for a default user quota with CIFS not enabled could severely degrade performance on page 67 The -m option for the disk replace start command is not recognized on page 67 Attempting to assign more than 500 disks or array LUNs with a single disk assign command causes a system panic on page 67 Moving disks to a system running an earlier version of Data ONTAP could cause disk identification issues on page 67
Data ONTAP can silently select varying disk or array LUN sizes when creating an aggregate on page 68 Qtree quotas might prevent explicit quotas from overriding the default on page 69
Configuring user mapping for a default user quota with CIFS not enabled could severely degrade performance
If you configure user mapping for a default user quota on a storage system for which CIFS is not enabled, a later attempt to delete a qtree could result in significantly degraded performance. This could happen whether CIFS was never enabled on that storage system or CIFS was enabled but later disabled. You are at risk for this issue if your /etc/quotas file contains lines like these: QUOTA_PERFORM_USER_MAPPING ON ... * user@/vol/vol1 50G ... QUOTA_PERFORM_USER_MAPPING OFF In this case, you must remove or comment out these user mapping directives from your /etc/quotas file and reinitialize quotas before disabling CIFS. After you reenable CIFS, you can reinstate the user mapping directives and reinitialize quotas again. Temporarily disabling and then reenabling CIFS for a brief maintenance window is unlikely to cause this issue.
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.
assign
Attempting to assign more than 500 disks or array LUNs with a single disk 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.
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
68 | Data ONTAP 8.0 7-Mode Release Notes 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 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 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 68 Discovering what disks Data ONTAP will automatically select on page 69
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.
About this task
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.
About this task
Suppose you have the following /etc/quotas file:

#Quota target #----------* type ---user@/vol/vol1 disk files thold sdisk sfile ---- ----- ----- ----- ----16K

14717 /vol/vol1/mytree user@/vol/vol1 tree 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
Limitation on EMC CX storage array LUN numbering on page 70 Exceeding the maximum number of assigned devices results in a panic on page 70
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 LUN 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.
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
Known problems and limitations | 71 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.
HA pair issues
If you are using HA pairs, you might need to familiarize yourself with these issues. For more information about these issues, see the Data ONTAP 7-Mode High-Availability Configuration Guide.
Next topics
Incorrect warning of termination in spite of a successful giveback on page 71 The ifconfig command and the FAS2040 e0P port on page 71 If takeover is enabled for network interface failure, automatic giveback should be disabled on page 71
Incorrect warning of termination in spite of a successful giveback

On systems running Data ONTAP 8.0 7-Mode, the cf giveback command may, despite a successful giveback, produce an EMS warning that the giveback terminated because the partner node did not boot successfully. This message can be safely ignored. An example output of the warning is shown below:
Thu Jul 29 08:13:27 GMT [plat-3270-5a: sfo.sendhome.partnerNoBoot:warning]: The giveback terminated because the partner node (plat-3270-5b) did not boot successfully.
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 | 73
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 Block Access Management Guide for iSCSI and FC on page 73 Changes to the File Access and Protocols Management Guide on page 75 Changes to the MultiStore Management Guide on page 77 Changes to the Data ONTAP Upgrade Guide on page 79
Changes to the Block Access Management Guide for iSCSI and FC

New information has become available since the previous revision of the Data ONTAP Block Access Management Guide for iSCSI and FC.
Next topics
Setting volume options for the autodelete configuration on page 73 Correction to configure onboard adapters for target mode on page 74
Setting volume options for the autodelete configuration

The final step is missing in the procedure "Setting volume options for the autodelete configuration" topic of "Configuring volumes and LUNs when using autodelete" section. Perform the following steps for "Setting volume options for the autodelete configuration": 1. Set the space guarantee on the volumes by entering the following command:
vol options vol_name guarantee volume
2. Ensure that autosize is disabled by entering the following command:

vol autosize disable vol_name Note: This option is disabled by default.
3. Set fractional reserve to zero percent, if it is not already, by entering the following command:
vol options vol_name fractional_reserve 0
4. Set the Snapshot copy reserve to zero percent by entering the following command:

snap reserve vol_name 0
The Snapshot copy space and application data is now combined into one large storage pool. 5. Configure Snapshot copies to begin being automatically deleted when the volume reaches the capacity threshold percentage by entering the following command:
snap autodelete vol_name trigger volume Note: The capacity threshold percentage is based on the size of the volume. For more details, see the Data ONTAP 7-Mode Data Protection Online Backup and Recovery Guide.
6. Set the try_first option to snap_delete by entering the following command:

vol options vol_name try_first snap_delete
This enables Data ONTAP to begin deleting Snapshot copies, starting with the oldest first, to free up space for application data. 7. Activate the snap autodelete settings by entering the following command:
snap autodelete vol_name on
When finished, create your space-reserved LUNs.
Correction to configure onboard adapters for target mode

The section "Configuring onboard adapters for target mode" has some incorrect information about onboard adapters and target expansion cards. Changes to "About this task" The existing content is incorrect: If you are installing target expansion adapters, or if you exceed the allowed number of adapter ports, you must set the onboard adapters to unconfigured before installing the expansion adapters. The corrected content is: If you exceed the allowed number of adapter ports, you must set the onboard adapters to initiator or unconfigured before installing the expansion adapters. Changes to the first step in the topic "Configuring onboard adapters for target mode" The following existing content is incorrect: 1. If you have already connected the port to a switch or fabric, take it offline by entering the following command:
fcp config adapter down adapter is the port number. You can specify more than one port.
Example
fcp config 0c 0d down
Ports 0c and 0d are taken offline.

Note: If the adapter does not go offline, you can also remove the cable from the appropriate adapter port on the system.
The corrected content is as follows: 1. Verify that the FC ports are not already configured as target ports by entering the following command:
fcadmin config
Example
fcadmin config Local Adapter Type State Status --------------------------------------------------0a initiator CONFIGURED online 0b initiator CONFIGURED online 0c target CONFIGURED online 0d target CONFIGURED online The preceding output displays two ports for host access. ----------------------------------------------------
Changes to the File Access and Protocols Management Guide

The Data ONTAP 7-Mode File Access and Protocols Management Guide should have included the following topics.
Next topics
Correction for disabling virus scanning on page 75 SMB 2.0 Support on page 76 Unsupported Windows features in the file serving environment on page 76 NFSv4 client compatibility on page 76 The file fingerprint command can be used for all data files in Data ONTAP 8.0 and later on page 77
Correction for disabling virus scanning

The section about enabling or disabling virus scanning lists the incorrect option for disabling virus scanning of read-only files that a client opens. The correct option is -novscanread and the full CLI command to disable virus scanning of read-only files is as follows:

cifs shares -change sharename -novscanread
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 76 The FTP server does not support Unicode characters on page 77
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 and later
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.
Changes to the MultiStore Management Guide

There are some changes to the existing content of the Data ONTAP MultiStore Management Guide.
Next topics
Corrections to the List of RSH and SSH commands on page 77 Corrections to the SnapVault support on vFiler units on page 78
Corrections to the List of RSH and SSH commands

"List of RSH and SSH commands" topic lists some commands that are not supported in Data ONTAP 8.0 and later releases. The following commands, which are listed in the Data ONTAP 8.0 7-Mode MultiStore Management Guide, are not supported in Data ONTAP 8.0 and later releases:
cifs config df dns echo fpolicy snap snapmirror snapvault vol vscan wcc
nbtstat nfs nis route sectrace
ypcat ypgroup ypmatch ypwhich
Corrections to the SnapVault support on vFiler units

The sections "Where to enter SnapVault commands" and "Features and limitations of the snapvault command" have some incorrect information about interoperability between SnapVault and MultiStore. Where to enter SnapVault commands The following existing content is incorrect: Commands entered on a nondefault vFiler unit makes changes on or displays information only about that specific vFiler unit. This content is corrected as follows: Some commands entered on a nondefault vFiler unit make changes on or display information only about that specific vFiler unit--for example, snapvault status and snapvault snap sched. Features and limitations of the snapvault command The following existing content is incorrect: The features of the snapvault command when used in a MultiStore context are as follows: Additional SnapVault licenses are not required. vFiler units use the same source and destination licenses as the physical storage systems. The SnapVault feature can be turned on and off independently on each vFiler unit. The snapvault.access and snapvault.enable options can be changed independently on each vFiler unit. Each vFiler unit has its own snapvault.conf file in the /etc directory. SnapVault relationships established between vFiler units are maintained across vFiler unit migration.
This content is corrected as follows: The features of the snapvault command when used in a MultiStore context are as follows: Additional SnapVault licenses are not required. vFiler units use the same source and destination licenses as the physical storage systems. The snapvault.access and snapvault.enable options can be changed independently on each vFiler unit.
Changes to the Data ONTAP Upgrade Guide

New information about upgrade procedures has become available since the previous revision of the Upgrade Guide.
Additional requirement for AT-FCX disk shelf firmware updates

The topic "Service availability during disk shelf firmware updates" currently lists two requirements for updating AT-FCX disk shelf firmware nondisruptively: minimum firmware version and MultiPath Storage configuration. There is an additional requirement that Data ONTAP 7.3.2 or later be running. The first row of the table should read as follows: Module AT-FCX Disk shelf model DS14mk2 AT System downtime required? With Multipath Storage, firmware version 37, and Data ONTAP 7.3.2 or later: No Without Multipath Storage: Yes
After the table, the AT-FCX information should also be updated to state that you cannot perform a Data ONTAP NDU under the following circumstances: AT-FCX disk shelves are attached to your system and one or more of the following is true: You have not verified that the latest AT-FCX firmware version is running. A Data ONTAP release earlier than 7.3.2 is running. AT-FCX version 36 or earlier is running. MultiPath Storage is not configured.
Where to find product documentation and other information | 81
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
Searching online information on page 81 Finding documentation on NOW on page 82

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
Searching online information

The NOW site includes a natural language search tool. The NOW Natural Language PowerSearch tool on the Support page on the NOW site allows you to search the following sources of information: Troubleshooting, including Bug Tools and Knowledgebase Documentation, including Product Documentation, Guides and Best Practices, and Support Communications Getting Started, including Navigating the New Support Site and Enabling AutoSupport Tech Assistance, including Requesting a Part (RMA) and Opening a Case Downloads including Software, Utility ToolChest, and Product Evaluations
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: Documentation > Access Product Documentation > Data ONTAP 7-Mode > Data ONTAP 8.0 7-Mode and later: Filer and V-Series systems For more information, see the NOW site at now.netapp.com/.

Ontap Release Note

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ontap Release Note

Uploaded by

Copyright:

Available Formats

Data ONTAP 8.

0 7-Mode Release Notes

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

Important cautions ..................................................................................... 41

Known problems and limitations .............................................................. 57

Changes to published documentation ....................................................... 73

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

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

System Configuration Guide

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

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

Ability to decrease maxfiles

Networking and security protocols enhancements

64-bit SNMP object identifiers (OIDs) are supported

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

22 | Data ONTAP 8.0 7-Mode Release Notes

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

24 | Data ONTAP 8.0 7-Mode Release Notes

If volumes with deduplication exceed the maximum supported size

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

High-availability pair (formerly active/active configuration) enhancements

pair has replaced active/active configuration.

HA pair terminology changes

Changes to MultiStore support

26 | Data ONTAP 8.0 7-Mode Release Notes

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 release family

Purpose Configures the ACP subsystem.

Release Introduced 8.0

28 | Data ONTAP 8.0 7-Mode Release Notes

Release Introduced 8.0

Backs up blocks of data to tape.

Backup and Recovery Guide na_smtape manpage

storage array modify