Data ONTAP® 8.2.1

Release Notes

For 7-Mode

Updated for 8.2.1

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089U.S.

Telephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 463-8277Web: www.netapp.comFeedback: doccomments@netapp.com

Part number: 215-08535_A0 ur003April 2014

Contents

Data ONTAP 8.2.1 Release Notes for 7-Mode ......................................... 10Changes introduced since Data ONTAP 8.2 ............................................ 12

Changes in Data ONTAP 8.2.1 for 7-Mode .............................................................. 12

Unsupported features ................................................................................. 17Functionality changes in future releases .................................................. 18New and changed features in the Data ONTAP 8.2 release family for

7-Mode .................................................................................................... 19New and changed platform and hardware support .................................................... 19

Support for the FAS80xx platform ................................................................ 19

Support for 400-GB SSDs ............................................................................. 19

Support for 1.6-TB SSDs .............................................................................. 19

Support for SAS optical cables ..................................................................... 20

Support for shelf hot-remove ........................................................................ 20

Support for 800-GB SSDs ............................................................................. 20

Support for 1.2-TB performance disks .......................................................... 20

3210 and 3140 systems with Flash Cache modules not supported ............... 21

Support for Flash Cache 2 modules .............................................................. 21

Manageability enhancements .................................................................................... 21

Support for histogram-based predictions in RAVE ...................................... 21

The system node service-processor commands now support the RLM ........ 21

Licensing changes for the Data ONTAP 8.2 release family ......................... 22

New command family for managing the SP from Data ONTAP .................. 23

Enhancements for delivery of AutoSupport messages .................................. 24

Enhancements to health monitoring .............................................................. 25

Messages in the /etc/messages file now include the system name ................ 25

Options for specifying uppercase and lowercase requirements in user

passwords ................................................................................................ 25

High-availability pair enhancements ......................................................................... 25

Support for 16 Gb FC-VI adapters in a MetroCluster configuration ............ 26

Support for SSDs in a MetroCluster configuration ....................................... 26

New cf.mode option replaces the cf license .................................................. 26

Table of Contents | 3

Support for unidirectional port mirroring in a MetroCluster

configuration ............................................................................................ 26

Support for ISL encryption in a MetroCluster configuration ........................ 26

Storage resource management enhancements ........................................................... 26

Increased maximum aggregate sizes for some FAS80xx systems ................ 26

Aggregates can be expanded to 64-bit format without adding storage ......... 27

Increased maximum Flash Pool cache sizes for FAS22xx systems .............. 27

Automated Workload Analyzer for Flash Pool cache sizing ........................ 27

Increased maximum aggregate size for some platforms ............................... 27

Multi-disk carrier and single-disk carrier disk shelves can be combined

in the same stack ...................................................................................... 27

Flash Pool aggregates support different RAID types and group sizes for

SSD cache ................................................................................................ 27

Flexibility for calculating maximum Flash Pool SSD cache size in HA

configurations .......................................................................................... 28

Aggregate Snapshot copy automatic deletion is always enabled .................. 28

Disabled volume guarantees no longer reenabled automatically .................. 28

Fractional reserve setting can be set only to 0 or 100 ................................... 28

Storage efficiency enhancements .............................................................................. 29

Support for detecting incompressible data in files ........................................ 29

FlexArray Virtualization (V-Series) enhancements .................................................. 29

Support for storage arrays on FAS systems .................................................. 29

V-Series functionality renamed as FlexArray Virtualization ........................ 29

Licensing requirement for Data ONTAP systems to use array LUNs .......... 30

Licensing enhancement in V-Series systems ................................................ 30

New storage arrays supported in Data ONTAP 8.2 ...................................... 30

Support added for one Data ONTAP FC initiator connecting to multiple

array target ports ...................................................................................... 30

Increased LUN count per Data ONTAP FC initiator .................................... 31

Support added for native disks in a MetroCluster configuration that

supports array LUNs ................................................................................ 31

Support added for SAS optical cables in MetroCluster configurations

that use array LUNs ................................................................................. 32

Enhancements for setting the target queue depth on a Data ONTAP

system that uses array LUNs ................................................................... 32

Array LUN limits information is now in the Hardware Universe ................. 32

4 | Release Notes

File access protocol enhancements ........................................................................... 32

Support for VMware vStorage over IPv6 ..................................................... 33

Maximum ACE limit for NFSv4 ACLs has increased .................................. 33

Support for SMB 2.x authentication with CIFS workgroup mode ............... 33

Enhancements for management of unresponsive LDAP servers .................. 33

Enabling new EMS messages to help troubleshoot Kerberos issues ............ 34

CIFS TCP window size increased to 64,240 bytes ....................................... 34

Data protection enhancements .................................................................................. 34

Support for multipath tape access ................................................................. 34

Support for Single SnapVault license ........................................................... 35

SyncMirror is enabled by default .................................................................. 35

Options for enabling the SnapLock functionality ......................................... 35

Automatic resizing of SnapMirror destination for a FlexVol volume .......... 35

Users cannot perform certain Qtree SnapMirror and SnapVault tasks

during the post-upgrade operations ......................................................... 35

Serial numbers used for tape aliasing ............................................................ 36

Data ONTAP Edge enhancements ............................................................................ 36

Data ONTAP changes that affect Data ONTAP Edge .................................. 37

Data ONTAP Edge and dvadmin changes .................................................... 37

Summary of new and changed commands and options in the DataONTAP 8.2 release family operating in 7-Mode ................................. 38

New commands in Data ONTAP 8.2 ........................................................................ 38

Changed commands in Data ONTAP 8.2 ................................................................. 40

Replaced or removed commands in Data ONTAP 8.2 ............................................. 46

New options in Data ONTAP 8.2 .............................................................................. 46

Changed options in the Data ONTAP 8.2 release family ......................................... 49

Requirements for running Data ONTAP 8.2 ........................................... 51Supported systems ..................................................................................................... 51

Unsupported systems ................................................................................................. 52

Where to get the latest firmware versions ................................................................. 52

FlexArray Virtualization (V-Series) interoperability and limits information ........... 53

Data ONTAP-v requirements and support information ............................................ 54

Important cautions ..................................................................................... 55Upgrade cautions ....................................................................................................... 55

Change in how Data ONTAP handles file names containing UTF-16

supplementary characters ........................................................................ 55

Table of Contents | 5

Compatible versions of management software are required ......................... 55

If you are using synchronous SnapMirror, upgrading to Data ONTAP

8.2 can cause performance degradation ................................................... 56

3210 and 3140 systems with Flash Cache modules not supported ............... 56

Modifying the state of deduplication during an intermediate upgrade can

cause storage system disruption .............................................................. 56

Disks offline in Windows Server 2008 and 2012 after Data ONTAP

upgrade .................................................................................................... 56

Stale metadata not automatically removed during deduplication

operations on volume .............................................................................. 57

Manageability cautions ............................................................................................. 57

If you reinstall a license key in Data ONTAP 8.2 or later, you must use

the new license key format ...................................................................... 57

Changes to SP firmware update methods ...................................................... 58

Storage management cautions ................................................................................... 59

Disk failures might increase for some disk models after upgrading to

this version of Data ONTAP ................................................................... 59

File access and protocols cautions ............................................................................ 60

CIFS startup might take several minutes after HA failover and giveback .... 60

Revert and downgrade cautions ................................................................................ 61

Reverting to a release earlier than Data ONTAP 8.2 might require

installation of licenses for some features ................................................. 61

Licensing implications for reverting a system that is shipped with Data

ONTAP 8.2 or later to an earlier release ................................................. 62

Downgrading or reverting to Data ONTAP 8.1 or earlier with a Flash

Pool aggregate root aggregate disables the system ................................. 62

SP firmware might require a downgrade if you revert or downgrade to

an earlier Data ONTAP release ............................................................... 62

Reverting to an earlier release of Data ONTAP when 32-bit volumes or

aggregate are converted to 64-bit format ................................................. 63

ACLs containing more than 400 ACEs are dropped during revert ............... 63

Known problems and limitations .............................................................. 64Manageability issues ................................................................................................. 64

Command typed in from one connection might be executed by a

concurrent connection ............................................................................. 64

6 | Release Notes

The wrfile command might fail to capture all input during a cut-and-

paste operation performed through the RLM or SP ................................ 64

Storage resource management issues ........................................................................ 65

Long disk list for aggregate creation could cause disruption ........................ 65

Storage system disruption due to unavailability of asynchronous

messages .................................................................................................. 65

Out of space errors could be returned when fractional reserve is set to

zero .......................................................................................................... 65

Disk-type mixing might occur even when disk type is specified .................. 66

Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded ............................................................. 66

FlexArray Virtualization (V-Series) issues ............................................................... 67

Too many storage devices presented to the Data ONTAP system ................ 67

Some Hitachi or HP XP array LUNs might not be visible ............................ 67

Network protocol issues ............................................................................................ 68

Restriction on using auto-configured LLA as a gateway for a default

route ......................................................................................................... 68

Error messages observed during change in the state of network interface

groups ...................................................................................................... 68

SNMPv3 access might fail for an existing user ............................................ 68

Existing traphosts fail to receive SNMP traps .............................................. 69

The first VLAN configured over a port might bring the port down

temporarily .............................................................................................. 69

SnapMirror transfer cannot be blocked by using the

interface.blocked.mgmt_data_traffic option ........................................... 69

Partner node might be unavailable during controller failover ....................... 70

Disabling fast path in some network environments ...................................... 70

File access and protocols issues ................................................................................ 71

Data ONTAP LDAP client does not support revoked certificates ................ 71

Option nfs.export.allow_provisional_access is nonfunctional ...................... 71

“Access denied” error when setting an ACL on the root directory of an

empty share .............................................................................................. 71

Number of existing locks larger than the maximum allowed limit after

upgrade .................................................................................................... 72

CIFS client authentication fails if host name exceeds 16 characters ............ 72

Table of Contents | 7

Excessive pending CIFS authentication requests can cause service

disruption ................................................................................................. 73

Microsoft Windows 7 and Windows 8 clients fail to rename files and

directories ................................................................................................ 73

Domain user unable to execute CLI commands ............................................ 73

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

CIFS widelinks are not accessible from Mac clients .................................... 74

Data ONTAP permits deleting a file when an alternate data stream of

the file is in use ........................................................................................ 74

VAAI copy offload limitations when exporting datastore volumes with

the actual flag .......................................................................................... 75

NFS VAAI copy offload uses block copy if the volume does not have

SIS enabled .............................................................................................. 75

Data protection issues ................................................................................................ 76

SnapVault cannot be enabled on vFiler units when SnapLock for

SnapVault relationships are present in vfiler0 ......................................... 76

SMTape operations abort if you turn off SnapMirror ................................... 76

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

DAR fails if the file and the LUN have the same name on the

destination volume ................................................................................... 76

SAN administration issues ........................................................................................ 77

Some Oracle Linux systems using ASMlib fail to recognize disk groups

when upgrading Data ONTAP ................................................................ 77

SAN configuration issues .......................................................................................... 77

Unified Target Adapter 2 (UTA2) in NetApp collateral is referred to as

CNA in product documentation ............................................................... 77

MultiStore issues ....................................................................................................... 78

vFiler unit migration using no-copy transfer not supported in a

MetroCluster configuration ..................................................................... 78

Online migration of vFiler units is not supported on Flash Pools ................. 78

Changes to published documentation ....................................................... 79Changes to V-Series document titles ........................................................................ 79

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

Missing options in the 7-Mode Command Reference Guide ........................ 79

Changes to the SAN Configuration Guide for 7-Mode ............................................. 80

Incorrect PVR requirements listed for shared SAN configurations .............. 80

8 | Release Notes

FAS80xx multifabric HA configuration has incorrect illustration ................ 81

Changes to the Data ONTAP Storage Management Guide for 7-Mode ................... 81

Physically moving an aggregate composed of disks ..................................... 81

Changes to the Archive and Compliance Management Guide ................................. 82

Correction to SnapLock support for Storage Encryption .............................. 82

Changes to the Upgrade and Revert/Downgrade Guide ........................................... 82

Data compression does not need to be reenabled after upgrade ................... 82

Changes to the FlexArray Virtualization Implementation Guide for Third-Party

Storage ................................................................................................................. 82

Workaround when LUNs are not visible with Hitachi or HP XP storage

arrays ....................................................................................................... 83

Changes to the FlexArray Virtualization Installation Requirements and

Reference Guide .................................................................................................. 84

Incorrect reference to a V-Series guide ......................................................... 84

Where to find product documentation and other information .............. 85Information available online ..................................................................................... 85

Finding documentation on the NetApp Support Site ................................................ 85

Copyright information ............................................................................... 86Trademark information ............................................................................. 87How to send your comments ...................................................................... 88

Table of Contents | 9

Data ONTAP 8.2.1 Release Notes for 7-Mode

The release notes describe new features, enhancements, and known issues for this release, as well asadditional information related to running this release on specific storage systems.

About the Data ONTAP 8.2.1 release

Data ONTAP 8.2.1 is a General Availability (GA) release and the first maintenance release in theData ONTAP 8.2 release family. For more information about Data ONTAP releases, see the DataONTAP Release Model on the NetApp Support Site.

If you are upgrading to this Data ONTAP release or reverting from this release to an earlier release,see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

Attention: If you have a 3210 or 3140 storage system with Flash Cache modules installed, do notupgrade to Data ONTAP 8.2 for 7-Mode. Flash Cache modules are not supported on 3210 or 3140systems running Data ONTAP 8.2 for 7-Mode.

For a complete list of functionality changes introduced in this release, see New and Changed featuresin the Data ONTAP 8.2 7-Mode Release Family on page 19.

Some Data ONTAP features are not supported in this release. For more information, see Unsupported features on page 17.

Name change for the V-Series functionality in Data ONTAP 8.2.1 RC2

Starting with Data ONTAP 8.2.1 RC2, the capability of using LUNs on a storage array, formerlyidentified as V-Series functionality, has a new name—Data ONTAP FlexArray VirtualizationSoftware. FlexArray Virtualization is supported as a licensed feature on all the new FAS platformsreleased with Data ONTAP 8.2.1 and later.

About these release notes

All of the information in this document applies to the Data ONTAP 8.2 release and later DataONTAP 8.2.x releases for 7-Mode for NetApp storage systems (FAS systems and V-Series systems),unless noted.

It is a best practice for all Data ONTAP users to review these release notes.

• If Data ONTAP is already running on storage systems in your environment, you shouldfamiliarize yourself with relevant topics before upgrading to Data ONTAP 8.2.

• If this is the first deployment of storage systems running Data ONTAP in your environment, youshould also refer to the Data ONTAP Information Library page for this release on the NetAppSupport Site.

• For more information about all Data ONTAP releases, see the Data ONTAP Release Model onthe NetApp Support Site.

10 | Release Notes

Related information

Data ONTAP Release Model: support.netapp.com/NOW/products/ontap_releasemodel/post70.shtmlData ONTAP Information Library page: support.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml

Data ONTAP 8.2.1 Release Notes for 7-Mode | 11

Changes introduced since Data ONTAP 8.2

You can find information about the changes that were introduced with each release since DataONTAP 8.2 in this section.

• If you are new to the Data ONTAP 8.2 release family, go directly to New and changed features inthe Data ONTAP 8.2 release family on page 19.

• All Data ONTAP releases include bug fixes.For more information, including bugs fixed in different releases, see the NetApp Support Site at support.netapp.com.

Changes in Data ONTAP 8.2.1 for 7-ModeThe Data ONTAP 8.2.1 release for 7-Mode includes support for new hardware, softwareenhancements, and bug fixes.

New platform and hardware support

This release includes support for the following new platform hardware:

• Support for the FAS8000 platform on page 19• Support for 400-GB SSDs on page 19• Support for 1.6-TB SSDs on page 19• Support for SAS optical cables on page 20• Support for shelf hot-remove on page 20

