Data ONTAP 8.2 Release Notes for 7Mode

Data ONTAP® 8.2

Release Notes

For 7-Mode

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: [email protected]

Part number: 215-07974_A0 ur004September 2013

Contents

Data ONTAP 8.2 Release Notes for 7-Mode .............................................. 9Unsupported features ................................................................................. 10New and changed features in the Data ONTAP 8.2 release family for

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

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

Support for Flash Cache 2 modules .............................................................. 11

Support for 800-GB SSDs ............................................................................. 12

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

SAS optical cables not supported .................................................................. 12

Manageability enhancements .................................................................................... 12

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

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

AutoSupport enhancements ........................................................................... 14

Enhancements to health monitoring .............................................................. 15

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

Options for specifying uppercase and lowercase requirements in user

passwords ................................................................................................ 15

High-availability pair enhancements ......................................................................... 15

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

Storage resource management enhancements ........................................................... 16

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

Flash Pool aggregates support different RAID types and group sizes for

SSD cache ................................................................................................ 16

Flexibility for calculating maximum Flash Pool SSD cache size in HA

configurations .......................................................................................... 16

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

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

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

Storage efficiency enhancements .............................................................................. 17

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

V-Series enhancements ............................................................................................. 17

Table of Contents | 3

New licensing requirement for V-Series systems ......................................... 17

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

Support added for one V-Series FC initiator connecting to multiple

target ports ............................................................................................... 18

Increased LUN count per V-Series FC initiator ............................................ 19

Support added for ALUA with EMC CLARiiON and VNX storage

arrays ....................................................................................................... 19

Support added for native disks in a V-Series MetroCluster configuration . . . 19

Enhancements for setting the target queue depth on a V-Series system ....... 19

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

File access protocol enhancements ........................................................................... 20

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

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

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

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

Data protection enhancements .................................................................................. 21

Support for multipath tape access ................................................................. 21

Support for Single SnapVault license ........................................................... 22

SyncMirror is enabled by default .................................................................. 22

Options for enabling the SnapLock functionality ......................................... 22

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

Users cannot perform certain Qtree SnapMirror and SnapVault tasks

during the post-upgrade operations ......................................................... 22

Serial numbers used for tape aliasing ............................................................ 23

Data ONTAP Edge enhancements ............................................................................ 23

Data ONTAP changes that affect Data ONTAP Edge .................................. 23

Data ONTAP Edge and dvadmin changes .................................................... 24

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

New commands in the Data ONTAP 8.2 release ...................................................... 25

Changed commands in the Data ONTAP 8.2 release ............................................... 26

Replaced or removed commands in the Data ONTAP 8.2 release ........................... 31

New options in the Data ONTAP 8.2 release ............................................................ 31

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

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

4 | Release Notes

Unsupported systems ................................................................................................. 37

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

V-Series interoperability and limits information ...................................................... 38

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

Important cautions ..................................................................................... 40Upgrade cautions ....................................................................................................... 40

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

If you are using synchronous SnapMirror, upgrading to Data ONTAP

8.2 can cause performance degradation ................................................... 40

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

Modifying the state of deduplication during an intermediate upgrade can

cause storage system disruption .............................................................. 41

Disks offline in Windows Server 2008 and 2012 after Data ONTAP

upgrade .................................................................................................... 41

RAID disk timeout option not updated correctly after upgrade .................... 41

Upgrade to Data ONTAP 8.2.x with deduplicated volumes can fail due

to insufficient space ................................................................................. 42

Stale metadata not automatically removed during deduplication

operations on volume .............................................................................. 43

SAS optical cables not supported .................................................................. 43

Manageability cautions ............................................................................................. 43

If you reinstall a license key in Data ONTAP 8.2, you must use the new

license key format .................................................................................... 43

Changes to SP firmware update methods ...................................................... 44

Network protocol cautions ........................................................................................ 45

System might panic if the network configuration entries in the /etc/rc

file are not in the recommended order ..................................................... 45

Storage management cautions ................................................................................... 45

Disk failures might increase for some disk models after upgrading to

this version of Data ONTAP ................................................................... 45

File access and protocols cautions ............................................................................ 46

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

Setup cautions ........................................................................................................... 47

CIFS setup overwrites the storage system password .................................... 47

Revert and downgrade cautions ................................................................................ 48


If you revert to a release earlier than Data ONTAP 8.2, you might need

to install licenses for some features ......................................................... 48

Licensing implications for reverting a system that is shipped with Data

ONTAP 8.2 to an earlier release .............................................................. 48

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

Pool aggregate root aggregate disables the system ................................. 49

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

an earlier Data ONTAP release ............................................................... 49

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

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

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

Known problems and limitations .............................................................. 50Manageability issues ................................................................................................. 50

Command typed in from one connection might be executed by a

concurrent connection ............................................................................. 50

Storage resource management issues ........................................................................ 50

Storage system disruption due to unavailability of asynchronous

messages .................................................................................................. 50

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

zero .......................................................................................................... 51

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

Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded ............................................................. 52

Configuring ACP to use a different port on a FAS2240 system disables

ACP for the local SAS expander ............................................................. 52

Incorrect error message when FlexClone volume creation fails on a

storage system that is halting ................................................................... 52

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

Some Hitachi and HP XP array LUNs might not be visible ......................... 53

Some HP 3PAR array LUNs might be reported as unknown devices if

