+ All Categories
Home > Documents > OnTap8.01 RC3 7Mode Release Notes

OnTap8.01 RC3 7Mode Release Notes

Date post: 10-Oct-2014
Category:
Upload: darjin
View: 227 times
Download: 4 times
Share this document with a friend
97
Data ONTAP® 8.0.1 7-Mode RC3 Release Notes NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 USA Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 4-NETAPP Documentation comments: [email protected] Information Web: http://www.netapp.com Part number: 215-05507_A0 2 December 2010
Transcript

Data ONTAP® 8.0.1 7-Mode RC3Release Notes

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPPDocumentation comments: [email protected] Web: http://www.netapp.com

Part number: 215-05507_A0

2 December 2010

Contents

Copyright information ............................................................................... 11Trademark information ............................................................................. 13Data ONTAP 8.0.1 7-Mode RC3 Release Notes ...................................... 15Changes introduced since Data ONTAP 8.0 ............................................ 17

Changes in the 8.0.1 7-Mode RC3 release ................................................................ 17

Changes in the 8.0.1 7-Mode RC2 release ................................................................ 19

Changes in the 8.0.1 7-Mode RC1 release ................................................................ 21

New and changed features in the Data ONTAP 8.0 7-Mode releasefamily ...................................................................................................... 25

New platform and hardware support ......................................................................... 26

Support for 32xx platform ............................................................................. 26

Support for 62xx platform ............................................................................. 27

Support for 512-GB and 256-GB Performance Acceleration Module

(PAM II) .................................................................................................. 27

Support for SSDs ........................................................................................... 28

Supported tape drives .................................................................................... 28

Support for 2 TB SATA disks ....................................................................... 28

Support for SA320 platform .......................................................................... 28

Changes in disk shelf support .................................................................................... 29

Support for DS2246 disk shelves .................................................................. 29

Support for DS4243 disk shelf ...................................................................... 29

Manageability enhancements .................................................................................... 30

Support for a 64-bit root volume ................................................................... 30

The Service Processor for the 32xx and the 62xx systems ........................... 30

Enhancements that allow you to specify SSL versions ................................. 31

SSL security improvements .......................................................................... 31

The default security settings .......................................................................... 31

Setup for root account password ................................................................... 32

The diagnostic account and the systemshell ................................................. 33

Boot menu enhancements and changes ......................................................... 33

Read reallocation of data ............................................................................... 33

Extents for FlexVol volumes ......................................................................... 33

Table of Contents | 3

Partner recipients for AutoSupport email notifications ................................. 34

AutoSupport message file attachments ......................................................... 34

New disk drive AutoSupport message sent weekly ...................................... 34

Storage resource management enhancements ........................................................... 34

Support for 64-bit aggregates ........................................................................ 35

File space utilization report ........................................................................... 35

Upgrading to Data ONTAP 8.0.1 increases volume capacity after

deduplication ........................................................................................... 35

Maximum simultaneous FlexClone file or FlexClone LUN operations

per storage system ................................................................................... 35

FlexClone files and FlexClone LUNs support on MultiStore ....................... 36

Increased maximum RAID group size for SATA disks ................................ 36

Networking and security protocols enhancements .................................................... 36

Support for the SMB 2.0 protocol ................................................................. 36

TSO in NICs .................................................................................................. 36

Support for CDP ............................................................................................ 37

Port-based load-balancing option for multimode interface groups ............... 37

64-bit SNMP object identifiers (OIDs) are supported .................................. 37

Configuration for receiving untagged traffic on VLAN tagged interfaces ... 37

Vifs are now known as interface groups ....................................................... 38

File access protocol enhancements ........................................................................... 38

Maximum number of auxiliary UNIX groups supported for a user .............. 38

Support for multiple open instances of the SMB named pipe on an

FPolicy server .......................................................................................... 38

Block protocol enhancements ................................................................................... 39

10-GbE Unified Target Adapter protocol support ........................................ 39

iSCSI RADIUS support ................................................................................ 39

Support for NetApp DataMotion for Volumes ............................................. 40

VMware VAAI features for ESX hosts support ............................................ 40

igroup scalability limits ................................................................................. 40

Data protection enhancements .................................................................................. 40

Support for 840 disk drives on fabric-attached MetroClusters ..................... 41

Support for out-of-order frame delivery for SnapMirror over Fibre

Channel .................................................................................................... 41

Support for SnapMirror relationship between two FlexClone volumes ....... 41

Support for SnapMirror network compression .............................................. 42

4 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Support for designated range of ports for NDMP data connections ............. 42

If volumes with deduplication exceed the maximum supported size ............ 42

NearStore license is not required for deduplication ...................................... 42

Maximum concurrent deduplication operations supported ........................... 42

Prerequisite for backing up data to tape using NDMP services .................... 42

Snapshot copy schedules ............................................................................... 43

SnapMirror support for 64-bit volumes ........................................................ 43

SnapVault support for 64-bit volumes .......................................................... 43

High availability pair (formerly active/active configuration) enhancements ............ 43

HA pair terminology changes ....................................................................... 44

Changes to MultiStore support .................................................................................. 44

Data Motion is not supported in the Data ONTAP 8.0 7-Mode release

family ....................................................................................................... 44

Changes to the Data ONTAP and V-Series libraries ................................................ 44

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family ............................................................................... 45

New commands in Data ONTAP 8.0 7-Mode release family ................................... 45

Changed commands in Data ONTAP 8.0 7-Mode release family ............................ 48

Replaced or removed commands in Data ONTAP 8.0 7-Mode release family ........ 51

New options in Data ONTAP 8.0 7-Mode release family ........................................ 52

Changed options in Data ONTAP 8.0 7-Mode release family .................................. 53

Requirements for running Data ONTAP 8.0.1 7-Mode .......................... 55Supported systems ..................................................................................................... 55

Unsupported systems ................................................................................................. 56

Storage system firmware ........................................................................................... 56

Storage systems that support Multipath Storage ....................................................... 57

V-Series requirements and support information ....................................................... 58

Requirements for V-Series fabric-attached MetroCluster configurations ..... 58

Important cautions ..................................................................................... 59Unsupported features ................................................................................................. 59

Upgrade and revert cautions ...................................................................................... 60

Change in nondisruptive upgrade procedure ................................................. 61

If you use upgrade images to upgrade to Data ONTAP 8.0.1 7-Mode or

later .......................................................................................................... 61

If you are updating a system with AT-FCX disk shelves attached ............... 62

If you are upgrading a FAS3050 system ....................................................... 62

Table of Contents | 5

Systems including DS14 shelves, ESH modules, or LRC modules .............. 63

Upgrading FAS3140/FAS3170 systems ....................................................... 64

Do not remove the special system files that are for restoring LUNs in

snapshot copies ........................................................................................ 64

If you are upgrading to Data ONTAP 8.0.1 7-Mode or later from a

release earlier than Data ONTAP 7.3 ...................................................... 64

If your root FlexVol volume does not meet the new size requirements ....... 66

If you are performing a nondisruptive upgrade on a system with

VMware ESX Server hosts ...................................................................... 66

If you are upgrading a system that includes deduplicated volumes .............. 66

If your system uses rtc or rdate as the protocol for time synchronization ... . 66

If you modify the timed options and then revert to a release prior to Data

ONTAP 8.0 7-Mode ................................................................................ 67

If you have been using the flex_cache license .............................................. 67

If you are reverting to a Data ONTAP release with a lower maximum

capacity .................................................................................................... 67

If you are reverting to a previous release and you use deduplication ........... 68

Block access protocol cautions ................................................................................. 68

Identical WWPNs can occur on both nodes in a cluster ............................... 69

If you deploy ALUA on storage systems with FCP or iSCSI ....................... 69

If you use Solaris 10 and the emlxs Fibre Channel Adapter driver .............. 69

cfmode support change in Data ONTAP 8.0 ................................................. 69

Data protection cautions ............................................................................................ 70

NetApp SnapValidator for Oracle not supported .......................................... 70

SnapLock is not supported ............................................................................ 70

Manageability cautions ............................................................................................. 71

If you need to boot the storage system from a Data ONTAP image

stored on a remote server ......................................................................... 71

TLS is not supported in the Data ONTAP 8.0 release family ....................... 71

RLM over IPv6 not supported in the Data ONTAP 8.0 release family ........ 71

New RLM firmware and its upgrade requirements ....................................... 72

Network protocol cautions ........................................................................................ 72

IPv6 is not supported ..................................................................................... 73

IPsec is not supported .................................................................................... 73

TOE is not supported ..................................................................................... 73

Known problems and limitations .............................................................. 75

6 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Manageability issues ................................................................................................. 75

RLM configuration is not saved if the RLM's Ethernet cable is not

connected ................................................................................................. 75

Issues regarding the EMS timed log ............................................................. 76

Shutdown delay in FAS2040 systems when critical thresholds are

crossed ..................................................................................................... 76

Network protocol issues ............................................................................................ 76

Enable caching with NIS lookup ................................................................... 76

Entries in the NIS group file should not exceed 1024 characters ................. 76

File access protocol issues ......................................................................................... 77

Client notification messages in Windows domains require NetBIOS .......... 77

Configuration issue for clients that mount NFS shares using a non-

reserved port ............................................................................................ 77

CIFS termination required before issuing a lock break ................................. 78

Mac clients cannot access CIFS shares using widelinks ............................... 78

Block access protocol issues ..................................................................................... 78

Brocade 200E switch speed must be set manually ........................................ 78

Disks offline in Windows 2008 after a standard upgrade ............................. 79

iSCSI Target HBA support ........................................................................... 79

If an iSCSI target HBA fails ......................................................................... 79

If you use the automatic sizing feature on thinly provisioned LUNs

when snap reserve is set to a non-zero value ........................................... 80

Data protection issues ................................................................................................ 81

Tape backup and volume move operations must not be performed

simultaneously ......................................................................................... 81

SMTape restore to an offline volume overwrites the data on that volume . . . 81

Deleted files occupy additional space on SMTape restored volumes ........... 82

Limitations when using SnapVault with nondefault vFiler units .................. 82

Restore engine does not honor any mandatory or advisory locks on files .... 83

Restore operation to a non-existent volume restores data to the root

volume ..................................................................................................... 83

Shutting down a storage system when SMTape operations are active

might result in a panic ............................................................................. 83

Suboptimal space savings with deduplication when 16 GB Performance

Acceleration Module is installed ............................................................. 83

Table of Contents | 7

If you use DataFabric Manager to manage SnapMirror or SnapVault

relationships between vFiler units ........................................................... 84

Creating more than 64 mirrored aggregates might impair disaster

recovery ................................................................................................... 84

Storage resource management issues ........................................................................ 85

Attempting to assign more than 500 disks or array LUNs with a single

disk assign command causes a system panic ........................................... 85

Moving disks to a system running an earlier version of Data ONTAP

could cause disk identification issues ...................................................... 85

Data ONTAP can silently select varying disk or array LUN sizes when

creating an aggregate ............................................................................... 86

SSD Spare blocks consumed limit reported as "N/A" .................................. 87

Forcing a FlexVol volume online must be done in diag mode ..................... 87

Third-party storage issues (V-Series systems only) .................................................. 87

Limitation on EMC CX storage array LUN numbering ............................... 87

Exceeding the maximum number of assigned devices results in a panic ...... 88

HA pair issues ........................................................................................................... 88

Do not disable the IP fastpath option on a 32xx system in an HA pair ........ 88

Incorrect warning of termination in spite of a successful giveback .............. 89

The ifconfig command and the FAS2040 e0P port ....................................... 89

If takeover is enabled for network interface failure, automatic giveback

should be disabled ................................................................................... 89

Changes to published documentation ....................................................... 91Changes to the Data Protection Tape Backup and Recovery Guide ......................... 91

Designating range of ports for NDMP data connections .............................. 91

Changes to the Storage Management Guide ............................................................. 92

Incorrect root FlexVol volume size requirement for 3160 systems .............. 92

Changes to the File Access and Protocols Management Guide ................................ 92

Unsupported Windows features in the file serving environment .................. 93

NFSv4 client compatibility ........................................................................... 93

The file fingerprint command can be used for all data files in Data

ONTAP 8.0.1 7-Mode ............................................................................. 93

Changes to the Block Access Management Guide for iSCSI and FC ....................... 94

Setting volume options for the autodelete configuration .............................. 94

Where to find product documentation and other information .............. 95Searching online information .................................................................................... 95

8 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Finding documentation on NOW .............................................................................. 95

Table of Contents | 9

Copyright information

Copyright © 1994–2010 NetApp, Inc. All rights reserved. Printed in the U.S.A.

No part of this document covered by copyright may be reproduced in any form or by any means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in anelectronic retrieval system—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED 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 notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

The product described in this manual may be protected by one or more U.S.A. patents, foreignpatents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Copyright information | 11

Trademark information