For more information, see New platform and hardware support on page 19.

New and changed features

This release includes the following new and changed features:

Manageability enhancements on page 21

• Support for histogram-based predictions in RAVE on page 21• The system node service-processor commands now support the RLM on page 21

High-availability pair enhancements on page 25

• Support for 16 Gb FC-VI adapter in a MetroCluster configuration on page 26• Support for SSDs in a MetroCluster configuration on page 26• Support for Unidirectional port mirroring in a MetroCluster configuration on page 26• Support for ISL encryption in a MetroCluster configuration on page 26

Storage resource management enhancements on page 26

12 | Release Notes

• Increased maximum aggregate sizes for some 80xx systems on page 26• Aggregate expansion to 64-bit format without adding storage on page 27• Increased maximum Flash Pool cache sizes for FAS22xx systems on page 27• Automated Workload Analyzer tool for Flash Pool cache sizing on page 27

FlexArray Virtualization enhancements on page 29

• Support for array LUNs on FAS systems on page 29• V-Series name change to FlexArray Virtualization on page 29• Licensing requirement for Data ONTAP systems to use array LUNs on page 30• Support added for one Data ONTAP FC initiator connecting to multiple target ports on page 30• Support added for SAS optical cables in MetroCluster configuration that use array LUNs on page

32• Licensing enhancement in V-Series systems on page 30

File access protocol enhancements on page 32

• Support for VMware vStorage over IPv6 on page 33• CIFS TCP window size increased to 64240 bytes on page 34

New and changed commands and options

This release includes the following new and changed commands and options:

New commands on page 38

• system node service-processor

Manages the Remote LAN Module.• ic unidirectional_mirroring

Enables or disables the unidirectional port mirroring.• fcvi ping adapter address

Pings a remote FC-VI port in same fabric.• fcvi logins adapter

Lists all the ports to which the FC-VI adapter logs in.

Changed commands on page 40

• aggr 64bit-upgrade start

This command is now available at the advanced privilege level.• snap list

The -fs-block-format option is added. This option enables the administrator to determinewhether 32-bit format Snapshot copies are present.

• sysconfig

This command now reports unknown and unsupported shelf types.• vol status

The -F and -S options are updated to accept the specification of units (KB, MB, GB, and TB).

Changed options on page 49

Changes introduced since Data ONTAP 8.2 | 13

• raid.disk.timeout.enable

This option is removed.

New cautions

The following caution is new in this release:

Upgrade cautions on page 55

• Change in how Data ONTAP handles file names containing UTF-16 supplementary characters (7-Mode) on page 55

Removed cautions

The following cautions that were included in the Data ONTAP 8.2 Release Notes have been removedin this release:

Upgrade cautions

• RAID disk timeout option not updated correctly after upgrade• SAS optical cables not supported

Networking cautions

• System might panic if the network configuration entries in the /etc/rc file are not in therecommended order

Setup cautions

• CIFS setup overwrites the storage system password

New known problems and limitations

There are new known issues in this release:

Storage resource management issues on page 65

• Long disk list for aggregate creation could cause disruption on page 65

FlexArray Virtualization (V-Series) issues on page 67

• Too many storage devices presented to the Data ONTAP system on page 67

Network protocol issues on page 68

• Error message observed during port up and down times of interface groups on page 68• SNMPv3 access failure for an existing user on page 68• Existing traphosts fail to receive SNMP traps on page 69• The first VLAN configured over a port might bring the port down temporarily on page 69

File access and protocols issues on page 71

• Option nfs.export.allow_provisional_access is nonfunctional on page 71

14 | Release Notes

• Access denied error when setting ACL at the root directory of an empty share on page 71• Deleting the base file of an open stream file is permissible in Data ONTAP on page 74

Data protection issues on page 76

• DAR fails if the file and LUN have the same name on the destination volume on page 76

SAN configuration issues on page 77

• UTA2 in NetApp collateral is referred to as CNA in product documentation on page 77

MultiStore issues on page 78

• vFiler unit migration using no-copy transfer not supported in a MetroCluster configuration onpage 78

Removed problems and limitations

The following known problems and limitations have been removed in this release:

Issues with V-Series systems working with LUNs from storage arrays

• Some HP 3PAR array LUNs might be reported as unknown devices if zoning is configuredbefore setting the host persona

• LUNs from a host group with fewer than 16 array LUNs are not visible on some Hitachi and HPstorage arrays

Storage resource management issues

• Configuring ACP to use a different port on a FAS2240 system disables ACP for the local SASexpander

• Incorrect error message when FlexClone volume creation fails on a storage system that is halting

File access and protocols issues

• Effective style of qtrees created on an NTFS volume before configuring CIFS• Windows Security tab unavailable for shares with long UNC paths

SAN Administration issues

• The fcp topology show command with the verbose or zoned option fails on very largefabrics

Documentation changes

The following new or changed information supplements the documentation available for this release:

Changes to the SAN Configuration Guide for 7-Mode on page 80

• Incorrect PVR requirements listed for shared SAN configurations on page 80• FAS80xx multifabric HA configuration has incorrect illustration on page 81

Changes to the Archive and Compliance Management Guide on page 82

Changes introduced since Data ONTAP 8.2 | 15

• Corrections to SnapLock support for Storage Encryption on page 82

Changes to the V-Series Installation Requirements and Reference Guide on page 84

• Incorrect reference to a V-Series guide on page 84

For more information about other important documentation updates, see Changes to publisheddocumentation on page 79.

16 | Release Notes

Unsupported features

This Data ONTAP release does not support some Data ONTAP features.

SnapMirror over Fibre Channel

Starting with Data ONTAP 8.2.1, SnapMirror over Fibre Channel (SMoFC) is not supported onFAS80xx and later systems.

For more information, see the KB article Limited FAS Platforms supported with SnapMirror overFibre Channel (SMoFC) 7-Mode with Data ONTAP 8.2.x.

For a list of SMoFC hardware platforms that are supported along with the Data ONTAP versions, seethe Interoperability Matrix at support.netapp.com/matrix.

NDMP v3

Starting with Data ONTAP 8.2, NDMP v3 is not supported.

Related information

NetApp Support Site: support.netapp.com

17

Functionality changes in future releases

Support for some features will be discontinued in a future release of Data ONTAP.

• Volume guarantees of type fileIn a future release of Data ONTAP, volume guarantees of type file will not be supported. Anyexisting volumes with guarantees of type file will be updated to another guarantee type whenyou upgrade to that release.

Related information

NetApp Support Site: support.netapp.com

18 | Release Notes

New and changed features in the Data ONTAP 8.2release family for 7-Mode

A number of new features and enhancements have been introduced in the Data ONTAP 8.2 releasefamily.

Some enhancements in this release might also be introduced in a maintenance release of an earlierData ONTAP release family. Before upgrading, be sure to consult with your NetApp representativeabout new Data ONTAP functionality to determine the best solution for your business needs.

Additional changes are described here. For other important information about changes to the productmade by these releases, see the release notes topic Summary of new and changed commands andoptions in the Data ONTAP 8.2 release family operating in 7-Mode on page 38. For managing andresolving bug issues, you can use the Bugs Online suite of tools; for more information, see BugsOnline on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

New and changed platform and hardware supportThis Data ONTAP release family supports new and changed hardware.

For information about the supported systems in Data ONTAP 8.2 for 7-Mode, see Supported systemson page 51. For information about the unsupported systems in Data ONTAP 8.2, see Unsupportedsystems on page 52.

Support for the FAS80xx platform

Data ONTAP 8.2.1 and later releases support the FAS80xx platform.

The FAS80xx Product Datasheet provides a comparative overview of the FAS8020, FAS8040, andFAS8060 platforms.

Support for 400-GB SSDs

400-GB SSDs are now supported in SAS-connected storage shelves. For information about whichstorage shelves and Data ONTAP versions support these SSDs, see the Hardware Universe at hwu.netapp.com.

Support for 1.6-TB SSDs

1.6-TB SSDs are now supported in SAS-connected storage shelves. For information about whichstorage shelves and Data ONTAP versions support these SSDs, see the Hardware Universe at hwu.netapp.com.

19

Support for SAS optical cables

Data ONTAP 8.2.1 and later 8.2.x releases support SAS optical cables on 32xx and 62xx storagesystems with SAS disk shelves using IOM6. Data ONTAP 8.2.1 is the first release in the DataONTAP 8.2 release family on which SAS optical cables are supported.

The SAS Storage Cabling and Infrastructure FAQ at www.netapp.com/us/media/sas-storage-cabling-and-infrastructure.pdf contains more information about SAS optical cables.

Installation information can be found in the DS4243, DS2246, DS4486, and DS4246 Disk ShelfInstallation and Service Guide and the Configuring a stretch MetroCluster system with SAS diskshelves and SAS optical cables document at the NetApp Support Site at support.netapp.com.

Support for shelf hot-remove

Data ONTAP 8.2.1 and later 8.2.x releases support the hot removal of disk shelves—the physicalremoval of disk shelves that have had the data evacuated—in multipath HA or single-controller-dual-path (multipath) storage systems that are up and serving data. You can hot remove one or more SASor FC disk shelves from anywhere within a stack or loop of disk shelves, or an entire stack or loop ofdisk shelves.

The following supported configurations and documents containing the shelf hot-remove procedurecan be found on the NetApp Support Site at support.netapp.com:

• Multipath HA and single-controller-dual-path storage systems with SAS disk shelves: DS4243,DS2246, DS4486, and DS4246 Disk Shelf Installation and Service Guide

• Stretch MetroCluster systems with SAS disk shelves and SAS optical cables: Configuring astretch MetroCluster system with SAS disk shelves and SAS optical cables

• MetroCluster systems with SAS disk shelves and FibreBridge 6500N bridges: Configuring aMetroCluster system with SAS disk shelves and FibreBridge 6500N bridges

• MetroCluster systems with FC disk shelves: Data ONTAP High Availability and MetroClusterConfiguration Guide for 7-Mode

• Single-controller-dual-path (multipath) systems with FC disk shelves: Hot-removing DS14 diskshelves in single-controller-dual-path (multipath) systems running Data ONTAP 8.2.1 or later

Support for 800-GB SSDs

In Data ONTAP 8.2 and later releases, 800-GB SSDs are supported for SSD-only aggregates andFlash Pool aggregates.

For information about which platforms and shelf types support these drives and aggregate types, seethe Hardware Universe at hwu.netapp.com.

Support for 1.2-TB performance disks

In Data ONTAP 8.2 and later releases, 1.2-TB disks are supported for SAS-connected disk shelves.These are performance disks (rather than capacity disks) and their speed is 10K RPM.

20 | Release Notes

3210 and 3140 systems with Flash Cache modules not supported

3210 and 3140 storage systems with Flash Cache modules are not supported in Data ONTAP 8.2 andlater 8.2.x releases operating in 7-Mode. You cannot upgrade to Data ONTAP 8.2 or later 8.2.xreleases if you have Flash Cache modules enabled in your 3210 or 3140 system.

KB article 2017616 contains information about this issue and can be found at kb.netapp.com/support/index?page=content&id=2017616.

Support for Flash Cache 2 modules

Data ONTAP 8.2 and later releases support the 2-TB, 1-TB, and 512-GB, PCIe-attached Flash Cache2 modules that use Flash technology.

For the Flash Cache 2 technical specifications, including supported platforms, go to www.netapp.com/us/products/storage-systems/flash-cache/flash-cache-tech-specs.html.

Manageability enhancementsThis release of Data ONTAP provides new and changed manageability capabilities.

Support for histogram-based predictions in RAVE

Starting in Data ONTAP 8.2.1, the speculative read-ahead engine (RAVE) in WAFL can captureadditional temporal data about previous user read requests to a file and use this information tointelligently speculate on future read requests. In prior releases, you could speculate based oninformation only from the current user I/O.

You can enable or disable the use of histograms for storage systems operating in 7-Mode by usingthe wafl rave use_histogram <value> command, whereby a value of 1 enables the featureand 0 disables it.

For more information about performance data and the statistics commands, see the Clustered DataONTAP System Administration Guide for Cluster Administrators Data ONTAP SystemAdministration Guide for 7-Mode.

The system node service-processor commands now support the RLM

Starting with Data ONTAP 8.2.1, you can use the system node service-processor commandsto manage the Remote LAN Module (RLM) from Data ONTAP. The rlm commands in the DataONTAP CLI are deprecated in favor of the system node service-processor commands.

You can use the system node service-processor commands to perform the following RLMmanagement tasks:

• Set up or modify the RLM network configuration (system node service-processornetwork modify)

New and changed features in the Data ONTAP 8.2 release family for 7-Mode | 21

• Display the RLM network configuration (system node service-processor networkshow)

• Display the RLM information (system node service-processor show)• Reboot the RLM and optionally specify the RLM firmware image (primary or backup) to use

(system node service-processor reboot-sp)• Display the details of the currently installed RLM firmware image (system node service-

processor image show)• Update the RLM firmware (system node service-processor image update)• Display the status for the latest RLM firmware update (system node service-processor

image update-progress show)

Licensing changes for the Data ONTAP 8.2 release family

Data ONTAP 8.2 introduces licensing changes that affect how you manage the licenses of yourstorage system.

The following licensing changes apply to the Data ONTAP 8.2 release family:

• How licensed features are mapped to packages has changed.Data ONTAP feature licenses are issued as packages, each of which contains multiple features ora single feature. A package requires a license key, and installing the key enables you to access allfeatures in the package. For example, installing the key for the SnapManager Suite package on asystem entitles the system to use all SnapManager products in the package. For information aboutthe features that require licenses in the Data ONTAP 8.2 release family, see the knowledgebasearticle Data ONTAP 8.2 Licensing Overview and References on the NetApp Support Site.

• Data ONTAP no longer displays license states for individual features that are part of a licensepackage; instead, Data ONTAP manages and displays entitlements at the license package level.

• A standard Data ONTAP license, also known as a node-locked license, is issued for a system witha specific serial number and is not valid on other systems.Installing a standard, node-locked license entitles the system to the licensed functionality.The Data ONTAP 8.2 release family treats a license installed prior to Data ONTAP 8.2 as astandard license. Therefore, a system running Data ONTAP 8.2 or later automatically has thestandard license for the package that the previously licensed functionality is part of.

• The length of a license key has been increased to 28 characters.Licenses installed in a release earlier than Data ONTAP 8.2 continue to work after you upgrade toData ONTAP 8.2 or later. However, if you need to reinstall a license in Data ONTAP 8.2 or later(for example, you deleted a previously installed license and want to reinstall it in Data ONTAP8.2 or later, or you perform a controller replacement procedure for a system running DataONTAP 8.2 or later), Data ONTAP requires that you enter the license key in the new, 28-character format.You can find license keys for your initial or add-on software orders at the NetApp Support Siteunder My Support > Software Licenses. For instance, you can search with the serial number ofa system to find all license keys associated with the system. If you cannot locate your license keysfrom the Software Licenses page, you should contact your sales or support representative.

22 | Release Notes

Note: If you wipe clean a system and reinstall it with a version that is earlier than DataONTAP 8.2, you need to use a license key format that is supported for the release that you areinstalling. For information about how to obtain the license keys, see the knowledgebase article Data ONTAP 8.2 Licensing Overview and References on the NetApp Support Site.

• Starting with Data ONTAP 8.2, the following functionality no longer requires a license, but youmight need to enable certain options before using it:

◦ High-availability (HA) configurationsYou must set options cf.mode to ha.

◦ MetroClusterYou must enable options cf.remote_syncmirror.enable and set options cf.modeto ha.

◦ SyncMirrorThere is no option that you need to enable.