zoning is configured before setting the host persona .............................. 53

LUNs from a host group with fewer than 16 array LUNs are not visible

on some Hitachi and HP storage arrays ................................................... 54

Network protocol issues ............................................................................................ 54

SnapMirror transfer cannot be blocked by using the

interface.blocked.mgmt_data_traffic option ........................................... 54

6 | Release Notes

Partner node might be unavailable during controller failover when an

interface name is used as a host name alias in the /etc/hosts file ............ 55

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

File access and protocols issues ................................................................................ 56

Windows Security tab unavailable for shares with long UNC paths ............ 56

Number of existing locks larger than the maximum allowed limit after

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

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

Excessive pending CIFS authentication requests can cause service

disruption ................................................................................................. 57

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

directories ................................................................................................ 58

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

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

Effective style of qtrees created on an NTFS volume before configuring

CIFS ......................................................................................................... 58

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

VAAI copy offload limitations when exporting datastore volumes with

the actual flag .......................................................................................... 59

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

SIS enabled .............................................................................................. 60

Data protection issues ................................................................................................ 60

SnapVault cannot be enabled on vFiler units when relationships are

present in vfiler0 ...................................................................................... 61

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

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

SAN administration issues ........................................................................................ 61

Some Oracle Linux systems using ASMlib fail to recognize disk groups

when upgrading Data ONTAP ................................................................ 61

The fcp topology show command with the verbose or zoned option fails

on very large fabrics ................................................................................ 62

Data ONTAP-v platform issues ................................................................................ 62

MultiStore issues ....................................................................................................... 62

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

Changes to published documentation ....................................................... 63Changes to the Commands Manual Page Reference ................................................. 63


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

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

Managing anonymous FTP access requires additional step .......................... 64

Changes to the Software Setup Guide ....................................................................... 64

Configuring a node for non-HA (stand-alone) use ........................................ 64

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

Usable and physical disk capacity table incomplete ..................................... 66

Changes to the System Administration Guide .......................................................... 67

Changes to troubleshooting AutoSupport over SMTP .................................. 67

Changes to the V-Series Implementation Guide for Third-Party Storage ................ 67

Additional storage arrays, by storage array family ....................................... 68

Workaround for the unknown device (L254/SES) problem with 3PAR

storage arrays ........................................................................................... 68

Workaround when LUNs are not visible with Hitachi and HP XP

storage arrays ........................................................................................... 70

Changes to the V-Series Installation Requirements and Reference Guide ............... 71

Error in the usable space required in an array LUN for a core dump ........... 71

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

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

Copyright information ............................................................................... 73Trademark information ............................................................................. 74How to send your comments ...................................................................... 75

8 | Release Notes

Data ONTAP 8.2 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 release

Data ONTAP 8.2 is a major release, the first General Availability (GA) release in the Data ONTAP8.2.x release family. For more information about Data ONTAP releases, see the Data ONTAPRelease 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 11.

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

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 operating in 7-Mode for NetApp storage systems (FAS systems and V-Seriessystems), 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.

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

9

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

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

http://support.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml

http://support.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml

Unsupported features

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

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

Related information

NetApp Support Site: support.netapp.com

10 | Release Notes

http://support.netapp.com/

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 25. 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 supports new and changed hardware.

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

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.

11

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

https://kb.netapp.com/support/index?page=content&id=2017616


http://www.netapp.com/us/products/storage-systems/flash-cache/flash-cache-tech-specs.html

Support for 800-GB SSDs

In Data ONTAP 8.2 and later releases, 800-GB SSDs are supported for SSD-only aggregates andFlash Pool aggregate 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.

SAS optical cables not supported

SAS optical cables are not supported on storage systems running Data ONTAP 8.2.

If you have a storage system using SAS optical cables, you cannot upgrade the storage system toData ONTAP 8.2.

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

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 automatically has the standardlicense for the package that the previously licensed functionality is part of.

12 | Release Notes

https://hwu.netapp.com/


• 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. However, if you need to reinstall a license in Data ONTAP 8.2 (for example,you deleted a previously installed license and want to reinstall it in Data ONTAP 8.2, or youperform a controller replacement procedure for a system running Data ONTAP 8.2), DataONTAP 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.

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, within a grace period (upto 90 days) the new controller can use the same licensed functionality that the original controllerhad.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 and changed features in the Data ONTAP 8.2 release family for 7-Mode | 13


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. These changes do not apply to the RLM.

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)• 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-processor

image 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-processor

image update-progress show)

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

AutoSupport enhancements

Data ONTAP 8.2 supports several enhancements to the delivery of AutoSupport messages.

AutoSupport On Demand enhances delivery of AutoSupport messages

AutoSupport On Demand is a new AutoSupport feature that ensures technical support has the data itneeds to provide quick incident resolution and preventative support.

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.

14 | Release Notes

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

When sending connection requests to SMTP mail servers, AutoSupport now specifies the fullyqualified domain name of the node, if you configured DNS. In previous releases, AutoSupportspecified only the host name.

Enhancements to health monitoring

The node connectivity health monitor now monitors SMB connections to ensure non-disruptiveoperations 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 cf.mode option replaces the cf license

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

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

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.

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.

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.

16 | Release Notes


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.

Storage efficiency enhancementsThis Data ONTAP release includes a new enhancement for storage efficiency enhancements. Thissection provides an 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.