NetApp; the NetApp logo; the Network Appliance logo; Bycast; Cryptainer; Cryptoshred;DataFabric; Data ONTAP; Decru; Decru DataFort; FAServer; FilerView; FlexCache; FlexClone;FlexShare; FlexVol; FPolicy; gFiler; Go further, faster; Manage ONTAP; MultiStore; NearStore;NetCache; NOW (NetApp on the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; SimulateONTAP; SnapCopy; SnapDrive; SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore;SnapValidator; SnapVault; Spinnaker Networks; Spinnaker Networks logo; SpinAccess;SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove; SpinServer; SpinStor; StorageGRID;StoreVault; SyncMirror; Topio; vFiler; VFM; and WAFL are registered trademarks of NetApp, Inc.in the U.S.A. and/or other countries. Network Appliance, Snapshot, and The evolution of storage aretrademarks of NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in someother countries. The StoreVault logo, ApplianceWatch, ApplianceWatch PRO, ASUP, AutoSupport,ComplianceClock, DataFort, Data Motion, FlexScale, FlexSuite, Lifetime Key Management,LockVault, NOW, MetroCluster, OpenKey, ReplicatorX, SecureAdmin, Shadow Tape,SnapDirector, SnapFilter, SnapMigrator, SnapSuite, Tech OnTap, Virtual File Manager, VPolicy,and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries. Get Successful andSelect are service marks of NetApp, Inc. in the U.S.A.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother 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/orother countries. Microsoft is a registered trademark and Windows Media is a trademark of MicrosoftCorporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, andSureStream 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 andshould be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Trademark information | 13

Data ONTAP 8.0.1 7-Mode RC3 Release Notes

These Release Notes describe new features, enhancements, and known issues for Data ONTAP 8.0.17-Mode RC3, as well as additional information related to running this release on specific storagesystems.

About the Data ONTAP 8.0.1 7-Mode RC3 release

Data ONTAP 8.0.1 7-Mode RC3 is the third maintenance release in the Data ONTAP 8.0. 7-Moderelease family. For more information about Data ONTAP releases, see the "Data ONTAP ReleaseModel" on the NOW site.

The Data ONTAP 8.0.1 7-Mode RC3 release includes support for the 32xx and 62xx platforms, theService Processor for the 32xx and 62xx systems, and support for the SA320 platform.

Attention:

If you are upgrading to Data ONTAP 8.0.1 7-Mode RC3 or a later Data ONTAP 8.0.x 7-Moderelease or reverting from this release to an earlier release, see the Data ONTAP 7-Mode UpgradeGuide.

Data ONTAP 8.0.1 7-Mode RC3 and later Data ONTAP 8.0.x 7-Mode releases support all of thefeatures in earlier versions of Data ONTAP 7.x releases with some exceptions, including thefollowing:

• NetApp SnapValidator for Oracle• SnapLock• IPv6

Do not upgrade your storage system to Data ONTAP 8.0.1 7-Mode RC3 or a later Data ONTAP8.0.x 7-Mode release if you have configured any of these features.

For more information, see Unsupported features on page 59.

About the Data ONTAP 8.0.1 7-Mode RC2 release

Data ONTAP 8.0.1 7-Mode RC2 is the second maintenance release in the Data ONTAP 8.0. 7-Moderelease family. For more information about Data ONTAP releases, see the "Data ONTAP ReleaseModel" on the NOW site.

Attention:

If you are upgrading to Data ONTAP 8.0.1 7-Mode RC2 or a later Data ONTAP 8.0.x 7-Moderelease or reverting from this release to an earlier release, see the Data ONTAP 7-Mode UpgradeGuide.

Data ONTAP 8.0.1 7-Mode RC3 Release Notes | 15

Data ONTAP 8.0.1 7-Mode RC2 and later Data ONTAP 8.0.x 7-Mode releases support all of thefeatures in earlier versions of Data ONTAP 7.x releases with some exceptions, including thefollowing:

• NetApp SnapValidator for Oracle• SnapLock• IPv6

Do not upgrade your storage system to Data ONTAP 8.0.1 7-Mode RC2 or a later Data ONTAP8.0.x 7-Mode release if you have configured any of these features.

For more information, see Unsupported features on page 59

About the Data ONTAP 8.0.1 7-Mode RC1 release

Data ONTAP 8.0.1 7-Mode RC1 is the first maintenance release in the Data ONTAP 8.0. 7-Moderelease family. For more information about Data ONTAP releases, see the "Data ONTAP ReleaseModel" on the NOW site.

The Data ONTAP 8.0.1 7-Mode RC1 release includes support for the new disk shelves DS2246 -supporting 2.5" SAS disk drives, support for solid-state disk (SSD) drives, and 256-GB /512-GBPCIe-attached Performance Acceleration Module (PAM II also known as Flash Cache module).

The Data ONTAP 8.0.1 7-Mode RC1 release also includes storage efficiency improvements such asincreased dedupe volume limits, data compression over the network for SnapMirror transfers, andsupport for 64-bit aggregates with data protection technologies SnapVault and SnapMirror.

Additional enhancements include, networking and security protocol enhancements, Data Motion forVolumes within LUNs and manageability enhancements including support for certain VMwarevStorage APIs for Array Integration (VAAI) features.

For a complete description of these and other new features, see New and changed features in the DataONTAP 8.0 7-Mode release family on page 25.

About these release notes

All the information in this document applies to the Data ONTAP 8.0.1 7-Mode RC1,RC2, and RC3releases and later Data ONTAP 8.0.x 7-Mode releases for NetApp storage systems (FAS systems,NearStore systems, and V-Series systems), unless noted. FAS systems and NearStore systems aresometimes called filers or appliances. Some of the information in this document applies to SAsystems.

These release notes are available in .html and .pdf formats. They are optimized for .html viewing andlinking.

Related information

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

16 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Changes introduced since Data ONTAP 8.0

If you are already familiar with an earlier release in the Data ONTAP 8.0 release family and youwant to see what is new since that release, you can see exactly which changes have been introducedwith each release in the Data ONTAP 8.0 family. To pinpoint what has changed since the release inthe Data ONTAP 8.0 family that you are familiar with, look at the changes that were introduced afterthat release.

Note:

• If you are new to the Data ONTAP 8.0 family, it is not necessary to read this section.Go directly to New and changed features in the Data ONTAP 8.0. 7-Mode releasefamily on page 25.

• All Data ONTAP releases include bug fixes.For more information, including comparisons of bugs fixed in different releases, see BugsOnline on the NOW site.

Next topics

Changes in the 8.0.1 7-Mode RC3 release on page 17

Changes in the 8.0.1 7-Mode RC2 release on page 19

Changes in the 8.0.1 7-Mode RC1 release on page 21

Related information

http://now.netapp.com/NOW/cgi-bin/bol/http://now.netapp.com/NOW/products/ontap_releasemodel/post70.shtml

Changes in the 8.0.1 7-Mode RC3 releaseData ONTAP 8.0.1 7-Mode RC3 includes support for the 32xx, 62xx, and SA320 platforms and theService Processor for the 32xx and 62xx systems. This release also includes improvements and bugfixes.

New and changed features in Data ONTAP 8.0.1 7-Mode RC3

The Data ONTAP 8.0.1 7-Mode RC3 includes the following new and changed features.

• Support for 32xx platform on page 26• Support for 62xx platform on page 27• Support for SA320 platform on page 28• The Service Processor for the 32xx and 62xx systems on page 30• Support for 840 disk drives on fabric-attached MetroClusters on page 41

Changes introduced since Data ONTAP 8.0 | 17

For information on all new and changed features in the Data ONTAP 8.0 7-mode release family, see New and changed features in the Data ONTAP 8.0. 7-Mode release family on page 25.

New commands in Data ONTAP 8.0.1 7-Mode RC3

No new commands were introduced in Data ONTAP 8.0.1 7-Mode RC3.

For information on all new commands in the Data ONTAP 8.0 7-mode release family, see Newcommands in Data ONTAP 8.0 7-Mode release family on page 45.

Changed commands in Data ONTAP 8.0.1 7-Mode RC3

No commands were changed in Data ONTAP 8.0.1 7-Mode RC3.

For information on all changed commands in the Data ONTAP 8.0 7-Mode release family, see Changed commands in Data ONTAP 8.0 7-Mode release family on page 48.

Commands removed in Data ONTAP 8.0.1 7-Mode RC3

No commands were removed in Data ONTAP 8.0.1 7-Mode RC3.

For information on the commands removed or replaced in the Data ONTAP 8.0 7-Mode releasefamily, see Replaced or removed commands in Data ONTAP 8.0 7-Mode releasefamily on page 51.

New options in Data ONTAP 8.0.1 7-Mode RC3

There were no new options introduced in Data ONTAP 8.0.1 7-Mode RC3.

For information on all new options in the Data ONTAP 8.0 7-Mode release family, see New optionsin Data ONTAP 8.0 7-Mode release family on page 52.

Changed options in Data ONTAP 8.0.1 7-Mode RC3

No options were changed in Data ONTAP 8.0.1 7-Mode RC3.

For information on all changed options in the Data ONTAP 8.0 7-Mode release family, see Changedoptions in Data ONTAP 8.0 7-Mode release family on page 53.

New cautions in Data ONTAP 8.0.1 7-Mode RC3

No new cautions were introduced in Data ONTAP 8.0.1 7-Mode RC3.

For information on all important cautions in the Data ONTAP 8.0 release family, see Importantcautions on page 59.

Cautions removed in Data ONTAP 8.0.1 7-Mode RC3

No cautions were removed from Data ONTAP 8.0.1 7-Mode RC3.

18 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Cautions changed in Data ONTAP 8.0.1 7-Mode RC3

The following caution changed in Data ONTAP 8.0.1 7-Mode RC3.

• SnapLock is not supported on page 70

For information on all changed cautions in the Data ONTAP 8.0 release family, see Importantcautions on page 59.

New known limitations in Data ONTAP 8.0.1 7-Mode RC3

The following new limitations were introduced in Data ONTAP 8.0.1 7-Mode RC3.

• Widelinks do not work from Mac clients on page 78• Forcing a FlexVol volume online must be done in diag mode on page 87

For information on all known limitations in the Data ONTAP 8.0 release family, see Knownproblems and limitations on page 75.

Limitations removed in Data ONTAP 8.0.1 7-Mode RC3

No limitations were removed from Data ONTAP 8.0.1 7-Mode RC3.

Documentation changes for Data ONTAP 8.0.1 7-Mode RC3

There were no documentation changes for Data ONTAP 8.0.1 7-Mode RC3 release.

For more information about important documentation changes, see Changes to publisheddocumentation on page 91.

Changes in the 8.0.1 7-Mode RC2 releaseData ONTAP incudes improvements and bux fixes.

New and changed features in Data ONTAP 8.0.1 7-Mode RC2

The Data ONTAP 8.0.1 7-Mode RC2 does not include any new and changed features.

For information on all new and changed features in the Data ONTAP 7-Mode 8.0 release family, see New and changed features in the Data ONTAP 8.0. 7-Mode release family on page 25.

New commands in Data ONTAP 8.0.1 7-Mode RC2

The following command was introduced in Data ONTAP 8.0.1 7-Mode RC2.

• du

For information on all new commands in the Data ONTAP 8.0 7-Mode release family, see Newcommands in Data ONTAP 8.0 7-mode release family on page 45.

Changes introduced since Data ONTAP 8.0 | 19

Changed commands in Data ONTAP 8.0.1 7-Mode RC2

No commands were changed in Data ONTAP 8.0.1 7-Mode RC2.

For information on all changed commands in the Data ONTAP 8.0 release family, see Changedcommands in Data ONTAP 8.0 7-Mode release family on page 48.

Commands removed in Data ONTAP 8.0.1 7-Mode RC2

No commands were removed in Data ONTAP 8.0.1 7-Mode RC2.

For information on the commands removed or replaced in the Data ONTAP 8.0 7-Mode releasefamily, see Replaced or removed commands in Data ONTAP 8.0 7-Mode releasefamily on page 51.

New options in Data ONTAP 8.0.1 7-Mode RC2

There were no new options introduced in Data ONTAP 8.0.1 7-Mode RC2.

For information on all new options in the Data ONTAP 8.0 7-Mode release family, see New optionsin Data ONTAP 8.0 7-Mode release family on page 52.

Changed options in Data ONTAP 8.0.1 7-Mode RC2

No options were changed in Data ONTAP 8.0.1 7-Mode RC2.

For information on all changed options in the Data ONTAP 8.0 7-Mode release family, see Changedoptions in Data ONTAP 8.0 7-Mode release family on page 53.

New cautions in Data ONTAP 8.0.1 7-Mode RC2

The following new caution was introduced in Data ONTAP 8.0.1 7-Mode RC2:

• If you are upgrading a FAS3050 system on page 62

For information on all important cautions in the Data ONTAP 8.0 7-Mode release family, see Important cautions on page 59.

Cautions removed in Data ONTAP 8.0.1 7-Mode RC2

No cautions were removed from Data ONTAP 8.0.1 7-Mode RC2.

Cautions changed in Data ONTAP 8.0.1 7-Mode RC2

No cautions changed in Data ONTAP 8.0.1 7-Mode RC2.

For information on all changed cautions in the Data ONTAP 8.0 7-Mode release family, see Important cautions on page 59.

20 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

New known limitations in Data ONTAP 8.0.1 7-Mode RC2

There were no new limitations introduced in Data ONTAP 8.0.1 7-Mode RC2.

For information on all known limitations in the Data ONTAP 8.0 7-Mode release family, see Knownproblems and limitations on page 75.

Limitations removed in Data ONTAP 8.0.1 7-Mode RC2

No limitations were removed from Data ONTAP 8.0.1 7-Mode RC2.

Documentation changes for Data ONTAP 8.0.1 7-Mode RC2

There were no documentation changes for Data ONTAP 8.0.1 7-Mode RC2 release.

For more information about important documentation changes, see Changes to publisheddocumentation on page 91.

Changes in the 8.0.1 7-Mode RC1 releaseData ONTAP 8.0.1 7-Mode RC1 includes PAM II support (also known as Flash Cache module), 64-bit root aggregates, SSD support, and 16 TB volume size for dedupe across all platforms. Thisrelease also includes increased maximum RAID group size for SATA disks. Additionally, DataONTAP 8.0.1 7-Mode RC1 includes bug fixes, such as features related to the ability to use Telnet orRemote Shell (RSH) sessions to update RLM firmware.

New and changed features in Data ONTAP 8.0.1 7-Mode RC1

The Data ONTAP 8.0.1 7-Mode RC1 release introduces the following new and changed features:

• Support for 512-GB and 256-GB Performance Acceleration Modules on page 27• Increased maximum RAID group size for SATA disks on page 36• Support for SSDs on page 28• Supported tape drives on page 28• Support for DS2246 disk shelves on page 29• Support for a 64-bit root volume on page 30• The Service Processor for the 32xx systems on page 30• Enhancements that allow you to specify SSL versions on page 31• File space utilization report on page 35• Upgrading to Data ONTAP 8.0.1 increases volume capacity after deduplication on page 35• FlexClone files and FlexClone LUNs support on MultiStore on page 36• Support for the SMB 2.0 protocol on page 36• TSO in NICs on page 36• Support for CDP on page 37• Port-based load-balancing option for multimode vifs on page 37

Changes introduced since Data ONTAP 8.0 | 21

• 10-GbE Unified Target Adapter protocol support on page 39• Support for nondisruptive volume move on page 40• VMware VAAI features for ESX hosts support on page 40• igroup scalability limits on page 40• Support for out-of-order frame delivery for SnapMirror over Fibre Channel on page 41• Support for SnapMirror relationship between two FlexClone volumes on page 41• Support for SnapMirror network compression on page 42• Designating range of ports for NDMP data connections on page 91

For more information, see New and changed features in the Data ONTAP 8.0. 7-Mode releasefamily on page 25.

New commands in Data ONTAP 8.0.1 7-Mode RC1

Data ONTAP 8.0.1 7-Mode RC1 introduces the following new command:

• cdpd

For more information, see New commands in Data ONTAP 8.0 7-Mode release family on page 45.

Changed commands in Data ONTAP 8.0.1 7-Mode RC1

The following commands have been changed in Data ONTAP 8.0.1 7-Mode RC1:

• ifgrp create multi

• software update

• storage show acp

• storage show fault

For more information see Changed commands in Data ONTAP 8.0 7-Mode releasefamily on page 48.

Commands removed in Data ONTAP 8.0.1 7-Mode RC1

No commands were removed in Data ONTAP 8.0.1 7-Mode RC1:

For more information, see Replaced or removed commands in Data ONTAP 8.0 7-Mode releasefamily on page 51.

New options in Data ONTAP 8.0.1 7-Mode RC1

Data ONTAP 8.0.1 7-Mode RC1 includes the following options:

• autosupport.periodic.tx_window time

• ndmpd.data_port_range

• nfs.v3.snapshot.active.fsid.enable

• nfs.v4.snapshot.active.fsid.enable

22 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

• ssl.v2.enable

• ssl.v3.enable

For more information, see New options in Data ONTAP 8.0 7-Mode release family on page 52.

Changed options in Data ONTAP 8.0.1 7-Mode RC1

No options were changed in Data ONTAP 8.0.1 7-Mode RC1.

For more information, see Changed options in Data ONTAP 8.0 7-Mode release family on page 53.

New cautions in Data ONTAP 8.0.1 7-Mode RC1

The following new cautions were introduced in Data ONTAP 8.0.1 7-Mode RC1:

• Change in nondisruptive upgrade procedure on page 61• NetApp SnapValidator for Oracle not supported on page 70

For more information, see Important cautions on page 59.

Cautions removed in Data ONTAP 8.0.1 7-Mode RC1

The following cautions that were included in the Data ONTAP 8.0 Release Notes have been removedfrom Data ONTAP 8.0.1 7-Mode RC1:

• If you are upgrading a system that includes FlexVol volumes• If you revert from Data ONTAP 8.0 7-Mode and attempt to access LUN data in a Snapshot copy• Compression for SnapMirror transfers not supported• SMB 2.0 is not supported• Using ACP can cause system panic• 512-GB and 256-GB Performance Acceleration modules not supported

Cautions changed in Data ONTAP 8.0.1 7-Mode RC1

The following cautions changed in Data ONTAP 8.0.1 7-Mode RC1:

• Determining system capacity and space guarantees on page 65• If you are reverting to a Data ONTAP release with a lower maximum capacity on page 67

For more information, see Upgrade and revert cautions on page 60.

New known limitations in Data ONTAP 8.0.1 7-Mode RC1

Data ONTAP 8.0.1 7-Mode RC1 includes the following new limitations:

• Do not disable the IP fastpath option on a 32xx system in an HA pair on page 88• Shutdown delay in FAS2040 systems when critical thresholds are crossed on page 76• CIFS termination required before issuing a lock break on page 78

Changes introduced since Data ONTAP 8.0 | 23

• Tape backup and volume move operations must not be performed simultaneously on page 81• SMTape restore to an offline volume overwrites the data on that volume on page 81• Deleted file occupies additional space on SMTape restored volume on page 82• SSD Spare Block Consumed Limit reported as N/A on page 87• Incorrect warning of termination in spite of a successful giveback on page 89

For more information, see Known problems and limitations on page 75.

Limitations removed in Data ONTAP 8.0.1 7-Mode RC1

The following limitations were removed from Data ONTAP 8.0.1 7-Mode RC1:

• The -m option for the disk replace start command is not recognized• Qtree quotas might prevent explicit quotas from overriding the default• 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• Down nodes in a cluster containing a FlexCache origin volume can prevent

the FlexCache volume from connecting to the origin

Documentation changes for Data ONTAP 8.0.1 7-Mode RC1

The following new or changed information supplements the documentation you received for the DataONTAP 8.0.1 7-Mode RC1 release:

• Changes to the Data Protection Tape Backup and Recovery Guide on page 91• Changes to the Storage Management Guide on page 92• Changes to the File Access and Protocols Management Guide on page 92• Changes to the Block Access Management Guide for iSCSI and FC on page 94

For more information about these and other important documentation changes, see Changes topublished documentation on page 91.

24 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

New and changed features in the Data ONTAP 8.07-Mode release family

This section covers features that were added or changed in the Data ONTAP 8.0 7-Mode releasefamily.

Note: Some new and changed features in this release might also be introduced in a maintenancerelease of an earlier 7G release family. Before upgrading, be sure to consult with your NetApprepresentative about new Data ONTAP functionality to determine the best solution for yourbusiness needs.

Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases provide a new aggregatetype, 64-bit aggregates, with a larger maximum aggregate and FlexVol sizes, as well as improvedperformance, resiliency, and management capabilities for storage resources.

For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 35.

Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases also provide new platformand hardware support as described in New platform and hardware support on page 26 ,additional management capabilities such as SSL security improvements, additional capabilitiesusing iSCSI and FCP protocols for NetApp SAN environments, and enhanced data protectiontechnologies such as SnapMirror and SnapVault.

Additional major changes made in Data ONTAP 8.0 7-Mode release family are described here. Forother important information in these release notes about changes to the product made by thesereleases, 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. For a comparisonof bugs fixed in different releases, see Bugs Online - Release Comparison on the NOW site.

Next topics

New platform and hardware support on page 26

Changes in disk shelf support on page 29

Manageability enhancements on page 30

Storage resource management enhancements on page 34

Networking and security protocols enhancements on page 36

File access protocol enhancements on page 38

Block protocol enhancements on page 39

Data protection enhancements on page 40

High availability pair (formerly active/active configuration) enhancements on page 43

Changes to MultiStore support on page 44

Changes to the Data ONTAP and V-Series libraries on page 44

New and changed features in the Data ONTAP 8.0 7-Mode release family | 25

Related concepts

New and changed commands and options in the Data ONTAP 8.0 7-Mode releasefamily on page 45

Related information

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

New platform and hardware supportThe Data ONTAP 8.0 7-Mode release family supports new hardware as listed. The new platform andhardware are listed in the order of most recently introduced first.

For information about supported systems, see Supported systems on page 55.

Next topics

Support for 32xx platform on page 26

Support for 62xx platform on page 27

Support for 512-GB and 256-GB Performance Acceleration Module (PAM II) on page 27

Support for SSDs on page 28

Supported tape drives on page 28

Support for 2 TB SATA disks on page 28

Support for SA320 platform on page 28

Support for 32xx platformData ONTAP 8.0.1 and later releases support the 32xx platform.

Attention: New 32xx systems are installed at the factory with the latest Data ONTAP 8.0.xrelease. Before configuring Data ONTAP 7.3.x functionality on 32xx systems, you must installData ONTAP 7.3.5 according to the instructions provided in the Knowledgebase Article KB 61578posted on the NOW site.

The 32xx supports the following features:

• One or two controllers in a chassisOne-controller systems can be configured with a filler blank or an I/O expansion module, whichprovides four full-length PCIe slots.

• Two Gigabit Ethernet ports per controller• Two HA ports per controller• Two 3-Gb or 6-Gb SAS ports per controller• Two 4-Gb Fibre Channel ports per controller• One USB port per controller• One private management (ACP) port per controller• One remote management port per controller

26 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

• One full-length PCIe slot and one 3/4-length PCIe slot per controller• Service Processor• 4 GB, 8 GB, or 16 GB main memory per controller• Support for DS14mk2, DS14mk2 AT, DS14mk4, DS4243, and DS2246 disk shelves• Maximum FlexVol volumes supported: 3210: 200; 3240 and 3270: 500• Two on-board 10-GbE ports that are not available for configuration

Support for 62xx platformData ONTAP 8.0.1 and later releases support the 62xx platform.

The 62xx platform supports the following features:

• One or two controllers in a chassisOne-controller systems can be configured with a filler blank or an I/O expansion module, whichprovides six PCIe slots.

• Two Gigabit Ethernet ports per controller• Four HA ports per controller• Four 2-Gb, 4-Gb, or 8-Gb FC ports per controller• One USB port per controller• One private management (ACP) port per controller• One remote management port per controller• Two custom vertical PCIe x8 Gen2 expansion slots

One supports NVRAM8 adapterOne supports quad-port FC adapter or quad-port SAS adapter

• Four PCIe x8 Gen2 expansion slots• Service Processor• 24 GB or 48 GB main memory per controller• Support for DS14mk2, DS14mk2AT, DS14mk4, DS4243, and DS2246 disk shelves

Support for 512-GB and 256-GB Performance Acceleration Module (PAM II)Data ONTAP 8.0.1 7-Mode and later Data ONTAP 8.0.x 7-Mode releases support a PCIe-attachedPerformance Acceleration Module (PAM II also known as Flash Cache module) that uses Flashtechnology.

The addition of PAM II optimizes the performance of random read-intensive workloads such as fileservices, messaging, virtual infrastructure, and OLTP databases without using more high-performance disk drives.

For more information about PAM II modules supported with your storage system models, see theSystem Configuration Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 27

Support for SSDsData ONTAP 8.0.1 7-Mode and later Data ONTAP 8.0.x releases support solid-state disks (SSDs).SSDs are flash memory-based storage devices that provide better overall performance than hard diskdrives, or HDDs, which are mechanical devices using rotating media.

For more information about SSDs, see the Data ONTAP 7-Mode Storage Management Guide. Forinformation about which storage system models support SSDs, see the System Configuration Guideat now.netapp.com.

Supported tape drivesData ONTAP 8.0.1 and later releases support Quantum LTO-4, Quantum LTO-5, Hewlett-PackardLTO-4, Hewlett-Packard LTO-5, and IBM LTO-5 tape drives.

Support for 2 TB SATA disksIn Data ONTAP 8.0 and later releases, 2 TB SATA disks are supported for both the SAS and FC diskconnection types. With these larger disks and 64-bit aggregates, you can create larger aggregatesbefore being affected by spindle and aggregate size limits.

For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 35

Support for SA320 platformData ONTAP 8.0.1 7-Mode and later releases support the SA320 platform. SA systems are storagesystems capable of storing only FlexCache volumes.

The SA320 supports the following features:

• One controller and IO expansion module in a chassis• Four full-length PCIe slots and one 3/4-length PCIe slot• Two Gigabit Ethernet ports• Two HA ports• Two 3-Gb or 6-Gb SAS ports• Two 4-Gb Fibre Channel ports• One private management (ACP) port• One remote management port• Service Processor• 16 GB main memory• Support for DS14mk2, DS14mk2 AT, DS14mk4, DS4243, and DS2246 disk shelves

28 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Changes in disk shelf supportThe Data ONTAP 8.0 7-Mode release family includes some changes to disk shelf support.

Next topics

Support for DS2246 disk shelves on page 29

Support for DS4243 disk shelf on page 29

Support for DS2246 disk shelvesThe DS2246 disk shelf is supported on certain Data ONTAP releases.

The DS2246 disk shelf which contains external SAS disk drives and 6-Gb I/O modules, is supportedon the following Data ONTAP releases:

• Data ONTAP 8.x releases: Data ONTAP 8.0P1 or later, except 2040 storage systems, 8.0.1or later.

• Data ONTAP 7.x releases: Data ONTAP 7.3.3P2 or later, except 2040 and 2050 storage systems,7.3.4 or later.

For more information about which disks and disk shelves are supported with your storage systemmodel, see the System Configuration Guide. For more information about the DS2246 disk shelf, seethe DS2246 Disk Shelf Installation and Service Guide.

Related information

System Configuration Guide

Support for DS4243 disk shelfData 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 diskshelf 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 theDS4243 disk shelf, see the System Configuration Guide. For more information about the DS4243disk shelf, see the DS4243 Disk Shelf Installation and Service Guide.

Related information

System Configuration Guide

New and changed features in the Data ONTAP 8.0 7-Mode release family | 29

Manageability enhancementsData ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases provide additionalmanagement capabilities using MultiStore, FilerView, and other tools.

Next topics

Support for a 64-bit root volume on page 30

The Service Processor for the 32xx and the 62xx systems on page 30

Enhancements that allow you to specify SSL versions on page 31

SSL security improvements on page 31

The default security settings on page 31

Setup for root account password on page 32

The diagnostic account and the systemshell on page 33

Boot menu enhancements and changes on page 33

Read reallocation of data on page 33

Extents for FlexVol volumes on page 33

Partner recipients for AutoSupport email notifications on page 34

AutoSupport message file attachments on page 34

New disk drive AutoSupport message sent weekly on page 34

Support for a 64-bit root volumeAlthough your storage system is shipped with the root volume in a 32-bit aggregate, you candesignate a different volume to be the new root volume. Starting in Data ONTAP 8.0.1, you can usea volume in a 64-bit aggregate for the root volume.

For more information about the root volume, see the Data ONTAP 7-Mode System AdministrationGuide. For more information about 64-bit aggregates and volumes, see the Data ONTAP 7-ModeStorage Management Guide.

The Service Processor for the 32xx and the 62xx systemsThe Service Processor (SP) is a remote management device that is included in the 32xx and the 62xxsystems. The SP enables you to access, monitor, and troubleshoot the storage system remotely.

The SP provides the following capabilities:

• The SP enables you to access the storage system remotely to diagnose, shut down, power-cycle,or reboot the system, regardless of the state of the storage controller.The SP is powered by a standby voltage, which is available as long as the system has input powerto at least one of the system’s power supplies.The SP is connected to the system through the serial console. You can log in to the SP by using aSecure Shell client application from an administration host. You can then use the SP CLI to

30 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

monitor and troubleshoot the system remotely. In addition, you can use the SP to access thesystem console and run Data ONTAP commands remotely.You can access the SP from the system console or access the system console from the SP. The SPallows you to open both an SP CLI session and a separate system console session simultaneously.

• The SP monitors environmental sensors and logs system events to help you take timely andeffective service actions in the event that a system problem occurs.The SP monitors the system temperatures, voltages, currents, and fan speeds. When the SPdetects that an environmental sensor has reached an abnormal condition, it logs the abnormalreadings, notifies Data ONTAP of the issue, and takes proactive actions as necessary to sendalerts and “down system” notifications through an AutoSupport message.If SNMP is enabled for the SP, the SP generates SNMP traps to configured trap hosts for all“down system” events.The SP also logs system events such as boot progress, Field Replaceable Unit (FRU) changes,Data ONTAP-generated events, and SP command history.

• Hardware-assisted takeover is available on systems that support the SP and have the SPconfigured.

For more information about the SP, see the Data ONTAP 7-Mode System Administration Guide.

For more information about hardware-assisted takeover, see the Data ONTAP 7-Mode High-Availability Configuration Guide.

You must ensure that your system has the latest SP firmware version. You can use the sp statuscommand to display the SP firmware version on your system, and, if necessary, update the SP to thelatest version that is available on the NOW site. For instructions on how to download and update theSP firmware, see the Data ONTAP 7-Mode Upgrade Guide.

Enhancements that allow you to specify SSL versionsIf your storage system has the SSL protocol enabled, you can further specify the SSL version(s) touse by using the ssl.v2.enable and the ssl.v3.enable options.

SSL security improvementsAs a precautionary measure due to security vulnerability CVE-2009-3555, the SSL renegotiationfeature is disabled in Data ONTAP.

The default security settingsOn storage systems shipped with Data ONTAP 8.0 7-Mode or later, secure protocols are enabled andnonsecure protocols are disabled by default.

SecureAdmin is set up automatically on storage systems shipped with Data ONTAP 8.0 7-Mode orlater. 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.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 31

On storage systems shipped with Data ONTAP 8.0 7-Mode or later, the following are the defaultoption settings for SSH and SSL:

• options ssh.enable on• options ssh2.enable on• options ssh1.enable off• options ssh.passwd_auth.enable on• options ssh.pubkey_auth.enable on• options httpd.admin.ssl.enable on

Also on storage systems shipped with Data ONTAP 8.0 7-Mode or later, the following are the defaultoption 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-Modeor later. For storage systems upgraded from an earlier version to the Data ONTAP 8.0 releasefamily, the above default settings do not apply. Instead, for those upgraded systems, the settingsremain unchanged after the upgrade. Also, if you make security setting modifications afterupgrading to the Data ONTAP 8.0 release family, the modifications are preserved even if thesystem reverts back to the previous Data ONTAP version.

For more information about the default security settings, see the Data ONTAP 7-Mode SystemAdministration Guide.

Setup for root account passwordDuring the initial setup of a storage system shipped with Data ONTAP 8.0 7-Mode or later, you areprompted to set up a password for the root account.

The following are the default password rules for all accounts whensecurity.passwd.rules.enable is set to on (the default):

• The password must be at least eight characters long.• The password must contain at least one number.• The password must contain at least two alphabetic characters.

Note: Subsequent invocations of the setup command do not prompt you to set up a password forthe root account.

For more information about setting up the storage system, see the Data ONTAP 7-Mode SoftwareSetup Guide.

32 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

The diagnostic account and the systemshellA diagnostic account, named “diag,” is provided with your storage system. You can enable thediagnostic account to perform troubleshooting tasks in the systemshell. The diagnostic account andthe systemshell are intended only for low-level diagnostic purposes and should be used only withguidance from technical support.

The diagnostic account is the only account that can be used to access the systemshell, through theadvanced command systemshell. The diagnostic account is disabled by default. You must enablethe account and set up its password before using it. Neither the diagnostic account nor thesystemshell is intended for general administrative purposes.

Boot menu enhancements and changesThe boot menu includes new menu options that allow you to restore the configuration informationfrom 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 nota new traditional root volume from the boot menu. However, preexisting traditional root volumes arestill supported.

For information about the boot menu, see the na_floppyboot(1) man page and the Data ONTAP 7-Mode System Administration Guide.

Read reallocation of dataFor workloads that perform a mixture of random writes and large and multiple sequential reads, theread reallocation function improves the file's layout and sequential read performance.

When you enable read reallocation by using the vol options read_realloc command, DataONTAP analyzes the parts of the file that are read sequentially. If the associated blocks are notalready largely contiguous, Data ONTAP updates the file's layout by rewriting those blocks toanother location on the disk. The rewrite improves the file's layout, thus improving the sequentialread 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) manpage and the Data ONTAP 7-Mode System Administration Guide.