• If you replace or upgrade a controller that is running Data ONTAP 8.2 or later, within a graceperiod (up to 90 days) the new controller can use the same licensed functionality that the originalcontroller had.During the grace period, you should contact your sales representative to obtain a proper licensekey to install on the new controller.During the grace period when the first valid license key is installed, you have 24 hours tocomplete license installation for all packages that you want the new controller to use. The graceperiod ends after the 24-hour period, and all previously installed licenses that were associatedwith the original system serial number will be removed from the new controller.

• Data ONTAP commands for managing licenses have been enhanced.

◦ The license add command now enables you to add multiple license keys at a time.◦ The license show command output has a different format and displays additional details.

For information about managing feature licenses, see the Data ONTAP System Administration Guidefor 7-Mode.

New command family for managing the SP from Data ONTAP

Starting with Data ONTAP 8.2, the system node service-processor commands are availablefor managing the Service Processor (SP) from Data ONTAP. The sp and software installcommands are deprecated in favor of the new commands.

The system node service-processor commands replace the sp commands for the followingtasks:

• Set up or modify the SP network configuration (system node service-processornetwork modify)

• Display the SP network configuration (system node service-processor network show)• Display the SP information (system node service-processor show)• Reboot the SP and optionally specify the SP firmware image (primary or backup) to use (system

node service-processor reboot-sp)

New and changed features in the Data ONTAP 8.2 release family for 7-Mode | 23

• Display the details of the currently installed SP firmware image (system node service-processor image show)

• Enable or disable the SP automatic firmware update (system node service-processorimage modify)

• Manually update the SP firmware and specify the update settings (system node service-processor image update)

• Display the status for the latest SP firmware update (system node service-processorimage update-progress show)

In addition, the software install command is no longer supported for the SP firmware update. Itis replaced by the system node service-processor image update command.

Enhancements for delivery of AutoSupport messages

This release of Data ONTAP provides the new AutoSupport On Demand feature, delivery of theFQDN to SMTP mail servers, and user space core reports in daily AutoSupport messages.

AutoSupport On Demand enhances delivery of AutoSupport messages

Starting in Data ONTAP 8.2, AutoSupport On Demand is a new AutoSupport feature that ensuresthat technical support has the data it needs to provide quick incident resolution and preventativesupport.

AutoSupport On Demand periodically sends HTTPS requests to technical support to obtain deliveryinstructions. The delivery instructions can include requests to generate new AutoSupport messages,retransmit previously generated messages, and disable delivery of messages for specific triggerevents. The requests go to the same technical support location that AutoSupport messages are sent.

AutoSupport On Demand is enabled by default. It automatically communicates with technicalsupport if AutoSupport is configured to send messages to technical support and the transport protocolis HTTPS.

For more information about AutoSupport On Demand, see the Data ONTAP System AdministrationGuide for 7-Mode.

The fully qualified domain name is now sent to SMTP mail servers

Starting in Data ONTAP 8.2, when sending connection requests to SMTP mail servers, AutoSupportnow specifies the fully qualified domain name of the node, if you configured DNS. In previousreleases, AutoSupport specified only the host name.The advantage of using the FQDN over the hostname addresses is better compliance with mail protocol standards, such as RFC 2821 and 2822. Sinceit is best practice to configure mail servers to verify that the name provided by the client is aresolvable FQDN, and to reject the email otherwise, this enhancement allows successful delivery ofAutoSupport messages using SMTP.

24 | Release Notes

User space core reports are now sent in daily AutoSupport messages

Starting with Data ONTAP 8.2.1, when a user space application crashes and restarts, it produces acore dump and a core report. The core report was previously collected as part of the weeklyAutoSupport message. It is now collected as part of the daily AutoSupport message for managementlogs. The core dump itself can be uploaded separately if desired.

Enhancements to health monitoring

The node connectivity health monitor in Data ONTAP 8.2 monitors SMB connections to ensurenondisruptive operations to Hyper-V applications.

For more information about health monitoring, see the Data ONTAP System Administration Guidefor 7-Mode.

Messages in the /etc/messages file now include the system name

Staring with Data ONTAP 8.2, messages in the /etc/messages file include the storage systemname. This change helps administrators of multiple systems see which system a given message camefrom.

Options for specifying uppercase and lowercase requirements in userpasswords

Starting with Data ONTAP 8.2, you can specify the minimum number of uppercase or lowercasealphabetic characters that a password must contain.

You can use the following options to specify the requirements of uppercase or lowercase alphabeticcharacters in user passwords:

• The security.passwd.rules.minimum.uppercase option specifies the minimum numberof uppercase alphabetic characters that a password must contain.The default is 0, which does not require that a password contain uppercase characters.

• The security.passwd.rules.minimum.lowercase option specifies the minimum numberof lowercase alphabetic characters that a password must contain.The default is 0, which does not require that a password contain lowercase characters.

High-availability pair enhancementsThis Data ONTAP release includes new features and enhancements relating to HA pairs.

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

Support for 16 Gb FC-VI adapters in a MetroCluster configuration

Starting with Data ONTAP 8.2.1, the 16 Gb FC-VI adapter is supported with MetroClusterconfigurations.

For more information about 16 Gb FC-VI adapters, see the Data ONTAP High Availability andMetroCluster Configuration Guide for 7-Mode.

Support for SSDs in a MetroCluster configuration

Aggregates composed only of solid-state disks (SSDs) are supported in MetroCluster configurations.

For more information about SSDs, see the Data ONTAP Storage Management Guide for 7-Mode.

New cf.mode option replaces the cf license

In Data ONTAP 8.2, the new cf.mode option replaces the requirement for the cf license.

Support for unidirectional port mirroring in a MetroCluster configuration

Starting with Data ONTAP 8.2.1, you can use unidirectional port mirroring in a MetroClusterconfiguration, which enables you to increase performance throughput by effectively utilizing the FC-VI links in that MetroCluster configuration.

To learn more about using unidirectional port mirroring, see the Data ONTAP High Availability andMetroCluster Configuration Guide for 7-Mode.

Support for ISL encryption in a MetroCluster configuration

Starting with Data ONTAP 8.2.1, the MetroCluster configuration supports ISL encryption onBrocade 6510 switches.

For more information about ISL encryption, see the Data ONTAP High Availability andMetroCluster Configuration Guide for 7-Mode and Fabric-attached MetroCluster Systems BrocadeSwitch Configuration Guide.

Storage resource management enhancementsThis Data ONTAP release includes a number of enhancements for performance, resiliency, andmanagement capabilities for storage resources.

Increased maximum aggregate sizes for some FAS80xx systems

The maximum aggregate sizes for the FAS8020, FAS8040, and FAS8060 systems have increasedsince Data ONTAP 8.2.1 RC2. For maximum aggregate sizes for all platforms, see the HardwareUniverse at hwu.netapp.com.

26 | Release Notes

Aggregates can be expanded to 64-bit format without adding storage

Starting with Data ONTAP 8.2.1, you can expand a 32-bit aggregate to the 64-bit format withoutadding storage to the aggregate. Converting to the 64-bit format enables you to use Data ONTAPfeatures that require 64-bit aggregates, such as compression and Flash Pool aggregates.

Increased maximum Flash Pool cache sizes for FAS22xx systems

The maximum size for Flash Pool caches has increased in Data ONTAP 8.2.1. To determine themaximum Flash Pool cache size for your system model, see the Hardware Universe.

Automated Workload Analyzer for Flash Pool cache sizing

Starting with Data ONTAP 8.2.1, the Automated Workload Analyzer (AWA) functionality isavailable. AWA is enabled on an aggregate and provides real-time workload analysis to estimate therecommended Flash Pool cache size and to predict cache hit rates.

AWA can be used on both Flash Pool aggregates and HDD-only aggregates. It can be used on acontroller with a Flash Cache module installed.

You access the AWA functionality by using the wafl awa command, available at the advancedprivilege level.

Increased maximum aggregate size for some platforms

The maximum aggregate size has increased for some platforms in Data ONTAP 8.2. For moreinformation, see the Hardware Universe at hwu.netapp.com.

Multi-disk carrier and single-disk carrier disk shelves can be combined inthe same stack

Starting with Data ONTAP 8.2.1, you can combine multi-disk carrier disk shelves with single-diskcarrier disk shelves (standard disk shelves) in the same stack.

Flash Pool aggregates support different RAID types and group sizes forSSD cache

For earlier versions of Data ONTAP, the SSD cache always had the same RAID type and RAIDgroup size as the HDD RAID groups. Starting in Data ONTAP 8.2, the SSD cache RAID type andRAID group size can be configured differently from the HDD RAID groups.

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

Flexibility for calculating maximum Flash Pool SSD cache size in HAconfigurations

There is a platform-dependent maximum size for the Flash Pool SSD cache. Starting in Data ONTAP8.2, the cache-size limits apply to the HA configuration as a whole, and can be split arbitrarilybetween the two nodes, provided that the total limit for the HA configuration is not exceeded.

In previous versions of Data ONTAP, the maximum Flash Pool SSD cache size was appliedindividually to both nodes in an HA configuration.

For more information about how Flash Pool cache capacity is calculated, see the Data ONTAPStorage Management Guide for 7-Mode.

Aggregate Snapshot copy automatic deletion is always enabled

In previous versions of Data ONTAP, you could disable aggregate Snapshot copy automatic deletion.Starting in Data ONTAP 8.2, aggregate Snapshot copy automatic deletion is always enabled andcannot be disabled.

You can control how many aggregate Snapshot copies are preserved by adjusting the size of theaggregate Snapshot reserve. By default, the aggregate Snapshot reserve is set to 0 percent for newlycreated aggregates. If you are using SyncMirror, you should keep your aggregate Snapshot reservefor that aggregate set to 5 percent or higher.

Disabled volume guarantees no longer reenabled automatically

Starting with Data ONTAP 8.2, after more space becomes available Data ONTAP no longerautomatically reenables the guarantee for volumes with disabled guarantees. This gives theadministrator control over when a volume with a disabled guarantee consumes space to enable itsguarantee.

Fractional reserve setting can be set only to 0 or 100

In previous versions of Data ONTAP, you could set the fractional reserve setting for a FlexVolvolume to any value, from 0 to 100. Starting with Data ONTAP 8.2, the fractional reserve setting canbe set only to 0 or 100.

If you upgrade a system to Data ONTAP 8.2 with volumes whose fractional reserve settings arebetween 1 and 99, the fractional reserve setting for those volumes is set to 0.

28 | Release Notes

Storage efficiency enhancementsThis Data ONTAP release includes a new enhancement for storage efficiency. This section providesan overview of the enhancement.

Support for detecting incompressible data in files

Data ONTAP 8.2 introduces the ability to check if a file is incompressible and for large files, you cancheck if a compression group within a file is incompressible. Incompressible data detection saves thesystem resources used by inline compression to compress incompressible data.

For more information about incompressible data detection, see the Data ONTAP StorageManagement Guide for 7-Mode.

FlexArray Virtualization (V-Series) enhancementsThis Data ONTAP release includes a number of new features and enhancements for FlexArrayVirtualization (V-Series).

Support for storage arrays on FAS systems

The new FAS systems released with Data ONTAP 8.2.1 and later can attach to storage arrays if therequired license is installed. The first of these platforms are the FAS8020, FAS8040, and FAS8060systems.

No new V-Series systems are released starting with Data ONTAP 8.2.1. However, the existing V-Series systems are supported in Data ONTAP 8.2.1.

Systems prior to Data ONTAP 8.2.1 that can use storage arrays

Most Data ONTAP platforms released prior to Data ONTAP 8.2.1 include FAS and V-Seriesequivalent models (for example, a FAS6280 and a V6280). Although both types of models canaccess native disks, only the V-Series systems (a system with a “V” or “GF” prefix) can attach tostorage arrays.

Important: The FAS systems released prior to Data ONTAP 8.2.1 cannot use LUNs on storagearrays even if they are upgraded to Data ONTAP 8.2.1; only the “V” equivalent of the FASplatforms can use array LUNs.

V-Series functionality renamed as FlexArray Virtualization

Starting with Data ONTAP 8.2.1, the capability of using LUNs on a storage array, formerlyidentified as the V-Series functionality, has a new name—Data ONTAP FlexArray Virtualization

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

Software. The capability of using array LUNs continues to be available as a licensed feature on DataONTAP.

In addition to the existing V-Series systems, all the new FAS platforms released in Data ONTAP8.2.1 and later can attach to storage arrays, with the appropriate license installed.

In the Data ONTAP and FlexArray Virtualization documentation, the V-Series systems and the newFAS systems are collectively referred to as Data ONTAP systems when it is necessary to clarify whatinformation applies to them and what information applies to storage arrays.

Licensing requirement for Data ONTAP systems to use array LUNs

Starting with Data ONTAP 8.2, the V_StorageAttach license package must be installed for V-Seriessystems to access LUNs on storage arrays. The new FAS systems releasing in Data ONTAP 8.2.1and later also require the V_StorageAttach license to be installed for them to use array LUNs.

For V-Series systems upgraded from previous Data ONTAP 8.x releases to 8.2, the license isautomatically updated to the V_StorageAttach license package.

Licensing enhancement in V-Series systems

Starting in Data ONTAP 8.2.1, V-Series systems do not reboot if the V_StorageAttach licensepackage is not installed within 72 hours. However, the license must be installed to be able to accessLUNs on storage arrays.

New storage arrays supported in Data ONTAP 8.2

Support for new storage arrays is added in Data ONTAP 8.2.

For information about the supported storage arrays, see the Interoperability Matrix at support.netapp.com.

Also see the FlexArray Virtualization Implementation Guide for Third-Party Storage for informationabout parameter settings for these storage arrays to work with Data ONTAP systems that uses arrayLUNs, supported configurations for the storage arrays, and so on.

Support added for one Data ONTAP FC initiator connecting to multiplearray target ports

Starting with Data ONTAP 8.2, you can connect a Data ONTAP FC initiator port to a maximum offour target ports on separate storage arrays. Connecting an FC initiator port to four target ports on thesame storage array is also supported; however, this configuration can be used only with storagearrays whose LUN masking, presentation, or host group capability allows for different LUN grouppresentations to the same FC initiator based on the target port being accessed.

See the FlexArray Virtualization Installation Requirements and Reference Guide for the rules forimplementing this type of configuration. See your storage array documentation for information about

30 | Release Notes

whether your storage array supports a Data ONTAP FC initiator connecting to multiple target portson the same storage array.

Note: Sharing of FC initiator ports is not supported in MetroCluster configurations that supportarray LUNs.

Increased LUN count per Data ONTAP FC initiator

The number of array LUNs that can be visible over an FC initiator has been increased in DataONTAP 8.2.

There are limits on how many array LUNs can be visible over an FC initiator port. These limits varyin different Data ONTAP releases. See the FlexArray Virtualization Best Practices Guide forinformation about the considerations for and number of array LUNs supported per initiator.

Support added for native disks in a MetroCluster configuration thatsupports array LUNs

Starting with Data ONTAP 8.2, a MetroCluster configuration that supports array LUNs can also usenative disks.

The following table identifies the Data ONTAP releases that support systems to use array LUNs ornative disks in a MetroCluster configuration:

Data ONTAP release Systems that can use array LUNs in a MetroClusterconfiguration

Prior to 8.2 V-Series systems only, and those systems can use only array LUNs

8.2 V-Series systems only, and those systems can use array LUNs, disks,or both

Note: Setting up the MetroCluster configuration requiresFibreBridge 6500N bridges and the native disks supported by thisbridge. These requirements are the same for fabric-attached andstretch MetroCluster configurations.

8.2.1 and later • V-Series systems, which can use array LUNs, disks, or both• FAS systems that can be licensed to use array LUNs

These systems can use disks also if desired, by using FibreBridge6500N bridges.

Starting with Data ONTAP 8.2, the MetroCluster configurations must meet the followingprerequisites:

• Setting up a MetroCluster configuration with Data ONTAP systems requires FibreBridge 6500Nbridges and the native disks supported by this bridge. These requirements are the same for fabric-attached and stretch MetroCluster configurations.

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

• The Data ONTAP systems must be running Data ONTAP operating in 7-Mode (clustered DataONTAP is not supported for MetroCluster configurations).

• The storage arrays and Data ONTAP systems must be identified in the Interoperability Matrix asbeing supported in MetroCluster configurations.

For more information, see the Data ONTAP High Availability and MetroCluster ConfigurationGuide for 7-Mode.

Support added for SAS optical cables in MetroCluster configurations thatuse array LUNs

Starting with Data ONTAP 8.2.1, SAS optical cables are supported in MetroCluster configurationsthat use array LUNs.

For more information on SAS optical cable support, see Support for SAS optical cables on page 20.

Enhancements for setting the target queue depth on a Data ONTAP systemthat uses array LUNs

The default target queue depth is increased in Data ONTAP 8.2 operating in 7-Mode.

For more information, see the FlexArray Virtualization Installation Requirements and ReferenceGuide.

Array LUN limits information is now in the Hardware Universe

Information about array LUN limits is now in the Hardware Universe.

The limits information about array LUNs has been in the V-Series Limits Reference for Third-PartyStorage and before that in the V-Series Support Matrix. As of April 2013, the array LUN limitsinformation is in the Hardware Universe at hwu.netapp.com, along with other limits information forsystems running Data ONTAP. The array LUN specific limits information in the Hardware Universeincludes maximum array LUN sizes for data LUNs, minimum array LUN sizes for spare core LUNsand the LUN used for the root volume, and more.

The Hardware Universe is the authoritative source for array LUN limits information for all DataONTAP releases starting from 7.2. As such, the V-Series Limits Reference for Third-Party Storage isno longer being provided on the NetApp Support Site.

File access protocol enhancementsThis Data ONTAP release includes a number of new features and enhancements for file access andprotocols management.

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

32 | Release Notes

Support for VMware vStorage over IPv6

Beginning with Data ONTAP 8.2.1, VMware vStorage is also supported over IPv6 networks.

For more information about VMware vStorage APIs for Array Integration (VAAI) features in a DataONTAP NFS environment, see the Data ONTAP File Access and Protocols Management Guide for7-Mode.

Maximum ACE limit for NFSv4 ACLs has increased

The maximum number of ACEs for each ACL has been increased to 1,024. This enables you to addsignificantly more ACEs to ACLs than in previous versions of Data ONTAP.

Support for SMB 2.x authentication with CIFS workgroup mode

Data ONTAP 8.2 and later releases provide support for using SMB 2.x authentication with CIFSworkgroup mode. Previously, CIFS workgroup authentication was performed by using SMB 1.0.

For information about CIFS workgroup mode and CIFS authentication, see the Data ONTAP FileAccess and Protocols Management Guide for 7-Mode.

Enhancements for management of unresponsive LDAP servers

Data ONTAP 8.2 and later releases enable administrators to better manage issues related tounresponsive LDAP servers. Two new options are available.

All servers in the list of LDAP servers are contacted serially, and the first one to make a successfulconnect and bind is used by the storage system. By default, if the LDAP server becomesunresponsive, LDAP requests fails after the bind timeout. The default is a timeout of 30 seconds withthree retries. If the ldap.fast_time_out.enable option is on and an LDAP request times out, allrequests that have been in the queue longer than the bind timeout are failed. This allows DataONTAP to quickly identify a complete LDAP failure and send error responses to its CIFS or NFSclients.

Two new options are available to manage the timeout settings. Both options take effect immediatelyand are persistent across reboots.

• ldap.fast_timeout.enable

This option controls the timeout behavior of LDAP client operations. If enabled, after a failureoccurs, the storage system does not retry connections to the failed LDAP server. The storagesystem waits for the number of seconds configured by the ldap.retry_delay option beforemaking another attempt to connect to LDAP servers. The default is on.

• ldap.retry_delay

The time, in seconds, to wait before trying to connect to LDAP servers after a failed attempt.Effective only if ldap.fast_timeout.enable is on. The range for this option is 0 through3600. The default value for this option is 120.

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

For information about managing LDAP servers, see the Data ONTAP File Access and ProtocolsManagement Guide for 7-Mode.

Enabling new EMS messages to help troubleshoot Kerberos issues

New EMS messages have been added to Data ONTAP to help troubleshoot Kerberos authenticationand connectivity issues.

Enable the new EMS messages for Kerberos by entering the following command:

options nfs.rpcsec.trace on

After you finish troubleshooting, disable the EMS message for Kerberos by entering the followingcommand:

options nfs.rpcsec.trace off

CIFS TCP window size increased to 64,240 bytes

In Data ONTAP 8.2.1, the default CIFS TCP window size has increased from 17,520 bytes to 64,240bytes. For a new Data ONTAP 8.2.1 installation, the TCP window size is 64,240 bytes. Thisenhancement improves performance on high-bandwidth networks.

If you upgrade the physical storage system (vFiler0) to Data ONTAP 8.2.1 or later, the default TCPwindow size is set to 64240 on all of the vFiler units, unless the value has been modified explicitly.

If you revert the storage system to Data ONTAP 8.2 or earlier, the default TCP window size is set tothe previous default value unless the value has been modified explicitly.

The administrator can modify the default values to customized values. For example, if theadministrator modifies the TCP window size to 28672 bytes by using the cifs.tcp_window_sizeoption, that value is retained across Data ONTAP upgrades and reversions.

Data protection enhancementsThis release of Data ONTAP provides new data protection features and enhancements.

For more information about the new features and enhancements, see the Data ONTAP DataProtection Tape Backup and Recovery Guide for 7-Mode and the Data ONTAP Data ProtectionOnline Backup and Recovery Guide for 7-Mode.

Support for multipath tape access

You can configure multiple paths from the storage system to access tape drives in a tape library. Ifone path fails, then the storage system can use the other paths to access tape drives without having toimmediately repair the failed path. This ensures that tape operations can be restarted.

For more information about multipath tape access, see the Data ONTAP Data Protection TapeBackup and Recovery Guide for 7-Mode

34 | Release Notes

Support for Single SnapVault license

Starting with Data ONTAP 8.2, you need not use separate license to enable SnapVault primary andSnapVault secondary. You must use the same SnapVault license to enable both the SnapVaultprimary and SnapVault secondary.

SyncMirror is enabled by default

Starting with Data ONTAP 8.2, you do not have to enable the SyncMirror license as it is enabled bydefault with SnapMirror license.

Options for enabling the SnapLock functionality

Starting with Data ONTAP 8.2, in addition to installing the license key for the SnapLockfunctionality, you need to enable the functionality by using the optionslicensed_feature.snaplock_enterprise for SnapLock Enterprise or optionslicensed_feature.snaplock for SnapLock Compliance.

For more information about enabling the SnapLock functionality, see the Data ONTAP Archive andCompliance Management Guide for 7-Mode.

Automatic resizing of SnapMirror destination for a FlexVol volume

Starting with Data ONTAP 8.2, if you increase the size of a SnapMirror source FlexVol volume andperform a SnapMirror transfer, the size of the SnapMirror destination FlexVol volume automaticallyincreases to that of the SnapMirror source FlexVol volume.

For information about resizing the SnapMirror source and destination volume pair for a FlexVolvolume, see the Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.

Users cannot perform certain Qtree SnapMirror and SnapVault tasks duringthe post-upgrade operations

When you upgrade to Data ONTAP 8.2, Qtree SnapMirror and SnapVault perform certain post-upgrade tasks, as part of which, all restart checkpoints are cleared and uninitialized relationships andqtrees are deleted. During this time, users will not be able to perform any tasks on uninitializedrelationships and qtrees, or on volumes containing these qtrees.

When the post-upgrade operations are complete, the message Post-upgrade operations forQtree SnapMirror and SnapVault are complete is displayed.

Note: Users must not take any volumes offline before or after the upgrade until the post-upgradeoperations are complete.

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

Serial numbers used for tape aliasing

A serial number (SN) is a unique identifier for a tape drive or a medium changer. Starting with DataONTAP 8.2, Data ONTAP generates aliases based on SN instead of the WWN. The alias remains thesame regardless of the multiple connections paths to the tape drive or medium changer. This helpsstorage systems to track the same tape drive or medium changer in a tape library configuration.

For more information about serial numbers, see the Data ONTAP Data Protection Tape Backup andRecovery Guide for 7-Mode

Data ONTAP Edge enhancementsStorage systems based on Data ONTAP-v technology, such as the Data ONTAP Edge product, canbe installed with Data ONTAP 8.2.1 software.

Data ONTAP Edge storage systems running Data ONTAP 8.2.1 software must be installed andmanaged using Data ONTAP-v Administration Tool (dvadmin) version 1.2.1 software. dvadmin isincluded on the Data ONTAP-v Installer virtual machine. You download the latest Data ONTAP-vInstaller from the NetApp Support Site at support.netapp.com.

When installing a new storage system using the Data ONTAP-v Installer (at version 8.2.1.121), bothData ONTAP and dvadmin are provided at the required versions. (The installer version number8.2.1.121 means Data ONTAP version 8.2.1 and dvadmin version 1.2.1.)

When upgrading existing Data ONTAP Edge systems to Data ONTAP 8.2.1, you must upgrade theData ONTAP image to version 8.2.1 first. Then you upgrade dvadmin to version 1.2.1 using the DataONTAP-v Installer.

See the following manuals for installation and upgrade details:

• Data ONTAP-v Administration Tool Installation Guide• Data ONTAP Edge Installation and Administration Guide• Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode

Note: The Data ONTAP Edge product names have been changed. The product previously knownas Data ONTAP Edge is now known as Data ONTAP Edge with the Value bundle. The productpreviously known as Data ONTAP Edge-T is now known as Data ONTAP Edge with the Premiumbundle. The differences are that the Value bundle contains the Data ONTAP features licenses forCIFS, NFS, iSCSI, FlexClone, SnapRestore, and SnapVault; whereas the Premium bundleadditionally contains the SnapMirror license.

36 | Release Notes

Data ONTAP changes that affect Data ONTAP Edge

The following changes will be seen in Data ONTAP Edge storage systems when running with DataONTAP 8.2.0, or greater, software:

• When using Data ONTAP Edge systems, the four port numbers for direct-attached SAS diskshave changed from using 0a.n through 0d.n to using 0b.n through 0e.n. This difference appears inthe output of Data ONTAP commands such as disk show, aggr status -r, and sysconfig.

• Jumbo frames are supported with Data ONTAP Edge systems. The selection of jumbo frames isnot available in the Data ONTAP Edge installation wizard, but you can make this change afterinstallation using Data ONTAP commands.

• Data ONTAP 8.2 provides only a single SnapVault license instead of providing a separate licensefor SnapVault primary systems and SnapVault secondary systems, like in earlier versions of DataONTAP software. This does not affect the SnapVault technology support for Data ONTAP Edgesystems:

◦ Data ONTAP Edge with the Value bundle can be configured as a SnapVault primary systemonly.

◦ Data ONTAP Edge with the Premium bundle can be configured as a SnapVault primary orSnapVault secondary system.

Data ONTAP Edge and dvadmin changes

The underlying Data ONTAP-v technology within Data ONTAP Edge systems has been updated. Inaddition, the Data ONTAP-v Administration Tool (dvadmin) has been updated to version 1.2.1.

The following new features and changes are available in this release:

• In previous releases, the Data ONTAP Edge virtual machine name was different from the storagesystem name and the host name. In this release, the virtual machine name you specify whencreating the Data ONTAP Edge virtual machine is also used as the storage system name and thehost name in order to make identification of the system easier. Note that when upgrading fromData ONTAP 8.2.0 to this new version, the names remain as you defined them during your 8.2.0installation.

• In previous releases, the Data ONTAP feature licenses for Data ONTAP Edge (now called DataONTAP Edge with the Value bundle) were installed automatically. This included the CIFS, NFS,iSCSI, FlexClone, SnapRestore, and SnapVault licenses. If you purchased the Data ONTAPEdge-T product (now called Data ONTAP Edge with the Premium bundle), you needed to installthe SnapMirror license manually. In this release, all the required licenses are installedautomatically for both the Value and Premium versions of the product.

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

Summary of new and changed commands andoptions in the Data ONTAP 8.2 release familyoperating in 7-Mode

You need to know information about the commands, options, and configuration files that have beenadded to the Data ONTAP 8.2 release family operating in 7-Mode.

These listings are not exhaustive. For detailed information about specific commands and options, seethe corresponding man pages.

New commands in Data ONTAP 8.2New commands have been added to this release.

For each command family and each command, the table provides the following information:

• The purpose of the command• The location of documentation about the command• The release in which the command was introduced

Command Purpose Documentation Release added

license show Displays information aboutinstalled licenses; replacesthe license command.

Data ONTAP SystemAdministration Guide for7-Mode

na_license(1) man page

8.2

nfs vstorage

stats

Displays various countersabout VMware vStorage overNFS activity on the storagesystem.

Data ONTAP File Accessand ProtocolsManagement Guide for 7-Mode

8.2

rlm update-status Displays the RLM updateprogress.

na_rlm(1) man page 8.2

system health

subsystem show

Displays the health status ofsubsystems.

system_health_subsystem(1) man page

8.2

38 | Release Notes

Command Purpose Documentation Release added

system node

service-processor

Manages the ServiceProcessor (SP) and theRemote LAN Module(RLM):

• Setting up or modifyingthe remote managementfirmware networkconfiguration

• Displaying the remotemanagement firmwarenetwork configuration

• Displaying the remotemanagement deviceinformation

• Rebooting the remotemanagement device andoptionally specifying theremote managementfirmware image (primaryor backup) to use

• Displaying the details ofthe remote managementfirmware image that iscurrently installed

• Enabling or disabling theremote managementautomatic firmwareupdate (supported for theSP only)

• Updating the remotemanagement firmwaremanually and specifyingthe update settings

• Displaying the status forthe latest remotemanagement firmwareupdate

man pages for systemnode service-

processor

8.2 for the SPsupport

8.2.1 for theRLM support

vol autosize

grow_shrink

Supports the volumeautoshrink capability.

Data ONTAP StorageManagement Guide for 7-Mode

na_vol(1) man page

8.2

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 39

Command Purpose Documentation Release added

ic

unidirectional_mi

rroring

Allows you to enable ordisable the unidirectional portmirroring.

Data ONTAP HighAvailability andMetroClusterConfiguration Guide for7-Mode

na_vol(1) man page

8.2.1

fcvi ping adapter

address

Allows you to ping a remoteFC-VI port in same fabric.

Data ONTAP HighAvailability andMetroClusterConfiguration Guide for7-Mode

na_vol(1) man page

8.2.1

fcvi logins

adapter

Lists all the ports to whichthe FC-VI adapter logs in.

It displays the followinginformation:

• Fibre Channel portidentifier

• Fibre Channel world wideport name

• login state of each port

na_vol(1) man page 8.2.1

Changed commands in Data ONTAP 8.2A number of commands have been changed in this release.

For each command family and each command, the table provides the following information:

• Change in the command• Location of documentation about the command• Release in which the change was introduced

Command Change Documentation Release commandchanged in

aggr 64bit-

upgrade start

This command is nowavailable at theadvanced privilegelevel.

Data ONTAP StorageManagement Guide for7-Mode

na_aggr(1) man page

8.2.1

40 | Release Notes

Command Change Documentation Release commandchanged in

aggr create The -p option wasadded to supportspecifying the poolfrom which theaggregate is to becreated.

na_aggr(1) man page 8.2

aggr options The -T option wasadded to supportchanging the RAIDtype of a Flash Pooltier.

Data ONTAP StorageManagement Guide for7-Mode

