Data ONTAP 7.3.3 Release Notes - Waterloo Computer ...ehashman/netapp/ontap/rnote.pdfMore concurrent...

Data ONTAP® 7.3.3 Release 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-05447_A0

18 May 2010

Contents

Copyright information.................................................................................15Trademark information...............................................................................17Data ONTAP 7.3.3 Release Notes................................................................19Changes introduced since Data ONTAP 7.3...............................................21

Changes in the 7.3.3 release........................................................................................21


Changes in the 7.3.1.1L1 release.................................................................................28

Changes in the 7.3.1.1 release.....................................................................................28


New and changed features in the Data ONTAP 7.3 release family..........37Changes to supported hardware and features..............................................................37

TOE automatically disabled ...........................................................................38

Flow control may be reported randomly by X1008A

10-Gb NIC with certain switches...............................................................38

Systems including DS14 shelves, ESH modules or LRC

modules are not supported.........................................................................38

Support for SnapVault integration options for use with NetBackup...............39

New platform and hardware support ..........................................................................39

Unrestricted increased aggregate capacity for FAS2020 systems...................39

New AutoSupport message for transparent vfiler migration...........................40

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

RLM supports IPv6.........................................................................................40

Support for DS4243 disk shelves ...................................................................40

Support for FAS2040 ......................................................................................40

Major nondisruptive upgrades for MetroClusters............................................41

Support for 31xx systems................................................................................41

Nondisruptive upgrade support for SATA disk drives.....................................41

UPS support.....................................................................................................41

Support for SA Systems .................................................................................42

Support for 512-GB and 256-GB Performance

Acceleration Modules ...............................................................................43

Support for 2 TB SATA disks..........................................................................43

Table of Contents | 3

MultiStore enhancements............................................................................................43

Online migration support on vFiler units........................................................43

Commands supported by the ONTAPI interface library.................................44

Secure communication for setup of disaster recovery and

data migration............................................................................................44

SnapMover license is not required...................................................................44

Deduplication support on vFiler units ............................................................44

Manageability enhancements......................................................................................45

SSL security improvements.............................................................................45

Nondisruptive upgrades for disk shelves controlled by

AT-FCX modules.......................................................................................45

Changes to the upgrade preparation process ..................................................46

Improved support for nondisruptive upgrades in SAN environments.............46

Upgrade Advisor planning tool........................................................................47

Read reallocation of data.................................................................................47

Extents for FlexVol volumes............................................................................48

Option to disable root access to the storage system........................................48

Audit log enhancement....................................................................................48

Read-only access to FilerView........................................................................49

Physical reallocation of data............................................................................49

Performance Acceleration Module and WAFL extended cache......................49

FilerView enhancements..................................................................................50

The e0M interface............................................................................................50

Data ONTAP supports up to 24 SSH sessions.................................................50

Only critical AutoSupport notifications are sent to the

autosupport.to recipients ...........................................................................51

Partner recipients for AutoSupport email notifications ..................................51

Networking and security protocols enhancements......................................................51

Support for IPv6..............................................................................................52

Support for CDP..............................................................................................55

Transport Layer Security protocol...................................................................55

TLS support in FilerView................................................................................55

Port-based load-balancing option for multimode vifs.....................................55

External cache group added to netapp.mib......................................................55

Round-robin load balancing is supported........................................................56

SNMPv3 supported .........................................................................................56

4 | Data ONTAP 7.3.3 Release Notes

New maximum number of network interfaces................................................56

File access protocol enhancements..............................................................................57

Support for multiple open instances of the SMB named

pipe on an FPolicy server ..........................................................................58

Support for the SMB 2.0 protocol...................................................................58

Kerberos Multi Realm support........................................................................58

NFSv4 enhancements .....................................................................................58

Enhancements to NFS access cache management...........................................59

Improved security for Perfmon connections....................................................59

New commands for debugging CIFS access control

problems ....................................................................................................59

New option for setting the minimum authentication level

and session security level that clients must use ........................................60

FPolicy enhancements.....................................................................................60

Maximum number of auxiliary UNIX groups supported

for a user....................................................................................................60

Block protocol enhancements......................................................................................60

Fibre Channel over Ethernet (FCoE) target expansion

adapter support...........................................................................................61

Takeover and giveback performance enhancements in a

SAN environment......................................................................................61

Ability to delete backing Snapshot copies of deleted LUN clones.................61

New default value for the maximum number of iSCSI

connections per session .............................................................................62

WWPN aliases.................................................................................................62

New windows_2008 LUN Multiprotocol Type (ostype).................................62

New solaris_efi, xen, and hyper_v LUN Multiprotocol

Types (ostypes)..........................................................................................62

Data protection enhancements.....................................................................................63

Use of SnapVault to protect a volume SnapMirror destination.......................64

TCP window size for a SnapMirror relationship.............................................64

Retention of older SnapVault Snapshot copies on

SnapVault secondary volumes...................................................................65

Compression for SnapMirror transfers............................................................65

If volumes with deduplication exceed the maximum

supported size.............................................................................................65


Snapshot copies and log files of SnapLock for SnapVault

use system clock for naming......................................................................65

Changes to the SnapLock autocommit feature ...............................................66

Backing up LUN clones to tape.......................................................................66

SnapLock supported in Data ONTAP 7.3.1 and later......................................66

LockVault now known as the SnapLock for SnapVault feature......................66

More concurrent transfers for qtree SnapMirror,

asynchronous volume SnapMirror, and SnapVault....................................67

Maximum number of concurrent replication operations

with ATA disks...........................................................................................67

Reservation of storage system resources for volume

SnapMirror, qtree SnapMirror, and SnapVault

replication operations.................................................................................67

Synchronous SnapMirror modes.....................................................................68

Space guarantee for a volume SnapMirror destination....................................69

Support for SnapMirror over Fibre Channel on FAS2050..............................69

SnapVault integration with SnapManager.......................................................70

SnapVault primary and secondary on the same storage system......................70

Enhancements to SnapVault for NetBackup....................................................70

Bandwidth optimization for Open Systems SnapVault...................................70

SnapVault for NetBackup supports basic block mode backups......................70

SnapVault with deduplication..........................................................................71

Deduplication metadata relocated...................................................................71

Deduplication configuration data relocated.....................................................71

Deduplication support on SnapLock volumes.................................................71

Deduplication checkpoint feature ...................................................................71

SnapLock support for vFiler units ..................................................................72

Qtree SnapMirror with deduplication..............................................................72

Volume SnapMirror with deduplication..........................................................72

Limit on entries in the snapmirror.conf file for each

storage system............................................................................................72

Automatic schedule for deduplication.............................................................73

Storage resource management enhancements.............................................................73

FlexClone files and FlexClone LUNs .............................................................73

Aggregate size calculation changes.................................................................73

SnapMirror destination space guarantee not disabled.....................................75


Autogrow capability for FlexCache volumes..................................................75

Support for changing to software-based disk ownership

nondisruptively...........................................................................................76

Disconnected operation for FlexCache volumes.............................................76

Active/active enhancements.........................................................................................76

Support for 672 disk drives on fabric-attached MetroClusters........................76

MetroCluster nodes on separate subnets.........................................................76

Hardware-assisted takeover.............................................................................77

Deduplication support on stretch and fabric-attached

MetroClusters ............................................................................................77

V-Series enhancements................................................................................................77

Changes to the V-Series and Data ONTAP 7.3.2 libraries ..............................78

V-Series support for native disk shelves..........................................................78

V-Series support for deduplication..................................................................79

V-Series support for IBM DS5100 and DS5300 storage arrays......................79

V-Series support for RamSan storage..............................................................79

New and changed commands and options in the DataONTAP 7.3 release family.......................................................................81

New commands in Data ONTAP 7.3...........................................................................81

Changed commands in Data ONTAP 7.3....................................................................85

New options in Data ONTAP 7.3................................................................................94

Changed options in Data ONTAP 7.3........................................................................100

Replaced or removed commands in Data ONTAP 7.3..............................................101

Requirements for running Data ONTAP 7.3............................................103Supported systems.....................................................................................................103

Systems you can use in active/active configurations ................................................104

Storage system firmware ..........................................................................................105

Storage systems that support Multipath Storage ......................................................105

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

Requirements for V-Series fabric-attached MetroCluster

configurations..........................................................................................106

Important cautions.....................................................................................107Upgrade and revert cautions......................................................................................107

If you are upgrading a system that includes FlexCache volumes..................108

If your system includes DS14 shelves, ESH modules, or

LRC modules...........................................................................................108


If you revert a system that has an X1106A-R6 or

X1107A-R6 Ethernet card installed.........................................................108

If you are upgrading to Data ONTAP 7.3 or later.........................................108

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

If you are performing a nondisruptive upgrade on a

system with VMware ESX Server hosts..................................................110

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

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

If you are using SharedStorage .....................................................................111

If you are upgrading a 60xx or SA600 system and want to

use the Upgrade Utility ...........................................................................111

If you are upgrading a FAS2020 system running Data

ONTAP 7.2.2L1.......................................................................................111

If you are upgrading a FAS20xx system .......................................................111

If you are upgrading to a 4-Gb HBA in a SAN

environment ............................................................................................112

If you are upgrading from a 2-Gb onboard port to a 4-Gb

adapter in a SAN environment ................................................................112

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

maximum capacity...................................................................................113

If you are reverting to a previous release and you use large

ACLs under NFSv4..................................................................................113

Network protocol cautions.........................................................................................114

If you use a vif that is named "vip"...............................................................114

If your system uses ATM for network connectivity.......................................115

Block access protocol cautions..................................................................................115

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

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

If jumpers J3 and J4 on QLogic 2 Gbps Fibre channel

target expansion are in positions 2 and 3.................................................116

If you use Solaris 10 and the emlxs Fibre Channel Adapter

driver .......................................................................................................116

If an iSCSI target HBA fails..........................................................................116

If you use the automatic sizing feature on thinly

provisioned LUNs when snap reserve is set to a

non-zero value..........................................................................................117


Data protection cautions............................................................................................117

Issues in SnapLock interaction with active/active

configuration ...........................................................................................118

Issues in moving SnapLock disks .................................................................118

Issues in booting a system running Data ONTAP 7.3.1 or

later with the first release of Data ONTAP 7.3 .......................................118

Issues in upgrading to Data ONTAP 7.3 if you have

SnapLock volumes ..................................................................................118

If you upgrade systems running FPolicy ......................................................119

Issues in reverting to Data ONTAP 7.3 if you have

SnapLock volumes...................................................................................119

If you are reverting to a previous release that does not

support deduplication with SnapLock volumes.......................................120

If you use DataFabric Manager to manage SnapMirror or

SnapVault relationships between vFiler units..........................................120

If you revert to a prior release, for a SnapMirror

destination with volumes using deduplication or clone operations.........121

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

Storage management cautions...................................................................................122

If you are replacing traditional volumes with FlexVol volumes....................122

If you see unexpected warnings and messages regarding

FlexVol volumes......................................................................................122

Known problems and limitations..............................................................125Manageability issues..................................................................................................125

vFiler DR configuration with the

snapmirror.checkip.enable option on fails, if

SnapMirror fails to authenticate destination IPv6 address......................125

No IPv6 support for AutoSupport e-mail notifications.................................126

AutoSupport option settings..........................................................................126

Change in sysstat -x command output ..........................................................126

RLM configuration is not saved if the RLM's Ethernet

cable is not connected..............................................................................126

File access protocol issues.........................................................................................127

Correction to required FPolicy screening requests........................................127

FPolicy file extension issue on revert............................................................127

FPolicy compatibility issue in NFSv4 environments....................................128


Limitations in the naming of FPolicy policies...............................................128

Some Group Policy Objects (GPOs) are applied

differently on storage systems than on Windows systems.......................128

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

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

Configuration issue for clients that mount NFS shares

using a non-reserved port.........................................................................129

NFSv4 client compatibility............................................................................129

Unicode character 0x0080 is not supported..................................................130

The FTP server does not support Unicode characters...................................130

No IPv6 support in FPolicy...........................................................................130

Network protocol issues............................................................................................130

The ping6 usage message is incorrect...........................................................130

Single-mode vif does not fail over correctly.................................................131

TOE is disabled..............................................................................................132

No IPv6 support for RIP and IPsec...............................................................132

Do not use VLAN deletion with IPsec..........................................................132

Enable caching with NIS lookup...................................................................132

Potentially reduced performance for IPsec traffic.........................................132

Block access protocol issues......................................................................................132

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

"option lun.partner_unreachable.default-partner.behavior:

Value must be 'drop', 'error', or 'start'" error message

periodically displays................................................................................133

FCoE adapters may fail to come online if the FCP service

is stopped and started too quickly............................................................133

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

Ongoing cfmode support...............................................................................134

cfmode restrictions for 8-Gb target expansion adapters................................135

Data protection issues................................................................................................135

Data recovery using SnapVault or SnapMirror for a qtree

with LUN clones......................................................................................136

Using SnapVault for NetBackup to protect applications...............................137

SnapVault for NetBackup is not supported with Symantec

Veritas NetBackup 6.5.............................................................................137

Changes to deduplication usage with SnapVault for NetBackup..................137


NetBackup managed SnapVault is unavailable.............................................138

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

SnapVault cannot be enabled on vFiler units when

SnapLock for SnapVault relationships are present in vfiler0...................139

Limitation of SnapLock for SnapVault relationship......................................139

Guidelines for creating a clone of a SnapVault destination volume..............139

Compatibility with SnapDrive and Snap Manager........................................140

Guidelines for creating a clone of a qtree SnapMirror

destination volume...................................................................................140

FlexVol volume limits with SnapMirror on a FAS250

storage system..........................................................................................141

Synchronous SnapMirror not supported for volumes with

deduplication............................................................................................141

SMB 2.0 not supported for SnapLock ..........................................................141

Possible effect of creating more than 64 mirrored

aggregates preventing disaster recovery from

functioning correctly................................................................................141

Protection Manager 3.7 does not perform optimally with

deduplication............................................................................................141

Improved sequential read performance for deduplicated

FlexVol volumes......................................................................................141

Volumes with deduplication are disabled after a

nondisruptive upgrade..............................................................................142

SnapVault issues in cascaded configurations.................................................142

Suboptimal space savings with deduplication when 16 GB

Performance Acceleration Module is installed........................................143

Storage resource management issues........................................................................143

The all keyword for the aggr add command is not yet

implemented ............................................................................................143

Moving disks to a system running an earlier version of

Data ONTAP could cause disk identification issues ...............................144

Data ONTAP can silently select varying disk or array

LUN sizes when enlarging or creating an aggregate ..............................144

Qtree quotas might prevent explicit quotas from

overriding the default...............................................................................145

FlexVol volume limit for FAS250 systems....................................................145


Offline nodes in origin cluster can affect FlexCache

volume performance................................................................................146

Adding a FlexCache origin volume to a vFiler unit might

cause caching system to panic.................................................................146

Offline status of origin volume running Data ONTAP 10.0

not correctly reported on FlexCache volume...........................................146

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

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

No support for REP with zone checksum type array LUNs......................................147

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

Active/active configuration issues.............................................................................148

If takeover is enabled for network interface failure,

automatic giveback should be disabled....................................................148

Changes to published documentation.......................................................149Changes to the Archive and Compliance Management Guide..................................149

Changes to cross-references to SnapLock information.................................149

Integration of third-party applications with SnapLock feature......................150

Changes to the Commands Manual Page Reference ................................................150

The na_ping6(1) man page lists incorrect options.........................................150

Changes to the Data Protection Online Backup and Recovery Guide.......................150

Syntax entry correction in the snapmirror.conf file.......................................150

Changes to the Data Protection Tape Backup and Recovery Guide .........................151

Backing up data to tape using NDMP services.............................................151

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

Correction for disabling virus scanning.........................................................151

Enhancements to NFS access cache management.........................................152

Changes to the V-Series Implementation Guide for IBM Storage.............................152

Changes to the V-Series Implementation Guide for Native Disk Shelves.................152

Array LUN sizing with 2 TB disks is not documented in all

V-Series Implementation Guides ........................................................................153

Changes to cross-references to SnapLock information.............................................153

Changes to the Upgrade guide...................................................................................153

Corrections to the "Deduplication requires additional free

space in aggregates after upgrading" section...........................................153

Where to find product documentation and other information...............155The Documentation Roadmap...................................................................................155


Searching online information ...................................................................................156

Finding documentation on NOW ..............................................................................156


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 an electronic retrievalsystem—without prior written permission of the copyright owner.

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

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WHICH ARE HEREBYDISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein, exceptas expressly agreed to in writing by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

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

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

Copyright information | 15

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 (NetAppon the Web); ONTAPI; RAID-DP; SANscreen; SecureShare; Simulate ONTAP; SnapCopy; SnapDrive;SnapLock; SnapManager; SnapMirror; SnapMover; SnapRestore; SnapValidator; SnapVault; SpinnakerNetworks; Spinnaker Networks logo; SpinAccess; SpinCluster; SpinFlex; SpinFS; SpinHA; SpinMove;SpinServer; SpinStor; StorageGRID; StoreVault; SyncMirror; Topio; vFiler; VFM; and WAFL areregistered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. Network Appliance, Snapshot,and The evolution of storage are trademarks of NetApp, Inc. in the U.S.A. and/or other countries andregistered trademarks in some other countries. The StoreVault logo, ApplianceWatch, ApplianceWatchPRO, ASUP, AutoSupport, ComplianceClock, DataFort, Data Motion, FlexScale, FlexSuite, LifetimeKey Management, LockVault, NOW, MetroCluster, OpenKey, ReplicatorX, SecureAdmin, ShadowTape, 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 of otherIBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or othercountries. 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, and SureStream aretrademarks 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 iscertified RealSystem compatible.

Trademark information | 17

Data ONTAP 7.3.3 Release Notes

The Data ONTAP 7.3.3 release contains online migration support on vFiler units, additional IPv6support, and other new features and enhancements.

About the Data ONTAP 7.3.3 release

Data ONTAP 7.3.3 is a release in the Data ONTAP 7.3 release family. For more information aboutData ONTAP releases, see the "Data ONTAP Release Model" on the NOW site.

Attention:

Upgrading to Data ONTAP 7.3 or later from an earlier release will cause existing FlexVol volumesto require more free space from their containing aggregate. You should therefore ensure that allsystems upgrading to Data ONTAP 7.3 have sufficient free space in their aggregates before upgrading.For more information, see If you are upgrading to Data ONTAP 7.3 or later on page 108.

Beginning with Data ONTAP 7.3, DS14 disk shelves (sometimes referred to as DS14mk1), LRCstorage I/O modules, and ESH storage I/O modules are no longer supported. If even one of thesedevices is attached to your storage system, you should not upgrade to Data ONTAP 7.3 or later. Formore information, see Systems including DS14 shelves, ESH modules or LRC modules are notsupported on page 38.

About these release notes

All the information in this document applies to the Data ONTAP 7.3.3 release for NetApp storagesystems (FAS systems, NearStore systems, and V-Series systems), unless noted. FAS systems andNearStore systems are sometimes called filers or appliances. Some of the information in this documentapplies to SA systems.

Note: There are no longer separate release notes for V-Series systems.

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

Data ONTAP 7.3.3 Release Notes | 19

http://now.netapp.com/NOW/products/ontap_releasemodel/post70.shtml

Changes introduced since Data ONTAP 7.3

If you are already familiar with an earlier release in the Data ONTAP 7.3 release family and you wantto see what is new since that release, you can see exactly which changes have been introduced witheach release in the Data ONTAP 7.3 family. To pinpoint what has changed since the release in the DataONTAP 7.3 family that you are familiar with, look at the changes that were introduced after that release.

Note:

• If you are new to the Data ONTAP 7.3 family, it is not necessary to read this section.Go directly to New and changed features in the Data ONTAP 7.3 release family on page 37.

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

Next topics

Changes in the 7.3.3 release on page 21


Changes in the 7.3.1.1L1 release on page 28

Changes in the 7.3.1.1 release on page 28


Related information

http://now.netapp.com/NOW/cgi-bin/bol/


Changes in the 7.3.3 releaseThe Data ONTAP 7.3.3 release contains online migration support on vFiler units, additional IPv6support, and other new features and enhancements.

New platform and hardware support

Data ONTAP 7.3.3 and later supports aggregates larger than 8 TB for FAS2020 systems withoutrestrictions. For more information, see Unrestricted increased aggregate capacity for FAS2020systems on page 39.

Data ONTAP 7.3.2 and later releases support 2 TB SATA disks. For more information see, Supportfor 2 TB SATA disks on page 43.

Changes introduced since Data ONTAP 7.3 | 21



For more information about all new platform and hardware support in the Data ONTAP 7.3 releasefamily, see New platform and hardware support on page 39.

New and changed features in Data ONTAP 7.3.3

The Data ONTAP 7.3.3 release introduces the following new and changed features:

• Maximum number of data disks per 16-TB aggregate on page 74

• Online migration support on vFiler units on page 43

• IPv6 features in Data ONTAP 7.3.3 on page 53

• Support for CDP on page 55

• Enhancements to NFS access cache management on page 59

• Improved security for Perfmon connections on page 59

• New RLM firmware and its upgrade requirements on page 109

For more information about new and changed features in the Data ONTAP 7.3. release family, see Newand changed features in the Data ONTAP 7.3 release family on page 37.

New commands in Data ONTAP 7.3.3

Data ONTAP 7.3.3 includes the following new command:

• cdpd

• nfs nsdb flush

For more information about new commands in Data ONTAP 7.3 release family, see New commandsin Data ONTAP 7.3 on page 81.

Changed commands in Data ONTAP 7.3.3

Data ONTAP 7.3.3 includes the following changed commands:

• exportfs -c

• exportfs -f

• fcp portname set

• fcp portname swap

• storage show fault

For more information about changed commands in Data ONTAP 7.3 release family , see Changedcommands in Data ONTAP 7.3 on page 85.

New options in Data ONTAP 7.3.3

Data ONTAP 7.3.3 includes the following new options:

• cdpd.holdtime


• cdpd.interval

• cifs.perfmon.allowed_users

• tftpd.max_connections

For more information about new options in Data ONTAP 7.3 release family, see New options in DataONTAP 7.3 on page 94.

New cautions in Data ONTAP 7.3.3

The following new caution was introduced in Data ONTAP 7.3.3 :

• New RLM firmware and its upgrade requirements on page 109

For more information about new cautions in Data ONTAP 7.3 release family, see Importantcautions on page 107.

Cautions changed in Data ONTAP 7.3.3

The following caution was changed in Data ONTAP 7.3.3

• If you are upgrading a FAS2020 system running Data ONTAP 7.2.2L1 on page 111

Cautions removed in Data ONTAP 7.3.3

The following cautions that were included in the Data ONTAP 7.3.2 Release Notes were removed fromthe Data ONTAP 7.3.3 Release Notes:

• Using ACP can cause system panic

• If you are upgrading a system that includes FlexVol volumes

• SnapMirror commands that become obsolete in Data ONTAP 8.0

• Routes for a vFiler unit not added in the partner node during takeover

• If you are upgrading a system with AT-FCX disk shelves attached

New known limitations in Data ONTAP 7.3.3

Data ONTAP 7.3.3 includes the following new known limitations:

• vFiler DR configuration with the snapmirror.checkip.enable option on fails, if SnapMirror fails toauthenticate destination IPv6 address on page 125

• SnapVault issues in cascaded configurations on page 142

• Single-mode vif does not fail over correctly on page 131

• Disks offline in Windows 2008 after a standard upgrade on page 133

• The ping6 usage message is incorrect on page 130

• RLM configuration is not saved if the RLM's Ethernet cable is not connected on page 126


For more information about new known limitations in Data ONTAP 7.3 release family, see Knownproblems and limitations on page 125.

Limitations removed in Data ONTAP 7.3.3

The following limitations that were included in the Data ONTAP 7.3.2 Release Notes have been removedfrom Data ONTAP 7.3.3 Release Notes:

• Metadata not backed up during dump of qtree SnapMirror destinations

• Limitation when destroying a vFiler unit that is part of an IPspace

• Delayed I/O seen on the host during controller forced takeover or giveback and reboots

The descriptions for the following limitations that were included in the Data ONTAP 7.3.2 ReleaseNotes have been moved to the Data ONTAP MultiStore Management Guide:

• Limitation when migrating a vFiler unit between the nodes of an active/active configuration

• Limitation when you create a vFiler unit in a nondefault IPspace

• Default limit on the number of vFiler units

• Syntax correction of the vfiler migrate start command

• Maximum vFiler units allowed in FAS2040 systems

Documentation changes for Data ONTAP 7.3.3

The following new or changed information supplements the documentation you received for the DataONTAP 7.3.3. release:

• Changes to the Archive and Compliance Management Guide on page 149

• Changes to the Commands Manual Page Reference on page 150

• Changes to the Data Protection Online Backup and Recovery Guide on page 150

• Changes to the Data Protection Tape Backup and Recovery Guide on page 151

• Changes to the File Access and Protocols Management Guide on page 151

• Changes to the V-Series Implementation Guide for IBM Storage on page 152

• Changes to the V-Series Implementation Guide for Native Disk Shelves on page 152

• Array LUN sizing with 2 TB disks is not documented in all V-Series Implementation Guideson page 153

• Changes to the Upgrade guide on page 153

For more information about these and other important documentation changes in the Data ONTAP 7.3release family, see Changes to published documentation on page 149.


Changes in the 7.3.2 releaseThe Data ONTAP 7.3.2 release supports FlexClone technology for files and LUNS, adds support forTransport Layer Security (TLS) version 1.0, and supports two new FCoE target expansion adapters.Data ONTAP 7.3.2 also supports port-based load balancing for multimode vifs. Data ONTAP 7.3.2introduces the ability to upgrade fabric-attached MetroClusters from one release family to anothernondisruptively (major nondisruptive upgrades) and also includes changes to the SnapLock autocommitfeature. FilerView in Data ONTAP 7.3.2 supports the TLS protocol.



• TOE automatically disabled on page 38

• New disk drive AutoSupport message sent weekly on page 40

• Support for DS4243 disk shelves on page 40

• Support for FAS2040 on page 40

• Major nondisruptive upgrades for MetroClusters on page 41

• TLS support in FilerView on page 55

• Transport Layer Security protocol on page 55

• External cache group added to netapp.mib on page 55

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