Extents for FlexVol volumesEnabling extents by setting the vol options extent command to on might improve performanceof Exchange database validation. However, to enable extents when storage space is a concern, youshould set the vol options extent command to space_optimized instead of on.

The space_optimized option conserves space. However, it results in degraded read performancethrough the Snapshot copies. Therefore, if fast read performance through Snapshot copies is a higherpriority 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 andthe Data ONTAP 7-Mode System Administration Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 33

Partner recipients for AutoSupport email notificationsThe new option autosupport.partner.to allows you to define the list of partner recipients forAutoSupport email notifications.

Whereas the autosupport.support.to option is read-only and displays where email-basedAutoSupport notifications are sent to technical support when the autosupport.support.enableoption is set to on (the default), the autosupport.partner.to option allows you to define a list ofpartner recipients who will receive all AutoSupport notifications regardless of the severity level orthe setting of the autosupport.support.enable option.

Using the autosupport.partner.to option, you can specify up to five email addresses forpartner recipients to receive AutoSupport notifications. The email addresses should be entered as acomma-separated list with no spaces between them. By default, the autosupport.partner.tooption is not defined and has an empty list.

To receive any email-based AutoSupport notifications, you must also define a mail host by using theautosupport.mailhost option.

AutoSupport message file attachmentsBeginning with Data ONTAP 8.0.1 7-Mode, the contents of /etc/messages and /etc/log/ems are nolonger sent in the body of AutoSupport messages. Instead, they are sent as .gz attachments toAutoSupport messages.