V-Series enhancementsThis Data ONTAP release includes a number of new features and enhancements for V-Seriessystems.

New licensing requirement for V-Series systems

The required license for V-Series systems to access LUNs on storage arrays has changed in DataONTAP 8.2.

Starting in Data ONTAP 8.2, the V_StorageAttach license package is required for V-Series systemsto be able to access LUNs on storage arrays. If this license is not installed, the system will rebootafter 72 hours.


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.

New storage arrays supported in Data ONTAP 8.2

Support for a number of new storage arrays was added in Data ONTAP 8.2.

V-Series added support for the following storage arrays in Data ONTAP 8.2:

• EMC Symmetrix storage arrays

• VMAX 40k• VMAX 20k (formerly VMAX)• VMAX 10k (formerly VMXe)

• Hitachi storage arrays

• HUS 110• HUS 130• HUS 150

• HP EVA storage arrays

• P6350• P6500• EVAx100

• IBM storage arrays

• DS8870• 3PAR storage arrays

• 3PAR StoreServ 7200• 3PAR StoreServ 7400

See the V-Series Implementation Guide for Third-Party Storage for information about parametersettings for these storage arrays to work with V-Series systems, supported configurations with thesestorage arrays, and so on.

Support added for one V-Series FC initiator connecting to multiple targetports

Starting in Data ONTAP 8.2, connecting a V-Series FC initiator port to up to four target ports onseparate storage arrays is supported. Connecting a V-Series FC initiator port to up to four target portson the same storage array is also supported; however, this configuration can be used only withstorage arrays whose LUN masking, presentation, or host group capability allows for different LUNgroup presentations to the same FC initiator based on the target port being accessed.

See the V-Series Installation Requirements and Reference Guide for the rules for implementing thistype of configuration. See your storage array documentation for information about whether your

18 | Release Notes

storage array would support a V-Series FC initiator connecting to multiple target ports on the samestorage array.

Increased LUN count per V-Series FC initiator

The number of array LUNs that can be visible over a V-Series FC initiator has been increased inData ONTAP 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 V-Series Best Practices Guide for information about theconsiderations for and number of array LUNs supported per initiator for Data ONTAP 8.2.

Support added for ALUA with EMC CLARiiON and VNX storage arrays

Starting in Data ONTAP 8.2, support has been added for ALUA (Asymmetric Logical Unit Access)with EMC CLARiiON and VNX arrays.

By default, support for ALUA is enabled in Data ONTAP; to use it, ALUA must be enabled on thestorage array. You should enable ALUA only on new configurations. You should not enable ALUAin an existing configuration.

See the V-Series Systems Implementation Guide for Third-Party Storage for more information.

Support added for native disks in a V-Series MetroCluster configuration

Starting in Data ONTAP 8.2, a V-Series MetroCluster configuration can include native disks.

Prior to Data ONTAP 8.2, a V-Series MetroCluster configuration could include only storage arrays.Starting in Data ONTAP 8.2, support for MetroCluster configurations with V-Series systems is asfollows:

• A MetroCluster configuration with V-Series systems can include native disks only, LUNs onstorage arrays only, or both.Setting up a MetroCluster configuration with V-Series systems requires FibreBridge 6500Nbridges and the native disks supported by this bridge. These requirements are the same for fabric-attached and stretch MetroCluster configurations.

• The V-Series systems must be 7-Mode systems (clustered Data ONTAP is not supported forMetroCluster configurations).

• The storage arrays and V-Series models must be identified in the Interoperability Matrix as beingsupported in MetroCluster configurations.

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

Enhancements for setting the target queue depth on a V-Series system

The default target queue depth increased in Data ONTAP 8.2.

For more information, see the V-Series Installation Requirements and Reference Guide.


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.

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 Data

20 | Release Notes


ONTAP 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.

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

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


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 install the SyncMirror license as it is enabled bydefault.

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.

22 | Release Notes

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 enhancementsSystems based on Data ONTAP-v technology, such as Data ONTAP Edge storage systems, can beinstalled with Data ONTAP 8.2 software.

Data ONTAP Edge and Data ONTAP Edge-T storage systems running Data ONTAP 8.2 softwaremust be installed using Data ONTAP-v Administration Tool (dvadmin) version 1.2.0 software.dvadmin is included on the Data ONTAP-v Installer virtual machine. You download the latest DataONTAP-v Installer 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.120), bothData ONTAP and dvadmin are provided at the required versions. (The installer version number8.2.120 means Data ONTAP version 8.2 and dvadmin version 1.2.0.)

When upgrading existing Data ONTAP Edge systems to Data ONTAP 8.2, you must upgrade theData ONTAP image to version 8.2 first. Then you upgrade dvadmin to version 1.2.0 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

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 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 commands such as disk show, aggr status -r, and sysconfig.

• Jumbo frames are now supported with Data ONTAP Edge systems. The selection of jumboframes is not available in the Data ONTAP Edge installation wizard, but you can make thischange after installation.

• 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 Data



ONTAP software. This does not affect the SnapVault technology support for Data ONTAP Edgesystems:

• Data ONTAP Edge can be configured as a SnapVault primary system only• Data ONTAP Edge-T can be configured as a SnapVault primary or SnapVault 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.0.

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

• A single instance of the dvadmin tool now can connect to a vCenter Server and manage multipleData ONTAP Edge storage systems instead of requiring one dvadmin instance for each DataONTAP Edge storage system. Note that each Data ONTAP Edge system must be on a separateESX host, and each ESX host must be connected to the same vCenter Server.