na_aggr(1) man page

8.2

aggr status The -S option wasadded. This optiondisplays detailedinformation about howspace is used in theaggregate.

Data ONTAP StorageManagement Guide for7-Mode

na_aggr(1) man page

8.2

autosupport

history show

The -generated-onoption has been added.This option displaysAutoSupport messagesthat were generated ata particular time.

na_autosupport(1) manpage

8.2

df Aggregate Snapshotspill, or the amount ofspace that aggregateSnapshot copies aretaking beyond theaggregate Snapshotreserve, is now shownas free space.Previously, it wasshown as used by theaggregate. With thischange, the outputs ofthe df and aggrstatus -S commandsare consistent.

na_df(1) man page 8.2

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 41

Command Change Documentation Release commandchanged in

license Deprecated andreplaced by thelicense show

command.

na_license(1) manpage

8.2

license add Accepts a list of 28digit upper-casealphanumeric characterkeys.

Data ONTAP SystemAdministration Guidefor 7-Modena_license(1) manpage

8.2

license delete Requires the packagename when you deletea license; requiresconfirmation to delete.

Data ONTAP SystemAdministration Guidefor 7-Modena_license(1) manpage

8.2

reallocate start The -u option has beenadded. This optionduplicates blocks thatare shared betweenfiles by deduplication.

na_reallocate(1) manpage

8.2

revert_to The -d option has beenadded. This optionenables theadministrator toproceed with revertingData ONTAP after thebacklog ofasynchronous deleteoperations iscompleted.

na_revert_to(1) manpage

8.2

sis config The -Q option has beenadded. This optionenables theadministrator to enableor disableincompressible datadetection on a volume.

Data ONTAP StorageManagement Guide for7-Modena_sis(1) man page

8.2

42 | Release Notes

Command Change Documentation Release commandchanged in

sis config The -z option has beenadded. This optionenables theadministrator tospecify the minimumfile size to attemptquick check on a file.

Data ONTAP StorageManagement Guide for7-Modena_sis(1) man page

8.2

sis start The -m option has beenadded. This optionenables theadministrator to scanexisting data, generatededuplicationmetadata, and skipshared blocks.

Data ONTAP StorageManagement Guide for7-Modena_sis(1) man page

8.2

sis start The -o option has beenadded. This optionenables theadministrator to scanexisting data and skipshared blockoptimization.

Data ONTAP StorageManagement Guide for7-Modena_sis(1) man page

8.2

snap list The -fs-block-format option hasbeen added. Thisoption enables theadministrator todetermine whether 32-bit format Snapshotcopies are present.

na_snap(1) man page 8.2.1

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 43

Command Change Documentation Release commandchanged in

software install The softwareinstall command isreplaced by thesystem node

service-processor

image update

command for manuallyupdating the SPfirmware.

Note: Thesoftware

install commandcontinues to supportthe RLM firmwareupdate.

The man page forsystem node

service-processor

image update

8.2

sp This command familyhas been deprecated infavor of the systemnode service-

processor commandfamily.

The man pages forsystem node

service-processor

8.2

sysconfig The Preload Rev fieldhas been added to theoutput with the -aoption for some FibreChannel initiatoradapters.

na_sysconfig(1) manpage

8.2

sysconfig This command nowreports unknown andunsupported shelftypes.

na_sysconfig(1) manpage

8.2.1

system health

autosupport

trigger history

show

The optional -asup-enable parameter hasbeen added. Thisparameter shows thealerts that did or didnot trigger anAutoSupport message.

na_system_health_autosupport(1) man page

8.2

44 | Release Notes

Command Change Documentation Release commandchanged in

system health

policy definition

modify

• The optional -asup-enable

parameter has beenadded. Thisparameter specifieswhether the alertsgenerated by thespecified healthpolicy triggers anAutoSupportmessage.

• Changes to the -enable parameterare now persistentacross reboots.

na_system_health_policy(1) man page

8.2

system health

policy definition

show

The optional -asup-enable parameter hasbeen added. Thisparameter shows healthpolicies that do or donot triggerAutoSupport messagesfor alerts.

na_system_health_policy(1) man page

8.2

vol autosize The -minimum-sizeand -shrink-threshold-percent parametershave been added tosupport the newautoshrink capability.

Data ONTAP StorageManagement Guide for7-Mode

na_vol(1) man page

8.2

vol status The -F and -S optionswere added. Theseoptions displaydetailed informationabout how space isused in the volume andin the volumefootprint, respectively.

Data ONTAP StorageManagement Guide for7-Mode

na_vol(1) man page

8.2

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 45

Command Change Documentation Release commandchanged in

vol status The -F and -S optionswere updated to acceptthe specification ofunits (KB, MB, GB,TB).

na_vol(1) man page 8.2.1

Replaced or removed commands in Data ONTAP 8.2You need to know which commands have been replaced or removed.

The following command is removed in Data ONTAP 8.2:

• aggr show_space

Use the aggr status -S command to see space usage in the aggregate. Use the df -hybridcommand to see space usage in the SSD cache of a Flash Pool aggregate.

New options in Data ONTAP 8.2This release includes new options that you can use with the options command.

The table provides the following information about each new option that you can use with theoptions command:

• Purpose of the option• Default value for the option• Data ONTAP release in which the option was introduced

For more information about the options command and individual options, see the na_options(1)man page.

Option Purpose Defaultvalue

Releaseadded

autosupport.support.reminder Enables or disables areminder message thatappears whenautosupport.suppor

t.enable is set to off.

Note: This option waspreviously hidden.

on 8.2

46 | Release Notes

Option Purpose Defaultvalue

Releaseadded

cf.giveback.auto.override.vetoes Overrides givebackvetoes. In previousversions of DataONTAP, this option wasnamedcf.giveback.auto.t

erminate.bigjobs.

off 8.2

cf.mode Enables HA mode on thecontroller. The HA modemust be set on bothcontrollers for the HAfunctionality.

This option replaces therequirement for a cflicense.

None. 8.2

coredump.savecore.warn Enables Data ONTAP toprompt for confirmationwhen deleting unsavedcore files.

off 8.2

disk.auto_assign_shelf Supports shelf-level diskautoassignment.

off 8.2

flexscale.readahead_blocks Caches readahead datathat the system evictsfrom buffer cache.Readahead data is datathat clients are likely torequest.

off 8.2

ldap.fast_timeout.enable Controls the timeoutbehavior of LDAP clientoperations.

on 8.2

ldap.retry_delay Sets the time, in seconds,to wait before trying toconnect to LDAP serversafter a failed attempt.

120 8.2

licensed_feature.snaplock.enable Enables the SnapLockCompliancefunctionality.

off 8.2

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 47

Option Purpose Defaultvalue

Releaseadded

licensed_feature.snaplock_enterpr

ise.enable

Enables the SnapLockEnterprise functionality.

off 8.2

nfs.rpcsec.trace Enables new EMSmessages to helptroubleshoot Kerberosissues.

off 8.2

raid.mix.hdd.disktype.capacity Enables mixingperformance disks withdifferent Data ONTAPdisk types in the sameaggregate.

on 8.2

raid.mix.hdd.disktype.performance Enables mixing capacitydisks with different DataONTAP disk types in thesame aggregate.

off 8.2

raid.mix.hdd.rpm.capacity Enables mixing capacitydisks with differentspeeds when creating oradding to aggregates.

off 8.2

raid.mix.hdd.rpm.performance Enables mixingperformance disks withdifferent speeds whencreating or adding toaggregates.

on 8.2

snapvault.stale_config_cleanup_en

able

Enables or disables thecleanup of staleSnapVaultconfigurations.

on 8.2

cf.remote_syncmirror.enable When set to on, enablesthe MetroClusterfunctionality.

off 8.2

security.passwd.rules.minimum.low

ercase

Specifies the minimumnumber of lowercasealphabetic charactersthat a password mustcontain

0 8.2

48 | Release Notes

Option Purpose Defaultvalue

Releaseadded

security.passwd.rules.minimum.upp

ercase

Specifies the minimumnumber of uppercasealphabetic charactersthat a password mustcontain

0 8.2

Changed options in the Data ONTAP 8.2 release familyYou need to know which options have changed or become obsolete.

For each option, the following table gives this information:

• Name of the changed option• Nature of the change• Release in which the change was introduced

For more information about the options command and individual options, see the na_options(1)man page.

Option Change Releasechanged

autosupport.cifs.verbose This option was removed. 8.2

cf.giveback.auto.terminate.bigj

obs

This option has been renamed ascf.giveback.auto.override.vetoe

s.

8.2

nfs.authsys.extended_groups_ns.

queue_max

The maximum limit for this option waschanged to 640.

8.2

nfs.thin_prov.ejuke The default for this option was changed toon.

8.2

nfs.v4.id.allow_numerics The default for this option was changed tooff.

8.2

raid.disk.timeout.enable This option was removed. 8.2.1

Summary of new and changed commands and options in the Data ONTAP 8.2 release family operatingin 7-Mode | 49

Option Change Releasechanged

raid.disktype.enable This option was replaced by the followingtwo options:

• raid.mix.hdd.disktype.capacit

y

• raid.mix.hdd.disktype.perform

ance

8.2

raid.rpm.ata.enable This option was replaced byraid.mix.hdd.rpm.capacity. Settingit to on enables disk speed mixing forcapacity disks.

8.2

raid.rpm.fcal.enable This option was replaced byraid.mix.hdd.rpm.performance.Setting it to off disables disk speedmixing for performance disks.

8.2

50 | Release Notes

Requirements for running Data ONTAP 8.2

You can verify whether you have the storage systems and firmware needed to run 7-Mode softwarefor the Data ONTAP 8.2 release family.

To determine the capacity and maximum volume size of your storage system model, see theHardware Universe at hwu.netapp.com.

Supported systemsYou need a supported storage system to run the Data ONTAP 8.2 release for 7-Mode.

The following FAS systems and V-Series systems are supported:

• FAS8020• FAS8040• FAS8060• 6290• 6280• 6250• 6240• 6220• 6210• 6080• 6040• 3270• 3250• 3240• 3220• 3210• 3170• 3160• 3140• FAS2240• FAS2220

Note: When a storage system name appears without a prefix (for example, 3270 instead ofFAS3270 or V3270), the related content applies to both FAS systems and V-Series systems.

The following FlexCache systems are supported:

• SA600

51

• SA320• SA300

The following Data ONTAP-v systems are supported:

• CBvM100 (Data ONTAP Edge with the Value bundle)• FDvM100 (Data ONTAP Edge with the Premium bundle)

All systems supported by the Data ONTAP 8.2 release family for 7-Mode, except Data ONTAP-vsystems, can be configured as an HA pair.

For more information about supported storage systems in the Data ONTAP 8.2 release family, seethe Hardware Universe at hwu.netapp.com.

Unsupported systemsSome storage systems are not supported in the Data ONTAP 8.2 release family operating in 7-Mode.

The following storage systems are not supported beginning in Data ONTAP 8.2:

• 6070• 6030• 3070• 3040• FAS2040

Note: Any mention of these unsupported platforms in the remainder of the documentation libraryis an oversight and will be removed in a future release.

Where to get the latest firmware versionsYou need to confirm that you have the latest firmware for your storage system, disks, and diskshelves.

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

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

Storage system firmware

It is best to upgrade to the latest version of storage system firmware. For a list of available systemfirmware, see the System Firmware Release Table at support.netapp.com/NOW/cgi-bin/fw. For moreinformation, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

52 | Release Notes

Disk firmware

For information about the latest disk firmware, see the Disk Drive & Firmware Matrix at support.netapp.com/NOW/download/tools/diskfw.

Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For moreinformation, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

Disk shelf firmware

For information about the latest disk shelf and ESH (Embedded Switched Hub) firmware, see theDisk Shelf & ESH Firmware Matrix at support.netapp.com/NOW/download/tools/diskshelf.

FlexArray Virtualization (V-Series) interoperability and limitsinformation

Not all Data ONTAP releases support the same features, configurations, storage system models, andstorage array models. During your deployment planning, you must check Data ONTAP supportinformation to ensure that your deployment conforms to Data ONTAP hardware and softwarerequirements for all systems in the deployment.

Previously, all support information used to set up deployments with storage arrays was included inthe V-Series Support Matrix, while the array LUN-specific limits were provided in the V-SeriesLimits Reference for Third-Party Storage and the V-Series Support Matrix. This information is nowavailable through tools as shown in the following table:

For information about... You should look here...

Data ONTAP working with devices, includingthe following:

• Supported storage arrays and storage arrayfirmware

• Supported switches and switch firmware• Whether your storage array supports

nondisruptive (live) upgrade of the storagearray firmware

• Whether a MetroCluster configuration issupported with your storage array

Interoperability Matrix at support.netapp.com

Requirements for running Data ONTAP 8.2 | 53

For information about... You should look here...

Data ONTAP limits for releases and platforms,including the following:

• Minimum and maximum array LUN sizes,including the minimum array LUN size forthe root volume and spare core array LUNs

• Minimum aggregate size for aggregates witharray LUNs

• Supported block size• Minimum and maximum capacity• Neighborhood limits

Hardware Universe at hwu.netapp.com

Data ONTAP-v requirements and support informationNot all Data ONTAP features or configurations are supported when running on a Data ONTAP-vplatform, including the Data ONTAP Edge product. This is because of differences when DataONTAP is running in a virtual machine on a host server instead of running on a NetApp storagecontroller.

See the "Data ONTAP-v supported and unsupported functionality" section in the Data ONTAP EdgeInstallation and Administration Guide for the list of unsupported Data ONTAP features.

The hardware platform on which Data ONTAP-v is installed must meet the requirements listed in theInteroperability Matrix at support.netapp.com/matrix.

54 | Release Notes

Important cautions

Before upgrading to this release of Data ONTAP, you need to read the important cautions 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 NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

Upgrade cautionsIf you are upgrading to this Data ONTAP release, you should review the cautions and takeappropriate action for any that apply in your environment.

For more information about procedures and planning, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

Change in how Data ONTAP handles file names containing UTF-16supplementary characters

Starting with Data ONTAP 8.2.1, there is a change in how Data ONTAP handles file namescontaining UTF-16 supplementary characters that you must be aware of if your environment usessuch file names.

Unicode character data is typically represented in Windows applications using the 16-bit UnicodeTransformation Format (UTF-16). Characters in the basic multilingual plane (BMP) of UTF-16 arerepresented as single 16-bit code units. Characters in the additional 16 supplementary planes arerepresented as pairs of 16-bit code units that are referred to as surrogate pairs.

When you create file names on the storage system that contain supplementary characters, DataONTAP checks the surrogate pairs. If they are valid, Data ONTAP accepts the file name. If they areinvalid, Data ONTAP now rejects the file name and returns an invalid file name error.

Compatible versions of management software are required

After you upgrade to Data ONTAP 8.2 or later, the license-list-info ZAPI is no longer supported. Asa result, you must install Data ONTAP management software versions that are supported by DataONTAP 8.2 or later.

The Data ONTAP management software affected by this change includes, but is not limited to, theSnapDrive and SnapManager products, Virtual Storage Console, and Operations Manager products.For the complete list of affected Data ONTAP management software, specific versions, and alerts,see the Interoperability Matrix Tool on the NetApp Support Site.

For the Data ONTAP API changes, including new and deprecated APIs, see the NMSDK APIDocumentation page on the NetApp Community.

55

Third-party applications or scripts written to use the license-list-info ZAPI will fail after the upgradeto Data ONTAP 8.2 or later. Therefore, if you use third-party applications, you should contact thevendors to obtain an update that is supported for Data ONTAP 8.2 or later.

If you are using synchronous SnapMirror, upgrading to Data ONTAP 8.2can cause performance degradation