New disk drive AutoSupport message sent weeklyA weekly NetApp Health Trigger (NHT) AutoSupport message provides information about anyfailed 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 enhancementsData ONTAP 8.0.1 7-Mode and later releases provide improved performance, resiliency, andmanagement capabilities for storage resources.

Next topics

Support for 64-bit aggregates on page 35

File space utilization report on page 35

Upgrading to Data ONTAP 8.0.1 increases volume capacity after deduplication on page 35

Maximum simultaneous FlexClone file or FlexClone LUN operations per storagesystem on page 35

34 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

FlexClone files and FlexClone LUNs support on MultiStore on page 36

Increased maximum RAID group size for SATA disks on page 36

Support for 64-bit aggregatesIn Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports a new type of aggregate, the64-bit aggregate. 64-bit aggregates have a larger maximum size than aggregates created with earlierversions of Data ONTAP. In addition, volumes contained by 64-bit aggregates have a largermaximum 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 yourstorage system. To determine the maximum 64-bit aggregate size for your storage system model, seethe System Configuration Guide. The maximum size of a volume contained by a 64-bit aggregatecorresponds to the maximum size of its containing aggregate.

The maximum size for legacy aggregates, now called 32-bit aggregates, remains 16 TB.

For more information, see the Data ONTAP 8.0 7-Mode Storage Management Guide and thena_aggr(1) man page.

File space utilization reportThe file space utilization report enables you to see the files and the amount of space that they occupyin a deduplicated volume. You can choose to either move or delete the files to reclaim the space.

This report provides a view of the total number of blocks in a file and the number of blocks that areshared by non-deduplicated or non-cloned files.

Note: Total blocks refer to the number of blocks in a file, including blocks that are required forstoring the file metadata.

Upgrading to Data ONTAP 8.0.1 increases volume capacity afterdeduplication

After you upgrade to Data ONTAP 8.0.1 and later from an earlier release of Data ONTAP, you canincrease the deduplicated volume size up to 16 TB.

Maximum simultaneous FlexClone file or FlexClone LUN operations perstorage system

Starting with Data ONTAP 8.0 7-Mode, you can simultaneously run a maximum of 500 FlexClonefile or FlexClone LUN operations on a storage system.

For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP 8.0 7-ModeStorage Management Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 35

FlexClone files and FlexClone LUNs support on MultiStoreIn Data ONTAP 7.3.3 and later releases of the 7.x release family, and in Data ONTAP 8.0.1 andlater, the FlexClone files and FlexClone LUNs commands are available in the default and nondefaultvfiler contexts.

You can use FlexClone files and LUNs feature to create writable, space-efficient clones of parentfiles and parent LUNs within a vFiler unit. Storage owned by a vFiler unit cannot be accessed ordiscovered from other vFiler unit by using the FlexClone file or LUN commands.

For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP 7-ModeStorage Management Guide.

Increased maximum RAID group size for SATA disksStarting in Data ONTAP 8.0.1, the maximum raid group size allowed for ATA, BSAS, and SATAdisks has increased from 16 to 20 disks. The default size remains the same, at 14 disks.

Networking and security protocols enhancementsData ONTAP 8.0.1 7-Mode and later releases provide enhanced network performance and securityfeatures.

Next topics

Support for the SMB 2.0 protocol on page 36

TSO in NICs on page 36

Support for CDP on page 37

Port-based load-balancing option for multimode interface groups on page 37

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

Configuration for receiving untagged traffic on VLAN tagged interfaces on page 37

Vifs are now known as interface groups on page 38

Support for the SMB 2.0 protocolData ONTAP 8.0.1 and later support the SMB 2.0 protocol, which is more suitable than the originalSMB protocol in environments requiring an increased level of scalability and data integrity.

For more information, see the Data ONTAP 7-Mode File Access and Protocols Management Guide.

TSO in NICsTCP segmentation offload (TSO) is a hardware feature supported on NICs to increase the host CPU'sefficiency.

Starting from Data ONTAP 8.0.1, TSO is enabled on all the supported network interfaces across allplatforms. In Data ONTAP 8.0.1, the new network interface cards that support TSO are:

36 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

• Dual 10G Ethernet Controller CNA - SFP+• 10 Gigabit Ethernet Controller IX1 - SFP+

For more information about TSO and the statistics displayed by the NICs, see the Data ONTAP 7-Mode Network Management Guide.

Support for CDPCisco Discovery Protocol (CDP) is supported in Data ONTAP 7.3.3 and later releases of the 7.xrelease family, and in Data ONTAP 8.0.1 and later. CDP enables you to automatically discover andview information about directly connected CDP-enabled devices in a network.

For more information about CDP, see the Data ONTAP 7-Mode Network Management Guide.

Port-based load-balancing option for multimode interface groupsPort-based load balancing is supported for multimode interface groups in Data ONTAP 7.3.2 andlater releases of the 7.x release family, and in Data ONTAP 8.0.1 and later. On a multimode interfacegroup, you can uniformly distribute outgoing traffic based on the transport layer (TCP or UDP) portsand network layer addresses by using the port-based load-balancing method.

The port-based load-balancing method uses a fast hashing algorithm on the source and destination IPaddresses along with the transport layer (TCP or UDP) port number.

For more information about port-based load balancing, see the Data ONTAP 7-Mode NetworkManagement Guide.

64-bit SNMP object identifiers (OIDs) are supportedIn Data ONTAP 7.2 and 7.3 release families, some OIDs in the netapp.mib file have low and high32-bit values. In Data ONTAP 8.0.1 7-Mode, these OIDs are replaced with 64-bit values. You shoulduse 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-bitOID misc64NfsOps. In the netapp.mib file, miscHighNfsOps and miscLowNfsOps are markedas 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 interfacesIn Data ONTAP 8.0.1 7-Mode, you can configure an IP address for a network interface with VLANs.Any untagged traffic goes to the base interface, and the tagged traffic goes to the respective VLAN.

For more information about this feature, see the Data ONTAP 7-Mode Network Management Guide.

For information about reverting with a configuration for receiving tagged and untagged frames on thesame network interface, see the Data ONTAP 7-Mode Upgrade Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 37

Vifs are now known as interface groupsStarting with Data ONTAP 8.0.1 7-Mode, vifs are known as interface groups. An interface grouprefers to a single virtual interface that is created by grouping together multiple physical interfaces. Inthe 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 informationabout interface groups and the ifgrp command, see the Data ONTAP 7-Mode NetworkManagement Guide.

File access protocol enhancementsData ONTAP 8.0.1 7-Mode and later releases provide new features of NFSv4 and FPolicy, newcommands for debugging CIFS file access control problems, a new option for specifying theminimum levels of authentication and session security that clients must use, and compatibility withWindows Vista and Windows Server 2008.

For more information about these features, see the Data ONTAP 7-Mode File Access and ProtocolsManagement Guide.

Next topics

Maximum number of auxiliary UNIX groups supported for a user on page 38

Support for multiple open instances of the SMB named pipe on an FPolicy server on page 38

Maximum number of auxiliary UNIX groups supported for a userIf you use Kerberos V5 authentication, the maximum number of auxiliary UNIX groups that a usercan be a member of is 32 by default. You can increase the maximum to 256 groups by setting thenfs.max_num_aux_groups option to 256. However, in FlexCache setups, Data ONTAP supportsa maximum of 32 auxiliary UNIX groups for FlexCache volumes, regardless of the value set for thisoption.

If you do not use Kerberos V5 authentication, the maximum number of auxiliary UNIX groups that auser can be a member of is 16.

For more information about the nfs.max_num_aux_groups option, see the na_options(1) manpage.

Support for multiple open instances of the SMB named pipe on an FPolicyserver

In Data ONTAP you can enable multiple open instances of the SMB named pipe on an FPolicyserver by using the fpolicy.multiple_pipes option.

For more information, see the Data ONTAP 7-Mode File Access and Protocols Management Guide.

38 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Block protocol enhancementsData ONTAP 8.0.1 7-Mode and later releases provide additional capabilities using iSCSI and FCPprotocols for NetApp SAN environments.

For more information about these features, see the Data ONTAP 7-Mode Block Access ManagementGuide for iSCSI and FC.

Next topics

10-GbE Unified Target Adapter protocol support on page 39

iSCSI RADIUS support on page 39

Support for NetApp DataMotion for Volumes on page 40

VMware VAAI features for ESX hosts support on page 40

igroup scalability limits on page 40

10-GbE Unified Target Adapter protocol supportThe current 10-GbE Unified Target Adapters (UTA) provide additional protocol options for SANand NAS connectivity by extending support to IP storage.

With Data ONTAP 8.0.1, the UTAs add support for the iSCSI, NFS, and CIFS protocols andcontinue to support the FCoE protocol.

The 10-GbE UTAs are still offered in two versions:

• Optical - part number X1139A-R6• Copper - part number X1140A-R6

For additional details, visit the Protocols solutions Web site and the Hardware Information Library(see the section in the library for NIC, HBA, TOE Target Flyers).

Related information

NetApp FCoE SAN solutions - http://www.netapp.com/us/products/protocols/fcoe/NetApp Protocols SAN solutions - http://www.netapp.com/us/products/protocols/Netapp Hardware Information Library - http://now.netapp.com/NOW/knowledge/docs/hardware/hardware_index.shtml

iSCSI RADIUS supportData ONTAP 8.0.1 7-Mode introduces support for iSCSI RADIUS, which allows you to centrallymanage iSCSI initiator authentication.

RADIUS still uses CHAP to authenticate iSCSI initiators, but it allows you to manage theauthentication process from a central RADIUS server, rather than manage them manually on eachstorage system. In larger SAN environments, this can greatly simplify iSCSI initiator managementand provide added security.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 39

In addition to simplifying CHAP password management, RADIUS also reduces the load on yourstorage system. The RADIUS client service runs on the storage system and communicates with theRADIUS server and initiators, but most of the authentication processing is handled by the RADIUSserver.

For more information, see the Data ONTAP 7-Mode Block Access Management Guide for iSCSI andFC.

Support for NetApp DataMotion for VolumesData ONTAP 8.0.1 7-Mode or later supports NetApp DataMotion for Volumes which enables you tonondisruptively move a volume from one aggregate to another within the same controller forcapacity utilization, improved performance, and to satisfy service-level agreements. In a SANenvironment, FlexVol volumes and the LUNs in the volumes are moved nondisruptively from oneaggregate to another.

The volume move occurs in three phases: setup phase, data copy phase, and cutover phase.

For more information about the volume move, see Data ONTAP 7-Mode Block Access ManagementGuide for iSCSI and FC.

VMware VAAI features for ESX hosts supportData ONTAP 8.0.1 and later supports certain VMware vStorage APIs for Array Integration (VAAI)features when the ESX host is running ESX 4.1 or later. These features help offload operations fromthe ESX host to the storage system and increase the network throughput.

The ESX host enables the features automatically in the correct environment. You can determine theextent to which your system is using the VAAI features by checking the statistics contained in theVAAI counters.

For more information about the VMware VAAI features for ESX hosts, see Data ONTAP 7-ModeBlock Access Management Guide for iSCSI and FC.

igroup scalability limitsData ONTAP 8.0.1 introduces support to expand the host side scalability by expanding the number ofigroups supported on FAS3xxx and FAS6xxx systems from 512 per controller to 1024 per controller.

Data protection enhancementsData ONTAP 8.0.1 7-Mode and later releases provide enhanced data protection technologies (such asSnapMirror and SnapVault), SMTape operations, and security administration.

For more information about these features, see the Data ONTAP 7-Mode Data Protection OnlineBackup and Recovery Guide and the Data ONTAP 7-Mode Data Protection Tape Backup andRecovery Guide.

40 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Next topics

Support for 840 disk drives on fabric-attached MetroClusters on page 41

Support for out-of-order frame delivery for SnapMirror over Fibre Channel on page 41

Support for SnapMirror relationship between two FlexClone volumes on page 41

Support for SnapMirror network compression on page 42

Support for designated range of ports for NDMP data connections on page 42

If volumes with deduplication exceed the maximum supported size on page 42

NearStore license is not required for deduplication on page 42

Maximum concurrent deduplication operations supported on page 42

Prerequisite for backing up data to tape using NDMP services on page 42

Snapshot copy schedules on page 43

SnapMirror support for 64-bit volumes on page 43

SnapVault support for 64-bit volumes on page 43

Support for 840 disk drives on fabric-attached MetroClustersIn Data ONTAP 8.0.1 7-Mode and later, fabric-attached MetroCluster configurations can support upto 840 disk drives.

For more information, see the Data ONTAP 7-Mode High-Availability Configuration Guide.

Support for out-of-order frame delivery for SnapMirror over Fibre ChannelData ONTAP 8.0.1 and later support out-of-order frame delivery for SnapMirror over Fibre Channel.

When enabled, out-of-order frame delivery for SnapMirror over Fibre Channel eliminates therequirement to deliver all the frames in the same sequence in which the frames were transmitted. Thisfeature ensures the uninterrupted SnapMirror transfers regardless of the order in which the frames aredelivered.

For more information about out-of-order frame delivery, see Data ONTAP 7-Mode Data ProtectionOnline Backup and Recovery Guide.

Support for SnapMirror relationship between two FlexClone volumesData ONTAP 8.0.1 and later support SnapMirror relationship between two FlexClone volumes.

The SnapMirror relationship between two FlexClone volumes that have the common base Snapshotcopy helps in establishing a SnapMirror relationship without transferring the common Snapshot dataagain to the destination system.

For more information about SnapMirror relationship between two FlexClone volumes, see DataONTAP 7-Mode Data Protection Online Backup and Recovery Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 41

Support for SnapMirror network compressionData ONTAP 7.3.2 and later releases of the 7.x release family, and Data ONTAP 8.0.1 and latersupport SnapMirror network compression. This feature is supported only for asynchronous volumeSnapMirror.

Note: The SnapMirror destination system should be using Data ONTAP 7.3.2 or later release thatsupport SnapMirror network compression.

The SnapMirror network compression feature enables data compression over the network forSnapMirror transfers. It helps in optimizing network bandwidth utilization between SnapMirrorsource and destination systems. This feature can be especially useful for connections that haverelatively low bandwidth, such as WAN connections.

For more information about SnapMirror network compression, see the Data ONTAP 7-Mode DataProtection Online Backup and Recovery Guide.

Support for designated range of ports for NDMP data connectionsData ONTAP 8.0.1 supports designated range of ports that can be used for NDMP data connectionsin response to NDMP_DATA_LISTEN and NDMP_MOVER_LISTEN operations. Therefore, youcan perform data migration by using ndmpcopy command and 3-way tape backups even inenvironments where the source and destination networks are separated by a firewall.

If volumes with deduplication exceed the maximum supported sizeVolumes continue to be online when they exceed the maximum supported size. For more informationabout the maximum volume size allowed for different storage systems, with and withoutdeduplication, see the Data ONTAP 7-Mode Storage Management Guide.