• A new host command has been added to move between hosts when you have multiple DataONTAP Edge storage systems being managed by a single instance of dvadmin through a vCenterServer. A host show command has also been added to show all the hosts on a vCenter Server.

• The standard Data ONTAP feature licenses required for a Data ONTAP Edge system now areinstalled automatically when the Data ONTAP Edge or Data ONTAP Edge-T system is installed.This includes the CIFS, NFS, iSCSI, FlexClone, SnapRestore, and SnapVault licenses. You donot need to download these licenses separately from the NetApp Support Site, and you do notneed to install them (using the Data ONTAP license add command) after installation.

Note: With Data ONTAP Edge-T systems, however, you must still enter the SnapMirrorlicense manually. This can be done within the installation steps in dvadmin so that the DataONTAP Edge-T system is completely configured upon the first boot.

• A new vm savecore command is available to save a Data ONTAP core dump to a file on thelocal system in cases where Data ONTAP has not saved the core dump to a core dump file.

• Six network ports (interfaces) are now created by default on the Data ONTAP Edge virtualmachine instead of four ports.

• A new virtual machine property (nodemgmt_interface) has been added so you can specify theinterface that will be used to manage the VM. For most installations the default setting ofinterface 1 (e0a) will work fine, however, you can select a number from 2 through 6 if you wantto manage the VM through a different interface.

• The vm disk reassign command has been replaced by the vm headswap command.• The minimum disk size for Data ONTAP Edge data disks now can be 1 GB in size instead of 2

GB in size.

24 | Release Notes

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.

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

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

For each command family and each command, the following table gives this 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

25

Command Purpose Documentation Release added

system node

service-processor

Manages the ServiceProcessor (SP):

• Setting up or modifyingthe SP networkconfiguration

• Displaying the SPnetwork configuration

• Displaying the SP deviceinformation

• Rebooting the SP andoptionally specifying theSP firmware image(primary or backup) touse

• Displaying the details ofthe SP firmware imagethat is currently installed

• Enabling or disabling theSP automatic firmwareupdate

• Manually updating the SPfirmware and specifyingthe update settings

• Displaying the status forthe latest SP firmwareupdate

man pages for systemnode service-

processor

8.2

vol autosize

grow_shrink

Supports the volumeautoshrink capability.

Data ONTAP StorageManagement Guide for 7-Mode

na_vol(1) man page

8.2

Changed commands in the Data ONTAP 8.2 releaseA 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

26 | 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.


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 | 27


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

28 | Release Notes


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


8.2

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


8.2

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


8.2

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

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

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

30 | Release Notes


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.


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.


na_vol(1) man page

8.2

Replaced or removed commands in the Data ONTAP 8.2release

You 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.

New options in the Data ONTAP 8.2 releaseThis 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

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

32 | Release Notes


Releaseadded

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

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



Releaseadded

snapvault.stale_config_cleanup_en

able

Enables or disables thecleanup of staleSnapVaultconfigurations.

on 8.2

licensed_feature.snaplock_enterpr

ise.enable

Enables the SnapLockEnterprise functionality.

off 8.2

licensed_feature.snaplock.enable Enables the SnapLockCompliancefunctionality.

off 8.2

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

off 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

34 | Release Notes

Option Change Releasechanged

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

8.2

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


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.

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

• 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• SA320• SA300

The following Data ONTAP-v systems are supported:

36 | Release Notes


• CBvM100 (Data ONTAP Edge)• FDvM100 (Data ONTAP Edge-T)

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.

Disk firmware

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

Requirements for running Data ONTAP 8.2 | 37


http://support.netapp.com/NOW/cgi-bin/fw

http://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.

V-Series interoperability and limits informationNot all Data ONTAP releases support the same features, configurations, storage system models, andstorage array models for V-Series systems. When planning your configuration, you need to checksources in addition to product documentation for interoperability details and limits information.

Previously, all support information used to set up deployments with storage arrays was included inthe V-Series Support Matrix, and array LUN-specific limits were also provided in the V-SeriesLimits Reference for Third-Party Storage and the V-Series Support Matrix. This information is nowdivided into two different tools that are the authoritative sources for this information, as shown in thefollowing 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

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

38 | Release Notes

http://support.netapp.com/NOW/download/tools/diskshelf/

http://support.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 and Data ONTAP Edge-T products). This is because ofdifferences when Data ONTAP is running in a virtual machine on a host system instead of runningon NetApp storage controllers.

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.

Requirements for running Data ONTAP 8.2 | 39

http://support.netapp.com/matrix

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.

Compatible versions of management software are required

After you upgrade to Data ONTAP 8.2, the license-list-info ZAPI is no longer supported. As a result,you must install Data ONTAP management software versions that are supported by Data ONTAP8.2.

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.

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

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.

40 | Release Notes


http://support.netapp.com/matrix

https://communities.netapp.com/community/interfaces_and_tools/developer/apidoc

https://communities.netapp.com/community/interfaces_and_tools/developer/apidoc

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 themoffline 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.

RAID disk timeout option not updated correctly after upgrade

In some cases, after upgrading to this version of Data ONTAP, the value of theraid.disk.timeout.enable option is not updated correctly. This increases exposure to

Important cautions | 41




application timeouts when one or more disks experience an extended-duration error recovery. Toavoid this issue, confirm the value of this hidden option after upgrading.