If you have deployed synchronous SnapMirror in Data ONTAP 8.1.x for 7-Mode, upgrading to DataONTAP 8.2 can cause performance degradation. To avoid this issue, you should remain in DataONTAP 8.1.x.

For more information, see the knowledgebase article 2017591 on the NetApp Support Site.

3210 and 3140 systems with Flash Cache modules not supported

3210 and 3140 storage systems with Flash Cache modules are not supported in Data ONTAP 8.2 andlater 8.2.x releases operating in 7-Mode. You cannot upgrade to Data ONTAP 8.2 or later 8.2.xreleases if you have Flash Cache modules enabled in your 3210 or 3140 system.

KB article 2017616 contains information about this issue and can be found at kb.netapp.com/support/index?page=content&id=2017616.

Modifying the state of deduplication during an intermediate upgrade cancause storage system disruption

If you are upgrading to Data ONTAP 8.2 from a release earlier than Data ONTAP 8.1, you mustperform an intermediate upgrade. During the intermediate upgrade if you modify the state ofdeduplication on a volume, then storage system disruption can occur.

You can upgrade from Data ONTAP 7.3.x to Data ONTAP 8.0.2 or Data ONTAP 8.0.3 and then toData ONTAP 8.1.x. You might disable deduplication before upgrading from Data ONTAP 7.3.x andthen enable deduplication after upgrading to Data ONTAP 8.1.x. If the next scheduled volumeefficiency operation runs on the volume before upgrading to Data ONTAP 8.2 , then storage systemdisruption can occur. However, if you upgrade to Data ONTAP 8.1.2 and enable deduplication on thevolume, then Data ONTAP generates an error message indicating the workaround.

As a workaround for this issue, after upgrading to Data ONTAP 8.2, you must run the sis starts-s command on the volume on which deduplication was disabled before initiating the intermediateupgrade.

Disks offline in Windows Server 2008 and 2012 after Data ONTAP upgrade

During a Data ONTAP upgrade, LUNs are assigned new revision numbers. Windows Server 2008and Windows Server 2012 interpret the LUNs with new revision numbers as new disks and set them

56 | Release Notes

offline after a host reboot; this status is shown in Windows management interfaces after the upgrade.Windows Server 2003 ignores LUN revision numbers.

If the disks are offline, bring them online by using Windows disk management tools or SnapDrivefunctionality.

You can work around this problem by setting the SAN policy to "Online All" prior to upgrading DataONTAP. Use the Windows diskpart command to change the SAN policy. After you upgrade DataONTAP, change the policy back to the default setting of "Offline Shared".

For more information, see Knowledgebase article 2013348 on the NetApp Support Site at support.netapp.com.

Stale metadata not automatically removed during deduplication operationson volume

Stale deduplication-related metadata can exist in the FlexVol volumes and aggregates on yoursystem, resulting in slow deduplication processing or your systems running out of space.

Your systems can experience this problem if you are upgrading from a Data ONTAP 8.1 release priorto 8.1.2P4, if deduplication is enabled on any FlexVol volume, and if a FlexVol volume or theassociated aggregate is more than 70 percent full. If these conditions exist, see bug ID 657692 beforeproceeding with an upgrade to Data ONTAP 8.2.

Related information

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

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

If you reinstall a license key in Data ONTAP 8.2 or later, you must use thenew license key format

Starting with Data ONTAP 8.2, all license keys are 28 characters in length. Licenses installed prior toData ONTAP 8.2 continue to work after you upgrade to Data ONTAP 8.2 or later. However, if youneed to reinstall a license when you are running Data ONTAP 8.2 or later, the old key is notaccepted.

The Data ONTAP 8.2 release family accepts a license key only in the new, 28-character format. Youcan find license keys for your initial or add-on software orders at the NetApp Support Site under MySupport > Software Licenses. For instance, you can search with the serial number of a system tofind all license keys associated with the system. If you cannot locate your license keys from theSoftware Licenses page, you should contact your sales or support representative.

Important cautions | 57

Changes to SP firmware update methods

Starting with Data ONTAP 8.2, a baseline SP firmware image is packaged with the Data ONTAPimage. By default, the SP automatic update functionality is enabled. You have the option to manuallytrigger an SP update.

Data ONTAP 8.2 and later releases include an SP firmware image that is called the baseline image.You do not need to download the baseline SP firmware image separately. If a new version of the SPfirmware becomes subsequently available, you have the option to download it from the SystemFirmware and Diagnostics Download page on the NetApp Support Site and update the SP firmwareto the downloaded version without upgrading the Data ONTAP version. For information aboutmanually downloading and updating the SP firmware, see the SP Firmware Download andInstallation Instructions on the NetApp Support Site.

Data ONTAP offers the following methods for managing SP firmware updates:

• The SP automatic update functionality is enabled by default, allowing the SP firmware to beautomatically updated in the following scenarios:

◦ When you upgrade to a new version of Data ONTAPThe Data ONTAP upgrade process automatically includes the SP firmware update, providedthat the SP firmware version bundled with Data ONTAP is newer than the SP version runningon the system.

◦ When you download a version of the SP firmware from the NetApp Support Site and thedownloaded version is newer than the one that the SP is currently running

You have the option to disable the SP automatic update functionality by using the system nodeservice-processor image modify command. However, it is best to leave the functionalityenabled. Disabling the functionality can result in suboptimal or nonqualified combinationsbetween the Data ONTAP image and the SP firmware image.

• Data ONTAP enables you to trigger an SP update manually and specify how the update shouldtake place by using the system node service-processor image update command.You can specify the following options:

◦ The SP firmware package to use (-package)You can update the SP firmware to a downloaded package by specifying the package filename. The system node image package show command displays all package files(including the files for the SP firmware package) that are available on a node.

◦ Whether to use the baseline SP firmware package for the SP update (-baseline)You can update the SP firmware to the baseline version that is bundled with the currentlyrunning version of Data ONTAP.

◦ Whether to update the entire firmware image or only the changed portions (-update-type)◦ If updating the entire firmware image, whether to also reset log settings to the factory default

and clear contents of all logs maintained by the SP, including the event logs, IPMI logs, andforensics logs (-clear-logs)

58 | Release Notes

For information about the system node service-processor image update command, seethe man page.

• Data ONTAP enables you to display the status for the latest SP firmware update by using thesystem node service-processor image update-progress show command.

Any existing connection to the SP is terminated when the SP firmware is being updated. This is thecase whether the SP firmware update is automatic or manually triggered.

Related information

NetApp Support Site: support.netapp.com

Storage management cautionsYou should review these issues and take appropriate action before upgrading or reinstalling.

Disk failures might increase for some disk models after upgrading to thisversion of Data ONTAP

Starting with Data ONTAP 8.1.2, the software install or upgrade includes new disk shelf firmwareversions for DS14mk2 AT and DS4243 disk shelves that provide enhanced disk error detection andprediction capabilities. Therefore, after upgrading to this version of Data ONTAP, you mightexperience an increase in the number of disk failures for certain disk shelf and disk models.

Increased disk failures after upgrading to this version of Data ONTAP is expected behavior,especially if you are upgrading from a version of Data ONTAP that did not include the new firmwareversions. You should follow standard best practices for spares when you upgrade, to ensure thatsufficient spares are always available.

The following table shows the disk shelf and disk models that might show an increased failure rateafter upgrading:

Storage enclosure Part number Output from sysconfig -a Capacity

DS14mk2 AT X/SP-269A-R5 X269_SMOOS01TSSX 1 TB

X/SP-268A-R5 X268_SMOOST75SSX 750 GB

X/SP-267A-R5 X267_SMOOST50SSX 500 GB

X/SP-262B-R5 X262_SMOOST25SSX 250 GB

DS4243 X/SP-302A-R5 X302_SMOOS01TSSM 1 TB

X/SP-310A-R5 X310_SMOOST50SSM 500 GB

For more information about this issue, see Bug ID 556910 in Bugs Online.

Important cautions | 59

Related information

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

File access and protocols cautionsIf your storage system is deployed in a NAS environment, you should review the important cautionsregarding file access and protocols management and take appropriate action before upgrading orreinstalling.

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

CIFS startup might take several minutes after HA failover and giveback

After an HA failover and giveback, the CIFS protocol might take several minutes to start up. If vFilerunits are present, they might not be initialized for the duration of the CIFS startup time. The delay inCIFS startup is typically due to network infrastructure issues related to domain controllers and LDAPservers.

About this task

To ensure that the domain controllers, DNS servers, and LDAP servers are accessible, it isrecommended that you run the following tests on the partner node for which giveback is to beinitiated before initiating a giveback. Successful execution of these commands does not guaranteethat CIFS startup during giveback will occur quickly. The servers that are responding now might faillater to respond when giveback occurs.

If the node contains vFiler units, you must complete the procedure on all vFiler units running CIFS.

Steps

1. Test domain controller connectivity and responsiveness by entering the following command:

cifs testdc

If the command fails, reconnect to a domain controller by using the cifs resetdc command.The cifs resetdc command terminates existing domain controller connections and thendiscovers available domain controllers and establishes new connections.

2. Verify that the cifs resetdc command succeeded by entering the following command:

cifs domaininfo

If the command fails, identify and fix the domain connectivity issue before proceeding.

3. Test Active Directory LDAP connectivity by entering the following command:

cifs adupdate

If the command fails, identify and fix the Active Directory LDAP issues before proceeding.

60 | Release Notes

4. Look up the SID of a domain user for the domain to which the CIFS server belongs by enteringthe following command:

wcc -s your_domain\user_account

If the command fails, identify and fix the issue before proceeding.

5. If LDAP is configured for user mapping, run LDAP queries by entering the following commands:

priv set advanced

getXXbyYY getpwbyname_r user_name

getXXbyYY getpwbyuid_r uid

If the commands fail, identify and fix the LDAP issues before initiating giveback.

Result

After you verify domain controller, DNS server, and LDAP server accessibility, you can proceedwith giveback.

Revert and downgrade cautionsIf you are reverting or downgrading from this release to an earlier release, you should review thecautions and take appropriate action for any that apply in your environment.

For more information about procedures and planning, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

Reverting to a release earlier than Data ONTAP 8.2 might requireinstallation of licenses for some features

If you gained access to licensed or entitled features by upgrading to Data ONTAP 8.2 or later andthese features required a license prior to Data ONTAP 8.2, you might need to install a license afterreverting. This is the case if a license was not previously installed for the release you revert to.

The licensing models for Data ONTAP 8.2 are different from earlier releases. Some functionality thatrequired a license prior to Data ONTAP 8.2 might be available for free or as part of a package thatyou are licensed to install in Data ONTAP 8.2 or later. If you did not install a license for thefunctionality prior to Data ONTAP 8.2 and you revert to the earlier release, you might need to installa license so that you can continue to use the functionality after the revert.

For example, you did not install a SyncMirror license prior to Data ONTAP 8.2. After you upgradeto Data ONTAP 8.2 or later, SyncMirror is available to you without a license. If you revert to arelease earlier than Data ONTAP 8.2, you must install a license to continue to use SyncMirror.

For information about the Data ONTAP 8.2 licensing model and the features that require licenses,see the knowledgebase article Data ONTAP 8.2 Licensing Overview and References on the NetAppSupport Site.

Important cautions | 61

For information about the Data ONTAP 8.1 licensing model and the features that require licenses,see the knowledgebase article Using License Keys with Data ONTAP 8.1 7-Mode FAQ on theNetApp Support Site.

Licensing implications for reverting a system that is shipped with DataONTAP 8.2 or later to an earlier release

You need to be aware of the licensing implications if you have a system that is shipped with DataONTAP 8.2 or later and you want to revert it to a release in the Data ONTAP 8.1 release family.

If your system is shipped with Data ONTAP 8.2 or later and you reinstall it with a release in the DataONTAP 8.1 release family, you must install a key for the desired license package in the formatsupported by the Data ONTAP 8.1 release family. To obtain a license key for the reinstalled system,contact your sales representative. For information about the Data ONTAP 8.1 licensing model andthe features that require licenses, see the knowledgebase article Using License Keys with DataONTAP 8.1 7-Mode FAQ on the NetApp Support Site.

Downgrading or reverting to Data ONTAP 8.1 or earlier with a Flash Poolaggregate root aggregate disables the system

If you configure a Flash Pool aggregate (an aggregate that contains both HDDs and SSDs) as yourroot aggregate and you want to downgrade or revert to any release of Data ONTAP earlier than 8.1.1,including 8.1, you must first move the root aggregate to an HDD or SSD aggregate. Otherwise, yoursystem will not boot after the downgrade or revert.

SP firmware might require a downgrade if you revert or downgrade to anearlier Data ONTAP release

If your current SP firmware version is not supported for the Data ONTAP release you aredowngrading or reverting to, you must install a supported SP firmware version for the earlier DataONTAP release.

After the Data ONTAP revert or downgrade process is complete, you must take the action to installan SP firmware version that is supported for the Data ONTAP version you reverted or downgradedto. To learn which SP firmware versions are supported by each Data ONTAP release, see the BIOSService Processor Support Matrix on the NetApp Support Site. For instructions about downloadingand installing an SP firmware version, see the System Firmware and Diagnostics Download page onthe NetApp Support Site.

62 | Release Notes

Reverting to an earlier release of Data ONTAP when 32-bit volumes oraggregate are converted to 64-bit format

After an upgrade, if you have converted the 32-bit volumes or aggregate to the 64-bit format, youcannot revert the source and destination systems to an older version of Data ONTAP until you deleteall of the Snapshot copies on both the source and the destination volumes.

ACLs containing more than 400 ACEs are dropped during revert

Support for up to 1,024 ACEs in NFSv4 ACLs is a new feature in Data ONTAP 8.2. Reverting to aprevious release family requires action if you have NFSv4 ACLs in your environment that containmore than 400 ACEs.

If you perform a file system revert to a Data ONTAP 8.1 release, any ACLs containing more than400 ACEs are dropped.

To avoid this issue, you should do the following:

1. Identify all ACLs containing more than 400 ACEs.

2. Modify them to contain 400 or fewer ACEs.

Important cautions | 63

Known problems and limitations

Some unexpected and potentially undesired post-upgrade behaviors, and in some cases workaroundsto avoid these behaviors, have been identified.

To request more information about an individual bug and to explore other bug-related tools, see BugsOnline on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

Manageability issuesYou should be familiar with the known issues and limitations in the management interface that affectyour ability to manage the storage system.

These issues include problems with command behavior, command output, or error messagespresented in the Data ONTAP CLI or web interface and problems with UNIX or operating systemcommands used to interface with your storage system.

Command typed in from one connection might be executed by aconcurrent connection

If the telnet.distinct.enable option is set to off, a command typed in from a consoleconnection that is initiated through the remote management device (the RLM or the SP) might beexecuted by a concurrent SSH or Telnet connection to the storage system.

When you access the storage system through a Telnet or SSH connection, and if there is an existingconsole session that is initiated through the remote management device, pressing Enter on yourTelnet or SSH session might execute a command that has just been typed in but not yet executedfrom the concurrent console session. This behavior might happen even if you do not see thecommand name on your Telnet or SSH session. This behavior might occur if thetelnet.distinct.enable option is set to off.

The wrfile command might fail to capture all input during a cut-and-pasteoperation performed through the RLM or SP

If you access the system console from the RLM or SP and you perform a cut-and-paste operation ongraphic input that involves using the wrfile command, the command might fail to capture all input.

This behavior is a result of the unusually high sustained data rate in the cut-and-paste operation. Youcan avoid this issue by using an SSH console session instead of accessing the system console throughthe RLM or SP.

64 | Release Notes

Storage resource management issuesYou should familiarize yourself with the storage resource management issues in this release.

Long disk list for aggregate creation could cause disruption

One option for specifying the disks to be included in a new aggregate is to list them by name. If youhave long disk names or a large number of disks and you specify one or more disk names incorrectly,Data ONTAP encounters a disruption.