• Fibre Channel over Ethernet (FCoE) target expansion adapter support on page 61

• If volumes with deduplication exceed the maximum supported size on page 65

• Retention of older SnapVault Snapshot copies on SnapVault secondary volumes on page 65

• Compression for SnapMirror transfers on page 65

• Changes to the SnapLock autocommit feature on page 66

• Snapshot copies and log files of SnapLock for SnapVault use system clock for naming on page 65

• Port-based load-balancing option for multimode vifs on page 55

• FlexClone files and FlexClone LUNs on page 73

• Support for 672 disk drives on fabric-attached MetroClusters on page 76

• SnapMover license is not required on page 44

For more information about new and changed features in Data ONTAP 7.3.2, see New and changedfeatures in the Data ONTAP 7.3 release family on page 37


For a description of the five new commands in Data ONTAP 7.3.2, see:


• New commands in Data ONTAP 7.3 on page 81


For a description of the nine changed commands in Data ONTAP 7.3.2, see:

• Changed commands in Data ONTAP 7.3 on page 85


For a description of the nine new options in Data ONTAP 7.3.2, see:

• New options in Data ONTAP 7.3 on page 94

Changed options in Data ONTAP 7.3.2

For a description of the four changed options in Data ONTAP 7.3.2, see:

• Changed options in Data ONTAP 7.3 on page 100


The following new cautions were introduced in Data ONTAP 7.3.2:

• If you are upgrading a system that includes FlexCache volumes on page 108

• Identical WWPNs can occur on both nodes in a cluster on page 115

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

For more information, see Important cautions on page 107.


The following cautions that were included in the Data ONTAP 7.3.1.1 Release Notes have been removedfrom the Data ONTAP 7.3.2:

• If the storage system panics during upgrade from the Data ONTAP 7.1 release family

• If you upgrade from releases earlier than Data ONTAP 6.5.1

• If you upgrade systems running SnapMirror

• If you upgrade storage systems with iSCSI targets

• If you want to change a storage system's hostname

• If you are using SnapLock in a MetroCluster configuration

• Aggregate reallocation is not supported on aggregates created before Data ONTAP 7.2

• Volume reallocation is not supported

• The wafliron tool requires free space in the root volume to run successfully

• When restoring a Snapshot copy, no deletion of the backing Snapshot copy until the LUN clonesplit is complete


• iSCSI Target HBA support

• The ostype parameter now required when creating LUNs and igroups

• Enabling iSNS server v.3.0

• Partition alignment problems cause an iSCSI LUN performance problem

• Brocade switch support for fabric-attached MetroCluster configurations

• Failed disks can cause giveback to fail

• CFO partner node's SSL certificate is used after takeover and giveback


Data ONTAP 7.3.2 includes the following new limitations:

• AutoSupport option settings on page 126

• TOE is disabled on page 132

• FCoE adapters may fail to come online if the FCP service is stopped and started tooquickly on page 133

• No support for REP with zone checksum type array LUNs on page 147

• "option lun.partner_unreachable.default-partner.behavior: Value must be 'drop', 'error', or 'start'"error message periodically displays on page 133

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


The following limitations that were included in the Data ONTAP 7.3.1.1 Release Notes have beenremoved from Data ONTAP 7.3.2:

• TOE acceleration is not available for vifs

• MAC address hard limits for TOE cards

• IPv6 not supported with FlexCache

• Operations involving vFiler units can disable quotas

• Aggregate reallocation is not supported on aggregates created before Data ONTAP 7.2

• Volume reallocation is not supported

• The wafliron tool requires free space in the root volume to run successfully

• When restoring a Snapshot copy, no deletion of the backing Snapshot copy until the LUN clonesplit is complete

• iSCSI Target HBA support

• The ostype parameter now required when creating LUNs and igroups

• Enabling iSNS server v.3.0

• Partition alignment problems cause an iSCSI LUN performance problem

• Brocade switch support for fabric-attached MetroCluster configurations


• Failed disks can cause giveback to fail

• CFO partner node's SSL certificate is used after takeover and giveback


The following new or changed information supplements the documentation you received for the DataONTAP 7.3.2 release:

• Default limit on the number of vFiler units (Describes the limits on the number of vFiler units instorage systems that have the MultiStore license enabled.)

• Changes to the V-Series Implementation Guide for Native Disk Shelves on page 152 (Describeschanges to the V-Series Implementation Guide for Native Disk Shelves dated December 2008, partnumber 210-04321_A0.)

• Syntax correction of the vfiler migrate start command

For more information about these and other important documentation changes, see Changes to publisheddocumentation on page 149.

Changes in the 7.3.1.1L1 releaseData ONTAP 7.3.1.1L1 provides critical fixes for storage controllers with the X1008A 10GbE networkadapter card running any Data ONTAP 7.3.x release.

Changes to supported hardware and features

The Data ONTAP 7.3.1.1L1 release introduces the following changes to supported hardware andfeatures:

• Flow control may be reported randomly by X1008A 10-Gb NIC with certain switches on page 38

For more information about changes to supported hardware and features in Data ONTAP 7.3.1.1L1,see Changes to supported hardware and features on page 37 .

Changes in the 7.3.1.1 releaseData ONTAP 7.3.1.1 now supports the round-robin load balancing option for multimode vifs andincludes additional considerations when planning to rejoin split aggregates. In addition, beginning withData ONTAP 7.3, DS14 disk shelves (sometimes referred to as DS14mk1), LRC storage I/O modules,and ESH storage I/O modules are no longer supported. Data ONTAP 7.3.1.1 also includes many bugfixes.


New and changed features in Data ONTAP 7.3.1.1

The Data ONTAP 7.3.1.1 release introduces the following new and changed features:

• Round-robin load balancing is supported on page 56

For more information about new and changed features in Data ONTAP 7.3.1.1, see New and changedfeatures in the Data ONTAP 7.3 release family on page 37.

Changes to supported hardware and features

The Data ONTAP 7.3.1.1 release introduces the following changes to supported hardware and features:

• Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 38

• Support for SnapVault integration options for use with NetBackup on page 39

For more information about changes to supported hardware and features in Data ONTAP 7.3.1.1, seeChanges to supported hardware and features on page 37 .

For more information about new platform and hardware support in Data ONTAP 7.3.1.1, see Newplatform and hardware support on page 39.

New or changed commands in Data ONTAP 7.3.1.1

Data ONTAP 7.3.1.1 includes the following changed command.

• vif create

For more information about changed commands in Data ONTAP 7.3.1.1, see Changed commands inData ONTAP 7.3 on page 85.

New or changed options in Data ONTAP 7.3.1.1

There were no new or changed options introduced in Data ONTAP 7.3.1.1.

New or changed cautions in Data ONTAP 7.3.1.1

The following new caution was introduced in Data ONTAP 7.3.1.1:

• If your system includes DS14 shelves, ESH modules, or LRC modules on page 108


Cautions removed in Data ONTAP 7.3.1.1

The following cautions that were included in the Data ONTAP 7.3.1 Release Notes have been removedfrom Data ONTAP 7.3.1.1:

• If you are upgrading a system that has vifs configured with the round-robin option

• Modifying the persistent configuration to remove round-robin load balancing


New known limitations in Data ONTAP 7.3.1.1

Data ONTAP 7.3.1.1 includes the following new limitations:

• Data recovery using SnapVault or SnapMirror for a qtree with LUN clones

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

Documentation changes for Data ONTAP 7.3.1.1

The following new or changed information supplements the documentation you received for the DataONTAP 7.3.1.1 release:

• Changes to disk shelf module support statements (contains updated information in the Data ONTAPActive/Active Configuration Guide and the Data ONTAP Upgrade Guide about DS14 disk shelves,LRC modules, and ESH modules.)

• Changes to cross-references to SnapLock information ( contains updated information aboutcross-references to SnapLock information.)

• Changes to the Network Management Guide ( includes guidelines for creating a second-level vif,updated information about the round-robin option for creating a multimode vif, and updatedinformation about load balancing in multimode vifs.)

• Changes to the Data Protection Online Backup and Recovery Guide(contains updated informationwhen planning to rejoin split aggregates that previously used MetroCluster to mirror SnapLockvolumes.)

• Changes to the Active/Active Configuration Guide (contains updated information when usingSnapLock in a MetroCluster configuration.)

• Changes to the File Access and Protocols Management Guide (contains updated informationregarding changes to creating a SnapLock Compliance SnapMirror relationship section, changes tolimitations of FPolicy, hyphen supported as a special character in Policy Name, caution beforedestroying a file policy, changes to configuring native file blocking section, and steps for configuringnative file blocking.)

• Changes to the Archive and Compliance Management Guide (contains updated information aboutcreating a SnapLock Compliance SnapMirror and restricting the destination volume before initializingthe SnapMirror relationship.)

For more information about these and other important documentation changes, see Changes to publisheddocumentation on page 149.

Changes in the 7.3.1 releaseData ONTAP 7.3.1 includes support for 3160 systems, support for IPv6 and new features related todeduplication, FlexCache, and WAFL. Data ONTAP 7.3.1 also includes bug fixes, such as featuresrelated to the ability to use Telnet or Remote Shell (RSH) sessions to update RLM firmware.




• Support for 31xx systems on page 41

• Nondisruptive upgrades for disk shelves controlled by AT-FCX modules on page 45

• Changes to the upgrade preparation process on page 46

• Read reallocation of data on page 47

• Extents for FlexVol volumes on page 48

• Support for IPv6 on page 52

• Kerberos Multi Realm support on page 58

• Support for the SMB 2.0 protocol on page 58

• IPv6 RFCs supported on page 54

• FPolicy enhancements on page 60

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

• New solaris_efi, xen, and hyper_v LUN Multiprotocol Types (ostypes) on page 62

• SnapLock supported in Data ONTAP 7.3.1 and later on page 66

• Support for SnapMirror over Fibre Channel on FAS2050 on page 69

• Deduplication support on SnapLock volumes on page 71

• SnapLock support for vFiler units on page 72

• Support for changing to software-based disk ownership nondisruptively on page 76

• Disconnected operation for FlexCache volumes on page 76

• Commands supported by the ONTAPI interface library on page 44

• Using SnapVault for NetBackup to protect applications on page 137

• Changes to deduplication usage with SnapVault for NetBackup on page 137

For more information about new and changed features in Data ONTAP 7.3.1, see New and changedfeatures in the Data ONTAP 7.3 release family on page 37.


Data ONTAP 7.3.1 introduces the following new commands:

• ndp

• ping6

• snaplock log archive

• snaplock log status

• snaplock log volume

• snaplock options

• snaplock privdel


• traceroute6


Data ONTAP 7.3.1 introduces the following changed commands:

• cifs setup

• environ shelf

• lock break

• nfs setup

• snap autodelete

• snapvault start

• storage show hub

• vfiler dr configure

• vfiler dr delete

• vfiler migrate

• vfiler migrate start

• vfiler migrate cancel

• vfiler migrate complete

• vfiler dr resynch

• vol clone create [-f]

• vol options

• vol optionsextent

• vol options read_realloc

• vol status-v

• vol status -w

For more information see Changed commands in Data ONTAP 7.3 on page 85 .

Commands removed in Data ONTAP 7.3.1

The following command was removed in Data ONTAP 7.3.1:

• software install

For more information, see Replaced or removed commands in Data ONTAP 7.3 on page 101.


Data ONTAP 7.3.1 includes the following options:

• autosupport.partner.to


• cifs.audit.liveview.allowed_users

• cifs.ipv6.enable

• cifs.smb2.client.enable

• cifs.smb2.enable

• cifs.smb2.durable_handle.enable

• cifs.smb2.durable_handle.timeout

• cifs.smb2.signing.required

• flexcache.deleg.high_water

• flexcache.deleg.low_water

• ftpd.ipv6.enable

• httpd.ipv6.enable

• ip.v6.enable

• ip.v6.ra_enable

• nfs.ifc.rcv.high

• nfs.ifc.rcv.low

• nfs.ipv6.enable

• nfs.max_num_aux_groups

• nfs.thin_prov.ejuke

• nfs.v4.setattr_acl_preserve

• raid.disktype.enable

• shelf.atfcx.auto.reset.enable

• shelf.esh4.auto.reset.enable

• snaplock.autocommit_period

• snaplock.compliance.write_verify {on|off}

• snaplock.log.default_retention

• snaplock.log.maximum_size

• snapvault.nbu.archival_snap_default

• snapvault.ossv.compression

• vif.failover.link_degraded

For more information, see New options in Data ONTAP 7.3 on page 94.

Changed options in Data ONTAP 7.3.1

The following options were changed in Data ONTAP 7.3.1:

• nlm.cleanup.timeout

For more information, see Changed options in Data ONTAP 7.3 on page 100 .



The following new cautions were introduced in Data ONTAP 7.3.1:

• If you revert to a prior release, for a SnapMirror destination with volumes using deduplication orclone operations on page 121

• If you are reverting to a previous release that does not support deduplication with SnapLockvolumes on page 120

• If you are reverting to a previous release and you use large ACLs under NFSv4 on page 113

• Guidelines for creating a clone of a SnapVault destination volume on page 139



The following cautions that were included in the Data ONTAP 7.3 Release Notes have been removedfrom Data ONTAP 7.3.1:

• If you are upgrading a FAS2020 system that includes aggregates larger than 8 TB.

• SnapLock not supportedSnapLock is not supported in the first release of Data ONTAP 7.3. However, Data ONTAP 7.3.1supports SnapLock with new features.

• If you are upgrading a system to this release and you use deduplication

• Lasers do not shut off on QLogic 2 Gbps Fibre Channel target expansion adapters.For more information see, Bug ID 265223.The workaround for this problem is to change the position of jumpers J3 and J4 on the adapter frompositions 2 and 3 to positions 1 and 2, respectively.


Data ONTAP 7.3.1 includes the following new limitations:

• No IPv6 support in FPolicy on page 130

• cfmode restrictions for 8-Gb target expansion adapters on page 135

• SnapVault cannot be enabled on vFiler units when SnapLock for SnapVault relationships are presentin vfiler0 on page 139

• SMB 2.0 not supported for SnapLock on page 141

• Limitation of incremental backup (removed limitation in DOT 7.3.2)

• IPv6 not supported with FlexCache (removed limitation in DOT 7.3.2)

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


The following limitations were removed from Data ONTAP 7.3.1:


• Certain timeout options for FlexCache attribute cache not always correctly displayed

• Creation of FlexClone volumes with space guarantee of none and fractional reserve of zero is notprevented

• Restriction on maximum volume sizeIf a volume has ever been larger than the maximum supported deduplication volume size on a storagesystem, then deduplication cannot be enabled on the volume, even if the volume has been shrunkto a size supported by the storage system.

• Solaris hosts using a 2-Gb QLogic Fibre Channel HBA require NetApp FCP Solaris Host Utilities4.3Solaris hosts using a 2-Gb QLogic Fibre Channel HBA such as Sun SG-XPCI1FC-QL2 (QLogicQLA2340) or Sun SG-XPCI2FC-QF2-Z (QLogic QLA2342) must use NetApp FCP Solaris HostUtilities 4.3 in order for the sanlun command to function properly.


The following new or changed information supplements the documentation you received for the DataONTAP 7.3.1 release:

• The Data ONTAP Active/Active Configuration Guide contains new information about active/activeconfigurations.

• The Data ONTAP Archive and Compliance Management Guide is a new guide in the Data ONTAP7.3.1 release and describes how to archive and protect data for compliance purposes.

• The Data ONTAP Data Protection Online Backup and Recovery Guide contains new informationabout SnapVault for NetBackup and configuring SnapMirror over Fibre Channel.

• The Data ONTAP File Access and Protocols Management Guide contains new information relatedto Kerberos Multi Realm support, including changes to the procedures for configuring Kerberosauthentication for CIFS and NFS.

• The Data ONTAP Network Management Guide contains information about the link local addressfor VLANs created on a network interface and also contains examples of the options interfacecommand.

• The Data ONTAP Storage Management Guide contains new information about support for 450-GBSAS and FC disks.

• The Data ONTAP System Administration Guide contains new information about SSH requests andIPv6 support.

For more information about these and other important documentation changes, see Changes to publisheddocumentation on page 149 .


New and changed features in the Data ONTAP 7.3release family

This section covers features that were added or changed in the Data ONTAP 7.3 release family.

The major changes made in Data ONTAP 7.3 family releases are described here. For other importantinformation in these release notes about changes to the product during these releases, see the summaryof all new and changed commands and options in the release family. For a comparison of bugs fixedin different releases, see Bugs Online on the NOW site.

Next topics

Changes to supported hardware and features on page 37

New platform and hardware support on page 39

MultiStore enhancements on page 43

Manageability enhancements on page 45

Networking and security protocols enhancements on page 51

File access protocol enhancements on page 57

Block protocol enhancements on page 60

Data protection enhancements on page 63

Storage resource management enhancements on page 73

Active/active enhancements on page 76

V-Series enhancements on page 77

Related information

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

Changes to supported hardware and featuresData ONTAP 7.3 and later releases provide additional changes to supported hardware and features.

Next topics

TOE automatically disabled on page 38

Flow control may be reported randomly by X1008A 10-Gb NIC with certain switches on page 38

Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 38

Support for SnapVault integration options for use with NetBackup on page 39

New and changed features in the Data ONTAP 7.3 release family | 37


TOE automatically disabledIf you upgrade to Data ONTAP 7.3.2, TCP offload engine (TOE) functionality is automatically disabled.

Flow control may be reported randomly by X1008A 10-Gb NIC with certainswitches

Unpredictable status results may occur when trying to enable flow control on a X1008A 10-Gb NICattached to a Cisco Nexus family switch.

Considerations

Even when all options are correctly enabled, reboots or other methods of forcing flow controlrenegotiation such as resetting ports, may result in the filer port negotiating flow control correctly butreporting incorrect results.

For example, the filer port may report random values of flow control as read from the ifstat commandsSend, Receive, Full or None, with no immediate pattern recognizable.

On the Cisco Nexus 5000 Series switch, Ethernet interfaces do not automatically detect the link-levelflow control capability because link-level flow control capability is disabled. You should set flowcontrol explicitly on both the switch and filer to your desired settings (on or off) and ignore the erroneousreports.

Systems including DS14 shelves, ESH modules or LRC modules are notsupported

Beginning with Data ONTAP 7.3, DS14 disk shelves, LRC storage I/O modules, and ESH storage I/Omodules are no longer supported. Upgrading a system with any of these devices attached to it will resultin an unsupported configuration. If even one of these devices is attached to your storage system, youshould 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 NetApp representativeto discuss upgrading to the latest DS14mk4 disk shelf with ESH4 storage I/O modules.

Support for SnapVault integration options for use with NetBackupSnapVault for NetBackup continues to be supported in the Data ONTAP 7.3 release family. However,Data ONTAP 8.0 and later releases of Data ONTAP will not support SnapVault integration options foruse with NetBackup.

New platform and hardware supportThe Data ONTAP 7.3 release family supports new hardware. The new platform and hardware are listedin the order that they were introduced, with the most recent listed first.

Next topics

Unrestricted increased aggregate capacity for FAS2020 systems on page 39

New AutoSupport message for transparent vfiler migration on page 40

New disk drive AutoSupport message sent weekly on page 40

RLM supports IPv6 on page 40

Support for DS4243 disk shelves on page 40

Support for FAS2040 on page 40

Major nondisruptive upgrades for MetroClusters on page 41

Support for 31xx systems on page 41

Nondisruptive upgrade support for SATA disk drives on page 41

UPS support on page 41

Support for SA Systems on page 42

Support for 512-GB and 256-GB Performance Acceleration Modules on page 43

Support for 2 TB SATA disks on page 43

Unrestricted increased aggregate capacity for FAS2020 systemsBeginning with Data ONTAP 7.3.3, FAS2020 systems support aggregate capacities of up to 16 TBwith no restrictions.

For more information about FAS2020 systems' storage capacity, see the System Configuration Guide.

Related information

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


http://now.netapp.com/NOW/knowledge/docs/hardware/NetApp/syscfg/

New AutoSupport message for transparent vfiler migrationIn Data ONTAP 7.3.3, an AutoSupport message is sent when transparent vfiler migration from onecontroller to another controller fails. Failure is defined by cutover exceeding 120 seconds.

The message will be triggered from both the source and destination controllers whenever transparentvfiler migration fails.

In addition, information about all the migrations that occurred during the past week are included in theweekly AutoSupport message. If a migration failed, the weekly message also contains informationabout the failure.

New disk drive AutoSupport message sent weeklyA weekly NetApp Health Trigger (NHT) AutoSupport message provides information about any faileddisk drives.

The message is sent each Sunday between 12:00 a.m. and 1 a.m. local time. If no drives failed duringthe past week, no weekly drive NHT message is sent.

By default, the NHT message is sent only to technical support.

RLM supports IPv6Beginning with Data ONTAP 7.3.3, the RLM supports IPv6. To send RLM traffic over IPv6, you mustbe running RLM version 4.0 and IPv6 must be enabled on the storage system.

For more information see New RLM firmware and its upgrade requirements on page 109.

Support for DS4243 disk shelvesStarting with Data ONTAP 7.3.2, the DS4243 disk shelf is supported. The DS4243 disk shelf containsexternal SAS and SAS-connected SATA disk drives.

For more information about which disks and disk shelves are supported with your storage system model,see the System Configuration Guide. For more information about the DS4243 disk shelf, see the DS4243Installation and Service Guide.

Support for FAS2040Data ONTAP 7.3.2 and later releases support the FAS2040 platform which supports the followingfeatures:

• One or two controllers

• Up to 12 internal SAS or SATA disks

• Four Gigabit Ethernet ports per controller

• One SAS port per controller


• One ACP (Alternate Control Path) port per controller

• Two 4-Gb Fibre Channel ports per controller

• Baseboard management controller (BMC) remote management device

• 4-GB memory per controller

Major nondisruptive upgrades for MetroClustersData ONTAP 7.3.2 introduces the ability to upgrade fabric-attached MetroClusters from one releasefamily to another nondisruptively (major nondisruptive upgrades). Data ONTAP 7.3 introduced theability to upgrade stretch MetroClusters from one release family to another nondisruptively.

For more information about fabric-attached and stretch MetroClusters, see the Data ONTAP Active/ActiveConfiguration Guide.

For more information about nondisruptive upgrades, see the Data ONTAP Upgrade Guide.

Support for 31xx systemsData ONTAP 7.3 and later releases support 31xx systems. The 3140 and 3170 systems were introducedin Data ONTAP 7.3, and the 3160 is part of the Data ONTAP 7.3.1 release.

• The 3140 system has 4 GB memory and one processor.The 3140 system also includes four available PCI-Express slots, two Gigabit Ethernet ports, oneManagement port, and four 4-Gb Fibre Channel ports.

• The 3170 system has 16 GB memory and two processors.The 3170 system also includes four available PCI-Express slots, two Gigabit Ethernet ports, oneManagement port, and four 4-Gb Fibre Channel ports.

• The 3160 system has 8 GB memory and two processors.The 3160 system also includes four available PCI-Express slots, two Gigabit Ethernet ports, oneManagement port, and four 4-Gb Fibre Channel ports. These are all per-controller. Typically, achassis contains two controllers.

Nondisruptive upgrade support for SATA disk drivesNondisruptive upgrades to Data ONTAP 7.3 releases are now fully supported for NFS and SAN storageenvironments employing SATA disk drives.

UPS supportData ONTAP 7.2.4 and later releases support uninterruptible power supply (UPS) devices from AmericanPower Conversion Corporation (APC). All models of APC SmartUPS and SymmetraUPS had alreadybeen supported.


Support for SA SystemsData ONTAP 7.2.5, 7.3, and later releases support the SA200, SA300, and SA600 systems. These SAsystems support a subset of features supported by FAS systems. SA systems are storage systems capableof storing only FlexCache volumes.

FlexCache volumes are sparsely populated volumes that are backed by a volume on a FAS system.When data that is not present in the FlexCache volume is requested, it is fetched from the backing, ororigin, volume and cached in the FlexCache volume.

You manage an SA system the same way you manage a FAS system, with the following differences:

• SA systems can be used only for FlexCache volumes.

• Only FlexCache volumes and the root volume can be mounted using NFSv2 or NFSv3.

• No file access protocol other than NFSv2 and NFSv3 is supported.

• Only the following licenses are supported:

• flexcache_nfs

• cluster

• flex_scale

• operations_manager

• protection_manager

• provisioning_manager

• The size of the root volume is restricted:

• Traditional root volumes cannot be increased in size.

• Flexible root volumes can grow only to 100 GB or the minimum root volume size, whicheveris larger.

• SA systems can be configured in a standard active/active configuration, but not a mirroredactive/active configuration or a mirrored MetroCluster.

If you are using an SA system, not all functionality described in the Data ONTAP documentation isavailable to you. The following table lists the Data ONTAP guides that you need to configure andmanage your SA system:

See...For information about...

Data ONTAP Storage Management GuideConfiguring and managing FlexCache volumes

Data ONTAP Software Setup GuideSetting up your SA system

Data ONTAP System Administration GuideConfiguring your root volume and general systemmaintenance

Data ONTAP Active/Active Configuration GuideConfiguring your SA system into a standardactive/active configuration


See...For information about...

Data ONTAP File Access and Protocols Management GuideMounting your root volume using NFS

Data ONTAP Network Management GuideConfiguring your network connections

Data ONTAP Upgrade GuideUpgrading your SA system

Support for 512-GB and 256-GB Performance Acceleration ModulesIn Data ONTAP 7.3.2 the 256-GB and 512-GB Performance Acceleration Module (PAM II) are supportedon a number of different systems.

Supported on these systems:Module typeData ONTAP Release

3170, 6040, and 6080512-GB Performance AccelerationModule

7.3.2

3070, 3140, and 3160256-GB Performance AccelerationModule

7.3.2

For more information, see Performance Acceleration Module and WAFL extended cache on page 49..

Support for 2 TB SATA disksIn Data ONTAP 7.3.2 and later releases, 2 TB SATA disks are supported for both the SAS and FC diskconnection types.

MultiStore enhancementsData ONTAP provides additional MultiStore capabilities.

Next topics

Online migration support on vFiler units on page 43

Commands supported by the ONTAPI interface library on page 44

Secure communication for setup of disaster recovery and data migration on page 44

SnapMover license is not required on page 44

Deduplication support on vFiler units on page 44