About this task

The following table shows the default value for this option by Data ONTAP version:

Data ONTAP version Value for raid.disk.timeout.enable option

7.3, 7.3.1 ata@jake,fc,ata@ario,sata,sas

7.3.2 and later versions in the 7.3 family ata@jake,fc,ata@ario,sata,sas,bsas

8.0 ata@jake,fc,ata@ario,sata,sas,bsas

8.0.1 ata@jake,fc,ata@ario,sata,sas,bsas,ssd

8.0.2 and later versions in the 8.0 family ata@jake,fc,ata@ario,sata,sas,bsas,ssd,fsas

8.1 ata@jake,fc,ata@ario,sata,sas,bsas,ssd,fsas

8.1.1 and later versions in the 8.1 family ata@jake,fc,ata@ario,sata,sas,bsas,ssd,fsas,msata

8.2 ata@jake,fc,ata@ario,sata,sas,bsas,ssd,fsas,msata

Steps

1. To confirm the value of this option, enter the following command:

options raid.disk.timeout.enable

2. If the value of this option is not as shown above for your (upgraded) version of Data ONTAP,update the option by entering the following command:

options raid.disk.timeout.enable value

Upgrade to Data ONTAP 8.2.x with deduplicated volumes can fail due toinsufficient space

In Data ONTAP 8.2.x releases, you must ensure that there is sufficient space on the aggregate and onthe volume to upgrade the deduplication metadata. You can use the df command to check the spaceavailable on the aggregate and on the volume.

Deduplication metadata can occupy up to 7 percent of the total physical data contained within thevolume, as follows:

• In an aggregate, deduplication metadata can occupy up to 3 percent of the total physical datacontained within the volume.

• In a volume, deduplication metadata can occupy up to 4 percent of the total amount of datacontained within the volume.

42 | Release Notes

In case of insufficient space, the upgrade will succeed but deduplication will be disabled on thevolume and no further deduplication will be carried out on the volume until you explicitly enablededuplication on the volume.

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

SAS optical cables not supported

SAS optical cables are not supported on storage systems running Data ONTAP 8.2.

If you have a storage system using SAS optical cables, you cannot upgrade the storage system toData ONTAP 8.2.

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, you must use the newlicense 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. However, if you need toreinstall a license when you are running Data ONTAP 8.2, the old key is not accepted.

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.



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)

44 | 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

Network protocol cautionsYou need to be aware of important cautions regarding network management.

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

System might panic if the network configuration entries in the /etc/rc fileare not in the recommended order

You should ensure that the entries in the /etc/rc file are in the recommended order. The incorrectorder can cause prolonged giveback or system reboot time, which might result in a system panic.

For more information about the ordering of entries in the /etc/rc file, see the Data ONTAP SystemAdministration Guide for 7-Mode.

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. Youshould follow standard best practices for spares when you upgrade, to ensure that sufficient sparesare 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.

Related information


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:

46 | Release Notes


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.

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.

Setup cautionsIf you are setting up a storage system for the first time, you should review the setup cautions.

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

CIFS setup overwrites the storage system password

The CIFS setup script resets the storage system password for the root account to match the localadministrator account password for CIFS.

CIFS setup requires a new root password. You can either specify a new password or reuse the samepassword by changing the password history settings. For more information, see the Data ONTAPSoftware Setup Guide for 7-Mode.


After you complete setting up CIFS, if you want to use a different password for the root account,follow the procedure for changing the storage system password in the Data ONTAP SystemAdministration Guide for 7-Mode.

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.

If you revert to a release earlier than Data ONTAP 8.2, you might need toinstall 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.

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 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 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 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 and

48 | Release Notes



the 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.

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.




http://support.netapp.com/NOW/download/tools/serviceimage/support/

http://support.netapp.com/NOW/download/tools/serviceimage/support/


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.

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

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 a

50 | Release Notes


successful 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• FlexClone LUNs• Virtual environments

If you are using one or more of these technologies with no fractional reserve, you need to preventerrors that can arise from running out of spaceand 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

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.

Known problems and limitations | 51

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.

Configuring ACP to use a different port on a FAS2240 system disables ACPfor the local SAS expander

If you configure ACP to use a different port than e0P (the default) on a FAS2240 system, the internalACPP module IOM6E becomes unresponsive, disabling ACP for the local SAS expander. Unlessyou are experiencing hardware issues on port e0P, always use the default port for ACP for theFAS2240 system.

Incorrect error message when FlexClone volume creation fails on a storagesystem that is halting

When you try creating a FlexClone volume on a storage system that is halting because of a reboot ora takeover, the clone creation operation might fail due to the unavailability of the license database.However, an incorrect error message is displayed: FlexClone not licensed.

The incorrect error message appears even if you have installed the FlexClone license. However, theparticular error message appears only when the first attempt at creating a FlexClone volume fails onthe storage system that is halting. Subsequent attempts at creating FlexClone volumes fail with thecorrect error message: License DB currently unavailable.

52 | Release Notes

Issues with V-Series systems working with LUNs fromstorage arrays

You should understand the known problems and limitations related to using V-Series systems withstorage arrays.

Some Hitachi and HP XP array LUNs might not be visible