The best way to avoid this issue is to use a disk count for aggregate creation. This is preferred tousing a disk list, because it allows Data ONTAP to select the disks to be used in the aggregate.

If you cannot use a disk count, you can create the aggregate with a smaller number of disks, and addthe rest of the disks to the newly created aggregate in one or more subsequent steps.

Storage system disruption due to unavailability of asynchronous messages

Storage system disruption occurs when there are no asynchronous messages that can be used toinitiate tasks between different sub-systems within Data ONTAP. The number of asynchronousmessages per storage system is limited.

Deduplication operations use the asynchronous messages to send information to the block-sharingstate machine. However, these asynchronous messages are not given back to the system after asuccessful deduplication operation. This reduces the number of available asynchronous messages andwhen the deduplication operations drain all the messages, it leads to a storage system disruption.

Because the asynchronous messages are more in number (in the order of thousands), it takes thosemany deduplication operations to drain all the messages.

You can fix this issue by rebooting the storage system. All the asynchronous messages arereallocated once the storage system finishes rebooting. However, the issue is not completely avoided,because the subsequent deduplication operations start draining the asynchronous messages.

Out of space errors could be returned when fractional reserve is set to zero

If you are configuring volumes with zero fractional reserve and you are using certain technologies orData ONTAP features, you must take some extra precautions to avoid out of space errors.

Setting fractional reserve to zero increases your storage utilization. However, an applicationaccessing data residing in the volume could experience a data outage if the volume is out of freespace, even with the volume guarantee set to volume, when any of the following technologies andData ONTAP features are in use:

• Deduplication• Compression• FlexClone files

Known problems and limitations | 65

• FlexClone LUNs• Virtual environments

If you are using one or more of these technologies with no fractional reserve, and you need to preventerrors that can arise from running out of space, you must use all of the following configurationsettings for the volume:

• Volume guarantee of volume• File or LUN reservations enabled• Volume Snapshot copy automatic deletion enabled with a commitment level of destroy

Note: If your rate of change is high, in rare cases the Snapshot copy automatic deletion couldfall behind, resulting in the volume running out of space, even with all of the requiredconfiguration settings in use.

In addition, you can optionally use the volume autogrow capability to decrease the likelihood ofSnapshot copies needing to be deleted automatically. If you enable the autogrow capability, you mustmonitor the free space in the associated aggregate. If the aggregate becomes full enough that thevolume is prevented from growing, more Snapshot copies will probably be deleted as the free spacein the volume is depleted.

If you do not want to monitor aggregate free space or have Snapshot copies automatically deleted,you can set the volume's fractional reserve setting to 100. This requires more free space up front, butguarantees that data modification operations will succeed even when the technologies listedpreviously are in use.

Disk-type mixing might occur even when disk type is specified

You can configure Data ONTAP to allow mixing of capacity or performance disk types whencreating or adding to aggregates. When you specify a disk type with the -T parameter, if disk-typemixing is enabled, Data ONTAP might use an equivalent disk type rather than the type you specified.

Read performance for mirrored aggregates not in a MetroClusterconfiguration might be degraded

The cf_remote license is installed by default on all new 32xx and 62xx storage systems for versionsof Data ONTAP earlier than 8.2. If you upgraded to Data ONTAP 8.2 and are using mirroredaggregates that are not in a MetroCluster configuration, the presence of this license can reduce readperformance because data is read from only one plex.

You can recover from this situation by using the following command to disable the license (on bothnodes for HA pairs):

options remote_syncmirror.enable off

This removes the restriction and allows data to be read from either plex.

66 | Release Notes

FlexArray Virtualization (V-Series) issuesYou should understand the known problems and limitations related to using Data ONTAP systemswith storage arrays.

Too many storage devices presented to the Data ONTAP system

Starting with Data ONTAP 8.2.1, a low-memory Data ONTAP system (a storage system withphysical memory of 8 GB or less) might not be able to detect some of the presented disks and arrayLUNs if the number of storage devices discovered by the Data ONTAP system exceeds themaximum number of assignable devices allowed for that platform.

In such a situation, an EMS message is generated by the Data ONTAP system.

If you run into this issue, you should reboot your storage system.

For information about the maximum number of storage devices allowed for different platforms, seethe Hardware Universe at hwu.netapp.com.

Some Hitachi or HP XP array LUNs might not be visible

In the case of Data ONTAP systems that support array LUNs, if the FC initiator ports are zoned withHitachi or HP XP array target ports before the storage array parameters are set and the LUNs aremapped to the host groups, you might not be able to see any LUNs presented to the Data ONTAPinterface.

In this situation, Data ONTAP generates one of the following EMS messages:[fci.device.login.reject:info] The PLOGI transmitted by port XX was

rejected by port_id 0xYYYY with reason code 0x9 'Invalid R_CTL Field',

explanation code 0x29 'Insufficient Resources to Support Login'

[fci.device.login.reject:info]: The PLOGI transmitted by port XX was

rejected by port_id 0xYYYY with reason code 0x3 'Nx_Port Not Available,

Temporary', explanation code 0x29 'Insufficient Resources to Support Login'

Workaround

If zoning is configured prior to setting the parameters and mapping the LUNs to the host groups, youcan resolve the problem of LUNs not being visible by performing a path reinitialization to force arediscovery of the array LUNs that are mapped from a Hitachi or HP XP storage array. Forinformation on the path reinitialization process, see Workaround when LUNs are not visible withHitachi or HP XP storage arrays on page 83.

Known problems and limitations | 67

Network protocol issuesYou should familiarize yourself with the network protocol issues in this release.

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

Restriction on using auto-configured LLA as a gateway for a default route

A link-local address (LLA), an address starting with fe80:, cannot be accessed by hosts outside of thesame subnet. Hosts within the same subnet can successfully access the LLA.

Because of an issue with the way in which IPv6 source addresses are selected, an LLA sourceaddress may be used instead of an address which is properly scoped (one that can reach addresses offthe local subnet). This can result in a loss of connectivity that affects some control plane applicationssuch as SNMP and RSH.

Due to this restriction, you should not use an auto-configured LLA as a gateway for a default route.Instead, assign a global scope IPv6 address as a gateway for a default route.

Error messages observed during change in the state of network interfacegroups

If there is change in the state of the network interface groups, error messages are displayed multipletimes on the Data ONTAP console.

When the status of interface groups is up or down, you will see the following error messages in thestorage system because of the change in the network interface state:

Event 'nbt.nbns.socketError' suppressed 13 times in last 500323 seconds.

NBT: Cannot do broadcast send on NBNS broadcast socket. Error 0x32: Network

is down.

These error messages end with the following notification message:

All CIFS name registrations have completed for the local server.

SNMPv3 access might fail for an existing user

SNMPv3 access might fail despite the user having the required permissions. This failure might occurafter a hardware change, which changes the System ID of the storage system.

When you face this issue, perform one of the following tasks:

• Change the password for the SNMPv3 user• Re-add the SNMPv3 user to your storage system

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

68 | Release Notes

Related information

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

Existing traphosts fail to receive SNMP traps

If an SNMP traphost is added or deleted, the existing SNMP traphosts stop receiving SNMP traps.

For example, consider a storage system configured with SNMP traphosts A and B added in order. Iftraphost B is deleted using the snmp traphost delete command, then A stops receiving furthertraps.

To resolve this issue, reinitialize the SNMP traphost system by executing the following command:

snmp init 1

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

Related information

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

The first VLAN configured over a port might bring the port downtemporarily

When you configure a VLAN for the first time over a port, the port might go down temporarily.

When you configure a VLAN over a port for the first time, the port might go down. This can causethe network to be temporarily disconnected.

However, the subsequent VLAN additions do not affect the port.

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

Related information

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

SnapMirror transfer cannot be blocked by using theinterface.blocked.mgmt_data_traffic option

In a single path SnapMirror transfer, you cannot use theinterface.blocked.mgmt_data_traffic option to block SnapMirror traffic from e0M on thedestination storage system. You can use this option to block SnapMirror transfer only on the sourcestorage system.

To block traffic from e0M, all the storage systems must use a consistent configuration. You mustensure that routes to the destination storage systems do not use e0M, and that neither SnapMirror norNDMP is configured to use an IP address that is assigned to e0M on a destination storage system.

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

Known problems and limitations | 69

Related information

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

Partner node might be unavailable during controller failover

When an interface name used for configuring the partner interface is applied as a host name alias inthe /etc/hosts file, and the interface name is used in an ifconfig command, the host name getsresolved in the local host context and not the partner context. This causes the partner node to beunavailable during takeover.

For example, while configuring the partner interface, the command fails during controller failover inthe following scenarios:

If the partner's /etc/rc file contains logs such as the following:

ifconfig ifgrp1 ifgrp1 netmask <netmask> partner ifgrp1

The partner's /etc/hosts file contains ifgrp1 as a host name alias:

10.10.10.10 toaster ifgrp1

The command fails because the name lookup of the interface group ifgrp1 occurs in the localhost's /etc/hosts file.

To avoid this issue, you should not use interface names as host name aliases in the /etc/hosts file.You should include the logs in one of the following formats:

• ifconfig ifgrp1 10.10.10.10 netmask <netmask> partner ifgrp1• ifconfig ifgrp1 hostname-ifgrp1 netmask <netmask> partner ifgrp1

You should also make the corresponding entry in the/etc/hosts file:

10.10.10.10 toaster-ifgrp1

For more details, see Bug ID 546958 in Bugs Online.

Related information

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

Disabling fast path in some network environments

Fast path is enabled by default on all storage systems. However, you might have to disable fast pathin certain environments in which fast path does not function optimally.

About this task

IP fast path is a mechanism that uses the network interface of an inbound request to send theresponse quickly by bypassing a routing table lookup. Fast path is enabled by default for all TCP andNFS over UDP connections.

70 | Release Notes

You might have to disable fast path if you are working in configurations of Cisco vPC, HP NICteaming, or asymmetric routing environments.

Step

1. To disable fast path, enter the following command:

options ip.fastpath.enable off

For more information, see the bug ID 494396 in Bugs Online on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

File access and protocols issuesIf your storage system is deployed in a NAS environment, you should review the known problemsand limitations regarding file access and protocols management and take appropriate action.

Data ONTAP LDAP client does not support revoked certificates

When LDAP over SSL is enabled, the Data ONTAP LDAP client does not support revokedcertificates. The LDAP client treats revoked certificates as if they are not revoked.

Option nfs.export.allow_provisional_access is nonfunctional

The nfs.export.allow_provisional_access option is nonfunctional. Even though it is visibleat the CLI and described in the man page, it does not modify any Data ONTAP NFS behavior.

“Access denied” error when setting an ACL on the root directory of anempty share

When setting an ACL on the root directory of an empty share, Windows Explorer returns an “accessdenied” error, even though the ACL is correctly set.

This issue occurs because Data ONTAP does not return “.” and “..” directory entries whenenumerating the root of an empty share.

The “access denied” error is based on an assumption in Windows Explorer that all directories haveboth a “.” and a “..” entry, which is not true even on NTFS volumes. The ACL is set correctly, andthe “access denied” error can be ignored. This issue applies to all Windows versions.

Use a Windows command-line utility, such as cacls.exe, to set permissions on the root of a share.

For more information about this issue, see Bug ID 527868 in Bugs Online.

Related information

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

Known problems and limitations | 71

Number of existing locks larger than the maximum allowed limit afterupgrade

When you upgrade a storage system from Data ONTAP 8.1.x to 8.2 or later, and then use the lockstatus -n command, the resulting output might display a larger number of current locks than themaximum number of locks allowed.

This issue can occur in the following scenario:

1. Before the upgrade, a client has a large number of locks.

2. You upgrade the storage system from Data ONTAP 8.1.x to 8.2 or later.This results in a slight reduction of the maximum limit of allowed locks.

3. The client reclaims its locks.Data ONTAP 8.2 or later allows the client to reclaim all locks, even if the total number is largerthan the new maximum limit of allowed locks.

4. You use the lock status -n command. Data ONTAP displays the amount of reclaimed lockswhich in this particular scenario can be larger than the maximum allowed limit of locks.

This behavior is expected and might only occur temporarily during an upgrade. As the clienteventually releases locks, the number of current locks continues to drop until it is below themaximum limit. After that, the number of new current locks can no longer exceed the maximumlimit.

CIFS client authentication fails if host name exceeds 16 characters

If a CIFS client with a NetBIOS name of more than 16 characters attempts to connect to the storagesystem, the authentication fails.

The storage system log records the following error message: AUTH:SPNEGO-Could not unpackNTLMSSP Authenticate token.

The connecting client displays the following error message:NT_STATUS_MORE_PROCESSING_REQUIRED.

To avoid this issue, you must ensure that the CIFS client name does not exceed 16 characters so thatit complies with NetBIOS specifications.

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

Related information

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

72 | Release Notes

Excessive pending CIFS authentication requests can cause servicedisruption

If domain controllers become unavailable to a vFiler unit, pending CIFS authentication requestsaccumulate on the storage system. If the issue is not resolved, this can prevent other vFiler units onthe storage system from successfully completing CIFS authentication requests.

Because a vFiler unit shares system resources with other vFiler units that are on the storage system,pending CIFS authentication requests for a vFiler unit could affect resources available to other vFilerunits.

Data ONTAP enables you to monitor pending CIFS authentication requests and take correctiveaction if needed. It generates SNMP traps in the following situations:

• The amount of pending CIFS authentication requests reaches 50 percent of total possible requests• The pending authentication requests drop down under 10 percent, meaning within a normal range

again

For information about SNMP, see the Data ONTAP Network Management Guide for 7-Mode.

Microsoft Windows 7 and Windows 8 clients fail to rename files anddirectories

When a Microsoft Windows 7 or Windows 8 client accesses an SMB share with widelinks enabled, itcan fail intermittently to rename files and directories on the mapped share. This can lead to asituation where attempts by Microsoft Office applications to save documents on the share fail.

This issue is caused by a bug in the Windows 7 and Windows 8 clients for which a hot fix isavailable from Microsoft. The bug is described and information about how to obtain the hot fix isprovided in the Microsoft KB articles Microsoft KB 2703610: support.microsoft.com/kb/2703610(Windows 7) and Microsoft KB 2821663: support.microsoft.com/kb/2821663 (Windows 8). The KBarticles also provide information about a workaround for this issue if you do not want to apply thehot fix.

Domain user unable to execute CLI commands

If you log in to the storage system CLI as a domain user and enter the command cifs gpupdate,all subsequently entered CLI commands on the currently active session fail and an error message isdisplayed.

The following error message is displayed:

[useradmin.unauthorized.user:warning] User domain_name\user_name denied access - missing required capability: 'cli-options'.

If you encounter this issue, log out, and then log back in to the CLI.

Known problems and limitations | 73

Client notification messages in Windows domains require NetBIOS

The Windows client notification feature used for client messaging, shutdown notices, and vscanalerts requires NetBIOS over TCP to be enabled in Data ONTAP.

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

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

CIFS widelinks are not accessible from Mac clients

When a user attempts to connect to a share using widelinks from a Mac OS X client, the attemptfails. Widelinks are not accessible from Mac OS X clients.

Windows clients make a Distributed File System (DFS) referral request after Data ONTAP returnsthe special error code STATUS_PATH_NOT_COVERED. The CIFS widelink feature uses thisbehavior in its implementation. In its DFS response, Data ONTAP can provide a referral that isconfigured by an administrator. The mapped referral allows a CIFS client to follow a UNIX symlink.

Although Mac OS supports DFS, Mac OS clients do not behave exactly like Windows clients in theway they handle the special DFS error code. Apple bug 13870704 has been created to document andtrack the issue. Customers encountering this issue with Mac support for widelinks should contactApple regarding this bug.

Related information

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