NearStore license is not required for deduplicationStarting with Data ONTAP 8.0.1 7-Mode, you do not have to enable the NearStore personalitylicense to use deduplication.

Maximum concurrent deduplication operations supportedYou can run a maximum of eight concurrent deduplication operations on all storage systems.

Prerequisite for backing up data to tape using NDMP servicesStarting from Data ONTAP 8.0 7-Mode, NDMP users must have the login-ndmp capability forsuccessfully authenticating NDMP sessions.

A predefined role named backup has the login-ndmp capability, by default. To provide a user withthe 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-ndmpcapability. Therefore, it is best to group all NDMP users into a single group that has the 'backup’role.

42 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Snapshot copy schedulesScheduled 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 creationthat has failed and automatically creates a Snapshot copy for that schedule. This feature is availablein 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 OnlineBackup and Recovery Guide.

SnapMirror support for 64-bit volumesData ONTAP 8.0.1 7-Mode and later releases in this release family support 64-bit volumes inaddition to 32-bit volumes. SnapMirror supports replication between 64-bit volumes and alsobetween 32-bit volumes. However, there are certain considerations when replicating volumes andqtrees using SnapMirror.

When replicating volumes by using SnapMirror, synchronously or asynchronously, the source anddestination volumes must be of the same type. Both the source and destination volumes must be 64-bit volumes or they must both be 32-bit volumes.

When replicating qtrees by using SnapMirror, the source and destination volumes can be of differenttypes. 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 7-Mode Data Protection Online Backup and Recovery Guide.

SnapVault support for 64-bit volumesData ONTAP 8.0.1 7-Mode and later releases in this release family support 64-bit volumes.SnapVault supports replication between 64-bit volumes, in addition to supporting replicationbetween 32-bit volumes. When replicating qtrees by using SnapVault, the source and destinationvolumes 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 ProtectionOnline Backup and Recovery Guide.

High availability pair (formerly active/active configuration)enhancements

Data ONTAP 8.0.1 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 HApair has replaced active/active configuration.

For more information about these features, see the Data ONTAP 7-Mode High-AvailabilityConfiguration Guide.

New and changed features in the Data ONTAP 8.0 7-Mode release family | 43

HA pair terminology changesThe high-availability (HA) functionality referred to as an HA pair in Data ONTAP 8.0 was called anactive/active configuration in the Data ONTAP 7.2 and 7.3 release families. In the Data ONTAP 7.1release 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 thesefeatures, see the Data ONTAP High-Availability Configuration Guide.

Changes to MultiStore supportData ONTAP provides MultiStore capabilities and changes.

Data Motion is not supported in the Data ONTAP 8.0 7-Mode release familyData Motion 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 technologiesso that you can perform data migrations nondisruptively in both physical and virtual environments.

Changes to the Data ONTAP and V-Series librariesThe Data ONTAP 7-Mode Software Setup Guide now provides information for basic setup of allsystems that run Data ONTAP, including a V-Series system. Data ONTAP guides and V-Seriesguides are now are available on the same Documentation web page.

Starting in Data ONTAP 7.3.2, much of the information about using Data ONTAP features with V-Series systems was integrated into the general Data ONTAP guides. This effort was continued inData ONTAP with the integration of V-Series system setup instructions into the Data ONTAP 7-Mode Software Setup Guide. As of Data ONTAP 8.0 7-Mode, there is no longer a separate setupguide for V-Series.

V-Series documents now focus primarily on information about implementation with the back-endstorage arrays.

The Data ONTAP 8.0 7-Mode Documentation page now provides both the general Data ONTAP 8.07-Mode guides and the V-Series specific guides on the same Documentation web page; there is nolonger a separate Documentation page for the V-Series guides. You can access the integrated DataONTAP 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

44 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

New and changed commands and options in theData ONTAP 8.0 7-Mode release family

This section provides information about the commands, options, and configuration files that havebeen changed in or added to the Data ONTAP 8.0.1 7-Mode release family.

Next topics

New commands in Data ONTAP 8.0 7-Mode release family on page 45

Changed commands in Data ONTAP 8.0 7-Mode release family on page 48

Replaced or removed commands in Data ONTAP 8.0 7-Mode release family on page 51

New options in Data ONTAP 8.0 7-Mode release family on page 52

Changed options in Data ONTAP 8.0 7-Mode release family on page 53

New commands in Data ONTAP 8.0 7-Mode release familyMany 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 Purpose Document Release Introduced

acpadmin

configureConfigures the ACPsubsystem.

Data ONTAP 7-ModeStorage ManagementGuide

na_acpadmin(1) manpage

8.0

acpadmin list_all Displays informationabout the ACP (AlternateControl Path) storagesubsystem.

Data ONTAP 7-ModeStorage ManagementGuide

na_acpadmin(1) manpage

8.0

cdpd Displays informationabout devices thatadvertise themselves byusing the CDPv1protocol.

Data ONTAP 7-ModeNetwork ManagementGuide

8.0.1

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 45

Command Purpose Document Release Introduced

du Displays the files andamount of space that theyoccupy in a deduplicatedvolume.

Data ONTAP 7-ModeStorage ManagementGuide

8.0.1

ifgrp Manages interface groupson your storage system.

This command replacesthe vif command.

However, the optionsremain the same.

Data ONTAP 7-ModeNetwork ManagementGuide

8.0

smtape abort Aborts a backup orrestore job initiated by theSMTape engine.

Data ONTAP 7-ModeData Protection TapeBackup and RecoveryGuide

na_smtape manpage

8.0

smtape backup Backs up blocks of datato tape.

Data ONTAP 7-ModeData Protection TapeBackup and RecoveryGuide

na_smtape manpage

8.0

smtape continue Continues an SMTape-initiated backup or restoreoperation after it hasreached the end of currenttape and is in the waitstate to write output to oraccept input from a newtape

Data ONTAP 7-ModeData Protection TapeBackup and RecoveryGuide

na_smtape manpage

8.0

smtape restore Restores blocks of datafrom tape.

Data ONTAP 7-ModeData Protection TapeBackup and RecoveryGuide

na_smtape manpage

8.0

smtape status Displays the status ofSMTape-initiated backupand restore operations

Data ONTAP 7-ModeData Protection TapeBackup and RecoveryGuide

na_smtape manpage

8.0

46 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Command Purpose Document Release Introduced

sp help Displays the DataONTAP sp commands

that you can enter at thestorage system prompt.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp reboot Reboots the SP andcauses the SP to performa self-test.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp setup Initiates the interactive SPsetup script.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp status Displays the currentstatus and the networkconfiguration of the SP.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp test autosuppo

rtSends a test e-mail to allrecipients specified withthe autosupport.to

option.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp test snmp Performs SNMP test onthe SP, forcing the SP tosend a test SNMP trap toall trap hosts specified inthe snmp traphost

command.

Data ONTAP 7-ModeSystem AdministrationGuide

na_sp(1) man page

8.0.1

sp update Updates the SP firmware. Data ONTAP 7-ModeUpgrade Guide

na_sp(1) man page

8.0.1

storage array

modifyModifies attributes ofarray profile records.

na_storage(1) man page 8.0

storage array

purge-databaseRemoves all records fromthe controller’s arrayprofile database.

na_storage(1) man page 8.0

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 47

Command Purpose Document Release Introduced

storage array

removeRemoves records for thespecified array from thecontroller’s array profiledatabase.

na_storage(1) man page 8.0

storage array

remove-portRemoves ports associatedwith an array profile.

na_storage(1) man page 8.0

storage array

showLists all array profilerecords known to thecontroller.

na_storage(1) man page 8.0

storage array

show-configProvides a summary ofthe connectivity to SAN-attached arrays connectedto the V-Series system’sFC initiator ports.

V-Series InstallationRequirements andReference Guide

na_storage(1) man page

8.0

storage array

show-luns array-

name

Lists all array LUNsexported from a namedstorage array.

na_storage(1) man page 8.0

storage array

show-portsLists all target ports forall storage arrays knownto the V-Series system.

na_storage(1) man page 8.0

storage show acp Displays informationabout the ACP (AlternateControl Path) storagesubsystem.

Data ONTAP 7-ModeStorage ManagementGuide

na_acpadmin(1) manpage

8.0

Changed commands in Data ONTAP 8.0 7-Mode releasefamily

This table lists the commands that have been changed in the Data ONTAP 8.0 7-Mode releasefamily.

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.

48 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Command Change Documentation Release commandchanged in

aggr create The -B option has been

added. This option isused to create a 64-bitaggregate.

na_aggr(1) man page

Data ONTAP 7-ModeStorage Management Guide

8.0

df The -x option has been

added. This optionsurpresses the display ofthe .snapshot lines.

na_df(1) man page 8.0

disk assign You can no longer usethis command to changethe ownership of a disk orarray LUN that is alreadyowned unless you arerunning the command onthe system that owns thedisk already.

na_disk(1) man page 8.0

environment shelf The ComplexProgrammable LogicDevide (CPLD) versionhas been added to theoutput.

na_environment(1) man page 8.0

ifgrp create

multiThe port value (port-

based load-balancing) forthe -b option has been

added.

Data ONTAP 7-ModeNetwork Management Guide

8.0.1

software update The -r option, which

suppresses automaticreboot, is now thedefault. To request anautomatic reboot, younow must specify the -R

option.

na_software(1) man page

Data ONTAP 7-ModeUpgrade Guide

8.0.1

storage show acp A column for "Moduletype" has been added tothe output. This showsthe type of the I/Omodule.

8.0.1

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 49

Command Change Documentation Release commandchanged in

storage show

expanderThe system interconnectlink (SIL) ports (the lastfour rows of output) arenow shown as [SIL0]through [SIL3].Previously they wereshown as [DIS0] through[DIS3].

na_storage(1) man page 8.0

storage show

expanderThe DS4243 disk shelfports are now listed as[SQR0]-[SQR3] for thesquare ports and [CIR4]-[CIR7] for the circleports. Previously theseports were listed as [IO0]-[IO7].

na_storage(1) man page 8.0

storage show

faultYou can now specify ashelf name for thiscommand to seeinformation about aspecific shelf.

8.0.1

sysconfig When the -r option is

used to display diskinformation for SAS-connected disks, theCHAN (channel) columnnow displays the port as"A" or "B", just as it doesfor FC-connected disks.Previously, "1" and "2"were used.

na_sysconfig(1) man page 8.0

vif This command has beenreplaced by the ifgrp

command.

Data ONTAP 7-ModeNetwork Management Guide

8.0

vol options The extent option

enables extents but canonly be used on FlexVolvolumes.

na_vol(1) man page and theData ONTAP 7-ModeSystem AdministrationGuide

8.0

50 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Command Change Documentation Release commandchanged in

vol options The read_realloc

option enables readreallocation but can onlybe used on FlexVolvolumes.

na_vol(1) man page and theData ONTAP 7-ModeSystem AdministrationGuide

8.0

vol status When the -r option is

used to display diskinformation for SAS-connected disks, theCHAN (channel) columnnow displays the port as"A" or "B", just as it doesfor FC-connected disks.Previously, "1" and "2"were used.

na_vol(1) man page 8.0

Replaced or removed commands in Data ONTAP 8.0 7-Moderelease 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. Toperform the equivalent operation, use the aggr command.

• vol add

• vol media_scrub

• vol migrate

• vol mirror

• vol scrub

• vol split

• vol verify

• vol wafliron

These commands are removed in Data ONTAP 8.0 7-Mode.

• snapmirror store

• snapmirror use

• snapmirror retrieve

In Data ONTAP 8.0 7-Mode, the vif command has been replaced by the ifgrp command. For moreinformation, see the Data ONTAP 8.0 7-Mode Network Management Guide.

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 51

New options in Data ONTAP 8.0 7-Mode release familyOptions 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 thisinformation:

• 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 Purpose DefaultValue

Releaseadded

autosupport.performance_

data.doit any_stringTriggers a performance snapshotAutoSupport message when any stringis added.

NA 8.0

autosupport.periodic.tx_

windowtimeSpecifies the randomized delay windowfor periodic AutoSupport messages.

60 minutes 8.0.1

cf.takeover.on_panic Triggers a takeover if the partner modepanics.

On 8.0

cf.takeover.on_reboot Triggers a takeover if the partner nodereboots.

The default ison, unlessFCP or iSCSIis licensed, inwhich casethe default isoff.

8.0

cf.givegack.auto.delay.s

econdsAdjusts the giveback delay time forautomatic giveback.

300 seconds 8.0

ndmpd.data_port_range Specifies a port range on which theNDMP server can listen for dataconnections

all 8.0.1

nfs.max_num_aux_groups Specifies the maximum number ofauxiliary UNIX groups that a user canbe a member of.

32 8.0

52 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Option Purpose DefaultValue

Releaseadded

nfs.v3.snapshot.active.f

sid.enableDetermines whether the FSID ofobjects in a snapshot matches the FSIDof the active file system for NFSv3.

on 8.0.1

nfs.v4.snapshot.active.f

sid.enableDetermines whether the FSID ofobjects in a snapshot matches the FSIDof the active file system for NFSv4.

off 8.0.1

fpolicy.multiple_pipes Enables multiple open instances of theSMB named pipe on an FPolicy server.

on 8.0

sp.setup Displays whether the SP has beenconfigured.

(N/A) 8.0.1

ssl.v2.enable Enables or disables SSLv2. on 8.0.1

ssl.v3.enable Enables or disables SSLv3. on 8.0.1

Changed options in Data ONTAP 8.0 7-Mode release familyThis 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 Change Release changed

flexscale.max_io_qdepth This option has become obsolete. 8.0

httpd.admin.enable The default for this option has beenchanged to off for systems

shipped with Data ONTAP 8.0 7-Mode or later.

8.0

httpd.admin.ssl.enable The default for this option has beenchanged to on for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

New and changed commands and options in the Data ONTAP 8.0 7-Mode release family | 53

Option Change Release changed

rsh.enable The default for this option has beenchanged to off for systems

shipped with Data ONTAP 8.0 7-Mode or later.

8.0

ssh.enable The default for this option has beenchanged to on for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

ssh2.enable The default for this option has beenchanged to on for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

security.passwd.rules.e

veryoneThe default for this option has beenchanged to on for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

security.passwd.rules.h

istoryThe default for this option has beenchanged to 6 for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

telnet.distinct.enable The default for this option has beenchanged to on for systems shipped

with Data ONTAP 8.0 7-Mode orlater.

8.0

telnet.enable The default for this option has beenchanged to off for systems

shipped with Data ONTAP 8.0 7-Mode or later.

8.0

timed.max_skew This option has become obsolete. 8.0

timed.proto The rtc and the rdate

parameters of this option havebecome obsolete. The default hasbeen changed to ntp.

8.0

timed.sched This option has become obsolete. 8.0

timed.window This option has become obsolete. 8.0

54 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Requirements for running Data ONTAP 8.0.1 7-Mode

You can use the information in this section to verify that you have the storage systems and firmwareneeded to run Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases, and inparticular, to create high-availability configurations.

To find out your storage system model's system capacity and maximum volume size, see the SystemConfiguration Guide.

Next topics

Supported systems on page 55

Unsupported systems on page 56

Storage system firmware on page 56

Storage systems that support Multipath Storage on page 57

V-Series requirements and support information on page 58

Related information

System Configuration Guide: now.netapp.com/NOW/knowledge/docs/hardware/NetApp/syscfg/

Supported systemsYou need one of the supported storage systems listed in this section to run Data ONTAP 8.0 7-Modeor later Data ONTAP 8.0.x 7-Mode releases.

The following FAS and V-series storage systems are supported:

• 60xx• 3140• 3160• 3170• 3040• 3070• 2040• 32xx• 62xx

The following FlexCache storage systems are supported:

• SA600• SA300

Requirements for running Data ONTAP 8.0.1 7-Mode | 55