Online migration support on vFiler unitsStarting with Data ONTAP 7.3.3, MultiStore supports online migration of vFiler units. By using onlinemigration, users can migrate vFiler units without experiencing any disruption in data availability. Youmust use Provisioning Manager to perform online migration of vFiler units.


For more information about online migration of vFiler units, see the Provisioning Manager andProtection Manager Guide to Common Workflows for Administrators and the Provisioning Managerand Protection Manager Printable Help for use with DataFabric Manager® Server 4.0.

Commands supported by the ONTAPI interface libraryThe ONTAPI interface library, which is part of the Manage Data ONTAP solutions, supports somenew functions.

The following new functions are supported:

• Retrieve vFiler unit network settings such as the following:

• DNS domain name and DNS server IP addresses

• NIS domain name and NIS server IP address

• Netmask in IP address binding information

• Migrate the vFiler unit and view the status

• Set the snapshot reserve percentage values

• Get or set the optional descriptive comment for a LUN

Secure communication for setup of disaster recovery and data migrationMultiStore supports disaster recovery and data migration implemented over SSL. When setting up orcontrolling disaster recovery or data migration, SSL is used only for the setup and control communicationbetween storage systems running Data ONTAP. The data being migrated or copied is not encryptedusing SSL.

For more information, see the Data ONTAP MultiStore Management Guide.

SnapMover license is not requiredStarting with Data ONTAP 7.3.2, the SnapMover license is not required to use the vfiler migrate-m nocopy command.

Deduplication support on vFiler unitsData ONTAP 7.3.1 and later releases provide enhanced deduplication support on vFiler units.You canperform deduplication operations from the CLI of all vFiler units, in addition to the CLI of vfiler0.

For more information, see the Data ONTAP MultiStore Management Guide.


Manageability enhancementsData ONTAP 7.3 and later releases provide additional management capabilities using MultiStore,FilerView, and other tools.

Next topics

SSL security improvements on page 45

Nondisruptive upgrades for disk shelves controlled by AT-FCX modules on page 45

Changes to the upgrade preparation process on page 46

Improved support for nondisruptive upgrades in SAN environments on page 46

Upgrade Advisor planning tool on page 47

Read reallocation of data on page 47

Extents for FlexVol volumes on page 48

Option to disable root access to the storage system on page 48

Audit log enhancement on page 48

Read-only access to FilerView on page 49

Physical reallocation of data on page 49

Performance Acceleration Module and WAFL extended cache on page 49

FilerView enhancements on page 50

The e0M interface on page 50

Data ONTAP supports up to 24 SSH sessions on page 50

Only critical AutoSupport notifications are sent to the autosupport.to recipients on page 51

Partner recipients for AutoSupport email notifications on page 51

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

Nondisruptive upgrades for disk shelves controlled by AT-FCX modulesData ONTAP 7.3.1 introduces the ability to update the firmware for DS14mk2 AT disk shelves withAT-FCX modules without needing to schedule system downtime for maintenance.

Your system must meet the following requirements to upgrade AT-FCX firmware nondisruptively:

• Data ONTAP 7.3.1 or later is installed.

• Multipath HA Storage is configured.

• Firmware version 37 or later is running on all shelves with AT-FCX modules.

Attention: It is strongly recommended that AT modules run firmware version 37 or later.


Upgrading disk shelf firmware to version 37 or later from any version earlier than 36 requiresdowntime.

For more information about nondisruptive AT-FCX firmware upgrades, see the Data ONTAP UpgradeGuide.

Changes to the upgrade preparation processBeginning in Data ONTAP 7.3.1, there are new recommendations for obtaining and installing DataONTAP upgrade images.

In previous releases, there were several methods available for obtaining Data ONTAP upgrade imagesand installing system files on your system. Beginning with Data ONTAP 7.3.1, the following methodis recommended:

• Copy Data ONTAP .exe upgrade images to your storage system or an HTTP server on your network.

• Install and manage upgrade images with the software command family.

• Use the software update command to upgrade from Data ONTAP 7.2 and later releases.

• Use the software install command to upgrade from Data ONTAP 7.0.x and Data ONTAP7.1.x.

The software commands include checks and validations to help ensure an efficient upgrade.

The following processes and commands are deprecated beginning in Data ONTAP 7.3.1. They will notbe supported in later release families.

• The use of client-based extraction and installation toolsInstead of using the tar command on UNIX hosts or setup.exe files on Windows hosts, copythe upgrade .exe file to the storage system and install it with the software command.

• The use of the software install command on systems running Data ONTAP 7.2 and laterYou must use the software install command to update a system running releases in the DataONTAP 7.0 or 7.1 families. However, to upgrade from Data ONTAP 7.2 or later releases, you mustuse the software update command.

If you are running a version of Data ONTAP earlier than 7.0, you should upgrade to the latest releasein the Data ONTAP 7.0 or later release family before upgrading to 7.3.1 or later. This allows you totake advantage of the software command family, which was not available prior to Data ONTAP 7.0.

For more information, see the Data ONTAP Upgrade Guide.

Improved support for nondisruptive upgrades in SAN environmentsBeginning with Data ONTAP 7.3, you are no longer required to submit an environment qualificationform before performing a nondisruptive upgrade to a major release or within a release family in a SANenvironment.


Note: Before performing a nondisruptive upgrade in a SAN environment, be sure to prepare carefullyusing recommendations in the Data ONTAP Upgrade Guide.

If your systems are configured to send AutoSupport messages, you should also use the UpgradeAdvisor tool on the NOW site to plan your upgrade.

Related information

ONTAP Upgrade Advisor -- now.netapp.com/NOW/asuphome/

Upgrade Advisor planning toolThe Upgrade Advisor is an online tool, available on the NOW site, for all systems with a valid contractthat are configured to send AutoSupport messages.

When you submit your system identification and target release to the Upgrade Advisor, the tool comparesAutoSupport data about your system to known requirements and limitations of the target release. UpgradeAdvisor then generates an upgrade plan (and optionally a back-out plan) with recommended preparationand execution procedures.

The Upgrade Advisor dramatically simplifies the process of qualifying your environment for a successfulupgrade, and the automated mechanism significantly reduces the potential for human error.

For more information, see the AutoSupport home on the NOW site at http://now.netapp.com/.

You should use the Upgrade Advisor tool (if it is available in your environment) to ensure that youhave met the requirements for upgrading to the current release and to generate an upgrade plan.

For more information about the Upgrade Advisor, see the Data ONTAP Upgrade Guide.

Related information

ONTAP Upgrade Advisor -- now.netapp.com/NOW/asuphome/

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, Data ONTAPanalyzes the parts of the file that are read sequentially. If the associated blocks are not already largelycontiguous, Data ONTAP updates the file's layout by rewriting those blocks to another location on thedisk. The rewrite improves the file's layout, thus improving the sequential read performance the nexttime that section of the file is read.

For more information about the vol options read_realloc command, see the na_vol(1) man pageand the Data ONTAP System Administration Guide.


http://now.netapp.com/NOW/asuphome/

http://now.netapp.com/

http://now.netapp.com/NOW/asuphome/

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 and theData ONTAP System Administration Guide.

Option to disable root access to the storage systemBy default, the root account's access to the storage system is enabled. You have the option to disablethe root account's access to the storage system, preventing the root account from logging in to the systemor executing any commands.

To prevent the root account from logging in to the system or executing any commands, a non-root userwith the security-complete-user-control security capability can disable the root account'saccess by setting the new option security.passwd.rootaccess.enable to off.

To reset the security.passwd.rootaccess.enable option to on (the default) to enable root access,a user must first change the root account's password.

The option to enable or disable root access is supported if you access the storage system through Telnet,RSH, SSH, HTTP Admin, NDMP, or the serial console.

The option to enable or disable root access is not supported if you access the storage system throughthe RLM.

For more information about how to disable the root account's access to the storage system, see the DataONTAP System Administration Guide.

Audit log enhancementChanges made to configuration and registry files are now audited. Read-only APIs by default are notaudited, but you can enable auditing of read-only APIs with the auditlog.readonly_api.enableoption.

When a configuration changes, the audit log shows the following information:

• What configuration files were accessed

• When the configuration files were accessed

• What has been changed in the configuration files

For more information, see the Data ONTAP System Administration Guide.


Read-only access to FilerViewUsers with the new filerview-readonly capability have read-only access to FilerView and canview objects on a storage system that FilerView manages. These users are not able to add or modifyobjects through FilerView.


Physical reallocation of dataA physical reallocation (using the -p option of the reallocate start command) reallocates userdata on the physical blocks in an aggregate, while preserving the logical block locations within a FlexVolvolume. You can perform physical reallocation with FlexVol volumes or with files and LUNs withinFlexVol volumes.

Physical reallocation might reduce the extra storage requirements in a FlexVol volume when reallocationis run on a volume with Snapshot copies. It might also reduce the amount of data that needs to betransmitted by SnapMirror on its next update after reallocation is performed on a SnapMirror sourcevolume.

Physical reallocation is not supported on FlexVol volumes or on files and LUNs within FlexVol volumesthat are in an aggregate created by a version of Data ONTAP earlier than version 7.2.

Note: LUNs in this context refer to the LUNs that Data ONTAP serves to clients, not to the arrayLUNs used for storage on a storage array.

Note: A file reallocation scan using reallocate start or reallocate start -p does notrearrange blocks that are shared between files by deduplication on deduplicated volumes. Since afile reallocation scan does not predictably improve read performance when used on deduplicatedvolumes, performing file reallocation on deduplicated volumes is not recommended. Instead, forfiles to benefit from the reallocation scan, they should be stored on volumes that are not enabled fordeduplication.


Performance Acceleration Module and WAFL extended cacheYou can increase Write Anywhere File Layout (WAFL) cache memory in storage systems runningData ONTAP 7.3 and later by using WAFL extended cache and the Performance Acceleration Module(PAM) family. WAFL extended cache is a software component of Data ONTAP and requires a license.

WAFL extended cache provides extra WAFL cache memory to improve the performance of the storagesystem by reducing the number of the system's disk reads. The options flexscale commands enableyou to control how user data blocks are cached.

With WAFL extended cache and the Performance Acceleration Module family, your storage system'scache memory can hold up to 31 aggregates (which would mean 31 traditional volumes, if your system


uses only traditional volumes). As long as your storage system has fewer than 31 aggregates total, thereis no limit to the number of flexible volumes that can be cached by the WAFL extended cache.


FilerView enhancementsFilerView in Data ONTAP 7.3 and later releases supports NFS version 4 and provides enhancedmanagement capabilities.

Starting with Data ONTAP 7.3, you can perform the following tasks using FilerView:

• Enable viewing objects

• Create FlexCache volumes

• View reclaimable size of Snapshot copies

• Create aggregates with mutually compatible disks

For more information about these features, see the FilerView online Help.

The e0M interfaceAvailable on 31xx storage systems, the e0M interface is dedicated to Data ONTAP managementactivities. The e0M interface enables you to access the storage system remotely to perform administrativetasks. By using the e0M interface, you can separate management traffic from data traffic on the storagesystem for security and throughput benefits.

On 31xx storage systems, the Ethernet port that is indicated by a wrench icon on the rear of the chassisconnects to an internal Ethernet switch. The internal Ethernet switch then provides connectivity to thee0M interface and the Remote LAN Module (RLM). Because the e0M interface and the RLM eachhave unique IP and MAC addresses, the Ethernet switch is able to direct traffic to either the e0Minterface or the RLM.

You can use the e0M interface to access the storage system with these protocols: Telnet, RSH, SNMP,HTTP, and—if SecureAdmin is enabled—SSH.

For information on how to set up the e0M interface, see the Data ONTAP Software Setup Guide. Formore information about the e0M interface, see the Data ONTAP System Administration Guide and theData ONTAP Network Management Guide.

Data ONTAP supports up to 24 SSH sessionsStarting with Data ONTAP 7.3, the maximum number of SSH administrative sessions you can runconcurrently is increased to 24.


Only critical AutoSupport notifications are sent to the autosupport.to recipientsStarting with Data ONTAP 7.3, only critical AutoSupport email notifications are sent to the recipientsdefined in the autosupport.to option. Non-critical notifications are suppressed.

All AutoSupport notifications, regardless of their level of severity, continue to be sent to technicalsupport as displayed by the read-only option autosupport.support.to. All AutoSupport notificationsthat have been sent to technical support are accessible to you on the NOW site.

For more information about the AutoSupport options, see the na_options(1) man page.

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 or thesetting of the autosupport.support.enable option.

Using the autosupport.partner.to option, you can specify up to five email addresses for partnerrecipients to receive AutoSupport notifications. The email addresses should be entered as acomma-separated list with no spaces between them. By default, the autosupport.partner.to optionis 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.

Networking and security protocols enhancementsData ONTAP 7.3 and later releases provide enhanced network performance and security features.

Next topics

Support for IPv6 on page 52

Support for CDP on page 55

Transport Layer Security protocol on page 55

TLS support in FilerView on page 55

Port-based load-balancing option for multimode vifs on page 55

External cache group added to netapp.mib on page 55

Round-robin load balancing is supported on page 56

SNMPv3 supported on page 56


New maximum number of network interfaces on page 56

Support for IPv6Starting with Data ONTAP 7.3.1, IPv6 addressing is supported. You can enable IPv6 on your storagesystems, and IPv6 for various tasks such as to configure network interfaces, VLANs, and vifs; inactive/active configurations; and to support for other protocols, including CIFS, NFS, HTTP, FTP.

You can enable IPv6 on your storage system during setup. For more information, see the Data ONTAPSoftware Setup Guide.

You can also enable IPv6 on your storage system during operation by setting the optionsip.v6.enable option to on. For more information, see the Data ONTAP Network Management Guide.

IPv6 features in Data ONTAP 7.3.1

The following IPv6 features are supported starting with Data ONTAP 7.3.1:

• IPv6 dual stack mechanism to enable communication over IPv4 and IPv6

• Neighbor Discovery that includes Router Discovery and Duplicate Address Detection

• IPv6 stateless address autoconfiguration, requiring minimal manual configuration of hosts

• Internet Control Message Protocol version 6 (ICMPv6)

• Path MTU discovery for IPv6

• Transmission of IPv6 packets over Ethernet links

• IPv6 static routes and router alert option

• Support for IPv6 in network administration commands, such as the traceroute6, ping6, netdiag,and pktt commands

• Support for a Telnet server to accept IPv6 connection requests

• Syslog for the IPv6-related events

• Host name and address resolution with DNS, DDNS, and NIS over IPv6

• Configuring VLANs with IPv6 addresses

• Configuring single-mode, static multimode, and dynamic multimode (LACP) vifs with IPv6 acrossmultiple NICs

• Support for SNMP v1, SNMP v2c, and SNMP v3 over IPv6

• Management Information Base (MIB) for TCP, UDP, ICMPv6, and IPv6

• Active/active configuration support for IPv6, which includes takeover and giveback of IPv6 addressesand routes, mapping partner IPv6 interfaces, and executing commands with IPv6 addresses in thepartner contextFor more information, see the Data ONTAP Active/Active Configuration Guide.

• MultiStore support for IPv6 addresses as network resources that can be assigned to the vFiler units.IPv6 addresses are supported in the vfiler commandsFor more information, see the Data ONTAP MultiStore Management Guide.

• Support for iSCSI over IPv6


For more information, see the Data ONTAP Block Access Management Guide for iSCSI and FC.

• Support for file access protocols—CIFS, FTP, HTTP, NFSv2, NFSv3, and NFSv4—over IPv6For more information, see the Data ONTAP File Access and Protocols Management Guide.

• Support for LDAP and Kerberos v5 with IPv6

• IPv6 addresses can be used to connect to the storage system over HTTPS for secure administrativeaccessSecureAdmin SSL must be enabled before you can issue HTTPS requests to the storage system.

• To connect to the storage system for SSH protocol version 2 if IPv6 is enabledSecureAdmin SSH must be enabled before you can issue SSH requests to the storage system.

IPv6 feature in Data ONTAP 7.3.2

Starting with Data ONTAP 7.3.2, you can add SNMP traphosts with IPv6 addresses. You should specifyonly IPv6 addresses, and not host names, to identify IPv6 traphosts.

IPv6 features in Data ONTAP 7.3.3

Starting with Data ONTAP 7.3.3, you can use IPv6 addresses for the following functions:

• Fast path over IPv6For more information, see the Data ONTAP Network Management Guide.

• To connect to the RLM if you have set up and enabled IPv6 for Data ONTAP, your RLM firmwareversion is 4.0 or later, and you have configured the RLM for IPv6Disabling IPv6 on Data ONTAP also disables IPv6 on the RLM.

Note: Using IPv6 to connect to the BMC is currently not supported.

For information about installing and updating the RLM firmware, see the Data ONTAP UpgradeGuide.For information about configuring the RLM, see the Data ONTAP System Administration Guide.

• In the hwassist options if IPv6 is set up and enabled in Data ONTAP and IPv6 is enabled on theRLM.

• In MetroCluster configurations if IPv6 is set up and enabled in Data ONTAP

• To connect to the storage system over the RSH protocol if both the rsh.enable option and theip.v6.enable option are set to on

• To access FilerView for managing the storage system if both the ip.v6.enable option and thehttpd.ipv6.enable option are set to on.

Note: Internet Explorer 6.0 does not support IPv6. To access FilerView using IPv6, you mustuse Internet Explorer 7.

• For the dump, restore, and ndmpcopy commands over IPv6For more information, see the Data ONTAP Data Protection Tape Backup and Recovery Guide.

• Ipv6 is supported with SnapMirror, SnapVault, and volume copy.For more information, see the Data ONTAP Data Protection Online Backup and Recovery Guide.


IPv6 RFCs supported

Support for Internet Protocol version 6 (IPv6) in Data ONTAP is extended based on certain RFCs. Thefollowing table lists the RFCs supported for this release.

DescriptionRFC

NFSv2RFC 1094

NFSv3RFC 1813

NFSv4RFC 3530

DNS extensions to support IPv6RFC 1886

Path MTU Discovery for IPv6RFC 1981

DNS and DDNS for IPv6RFC 2136

Advanced Sockets API for IPv6RFC 2292

IPv6 specificationRFC 2460

Neighbor Discovery for IPv6RFC 2461

IPv6 Stateless Address AutoconfigurationRFC 2462

Transmission of IPv6 Packets over Ethernet NetworksRFC 2464

Management Information Base for IP Version 6: Textual Conventions and General GroupRFC 2465

Management Information Base for IP Version 6: ICMPv6RFC 2466

Basic Socket Interface Extensions for IPv6RFC 2553

IPv6 Router Alert OptionRFC 2711

Transition Mechanisms for IPv6 Hosts and Routers (Dual Stack Mode)RFC 2893

BSD Syslog Protocol (Syslog capabilities for IPv6-related events)RFC 3164

IPv6 Scoped Address ArchitectureRFC 4007

Management Information Base for the Transmission Control ProtocolRFC 4022

Management Information Base for the User Datagram ProtocolRFC 4113

Kerberos v5RFC 4120

Unique Local IPv6 Unicast AddressesRFC 4193

Secure Shell (SSHv2)RFC 4254

IPv6 Addressing ArchitectureRFC 4291

ICMPv6 for IPv6RFC 4443

LDAPRFC 4512


Support for CDPStarting with Data ONTAP 7.3.3, Cisco Discovery Protocol (CDP) is supported. CDP enables you toautomatically discover and view information about directly connected CDP-enabled devices in a network.

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

Transport Layer Security protocolData ONTAP 7.3.2 and later versions in the Data ONTAP 7.3 release family add support for TransportLayer Security (TLS) version 1.0, which provides better security protections than previous SSL versionsdid.

If you enable TLS on a storage system, you can use it with HTTPS, LDAP, and FTPS traffic, providedthat other required Data ONTAP options for HTTPS, LDAP, and FTPS are also enabled.

TLS is disabled by default, and setting up SSL does not automatically enable TLS. For informationabout how to enable TLS, see the Data ONTAP System Administration Guide.

TLS support in FilerViewFilerView in Data ONTAP 7.3.2 and later supports the Transport Layer Security (TLS) protocol.

To enable the TLS protocol on a storage system, you have to enable the TLS feature by settingtls.enable to on. The default value is off .

Note: Before setting the TLS feature, you have to enable Secure Sockets Layer (SSL). For moreinformation, see the Data ONTAP System Administration Guide.

Port-based load-balancing option for multimode vifsStarting with Data ONTAP 7.3.2, port-based load balancing is supported for multimode vifs. On amultimode vif, you can equalize egress traffic based on the transport layer (TCP or UDP) ports andnetwork layer (IPv4 or IPv6) 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 port number.

External cache group added to netapp.mibIn Data ONTAP 7.3.2, a new group, extcache, is added to the netapp.mib file . A managementutility can use this group to query the storage system for the status and statistics of the PerformanceAcceleration Module (PAM) card by using SNMP.

The object identifier (OID) of the extcache group is 1.3.6.1.4.1.789.1.26.X.0, where X is a field underthe extcache group.


For more information about the fields under the extcache group, see the latest netapp.mib file fromthe NOW site.

Round-robin load balancing is supportedData ONTAP 7.3.1.1 supports the round-robin load balancing option for multimode vifs. Load balancingensures that all the interfaces of a multimode vif are equally utilized for outgoing traffic.

You should use the round-robin option for load balancing a single connection's traffic across multiplelinks to increase single connection throughput . However, this method might cause out-of-order packetdelivery. If the remote TCP endpoints do not handle TCP reassembly correctly or lack sufficient memoryto store out of order packets, they may be forced to drop packets, and this can lead to unnecessaryretransmissions from the storage controller.

For more information about the other load balancing options available for multimode vifs, see the DataONTAP Network Management Guide.

SNMPv3 supportedData ONTAP 7.3 and later releases support SNMPv3, giving users security enhancements not availablein earlier versions of SNMP. Data ONTAP has also changed its netapp.mib file to conform to SNMPv2and SNMPv3 MIB guidelines. SNMPv3 supports a new "authentication, no privacy" privilege,counter64-based MIBs, and new client-side commands.

SNMPv3 includes these new features that work with Data ONTAP:

• An authentication, no privacy privilege using MD5

• Counter64-based MIBs, which reduce errors caused by having two entries that denote high and lowvalues for 64-bit variables

• These new client-side commands, are supported by SNMPv3:

• snmpbulkwalk displays all the leaves on an SNMP tree as a result of a single query

• snmpbulkget collects all the leaves on an SNMP tree as a result of a single query

For additional information about these features see the Data ONTAP Network Management Guide.

New maximum number of network interfacesBeginning with Data ONTAP 7.3, storage systems, except for the smallest models, are no longer limitedto 128 interfaces per storage system. Larger storage systems can accommodate from 256 to 1024 networkinterfaces per system depending on the system's memory and whether they are in a clustered oractive/active configuration.

Run the sysconfig command and refer to the Memory size field displayed for your storage system'sslot 0 system board to determine your storage system memory.


The new maximum number of network interfaces allowed for each system are shown in the followingtable. The total number of interfaces can include physical, vif, VLAN, vh, and loopback interfaces.

The number of physical interfaces depends on the storage system model. Each storage system cansupport up to 16 vifs. The maximum number of VLANs that can be supported equals the maximumnumber of network interfaces shown in the following table minus the total number of physical interfaces,vifs, vh, and loopback interfaces supported by the storage system.

Maximum number of network interfacesStorage system memory

1282 GB or less

2562 GB or less in an active/active configuration

2566 GB or less

5126 GB or less in an active/active configuration

512More than 6 GB

1024More than 6 GB in an active/active configuration

The number of physical interfaces depends on the storage system model. See your storage systemdocumentation for the number of supported physical interfaces.

File access protocol enhancementsData ONTAP 7.3 and later releases provide new features of NFSv4 and FPolicy, new commands fordebugging CIFS file access control problems, a new option for specifying the minimum levels ofauthentication and session security that clients must use, and compatibility with Windows Vista andWindows Server 2008.

For more information about these features, see the Data ONTAP File Access and Protocols ManagementGuide.

Next topics

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

Support for the SMB 2.0 protocol on page 58

Kerberos Multi Realm support on page 58

NFSv4 enhancements on page 58

Enhancements to NFS access cache management on page 59

Improved security for Perfmon connections on page 59

New commands for debugging CIFS access control problems on page 59

New option for setting the minimum authentication level and session security level that clientsmust use on page 60

FPolicy enhancements on page 60


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

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

In Data ONTAP 7.3.2 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 File Access and Protocols Management Guide.

Support for the SMB 2.0 protocolData ONTAP 7.3.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.

To support the SMB 2.0 protocol, Data ONTAP 7.3.1 and later include several new options. For moreinformation, see New options in Data ONTAP 7.3 on page 94 .


Kerberos Multi Realm supportIn Data ONTAP 7.3.1 and later releases, you can configure Data ONTAP to use a UNIX-based KDCfor NFS and an Active Directory-based KDC for CIFS. This configuration is called a Kerberos MultiRealm configuration.


NFSv4 enhancementsData ONTAP 7.3 and later releases provide new NFSv4 features and enhancements.

These are the new NFSv4 features:

• Support for nested export rules

• Support for Unicode

• Support for Kerberized callbacks

• Support for the fsecurity show command (displays ACLs on files and directories)

• Support for SKT_TRACE modules

These are the NFSv4 enhancements:

• Access to .snapshot entries from Solaris clients

• Support for the "nosuid" export rule

• Increase of the maximum size of ACLs from 192 to 400 ACEs

• More read and write parallelism in WAFL through Waffinity changes

• Delegation callback enhancements:


A new thread-pool is added for delegation callback.•

• Callbacks now use non-reserved ports.

• A rewritten reply cache that is now multi-processor (MP) enabled

• Resolution of issues with UID/GID name mapping, especially in regard to cluster failover (CFO)configurations

• Handling of Incoming UTF-8 strings as sym-link data

Enhancements to NFS access cache managementBeginning in Data ONTAP 7.3.3, the exportfs command includes updated options for managingentries in the NFS access cache.

The -c option of the exportfs command has been updated to take multiple IP addresses as arguments.This enables verification of current export rights for multiple clients in one operation.

The -f option of the exportfs command now includes a -n parameter, which allows you to flushaccess cache entries that correspond to a specific host.

For more information, see the exportfs(1) man page and the Data ONTAP File Access and ProtocolsManagement Guide.