Data ONTAP permits deleting a file when an alternate data stream of the fileis in use

Data ONTAP differs with Microsoft servers in its handling of deleting a file with alternate datastreams attached. Data ONTAP allows deleting a file when an alternate data stream of the file is inuse.

In contrast, Microsoft servers disallow deleting a file that has any of its data streams open.

For more information about this issue, see Bug ID 627258 in Bugs Online.

74 | Release Notes

VAAI copy offload limitations when exporting datastore volumes with theactual flag

Data ONTAP supports certain VMware vStorage APIs for Array Integration (VAAI) features in anNFS environment, such as copy offloading. However, VMware vStorage over NFS has a copyoffloading limitation when exporting datastore volumes with the actual flag.

If you export a datastore volume with the actual flag, the export path should have a single componentfor the VAAI copy offload to work properly. For example:

sys1> exportfs -p actual=/vol/VAAI,root=192.168.42.227 /VAAI-ALIAS

Note: Copy offload does not work for multi-component export paths, such as the following:

sys1> exportfs -p actual=/vol/VAAI,root=192.168.42.227 /vol/VAAI-ALIAS

NFS VAAI copy offload uses block copy if the volume does not have SISenabled

The copy offload feature provided by the NFS Plug-in for VMware VAAI results in a block copy if aFlexVol volume that backs an NFS datastore has never had SIS enabled, or if the sis undocommand has been run against it. Normally, the NFS VAAI copy offload feature uses a FlexClonecopy operation to perform a fast and space-efficient copy. If SIS is not enabled on the volumecontaining the source and destination files, the copy offload defaults to using a block copy.

This issue has been seen only on storage systems running Data ONTAP operating in 7-Mode.

To enable the copy offload feature of VAAI for intra-volume clones and file copies, ensure that thevolume has SIS enabled. When you create a volume with Virtual Storage Console for VMwarevSphere, it by default enables SIS on datastore volumes.

Volume with SIS enabled

This example uses the sis on command to enable the VAAI_SIS volume for copy offloadingand deduplication. It then uses the vol status command to verify the change and show thatsis is listed for the volume VAAI_SIS:

NetApp1> sis on /vol/VAAI_SISNetApp1> vol status

Volume State Status Optionsvol0 online raid_dp, flex root 64-bitVAAI_SIS raid_dp, flex

Known problems and limitations | 75

sis 64-bit

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

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

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 alsomanually set the snapvault.lockvault_log_volume option to the name of a SnapLock forSnapVault log volume. After this option is set, SnapVault cannot be enabled on any vFiler units onthe storage system. For more information about the snapvault.lockvault_log_volume option,see the na_snapvault(1) man page.

SMTape operations abort if you turn off SnapMirror

If you turn off SnapMirror while performing SMTape backup and restore operations, SMTapeoperations such as smtape backup and smtape restore are aborted.

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

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

DAR fails if the file and the LUN have the same name on the destinationvolume

When DAR (Direct Access Recovery) of a file whose file name is the same as a LUN name on thedestination volume is performed, then the DAR fails. For a successful restore, perform DAR of thefile again.

76 | Release Notes

SAN administration issuesIf your storage systems are part of a SAN environment, you might need to familiarize yourself withSAN administration issues in this release.

For more information about these issues, see the Data ONTAP SAN Administration Guide for 7-Mode.

Some Oracle Linux systems using ASMlib fail to recognize disk groupswhen upgrading Data ONTAP

After upgrading to Data ONTAP 8.0.4, 8.1.1, 8.2 or later releases, some Oracle Linux-based systemsusing ASMlib can fail to recognize disk groups.

This problem is due to a change made in the Data ONTAP SCSI READ CAPACITY (16) parameterdata, which reports the number of logical blocks per physical block in the LUN.

For more information, see the KB article Oracle ASMlib reports ASM diskgroup has inconsistentsector size following a Data ONTAP upgrade.

The following two workarounds are available for this issue:

• Oracle recommends bypassing ASMlib by setting ASM_DISKSTRING, as shown in thefollowing example:

ASM_DISKSTRING = '/dev/oracleasm/disks/*'

• You should use the lun set command to disable the report-physical-size option for theaffected LUNs.For more information about the report-physical-size option, see the man page for the lunset command.

SAN configuration issuesYou should be familiar with the known issues related to SAN configuration.

Unified Target Adapter 2 (UTA2) in NetApp collateral is referred to as CNAin product documentation

NetApp uses the marketing term UTA2 to refer to a new generation of network adapters that can beconfigured as either 10-Gb Ethernet and FCoE ports or as 16-Gb FC initiator or target ports.

These ports are available as the X1143A-R6 adapter and as onboard ports on the FAS80xx systems.The Data ONTAP CLI and NetApp hardware and software documentation refer to these as CNAports.

Known problems and limitations | 77

MultiStore issuesYou should familiarize yourself with the MultiStore issues in this release.

For more information about these issues, see the Data ONTAP MultiStore Management Guide for 7-Mode.

vFiler unit migration using no-copy transfer not supported in aMetroCluster configuration

vFiler units can be migrated between storage systems in a HA pair by using the vfiler migrate -m nocopy command. However, when you are using a MetroCluster configuration, the vfilermigrate -m nocopy command is not supported.

Online migration of vFiler units is not supported on Flash Pools

You cannot perform online migration of vFiler units if a source vFiler unit has volumes on FlashPools or a Flash Pool is selected on the destination storage system for online migration.

78 | Release Notes

Changes to published documentation

Some information about this release has become available after the set of guides provided with thisrelease were published. The information should be used in conjunction with the guides provided withthis release of Data ONTAP.

Changes to V-Series document titlesStarting with Data ONTAP 8.2.1, the titles of the V-Series documents are changing because of thechange in name of the V-Series functionality to FlexArray Virtualization Software.

The new titles of the V-Series guides in Data ONTAP 8.2.1 (and later releases) are as follows:

Titles prior to Data ONTAP 8.2.1 Updated titles from Data ONTAP 8.2.1onwards

V-Series Systems Implementation Guide forNetApp E-Series Storage

FlexArray Virtualization Implementation Guidefor NetApp E-Series Storage

V-Series Systems Implementation Guide forThird-Party Storage

FlexArray Virtualization Implementation Guidefor Third-Party Storage

V-Series Systems Installation Requirements andReference Guide

FlexArray Virtualization InstallationRequirements and Reference Guide

Changes to the Commands Manual Page ReferenceNew information has become available since the previous revision of the Data ONTAP Commands:Manual Page Reference.

Missing options in the 7-Mode Command Reference Guide

Some options are missing in the Data ONTAP Commands: Manual Page Reference for 7-Mode,Volume 1.

The missing options are as follows:

Option Purpose Default value

coredump.savecore.warn Enables Data ONTAP toprompt for confirmation whendeleting unsaved core files

off

79

Option Purpose Default value

licensed_feature.snaplo

ck_enterprise.enable

Enables the SnapLockEnterprise functionality

off

licensed_feature.snaplo

ck.enable

Enables the SnapLockCompliance functionality

off

nfs.authsys.extended_gr

oups_ns.queue_max

Controls the maximum numberof requests that can be queuedat any given time to obtain theGIDs from the name service

80

Note: The maximum limit for nfs.authsys.extended_groups_ns.queue_max was changedto 640.

Changes to the SAN Configuration Guide for 7-ModeNew information has become available since the previous revision of the Data ONTAP SANConfiguration Guide for 7-Mode.

The previous title of this guide was Fibre Channel and iSCSI Configuration Guide for the DataONTAP 8.1 7-Mode Release Family.

Incorrect PVR requirements listed for shared SAN configurations

The Data ONTAP SAN Administration Guide for 7-Mode incorrectly indicates that a PVR is neededfor certain requirements.

The “Shared SAN configurations” topic incorrectly states that a PVR is needed for configurationsthat meet the requirements listed in the table. A PVR is needed for configurations that do not meetthe requirements listed in the table. A PVR is not needed for configurations that do meet thoserequirements.

Host Supported configuration

Windows EMC CX3, CX4, and VNX storage arrays with PowerPath 4.5 or later connected to aData ONTAP storage system using Data ONTAP DSM for Windows MPIO. Thisapplies equally to Windows 2003, Windows 2008, and Windows 2012.

Solaris EMC CX3, CX4, and VNX storage arrays PowerPath 5 or later connected to a DataONTAP storage system using MPxIO

AIX EMC CX3, CX4, and VNX storage arrays PowerPath 5 or later connected to a DataONTAP storage system using AIX MPIO

80 | Release Notes

FAS80xx multifabric HA configuration has incorrect illustration

The Data ONTAP SAN Configuration Guide for 7-Mode displays an incorrect illustration of theFAS80xx mulitfabric HA configuration.

There are two or more fabrics between the hosts and the controllers in a multifabric HAconfiguration. The illustration in the Data ONTAP SAN Configuration Guide for 7-Mode only showsone fabric. The correct illustration is as follows:

Host 1 Host 2 Host N

Controller 1

Controller 2

Switch/Fabric 1 Switch/Fabric 2

0c 1a 0d 1b

0d 1b0c 1a

Changes to the Data ONTAP Storage Management Guide for7-Mode

New information has become available since the previous revision of the Data ONTAP StorageManagement Guide for 7-Mode.

Physically moving an aggregate composed of disks

The topic “Physically moving an aggregate composed of disks” contains steps to reboot back intoNormal mode before removing the ownership information from the disks. This is incorrect.

You must remove the ownership information from the disks to be moved while you are still inMaintenance mode. The correct process flow for preparing to move the aggregate is as follows:

Changes to published documentation | 81

• Turn off disk ownership autoassignment if needed.• Boot into Maintenance mode.• Take the aggregate offline.• Remove the ownership information from the disks to be moved.• Reboot into Normal mode.• Remove the disks and disk shelves from the source system.

For the complete procedure, including command syntax and prerequisites, see the topic.

Changes to the Archive and Compliance Management GuideNew information has become available since the previous revision of the Data ONTAP Archive andCompliance Management Guide for 7-Mode.

Correction to SnapLock support for Storage Encryption

The topic “Licensing SnapLock functionality” in the Data ONTAP Archive and ComplianceManagement Guide for 7-Mode contains incorrect information that Storage Encryption is supportedon SnapLock Enterprise volumes. Storage Encryption is not supported on SnapLock volumes.

Changes to the Upgrade and Revert/Downgrade GuideNew information about upgrade procedures has become available since the previous revision of theData ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

Data compression does not need to be reenabled after upgrade

The topic “Verifying system status after an upgrade” contains a step that incorrectly states that datacompression is disabled by default during the Data ONTAP upgrade, and that you must reenable itwhen the upgrade is complete.

Data compression is not disabled when upgrading to Data ONTAP 8.2. Therefore, you do not need toreenable it after the upgrade is complete.

Changes to the FlexArray Virtualization ImplementationGuide for Third-Party Storage

There are some changes to the existing content of the FlexArray Virtualization ImplementationGuide for Third-Party Storage.

82 | Release Notes

Workaround when LUNs are not visible with Hitachi or HP XP storagearrays

The storage array parameters specified in the FlexArray Virtualization Implementation Guide forThird-Party Storage should be set and LUNs should be mapped to the host groups before the switchis zoned to connect the Data ONTAP system that uses array LUNs to a Hitachi or HP XP storagearray.

If zoning was configured prior to setting the parameters and mapping the LUNs to the host groups,you can resolve the problem of LUNs not being visible by doing a path reinitialization. The pathreinitialization forces a rediscovery of the array LUNs that are mapped from a Hitachi or HP XPstorage array.

The procedure you use depends on whether aggregates with Hitachi or HP XP array LUNs havealready been configured on the Data ONTAP system. (In the following procedures, assume thatNode-1 and Node-2 are the names of the Data ONTAP nodes.)

If aggregates with Hitachi or HP XP array LUNs are already created on a 7-Mode DataONTAP system that uses array LUNs

1. Run the following command to ensure that HA configuration is enabled on your Data ONTAPsystems:

cf status

2. Perform a takeover operation on Node-1 by running the following command:

cf takeover

3. Run the following command again to verify that Node-2 is ready for a giveback operation:

cf status

The following output is displayed:

Node-1> cf statusNode-1 has taken over Node-2Node-2 is ready for giveback

4. Perform a giveback operation on Node-1 by running the following command:

cf giveback

5. On Node-2, repeat Step 2 through Step 4.

If aggregates with Hitachi or HP XP array LUNs have not been created on a 7-ModeData ONTAP system that uses array LUNs

1. Run the following command to list all the Data ONTAP FC initiator ports that are connected tothe Hitachi or HP XP storage array:

Changes to published documentation | 83

sysconfig -v

2. Run the following command to take all the listed ports offline:

priv set advanced;fcadmin offline <adapter>

For example:

priv set advanced;fcadmin offline 0a

3. Run the following command to bring all the listed ports online:

priv set advanced;fcadmin online <adapter>

For example:

priv set advanced;fcadmin online 0a

Changes to the FlexArray Virtualization InstallationRequirements and Reference Guide

There are some changes to the existing content of the FlexArray Virtualization InstallationRequirements and Reference Guide.

Incorrect reference to a V-Series guide

The topic 'Getting started with troubleshooting' of the FlexArray Virtualization InstallationRequirements and Reference Guide incorrectly refers to the V-Series Systems Implementation Guidefor Third-Party Storage instead of the FlexArray Virtualization Implementation Guide for Third-Party Storage.

84 | Release Notes

Where to find product documentation and otherinformation

You can access documentation for all NetApp products and find other product information resources,such as technical reports and white papers, in the NetApp Library on the NetApp Support Site at support.netapp.com.

Related information

NetApp Support Site: support.netapp.comAccess & Order Product Documentation: support.netapp.com/knowledge/docs/docs.shtmlNetApp Library: Technical Reports: www.netapp.com/library

Information available onlineThe NetApp Support Site includes a natural language search tool so that you can search easily formany sources of useful information.

You can search for the following sources of information at support.netapp.com:

• Troubleshooting, including bug tools and knowledgebase articles• Documentation, including product guides and best practices, support communications, and

interoperability/compatibility matrix• Getting started, including navigating the site• Enabling AutoSupport and using the Support Owner's Manual• Technical assistance, including requesting a part (RMA), opening a case, and contacting technical

support• Downloads, including software, utility ToolChest, and product evaluations

Finding documentation on the NetApp Support SiteYou can access the current Data ONTAP documentation library from the NetApp Support Site.

The documentation roadmap and the latest documentation for this Data ONTAP release are at support.netapp.com/documentation/productsatoz/index.html.

85

Copyright information

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

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

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

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

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

The product described in this manual may be protected by one or more U.S. 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 ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

86 | Release Notes

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Customer Fitness, Cryptainer, CryptoShred, CyberSnap, Data CenterFitness, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engeniologo, E-Stack, ExpressPod, FAServer, FastStak, FilerView, Fitness, Flash Accel, Flash Cache, FlashPool, FlashRay, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy,GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management,LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetAppon the Web), Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, ShadowTape, Simplicity, Simulate ONTAP, SnapCopy, Snap Creator, SnapDirector, SnapDrive, SnapFilter,SnapIntegrator, SnapLock, SnapManager, SnapMigrator, SnapMirror, SnapMover, SnapProtect,SnapRestore, Snapshot, SnapSuite, SnapValidator, SnapVault, StorageGRID, StoreVault, theStoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, VelocityStak, vFiler,VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registeredtrademarks of NetApp, Inc. in the United States, other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United Statesand/or other countries. Microsoft is a registered trademark and Windows Media is a trademark ofMicrosoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

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

NetApp, Inc. NetCache is certified RealSystem compatible.

87

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by email to doccomments@netapp.com. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.• Telephone: +1 (408) 822-6000• Fax: +1 (408) 822-4501• Support telephone: +1 (888) 463-8277

88 | Release Notes