All systems supported by Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releasescan be configured as an HA pair.

For additional information about supported storage systems in Data ONTAP 8.0 7-Mode and laterData ONTAP 8.0.x 7-Mode releases, see the System Configuration Guide.

Unsupported systemsThere are some storage systems that are not supported in the Data ONTAP 8.0 7-Mode releasefamily.

The following storage system models are not supported in Data ONTAP 8.0 7-Mode and later DataONTAP 8.0.x 7-Mode releases:

• 9xx• GF900• 2xx• GF270c• R200• 2020• 2050• 3020• 3050• SA200

Storage system firmwareYou need to confirm that you have the latest firmware for your storage system, disks, and diskshelves.

The following storage system components have firmware that sometimes requires upgrading:

• Motherboards (their firmware is also known as system or storage system firmware)• Disk drives• Disk shelves

Storage system firmware

It is best to upgrade to the latest version of storage system firmware. For a list of available systemfirmware, see the "System Firmware Release Table" on the NOW site.

Note: The latest system firmware is included with Data ONTAP upgrade packages. For moreinformation, see the Data ONTAP 7-Mode Upgrade Guide.

56 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Disk firmware

For information about the latest disk firmware, see the "Disk Drive & Firmware Matrix" on theNOW site.

Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For moreinformation, 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/fwDisk 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 StorageTo configure Multipath Storage, which provides redundancy for the path from each controller toevery disk shelf in the configuration and is the preferred cabling method, you need to have asupported storage system, disk shelves and modules.

Multipath Storage is supported on the following NetApp storage systems and disk shelves:

• All FAS systems• All SA systems

• V60xx,V30xx, and V31xx storage systems• All disk shelves except the following disk shelves and modules:

• Non-RoHS-compliant ESH2 modules• Non-RoHS-compliant AT-FCX modules

Note: While Multipath adds value to a stretch MetroCluster environment, it is not necessary in afabric-attached MetroCluster configuration because multiple paths already exist.

The only V-series systems that support native disk shelves are V60xx, V30xx, and V31xx .Therefore, they are the only V-series models for which Multipath Storage applies on V-Seriessystems. On each node in an active/active configuration of V-Series systems using native diskshelves, you must configure the fc-non-array-adapter list environment variable for thefirst 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.

Requirements for running Data ONTAP 8.0.1 7-Mode | 57

V-Series requirements and support informationNot all Data ONTAP releases support the same features, configurations, storage system models, andstorage array models for V-Series systems. The V-Series Support Matrix is the final authority onsupported 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 andstorage 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 withV-Series systems. You can access the V-Series Support Matrix on the NOW site.

Requirements for V-Series fabric-attached MetroCluster configurationsV-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 "clustertakeover 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 toconfigure switches, hardware, or both to support in-order delivery of FC-VI traffic.

58 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Important cautions

Before deploying this release of Data ONTAP, make sure that you read the following items toidentify 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 BugsOnline on the NOW site.

Next topics

Unsupported features on page 59

Upgrade and revert cautions on page 60

Block access protocol cautions on page 68

Data protection cautions on page 70

Manageability cautions on page 71

Network protocol cautions on page 72

Related information

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

Unsupported featuresSome 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 Data ONTAP 8.0.1 7-Mode:

• NetApp SnapValidator for Oracle not supported on page 70• SnapLock is not supported on page 70• IPv6 is not supported on page 73

Doing so might cause your system to halt or make storage data unavailable to your clients. If yourequire these features in your business environment, contact your NetApp representative to evaluatethe best upgrade path.

If you have configured any of the following features in an earlier Data ONTAP release, they aredisabled during the upgrade to Data ONTAP 8.0.1 7-Mode:

• Data Motion is not supported on page 44• TLS is not supported on page 71• If you need to boot the storage system from a Data ONTAP image stored on a remote

server on page 71

Important cautions | 59

• IPsec is not supported on page 73• TOE is not supported on page 73

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 63• If you use upgrade images to upgrade to Data ONTAP 8.0 7-Mode or later on page 61• Hardware-based disk ownership• Media kits• SnapVault for NetBackup

Upgrade and revert cautionsIf 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

Change in nondisruptive upgrade procedure on page 61

If you use upgrade images to upgrade to Data ONTAP 8.0.1 7-Mode or later on page 61

If you are updating a system with AT-FCX disk shelves attached on page 62

If you are upgrading a FAS3050 system on page 62

Systems including DS14 shelves, ESH modules or LRC modules on page 63

Upgrading FAS3140/FAS3170 systems on page 64

Do not remove the special system files that are for restoring LUNs in snapshot copies on page 64

If you are upgrading to Data ONTAP 8.0.1 7-Mode or later from a release earlier than DataONTAP 7.3 on page 64

If your root FlexVol volume does not meet the new size requirements on page 66

If you are performing a nondisruptive upgrade on a system with VMware ESX Serverhosts on page 66

If you are upgrading a system that includes deduplicated volumes on page 66

If your system uses rtc or rdate as the protocol for time synchronization on page 66

If you modify the timed options and then revert to a release prior to Data ONTAP 8.0 7-Mode on page 67

If you have been using the flex_cache license on page 67

If you are reverting to a Data ONTAP release with a lower maximum capacity on page 67

If you are reverting to a previous release and you use deduplication on page 68

60 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Change in nondisruptive upgrade procedureWhen you upgrade to this Data ONTAP release, you should be aware of changes in the softwareupdate command syntax and the requirement for boot environment access.

Beginning with system firmware is updated automatically. It is no longer necessary to access theboot environment for upgrades from a Data ONTAP 8.0.x release to a later release.

Note: This change only refers to minor nondisruptive upgrades (within a release family). Whenupgrading to a Data ONTAP 8.0.x release from an earlier release family, you must enter the bootenvironment during the takeover phase to ensure that the Data ONTAP 8.0.x release is running thecorrect firmware release.

Beginning with , the -r option (no automatic reboot) is the default for the software updatecommand.

Note: However, when you first upgrade to Data ONTAP or a later release in the family, you mustto specify the -r option for nondisruptive upgrades. In subsequent major and minor nondisruptiveupgrades, it will longer be required to specify the option.

If you use upgrade images to upgrade to Data ONTAP 8.0.1 7-Mode or laterYou must obtain Data ONTAP upgrade images from the NOW site and copy them to your storagesystem. Media kits, including CD-ROMs with upgrade images, are no longer available, and theprocess of installing upgrade images from UNIX or Windows clients is no longer supported.

Beginning with Data ONTAP 8.0.1 7-Mode, media kits including CD-ROMs are no longer available.You must obtain upgrade images from the NOW site and copy them to your storage system or to anHTTP server in your environment.

Beginning with Data ONTAP 8.0.1 7-Mode, the following processes are no longer supported forextracting and installing Data ONTAP upgrade images:

• Using the tar command from UNIX clients• Using the setup.exe file and WinZip from Windows clients

For the upgrade to Data ONTAP 8.0.1 7-Mode and later releases, .exe images are no longeravailable. You must use one of the following image types depending on the upgrade you areperforming:

• .zip images, for upgrades from an earlier release family to Data ONTAP 8.0.1 7-Mode• .tgz images, for upgrades from any Data ONTAP 8.0.1 7-Mode release to a later release

After you have upgraded to Data ONTAP 8.0.1 7-Mode or later, you can only use .tgz images forfurther upgrades.

After you have copied the .zip or .tgz image to your storage system, you can install it with thesoftware update command. Alternatively, you can make the .zip or .tgz image available from anHTTP server in your environment, then use the software update command to copy the upgrade

Important cautions | 61

image from the HTTP server, extract and install the system files, and download the files to the bootdevice with one command.

For more information about upgrade images, see the Data ONTAP 8.0 7-Mode Upgrade Guide.

If you are updating a system with AT-FCX disk shelves attachedIf your AT-FCX disk shelf is running firmware version 37 or later, you can perform firmwareupdates to that shelf without causing a pause in I/O operations from that shelf. However, theshelf.fw.ndu.enable option must be set to on.

In some earlier Data ONTAP versions before nondisruptive AT-FCX firmware upgrades weresupported, the shelf.fw.ndu.enable option was set to off by default. Because of a knownproblem in later releases, the option is not automatically set to on during Data ONTAP upgrades,even when nondisruptive shelf firmware upgrades are supported in the later version.

Therefore, before performing a nondisruptive upgrade to your AT-FCX shelf firmware, you shouldensure that the shelf.fw.ndu.enable option is set to on.

Note: If you are planning to use the nondisruptive method (NDU) to upgrade to Data ONTAP 8.07-Mode, you must update shelf firmware to the latest version before upgrading Data ONTAP.

Related information

Bug ID 396599: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=396599

If you are upgrading a FAS3050 systemAs of Data ONTAP 7.3.3, the threshold limits for the NVRAM5 battery sensor have changed for theFAS3050 systems. Before initiating an upgrade to Data ONTAP 7.3.3 or later, you must ensure thatthe NVRAM5 battery sensor reading for your FAS3050 system is within the new threshold limits.

About this task

The following are the new threshold limits for the FAS3050 NVRAM5 battery sensor:

• Critical low: 3649 mV• Warning low: 3849 mV• Warning high: 4250 mV• Critical high: 4250 mV

If the current NVRAM5 battery sensor reading is not between 3849 mV (warning low) and 4250 mV(warning high), the system will fail to boot the new image during the nondisruptive upgrade to DataONTAP 7.3.3 or later.

Steps

1. To display the current sensor state, reading, and threshold limits for all sensors, including thesensor information for the NVRAM5 battery, enter the following command:

62 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

environment head list-sensors

ExampleThe following example shows the NVRAM5 battery sensor output from a FAS3050 system:

system> environment head list-sensors

Sensor Name State Current Critical Warning Warning Critical Reading Low Low High High--------------------------------------------------------------------------------[...]NVRAM5-battery-3 normal 4014 mV 1450 mV 2350 mV 4300 mV 4400 mV [...]

Note: The NVRAM5 battery sensor state might show normal even if the reading does notconform to the new threshold limits.

2. If the current reading of the NVRAM5 battery sensor is not between 3849 mV (warning low) and4250 mV (warning high), perform one of the following steps:

• If the current NVRAM5 battery reading is lower than 3849 mV, allow the charge on thebattery to reach full voltage before proceeding with the upgrade.

• If the battery is faulty, replace the battery before proceeding with the upgrade.

Systems including DS14 shelves, ESH modules or LRC modulesBeginning 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 willresult in an unsupported configuration. If even one of these devices is attached to your storagesystem, 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. Thismeans 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 besupported:

• 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 includesthe obsolete DS14mk1, ESH, or LRC storage hardware, you should contact your NetApprepresentative to discuss upgrading to the latest DS14mk4 disk shelf with ESH4 storage I/O modules.

Important cautions | 63

Upgrading FAS3140/FAS3170 systemsIf you are running iSCSI traffic on your FAS3140/FAS3170 system and you are upgrading from DataONTAP version 7.3 or earlier to version 8.0, you will no longer be able to run iSCSI traffic on thee0M and e0P interfaces.

About this task

In addition, if you revert from Data ONTAP version 8.0, the e0M and e0P interfaces remain disabledfor 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 379056 in Bugs Online. If changes do occurto target portal group configurations after upgrade, refer to the Public Report in bug 379056 forinformation about how to solve the problems.

Related information

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

Do not remove the special system files that are for restoring LUNs insnapshot copies

For storage systems upgraded from a release earlier than Data ONTAP 8.0, some system files exist inevery volume of the system. You must not remove or modify these files unless technical supportdirects you to do so. These files enable you to restore LUNs in Snapshot copies if you revert to arelease 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

If you are upgrading to Data ONTAP 8.0.1 7-Mode or later from a releaseearlier than Data ONTAP 7.3

Upgrading to Data ONTAP 8.0.1 7-Mode or later from a release earlier than Data ONTAP 7.3 willcause 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 FlexVolvolumes 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 most96 percent used space in their aggregates. If there is insufficient free space in an aggregate tosatisfy the increased requirement from its FlexVol volumes, the space guarantee for one or morevolumes in that aggregate could be disabled.

64 | Data ONTAP 8.0.1 7-Mode RC3 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.3or 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 ormore, do not proceed with the upgrade until you have used the Upgrade Advisor or aggrSpaceChecktools 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... Then...

96% or less for all aggregates You can proceed with your upgrade to Data ONTAP 7.3; no further actionis 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 yourenvironment.

If your system is... Then continue to plan your upgrade withthe...

Configured to send AutoSupport messages to NetApp Upgrade Advisor tool.

Not configured to send AutoSupport messages toNetApp

aggrSpaceCheck tool.

These tools can assess the free space requirements for your system in Data ONTAP 7.3 and laterreleases. If you do not have sufficient free space, the tools will recommend a course of action toensure a successful upgrade.

Note: The Upgrade Advisor can also assess other upgrade requirements and recommendsolutions. Using it is the recommended upgrade methodology.

After you finish

After using these tools and completing the upgrade, make sure that your space guarantees areconfigured according to your requirements.

Important cautions | 65

If your root FlexVol volume does not meet the new size requirementsThe minimum required size for root FlexVol volumes has been increased for every system runningthe Data ONTAP 8.0 release family. If your root FlexVol volume does not meet the newrequirements, 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 systemproblem occurs, these files are needed to provide technical support.

For more information about root volumes and the root FlexVol volume requirements for yourplatform, see the Data ONTAP 7-Mode System Administration Guide.

If you are performing a nondisruptive upgrade on a system with VMwareESX Server hosts

Before performing a nondisruptive upgrade on storage systems exporting data over NFS to VMwareESX 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 servicedisruption 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) onWindows be correctly aligned with the storage systems' WAFL file system.

For more information about verifying and updating these configurations, see the Data ONTAP 7-Mode Upgrade Guide.

If you are upgrading a system that includes deduplicated volumesYou can perform major and minor nondisruptive upgrades when deduplication is enabled, providedthat no more than 300 FlexVol volumes have deduplication enabled and that no deduplicationoperations are running during the Data ONTAP upgrade.

For information about deduplication, see the Data ONTAP 7-Mode Storage Management Guide andthe sis(1) man page.

If your system uses rtc or rdate as the protocol for time synchronizationStarting with Data ONTAP 8.0 7-Mode, the Network Time Protocol (NTP) protocol is the onlysupported protocol for time synchronization. The rtc and the rdate protocols of the timed.protooption 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 timeafter you upgrade it to Data ONTAP 8.0 7-Mode or later. Problems can occur when the storagesystem clock is inaccurate.

66 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

If your system does not already use NTP as the protocol for time synchronization, immediately afterupgrading to Data ONTAP 8.0 7-Mode or later you must set timed.proto to ntp, settimed.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 arelease prior to Data ONTAP 8.0 7-Mode.

For information about how to synchronize the system time, see the Data ONTAP 7-Mode SystemAdministration Guide.

If you modify the timed options and then revert to a release prior to DataONTAP 8.0 7-Mode

Starting with Data ONTAP 8.0, several timed options are obsolete although they remain visible inthe CLI and can be modified.

The following timed options have no effect in Data ONTAP 8.0 7-Mode or later:

• The timed.max_skew option• The timed.sched option• The timed.window option• The rtc and the rdate protocols of the timed.proto option

If you attempt to set the above options when the system is running Data ONTAP 8.0 7-Mode or later,they will have no effect. However, these settings will take effect after the system is reverted back to arelease that supports the options.

If you have been using the flex_cache licenseYou should install the flexcache_nfs license before upgrading to this release of Data ONTAP. Ifyou do not install the flexcache_nfs license, your FlexCache volumes will not work until youinstall the license.

If you are reverting to a Data ONTAP release with a lower maximumcapacity

When you revert to an earlier Data ONTAP release, your storage system must conform to themaximum capacity limitations of the earlier release.