If V-Series system system FC initiator ports are zoned with Hitachi and HP XP array target portsbefore the storage array parameters are set and the LUNs are mapped to the host groups, you mightnot be able to see any LUNs presented on Data ONTAP.

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 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 performing a path re-initialization to forcea rediscovery of the array LUNs that are mapped from a Hitachi or HP XP storage array. See Workaround when LUNs are not visible with Hitachi and HP XP storage arrays on page 70.

Some HP 3PAR array LUNs might be reported as unknown devices ifzoning is configured before setting the host persona

If V-Series system FC initiator ports are zoned with HP 3PAR array target ports before the correcthost persona is set on the 3PAR storage array, Data ONTAP reports some of the LUNs as unknowndevices. These LUNs cannot be assigned to the V-Series system.

Data ONTAP expects a Product ID of VV for array LUNs of 3PAR storage arrays. If zoning isconfigured before setting the host persona, the storage array might report a Product ID of SES andidentify a LUN as LUN 254. This results in some LUNs being reported as unknown devices.

In this situation, Data ONTAP generates the following EMS message:mlm.array.unknown:warning - Array LUN XXXXXXXX.126L254 [S/N 'XXXXXXX'

vendor '3PARdata' product 'SES'] is unknown and is not supported in this

version of Data ONTAP


Workaround

If zoning was configured before the host definition, you can resolve the LUN 254 unknown deviceproblem by doing path re-initialization to force a rediscovery of the array LUNs that are mappedfrom a 3PAR storage array. See Workaround for the unknown device (L254) problem with 3PARstorage arrays on page 68.

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

Related information


LUNs from a host group with fewer than 16 array LUNs are not visible onsome Hitachi and HP storage arrays

Starting in Data ONTAP 8.2, Data ONTAP verifies that the REPORT LUNs response data contentsmatches the number bytes transferred by the device. A mismatch in the number of bytes transferredmight occur with Hitachi 9970, VSP, USP-V, and HP 9500 storage arrays when fewer than 16 LUNsare visible in a host group.

This mismatch of transferred data to response data contents prevents the LUNs from being visible toData ONTAP when fewer than 16 LUNs are visible in the host group.

When this situation occurs, Data ONTAP generates the following EMS message:[localhost:mlm.bad.topology.data:CRITICAL]: The device with wwnn

50060e8005430771 and wwpn 50060e8005430771 is reporting inconsistent

"REPORT LUNS" data.

The workaround for this problem is to create a least 16 LUNs in each host group. For moreinformation about this issue, see Bug 705779 in Bugs Online.

Related information


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

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

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 the

54 | Release Notes



destination 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.


Related information


Partner node might be unavailable during controller failover when aninterface name is used as a host name alias in the /etc/hosts file

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, resulting in unavailability of the partnernode during takeover.

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

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



http://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 scenarios to avoid issues such as performance degradation or failed software upgrade.

About this task

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

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.

Windows Security tab unavailable for shares with long UNC paths

If the UNC path (\\servername\sharename\filepath) of the share contains more than 256characters (excluding the initial “\\” in the UNC path), then the Security tab in the WindowsProperties box is unavailable. This is a Windows client issue rather than a Data ONTAP issue.

To avoid this issue, do not create shares with UNC paths with more than 256 characters.

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.

56 | Release Notes


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.


Related information


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.

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.

Effective style of qtrees created on an NTFS volume before configuringCIFS

On a newly installed storage controller without CIFS configured, if you create a qtree on a volumethat has security style set to NTFS, the resulting qtree has NTFS as the security style and UNIX asthe effective style. This means that UNIX clients can set attributes on the NTFS volumes, whichnormally would not be allowed.

The effective style of these qtrees does not change even after CIFS is configured for NTFS only. Youmust avoid setting the security style of a volume to NTFS before configuring CIFS on a newlyinstalled storage system.

58 | Release Notes

http://support.microsoft.com/kb/2703610

http://support.microsoft.com/kb/2821663

You can change the effective style of a qtree to NTFS by using the following command:

qtree security qtree path ntfs

For more information about this issue, see bug ID 509178 in Bugs Online. For more informationabout setting the security styles for qtrees, see the Data ONTAP File Access and ProtocolsManagement Guide for 7-Mode.

Related information

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

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

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

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 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.

60 | Release Notes

SnapVault cannot be enabled on vFiler units when relationships arepresent in vfiler0

When you create in vfiler0, you also manually set the snapvault.lockvault_log_volume optionto the name of a log volume. After this option is set, SnapVault cannot be enabled on any vFiler unitson the storage system. For more information about the snapvault.lockvault_log_volumeoption, 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.

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 and 8.1.1, 8.2.0 or later releases, some Oracle Linux-basedsystems using ASMlib can fail to recognize disk groups.

This problem is due to a change made in Data ONTAP's 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 below:

ASM_DISKSTRING = '/dev/oracleasm/disks/*'




• NetApp recommends using the "lun set" command to disable the report-physical-sizeoption for the affected LUNs. For more information about the report-physical-size option,see the man page for the lun set command.

The fcp topology show command with the verbose or zoned option fails onvery large fabrics

Running the fcp topology show -v|z command on a target port connected to a very large fabricmight return a none connected message.

This message incorrectly indicates that there is no fabric connected to that port.

As a workaround, you can run the fcp topology show command without the verbose or zonedoptions. This returns concise output only.

More detailed fabric information can be obtained from the fabric switches.

Data ONTAP-v platform issuesThere are certain issues and restrictions you should be aware of when using products based on theData ONTAP-v platform. This includes the Data ONTAP Edge and Data ONTAP Edge-T products.