Improved security for Perfmon connectionsBeginning in Data ONTAP 7.3.3, only administrative users are granted Perfmon connections to DataONTAP by default. Access for other users or groups must be defined explicitly.

In earlier releases, Data ONTAP did not check access permissions for connections from the MicrosoftPerfmon tool. As a result, any user could use Perfmon to access a storage system, view performancedata, and set counters, which could lead to security and performance problems.

Data ONTAP 7.3.3 and later releases include the cifs.perfmon.allowed_users option, whichtakes arguments that grant access only to specified users or groups. By default, no argument is set,which restricts access to Administrators only.

For more information about the cifs.perfmon.allowed_users option, see the options(1) manpage.

New commands for debugging CIFS access control problemsData ONTAP 7.3 and later releases provide new commands for debugging CIFS access control problems.

Commands for debugging CIFS access control problems include the sectrace add, sectraceremove, sectrace show, and sectrace print-status commands. For more information aboutthese commands, see the Data ONTAP File Access and Protocols Management Guide and thena_sectrace(1) man page.


New option for setting the minimum authentication level and session securitylevel that clients must use

Data ONTAP 7.3 and later releases provide a new option, cifs.LMCompatibilityLevel, for settingthe minimum authentication level and session security level that clients must use to access files on thestorage system.

For more information about this option, see the Data ONTAP File Access and Protocols ManagementGuide and the na_options(1) man page.

FPolicy enhancementsFPolicy for Data ONTAP 7.3.1 and later introduces a number of new features.

Following are the new features of FPolicy:

• Support for screening of certain CIFS operations on alternate data streams

• Support for registration of multiple FPolicy servers from a single IP address

• Support for screening of CIFS operations from SMB 2.0 clients

• Enhancements are made to the internal implementation of the FPolicy subsystem that improve theway multiple requests are handled in parallel. This is expected to improve the request processingthroughput of the FPolicy subsystem. The actual increase in throughput varies depending on thethird party FPolicy application server being used and on the load on the storage subsystem.

Maximum number of auxiliary UNIX groups supported for a userIf you use Kerberos V5 authentication, the maximum number of auxiliary UNIX groups that a user canbe 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) man page.

Block protocol enhancementsData ONTAP 7.3 and later releases provide additional capabilities using iSCSI and FCP protocols forNetApp SAN environments.

For more information about these features, see the Data ONTAP Block Access Management Guide foriSCSI and FC.


Next topics

Fibre Channel over Ethernet (FCoE) target expansion adapter support on page 61

Takeover and giveback performance enhancements in a SAN environment on page 61

Ability to delete backing Snapshot copies of deleted LUN clones on page 61

New default value for the maximum number of iSCSI connections per session on page 62

WWPN aliases on page 62

New windows_2008 LUN Multiprotocol Type (ostype) on page 62

New solaris_efi, xen, and hyper_v LUN Multiprotocol Types (ostypes) on page 62

Fibre Channel over Ethernet (FCoE) target expansion adapter supportData ONTAP 7.3.2 supports two new FCoE target expansion adapters, which extend Fibre Channelinto the Ethernet network and provide additional options for SAN connectivity.

The following adapters are supported:

• Optical - part number X1139A-R6

• Copper - part number X1140A-R6

For additional details, visit the FCoE SAN solutions Web site.

Related information

NetApp FCoE SAN solutions - http://www.netapp.com/us/products/protocols/fcoe/

Takeover and giveback performance enhancements in a SAN environmentTakeover and giveback times are significantly improved on systems with a large number of LUNs(between 500 and 2000) and systems under heavy I/O load in a SAN environment.

Note: LUNs in this context refer to Data ONTAP-served LUNs, not LUNs on third-party storage.

Ability to delete backing Snapshot copies of deleted LUN clonesStarting with Data ONTAP 7.3, you can enable a system to lock backing Snapshot copies of the activeLUN clone only. If you enable the locking of the active LUN clone only and then want to delete theactive LUN clone, you can delete the base Snapshot copy without having to first delete the more recentbacking Snapshot copies.

Before Data ONTAP 7.3, the system automatically locked all backing Snapshot copies when Snapshotcopies of LUN clones were taken.

To enable a system to lock backing Snapshot copies for the active LUN clone only, enter the followingcommand:

vol options volume_name snapshot_clone_dependency on

Note: The snapshot_clone_dependency option is set to off by default.


http://www.netapp.com/us/products/protocols/fcoe/

For more information, see the Data ONTAP Block Access Management Guide for iSCSI and FC.

New default value for the maximum number of iSCSI connections per sessionStarting with Data ONTAP 7.3, the default value for the maximum number of iSCSI connections persession is 32. You can change the default value by setting the iscsi.max_connections_per_secondoption to a value from 1 to 32. To change the option back to the default, set theiscsi.max_connections_per_session option to use_system_default.

WWPN aliasesWWPNs are identified by a unique, 64-bit identifier displayed as a 16-character hexadecimal value inData ONTAP. However, SAN administrators might find it easier to identify Fibre Channel ports usingan alias instead, especially in larger SANs.

Starting with Data ONTAP 7.3, you can use the wwpn-alias sub-command to create, remove, anddisplay WWPN aliases.

New windows_2008 LUN Multiprotocol Type (ostype)In Data ONTAP 7.3 and later, you can use the new windows_2008 Multiprotocol Type for WindowsServer 2008. You specify this LUN Multiprotocol Type by using windows_2008 as the value forostype.

If you are using Windows Server 2008 in conjunction with Data ONTAP, you must specify thewindows_2008 LUN Multiprotocol Type as the value of ostype to avoid performance problems.However, note that if you are using SnapDrive to create your LUNs, SnapDrive uses the windows_gptLUN Multiprotocol Type, but partitions the LUNs in a way that avoids performance problems.

Data ONTAP actually implements the windows_2008 LUN Multiprotocol Type to achieve the bestperformance with the standard partitioning.

Note: Future versions of SnapDrive will use the windows_2008 LUN Multiprotocol Type.

New solaris_efi, xen, and hyper_v LUN Multiprotocol Types (ostypes)Beginning in Data ONTAP 7.3.1, you can use the following new LUN Multiprotocol Types:solaris_efi, xen, and hyper_v.You specify the LUN Multiprotocol Type by using solaris_efi,xen, or hyper_v as the value for ostype.

Follow these guidelines when using the new LUN Multiprotocol Types:


When to useLUN Multiprotocol Type

If you are using Solaris EFI labels.

Note: Using any other LUN Multiprotocol Typewith Solaris EFI labels might result in LUNmisalignment problems. Refer to your Solaris HostUtilities documentation and release notes for moreinformation.

solaris_efi

If you are using Xen and your LUNs will be configuredwith Linux LVM with Dom0.

Note: For raw LUNs, use the type of guest operatingsystem as the LUN Multiprotocol Type.

xen

If you are using Windows Server 2008 Hyper-V andyour LUNs contain virtual hard disks (VHDs).

Note: For raw LUNs, use the type of child operatingsystem as the LUN Multiprotocol Type.

hyper_v

Data protection enhancementsData ONTAP 7.3 and later releases provide enhanced Snapshot data protection technologies (such asSnapMirror), tape backup support, and security administration.

For more information about these features, see the Data ONTAP Data Protection Online Backup andRecovery Guide and the Data ONTAP Data Protection Tape Backup and Recovery Guide.

Next topics

Use of SnapVault to protect a volume SnapMirror destination on page 64

TCP window size for a SnapMirror relationship on page 64

Retention of older SnapVault Snapshot copies on SnapVault secondary volumes on page 65

Compression for SnapMirror transfers on page 65

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

Snapshot copies and log files of SnapLock for SnapVault use system clock for naming on page 65

Changes to the SnapLock autocommit feature on page 66

Backing up LUN clones to tape on page 66

SnapLock supported in Data ONTAP 7.3.1 and later on page 66

LockVault now known as the SnapLock for SnapVault feature on page 66

More concurrent transfers for qtree SnapMirror, asynchronous volume SnapMirror, andSnapVault on page 67

Maximum number of concurrent replication operations with ATA disks on page 67


Reservation of storage system resources for volume SnapMirror, qtree SnapMirror, and SnapVaultreplication operations on page 67

Synchronous SnapMirror modes on page 68

Space guarantee for a volume SnapMirror destination on page 69

Support for SnapMirror over Fibre Channel on FAS2050 on page 69

SnapVault integration with SnapManager on page 70

SnapVault primary and secondary on the same storage system on page 70

Enhancements to SnapVault for NetBackup on page 70

Bandwidth optimization for Open Systems SnapVault on page 70

SnapVault for NetBackup supports basic block mode backups on page 70

SnapVault with deduplication on page 71

Deduplication metadata relocated on page 71

Deduplication configuration data relocated on page 71

Deduplication support on SnapLock volumes on page 71

Deduplication checkpoint feature on page 71

SnapLock support for vFiler units on page 72

Qtree SnapMirror with deduplication on page 72

Volume SnapMirror with deduplication on page 72

Limit on entries in the snapmirror.conf file for each storage system on page 72

Automatic schedule for deduplication on page 73

Use of SnapVault to protect a volume SnapMirror destinationIn Data ONTAP 7.3.2 and later releases in the Data ONTAP 7.3 release family, SnapVault supportsthe use of a user-specified Snapshot copy for backing up a volume SnapMirror destination.

Note: To be able to specify a Snapshot copy for the SnapVault backup of a SnapMirror destination,you need to preserve the Snapshot copy.

For more information about the use of SnapVault for backing up a volume SnapMirror destination, seethe Data ONTAP Data Protection Online Backup and Recovery Guide.

TCP window size for a SnapMirror relationshipData ONTAP 7.3.2 and later releases in the Data ONTAP 7.3 release family support TCP window sizesupto 14 MB for a multipath SnapMirror relationship. This option is applicable only for asynchronousSnapMirror relationships.

Note: You should only adjust the TCP window size for a SnapMirror relationship, if there arethroughput issues related to bandwidth utilization.

For more information about adjusting the TCP window size for a SnapMirror relationship, see the DataONTAP Data Protection Online Backup and Recovery Guide.


Retention of older SnapVault Snapshot copies on SnapVault secondaryvolumes

In Data ONTAP 7.3.2 and later, you can retain SnapVault Snapshot copies on SnapVault secondaryvolumes.

You enable the preservesnap or preserve option to retain SnapVault Snapshot copies on SnapVaultsecondary volumes. When you enable this option, SnapVault does not delete an older Snapshot copyto create a new Snapshot copy when the maximum retention limit is reached. In such a case, you canmanually delete some Snapshot copies to make space available for new Snapshot copies. You can alsoclone the volume to create new Snapshot copies on this new volume while preserving the older Snapshotcopies intact on the old base volume.

For more information about retaining older SnapVault Snapshot copies on SnapVault secondary volumes,see the Data ONTAP Data Protection Online Backup and Recovery Guide.

Compression for SnapMirror transfersData ONTAP 7.3.2 and later releases in the Data ONTAP 7.3 release family support compression forvolume SnapMirror transfers. This feature is supported only for asynchronous volume SnapMirror.

Note: The SnapMirror destination system should be using Data ONTAP 7.3.2.

The compression feature of SnapMirror enables data compression over the network for SnapMirrortransfers. It helps in optimizing network bandwidth utilization between SnapMirror source and destinationsystems. This feature can be especially useful for connections that have relatively low bandwidth, suchas WAN connections.

For more information about the compression feature for volume SnapMirror, see the Data ONTAP DataProtection Online Backup and Recovery Guide.

If volumes with deduplication exceed the maximum supported sizeIn Data ONTAP 7.3.2, volumes continue to be online when they exceed the maximum supported size.However, deduplication is disabled on such volumes. For more information about the maximum volumesize allowed for different storage systems, with and without deduplication, see the Data ONTAP StorageManagement Guide.

Snapshot copies and log files of SnapLock for SnapVault use system clockfor naming

Starting with Data ONTAP 7.3.2, the time value specified in the names of the Snapshot copies and thelog files that are created by the SnapLock for SnapVault feature uses the system clock instead ofcomplianceclock.

For more information, see the Data ONTAP Archive and Compliance Management Guide.


Changes to the SnapLock autocommit featureStarting with Data ONTAP 7.3.2, the SnapLock autocommit operation uses the system clock to commita file to the WORM state.

For more information about this feature, see the Data ONTAP Archive and Compliance ManagementGuide.

Backing up LUN clones to tape

When you back up data to tape, the dump command will not back up the LUN clones that are inconsistent.

For all other LUN clones, the dump command will lock their backing Snapshot copies to ensure thatthey do not become inconsistent during the backup.

Note: LUNs in this context refer to Data ONTAP served LUNs, not LUNs on third-party storage.

SnapLock supported in Data ONTAP 7.3.1 and laterData ONTAP 7.3.1 and later supports SnapLock, with new features.

In Data ONTAP 7.3.1 and later, you can create SnapLock Enterprise and SnapLock Compliance volumeson a storage system.

SnapLock includes the following new features in Data ONTAP 7.3.1 and later:

• Privileged delete

• SnapLock logging

• Fingerprinting

SnapLock supports the following Data ONTAP features :

• Deduplication

• vFiler unit

For more information about these features, see the Data ONTAP Archive and Compliance ManagementGuide and the Data ONTAP Upgrade Guide.

LockVault now known as the SnapLock for SnapVault featureStarting with Data ONTAP 7.3.1, the LockVault feature is known as the SnapLock for SnapVaultfeature.


More concurrent transfers for qtree SnapMirror, asynchronous volumeSnapMirror, and SnapVault

In Data ONTAP 7.3 and later, qtree SnapMirror, asynchronous volume SnapMirror, and SnapVaulteach support a higher number of concurrent transfers. However, Open Systems SnapVault does nothave a higher limit of concurrent transfers.

For details, see the Data ONTAP Data Protection Online Backup and Recovery Guide.

Maximum number of concurrent replication operations with ATA disksIn Data ONTAP 7.3 and later, the use of ATA disks does not affect the maximum number of concurrentreplication operations a storage system can perform.

For more information, see the topic about Data protection using SnapMirror in the Data ONTAP DataProtection Online Backup and Recovery Guide.

Reservation of storage system resources for volume SnapMirror, qtreeSnapMirror, and SnapVault replication operations

In Data ONTAP 7.3 and later, you can reserve resources for a specific number of volume SnapMirror,qtree SnapMirror, or SnapVault replication operations on a storage system. The reserved resources arenot available for other types of replication.

For example, if you reserve a specified number of volume SnapMirror replication operations, theresources required for the operations are set aside on the storage system. This means that a volumeSnapMirror replication operation for the storage system, acting as a source or a destination, is guaranteedto start until the specified limit of reserved operations is met. It also means that the maximum numberof operations for other types of replication, such as qtree SnapMirror or SnapVault, would be reducedin order to keep the resources free for volume SnapMirror replication operations.

Note: If the total number of concurrent replication operations is below the maximum limit, thestorage system runs more of the replication operations, above the limit reserved for a specific typeof replication until the total number of such operations has reached its maximum.

You can specify the number of reserved transfers using one of the following commands:

For volume SnapMirror:

options replication.volume.reserved_transfers n

For qtree SnapMirror and SnapVault:

options replication.logical.reserved_transfers n

n is the number of reserved transfers. The default value of n is 0.


Synchronous SnapMirror modesIn Data ONTAP 7.3 and later, the outstanding parameter is not used for semi-synchronous SnapMirrorconfigurations.

• This change affects the snapmirror.conf file syntax.

• This change does not affect synchronous SnapMirror configurations.

• This change does not disrupt the operation of storage systems.

A new option called semi-sync replaces the outstanding parameter. This new option provides arecovery point objective of approximately 10 seconds. This means that you might lose the data updatedin the last 10 seconds or less. This change is intended to optimize performance.

Therefore, starting with Data ONTAP 7.3 and later, synchronous SnapMirror is available in two modes:

• SnapMirror Sync: The source storage system acknowledges a client write operation only after boththe source and destination storage systems have completed the write operation.

• SnapMirror Semi-Sync: The source storage system acknowledges the client write operationimmediately after the source receives the data. The destination storage system is synchronized withthe source at intervals of approximately 10 seconds.

To avoid disrupting the existing configuration, SnapMirror interprets the old outstanding options asfollows:

• If the outstanding parameter is set as less than 10 seconds or less than 500 operations, therelationship is converted to SnapMirror Sync (equivalent to sync in the /etc/snapmirror.conffile).For example, these might be two entries in the /etc/snapmirror.conf file.

systemA:vol-1 systemB:vol-2 outstanding=1s sync

systemA:vol-1 systemB:vol-2 outstanding=200ops sync

Either of the two preceding entries, would be interpreted as this command:

systemA:vol-1 systemB:vol-2 - sync

• If the outstanding parameter is set as more than or equal to 10 seconds, or more than or equal to500 ops, the relationship is converted to SnapMirror Semi-Sync (equivalent to sync in the/etc/snapmirror.conf file).For example, these are two entries in the /etc/snapmirror.conf file.

systemA:vol-1 systemB:vol-2 outstanding=10s sync

systemA:vol-1 systemB:vol-2 outstanding=500ops sync

Either of the two preceding entries, would be interpreted as:

systemA:vol-1 systemB:vol-2 - semi-sync

Note: SnapMirror does not modify the content of the snapmirror.conf file.


Space guarantee for a volume SnapMirror destinationStarting with Data ONTAP 7.3, you can enable space guarantee for a SnapMirror destination FlexVolvolume. This feature enables you to reserve space in an aggregate for a SnapMirror destination volume.

Data ONTAP 7.0 and later releases support space guarantees for FlexVol volumes. Data ONTAP 7.3extends this feature to SnapMirror destination volumes.

When you upgrade a volume SnapMirror destination to Data ONTAP 7.3, the volume guarantees arenot set for the SnapMirror destination volumes. This is indicated by upgraded_replica, listed as oneof the options displayed for the volume, when you use the vol status command.

system-b> vol status sm-dst-vol Volume State Status Options sm-dst-vol online raid_dp, flex snapmirrored=on, snapmirrored upgraded_replica, read-only fs_size_fixed=on, guarantee=volume(disabled) Containing aggregate: 'aggr2'

You can change the space guarantee for the volume by using the following command.

vol options vol_name guarantee {none | file | volume}

system-b> vol options sm-dst-vol guarantee volume

If you use the vol status command for the volume after setting the space guarantee, theupgraded_replica option will not be displayed.

system-b> vol status sm-dst-vol Volume State Status Options sm-dst-vol online raid_dp, flex snapmirrored=on, snapmirrored fs_size_fixed=on, read-only guarantee=volume, Containing aggregate: 'aggr2'

For more information about volume space guarantees, see the Data ONTAP Storage ManagementGuide.

Note: In a volume SnapMirror relationship, you can enable volume guarantees for both the sourceand the destination volumes.

As releases earlier than Data ONTAP 7.3 do not support space guarantees for a volume SnapMirrordestination, reverting to an earlier release would make the guarantees ineffective.

Support for SnapMirror over Fibre Channel on FAS2050In Data ONTAP 7.3.1 and later releases, SnapMirror over Fibre Channel is supported for FAS2050.You need to add an X1124 Fibre Channel adapter to use this feature.

For more information about hardware support, see the System Configuration Guide.


SnapVault integration with SnapManagerData ONTAP 7.3 and later provide disk-to-disk backup and restore functionalities for SnapManagerby integrating SnapVault functionality with SnapManager 5.0 and later and with SnapDrive 6.0 forWindows and later. You need Protection Manager to make this solution work. SnapManager usesSnapDrive as a conduit to support Protection Manager retention policies and schedules. Starting withData ONTAP 7.3, the SnapVault restore functionality provides nondisruptive baseline and incrementalrestores. This new functionality is exported to SnapManager using Data ONTAP APIs.

SnapVault primary and secondary on the same storage systemIn Data ONTAP 7.3 and later, the SnapVault primary and secondary feature can be on the same storagesystem. This capability allows customers to license both the SnapVault primary license and the SnapVaultsecondary license on the same storage system.

A storage system licensed for both the SnapVault primary license and the SnapVault secondary licensecan send and receive SnapVault backups from other storage systems or locally within itself (for example,between FC and ATA aggregates).

Note: The primary and secondary qtrees cannot be within the same volume of the storage system.

Enhancements to SnapVault for NetBackupSnapVault for NetBackup is available and supported beginning with Data ONTAP 7.3.

Several significant improvements have been made to SnapVault for NetBackup. The following are thekey enhancements:

• PerformanceWrite throughput rates, for both unstructured (file) data, significantly improved over earlier versions

• Improvements in metadata storage efficiency

• Support for active-active storage controller configurations

Bandwidth optimization for Open Systems SnapVaultBeginning with Data ONTAP 7.3, the SnapVault secondary storage systems support bandwidthoptimization for Open Systems SnapVault. However, qtree SnapMirror, volume SnapMirror, andSnapVault do not support bandwidth optimization.

SnapVault for NetBackup supports basic block mode backupsStarting with Data ONTAP 7.3.1, SnapVault for NetBackup supports basic block mode backups.

Basic block mode backups provide speed and inline deduplication capabilities of regular File SystemExport (FSE) mode backups without exposing the file system for export.


For more information about this feature, see the Data ONTAP Data Protection Online Backup andRecovery Guide.

SnapVault with deduplicationIn Data ONTAP 7.3 and later, the deduplication feature is integrated with SnapVault. Every baselineor incremental SnapVault transfer initiates a deduplication operation after the archival Snapshot copyis taken on the destination system.

Deduplication metadata relocatedIn Data ONTAP 7.3 and later, the fingerprint database and the change logs used by the deduplicationprocess are located outside the volume, in the aggregate. The fingerprint database and the change logsform the deduplication metadata. Because the metadata resides in the aggregate outside the volume, itis not included in the FlexVol volume Snapshot copies. This change enables deduplication to achievehigher space savings.

For information about the use of SnapMirror for replicating volumes that use deduplication, see theData ONTAP Data Protection Online Backup and Recovery Guide.

Deduplication configuration data relocatedIn Data ONTAP 7.3 and later, the deduplication configuration data for a given volume is located in ametafile within the volume. (Previously, it was located in the registry in the root volume.) This changehelps volume-level operations such as volume SnapMirror, snap restore, vol copy, and volclone to keep the deduplication configuration data about the volume on the destination consistent withthe source.

Deduplication support on SnapLock volumesBeginning with Data ONTAP 7.3.1, deduplication is supported on SnapLock volumes.

However, if deduplication is enabled on a SnapLock volume and you attempt to revert to a Data ONTAPrelease that does not support deduplication on SnapLock volumes, you will see an error message. Toavoid or recover from this situation, contact technical support.

Deduplication checkpoint featureThe checkpoint feature is used to log the execution process of a deduplication operation periodically.

When a deduplication operation is stopped for any reason and a checkpoint data exists, the samededuplication process can resume from the latest checkpoint file.


SnapLock support for vFiler unitsStarting with Data ONTAP 7.3.1, SnapLock is compatible with vFiler units. However, SnapLockdisallows vFiler unit creation if the root of the vFiler unit is on a SnapLock volume. The privilegeddelete feature is also not supported on the vFiler units.

For more information, see the Data ONTAP Archive and Compliance Management Guide.

Qtree SnapMirror with deduplicationIn Data ONTAP 7.3 and later, the deduplication feature supports qtree SnapMirror. Qtree SnapMirrordoes not automatically initiate a deduplication operation at the completion of every individual qtreeSnapMirror transfer. You can set up a deduplication schedule independent of your qtree SnapMirrortransfer schedule.

When using qtree SnapMirror with deduplication, remember the following:

• To use deduplication with qtree SnapMirror, you should enable both deduplication and SnapMirrorlicenses.

• Deduplication can be enabled on the source system, the destination system, or both systems.

• The source system sends duplicate blocks to the destination system even if deduplication is enabledon the source system.Therefore, there are no network bandwidth savings.

• The deduplication schedule is not tied to a qtree SnapMirror update and can be configured just likethe deduplication schedule for any volume.

Volume SnapMirror with deduplicationIn Data ONTAP 7.3 and later, the fingerprint database and the change logs that the deduplication processuses are located outside a volume, in its aggregate. Therefore, volume SnapMirror does not transferthem to a destination. This change provides additional network bandwidth savings.

Limit on entries in the snapmirror.conf file for each storage systemThe limit on the number of valid entries for each storage system in the /etc/snapmirror.conf fileis increased to 1,024.

Note: This limitation is different from the maximum number of concurrent replications you canhave on a storage system.

For more information, see the SnapMirror chapter in the Data ONTAP Data Protection Online Backupand Recovery Guide.


Automatic schedule for deduplicationDeduplication runs automatically when the number of blocks added or changed since the lastdeduplication operation exceeds a specified percentage (20 percent by default) of the total number ofblocks that the deduplication operation has already processed. Starting with Data ONTAP 7.3.2, youcan configure this percentage value by using the sis config -s auto@num /vol/volname command.Here, num is a two-digit number to specify the percentage.

Storage resource management enhancementsData ONTAP 7.3 and later releases provide improved performance, resiliency, and managementcapabilities for storage resources.

Next topics

FlexClone files and FlexClone LUNs on page 73

Aggregate size calculation changes on page 73

SnapMirror destination space guarantee not disabled on page 75

Autogrow capability for FlexCache volumes on page 75

Support for changing to software-based disk ownership nondisruptively on page 76

Disconnected operation for FlexCache volumes on page 76

FlexClone files and FlexClone LUNsStarting with Data ONTAP 7.3.2, you can clone files and LUNs inside a FlexVol volume using theFlexClone technology. You can clone a LUN without the need of a backing Snapshot copy. A clonedfile is called a FlexClone file and a cloned LUN is called a FlexClone LUN.

In Data ONTAP 7.3.1, the FlexClone files and FlexClone LUNs feature commands are available in thepriv set advanced mode. Starting with Data ONTAP 7.3.2, the feature commands are available inthe admin mode.

For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP StorageManagement Guide.

Aggregate size calculation changesIn Data ONTAP 7.3 and later releases, the total size of an aggregate is computed using the usable sizeof its data disks rather than the raw size of all of its disks.

In previous releases of Data ONTAP, the total size of an aggregate was computed by adding togetherthe raw size of all disks in the aggregate, including parity disks, and regardless of the amount of diskspace available to be used in each data disk. This method of computing the aggregate size could result