If you upgraded your system to a release that supports greater capacities and you configured storageto utilize the new capacities, you must reconfigure your system to the lower capacity limits beforeyou revert. If you don't reconfigure in this way, the storage system will not boot up following therevert process until the excess capacity has been disconnected.

You can reduce the total capacity of your system by destroying aggregates or by moving aggregatesto a different system. The system to which storage is relocated must meet the followingrequirements:

• It has spare capacity to accommodate the relocated storage.

Important cautions | 67

• It is running the same or a later Data ONTAP release as the system where the disks are currentlyinstalled.

• 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 StorageManagement Guide.

For more information about maximum capacity limits for a given Data ONTAP release, see theSystem 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 deduplicationIn 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 previousrelease 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 operationsperformed earlier. However, the new data written to the volume after the revert process will obtainspace savings through deduplication within the new data only, and not from the data that existedbefore the revert process.

To use deduplication for all the data within the volume, and thus obtain higher space savings, use thesis start -s command. This command rebuilds the deduplication metadata for all the data in thevolume. This process can take several days, depending on the size of the logical data in the volume.

Attention: Before using the sis start -s command, ensure that the volume has sufficient freespace to accommodate the addition of the deduplication metadata. The deduplication metadatauses between 4 and 6 percent of the logical data size in the volume.

Block access protocol cautionsIf your storage system is deployed in a SAN environment, you should review these issues and takeappropriate action before upgrading or reinstalling.

For more information about these issues, see the Data ONTAP 7-Mode Block Access ManagementGuide for iSCSI and FC.

Next topics

Identical WWPNs can occur on both nodes in a cluster on page 69

If you deploy ALUA on storage systems with FCP or iSCSI on page 69

If you use Solaris 10 and the emlxs Fibre Channel Adapter driver on page 69

cfmode support change in Data ONTAP 8.0 on page 69

68 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Identical WWPNs can occur on both nodes in a clusterIf a system and its disks are disconnected from its partner and then connected to a different partner, itis 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 secondarysystems, causing each system to compute identical WWPNs for its target ports. As a result, hosts willexperience 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 268320in Bugs Online, or see KB 35532.

If you deploy ALUA on storage systems with FCP or iSCSIIf you deploy the T10 Asymmetric Logical Unit Access (ALUA) standard for SCSI on FibreChannel-enabled storage systems or iSCSI-enabled storage systems, ensure that your hosts supportALUA before enabling ALUA. Enabling ALUA for a host that does not support ALUA can causehost failures during cluster failover.

Check the appropriate host compatibility matrix on the Compatibility and Configuration Guide forNetApp FCP and iSCSI Products page on the NOW site to see if ALUA is supported on your hostsystem.

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 driverIf you are using Solaris 10 and the emlxs Fibre Channel Adapter driver, you need to upgrade to the2.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.0For Fibre Channel SAN configurations in Data ONTAP 8.0 and later releases, only single_imagecfmode (cluster failover mode) is supported. If you are upgrading high-availability FC SAN systemsfrom an earlier release and they are configured for any other cfmode, you must migrate them tosingle_image mode before upgrading to Data ONTAP 8.0 or later.

For detailed instructions about migrating to single_image mode, see Changing the Cluster cfmodeSetting 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/

Important cautions | 69

Data protection cautionsIf your storage system is configured with licenses for data protection technologies, you should reviewthese issues and take appropriate action before upgrading or reinstalling.

For more information about these issues, see the Data ONTAP 7-Mode Data Protection OnlineBackup and Recovery Guide.

Next topicsNetApp SnapValidator for Oracle not supported on page 70SnapLock is not supported on page 70

NetApp SnapValidator for Oracle not supportedNetApp SnapValidator for Oracle is not supported in Data ONTAP 8.0 7-Mode and later DataONTAP 8.0.x 7-Mode releases. For more information, contact NetApp technical support.

SnapLock is not supportedSnapLock is not supported in Data ONTAP 8.0.1 7-Mode. A storage system halts if it containsSnapLock volumes and is upgraded to Data ONTAP 8.0.1 7-Mode. Therefore, if you are runningSnapLock on your current release of Data ONTAP, you should not upgrade to Data ONTAP 8.0.1 7-Mode.

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 youwill see a snaplock license is required message:

• vol create -L• aggr create -L• date -c• date -c initialize

Download of Data ONTAP 8.0.1 7-Mode on storage systems with SnapLock volume

In some versions of Data ONTAP 7.2.x and Data ONTAP 7.3.x with SnapLock volumes, you mightbe able to download Data ONTAP 8.0.1. However, because Data ONTAP 8.0.1 does not support theSnapLock feature, your storage system will halt when you reboot it with Data ONTAP 8.0.1.

Following is an example of an error message displayed on the storage system console:

Found SnapLock disk:v5.29 Use fcadmin device_map for shelf andslot info This release does not support SnapLock.Remove theSnapLock disks from this system.Found SnapLock disk: v5.32 Use fcadmin device_map for shelf and slot infoThis release does not support SnapLock.Remove the SnapLock disks fromthis system This release does not support SnapLock.Halting the system!!!

70 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

To recover-boot with a release that supports SnapLock or unplug theSnapLock disks.

In such a scenario, contact technical support immediately.

Manageability cautionsIf you are a storage system administrator, you should familiarize yourself with these manageabilityissues.

For more information about these cautions, see the Data ONTAP 7-Mode System AdministrationGuide.

Next topics

If you need to boot the storage system from a Data ONTAP image stored on a remoteserver on page 71

TLS is not supported in the Data ONTAP 8.0 release family on page 71

RLM over IPv6 not supported in the Data ONTAP 8.0 release family on page 71

New RLM firmware and its upgrade requirements on page 72

If you need to boot the storage system from a Data ONTAP image stored ona remote server

In the Data ONTAP 8.0 release family, netboot is not a supported function, unless you are restoringthe Data ONTAP image on the boot device, such as a PC CompactFlash card. If you need to boot thestorage 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 onthe card, see the Replacing a CompactFlash Card flyer that is applicable to your version of DataONTAP.

TLS is not supported in the Data ONTAP 8.0 release familyTransport 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 runthe 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 familyIf 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 notsupported in the Data ONTAP 8.0 release family.

If your RLM configuration does not include static IPv4 or DHCP IPv4 , you need to reconfigure theRLM by using the rlm setup command after upgrading to the Data ONTAP 8.0 release family.

Important cautions | 71

For information about the RLM, see the Data ONTAP 7-Mode System Administration Guide.

New RLM firmware and its upgrade requirementsRLM firmware versions 4.0 and later require a different layout on flash media. You must ensure thatyou are running the latest 3.1.x RLM firmware to enable the transition to the new layout, then updateto 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 earlierthan 3.1, you must first perform an intermediate update to the latest 3.1.x firmware, then update from3.1 to 4.0 in a separate operation.

Attention: Regardless of whether you update RLM firmware from the Data ONTAP CLI or theRLM CLI, do not update directly from a firmware version earlier than 3.1 to 4.0 or later. Doing sowill 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, youmust run the rlm update command with the -f option for a full image update. Further updates donot 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-ModeUpgrade Guide.

For information about configuring the RLM, see the Data ONTAP 7-Mode System AdministrationGuide.

Network protocol cautionsIf 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 73

IPsec is not supported on page 73

TOE is not supported on page 73

72 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

IPv6 is not supportedIPv6 is not supported in Data ONTAP 8.0 and later. If you want to upgrade from a Data ONTAPversion that supports IPv6 to Data ONTAP 8.0 or later, see the Data ONTAP 7-Mode UpgradeGuide.

IPsec is not supportedIPsec is not supported in Data ONTAP 8.0 and later. If IPsec is enabled on your storage system, beaware that it will be disabled automatically during the upgrade to the Data ONTAP 8.0 releasefamily.

TOE is not supportedIn Data ONTAP 8.0 7-Mode and later Data ONTAP 8.0.x 7-Mode releases, the TOE functionality isnot supported. There is no adverse effect on the performance of your storage system because TOE isdisabled.

Important cautions | 73

Known problems and limitations

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds toavoid these behaviors, have been identified in this release.

To request more information about an individual bug and to explore other bug-related tools, see BugsOnline on the NOW site.

Next topics

Manageability issues on page 75

Network protocol issues on page 76

File access protocol issues on page 77

Block access protocol issues on page 78

Data protection issues on page 81

Storage resource management issues on page 85

Third-party storage issues (V-Series systems only) on page 87

HA pair issues on page 88

Related information

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

Manageability issuesYou 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 75

Issues regarding the EMS timed log on page 76

Shutdown delay in FAS2040 systems when critical thresholds are crossed on page 76

RLM configuration is not saved if the RLM's Ethernet cable is notconnected

If the RLM's Ethernet cable is not connected when you use the rlm setup command to configurethe RLM, after connecting the cable you must rerun rlm setup.

Known problems and limitations | 75

Issues regarding the EMS timed logThe NTP Daemon automatically adjusts the storage system time to keep the system clock in syncwith the specified NTP server. However, due to a regression effect, EMS does not log the timeadjustments even when the timed.log option is set to on.

Shutdown delay in FAS2040 systems when critical thresholds are crossedIn FAS2040 systems running Data ONTAP 8.0.1, after an a critical temperature or voltage thresholdhas been crossed, there is a two-minute delay before the system shuts down. The purpose of the delayis to provide enough time for AutoSupport messages to be delivered.

There is no shutdown delay if three or more fans fail.

If the system is running a heavy load or if the network is slow, the AutoSupport message might notbe delivered. However, EMS messages report that thresholds have been crossed, regardless ofwhether an AutoSupport message is delivered.

Network protocol issuesIf 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 76

Entries in the NIS group file should not exceed 1024 characters on page 76

Enable caching with NIS lookupIf you use NIS for group lookup services, disabling NIS group caching can severely degradeperformance.

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 couldlead to timeouts as CIFS clients attempt authentication.

Entries in the NIS group file should not exceed 1024 charactersData ONTAP supports a maximum of 1024 characters per line in the /etc/group file on the NISserver. 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 exceed1024 characters.

For more information, see Bug ID 19563 in Bugs Online.

76 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Related information

http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=19563

File access protocol issuesIf your storage systems provide CIFS, NFS, or FTP client services, you might need to familiarizeyourself with file access protocol issues.

For more information about these issues, see the Data ONTAP 7-Mode File Access and ProtocolsManagement Guide.

Next topics

Client notification messages in Windows domains require NetBIOS on page 77

Configuration issue for clients that mount NFS shares using a non-reserved port on page 77

CIFS termination required before issuing a lock break on page 78

Mac clients cannot access CIFS shares using widelinks on page 78

Client notification messages in Windows domains require NetBIOSThe Windows client notification feature used for client messaging, shutdown notices, and vscanalerts requires NetBIOS over TCP to be enabled in Data ONTAP.

Similarly, NetBIOS over TCP must be enabled on Windows clients and the Windows Messengerservice must be running.

By default, the Windows Messenger service is disabled on Windows 2003 and Windows XP SP2clients.

Configuration issue for clients that mount NFS shares using a non-reserved port

The nfs.mount_rootonly option should be set to off on a storage system that must supportclients 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 reservedports (that is, ports with numbers lower than 1024) to mount the NFS shares.

Known problems and limitations | 77

CIFS termination required before issuing a lock breakYou must terminate CIFS or at least the CIFS session corresponding to the lock before issuing a lockbreak to avoid a potential system panic. The lock break command now displays a warning toremind you to terminate CIFS first.

Mac clients cannot access CIFS shares using widelinksAccessing CIFS shares using widelinks does not work from Mac clients.

Block access protocol issuesIf your storage systems are part of a SAN environment, you might need to familiarize yourself withblock access protocol issues in this release.

For more information about these issues, see the Data ONTAP 7-Mode Block Access ManagementGuide for iSCSI and FC.

Next topics

Brocade 200E switch speed must be set manually on page 78

Disks offline in Windows 2008 after a standard upgrade on page 79

iSCSI Target HBA support on page 79

If an iSCSI target HBA fails on page 79

If you use the automatic sizing feature on thinly provisioned LUNs when snap reserve is set to anon-zero value on page 80

Brocade 200E switch speed must be set manuallyWhen set with link speed auto-negotiation, Brocade 200E switches do not always attain maximumexpected connection speeds with attached devices.

By default, both Brocade 200E (4 Gbps) switch ports and QLogic host bus adapters (HBAs) are setto negotiate connection link speeds automatically. However, link speed auto-negotiation between200E Switch ports and QLogic HBAs might not always result in the maximum expected connectionspeed, thus degrading performance. As an example, an expected 4-Gbps link might only carry trafficat 2 Gbps.

To avoid this problem, do not use the link speed auto-negotiation feature on the Brocade 200Eswitch. Instead, manually set individual 200E switch ports at the desired maximum link speed thatmatches the speed capability of the connected device.

Note: This problem might also affect connections between Brocade 200E switches and otherdevices, such as Fibre Channel adapters and disk shelves. For this reason, you should manually setthe Brocade 200E switch speed for connections to all devices.

78 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Related information

Bug ID 245884: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=245884

Setting Brocade 200E switch speed manually

You can use the Brocade switch console interface to configure link speed settings.

Steps

1. Enter the following command at the switch console to manually set the speed:

portCfgSpeed port_number speed_level

2. Enter the following command at the switch console to verify the link speed:

switchshow

Disks offline in Windows 2008 after a standard upgradeDuring a standard upgrade to Data ONTAP 7.3.3 and later releases, LUNs are assigned new revisionnumbers. Windows Server 2008 software interprets the LUNs with new revision numbers as newdisks and sets them offline; this status is shown in Windows 2008 management interfaces after theupgrade. Windows Server 2003 ignores the LUN revision number.

You can work around this problem using the nondisruptive upgrade method, which allows the LUNsto maintain their revision numbers. You can also bring the disks online after the upgrade usingWindows disk management tools or SnapDrive functionality.

For more information, see the knowledgebase article Disks show as offline in Windows 2008 afterData 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 supportSome storage systems support the use of an iSCSI target HBA, which contains special networkinterfaces that offload part of the iSCSI protocol processing. You cannot combine these iSCSIhardware-accelerated interfaces with standard iSCSI storage system interfaces in the same targetportal group.

If you attempt to combine these interfaces, an error message is displayed.

If an iSCSI target HBA failsIf your iSCSI target HBA fails, the iSCSI initiators connected to this HBA might time out, promptingthe 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, ordevice driver defects.

Known problems and limitations | 79

Note: If MPIO is configured on the hosts, I/O should be re-routed as expected, preventing anydisruption 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 whensnap 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 theseinstances, you must use the automatic sizing feature for thinly provisioned LUNs in FlexVol volumesto work properly.

About this task

Using the automatic sizing feature is required because the space from deleted Snapshot copies canonly be used to fulfill Snapshot space requests. Furthermore, the automatic deletion process will notbegin 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 maximumsize, and if there is space available in its containing aggregate, the FlexVol volume's size willincrease by the specified increment.

80 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Data protection issuesIf you use data protection products that include Snapshot technology (such as SnapRestore,SnapVault, SnapMirror, and SnapManager), you might have to familiarize yourself with relevantdata protection issues.

For more information about these issues, see the Data ONTAP 7-Mode Data Protection OnlineBackup and Recovery Guide and the Data ONTAP 7-Mode Data Protection Tape Backup andRecovery Guide.

Next topics

Tape backup and volume move operations must not be performed simultaneously on page 81

SMTape restore to an offline volume overwrites the data on that volume on page 81

Deleted files occupy additional space on SMTape restored volumes on page 82

Limitations when using SnapVault with nondefault vFiler units on page 82

Restore engine does not honor any mandatory or advisory locks on files on page 83

Restore operation to a non-existent volume restores data to the root volume on page 83

Shutting down a storage system when SMTape operations are active might result in apanic on page 83

Suboptimal space savings with deduplication when 16 GB Performance Acceleration Module isinstalled on page 83