The Data ONTAP-v storage software running on a virtual machine does not support all thefunctionality of Data ONTAP compared to when it is running on a hardware controller. See the "DataONTAP-v supported and unsupported functionality" section in the Data ONTAP Edge Installationand Administration Guide for more information.

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.

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.

62 | 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 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

ldap.fast_timeout.enabl

e

Controls the timeout behaviorof LDAP client operations

on

ldap.retry_delay Sets the time, in seconds, towait before trying to connect toLDAP servers after a failedattempt

120

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.

63

Changes to the File Access and Protocols ManagementGuide

New information has become available since the previous revision of the Data ONTAP File Accessand Protocols Management Guide for 7-Mode.

Managing anonymous FTP access requires additional step

The instructions for managing anonymous FTP access in the Data ONTAP File Access and ProtocolsManagement Guide for 7-Mode require an additional step to authenticate the anonymous user.

To allow FTP access by the anonymous user, you must also add an entry for the anonymous user tothe /etc/passwd file.

Example:

ftp::14:5:Anonymous FTP:/ftp:

The password field for this entry must be empty.

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

Changes to the Software Setup GuideAdditional information has become available since the last revision of the Data ONTAP SoftwareSetup Guide for 7-Mode.

Configuring a node for non-HA (stand-alone) use

By default, storage controllers are configured for use in HA mode. To use a controller in stand-alonemode, you must change the node to non-HA mode.

Before you begin

You must determine the current configuration of the storage controller because the HA mode statecan vary. You can use the cf status command to determine the current configuration.

The HA Configuration Checker has been replaced with the Config Advisor Tool. Config Advisor is aconfiguration validation and health check tool for NetApp systems. Support for Config Advisor islimited, and available only online.

64 | Release Notes

About this task

When a storage controller is shipped from the factory or when Data ONTAP is reinstalled usingoption four of the Data ONTAP boot menu (Clean configuration and initialize alldisks), HA mode is enabled by default, and the system's nonvolatile memory (NVRAM orNVMEM) is split. If you plan to use the controller in standalone mode, you must configure the nodeas non-HA. Reconfiguring the node as non-HA mode enables full use of the system's nonvolatilememory.

Note: Configuring the node as standalone removes the availability benefits of the HAconfiguration and creates a single point of failure.

For information on using the boot menu to manage the storage system, see the Data ONTAP SystemAdministration Guide for 7-Mode.

Choices

• If the cf status output displays Non-HA mode, then the node is configured for non-HA modeand you are finished:

Example

node > cf statusNon-HA mode.

• If the cf status output directs you to reboot, you must reboot the node to enable full use of thesystem's nonvolatile memory:

Example

node> cf statusNon-HA mode. Reboot to use full NVRAM.

a) Reboot the node using the following command:

node> reboot

After the node reboots, you are finished.• If the cf status output displays Controller Failover enabled, you must disable both

controller failover and HA mode and then reboot the node to enable full use of the system'snonvolatile memory:

Example

node> cf statusController Failover enabled

a) Disable controller failover using the following command:

Changes to published documentation | 65

node> cf disable

b) Set the mode to non-HA by using the following command:

node> options cf.mode non_ha

c) Reboot the node by using the following command:

node> reboot

After the node reboots, you are finished.• If the cf status output displays Controller Failover disabled, then the HA mode is

still enabled, so you must set the HA mode to non-HA and reboot the node to enable full use ofthe system's nonvolatile memory:

Example

node> cf statusController Failover disabled

a) Set the mode to non-HA by using the following command:

node> options cf.mode non_ha

b) Reboot the node by using the following command:

node> reboot

After the node reboots, you are finished.

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.

Usable and physical disk capacity by disk size

The values for the multi-drive carrier 3-TB and 4-TB drives are missing.

The following table lists the approximate physical and usable capacities for the disk sizes currentlysupported by Data ONTAP. The numbers shown are in Mebibytes (MiBs). This unit of measure isequivalent to 2 to the 20th power bytes. (MBs, in contrast, are 10 to the sixth power bytes.)

The physical capacities listed in the table are approximations; actual physical disk capacities vary bymanufacturer. The technical documentation for your disks contains the exact physical disk capacities.

Disk size as described bymanufacturer

Physical capacity (MiBs,approximate)

Usable capacity (MiBs)

300 GB Performance 280,104 272,000

66 | Release Notes

Disk size as described bymanufacturer

Physical capacity (MiBs,approximate)

Usable capacity (MiBs)

450 GB Performance 420,156 418,000

500 GB Capacity 423,946 423,111

600 GB Performance 560,208 560,000

900 GB Performance 858,483 857,000

1.2 TB Performance 1,144,641 1,142,352

1 TB Capacity 847,884 847,555

2 TB Capacity 1,695,702 1,695,466

3 TB Capacity ( X308A, single-drive carrier)

2,543,634 2,538,546

3 TB Capacity ( X478A, multi-drive carrier)

2,891,588 2,811,241

4 TB Capacity (X477A, single-drive carrier)

3,815,447 3,807,816

4 TB Capacity (X480A, multi-drive carrier)

3,815,447 3,748,319

Changes to the System Administration GuideAdditional information has become available since the last revision of the Data ONTAP SystemAdministration Guide for 7-Mode.

Changes to troubleshooting AutoSupport over SMTP