in an aggregate exceeding the maximum allowable size even though the amount of usable space in thataggregate was much smaller than the maximum allowable aggregate size.

In Data ONTAP 7.3 and later releases, only the "used size" (as reported by the sysconfig -r command)of data disks is used to calculate the total aggregate size. If you were prevented from adding disks toan aggregate due to aggregate size constraints in an earlier version of Data ONTAP, you might be ableto add more disks to that aggregate after upgrading to Data ONTAP 7.3.

Maximum number of data disks per 16-TB aggregate

With the aggregate size calculation changes present in Data ONTAP 7.3, you can include more datadisks in an aggregate without exceeding the aggregate size limit.

The following table shows the maximum number of data disks that can be included in a 16-TB aggregatefor Data ONTAP 7.3 and for previous releases.

Maximum with DataONTAP 7.3

Maximum with DataONTAP 7.2 and earlier

RAID groups <= 16Data disk typeData disk size

493421FC36 GB

246212FC72 GB

123106FC/SAS144 GB

6151FC/SAS300 GB

4033FC/SAS450 GB

7968SATA250 GB

6153SATA320 GB

3933SATA500 GB

2622SATA750 GB

1915SATA1 TB

9N/ASATA2 TB

Note: Not all disk sizes are supported in all versions of the Data ONTAP release family. See theSystem Configuration Guide for information about what disk sizes are supported for a specific versionof Data ONTAP.


SnapMirror destination space guarantee not disabledIn Data ONTAP 7.3 and later releases, the space guarantee on SnapMirror destination FlexVol volumesis no longer automatically disabled. If you are upgrading the storage system to Data ONTAP 7.3, andyou have existing SnapMirror destination volumes, you need to enable the guarantee on these volumes.

Starting in Data ONTAP 7.3, when you designate a FlexVol volume as a SnapMirror destination volume,its space guarantee remains enabled.

When you upgrade a system to Data ONTAP 7.3 with an existing FlexVol volume that is a SnapMirrordestination with a disabled space guarantee that was originally of type volume, the vol statuscommand displays the new volume option upgraded_replica. This option indicates that the spaceguarantee on this volume, originally of type volume, was disabled because the volume was used as aSnapMirror destination in a Data ONTAP version earlier than 7.3.

If you have sufficient space in the volume's containing aggregate, you can use the vol option commandto change the space guarantee to either volume or none. When you make that change, theupgraded_replica volume option disappears.

Autogrow capability for FlexCache volumesIn Data ONTAP 7.3 and later releases, FlexCache volumes can be configured to increase their sizeautomatically as the size of the cached data increases.

In earlier releases, the best way to size a FlexCache volume to avoid performance issues due to incorrectsizing was to size all FlexCache volumes to be the same size as their containing aggregate. With DataONTAP 7.3, however, you should size new FlexCache volumes to use the automatic resizing capability.

With this new capability enabled, Data ONTAP automatically increases the size of the FlexCachevolume when the size of the working set becomes too large for the current size of the FlexCache volume.

Data ONTAP never decreases the size of the FlexCache volume. However, as for previous releases ofData ONTAP, if there is contention between FlexCache volumes for free space, the FlexCache volumeswith the most data accesses are allocated more space, while FlexCache volumes that are accessed lessfrequently are truncated. When a FlexCache volume is truncated, no data is lost.

New FlexCache volumes created in Data ONTAP 7.3 and later releases have the Autogrow capabilityenabled by default. If necessary, you can use the vol options command to disable theflexcache_autogrow option.

FlexCache volumes created using an earlier version of Data ONTAP, and then upgraded to Data ONTAP7.3, have the Auotgrow capability disabled by default. If you want to enable it, you can use the voloptions command to enable the flexcache_autogrow option.

Note: If you have sized your FlexCache volumes to be the same size as their containing aggregatein a previous release and you are satisfied with the configuration, you do not need to reconfigurethese FlexCache volumes to use the new automatic resizing capability.


For more information about the FlexCache Autogrow capability, see the Data ONTAP StorageManagement Guide.

Support for changing to software-based disk ownership nondisruptivelyStarting with Data ONTAP 7.3.1, you can change an active/active configuration from hardware-baseddisk ownership to software-based disk ownership without having to take both nodes of an active/activeconfiguration offline at the same time. Future versions of Data ONTAP will not support hardware-baseddisk ownership.

Disconnected operation for FlexCache volumesIn Data ONTAP 7.3.1 and later releases, a FlexCache volume can be configured to return cached dataeven when it has lost its connection to its origin volume. You can configure how long the disconnectedFlexCache volume serves potentially stale data. Connection to the origin volume should be reestablishedas quickly as possible.

For more information, see the information about the flex_cache volume options on the na_vol(1)man page.

Active/active enhancementsData ONTAP 7.3 and later releases include the new Multipath Storage feature and additionalMetroCluster support.

For more information about these features, see the Data ONTAP Active/Active Configuration Guide.

Next topics

Support for 672 disk drives on fabric-attached MetroClusters on page 76

MetroCluster nodes on separate subnets on page 76

Hardware-assisted takeover on page 77

Deduplication support on stretch and fabric-attached MetroClusters on page 77

Support for 672 disk drives on fabric-attached MetroClustersStarting with the Data ONTAP 7.3.2 release, fabric-attached MetroCluster configurations can supportup to 672 disk drives (if that is within the maximum storage capacity of the system).

For more information, see the Data ONTAP Active/Active Configuration Guide.

MetroCluster nodes on separate subnetsStarting with the Data ONTAP 7.3.2, nodes in a MetroCluster configuration can be configured onseparate subnets.


To do this, you must create an /etc/mcrc file and enable the cf.takeover.use_mcrc_file optionon both nodes.


Hardware-assisted takeoverIn the Data ONTAP 7.3 release family, active/active configurations support hardware-assisted takeover.Hardware-assisted takeover allows systems with Remote LAN Modules (RLMs) to improve the speedwith which takeover events are detected, thereby speeding up the takeover time.

Note: The hardware-assisted takeover feature is available only on systems that support Remote LANModules (RLMs) and have the RLM installed and set up. It is not supported on the FAS20xx systems,which use the Baseboard Management Controller (BMC) as a remote management card.

When enabled, hardware-assisted takeover takes advantage of the remote management card's capabilitiesto detect failures on the local machine that could require a takeover. If a failure is detected, the cardsends an alert to the partner node and the partner, if the failure is of a certain type, performs a takeover.These alerts can speed takeover, because if an alert is received, the Data ONTAP takeover process onthe partner does not have to take the time to verify that the failing system is no longer giving a heartbeatand confirm that a takeover is actually required.

The hardware-assisted takeover option (cf.hw_assist) is enabled by default. The cf hw_assiststatus and cf hw_assist stats commands display information about the hardware-assistedtakeover functionality, and the cf hw_assist test command tests the functionality.


Deduplication support on stretch and fabric-attached MetroClustersData ONTAP 7.3.1 and later releases support deduplication on stretch and fabric-attached MetroClusters.This support applies to FAS and V-Series systems.

For more information about deduplication support on active/active configurations and MetroClusters,see the Data ONTAP Data Protection Online Backup and Recovery Guide and TR-3505, NetAppDeduplication for FAS Deployment and Implementation Guide.

Related information

TR-3505, NetApp Deduplication for FAS Deployment and Implementation Guide

V-Series enhancementsData ONTAP 7.3 and later provides enhancements specific to V-Series systems. Other Data ONTAPenhancements also apply to V-Series systems unless otherwise noted.


http://media.netapp.com/documents/tr-3505.pdf

Next topics

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

V-Series support for native disk shelves on page 78

V-Series support for deduplication on page 79

V-Series support for IBM DS5100 and DS5300 storage arrays on page 79

V-Series support for RamSan storage on page 79

Changes to the V-Series and Data ONTAP 7.3.2 librariesThe V-Series 7.3.2 guides now focus primarily on planning for and setting up a V-Series system witha third-party storage array. Most V-Series specific information about Data ONTAP features has beenintegrated into the general Data ONTAP guides.

For Data ONTAP 7.3.2, a new V-Series Installation Requirements and Reference Guide replaces thefollowing two guides:

• V-Series Planning Guide

• V-Series Installation Requirements, Quick Start, and Reference Guide

Previously, V-Series customers had to use both the Data ONTAP guides and the V-Series guides tofind all the information they needed to set up many of the Data ONTAP features on a V-Series system.Starting with Data ONTAP 7.3.2, most V-Series specific information about Data ONTAP features hasbeen integrated into most of the general Data ONTAP documents. Most V-Series documents now focusprimarily on information about implementation with the back-end storage arrays.

Examples of integration of V-Series information into the Data ONTAP guides are as follows:

• The Data ONTAP Storage Management Guide now includes V-Series specific information aboutdisk ownership, creating and managing aggregates and volumes, and managing array LUNs.

• The Data ONTAP Data Protection and Online Backup Guide contains a new section aboutrequirements for using SyncMirror with third-party storage.

• The Data ONTAP Upgrade Guide provides upgrade information for all systems that run DataONTAP.

Note: In Data ONTAP 7.3.2, there is still a separate setup guide for V-Series.

V-Series support for native disk shelvesStarting with Data ONTAP 7.3, V-Series expands its support matrix to include storage for native diskshelves and native disks.

Starting with Data ONTAP 7.3, V-Series can virtualize storage from both third-party storage arrayvendors and native disk shelves. The Data ONTAP software provides a unified storage software platformthat simplifies managing both native disk shelves and LUNs on storage arrays. You can add storagewhen and where you need it, without disruption.


See the V-Series Implementation Guide for Native Disk Shelves for additional information about thisfeature.

V-Series support for deduplicationIn Data ONTAP 7.3 and later, you can use the deduplication feature on a V-Series system with aNearStore license. The checksum type you can use with deduplication on a V-Series system is restricted.

Only block checksum type (BCS) is supported with deduplication on a V-Series system. Zoned checksumtype is not supported.

See the Data ONTAP Data Protection Online Backup and Recovery Guide for more information aboutNearStore configuration.

V-Series support for IBM DS5100 and DS5300 storage arraysStarting in Data ONTAP 7.3.1, V-Series supports IBM DS5100 and DS5300 storage arrays.

The configuration settings that are required to work with V-Series systems are the same for the DS5100,DS5300, and DS4xxx storage arrays. See the information about the DS4xxx storage arrays in theV-Series Implementation Guide for IBM Storage to determine what settings to configure on the DS5100or DS5300 storage arrays.

Data ONTAP considers the DS5100 and DS5300 storage arrays to be in a different storage array familythan the DS4xxx models. Therefore, you should not mix array LUNs from a DS5100 or DS5300 in thesame aggregate with LUNs from other IBM storage array models (or with LUNs from other vendors).

V-Series support for RamSan storageStarting in Data ONTAP 7.3.1, V-Series supports the RamSan-500 storage array.

The RamSan-500 storage array is an enterprise-class storage array based on RAID-protected flashstorage. A RamSan-500 uses solid state disk storage rather than disk-based storage (spinning disks).

For details, see the the V-Series Implementation Guide for RamSan Storage. See the V-Series SupportMatrix for information about the V-Series platforms and switches that are supported with theRamSan-500.


New and changed commands and options in theData ONTAP 7.3 release family

This section provides information about the commands, options, and configuration files that have beenchanged in or added to the Data ONTAP 7.3 release family.

Next topics

New commands in Data ONTAP 7.3 on page 81

Changed commands in Data ONTAP 7.3 on page 85

New options in Data ONTAP 7.3 on page 94

Changed options in Data ONTAP 7.3 on page 100

Replaced or removed commands in Data ONTAP 7.3 on page 101

New commands in Data ONTAP 7.3Commands have been added for FPolicy options and IPv6. There are also new commands to enablenew storage system features and to improve file access, block access, data protection, and storageresources management.

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 7.3 release in which the command was introduced

Release introducedDocumentationPurposeCommand

7.3.2Data ONTAP StorageManagement Guide

na_acpadmin(1) manpage

Displays information about the ACP(Alternate Control Path) storagesubsystem.

acpadmin list_all

7.3.3Data ONTAP NetworkManagement Guide

Displays information about devicesthat advertise themselves by usingthe CDPv1 protocol.

cdpd

7.3Data ONTAPActive/ActiveConfiguration Guide

Displays statistics abouthardware-assisted takeovers.

cf hw_assist stats

New and changed commands and options in the Data ONTAP 7.3 release family | 81



Displays status and statistics for thehardware-assisted takeover feature,and can test the feature.

cf hw_assist

status


Sends a test alert to the partner toverify operation of thehardware-assisted takeover feature.

cf hw_assist test


na_clone(1) man page

Clears the status of a failedFlexClone file or FlexClone LUNoperation.

clone clear



Creates a FlexClone file orFlexClone LUN of a parent file orLUN inside a FlexVol volume.

clone start



Views the status of all FlexClonefiles or FlexClone LUNs operationscurrently running, FlexCloneoperations that failed, and thereason for the failure.

clone status



Stops a FlexClone file or FlexCloneLUN operation.

clone stop

7.3.1Data ONTAP Archiveand ComplianceManagement Guide

Calculates the fingerprint of the fileusing md5 or sha-256 digestalgorithm.

file fingerprint

7.3na_fpolicy(1) manpage

Displays the status of all the FPolicyservers that are registered to the filepolicy.

fpolicy servers

show

7.3.1na_ndp(1) man pageControls or diagnoses IPv6 neighbordiscovery protocol.

ndp

7.3.3na_nfs(1) man pageFlushes specified entries from thename server database cache(NSDB).

nfs nsdb flush

7.3.1Data ONTAP NetworkManagement Guide

na_ping6(1) man page

Sends ICMPv6 ECHO_REQUESTpackets to network hosts.

ping6



7.3Data ONTAP SystemAdministration Guide

na_rdfile(1) man page

Reads the specified file and writesthe contents to standard output.

rdfile


na_rlm(1) man page

Performs an SNMP test on theRLM.

rlm test snmp


na_rshstat(1) man page

Displays information about activeRSH sessions.

rshstat

7.3Data ONTAP FileAccess and ProtocolsManagement Guide

na_sectrace(1) manpage

Adds a permission tracing filter fortracing access control problems.You can add up to 10 permissiontracing filters.

sectrace add



Displays information about whyData ONTAP allowed or deniedaccess to a particular client or user.Data ONTAP provides this extrainformation in addition to theinformation it logs to the consolewhen the criteria of a permissiontracing filter are met.

sectrace

print-status



Removes a permission tracing filter.Because permission tracing filtershave a minor effect on performance,you should use them for debuggingpurposes only, removing them whenyou are finished.

sectrace remove



Displays one or all permissiontracing filters on a storage system.

sectrace show




na_snaplock(1) manpage

Archives active SnapLock log file.snaplock log

archive



Displays the status of activeSnapLock log files on a volume.

snaplock log

status



Sets the active SnapLock logvolume to the volume namespecified. If the volume name is notspecified, displays the current activelog volume name.

snaplock log

volume



The privdel option shows stateof the privileged delete option onthe SnapLock Enterprise volume.

snaplock options



Deletes unexpired files on aSnapLock Enterprise volume.

snaplock privdel


na_stats(1) man page

Displays the list of defined presetsin a system.

stats list presets


na_acpadmin(1) manpage

Displays information about the ACP(Alternate Control Path) storagesubsystem.

storage show acp

7.3.2na_storage(1) manpage

Provides information about diskshelf faults.

storage show fault



7.3.1na_traceroute6(1) manpage

Prints the route IPv6 packets taketo reach the destination.

traceroute6


na_wrfile(1) man page

Reads data from standard input,which is input from the console ora file, and writes or appends theinput into the specified file.

wrfile

Changed commands in Data ONTAP 7.3Commands have been modified to improve disk shelf suppport and enhance network and storageresources management. Additionally, changes have been made to the snap autodelete, vfiler,vol options, and vol status commands.

For each command family and each command, the following table gives this information:

• The change in the command

• The location of documentation about the feature

• The Data ONTAP 7.3 release in which the change was introduced

Releasecommandchanged in

DocumentationChangeCommand

7.3na_aggr(1) manpage

Data ONTAPStorageManagement Guide

For native storage, the defaultRAID type for traditional volumesis now RAID-DP.

aggr create

7.3.1na_cifs_setup(1)man page and

Data ONTAP FileAccess andProtocolsManagement Guide

Includes new and modifiedprompts related to Kerberos MultiRealm support.

cifs setup




7.3na_disk(1) man pageand


The -T option has been added.This option enables you to specifythe disk type when you assigndisks or array LUNs.

disk assign

7.3.2na_disk(1) man pageYou can no longer use thiscommand to change the ownershipof a disk or array LUN that isalready owned unless you arerunning the command on thesystem that owns the disk already.

disk assign

7.3.1na_environment(1)man page

Output changed to include whethera disk shelf supports automaticpowercycling.

environment shelf

7.3.2na_environment(1)man page

Output changed to include SESinformation.

environment shelf

7.3.3na_exportfs(1) manpage

The -c option has been updatedto take multiple IP addresses asarguments. This enablesverification of current exportrights for multiple clients in oneoperation.

exportfs -c

7.3.3na_exportfs(1) manpage

The -f option now includes a -nparameter, which allows you toflush access cache entries thatcorrespond to a specific host.

exportfs -f

7.3.3na_portname(1) manpage

The -f option has been added. Ifyou use the -f option, it overridesthe warning message you receivewhen changing the WWPNs.

fcp portname set

7.3.3na_portname(1) manpage

The -f option has been added. Ifyou use the -f option, it overridesthe warning message you receivewhen changing the WWPNs.

fcp portname swap





Thecifs_disconnect_check

option is added. When thecifs_disconnect_check

option is enabled (set to on),specifies that CIFS requestsassociated with disconnectedsessions will not be sent to FPolicyservers for screening.

fpolicy options


The cifs_setattr option isadded. This option displays thecurrent setting for thecifs_setattr option. If setto on, then the CIFS requests tochange the file security descriptorwill be screened by the policy.

fpolicy options


Theserverprogress_timeout

option is added. This option setsor displays the value ofserverprogress_timeout

for the policy. This is themaximum time an FPolicy servercan remain unresponsive whileprocessing the maximum allowednumber of screen requests.

fpolicy options


The reqcancel _timeoutoption is added. This option setsor displays the value ofreqcancel _timeout forthe policy. This is the maximumtime allowed to an FPolicy serverto screen a request.

fpolicy options




7.3.1na_fpolicy(1) manpage

The monitor_ads option isadded. This option enables ordisables notification for CIFSoperations performed on alternatedata streams.

fpolicy options

7.3.1na_fpolicy(1) manpage

The -I option is added. Thisoption displays a list of FPolicyservers connected to the storagesystem from the given IP address.

fpolicy servers show

7.3.2na_ifconfig(1) manpage

Data ONTAPNetworkManagement Guide

The dad_attempts option hasbeen added. This option is used tospecify the number of consecutiveNeighbor Solicitation messages tobe sent while performingDuplicate Address Detection on atentative address.

ifconfig

7.3.1na_lock(1) man pageThe -net option is added. Thisoption breaks locks of thespecified network family. Thiscommand affects NLM protocolsonly.

lock break

7.3na_lun(1) man pageWhen the new LUN class ofstaging is specified, informationabout the temporary LUNspreserved in the staging area isreported.

lun show

7.3.1na_nfs(1) man pageand

Data ONTAP FileAccess andProtocolsManagement Guide

Includes new and modifiedprompts related to Kerberos MultiRealm support.

nfs setup




7.3.3Data ONTAPNetworkManagement Guide

IPv6 address can be used as anargument

Note: It is no longer necessaryto use the ping6 command toreach IPv6 hosts.

ping

7.3Data ONTAP SystemAdministrationGuide

na_reallocate(1) manpage

The -p option has been added.The option reallocates user dataon the physical blocks in theaggregate, while preserving thelogical block locations within aflexible volume.

reallocate start

7.3.1na_snap(1) manpage and

Data ONTAP DataProtection OnlineBackup andRecovery Guide

The destroy value for thecommitment option destroysonly Snapshot copies lockedbecause of data backing and dataprotection mechanisms.

snap autodelete

7.3.1na_snap(1) manpage and


The destroy_list optioncontrols what type of lockedSnapshot copies, if any, can bedeleted.

snap autodelete

7.3.1na_snapvault(1) manpage and


The -o option has been added. -ocompression=on enables thecompression feature for bandwidthoptimization for a new OpenSystems SnapVault relationship.

snapvault start

7.3na_snapvault(1) manpage and


The -t option has been added.This option displays therelationships that are active.

snapvault status





na_stats(1) manpage

The -p flexscale option hasbeen added and displaysinformation about a system'sWAFL extended cacheconfiguration.

stats show


na_stats(1) manpage

The -p flexscale-accessoption has been added anddisplays usage and accessinformation related to WAFLextended cache.

stats show

7.3.2Data ONTAP SystemAdministrationGuide

na_stats(1) manpage

The output of the -pflexscale-access optionnow includes information aboutreplaced disk IOs and metadatahits and misses.

stats show

7.3na_storage(1) manpage

The -f option is no longerrequired to disable a tape deviceif the device is not in use.

storage disable


The system interconnect link (SIL)ports (the last four rows of output)are now shown as [SIL0] through[SIL3]. Previously they wereshown as [DIS0] through [DIS3].

storage show expander


The DS4243 disk shelf ports arenow listed as [SQR0]-[SQR3] forthe square ports and[CIR4]-[CIR7] for the circle ports.Previously these ports were listedas [IO 0]-[IO7].

storage show expander


You can now specify a shelf namefor this command.

storage show fault


The output now includes morecounters when ESH4 shelffirmware version 13 or later ispresent.

storage show hub




7.3na_sysconfig(1) manpage

The -h option has been added.This option displays the samedetailed information as the-aoption, except that an appropriateunit is used (KB, GB, or TB) andthese units are calculated based onthe powers of two.

sysconfig

7.3.2na_sysconfig(1) manpage

When the -r option is used todisplay disk information forSAS-connected disks, the CHAN(channel) column now displays theport as "A" or "B", just as it doesfor FC-connected disks.Previously, "1" and "2" were used.

sysconfig


na_useradmin(1)man page

The new -x option displays theextended information for alladministrators.

useradmin user list


na_useradmin(1)man page

Displays the username of the userrunning this command.

useradmin whoami

7.3.1na_vfiler(1) manpage and DataONTAP MultiStoreManagement Guide

The -c secure option has beenadded. The -c secure optioncan be used when you want to usethe SSL command channel fordisaster recovery.

vfiler dr configure



vfiler dr delete






vfiler migrate



vfiler migrate cancel



vfiler migrate complete



vfiler migrate start



vfiler dr resync

7.3.1.1na_vif(1) man page

Data ONTAPNetworkManagement Guide

The rr value (round-robin loadbalancing) for the -b option hasbeen added.

vif create

7.3.2Data ONTAPNetworkManagement Guide

The port value (port-basedload-balancing) for the -b optionhas been added.

vif create




7.3.1Data ONTAPArchive andComplianceManagement Guide

The -f option is added. It is usedto force the creation of clone onSnapLock volumes

vol clone create

7.3na_aggr(1) manpage and


For native storage, the defaultRAID type for traditional volumesis now RAID-DP.

vol create

7.3Data ONTAPStorageManagement Guide

If you attempt to take a volumeoffline while any files containedby that volume are open, DataONTAP now returns the names ofthe open files and the process thatopened them along with the failuremessage.

vol offline

7.3Data ONTAPStorageManagement Guide

The newflexcache_autogrow

volume option enables or disablesthe Autogrow capability forFlexCache volumes.

vol options

7.3.1na_vol(1) man pageand


The nbu_archival_snapoption has been added. Setting thisoption to on for a volume enablesarchival Snapshot copies forSnapVault for NetBackup.

vol options

7.3na_vol(1) man pageand

Data ONTAP BlockAccess ManagementGuide

Thesnapshot_clone_dependency

option has been added. Setting thisoption to on enables a system tolock backing Snapshot copies forthe active LUN clone only.

vol options

7.3.1na_vol(1) man pageThe extent option enablesextents but can only be used onFlexVol volumes.

vol options




7.3.1na_vol(1) man pageThe read_realloc optionenables read reallocation but canonly be used on FlexVol volumes.

vol options

7.3na_vol(1) man pageReturns newupgraded_replica optionwhen a SnapMirror destinationvolume's space guarantee has beendisabled after an upgrade.

vol status

7.3.1na_vol(1) man pageThe -v option now returnsautodelete and autosize settings.

vol status

7.3.1Data ONTAPArchive andComplianceManagement Guide

The -w option is added. Thisoption prints the expiration timefor the SnapLock volume

vol status

7.3.2na_vol(1) man pageWhen the -r option is used todisplay disk information forSAS-connected disks, the CHAN(channel) column now displays theport as "A" or "B", just as it doesfor FC-connected disks.Previously, "1" and "2" were used.

vol status

New options in Data ONTAP 7.3Options that can be used with the options command have been added to enable new storage systemfeatures and to improve network, file access, block access, data protection, disk types, and storageresources management.

For each new option that can be used with the options command, the following table gives thisinformation:

• The name of the new option

• A description of the option's purpose

• The default value for the option

• The Data ONTAP release in which the option was introduced


For more information about the options command and individual options, see the na_options(1) manpage.

Releaseintroduced

Default valuePurposeOption

7.3offControls auditing of APIs based on theirroles.

auditlog.readonly_api.enable

7.3.2offSends a copy of NetApp Health Trigger(NHT) disk data to the customer "to"list.

autosupport.local.nht_data.enable

7.3.2onSends a copy of NetApp Health Trigger(NHT) disk drive data to home.

autosupport.nht_data.enable

7.3.1notconfigured

Defines the list of recipients who willreceive all AutoSupport emailnotifications regardless of the severitylevel.

autosupport.partner.to

7.3.3onEnables or disables Cisco DiscoveryProtocol (CDP) on the storage system.

cdpd.enable

7.3.3180 secondsConfigures the hold time for CDPadvertisements.

cdpd.holdtime

7.3.360 secondsConfigures the time interval for sendingCDP advertisements.

cdpd.interval

7.3onEnables or disables hardware-assistedtakeover. Hardware-assisted takeover isenabled by default on systems that useRemote LAN Module (RLM).

cf.hw_assist.enable

7.3IP address onthe e0a portof the partner

Sets the partner address used by thehardware-assisted takeover process onthe remote management card.