If you use DataFabric Manager to manage SnapMirror or SnapVault relationships between vFilerunits on page 84

Creating more than 64 mirrored aggregates might impair disaster recovery on page 84

Tape backup and volume move operations must not be performedsimultaneously

You must not perform a tape backup or restore operation while a volume move operation is incutover phase. Similarly, you must not perform a volume move operation while a tape backup orrestore is in progress. You should wait until one of the operations is complete before initiating theother.

For more information about volume move operation, see Data ONTAP 7-Mode Block AccessManagement Guide for iSCSI and FC.

SMTape restore to an offline volume overwrites the data on that volumeIf you perform an SMTape restore to an offline volume, the data on tape overwrites the data on thatoffline volume.

Known problems and limitations | 81

Deleted files occupy additional space on SMTape restored volumesOn an SMTape restored volume, a Snapshot copy might lock the data blocks of a deleted file, thusoccupying additional space on the restored volume.

When you delete a large file from a volume, the data blocks of that file are not freed immediately. Ifyou perform an SMTape backup immediately after deleting the file, some data blocks of the deletedfile are also backed up. After restore, those data blocks reside on the volume and are locked in theSnapshot copy.

To free the space on the restored volume, delete the Snapshot copy that locked the data blocks of thedeleted file.

Limitations when using SnapVault with nondefault vFiler unitsThere are certain limitations when using SnapVault with nondefault vFiler units. These limitationsapply to all Data ONTAP releases that support nondefault vFiler units.

The management of SnapVault secondary (creation or modification of SnapVault relationships andschedules at the SnapVault secondary) is only supported from the default vFiler unit (vfiler0). Themanagement of SnapVault secondary is not supported from a nondefault vFiler context. If thevolume containing the SnapVault destination qtree is owned by a nondefault vFiler unit, theSnapVault 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 secondaryvolume

Ownership of SnapVault secondary volume

Default vFiler unit (vfiler0) Nondefault vFiler unit

Default vFiler unit (vfiler0) Yes Yes

Nondefault vFiler unit No 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 primaryvolume

Ownership of SnapVault primary volume

Default vFiler unit (vfiler0) Nondefault vFiler unit

Default vFiler unit (vfiler0) Yes Yes

82 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Management of SnapVault primaryvolume

Ownership of SnapVault primary volume

Nondefault vFiler unit

No Yes

(From a nondefault vFilercontext, you can only manage

volumes owned by thatnondefault vFiler unit.)

DataFabric Manager support for the management of SnapVault relationships

DataFabric Manager supports the management of SnapVault relationships for volumes through thedefault vFiler (vFiler0) context only. When using DataFabric Manager, the following limitationsapply 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 filesThe 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 rootvolume

If the destination of your restore operation is a non-existent volume, data is restored to the rootvolume.

Shutting down a storage system when SMTape operations are active mightresult in a panic

If you shut down a storage system that has currently active SMTape operations, it might result in apanic.

You must ensure to abort all the active SMTape operations using the smtape abort commandbefore shutting down the storage system.

Suboptimal space savings with deduplication when 16 GB PerformanceAcceleration Module is installed

When you run a deduplication scan by using the sis start -s command on a volume withexisting data and with the 16-GB Performance Acceleration Module installed, you obtain suboptimalspace savings.

Known problems and limitations | 83

If you use DataFabric Manager to manage SnapMirror or SnapVaultrelationships between vFiler units

For Data ONTAP 7.2 and later, SnapMirror and SnapVault relationships can be created using vFilerunits. However, DataFabric Manager 3.4 and earlier releases cannot use vFiler units for managingSnapMirror 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 accessonly to the destination vFiler unit, then the relationship creation, scheduled backups, on-demandbackups, 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 thesnapmirror.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 errormessage source unknown. This occurs when both of these conditions are met:

• A relationship between two vFiler units is imported into DataFabric Manager by auto-discovery or is added manually.

• The destination hosting system is not able to contact the source vFiler IP address.

Workaround: Ensure that the host name or IP address of the source system that is used to createrelationships can be reached from the destination hosting system.

Related information

Bug ID 191367: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=191367

Creating more than 64 mirrored aggregates might impair disaster recoveryIf you create more than 64 mirrored or SyncMirror aggregates per storage system (or per node in amirrored cluster or MetroCluster), an out-of-date plex might be brought back online after some typesof failures.

To avoid bringing an out-of-date plex back online, do not create more than 64 mirrored aggregatesper system, even though Data ONTAP does not prevent you from doing so.

84 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Storage resource management issuesIf you have more than one size of disk installed in your storage system, if you have configuredquotas, if you use FlexCache volumes, or if you are using FlexVol volumes on FAS250 systems, youshould familiarize yourself with these storage resource management issues.

Next topics

Attempting to assign more than 500 disks or array LUNs with a single disk assign commandcauses a system panic on page 85

Moving disks to a system running an earlier version of Data ONTAP could cause diskidentification issues on page 85

Data ONTAP can silently select varying disk or array LUN sizes when creating anaggregate on page 86

SSD Spare blocks consumed limit reported as "N/A" on page 87

Forcing a FlexVol volume online must be done in diag mode on page 87

Attempting to assign more than 500 disks or array LUNs with a single diskassign command causes a system panic

You can use the all keyword or wildcards to operate on multiple disks or array LUNs when you usethe disk assign command. However, if the disk assign command designates more than 500disks or array LUNs, the system will panic.

Moving disks to a system running an earlier version of Data ONTAP couldcause disk identification issues

If you remove a disk from a storage system running Data ONTAP 7.3 or later and place it into astorage system running a version of Data ONTAP earlier than 7.3, the software disk ownershipinformation will be incorrect for the earlier version and might prevent Data ONTAP from identifyingor correctly assigning the disk.

The disk identification issues cannot be solved except by returning the disk to the original storagesystem and removing the software disk ownership information using the more recent version of DataONTAP.

To avoid causing disk identification issues, always use the recommended procedure for removing adata disk, which includes removing the software disk ownership information from the disk beforeremoving 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 movea disk from a V-Series system to a V-Series system running a version of Data ONTAP earlier than7.3.

Known problems and limitations | 85

Data ONTAP can silently select varying disk or array LUN sizes whencreating an aggregate

If disks or array LUNs of varying size are present in your storage system, relying on automatic diskselection 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 selectsdisks or array LUNs based on various criteria including size, speed, and checksum type. To ensurethat the disks or array LUNs selected are the size you want, specify the disk or array LUN size whencreating 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 86

Discovering what disks Data ONTAP will automatically select on page 86

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 oradding 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

ExampleFor 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 addcommand.

About this task

When you use the -n option, the disks that would be selected automatically, if you created anaggregate or added to an aggregate, are displayed. The creation or addition is not performed. If theselected disks are not what you intended, you can specify a disk list when you enter the aggrcreate or aggr add command.

86 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Step

1. To list the disks that would be selected for an aggr create command, enter the followingcommand:

aggr create aggr_name -n disk_list

ExampleFor example, to list the disks that would be used for the creation of the newaggr aggregate usingeight automatically selected disks, enter the following command:

aggr create newaggr -n 8

SSD Spare blocks consumed limit reported as "N/A"When Data ONTAP reports status information for SSDs, the Spare blocks consumed limit value isdisplayed as "N/A." The spare blocks consumed limit for currently shipping SSDs is 90%.

Forcing a FlexVol volume online must be done in diag modeIf you need to issue the vol online -f command to force a FlexVol volume online, you must usethe diag privilege level to do so.

Third-party storage issues (V-Series systems only)When Data ONTAP uses third-party storage, issues can occur with the switches and storage arrays inthe configuration.

Next topics

Limitation on EMC CX storage array LUN numbering on page 87

Exceeding the maximum number of assigned devices results in a panic on page 88

Limitation on EMC CX storage array LUN numberingIf you are not using Storage Groups on your CX storage array, do not assign LUN numbers greaterthan 254 to array LUNs for V-Series.

If you are not using Storage Groups, the CX storage array might not present internal LUN numbersgreater than 254 to your V-Series system. If this occurred, V-Series would not be able to see thosearray LUNs.

If you are using Storage Groups, the CX storage array automatically assigns internal LUN numberslower than 255.

Known problems and limitations | 87

Exceeding the maximum number of assigned devices results in a panicIf more than 256 array LUNs from a specific storage array target port to a specific V-Series FCinitiator 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 initiatorport should be assigned (in the Data ONTAP configuration) to a V-Series system. This is a DataONTAP limitation. If more than 256 LUNs from the same storage array port to the same V-Series FCinitiator port are assigned to the V-Series system, the V-Series system panics if you try to boot it andissues a message similar to the following:

PANIC: ../common/raidv2/pool_sort.c:2359: Assertion failure. in SK processconfig_thread on release NetApp Release 7.3.2

If you assigned more than 256 LUNs from the same storage array target port to the V-Series system,you must remove ownership of enough of the array LUNs so that no more than 256 array LUNs fromthe same target port to the same V-Series FC initiator are assigned to the V-Series system.

HA pair issuesIf you are using the cf.takeover.on_network_interface_failure option, you might need tofamiliarize yourself with this HA pair issues.

For more information about these issues, see the Data ONTAP 7-Mode High-AvailabilityConfiguration Guide.

Next topics

Do not disable the IP fastpath option on a 32xx system in an HA pair on page 88

Incorrect warning of termination in spite of a successful giveback on page 89

The ifconfig command and the FAS2040 e0P port on page 89

If takeover is enabled for network interface failure, automatic giveback should bedisabled on page 89

Do not disable the IP fastpath option on a 32xx system in an HA pairDo not disable the ip.fastpath.enable option on any 32xx system in an HA pair. This option is on bydefault.

If you disable the option by setting it to off, the HA interconnect between the nodes in the pair fails,because the iWARP protocol used by the interconnect cannot establish a multicast route without thefast path mechanism. If you have disabled the option and have encountered this problem, you can usethe options ip.fastpath.enable oncommand to renable the fast path.

88 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Incorrect warning of termination in spite of a successful givebackOn systems running Data ONTAP 8.0 7-Mode, the cf giveback command may, despite asuccessful giveback, produce an EMS warning that the giveback terminated because the partner nodedid 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 portDo not use the ifconfig command to configure the e0P port on a FAS2040 system. This port is usedto implement the Disk Shelf Alternate Control Path network only and is configured automatically.

If takeover is enabled for network interface failure, automatic givebackshould be disabled

If you set the cf.takeover.on_network_interface_failure option to on to enable automaticfailover on network interface failures, ensure that you have the cf.giveback.auto.enable optionset to off.

If the cf.giveback.auto.enable option is set to on, a network interface failure could result in acontinuous series of takeovers and givebacks until the network interface problem is resolved.

Known problems and limitations | 89

Changes to published documentation

Some information about this release has become available after the set of guides provided with thisrelease were published. The information should be used in conjunction with the guides provided withthis release of Data ONTAP.

Next topics

Changes to the Data Protection Tape Backup and Recovery Guide on page 91

Changes to the Storage Management Guide on page 92

Changes to the File Access and Protocols Management Guide on page 92

Changes to the Block Access Management Guide for iSCSI and FC on page 94

Changes to the Data Protection Tape Backup and RecoveryGuide

Some additional information about tape backup features has become available since the previousrevision of the Data ONTAP 7-Mode Data Protection Tape Backup and Recovery Guide.

Designating range of ports for NDMP data connectionsData ONTAP 8.0.1 supports designated range of ports that can be used for NDMP data connectionsin response to NDMP_DATA_LISTEN and NDMP_MOVER_LISTEN operations.

About this task

Data ONTAP 8.0 7-Mode and earlier versions do not support data migration by using ndmpcopycommand and 3-way tape backups in environments where the source and destination networks areseparated by a firewall. This is because the data or mover port that is used in a data transfer isunpredictable.

Starting with Data ONTAP 8.0.1, administrators can designate range of ports that can be used forNDMP data connections in response to NDMP_DATA_LISTEN and NDMP_MOVER_LISTENoperations. Therefore, Data ONTAP 8.0.1 enables you to perform data migration by using ndmpcopycommand and 3-way tape backups even in environments where the source and destination networksare separated by a firewall.

Step

1. To enable the data port range, enter the following command:

options ndmpd.data_port_range {start_port-end_port}

Changes to published documentation | 91

The ndmpd.data_port_range option allows administrators to specify a port range on whichthe NDMP server can listen for data connections.

The start_port and end_port indicate the range of ports designated for data connection andcan have values between 1024 and 65535; start_port must be less than or equal to end_port.

If a valid range is specified, NDMP uses a port within that range to listen for incoming dataconnections. A listen request fails if no ports in the specified range are free.

The default value for ndmpd.data_port_range option is all. The all implies that anyavailable port can be used to listen for data connections.

Note: The ndmpd.data_port_range option is persistent across reboots.

Example

Filer1> options ndmpd.data_port_range 1024-2048

Changes to the Storage Management GuideNew information has become available since the previous revision of the Storage ManagementGuide.

Incorrect root FlexVol volume size requirement for 3160 systemsThe size requirement for root FlexVol volumes section in the Data ONTAP Storage ManagementGuide contains an incorrect root FlexVol volume size requirement for 3160 systems. The minimumsize for the root FlexVol volume for 3160 systems should be 240 GB.

Changes to the File Access and Protocols ManagementGuide

The Data ONTAP 7-Mode File Access and Protocols Management Guide should have included thefollowing topics.

Next topics

Unsupported Windows features in the file serving environment on page 93

NFSv4 client compatibility on page 93

The file fingerprint command can be used for all data files in Data ONTAP 8.0.1 7-Mode on page 93

92 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Unsupported Windows features in the file serving environmentThis 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 compatibilityWhen your NFSv4 clients are in a different domain than your NetApp device is in, you might need toenter the client domain name as the value for the Data ONTAP option nfs.v4.id.domain in orderto provide mapping for file ownership and group membership.

For more information about mapping options, see RFC 3530 and your client operating systemdocumentation.

If you have any client using NFSv4 that needs to access a storage system, ensure that the DataONTAP option nfs.v4.enable is set to on. In new installations, this option is set to off bydefault.

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 placeof Unicode characters.

Related information

Bug ID 71627: now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=71627

The file fingerprint command can be used for all data files in Data ONTAP8.0.1 7-Mode

A fingerprint enables you to check data integrity. You can create fingerprints for all data files byusing the file fingerprint command.

The fingerprint operation generates a fingerprint on a per-file basis by using the hashing algorithms,MD5 or SHA-256.

Changes to published documentation | 93

For more information about the file fingerprint command, see the na_file(1) man page.

Changes to the Block Access Management Guide for iSCSIand FC

New information has become available since the previous revision of the Data ONTAP Block AccessManagement Guide for iSCSI and FC.

Setting volume options for the autodelete configurationThe 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 thecapacity 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 freeup 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.

94 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes

Where to find product documentation and otherinformation

You can access documentation for all NetApp products on the NetApp on the Web (NOW) site atnow.netapp.com. You can also find other product information resources, such as technical reportsand white papers, in the NetApp Library at www.netapp.com.

Next topics

Searching online information on page 95

Finding documentation on NOW on page 95

Related information

NetApp on the Web (NOW) site: now.netapp.comAccess & Order Product Documentation: now.netapp.com/knowledge/docs/docs.shtmlNetApp Library: Technical Reports: www.netapp.com/library/tr

Searching online informationThe NOW site includes a natural language search tool.

The NOW Natural Language PowerSearch tool on the Support page on the NOW site allows you tosearch 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 NOWThe 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 thispath of links from the NOW home page:

Where to find product documentation and other information | 95

Documentation > Access Product Documentation > Data ONTAP 7-Mode > Data ONTAP 8.07-Mode and later: Filer and V-Series systems

For more information, see the NOW site at now.netapp.com.

96 | Data ONTAP 8.0.1 7-Mode RC3 Release Notes


Recommended