In the topic titled “Troubleshooting AutoSupport over SMTP,” the information about using the

dns info

command should say that you use it to enable and configure the storage system.

Changes to the V-Series Implementation Guide for Third-Party Storage

Additional information has become available since the last revision of the V-Series ImplementationGuide for Third-Party Storage.


Additional storage arrays, by storage array family

In the V-Series Implementation Guide for Third-Party Storage, some supported storage arrays are notlisted because the information was not available at the time of publication.

Change to the HP EVA storage array families topic

The HP EVAx100 storage array should be included in the HP EVA storage array families topic.

Family 2 should read as follows:

• EVA 4100• EVA 6100• EVA 8100• HP EVAx100

Change to the IBM storage array families topic

The DS8870 storage array should be included in the Family 5 list.


• DS8800 model 951• DS8700 models 941, 94E• DS8870

There is no Family 6.

Change to the 3PAR storage array families topic

The 3PAR StoreServ 7200 and 3PAR StoreServe 7400 storage arrays should be included in the3PAR storage array families topic.


• P10000 - V400• P10000 - V800• 3PAR StoreServ 7200• 3PAR StoreServe 7400

Workaround for the unknown device (L254/SES) problem with 3PARstorage arrays

The host definition, with the host persona specified in the V-Series Implementation Guide for Third-Party Storage, should be created on a 3PAR storage array before the switch is zoned to connect theV-Series system to a 3PAR storage array. If zoning is configured before the host definition, Data

68 | Release Notes

ONTAP discovers a 3PAR array LUN as LUN 254 and product type SES, which Data ONTAPcannot use.

When Data ONTAP discovers 3PAR array LUNs as LUN 254 and product type SES, newly mapped3PAR LUNs cannot be assigned to V-Series systems and some 3PAR LUNs that might have alreadybeen added to an aggregate cannot be used because Data ONTAP sees a LUN 254. Data ONTAPgenerates EMS messages for the LUN it discovered as LUN 254 and product type SES, reportingsome LUNs as unknown devices.

If zoning was configured before the host definition, you can resolve the LUN 254/SES unknowndevice problem by forcing a rediscovery of the array LUNs that are mapped from a 3PAR storagearray. The procedure you use depends on whether aggregates with 3PAR array LUNs have alreadybeen configured on the V-Series system. (In the following procedures, assume that Node-1 andNode-2 are the names of the V-Series nodes.)

If aggregates with 3PAR array LUNs were already created on a 7-Mode V-Seriessystem

1. Run the following command to ensure that HA configuration is enabled on your V-Seriessystems:

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 3PAR array LUNs have not been created on a 7-Mode V-Seriessystem

1. Run the following command to list all of the V-Series FC initiator ports that are connected to the3PAR storage array:

sysconfig -v

2. Run the following command to take all of 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 of the listed ports online:

priv set advanced;fcadmin online <adapter>

For example:

priv set advanced;fcadmin online 0a

Workaround when LUNs are not visible with Hitachi and HP XP storagearrays

The storage array parameters specified in the V-Series Implementation Guide for Third-Party Storageshould be set and LUNs should be mapped to the host groups before the switch is zoned to connectthe V-Series system to a Hitachi or HP XP storage array.

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 V-Series system. (In the following procedures, assume that Node-1and Node-2 are the names of the V-Series nodes.)

If aggregates with Hitachi or HP XP array LUNs were already created on a 7-Mode V-Series system

1. Run the following command to ensure that HA configuration is enabled on your V-Seriessystems:

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

70 | Release Notes

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-Mode V-Series system

1. Run the following command to list all the V-Series FC initiator ports that are connected to theHitachi or HP XP storage array:

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 V-Series Installation Requirements andReference Guide

New information has become available since the last revision of the V-Series InstallationRequirements and Reference Guide.

Error in the usable space required in an array LUN for a core dump

For array LUNs less than or equal to 2 TiB, the usable space required for a core dump is 1%.

The topic “Elements that reduce the usable space in an array LUN” in the V-Series InstallationRequirements and Reference Guide shows the required space as 0.1%. This is not correct. Therequired space for a core dump for array LUNs less than or equal to 2 TiB is 1%.


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

Searching online informationThe 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• Documentation, including product documentation, 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.

72 | Release Notes



http://support.netapp.com/knowledge/docs/docs.shtml

http://www.netapp.com/library


https://support.netapp.com/documentation/productsatoz/index.html

Copyright information

Copyright © 1994–2013 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).

73

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, ComplianceClock, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, DataONTAP, DataFabric, DataFort, Decru, Decru DataFort, DenseStak, Engenio, Engenio logo, E-Stack,ExpressPod, FAServer, FastStak, FilerView, Flash Accel, Flash Cache, Flash Pool, FlashRay,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol, FPolicy, GetSuccessful,gFiler, Go further, faster, Imagine Virtually Anything, Lifetime Key Management, LockVault, Mars,Manage ONTAP, MetroCluster, MultiStore, NearStore, NetCache, NOW (NetApp on the Web),Onaro, OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX, SANscreen,SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service Builder, Shadow Tape,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.

74 | Release Notes

http://www.ibm.com/legal/copytrade.shtml

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 [email protected]. 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

75

mailto:[email protected]

Data ONTAP 8.2 Release Notes for 7Mode

Documents

Transcript of Data ONTAP 8.2 Release Notes for 7Mode