cf.hw_assist.partner.address

7.34004Sets the partner port used by thehardware-assisted takeover process onthe remote management card.

cf.hw_assist.partner.port

7.3.2offSets the system to use the /etc/mcrcfile rather than the /etc/rc file toconfigure partner interfaces upontakeover. Applies to MetroClusterconfigurations only.

cf.takeover.use_mcrc_file


Releaseintroduced


7.3.1onSpecifies the user or group of users whocan access audit records using theLiveView feature.

cifs.audit.liveview.allowed_users

7.3.1offEnables or disables CIFS over IPv6.cifs.ipv6.enable

7.31Sets the storage system's minimumsecurity level (that is, the minimum levelof the security tokens that the storagesystem accepts from clients).

cifs.LMCompatibilityLevel

7.3.3no entry

(allows accessonly toAdministrators)

Specifies users or groups (in addition toAdministrators) that are allowed to viewperformance data using MicrosoftPerfmon.

cifs.perfmon.allowed_users

7.3.1offEnables or disables the storage system'sSMB 2.0 protocol client capability.

cifs.smb2.client.enable

7.3.1offEnables or disables the SMB 2.0protocol.

cifs.smb2.enable

7.3.1onEnables or disables SMB 2.0 durablehandles.

cifs.smb2.durable_handle.enable

7.3.116mSpecifies the SMB 2.0 durable handletimeout value.

cifs.smb2.durable_handle.timeout

7.3.1offEnables or disables the requirement thatclients sign SMB 2.0 messages.

cifs.smb2.signing.required

7.3.190Controls the number of outstandingdelegations allowed by the originvolume. Do not modify this optionunless instructed to do so by technicalsupport.

flexcache.deleg.high_water

7.3.150Controls the number of outstandingdelegations allowed by the originvolume. Do not modify this optionunless instructed to do so by technicalsupport.

flexcache.deleg.low_water


Releaseintroduced


7.3offEnables or disables FlexScalefunctionality. If your storage systemdoes not have the PerformanceAcceleration Module, this option enablesor disables Predictive Cache Statistics(PCS).

flexscale.enable

7.3offControls whether low-priority user datablocks are cached by FlexScale.

flexscale.lopri_data_blocks

7.3512Displays the maximum I/O queue depthfor FlexScale.

Note: You should not change thedefault settings.

flexscale.max_io_qdepth

7.3onControls whether normal user datablocks are cached by FlexScale.

flexscale.normal_data_blocks

7.3.2offControls the sampling rate of thePredictive Cache Statistics (PCS.)

flexscale.pcs_high_res

7.3.2Automaticallyset by PCSbased on thesystemmemory.

Controls the size of the cache emulatedby PCS.

flexscale.pcs_size

7.3.2onEnables multiple open instances of theSMB named pipe on an FPolicy server.

fpolicy.multiple_pipes

7.3.1offEnables or disables FTP over IPv6.ftpd.ipv6.enable

7.3.1offEnables or disables HTTP and HTTPSover IPv6.

httpd.ipv6.enable

7.3.1offEnables or disables IPv6 on the storagesystem.

ip.v6.enable

7.3.1onEnables or disables the router-advertisedaddress autoconfiguration for IPv6.

ip.v6.ra_enable

7.3.198910Specifies the NFS TCP flow control highwater mark. Data ONTAP starts flowcontrol when the TCP packet data goesabove this threshold.

nfs.ifc.rcv.high


Releaseintroduced


7.3.133170Specifies the NFS TCP flow control lowwater mark. Data ONTAP stops flowcontrol when the TCP packet data goesbelow this threshold.

nfs.ifc.rcv.low

7.3.1offEnables or disables NFS over IPv6.nfs.ipv6.enable

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

nfs.max_num_aux_groups

7.3.1offSpecifies whether the NFS server forcesa client to retry a request by breakingthe connection or by sendingNFSERR_JUKEBOX (NFSv3) orNFS4ERR_DELAY (NFSv4). Does notaffect NFSv2.

nfs.thin_prov.ejuke

7.3.1offEnables certain disk types to be mixedwith an aggregate.

raid.disktype.enable

7.30Specifies the number of reservedtransfers for SnapMirror volumes.

replication.volume.

reserved_transfers

7.30Specifies the number of reservedtransfers for SnapMirror and SnapVaultqtrees.

replication.logical.

reserved_transfers

7.3onEnables or disables the SNMP traps foronly the RLM.

rlm.snmp.traps

7.3onEnables or disables root access to thestorage system.

security.passwd.rootaccess.enable

7.3For semi-synchronous SnapMirrorconfigurations, this option is usedinstead of the outstanding parameterand provides a recovery point objectiveof approximately 10 seconds.

semi-sync

7.3.2"" (null)Sets the override path for the user'shome directory.

sftp.dir_override

7.3.2offEnables the SSH File Transfer Protocol(SFTP).

sftp.enable


Releaseintroduced


7.3.1autoEnables automatic shelf power-cyclingfor AT-FCX shelves with the requiredpower supply and shelf firmwareversion.

shelf.atfcx.auto.reset.enable

7.3.1offEnables automatic shelf power-cyclingfor ESH4 shelves with the requiredpower supply and shelf firmwareversion.

shelf.esh4.auto.reset.enable

7.3.1noneSets the autocommit time delay.snaplock.autocommit_period

7.3.1offThis option is used to verify disk writesto SnapLock Compliance volumes whenimmediate verification of the recordingprocess is required.

snaplock.compliance.write_verify

7.3.16mSpecifies a default retention policy fora secure log file.

snaplock.log.default_retention

7.3.110mThis option specifies the maximum sizefor a secure log before the file is closedand a new log file is generated for useby the secure logging infrastructure.

snaplock.log.maximum_size

7.3.1onSets the default value for thenbu_archival_snap vol option onnew volumes.

snapvault.nbu.

archival_snap_default

7.3.1offEnables or disables the compressionfeature globally for Open SystemsSnapVault relationships.

snapvault.ossv.compression

7.3.2offEnables the Transport Layer Security(TLS) protocol.

tls.enable

7.3.38Controls the maximum number ofconcurrent TFTP connections served bythe storage system.

tftpd.max_connections

7.3.1offIf set to ON and one or more of the linksin the active multimode vif fails, afailover to a multimode vif that has ahigher aggregate bandwidth will occur.

vif.failover.link_degraded


Changed options in Data ONTAP 7.3Options have been modified to improve network and storage resource management.

For each option, the following table gives this information:

• The name of the changed option

• The nature of the change

• The location of documentation about the option

• The Data ONTAP 7.3 release in which the change was introduced

For more information about the options command and individual options, see the na_options(1) manpage.

Release changedDocumentationChangeOption

7.3.2The default value for this optionhas been changed from anempty string to mailhost.

autosupport.mailhost

7.3.2This option has becomeobsolete.

flexscale.max_io_qdepth

7.3.2This option has becomeobsolete.

ip.tcp.protocol.offload.enable

7.3The value foruse_system_default

has been changed from 4 to 32.

iscsi.max_connections

_per_session

7.3.1The default value for this optionhas changed from 5 seconds to100 milliseconds.

nlm.cleanup.timeout

7.3.1.1L1Beginning with Data ONTAP7.3.1.1L1, the value of thisoption is automatically adjustedwhen the value of thenfs.tcp.recvwindowsize optionis changed.

nfs.ifc.rcv.high

7.3.1.1L1Beginning with Data ONTAP7.3.1.1L1, the default value forthis option has increased.

nfs.ifc.rcv.low


Release changedDocumentationChangeOption

7.3.3Bug 316727Beginning in Data ONTAP7.3.3, this option has beenremoved.

nfs.v4.setattr_ack_preserve

7.3.2This option has beendeprecated.

timed.max_skew

7.3.2The rtc and the rdateparameters of this option havebeen deprecated.

timed.proto


timed.sched


timed.window

Related information


Replaced or removed commands in Data ONTAP 7.3The software install command is deprecated in Data ONTAP 7.3.1 and will not be supported infuture release families. Use the software update command instead to update from Data ONTAP7.2 and later releases.

Note: If you are upgrading from a Data ONTAP 7.0.x or 7.1.x release, you must use the softwareinstall command.



Requirements for running Data ONTAP 7.3

You can use this information to verify that you have the storage systems and firmware needed to runData ONTAP 7.3 and later, and in particular, to create active/active configurations, formerly known asclusters.

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

Next topics

Supported systems on page 103

Systems you can use in active/active configurations on page 104

Storage system firmware on page 105

Storage systems that support Multipath Storage on page 105

V-Series requirements and support information on page 106

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 a Data ONTAP 7.3.x release.

Attention:

Beginning with Data ONTAP 7.3, DS14 disk shelves (sometimes referred to as DS14mk1), LRCstorage I/O modules, and ESH storage I/O modules are no longer supported. If even one of thesedevices is attached to your storage system, you should not upgrade to Data ONTAP 7.3 or later.

DS14 shelves, LRC modules, and ESH modules are no longer supported at all. For more information,see Systems including DS14 shelves, ESH modules or LRC modules are not supported on page 38 .

The following models of storage systems are supported:

• 60xx

• 31xx

• 30xx

• FAS20xx

• FAS900 and GF900 series

• FAS200 series and GF270c

Requirements for running Data ONTAP 7.3 | 103


• NearStore R200

• All SA systems

Systems you can use in active/active configurationsTo create active/active configurations, you need to use supported systems listed in this section.

Active/active configurations are supported on the following NetApp storage systems:

• 6080

• 6070

• 6040

• 6030

• 3140

• 3160

• 3170

• 3070

• 3050

• 3040

• 3020

• FAS2050

• FAS2040

• FAS2020

• 980

• 960

• 940

• 920

• FAS270

• GF270c

• SA600

• SA300

• SA200

FAS20xx, 31xx, 30xx and 60xx systems support active/active configurations regardless of whether theshelf connected to the system is FC-AL, ATA or SAS.


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

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

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

• Disk drives

• Disk shelves

Storage system firmware

It is best to upgrade to the latest version of storage system firmware. For a list of available 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 Upgrade Guide.

Disk firmware

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

Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For moreinformation, see the Data ONTAP Upgrade Guide.

Disk shelf firmware

For information about the latest disk shelf and ESH (Embedded Switched Hub) firmware, see the "DiskShelf & ESH Firmware Matrix" on the NOW site.

Related information

System Firmware Release Table: now.netapp.com/NOW/cgi-bin/fw

Disk Drive & Firmware Matrix: now.netapp.com/NOW/download/tools/diskfw/

Disk Shelf & ESH Firmware Matrix: now.netapp.com/NOW/download/tools/diskshelf/

Storage systems that support Multipath StorageTo configure Multipath Storage, which provides redundancy for the path from each controller to everydisk shelf in the configuration and is the preferred cabling method, you need to have a supported storagesystem, disk shelves, and modules.

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

Requirements for running Data ONTAP 7.3 | 105

http://now.netapp.com/NOW/cgi-bin/fw

http://now.netapp.com/NOW/download/tools/diskfw/

http://now.netapp.com/NOW/download/tools/diskshelf/

• All FAS systems except the FAS200 series storage systems

• All SA systems

• V60xx,V30xx, and V31xx storage systems

• All disk shelves except the following disk shelves and modules:

• DS14 and earlier disk shelves (DS14mk2 and later disk shelves do support Multipath Storage)

• ESH modules (RoHS-compliant ESH2 and later modules do support Multipath Storage)

• 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-Series systems. On eachnode in an active/active configuration of V-Series systems using native disk shelves, you must configurethe fc-non-array-adapter list environment variable for the first disk shelf on a new loopto the V-Series system.

Note: Setting the fc-non-array-adapter list environment variable is not required onV-Series systems configured with DS4243 disk shelves.

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 and storagearrays, as well as supported microcode, license code, and storage array firmware versions. The V-SeriesSupport Matrix also identifies switch connectivity and topology that can be used with V-Series systems.You can access the V-Series Support Matrix on the NOW site.

Requirements for V-Series fabric-attached MetroCluster 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.


Important cautions

Before deploying this release of Data ONTAP, make sure that you read the following items to identifyand 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

Upgrade and revert cautions on page 107

Network protocol cautions on page 114

Block access protocol cautions on page 115

Data protection cautions on page 117

Storage management cautions on page 122

Related information


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 Upgrade Guide.

Next topics

If you are upgrading a system that includes FlexCache volumes on page 108

If your system includes DS14 shelves, ESH modules, or LRC modules on page 108

If you revert a system that has an X1106A-R6 or X1107A-R6 Ethernet card installed on page 108

If you are upgrading to Data ONTAP 7.3 or later on page 108

New RLM firmware and its upgrade requirements on page 109

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

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

If you have been using the flex_cache license on page 111

If you are using SharedStorage on page 111

If you are upgrading a 60xx or SA600 system and want to use the Upgrade Utility on page 111

If you are upgrading a FAS2020 system running Data ONTAP 7.2.2L1 on page 111

Important cautions | 107


If you are upgrading a FAS20xx system on page 111

If you are upgrading to a 4-Gb HBA in a SAN environment on page 112

If you are upgrading from a 2-Gb onboard port to a 4-Gb adapter in a SAN environmenton page 112

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

If you are reverting to a previous release and you use large ACLs under NFSv4 on page 113

If you are upgrading a system that includes FlexCache volumesBefore upgrading a system that includes FlexCache volumes, verify that the convert_ucode volumeoption is set to off for all FlexCache volumes. Failure to turn the convert_ucode volume optionoff before upgrading could cause a system panic.

If your system includes DS14 shelves, ESH modules, or LRC modulesBeginning with Data ONTAP 7.3, DS14 disk shelves (sometimes referred to as DS14mk1), LRC storageI/O modules, and ESH storage I/O modules are no longer supported.

Upgrading a system with any of these devices attached to it will result in an unsupported configuration.If even one of these devices is attached to your storage system, you should not upgrade to Data ONTAP7.3 or later.

For more information, see Systems including DS14 shelves, ESH modules or LRC modules are notsupported on page 38 .

If you revert a system that has an X1106A-R6 or X1107A-R6 Ethernet cardinstalled

Data ONTAP 7.3.2 and later releases support X1106A-R6 and X1107A-R6 10-Gigabit Ethernet cards.You must remove these cards before reverting to a previous release.

Related information

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

If you are upgrading to Data ONTAP 7.3 or laterUpgrading to Data ONTAP 7.3 or later from an earlier release will cause existing FlexVol volumes torequire 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 to satisfythe increased requirement from its FlexVol volumes, the space guarantee for one or more volumesin that aggregate could be disabled.



For more information, see the Data ONTAP Upgrade Guide.

Determining system capacity and space guarantees

If you suspect that your system has almost used all of its free space, or if you use thin provisioning,you should check the amount of space in use by each aggregate. If any aggregate is 97 percent full 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

Then ...If the capacity field shows ...

You can proceed with your upgrade to Data ONTAP 7.3;no further action is required.

96% or less for all aggregates

Continue with step 2.97% or more for any aggregate

2. Use a Web browser to go to the NOW Web site and select the appropriate upgrade tool for yourenvironment.

Then ...If your system ...

Continue to plan your upgrade with the UpgradeAdvisor tool.

Is configured to send AutoSupport messages toNetApp

Continue to plan your upgrade with theaggrSpaceCheck tool.

Is not configured to send AutoSupport messages toNetApp

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 recommend solutions.Using it is the recommended upgrade methodology.

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

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 earlier than3.1, you must first perform an intermediate update to the latest 3.1.x firmware, then update from 3.1 to4.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 the Data ONTAP CLI, you must run the rlm updatecommand with the -f advanced option. Further updates do not require the advanced option.

If you are updating RLM firmware from the RLM CLI, you can use the normal procedure.

Note: Beginning with Data ONTAP 7.3.3, the RLM supports IPv6. To send RLM traffic over IPv6,you must be running RLM version 4.0 and IPv6 must be enabled on the storage system.

If you do not plan to send RLM traffic over IPv6 on Data ONTAP 7.3 releases, it is not required toupdate RLM firmware to 4.0 or later. However, firmware version 4.0 includes other enhancements,and it is a best practice to be running the latest firmware on your RLM.

For information about installing and updating the RLM firmware, see the Data ONTAP Upgrade Guide.

For information about configuring the RLM, see the Data ONTAP System Administration Guide.

If you are performing a nondisruptive upgrade on a system with VMware ESXServer 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. Thisverification will help ensure that VMware guest operating systems do not experience service disruptionduring 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 UpgradeGuide.

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


For information about deduplication, see the Data ONTAP Storage Management Guide and the sis(1)man page.

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 you installthe license.

If you are using SharedStorageThe SharedStorage functionality is not available in Data ONTAP 7.2 and later releases. If you are usingSharedStorage in an earlier Data ONTAP release and you want to continue using it, do not upgrade toData ONTAP 7.2 or later.

If you need to upgrade to Data ONTAP 7.2 or later and you must continue to use SharedStorage, contacttechnical support.

If you are upgrading a 60xx or SA600 system and want to use the UpgradeUtility

The Upgrade Utility does not currently work with 60xx and SA600 systems.

Note: The Upgrade Utility is deprecated in the Data ONTAP 7.3 release family. The utility will notbe supported in Data ONTAP 8.0 and later releases.

Related information

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

If you are upgrading a FAS2020 system running Data ONTAP 7.2.2L1If you configured aggregates larger than 8 TB on a FAS2020 system running Data ONTAP 7.2.2L1,you cannot use the nondisruptive method to upgrade to any later release; you must use the standardupgrade method.

If you are upgrading a FAS20xx systemThis Data ONTAP release includes new firmware for the Baseboard Management Controller (BMC).If you have not already installed BMC version 1.2, you should install the new BMC firmware immediatelyafter upgrading.

For information about updating the BMC firmware, see the Data ONTAP Upgrade Guide.



If you are upgrading to a 4-Gb HBA in a SAN environmentIf you attempt to run a 30xx or 60xx system with a 4-Gb HBA in an unsupported cfmode, the 4-GbHBA is set to offline and an error message is displayed.

You must change the cfmode to single_image or standby cfmode before upgrading. Only single_imageand standby cfmodes are supported with the new 4-Gb Fibre Channel host bus adapters (HBAs) on30xx and 60xx storage systems.

In addition, Data ONTAP does not allow changing from a supported cfmode to an unsupported cfmodewith the 4-Gb HBA installed on these systems.

If you are upgrading from a 2-Gb onboard port to a 4-Gb adapter in a SANenvironment

If you have a FAS 30xx or FAS 60xx series storage system, you must stop the FCP service and set theonboard port as unconfigured before installing the 4-Gb adapter. Failure to do so might result in astorage system panic and lost data.

Note: When you upgrade from the onboard ports to the 4-Gb HBAs, the worldwide port names(WWPNs) will change, which requires that you reconfigure any UNIX hosts with the newly assignedWWPNs.

Reconfiguring the 2-Gb onboard port

You must reconfigure the 2-Gb onboard port before installing a 4-Gb adapter.

Steps

1. Stop the FCP service by entering the following command:

fcp stop

The FCP service is stopped and all target adapters are taken offline.

2. Set the onboard FC ports to unconfigured:

fcadmin config -t unconfig ports

Example

fcadmin config -t unconfig 0b 0d

The onboard FC ports are unconfigured.

3. Ensure the cfmode is set to single_image or standby.

4. Shut down the storage system.

5. Install the 4-Gb adapter according to the instructions provided with the adapter.


6. Power on the storage system.

If you are reverting to a Data ONTAP release with a lower maximum capacityWhen you revert to an earlier Data ONTAP release, your storage system must conform to the maximumcapacity limitations of the earlier release. If you upgraded your system to a release that supports greatercapacities and you configured storage to utilize the new capacities, you must reconfigure your systemto the lower capacity limits before you revert. If you don't reconfigure in this way, the storage systemwill not boot up following the revert process until the excess capacity has been disconnected.

To access any storage in excess of system limits, you must disconnect it from the system you arereverting. Excess capacity must be disconnected for relocation to a different storage system in a waythat allows aggregates to remain intact.

The system to which storage is relocated must meet the following requirements:

• It has spare capacity room to accommodate the relocated storage.

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

• It is running a Data ONTAP release that supports the relocated disks.

For more information about physically moving aggregates, see the Data ONTAP Storage ManagementGuide.

For more information about maximum capacity limits for a given Data ONTAP release, see the SystemConfiguration 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 large ACLs under NFSv4If you are running NFSv4 and use large ACLs, you can run the pre_revert_acl script to replace the largeACLs so that Data ONTAP does not replace them with a default ACL during the reversion.

In Data ONTAP 7.3 and later, you can have more than 192 ACEs per ACL in NFSv4. However, inreleases earlier than Data ONTAP 7.3, the maximum number of ACEs was 192. Therefore, when yourevert Data ONTAP 7.3 and later to a release earlier than Data ONTAP 7.3, Data ONTAP automaticallyreplaces large ACLs (those with more than 192 ACEs) with a default ACL. To mitigate any concernsassociated with the setting of this default ACL, NetApp provides a Perl script called pre_revert_acl.

Before doing the revert, you should run the pre_revert_acl script from an NFS client with root permissionsover all the exports of the storage system (or vFiler unit). This script works by mounting each exportof the storage system, iterating over all the directories and files under that export, and listing the filesthat have large ACLs (ACLs with more than 192 ACEs). Optionally, the script can also replace thelarge ACL on each file with an ACL that you provide.

The pre_revert_acl script is available at http://now.netapp.com/eservice/toolchest.



http://now.netapp.com/eservice/toolchest

If you are not running NFSv4 on your system, you can ignore the ACL-related message displayed atthe time of revert.

Network protocol cautionsIf you use FilerView to manage network interfaces or if your network configuration includes a vif, youshould review these issues and take appropriate action before upgrading.

For more information about these issues, see the Data ONTAP Network Management Guide.

Next topics

If you use a vif that is named "vip" on page 114

If your system uses ATM for network connectivity on page 115

If you use a vif that is named "vip"Beginning in Data ONTAP 7.2, the string "vip" is reserved for private virtual interfaces. If you haveconfigured a vif (a feature that implements link aggregation) named "vip" on your storage system inan earlier release, you must rename that vif if you want to upgrade your system to Data ONTAP 7.2.1or later.

If you keep "vip" as the name of a vif and you upgrade to Data ONTAP 7.2.1 or later, the interfacestatus of the vif named "vip" will be set to down and the interface will be unavailable for network traffic.

For more information about creating a vif or renaming a vif, see the Data ONTAP Network ManagementGuide.

Renaming a vif

You should use the vif command to correct the interface name before upgrading to Data ONTAP 7.2.1or later.

Steps

1. Bring down the vif by entering the following command:

ifconfig vip down

2. Destroy the vif by entering the following command :

vif destroy vip

3. Re-create the vif and give it a different unique name, entering the following command:

vif create new_vif_name


If your system uses ATM for network connectivityATM is no longer supported in Data ONTAP 7.3 and later releases. If your system is running a DataONTAP 7.2.x release and uses ATM for network connectivity, do not upgrade to Data ONTAP 7.3 orlater.

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 Block Access Management Guide foriSCSI and FC.

Next topics

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

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

If jumpers J3 and J4 on QLogic 2 Gbps Fibre channel target expansion are in positions 2 and3 on page 116

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

If an iSCSI target HBA fails on page 116

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

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. This problem exists onlywith systems in single_image cfmode.

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 268320 inBugs 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 cause hostfailures during cluster failover.


http://now.netapp.com/NOW/cgi-bin/bol

https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb35532

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 jumpers J3 and J4 on QLogic 2 Gbps Fibre channel target expansion arein positions 2 and 3

When Data ONTAP panics because it has entered an illegal state, all Fibre Channel target expansionadapters shut down. However, the lasers on the QLogic 2 Gbps target expansion adapters (modelsX1028A/X1033A) will sometimes remain on. This situation can cause the host to mistakenly perceivethat the storage system is still running.

The workaround for this problem is to change the position of jumpers J3 and J4 on the adapter frompositions 2 and 3 to positions 1 and 2, respectively.

Related information


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 athttp://sunsolve.sun.com/search/document.do?assetkey=1-66-231581-1.

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.

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


http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/



http://sunsolve.sun.com/search/document.do?assetkey=1-66-231581-1

http://sunsolve.sun.com/search/document.do?assetkey=1-66-231581-1

http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb42930


If you use the automatic sizing feature on thinly provisioned LUNs when snapreserve is set to a non-zero value

Generally, before you thinly provision LUNs, you should set snap reserve to zero. However, thereare rare exceptions that require you to set snap reserve to a value other than zero. In these instances,you must use the automatic sizing feature for thinly provisioned LUNs in FlexVol volumes to workproperly.

Considerations

Using the automatic sizing feature is required because the space from deleted Snapshot copies can onlybe used to fulfill Snapshot space requests. Furthermore, the automatic deletion process will not beginuntil the snap reserve value is exceeded.

Step

1. Enter the following command:

vol autosize vol_name [-m size] [-I size] on

-m size is the maximum size to which the volume will grow. Specify a size in k (KB), m (MB), g(GB), or t (TB).

-I size is the increment by which the volume's size increases. Specify a size in k (KB), m (MB),g (GB) or t (TB).

If the specified FlexVol volume is about to run out of free space and is smaller than its maximum size,and if there is space available in its containing aggregate, the FlexVol volume's size will increase bythe specified increment.

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 Data Protection Online Backup andRecovery Guide.

Next topics

Issues in SnapLock interaction with active/active configuration on page 118

Issues in moving SnapLock disks on page 118

Issues in booting a system running Data ONTAP 7.3.1 or later with the first release of Data ONTAP7.3 on page 118

Issues in upgrading to Data ONTAP 7.3 if you have SnapLock volumes on page 118


If you upgrade systems running FPolicy on page 119

Issues in reverting to Data ONTAP 7.3 if you have SnapLock volumes on page 119

If you are reverting to a previous release that does not support deduplication with SnapLockvolumes on page 120

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

If you revert to a prior release, for a SnapMirror destination with volumes using deduplication orclone operations on page 121

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

Issues in SnapLock interaction with active/active configurationSnapLock volumes cannot be created in an active/active configuration if one node is running on thefirst release of Data ONTAP 7.3 and the other node is running on Data ONTAP 7.3.1 or later. This isbecause the first release of Data ONTAP 7.3 does not support SnapLock.

For more information, see Data ONTAP Archive and Compliance Management Guide.

Issues in moving SnapLock disksIf SnapLock disks are moved to a storage system that is running the first release of Data ONTAP 7.3,the system will halt. This happens because SnapLock is not supported in the first release of Data ONTAP7.3.

However, if you move the SnapLock disks to a storage system that is running Data ONTAP 7.3.1 orlater, the system continues to be operational. If the SnapLock disks are recognized by the storage systemrunning on Data ONTAP 7.3.1 or later, the storage system will bring the disks online.

Issues in booting a system running Data ONTAP 7.3.1 or later with the firstrelease of Data ONTAP 7.3

If your storage system is running Data ONTAP 7.3.1 or later with SnapLock volumes and you attemptto boot the system with the first release of Data ONTAP 7.3, the system will halt. This happens becauseSnapLock is not supported in the first release of Data ONTAP 7.3.

To recover from such a halt, perform one of the following steps:

• Reboot the system in Data ONTAP 7.3.1 or later.

• Remove the SnapLock disks from the system and continue to boot using the first release of DataONTAP 7.3. You should immediately attach the removed SnapLock disks to a Data ONTAP systemthat supports SnapLock.

Issues in upgrading to Data ONTAP 7.3 if you have SnapLock volumesIf you have SnapLock volumes in your storage system and you upgrade from an earlier release family(such as a Data ONTAP 7.2 release) to the Data ONTAP 7.3 release family by booting the system with


the first release of Data ONTAP 7.3, the system will halt. The halt will occur in the very early bootphase (much before any on-disk structure is updated).This happens because SnapLock is not supportedin the first release of Data ONTAP 7.3.

To recover from this halt, perform one of the following steps:

• Reboot the system in the previous release which supported SnapLock. (For example, if you areupgrading from Data ONTAP 7.2.5.1, boot the system with Data ONTAP 7.2.5.1.)

• Remove the SnapLock disks from the system and continue to boot with the first release of DataONTAP 7.3.

Note: You should immediately attach the removed SnapLock disks to a Data ONTAP systemthat supports SnapLock.

However, if you upgrade from an earlier release that supports SnapLock to Data ONTAP 7.3.1 or later,which also supports SnapLock, the bootup and upgrade process will proceed normally and the systemwill be fully operational.

If you upgrade systems running FPolicyIf your system includes directories created or modified with NFS and you have configured FPolicy toscan files in these directories, FPolicy functionality might not be available during all or part of theupgrade process.

When you upgrade to Data ONTAP 7.3 or later from a release earlier than 7.2, Inode To Pathname(I2P) information is reinitialized on each existing volume on your system. FPolicy file screeningconfigured for native file blocking will not take place in these directories until the I2P initializationprocess is completed.

For more information about I2P reinitialization, see the Data ONTAP Upgrade Guide.

Issues in reverting to Data ONTAP 7.3 if you have SnapLock volumesSnapLock is not supported in the first release of Data ONTAP 7.3. Therefore, when reverting a storagesystem that contains SnapLock volumes to Data ONTAP 7.3 release family, you need to be aware ofcertain issues.

You can successfully revert to any release in the Data ONTAP 7.3 family even if your system containsSnapLock volumes. However, if you boot such a system with the first release of Data ONTAP 7.3, thesystem will halt. The list of SnapLock disks causing the system to halt will be listed on the console.

To recover from such a halt, perform one of the following steps:

• Reboot the system using a Data ONTAP release that supports SnapLock.

• Remove the SnapLock disks from the storage system. You will then be able to boot up using thefirst release of Data ONTAP 7.3.


Note: You should immediately attach the removed SnapLock disks to a Data ONTAP systemthat supports SnapLock.

If you boot a storage system containing SnapLock volumes in Data ONTAP 7.3.1 or later, the systemwill boot up normally and continue to be operational.

If you are reverting to a previous release that does not support deduplicationwith SnapLock volumes

Beginning with Data ONTAP 7.3.1, deduplication is supported on the SnapLock volumes.

However, if deduplication is enabled on a SnapLock volume and you attempt to revert to a Data ONTAPrelease that does not support deduplication on SnapLock volumes, you will see the following errormessage.

Volume "volname" cannot be reverted because SIS has been enabled on it. You must undo SIS on this volume before continuing with the revert.

To avoid or recover from this situation, contact technical support.

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, andyou receive an error message:request denied by source filer, check access permissions on source

Workaround: To allow access to the destination hosting storage system, set the snapmirror.accessand snapvault.access options on the source system.

• If the ndmpd.preferred_interfaces option is not specified on the source hosting system, thenthe 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-discoveryor 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


If you revert to a prior release, for a SnapMirror destination with volumesusing deduplication or clone operations

For a volume SnapMirror relationship, the destination storage system should use a Data ONTAP releaseidentical to or later than that used by the source.

In releases prior to Data ONTAP 7.3.1, when replicating volumes with deduplication, the NearStorepersonality license was required on the destination storage system. However, for Data ONTAP 7.3.1or later, it is not essential to enable the NearStore personality license on the destination for replicatingsuch volumes. Therefore, if you revert from Data ONTAP 7.3.1 or later to a prior release, ensure thatthe NearStore personality license is enabled on the destination storage system. Otherwise, after therevert operation, volume SnapMirror updates will fail for any volumes on the source that usededuplication.

Note: When using SnapMirror to replicate volumes that use deduplication or clone operations, thedestination storage system should support deduplication.

For more information about the NearStore personality license and the storage systems that supportdeduplication, see the Data ONTAP Data Protection Online Backup and Recovery Guide.

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 7.3 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 operations performedearlier. However, the new data written to the volume after the revert process will obtain space savingsthrough deduplication within the new data only, and not from the data that existed before the revertprocess.

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 metadata usesbetween 4 and 6 percent of the logical data size in the volume.



Storage management cautionsIf you are migrating data to a new system or configuring FlexVol volumes, you might need to familiarizeyourself with FlexVol storage management issues. Additionally, If you have DS2342 disk shelvesattached to your storage system, you should review DS2342 disk shelves issues and take appropriateaction.

For more information about these issues, see the Data ONTAP Storage Management Guide.

Next topics

If you are replacing traditional volumes with FlexVol volumes on page 122

If you see unexpected warnings and messages regarding FlexVol volumes on page 122

If you are replacing traditional volumes with FlexVol volumesFlexVol volumes have different best practices, optimal configurations, and performance characteristicsfrom those of traditional volumes. Make sure you understand these differences by referring to theFlexVol volume documentation, and deploy the configuration that is optimal for your environment.

For information about deploying a storage solution with FlexVol volumes, including migration andperformance considerations, see the technical report Introduction to Data ONTAP Release 7G (availablefrom the NetApp Library). For detailed information about configuring FlexVol volumes and aggregates,see the Storage Management Guide.

Related information

Introduction to Data ONTAP Release 7G: www.netapp.com/library/tr/3356.pdf

If you see unexpected warnings and messages regarding FlexVol volumesIf an aggregate is unexpectedly taken offline because of a hardware failure (for example, if you havean aggregate on a loop and the loop fails), you might see unexpected warnings and messages.

Data ONTAP assigns a unique file system identifier (FSID) to every flexible volume on a system. DataONTAP cannot check the FSIDs of offline flexible volumes. Data ONTAP does detect the possibilityof FSID conflict and issues warnings and messages alerting you to the possibility of duplicate FSIDcreation.

During the time the aggregate is offline, you might see warnings and messages during operations suchas these:

• Creating a new flexible volume, including by cloningIn this case, you will see a warning. You can override the warning, but if you do, you might seeadditional problems. If possible, do not create new FlexVol volumes until after you bring the offlineaggregate back online.

• Bringing a flexible volume online


http://www.netapp.com/library/tr/3356.pdf

Before the flexible volume is brought online, Data ONTAP checks the FSID. If there is a duplicateFSID, you see the following message:

vol online: FSID marked invalid because it already exists.Unable to bring volume 'volname' online

The volume does not come online. You cannot override this warning. See Knowledge Base articlekb4361 on the NOW site for additional information.

• Accessing of a volume by a vFiler unitYou might see a message from the vFiler unit about a volume being in an unexpected state. Thevolume reported might not be an offline volume. NFS clients will not be able to access the reportedvFiler volume.You can fix this problem by first taking the volume offline using the following command:

vol offline volname

Then bring the volume back online using the following command:

vol online volname

Related information

Unexpected offline aggregates, data from filer is unavailable:now.netapp.com/Knowledgebase/solutionarea.asp?id=kb4361




Known problems and limitations

Some unexpected and potentially undesired behaviors, as well as, in some cases, workarounds to avoidthese 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 125

File access protocol issues on page 127

Network protocol issues on page 130

Block access protocol issues on page 132

Data protection issues on page 135

Storage resource management issues on page 143

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

Active/active configuration issues on page 148

Related information


Manageability issuesYou might have to familiarize yourself with some issues related to manageability in this release.

Next topics

vFiler DR configuration with the snapmirror.checkip.enable option on fails, if SnapMirror failsto authenticate destination IPv6 address on page 125

No IPv6 support for AutoSupport e-mail notifications on page 126

AutoSupport option settings on page 126

Change in sysstat -x command output on page 126

RLM configuration is not saved if the RLM's Ethernet cable is not connected on page 126

vFiler DR configuration with the snapmirror.checkip.enable option on fails,if SnapMirror fails to authenticate destination IPv6 address

When you configure vFiler units for disaster recovery, if the snapmirror.checkip.enable optionis set to onon the source storage system and the IPv6 address of the source storage system is used for

Known problems and limitations | 125


communication, SnapMirror requires the IPv6 address of the destination storage system to set up aSnapMirror relationship.

You must specify the destination storage system’s IPv6 address in the list of allowed addresses forSnapMirror relationship on the source storage system. You can add the destination storage system’sIPv6 address either to the snapmirror.access option, or to the/etc/snapmirror.allow file ifthe snapmirror.access option is set to legacy.

For more information about the snapmirror.checkip.enable option, see the Data ONTAP DataProtection Online Backup and Recovery Guide .

No IPv6 support for AutoSupport e-mail notificationsNetApp does not provide a global unicast IPv6 address for AutoSupport e-mail notifications to be sentfrom the storage system to technical support. Therefore, a dual IPv4/IPv6 configuration mode is requiredfor storage systems that use AutoSupport.

AutoSupport option settingsIn Data ONTAP 7.3.2, two AutoSupport options of the option command cannot be enabled, and twoothers cannot be disabled.

The autosupport.local.nht_data.enable andautosupport.local.performance_data.enable options cannot be enabled. Theautosupport.local.nht_data.enable option should send an AutoSupport message containingNetApp Health Test (NHT) disk data to the "autosupport.to" list. Theautosupport.local.performance_data.enable option should send the weekly performanceAutoSupport message to the "autosupport.to" list.

The autosupport.nht_data.enable and autosupport.performance_data.enable optionscannot be disabled. The autosupport.nht_data.enable option sends an AutoSupport messagecontaining NHT disk data to technical support. The autosupport.performance_data.enableoption sends weekly performance AutoSupport messages to technical support.

Change in sysstat -x command outputIn Data ONTAP 7.1 and later releases, the DAFS column is no longer displayed in the sysstat -xcommand output.

Note that any scripts that currently depend on the sysstat -x command output might need to berevised.

RLM configuration is not saved if the RLM's Ethernet cable is not connectedIf the RLM's Ethernet cable is not connected when you use the rlm setup command to configure theRLM, after connecting the cable you must rerun rlm setup.


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 File Access and Protocols ManagementGuide.

Next topics

Correction to required FPolicy screening requests on page 127

FPolicy file extension issue on revert on page 127

FPolicy compatibility issue in NFSv4 environments on page 128

Limitations in the naming of FPolicy policies on page 128

Some Group Policy Objects (GPOs) are applied differently on storage systems than on Windowssystems on page 128

Client notification messages in Windows domains require NetBIOS on page 129

Unsupported Windows features in the file serving environment on page 129

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

NFSv4 client compatibility on page 129

Unicode character 0x0080 is not supported on page 130

The FTP server does not support Unicode characters on page 130

No IPv6 support in FPolicy on page 130

Correction to required FPolicy screening requestsBeginning with the Data ONTAP 7.2.2 release, if the required option is on and the FPolicy servercannot be contacted, the client request is denied.

In earlier Data ONTAP releases, required FPolicy file screening did not work as expected if an FPolicyserver could not be contacted. If a file policy was set to require screening (using the required optionof the fpolicy options command) for a particular file type, but the FPolicy server could not becontacted (because of an internal error), client requests to access the files controlled by the file policywere still allowed to be completed.

FPolicy file extension issue on revertStarting with Data ONTAP 7.3, the file name extension length supported by FPolicy for screening isincreased to 260 characters. However, if you add extensions longer than three characters to the list ofextensions to be screened in Data ONTAP, you cannot revert to an earlier version. This is because theearlier versions of Data ONTAP do not support extensions with more than three characters. Therefore,you must remove extensions longer than three characters before reverting to an earlier version.

It is recommended that you check your FPolicy extension list before reverting.


FPolicy compatibility issue in NFSv4 environmentsIf you are running an application that uses the FPolicy engine and the application is running in an NFSv4environment, you should upgrade the application to support NFSv4.

Beginning in Data ONTAP 7.3, FPolicy supports NFSv4. Previously, FPolicy did not support NFSv4and NFSv4 requests were not passed on to any FPolicy-based application.

Although FPolicy now supports NFSv4, the FPolicy-based application might not support NFSv4. If anapplication that does not support NFSv4 receives notice of NFSv4 file operations (such as file OPENand CLOSE events), these file operations might appear as UNKNOWN events to the application andgenerate error messages.

To avoid these compatibility problems, you should upgrade any FPolicy-based applications to supportNFSv4.

Limitations in the naming of FPolicy policiesBeginning with Data ONTAP 7.3 RC2, a file policy name can consist of only Unicode characters. Nospecial characters other than the underscore (_) or the hyphen (-) are allowed in the policy name.

If you upgrade from an release earlier than Data ONTAP 7.3 RC2, and FPolicy used a policy namewith a special character, FPolicy will continue to use the special characters in that policy name. However,FPolicy will not allow the creation of new policies with names containing special characters other thanthe underscore (_) or the hyphen (-). In addition to not allowing the special characters in new policynames, FPolicy truncates the names that contain a "." (dot) in them, by dropping the characters afterand including the "." (dot). Any options configured on such policies will be lost after the upgrade.

For example, a policy with the name abc.xyz is created in Data ONTAP 7.2. After you upgrade toData ONTAP 7.3, the policy name changes to abc only. The options configured on this policy (abc.xyz)are lost.

Some Group Policy Objects (GPOs) are applied differently on storage systemsthan on Windows systems

Data ONTAP 7.1 and later releases support Group Policy Objects (GPOs) that are relevant to storagesystem management. However, Audit Policy GPOs, which are Local Policy GPOs, are applied differentlyon NetApp storage systems than on Windows systems.

The application differences occur because the underlying logging and auditing technologies are different.Audit GPOs are applied to storage systems by mapping and setting corresponding Data ONTAP options.The effect of mapping these options is similar, but not identical, to Audit policy settings. For moreinformation, see the Data ONTAP File Access and Protocols Management Guide.


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

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

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

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

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

The nfs.mount_rootonly option should be set to off on a storage system that must support clientsthat mount NFS shares using a non-reserved port even when the user is logged in as root. Such clientsinclude 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.

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 Data ONTAPoption nfs.v4.enable is set to on. In new installations, this option is set to off by default.

Unicode character 0x0080 is not supportedIf you attempt to create or rename a file or directory from a CIFS client with a name that contains theUnicode character 0x0080, an error will appear.

The FTP server does not support Unicode charactersThe 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


No IPv6 support in FPolicyStarting with Data ONTAP 7.3.1, IPv6 is supported on storage systems. However, FPolicy does notsupport IPv6.

Network protocol issuesIf your storage systems are configured for Brocade switches, TOE devices, VLANs, NIS, or IPSec, youmight need to familiarize yourself with current network protocol issues.

For more information about these issues, see the Data ONTAP Network Management Guide.

Next topics

The ping6 usage message is incorrect on page 130

Single-mode vif does not fail over correctly on page 131

TOE is disabled on page 132

No IPv6 support for RIP and IPsec on page 132

Do not use VLAN deletion with IPsec on page 132

Enable caching with NIS lookup on page 132

Potentially reduced performance for IPsec traffic on page 132

The ping6 usage message is incorrectIn the command-line interface, the ping6 command usage lists the -f option. However, Data ONTAPdoes not support the -f option of the ping6 command.



Single-mode vif does not fail over correctlySometimes, the underlying network interface in a single-mode vif does not fail over correctly to thespecified interface. In such cases, the vif status is down. To resolve this issue, you should verify theflags field in the vif status command output.

Possible scenarios when the vif does not fail over correctly are as follows:

• The switch connected to the interface is turned off and then turned on

• Underlying links of the vif are unplugged and then plugged in

The cause for this behavior can be that some flags were not reset properly after the underlying interfacewas plugged back in (although the interface is configured to the up status). You can verify the statusof the vif by checking the flags field in the vif status command output.

For example, in the following output, the flags field is not set for the interface e0b:

system1> vif status vif0default: transmit 'IP Load balancing', VIF Type 'multi_mode', fail 'log'vif0: 1 link, transmit 'none', VIF Type 'single_mode' fail 'default' VIF Status Up Addr_set up: e0a: state up, since 31Dec2008 11:35:08 (00:39:16) mediatype: auto-1000t-fd-up flags: enabled input packets 706738, input bytes 110244559 output packets 705879, output bytes 108626114 output probe packets 354968, input probe packets 342950 up indications 6, broken indications 7 drops (if) 0, drops (link) 29 indication: up at 31Dec2008 11:35:08 consecutive 2129806, transitions 14 down: e0b: state down, since 31Dec2008 11:35:08 (00:39:16) mediatype: auto-1000t-fd-up

flags: input packets 4120296422, input bytes 11894841698426 output packets 1543747818, output bytes 13576720461678 output probe packets 354968, input probe packets 343739 up indications 6, broken indications 6 drops (if) 0, drops (link) 20 indication: broken at 30Dec2008 17:28:08 consecutive 2129804, transitions 13

If the flag field for any network interface constituting the vif is not set, you should try unplugging andplugging in the interface link repeatedly until the flags field shows enabled in the vif statuscommand output.

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


TOE is disabledIn Data ONTAP 7.3.2, TOE functionality is disabled by default. There is no adverse effect on theperformance of your storage system because TOE is disabled. However, if you want to enable TOE,contact technical support.

No IPv6 support for RIP and IPsecRIPng, an extension of RIPv2 for support of IPv6, is not supported currently in Data ONTAP. Also,Data ONTAP does not support IPsec over IPv6.

Do not use VLAN deletion with IPsecIf you delete VLAN interfaces when IPsec is enabled, delete them one by one. Do not use the vlandelete -q command.

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

Whenever you enable NIS lookups (with the nis.enable option), make sure to also enable caching(with the nis.group_update.enable option). Failure to enable these two options together couldlead to timeouts as CIFS clients attempt authentication.

Potentially reduced performance for IPsec trafficData ONTAP 7.1 and later releases do not support hardware-assisted IPsec encryption and instead useonly software encryption.

If your storage system includes hardware-assisted encryption, and you use IPsec encryption for highvolumes of traffic, you might see reduced throughput for the IPsec-encrypted traffic.

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 Block Access Management Guide foriSCSI and FC.

Next topics

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


"option lun.partner_unreachable.default-partner.behavior: Value must be 'drop', 'error', or 'start'"error message periodically displays on page 133

FCoE adapters may fail to come online if the FCP service is stopped and started tooquickly on page 133

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

Ongoing cfmode support on page 134

cfmode restrictions for 8-Gb target expansion adapters on page 135

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

You can work around this problem using the nondisruptive upgrade method, which allows the LUNrevision numbers to retain their previous version. You can also bring the disks online after the upgradeusing Windows disk management tools or SnapDrive functionality.

For more information, see the knowledgebase article Disks show as offline in Windows 2008 after DataONTAP 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

"option lun.partner_unreachable.default-partner.behavior: Value must be'drop', 'error', or 'start'" error message periodically displays

Even though the value of option lun.partner_unreachable.default-partner.behavior isset to drop, this error message periodically displays on the system console.

Data ONTAP periodically reads the value for this option from the registry.local file on disk.Unless the option is explicitly set, the value on the registry.local file remains as unknown.

To remedy this problem, force the change in the registry.local file by issuing the followingcommand:

option lun.partner_unreachable.default-partner.behavior drop

For more technical details, refer to bug 370971 in Bugs Online.

FCoE adapters may fail to come online if the FCP service is stopped andstarted too quickly

The first-generation Qlogic 8432 FCoE adapter takes some additional time to bring online and takeoffline. As a result, if you stop the FCP service and restart it too quickly, the adapter may fail to comeonline.




http://now.netapp.com/NOW/cgi-bin/bol

To avoid this problem, wait a few seconds before restarting the FCP service.

Note: This problem will be addressed in the next generation of FCoE adapters.

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 set tonegotiate connection link speeds automatically. However, link speed auto-negotiation between 200ESwitch ports and QLogic HBAs might not always result in the maximum expected connection speed,thus degrading performance. As an example, an expected 4-Gbps link might only carry traffic at 2 Gbps.

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

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

Related information


Setting Brocade 200E switch speed manually

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

Steps

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

portCfgSpeed port_number speed_level

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

switchshow

Ongoing cfmode supportSingle_image is the only supported cfmode for new installations starting with Data ONTAP 7.3.

If you are upgrading to Data ONTAP 7.3 or later from a prior release, follow these guidelines:

• On legacy systems, including the 900 series, FAS200 series, and GF270c systems, you can continueto use other cfmodes that are supported on your systems.You can freely change from one supported cfmode to any other supported cfmode on these systems.



See "How to manage FCP with active/active configurations" in the Block Access Management Guidefor iSCSI and FCP for the list of supported cfmodes by storage system model.

• On FAS20xx, 30xx and 60xx systems, you can continue to run the existing cfmode after upgrading.If you change to single_image cfmode, you cannot revert to other cfmodes.See Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations for instructions onupgrading to single_image cfmode.

Related information

Changing the Cluster cfmode Setting in Fibre Channel SAN Configurations -http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/

cfmode restrictions for 8-Gb target expansion adapters8-Gb target expansion adapters support only single_image cfmode.

However, 8-Gb initiators can connect to all targets, regardless of speed, in whatever cfmode the targetsupports.

For more information about cfmode restrictions, see the Block Access Management Guide for iSCSIand FC.

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 relevant data protectionissues.

For more information about these issues, see the Data ONTAP Data Protection Online Backup andRecovery Guide and the Data ONTAP Data Protection Tape Backup and Recovery Guide.

Next topics

Data recovery using SnapVault or SnapMirror for a qtree with LUN clones on page 136

Using SnapVault for NetBackup to protect applications on page 137

SnapVault for NetBackup is not supported with Symantec Veritas NetBackup 6.5 on page 137

Changes to deduplication usage with SnapVault for NetBackup on page 137

NetBackup managed SnapVault is unavailable on page 138

Limitations when using SnapVault with nondefault vFiler units on page 138

SnapVault cannot be enabled on vFiler units when SnapLock for SnapVault relationships arepresent in vfiler0 on page 139

Limitation of SnapLock for SnapVault relationship on page 139

Guidelines for creating a clone of a SnapVault destination volume on page 139

Compatibility with SnapDrive and Snap Manager on page 140




Guidelines for creating a clone of a qtree SnapMirror destination volume on page 140

FlexVol volume limits with SnapMirror on a FAS250 storage system on page 141

Synchronous SnapMirror not supported for volumes with deduplication on page 141

SMB 2.0 not supported for SnapLock on page 141

Possible effect of creating more than 64 mirrored aggregates preventing disaster recovery fromfunctioning correctly on page 141

Protection Manager 3.7 does not perform optimally with deduplication on page 141

Improved sequential read performance for deduplicated FlexVol volumes on page 141

Volumes with deduplication are disabled after a nondisruptive upgrade on page 142

SnapVault issues in cascaded configurations on page 142

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

Data recovery using SnapVault or SnapMirror for a qtree with LUN clonesYou can use SnapVault to perform an in-place restore for a source qtree, from the destination qtree.However, if the source qtree has LUN clones, in-place restore is not supported. The use of snapmirrorresync for restoring data to a source qtree with LUN clones is also not supported.

On replicating qtrees with LUN clones, each LUN clone within the qtree is stored as a LUN within thedestination qtree. This applies to both SnapVault and qtree SnapMirror. Therefore, when you recoverdata from such a destination qtree, the original LUN clones would be restored as complete LUNs.

SnapVault

To recover data from the destination qtree using SnapVault, you can use one of the following optionsfor a qtree with LUN clones.

• Delete the LUN clones within the source qtree, and then perform an in-place restore, using thesnapvault restore command.

Note: If you attempt an in-place restore for a qtree with LUN clones, the system displays thefollowing error message:

Qtree has lun clones

• Restore the data to a new qtree, by using the snapvault restore command.

Attention: For a qtree with LUN clones, ensure that the volume has enough free space to store theLUN clones as complete LUNs before you initiate data recovery using SnapVault or qtree SnapMirror.

Qtree SnapMirror

In case of qtree SnapMirror, to recover data for a qtree with LUN clones, you can replicate the destinationqtree to a new qtree.


Note: If you attempt to recover data from the destination to a source qtree with LUN clones, usinga snapmirror resync operation, the system displays the following error message:

cannot resync as qtree has one or more lun clonesAborting resync.

For more information about restoring data using SnapVault and SnapMirror, see the Data ONTAP DataProtection Online Backup and Recovery Guide.

Using SnapVault for NetBackup to protect applicationsStarting with Data ONTAP 7.3.1, new SnapVault for NetBackup configurations for protectingapplications are not supported.

All currently installed SnapVault for NetBackup solutions based on Data ONTAP 7.2 or Data ONTAP7.3 or later, continue to be fully supported for protecting data in applications such as Oracle, MicrosoftSQL Server, Sybase, and IBM DB2.

SnapVault for NetBackup support for protecting applications is limited to customers who are alreadyusing SnapVault for NetBackup.

SnapVault for NetBackup is not supported with Symantec Veritas NetBackup6.5

Due to a software problem with Symantec Veritas NetBackup 6.5, SnapVault for NetBackup does notwork with NetBackup 6.5. Symantec has fixed this problem in NetBackup 6.5.1 and later. SnapVaultfor NetBackup works with NetBackup 6.0MP5 or NetBackup 6.5.1 and later.

Changes to deduplication usage with SnapVault for NetBackupData ONTAP 7.3.1 and later no longer support deduplication for use with SnapVault for NetBackup.This change applies to both structured (database) and unstructured (file) data types.

Table 1: Data deduplication options for SnapVault for NetBackup with Data ONTAP 7.3.1 and later

Post-replicationThrough SnapVault forNetBackup only

Data type

NoYes, automatic inline block-sharingUnstructured (file system) data

NoNoStructured (application) data

The SnapVault for NetBackup specific inline block sharing feature, which provides deduplicationsupport for file data only, continues to be supported, and is not affected by this change. Deduplicationin a non-SnapVault for NetBackup configuration (for example, NetBackup shared or flexible diskoption) remains supported and is not affected by this change.


NetBackup managed SnapVault is unavailableStarting with the release of Data ONTAP 7.3, configuring and managing SnapVault replication betweenNetApp primary and secondary storage using Symantec VERITAS NetBackup is no longer available.NetBackup management for SnapVault replication remains available and supported when used withversions of Data ONTAP earlier than 7.3.

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 the volumecontaining the SnapVault destination qtree is owned by a nondefault vFiler unit, the SnapVault secondaryneeds to be managed through the default vFiler unit (vfiler0).

Table 2: vFiler unit support with SnapVault secondary volumes

The following table shows vFiler unit support with SnapVault secondary volumes for different combinations.

Ownership of SnapVault secondary volumeManagement of SnapVault secondary volume

Nondefault vFiler unitDefault vFiler unit (vfiler0)

YesYesDefault vFiler unit (vfiler0)

NoNoNondefault vFiler unit

The management of SnapVault primary in a vfiler context is supported.

Table 3: vFiler unit support with SnapVault primary volumes

The following table shows vFiler unit support with SnapVault primary volumes for different combinations.

Ownership of SnapVault primary volumeManagement of SnapVault primary volume

Nondefault vFiler unitDefault vFiler unit (vfiler0)

YesYesDefault vFiler unit (vfiler0)

Yes

(From a nondefault vFilercontext, you can only manage

volumes owned by thatnondefault vFiler unit.)

No

Nondefault 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 limitations applyfor SnapVault relationships involving nondefault vFiler units.

• You can only view SnapVault relationships configured through the default vFiler unit (vfiler0). Youcannot 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.

SnapVault cannot be enabled on vFiler units when SnapLock for SnapVaultrelationships are present in vfiler0

When you create SnapVault relationships for SnapLock secondary volumes in vfiler0, you also manuallyset the snapvault.lockvault_log_volume option to the name of a SnapLock for SnapVault logvolume. After this option is set, SnapVault cannot be enabled on any vFiler units on the storage system.For more information about the snapvault.lockvault_log_volume option, see the na_snapvault(1)man page.

Limitation of SnapLock for SnapVault relationshipBeginning with Data ONTAP 7.3.1, you cannot have a SnapLock for SnapVault relationship betweenthe SnapLock Compliance source and SnapLock Compliance destination volumes.

If you upgrade the storage system to Data ONTAP 7.3.1 or later, you must ensure that the destinationfor SnapLock for SnapVault relationship is not a SnapLock Compliance volume. If the destinationvolume is a SnapLock Compliance volume, the SnapVault update fails.

For more information, see Data ONTAP Archive and Compliance Management Guide.

Guidelines for creating a clone of a SnapVault destination volumeWhen creating a clone of a SnapVault destination volume, you should make sure that no SnapVaulttransfers are active for that volume.

You can check the status of SnapVault transfers by using the snapvault status -l command. Ifyou find that the status is idle, you can proceed with the creation of the volume clone. The vol clonecreate command for a SnapVault destination volume creates a writable clone if the SnapVault transferstatus is idle.

If a clone is not created, wait till the status becomes idle and then create the clone. The status shouldbe idle between scheduled SnapVault transfers.

If the clone is already created and is in the read-only state, then convert the relationship into a SnapMirrorrelationship by using the snapvault convert command. You should quiesce the relationship usingthe snapmirror quiesce command, and then break the relationship.


Compatibility with SnapDrive and Snap ManagerThis version of Data ONTAP is not supported by all versions of NetApp software for Windows clients.Before installing or upgrading to this version of Data ONTAP, make sure that the SnapManager andSnapDrive versions you are running or plan to install are compatible with this release.

For more information about supported versions of Data ONTAP for client software, see the appropriatematrix entry on the NOW site.

Related information

SnapDrive & SnapManager Compatibility Matrix:now.netapp.com/NOW/knowledge/docs/olio/guides/snapmanager_snapdrive_compatibility/index.shtml

Guidelines for creating a clone of a qtree SnapMirror destination volumeWhen using the vol clone create command to create a clone of a qtree SnapMirror destinationvolume, you need to consider the status of any qtree SnapMirror transfers for that volume.

You can check the status of SnapMirror transfers by using the snapmirror status -l command.

The following table describes the different scenarios possible, when creating a clone of a qtree SnapMirror destinationvolume.

Then, for the creation of a clone of the qtree SnapMirror destination...If the status of qtreeSnapMirror transfersfor a specific volumeis...

The clone will be writable.

Note: It is recommended that you create a clone of a qtree SnapMirror destination,when the status is idle.

Idle

You can specify a Snapshot copy that is older than any of the Snapshot copies beingused for transfers. In this case, the clone will be writable.

Active

If you do not specify a Snapshot copy for the creation, the clone will be read-only.

For a read-only clone created when a SnapMirror transfer is active for the volume, theSnapMirror relationship is active for the clone. Therefore, for the clone, you need toquiesce the SnapMirror transfer and break the SnapMirror relationship. This wouldmake the clone writable.

Note: The original SnapMirror transfer or relationship need not be modified. Youonly need to change the status of the clone to make it writable.

Note: If you use the snapmirror quiesce or snapmirror break command on a writable clone,then the storage system displays an error message and proceeds without effect.

For more information about creating volume clones, see the Data ONTAP Storage Management Guide.


http://now.netapp.com/NOW/knowledge/docs/olio/guides/snapmanager_snapdrive_compatibility/index.shtml

http://now.netapp.com/NOW/knowledge/docs/olio/guides/snapmanager_snapdrive_compatibility/index.shtml

FlexVol volume limits with SnapMirror on a FAS250 storage systemThe FAS250 storage system supports a maximum of 200 FlexVol volumes.

When you use SnapMirror to migrate FlexVol volumes to a FAS250 storage system, you should ensurethat the FlexVol volumes on the destination storage system are accessible, before removing the originaldata from the source storage system.

Note: As a best practice, due to the memory limitations of a FAS250 storage system, the recommendedlimit for FlexVol volumes is 100.

Synchronous SnapMirror not supported for volumes with deduplicationVolumes using deduplication cannot be replicated using synchronous SnapMirror.

SMB 2.0 not supported for SnapLockIn Data ONTAP 7.3.1 and later, Server Message Block (SMB) 2.0 is supported. However, the SnapLockfunctionality does not support SMB 2.0.

Possible effect of creating more than 64 mirrored aggregates preventingdisaster recovery from functioning correctly

If 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 aggregates persystem, even though Data ONTAP does not prevent you from doing so.

Protection Manager 3.7 does not perform optimally with deduplicationIntegration with deduplication does not work optimally with Protection Manager 3.7 because theretention of Snapshot copies causes deduplicated blocks to be locked within the Snapshot copies. Inthis case, deduplication savings will be limited

Do not use Protection Manager 3.7 on volumes that have deduplication enabled.

Improved sequential read performance for deduplicated FlexVol volumesIn Data ONTAP 7.2.6 and later releases of the Data ONTAP 7.2 release family, and in Data ONTAP7.3.1, the performance of sequential read operations on large deduplicated VMDK files has improved.

In VMware environments, the VMDKs are created with a large number of duplicate blocks. This resultsin a high number of shared blocks after running deduplication. Therefore, applications that performlarge sequential read operations, such as dump, have low throughput when run on VMDK files.


In Data ONTAP 7.2.6 and later releases of the Data ONTAP 7.2 release family, and in Data ONTAP7.3.1, highly shared blocks are efficiently cached and read from the in-memory cache instead of thedisk every time. This caching improves the sequential read performance on VMDK files.

Volumes with deduplication are disabled after a nondisruptive upgradeIn an active/active configuration with a two- node cluster, when one node performs a nondisruptiveupgrade to Data ONTAP 7.3 or Data ONTAP 7.3.1 from a release prior to the Data ONTAP 7.3 releasefamily, the nodes are updated sequentially. Deduplication is disabled for the volumes on the secondnode that is upgraded.

If the takeover storage system has been upgraded to Data ONTAP 7.3 or Data ONTAP 7.3.1, andassumes the functions of the “failed” partner while it is being upgraded, deduplication is disabled onthe volumes belonging to the “failed” node running the earlier release.

After the takeover, deduplication schedules set in the earlier release are reset on those volumes.

After both the nodes have been upgraded, deduplication has to be reenabled and deduplication schedulesreconfigured for each volume impacted.

You can use the sis status command to view the deduplication status of the volume, and the sison command to enable deduplication.

You can use the following command to check deduplication schedules:

• sis config

You can use the following command to set deduplication schedules:

• sis config -s schedule path

Note: Before you start performing a nondisruptive upgrade, make a list of volumes enabled withdeduplication and their schedule so that they can be reconfigured after the nondisruptive upgrade iscomplete.

Note: Upgrades within the same Data ONTAP release family (minor nondisruptive upgrade betweenData ONTAP 7.3 and Data ONTAP 7.3.1) does not disable deduplication.

SnapVault issues in cascaded configurationsYou might encounter a disruption in service during SnapVault operations involving cascadedconfigurations.

A disruption in service during a SnapVault operation might occurs during one of the following scenarios:

• While using SnapVault to protect a volume SnapMirror destination or while using volume SnapMIrrorto protect a SnapVault destination, if any of the volumes in the cascade is a SnapLock volume, youmight encounter a disruption in service. For more information, refer to Bug ID 388751.

• Starting with Data ONTAP 7.3.2, if you are using SnapVault schedules to backup qtrees in a volumeSnapMirror destination volume and if you have not configured the corresponding SnapVault primary


schedules on the volume SnapMirror primary volume, SnapVault backups can fail. For moreinformation, refer to Bug ID 393481.

Related information

Bug ID 393481

Bug ID 388751

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 with existingdata and with the 16-GB Performance Acceleration Module installed, you obtain suboptimal spacesavings.

Storage resource management issuesIf you have more than one size of disk installed in your storage system, if you have configured quotas,if you use FlexCache volumes, or if you are using FlexVol volumes on FAS250 systems, you shouldfamiliarize yourself with these storage resource management issues.

Next topics

The all keyword for the aggr add command is not yet implemented on page 143

Moving disks to a system running an earlier version of Data ONTAP could cause disk identificationissues on page 144

Data ONTAP can silently select varying disk or array LUN sizes when enlarging or creating anaggregate on page 144

Qtree quotas might prevent explicit quotas from overriding the default on page 145

FlexVol volume limit for FAS250 systems on page 145

Offline nodes in origin cluster can affect FlexCache volume performance on page 146

Adding a FlexCache origin volume to a vFiler unit might cause caching system to panic on page 146

Offline status of origin volume running Data ONTAP 10.0 not correctly reported on FlexCachevolume on page 146

The all keyword for the aggr add command is not yet implementedThe all keyword for the -g option of the aggr add command, which should cause Data ONTAP tofill all existing RAID groups before creating any new ones, has no effect.




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 a storagesystem running a version of Data ONTAP earlier than 7.3, the software disk ownership informationwill be incorrect for the earlier version and might prevent Data ONTAP from identifying or correctlyassigning 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 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.

Data ONTAP can silently select varying disk or array LUN sizes when enlargingor creating 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 or add storage to an existing aggregate using automatic disk selection,Data ONTAP selects disks or array LUNs based on various criteria including size, speed, and checksumtype. To ensure that the selected disks or array LUNs are the size you want, specify the disk or arrayLUN size when creating or increasing the size of an aggregate.

For more information, see Bug ID 147711 in Bugs Online and the na_aggr(1) man page.

Next topics

Adding disks when varying sized disks are in use on page 144

Discovering what disks Data ONTAP will automatically select on page 145

Related information

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

Adding disks when varying sized disks are in use

When you have disks of different sizes available, always specify the disk size when creating or addingto 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 add command.

When you use the -n option, the disks that would be selected automatically, if you created an aggregateor added to an aggregate, are displayed. The creation or addition is not performed. If the selected disksare not what you intended, you can specify a disk list when you enter the aggr create or aggr addcommand.

Step

1. To list the disks that would be selected for an aggr create command, enter the following command:

aggr create aggr_name -n disk_list

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

Qtree quotas might prevent explicit quotas from overriding the defaultIf you are overriding a default user or group quota in a volume that has qtrees with quotas applied, theoverride will not apply within those qtrees unless you also apply the override explicitly to those qtrees.

If you have a default user or group quota on a volume, and you want to override that default quota fora particular user or group, note this issue: If you also have one or more qtree quotas on that volume,the explicit quota might not take precedence over the default quota within those qtrees as expected.

FlexVol volume limit for FAS250 systemsIt is recommended that you not create more than 100 FlexVol volumes on FAS250 systems because oftheir low memory capacity.


Offline nodes in origin cluster can affect FlexCache volume performanceIf a FlexCache origin volume is on a system running Data ONTAP 10.0.3 or later, and any of the nodesin the cluster for that system is offline when the FlexCache connection is established, delegations arenot provided for that FlexCache volume.

Not having delegations can result in more requests to the origin to verify attributes.

For best FlexCache volume performance, ensure that all of the nodes in the cluster containing the originvolume are online when you create the FlexVol volume or reestablish the FlexCache connection.

Adding a FlexCache origin volume to a vFiler unit might cause caching systemto panic

If you attempt to add a FlexCache origin volume with existing FlexCache cache volumes to a vFilerunit using either the vfiler create or vfiler add command, the systems that contain theFlexCache cache volumes might panic.

To avoid this issue, destroy all FlexCache volumes backed by the origin volume before adding theorigin volume to a different vFiler unit.

Offline status of origin volume running Data ONTAP 10.0 not correctly reportedon FlexCache volume

If a FlexCache volume is backed by an origin volume on a system running a version of Data ONTAPin the 10.0 release family, and that origin volume is offline, you need to run the vol status commandon the origin system to confirm whether the origin volume is offline.

Normally, if the origin volume for a FlexCache volume is offline, the output of the vol statuscommand for the FlexCache volume shows the following status string:

• rem vol unavail

This status indicates that the origin volume is offline. However, if the offline origin volume is on asystem running a version of Data ONTAP in the 10.0 release family, this string is not shown.

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

Exceeding the maximum number of assigned devices results in a panic on page 147

No support for REP with zone checksum type array LUNs on page 147


Limitation on EMC CX storage array LUN numbering on page 147

Exceeding the maximum number of assigned devices resultsin a panic

If more than 256 array LUNs from a specific storage array target port to a specific V-Series FC initiatorport are assigned to a V-Series system, the V-Series system panics when you try to boot it.

No more than 256 array LUNs from a specific storage array port to a specific V-Series FC initiator portshould be assigned (in the Data ONTAP configuration) to a V-Series system. This is a Data ONTAPlimitation. If more than 256 LUNs from the same storage array port to the same V-Series FC initiatorport are assigned to the V-Series system, the V-Series system panics if you try to boot it and issues amessage 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.

No support for REP with zone checksum type array LUNsRAID Error Propagation (REP) is not supported with volumes and aggregates that contain zone checksumtype array LUNs.

Limitation on EMC CX storage array LUN numberingIf you are not using Storage Groups on your CX storage array, do not assign LUN numbers greater than254 to array LUNs for V-Series.

If you are not using Storage Groups, the CX storage array might not present internal LUNs numbersgreater than 254 to your V-Series system. If this occurred, V-Series would not be able to see those arrayLUNs.

If you are using Storage Groups, the CX storage array automatically assigns internal LUN numberslower than 255.


Active/active configuration issuesIf you are using the cf.takeover.on_network_interface_failure option, you might need tofamiliarize yourself with this active/active configuration issues.

For more information about these issues, see the Data ONTAP Active/Active Configuration Guide.

If takeover is enabled for network interface failure, automatic giveback shouldbe 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.


Changes to published documentation

Some information about the Data ONTAP 7.3 release family has become available after the set of guidesprovided with this release were published. The information should be used in conjunction with theguides provided with this release of Data ONTAP.

Next topics

Changes to the Archive and Compliance Management Guide on page 149

Changes to the Commands Manual Page Reference on page 150

Changes to the Data Protection Online Backup and Recovery Guide on page 150

Changes to the Data Protection Tape Backup and Recovery Guide on page 151

Changes to the File Access and Protocols Management Guide on page 151

Changes to the V-Series Implementation Guide for IBM Storage on page 152

Changes to the V-Series Implementation Guide for Native Disk Shelves on page 152

Array LUN sizing with 2 TB disks is not documented in all V-Series Implementation Guideson page 153

Changes to cross-references to SnapLock information on page 153

Changes to the Upgrade guide on page 153

Changes to the Archive and Compliance Management GuideNew information has become available since the previous revision of the Archive and ComplianceManagement Guide.

Next topics

Changes to cross-references to SnapLock information on page 153

Integration of third-party applications with SnapLock feature on page 150

Changes to cross-references to SnapLock informationStarting with Data ONTAP 7.3.1, the SnapLock feature is explained in Data ONTAP Archive andCompliance Management Guide.The cross-references to SnapLock in Data ONTAP SystemAdministration Guide, Data ONTAP Storage Management Guide, and Data ONTAP DocumentationRoadmap incorrectly reference the Data ONTAP Data Protection Online Backup and Recovery Guide.

Changes to published documentation | 149

Integration of third-party applications with SnapLock featureStarting with Data ONTAP 7.3.3, information about integrating third-party applications with theSnapLock feature by using Manage ONTAP SDK is provided in Data ONTAP Archive and ComplianceManagement Guide .

Changes to the Commands Manual Page ReferenceNew information has become available since the previous revision of the Data ONTAP Commands:Manual Page Reference.

The na_ping6(1) man page lists incorrect optionsThe -a option and its sub-options listed in the na_ping6(1) man page are not supported in Data ONTAP.The -s option in the na_ping6(1) man page is incorrect. Instead, you must use the -d option to specifythe data packet size with the ping6 command.

Changes to the Data Protection Online Backup and RecoveryGuide

New information has become available since the previous revision of the Data Protection Online Backupand Recovery Guide.

Syntax entry correction in the snapmirror.conf fileIn the section titled "Enabling compression for a SnapMirror transfer" in the Data ONTAP DataProtection Online Backup and Recovery Guide, the syntax entry in the snapmirror.conf file that isrequired for enabling compression and the corresponding examples are incorrect.

The incorrect syntax entry for enabling compression in Step 3 is as follows:

connection_name:src_vol dst_system:dst_vol compression=enable - * * * *

The correct syntax entry for enabling compression is:

connection_name:src_vol dst_system:dst_vol compression=enable * * * *

The incorrect syntax entry in the example of step 3 is as follows:

conxn_1:src_vol dst_system:dst_vol compression=enable - * * * *

The correct syntax entry in the example of Step 3 is as follows:

conxn_1:src_vol dst_system:dst_vol compression=enable * * * *


The incorrect syntax entry in the "Compression for a multipath SnapMirror relationship" example is asfollows:

connection_name:src_vol dst_system:dst_vol compression=enable - * * * *

The correct syntax entry in the "Compression for a multipath SnapMirror relationship" example is asfollows:

connection_name:src_vol dst_system:dst_vol compression=enable * * * *

Changes to the Data Protection Tape Backup and RecoveryGuide

Some additional information about tape backup features has become available since the previous revisionof the Data ONTAP Data Protection Tape Backup and Recovery Guide.

Backing up data to tape using NDMP servicesBacking up data to tape using NDMP services has been moved to the Data Protection Tape Backupand Recovery Guide.

For more information about backing up data to tape using NDMP services, see the Data ProtectionTape Backup and Recovery Guide.

Changes to the File Access and Protocols Management GuideNew information has become available since the previous revision of the Data ONTAP File Access andProtocols Management Guide.

Next topics

Correction for disabling virus scanning on page 151

Enhancements to NFS access cache management on page 152

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

cifs shares -change sharename novscanread


Enhancements to NFS access cache managementBeginning in Data ONTAP 7.3.3, the exportfs command includes new functionality that is not listedin the "Adding entries to the access cache" and "Removing entries from the access cache" topics onpages 30 and 31 of the Data ONTAP File Access and Protocols Management Guide.

The -c option of the exportfs command has been updated to take multiple IP addresses as arguments.This enables verification of current export rights for multiple clients in one operation.

The -f option of the exportfs command now includes a -n parameter, which allows you to flushaccess cache entries that correspond to a specific host.

For more information, see the exportfs(1) man page.

Changes to the V-Series Implementation Guide for IBM Storage

The V-Series Implementation Guide for IBM Storage dated July 2009, part number 210-04510_A0contains a statement on page 28 warning about using a specific layout with a DS4xxx storage array.This statement should also warn against using this layout with a DS5xxx storage array. The informationon this page should read as follows:

Attention: Do not use this layout if your configuration includes a DS4xxx storage array, DS5xxxstorage array, or any other storage array that implements standby paths to storage. The reason is thatif a switch fails, the V-Series systems can only access the array LUNs through opposite storage arraycontrollers. Performance can degrade to the point where the data is unavailable because every accessto an array LUN requires Data ONTAP to first change the LUN’s affinity.

Changes to the V-Series Implementation Guide for Native DiskShelves

Always check the shipping date of your AT-FCX modules if you are unsure that they meet the disktype requirements.

The V-Series Implementation Guide for Native Disk Shelves dated December 2008, part number210-04321_A0, contains a statement on page 65 that implies you should check the version of AT-FCXmodules only if you are moving a disk shelf from a FAS system to a V-Series system. In fact, youshould always check the version of the AT-FCX modules if you are unsure if they meet the requirementsfor disk types that V-Series supports. The information on page 65 should read as follows:

Note: Only AT-FCX modules shipped in December 2005 or later are supported. If you are unsurewhether your module is the correct version, see the Data ONTAP Active/Active Configuration Guidefor the procedure for checking the version of the AT-FCX module.


Array LUN sizing with 2 TB disks is not documented in allV-Series Implementation Guides

Starting with Data ONTAP versions 7.3.3 and 8.0, 2 TB drives are supported on arrays configured withV-Series systems. These larger drives increase the maximum usable size supported for array LUNs.

Not all of the V-Series Implementation Guides have been updated to include the supported maximumarray LUN sizes. To calculate the maximum array LUN sizes supported with the 2 TB drives, doublethe maximum usable value that is provided for array LUNs with Data ONTAP 7.3.2. The maximumusable values are provided in the Guidelines for array LUN sizing section of the Implementation Guides.

Changes to cross-references to SnapLock informationStarting with Data ONTAP 7.3.1, the SnapLock feature is explained in Data ONTAP Archive andCompliance Management Guide.The cross-references to SnapLock in Data ONTAP SystemAdministration Guide, Data ONTAP Storage Management Guide, and Data ONTAP DocumentationRoadmap incorrectly reference the Data ONTAP Data Protection Online Backup and Recovery Guide.

Changes to the Upgrade guideNew information about various topics has become available since the previous revision of the DataONTAP Upgrade Guide.

Corrections to the "Deduplication requires additional free space in aggregatesafter upgrading" section

The following existing content is incorrect: Before running deduplication for the first time, you shouldensure that the aggregate has free space that is at least 4 percent of the total data usage for all volumesin the aggregate, in addition to 2 percent free space for FlexVol volumes.

This content is corrected as follows: Before running deduplication for the first time, you should ensurethat the aggregate has free space that is at least 4 percent of the total data usage for all volumes in theaggregate that have deduplication enabled, in addition to 2 percent free space for FlexVol volumes.


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 reports andwhite papers, in the NetApp Library at www.netapp.com.

Next topics

The Documentation Roadmap on page 155

Searching online information on page 156

Finding documentation on NOW on page 156

Related information

NetApp on the Web (NOW) site: now.netapp.com

Access & Order Product Documentation: now.netapp.com/knowledge/docs/docs.shtml

NetApp Library: Technical Reports: www.netapp.com/library/tr

The Documentation RoadmapThe Documentation Roadmap lists NetApp documents and other information that can help you configureand administer your storage system.

The Documentation Roadmap, which you can find on the Data ONTAP Documentation page for thisrelease on the NOW site, lists NetApp documents and NOW pages (including such things as tools andtechnical reports) that can help you complete the following major tasks:

• Installing new NetApp systems

• Configuring new NetApp systems

• Upgrading Data ONTAP software on NetApp systems

• Managing NetApp systems

• Diagnosing and troubleshooting problems

• Customizing or automating processes

Note: V-Series documents are not included in the Documentation Roadmap. See the V-Seriesdocuments on the NOW site.

Where to find product documentation and other information | 155

http://now.netapp.com

http://now.netapp.com/knowledge/docs/docs.shtml

http://www.netapp.com/library/tr/

Searching online informationThe NOW site includes a natural language search tool.

The NOW Natural Language PowerSearch tool on the Service and Support page on the NOW siteallows you to search the following sources of information:

• Product manuals

• Knowledgebase solutions

• Bugs online

• Tools/other documentation

• Partner knowledgebases

Related information

Service and Support: now.netapp.com/eservice/SupportHome.jsp

Finding documentation on 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, followthe Documentation links on the NOW site to the Information Library page. You can use this path oflinks from the NOW home page:

Technical Assistance and Documentation ➤ Access and Order Product Documentation ➤ DataONTAP ➤ Data ONTAP 7-Mode and later: Filer and V-Series systems


http://now.netapp.com/eservice/SupportHome.jsp

Date post:	26-Mar-2018
Category:	Documents
Upload:	nguyennguyet
View:	225 times
Download:	2 times

Data ONTAP 7.3.3 Release Notes - Waterloo Computer ...ehashman/netapp/ontap/rnote.pdfMore concurrent...

Documents