Data ONTAP 8.2 Release Notes For 7mode

Data ONTAP
8.2
Release Notes
For 7-Mode
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
Web: www.netapp.com
Feedback: doccomments@netapp.com
Part number: 215-07974_A0 ur004
September 2013
Contents
Data ONTAP 8.2 Release Notes for 7-Mode .............................................. 9
Unsupported features ................................................................................. 10
New and changed features in the Data ONTAP 8.2 release family for
7-Mode .................................................................................................... 11
New 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 Data
ONTAP 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 ........................................... 36
Supported 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 ..................................................................................... 40
Upgrade 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 .............................................................. 50
Manageability 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 ....................................................... 63
Changes 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 .............. 72
Searching online information .................................................................................... 72
Finding documentation on the NetApp Support Site ................................................ 72
Copyright information ............................................................................... 73
Trademark information ............................................................................. 74
How 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 as
additional 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 ONTAP
8.2.x release family. For more information about Data ONTAP releases, see the Data ONTAP
Release Model on the NetApp Support Site.
If you are upgrading to this Data ONTAP release or reverting from this release to an earlier release,
see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.
Attention: If you have a 3210 or 3140 storage system with Flash Cache modules installed, do not
upgrade to Data ONTAP 8.2 for 7-Mode. Flash Cache modules are not supported on 3210 or 3140
systems running Data ONTAP 8.2 for 7-Mode.
For a complete list of functionality changes introduced in this release, see New and Changed features
in 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 Data
ONTAP 8.2.x releases operating in 7-Mode for NetApp storage systems (FAS systems and V-Series
systems), unless noted.
It is a best practice for all Data ONTAP users to review these release notes.
If Data ONTAP is already running on storage systems in your environment, you should
familiarize 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, you
should also refer to the Data ONTAP Information Library page for this release on the NetApp
Support Site.
For more information about all Data ONTAP releases, see the Data ONTAP Release Model on
the NetApp Support Site.
Related information
Data ONTAP Release Model: support.netapp.com/NOW/products/ontap_releasemodel/
post70.shtml
Data ONTAP Information Library page: support.netapp.com/NOW/knowledge/docs/ontap/
ontap_index.shtml
9
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
New and changed features in the Data ONTAP 8.2
release family for 7-Mode
A number of new features and enhancements have been introduced in the Data ONTAP 8.2 release
family.
Some enhancements in this release might also be introduced in a maintenance release of an earlier
Data ONTAP release family. Before upgrading, be sure to consult with your NetApp representative
about new Data ONTAP functionality to determine the best solution for your business needs.
Additional changes are described here. For other important information about changes to the product
made by these releases, see the release notes topic Summary of new and changed commands and
options in the Data ONTAP 8.2 release family operating in 7-Mode on page 25. For managing and
resolving bug issues, you can use the Bugs Online suite of tools; for more information, see Bugs
Online on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.
New and changed platform and hardware support
This Data ONTAP release supports new and changed hardware.
For information about the supported systems in Data ONTAP 8.2 for 7-Mode, see Supported systems
on page 36. For information about the unsupported systems in Data ONTAP 8.2, see Unsupported
systems 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 and
later 8.2.x releases operating in 7-Mode. You cannot upgrade to Data ONTAP 8.2 or later 8.2.x
releases 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 Cache
2 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
Support for 800-GB SSDs
In Data ONTAP 8.2 and later releases, 800-GB SSDs are supported for SSD-only aggregates and
Flash Pool aggregate aggregates.
For information about which platforms and shelf types support these drives and aggregate types, see
the 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 to
Data ONTAP 8.2.
Manageability enhancements
This 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 your
storage 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 or
a single feature. A package requires a license key, and installing the key enables you to access all
features in the package. For example, installing the key for the SnapManager Suite package on a
system entitles the system to use all SnapManager products in the package. For information about
the features that require licenses in the Data ONTAP 8.2 release family, see the knowledgebase
article 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 license
package; 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 with
a 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 a
standard license. Therefore, a system running Data ONTAP 8.2 automatically has the standard
license for the package that the previously licensed functionality is part of.
12 | Release Notes
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 to
Data 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 you
perform a controller replacement procedure for a system running Data ONTAP 8.2), Data
ONTAP requires that you enter the license key in the new, 28-character format.
You can find license keys for your initial or add-on software orders at the NetApp Support Site
under My Support > Software Licenses. For instance, you can search with the serial number of
a system to find all license keys associated with the system. If you cannot locate your license keys
from 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 Data
ONTAP 8.2, you need to use a license key format that is supported for the release that you are
installing. 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 you
might need to enable certain options before using it:
High-availability (HA) configurations
You must set options cf.mode to ha.
MetroCluster
You must enable options cf.remote_syncmirror.enable and set options cf.mode
to ha.
SyncMirror
There 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 (up
to 90 days) the new controller can use the same licensed functionality that the original controller
had.
During the grace period, you should contact your sales representative to obtain a proper license
key to install on the new controller.
During the grace period when the first valid license key is installed, you have 24 hours to
complete license installation for all packages that you want the new controller to use. The grace
period ends after the 24-hour period, and all previously installed licenses that were associated
with 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 Guide
for 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 available
for managing the Service Processor (SP) from Data ONTAP. The sp and software install
commands 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 following
tasks:
Set up or modify the SP network configuration (system node service-processor
network 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 it
needs to provide quick incident resolution and preventative support.
AutoSupport On Demand periodically sends HTTPS requests to technical support to obtain delivery
instructions. The delivery instructions can include requests to generate new AutoSupport messages,
retransmit previously generated messages, and disable delivery of messages for specific trigger
events. 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 technical
support if AutoSupport is configured to send messages to technical support and the transport protocol
is HTTPS.
For more information about AutoSupport On Demand, see the Data ONTAP System Administration
Guide 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 fully
qualified domain name of the node, if you configured DNS. In previous releases, AutoSupport
specified only the host name.
Enhancements to health monitoring
The node connectivity health monitor now monitors SMB connections to ensure non-disruptive
operations to Hyper-V applications.
For more information about health monitoring, see the Data ONTAP System Administration Guide
for 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 system
name. This change helps administrators of multiple systems see which system a given message came
from.
Options for specifying uppercase and lowercase requirements in user
passwords
Starting with Data ONTAP 8.2, you can specify the minimum number of uppercase or lowercase
alphabetic characters that a password must contain.
You can use the following options to specify the requirements of uppercase or lowercase alphabetic
characters in user passwords:
The security.passwd.rules.minimum.uppercase option specifies the minimum number
of 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 number
of 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 enhancements
This 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 enhancements
This Data ONTAP release includes a number of enhancements for performance, resiliency, and
management 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 more
information, see the Hardware Universe at hwu.netapp.com.
Flash Pool aggregates support different RAID types and group sizes for
SSD cache
For earlier versions of Data ONTAP, the SSD cache always had the same RAID type and RAID
group size as the HDD RAID groups. Starting in Data ONTAP 8.2, the SSD cache RAID type and
RAID group size can be configured differently from the HDD RAID groups.
Flexibility for calculating maximum Flash Pool SSD cache size in HA
configurations
There is a platform-dependent maximum size for the Flash Pool SSD cache. Starting in Data ONTAP
8.2, the cache-size limits apply to the HA configuration as a whole, and can be split arbitrarily
between 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 applied
individually to both nodes in an HA configuration.
For more information about how Flash Pool cache capacity is calculated, see the Data ONTAP
Storage 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 and
cannot be disabled.
You can control how many aggregate Snapshot copies are preserved by adjusting the size of the
aggregate Snapshot reserve. By default, the aggregate Snapshot reserve is set to 0 percent for newly
created 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 longer
automatically reenables the guarantee for volumes with disabled guarantees. This gives the
administrator control over when a volume with a disabled guarantee consumes space to enable its
guarantee.
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 FlexVol
volume to any value, from 0 to 100. Starting with Data ONTAP 8.2, the fractional reserve setting can
be set only to 0 or 100.
If you upgrade a system to Data ONTAP 8.2 with volumes whose fractional reserve settings are
between 1 and 99, the fractional reserve setting for those volumes is set to 0.
Storage efficiency enhancements
This Data ONTAP release includes a new enhancement for storage efficiency enhancements. This
section 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 can
check if a compression group within a file is incompressible. Incompressible data detection saves the
system resources used by inline compression to compress incompressible data.
For more information about incompressible data detection, see the Data ONTAP Storage
Management Guide for 7-Mode.
V-Series enhancements
This Data ONTAP release includes a number of new features and enhancements for V-Series
systems.
New licensing requirement for V-Series systems
The required license for V-Series systems to access LUNs on storage arrays has changed in Data
ONTAP 8.2.
Starting in Data ONTAP 8.2, the V_StorageAttach license package is required for V-Series systems
to be able to access LUNs on storage arrays. If this license is not installed, the system will reboot
after 72 hours.
For V-Series systems upgraded from previous Data ONTAP 8.x releases to 8.2, the license is
automatically 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 parameter
settings for these storage arrays to work with V-Series systems, supported configurations with these
storage arrays, and so on.
Support added for one V-Series FC initiator connecting to multiple target
ports
Starting in Data ONTAP 8.2, connecting a V-Series FC initiator port to up to four target ports on
separate storage arrays is supported. Connecting a V-Series FC initiator port to up to four target ports
on the same storage array is also supported; however, this configuration can be used only with
storage arrays whose LUN masking, presentation, or host group capability allows for different LUN
group 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 this
type 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 same
storage 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 in
Data ONTAP 8.2.
There are limits on how many array LUNs can be visible over an FC initiator port. These limits vary
in different Data ONTAP releases. See the V-Series Best Practices Guide for information about the
considerations 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 the
storage array. You should enable ALUA only on new configurations. You should not enable ALUA
in 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 as
follows:
A MetroCluster configuration with V-Series systems can include native disks only, LUNs on
storage arrays only, or both.
Setting up a MetroCluster configuration with V-Series systems requires FibreBridge 6500N
bridges 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 for
MetroCluster configurations).
The storage arrays and V-Series models must be identified in the Interoperability Matrix as being
supported in MetroCluster configurations.
For more information, see the Data ONTAP High Availability and MetroCluster Configuration
Guide 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-Party
Storage and before that in the V-Series Support Matrix. As of April 2013, the array LUN limits
information is in the Hardware Universe at hwu.netapp.com, along with other limits information for
systems running Data ONTAP. The array LUN specific limits information in the Hardware Universe
includes maximum array LUN sizes for data LUNs, minimum array LUN sizes for spare core LUNs
and the LUN used for the root volume, and more.
The Hardware Universe is the authoritative source for array LUN limits information for all Data
ONTAP releases starting from 7.2. As such, the V-Series Limits Reference for Third-Party Storage is
no longer being provided on the NetApp Support Site.
File access protocol enhancements
This Data ONTAP release includes a number of new features and enhancements for file access and
protocols management.
For detailed information about these features, see the Data ONTAP File Access and Protocols
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 add
significantly 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 CIFS
workgroup 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 File
Access 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 to
unresponsive 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 successful
connect and bind is used by the storage system. By default, if the LDAP server becomes
unresponsive, LDAP requests fails after the bind timeout. The default is a timeout of 30 seconds with
three retries. If the ldap.fast_time_out.enable option is on and an LDAP request times out, all
requests 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 NFS
clients.
Two new options are available to manage the timeout settings. Both options take effect immediately
and are persistent across reboots.
ldap.fast_timeout.enable
This option controls the timeout behavior of LDAP client operations. If enabled, after a failure
occurs, the storage system does not retry connections to the failed LDAP server. The storage
system waits for the number of seconds configured by the ldap.retry_delay option before
making 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 through
3600. The default value for this option is 120.
For information about managing LDAP servers, see the Data ONTAP File Access and Protocols
Enabling new EMS messages to help troubleshoot Kerberos issues
New EMS messages have been added to Data ONTAP to help troubleshoot Kerberos authentication
and 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 following
command:
options nfs.rpcsec.trace off
Data protection enhancements
This release of Data ONTAP provides new data protection features and enhancements.
For more information about the new features and enhancements, see the Data ONTAP Data
Protection Tape Backup and Recovery Guide for 7-Mode and the Data ONTAP Data Protection
Online 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. If
one path fails, then the storage system can use the other paths to access tape drives without having to
immediately 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 Tape
Backup 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 and
SnapVault secondary. You must use the same SnapVault license to enable both the SnapVault
primary 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 by
default.
Options for enabling the SnapLock functionality
Starting with Data ONTAP 8.2, in addition to installing the license key for the SnapLock
functionality, you need to enable the functionality by using the options
licensed_feature.snaplock_enterprise for SnapLock Enterprise or options
licensed_feature.snaplock for SnapLock Compliance.
For more information about enabling the SnapLock functionality, see the Data ONTAP Archive and
Compliance 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 and
perform a SnapMirror transfer, the size of the SnapMirror destination FlexVol volume automatically
increases to that of the SnapMirror source FlexVol volume.
For information about resizing the SnapMirror source and destination volume pair for a FlexVol
volume, see the Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.
Users cannot perform certain Qtree SnapMirror and SnapVault tasks during
the 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 and
qtrees are deleted. During this time, users will not be able to perform any tasks on uninitialized
relationships and qtrees, or on volumes containing these qtrees.
When the post-upgrade operations are complete, the message Post-upgrade operations for
Qtree SnapMirror and SnapVault are complete is displayed.
Note: Users must not take any volumes offline before or after the upgrade until the post-upgrade
operations 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 Data
ONTAP 8.2, Data ONTAP generates aliases based on SN instead of the WWN. The alias remains the
same regardless of the multiple connections paths to the tape drive or medium changer. This helps
storage 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 and
Recovery Guide for 7-Mode
Data ONTAP Edge enhancements
Systems based on Data ONTAP-v technology, such as Data ONTAP Edge storage systems, can be
installed with Data ONTAP 8.2 software.
Data ONTAP Edge and Data ONTAP Edge-T storage systems running Data ONTAP 8.2 software
must 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 Data
ONTAP-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), both
Data ONTAP and dvadmin are provided at the required versions. (The installer version number
8.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 the
Data ONTAP image to version 8.2 first. Then you upgrade dvadmin to version 1.2.0 using the Data
ONTAP-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 Data
ONTAP 8.2.0 software:
When using Data ONTAP Edge systems, the four port numbers for direct-attached SAS disks
have changed from using 0a.n through 0d.n to using 0b.n through 0e.n. This difference appears in
the 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 jumbo
frames is not available in the Data ONTAP Edge installation wizard, but you can make this
change after installation.
Data ONTAP 8.2 provides only a single SnapVault license instead of providing a separate license
for 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 Edge
systems:
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. In
addition, 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 multiple
Data ONTAP Edge storage systems instead of requiring one dvadmin instance for each Data
ONTAP Edge storage system. Note that each Data ONTAP Edge system must be on a separate
ESX 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 Data
ONTAP Edge storage systems being managed by a single instance of dvadmin through a vCenter
Server. 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 are
installed 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 do
not need to download these licenses separately from the NetApp Support Site, and you do not
need 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 SnapMirror
license manually. This can be done within the installation steps in dvadmin so that the Data
ONTAP 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 the
local 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 virtual
machine instead of four ports.
A new virtual machine property (nodemgmt_interface) has been added so you can specify the
interface that will be used to manage the VM. For most installations the default setting of
interface 1 (e0a) will work fine, however, you can select a number from 2 through 6 if you want
to 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 and
options in the Data ONTAP 8.2 release family
operating in 7-Mode
You need to know information about the commands, options, and configuration files that have been
added to the Data ONTAP 8.2 release family.
These listings are not exhaustive. For detailed information about specific commands and options, see
the corresponding man pages.
New commands in the Data ONTAP 8.2 release
Many 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 about
installed licenses; replaces
the license command.
Data ONTAP System
Administration Guide for
7-Mode
na_license(1) man page
8.2
nfs vstorage
stats
Displays various counters
about VMware vStorage over
NFS activity on the storage
system.
Data ONTAP File Access
and Protocols
Management Guide for 7-
Mode
8.2
rlm update-status Displays the RLM update
progress.
na_rlm(1) man page 8.2
system health
subsystem show
Displays the health status of
subsystems.
system_health_subsyste
m(1) man page
8.2
25
Command Purpose Documentation Release added
system node
service-processor
Manages the Service
Processor (SP):
Setting up or modifying
the SP network
configuration
Displaying the SP
network configuration
Displaying the SP device
information
Rebooting the SP and
optionally specifying the
SP firmware image
(primary or backup) to
use
Displaying the details of
the SP firmware image
that is currently installed
Enabling or disabling the
SP automatic firmware
update
Manually updating the SP
firmware and specifying
the update settings
Displaying the status for
the latest SP firmware
update
man pages for system
node service-
processor
8.2
vol autosize
grow_shrink
Supports the volume
autoshrink capability.
Data ONTAP Storage
Management Guide for 7-
Mode
na_vol(1) man page
8.2
Changed commands in the Data ONTAP 8.2 release
A 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 command
changed in
aggr create The -p option was
added to support
specifying the pool
from which the
aggregate is to be
created.
na_aggr(1) man page 8.2
aggr options The -T option was
added to support
changing the RAID
type of a Flash Pool
tier.
Data ONTAP Storage
Management Guide for
7-Mode
na_aggr(1) man page
8.2
aggr status The -S option was
added. This option
displays detailed
information about how
space is used in the
aggregate.
Data ONTAP Storage
7-Mode
na_aggr(1) man page
8.2
autosupport
history show
The -generated-on
option has been added.
This option displays
AutoSupport messages
that were generated at
a particular time.
na_autosupport(1) man
page
8.2
df Aggregate Snapshot
spill, or the amount of
space that aggregate
Snapshot copies are
taking beyond the
aggregate Snapshot
reserve, is now shown
as free space.
Previously, it was
shown as used by the
aggregate. With this
change, the outputs of
the df and aggr
status -S commands
are consistent.
na_df(1) man page 8.2
Summary of new and changed commands and options in the Data ONTAP 8.2 release family operating
in 7-Mode | 27
changed in
license Deprecated and
replaced by the
license show
command.
na_license(1) man
page
8.2
license add Accepts a list of 28
digit upper-case
alphanumeric character
keys.
Data ONTAP System
Administration Guide
for 7-Mode
na_license(1) man
page
8.2
license delete Requires the package
name when you delete
a license; requires
confirmation to delete.
Data ONTAP System
Administration Guide
for 7-Mode
na_license(1) man
page
8.2
reallocate start The -u option has been
added. This option
duplicates blocks that
are shared between
files by deduplication.
na_reallocate(1) man
page
8.2
revert_to The -d option has been
added. This option
enables the
administrator to
proceed with reverting
Data ONTAP after the
backlog of
asynchronous delete
operations is
completed.
na_revert_to(1) man
page
8.2
sis config The -Q option has been
added. This option
enables the
administrator to enable
or disable
incompressible data
detection on a volume.
Data ONTAP Storage
7-Mode
na_sis(1) man page
8.2
28 | Release Notes
changed in
sis config The -z option has been
added. This option
enables the
administrator to
specify the minimum
file size to attempt
quick check on a file.
Data ONTAP Storage
7-Mode
na_sis(1) man page
8.2
sis start The -m option has been
added. This option
enables the
administrator to scan
existing data, generate
deduplication
metadata, and skip
shared blocks.
Data ONTAP Storage
7-Mode
na_sis(1) man page
8.2
sis start The -o option has been
added. This option
enables the
administrator to scan
existing data and skip
shared block
optimization.
Data ONTAP Storage
7-Mode
na_sis(1) man page
8.2
software install The software
install command is
replaced by the
system node
service-processor
image update
command for manually
updating the SP
firmware.
Note: The
software
install command
continues to support
the RLM firmware
update.
The man page for
system node
service-processor
image update
8.2
in 7-Mode | 29
changed in
sp This command family
has been deprecated in
favor of the system
node service-
processor command
family.
The man pages for
system node
service-processor
8.2
sysconfig The Preload Rev field
has been added to the
output with the -a
option for some Fibre
Channel initiator
adapters.
na_sysconfig(1) man
page
8.2
system health
autosupport
trigger history
show
The optional -asup-
enable parameter has
been added. This
parameter shows the
alerts that did or did
not trigger an
AutoSupport message.
na_system_health_auto
support(1) man page
8.2
system health
policy definition
modify
The optional -
asup-enable
parameter has been
added. This
parameter specifies
whether the alerts
generated by the
specified health
policy triggers an
AutoSupport
message.
Changes to the -
enable parameter
are now persistent
across reboots.
na_system_health_poli
cy(1) man page
8.2
30 | Release Notes
changed in
system health
policy definition
show
The optional -asup-
enable parameter has
been added. This
parameter shows health
policies that do or do
not trigger
AutoSupport messages
for alerts.
na_system_health_poli
cy(1) man page
8.2
vol autosize The -minimum-size
and -shrink-threshold-
percent parameters
have been added to
support the new
autoshrink capability.
Data ONTAP Storage
7-Mode
na_vol(1) man page
8.2
vol status The -F and -S options
were added. These
options display
detailed information
about how space is
used in the volume and
in the volume
footprint, respectively.
Data ONTAP Storage
7-Mode
na_vol(1) man page
8.2
Replaced or removed commands in the Data ONTAP 8.2
release
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 -hybrid
command to see space usage in the SSD cache of a Flash Pool.
New options in the Data ONTAP 8.2 release
This 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 the
options command:
in 7-Mode | 31
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 Default
value
Release
added
autosupport.support.reminder Enables or disables a
reminder message that
appears when
autosupport.suppor
t.enable is set to off.
Note: This option was
previously hidden.
on 8.2
cf.giveback.auto.override.vetoes Overrides giveback
vetoes. In previous
versions of Data
ONTAP, this option was
named
cf.giveback.auto.t
erminate.bigjobs.
off 8.2
cf.mode Enables HA mode on the
controller. The HA mode
must be set on both
controllers for the HA
functionality.
This option replaces the
requirement for a cf
license.
None. 8.2
coredump.savecore.warn Enables Data ONTAP to
prompt for confirmation
when deleting unsaved
core files.
off 8.2
disk.auto_assign_shelf Supports shelf-level disk
autoassignment.
off 8.2
32 | Release Notes
value
Release
added
flexscale.readahead_blocks Caches readahead data
that the system evicts
from buffer cache.
Readahead data is data
that clients are likely to
request.
off 8.2
ldap.fast_timeout.enable Controls the timeout
behavior of LDAP client
operations.
on 8.2
ldap.retry_delay Sets the time, in seconds,
to wait before trying to
connect to LDAP servers
after a failed attempt.
120 8.2
nfs.rpcsec.trace Enables new EMS
messages to help
troubleshoot Kerberos
issues.
off 8.2
raid.mix.hdd.disktype.capacity Enables mixing
performance disks with
different Data ONTAP
disk types in the same
aggregate.
on 8.2
raid.mix.hdd.disktype.performance Enables mixing capacity
disks with different Data
ONTAP disk types in the
same aggregate.
off 8.2
raid.mix.hdd.rpm.capacity Enables mixing capacity
disks with different
speeds when creating or
adding to aggregates.
off 8.2
raid.mix.hdd.rpm.performance Enables mixing
performance disks with
different speeds when
creating or adding to
aggregates.
on 8.2
in 7-Mode | 33
value
Release
added
snapvault.stale_config_cleanup_en
able
Enables or disables the
cleanup of stale
SnapVault
configurations.
on 8.2
licensed_feature.snaplock_enterpr
ise.enable
Enables the SnapLock
Enterprise functionality.
off 8.2
licensed_feature.snaplock.enable Enables the SnapLock
Compliance
functionality.
off 8.2
cf.remote_syncmirror.enable When set to on, enables
the MetroCluster
functionality.
off 8.2
Changed options in the Data ONTAP 8.2 release family
You 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 Release
changed
autosupport.cifs.verbose This option was removed. 8.2
cf.giveback.auto.terminate.bigj
obs
This option has been renamed as
cf.giveback.auto.override.vetoe
s.
8.2
nfs.authsys.extended_groups_ns.
queue_max
The maximum limit for this option was
changed to 640.
8.2
nfs.thin_prov.ejuke The default for this option was changed to
on.
8.2
34 | Release Notes
Option Change Release
changed
nfs.v4.id.allow_numerics The default for this option was changed to
off.
8.2
raid.disktype.enable This option was replaced by the following
two options:
raid.mix.hdd.disktype.capacit
y
raid.mix.hdd.disktype.perform
ance
8.2
raid.rpm.ata.enable This option was replaced by
raid.mix.hdd.rpm.capacity. Setting
it to on enables disk speed mixing for
capacity disks.
8.2
raid.rpm.fcal.enable This option was replaced by
raid.mix.hdd.rpm.performance.
Setting it to off disables disk speed
mixing for performance disks.
8.2
in 7-Mode | 35
Requirements for running Data ONTAP 8.2
You can verify whether you have the storage systems and firmware needed to run 7-Mode software
for the Data ONTAP 8.2 release family.
To determine the capacity and maximum volume size of your storage system model, see the
Hardware Universe at hwu.netapp.com.
Supported systems
You 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 of
FAS3270 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-v
systems, can be configured as an HA pair.
For more information about supported storage systems in the Data ONTAP 8.2 release family, see
the Hardware Universe at hwu.netapp.com.
Unsupported systems
Some 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 library
is an oversight and will be removed in a future release.
Where to get the latest firmware versions
You need to confirm that you have the latest firmware for your storage system, disks, and disk
shelves.
The following storage system components have firmware that sometimes requires upgrading:
Motherboards (their firmware is also known as system or storage system firmware)
Disk drives
Disk shelves
Storage system firmware
It is best to upgrade to the latest version of storage system firmware. For a list of available system
firmware, see the System Firmware Release Table at support.netapp.com/NOW/cgi-bin/fw. For more
information, 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
Note: New disk firmware is sometimes included with Data ONTAP upgrade packages. For more
information, 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 the
Disk Shelf & ESH Firmware Matrix at support.netapp.com/NOW/download/tools/diskshelf.
V-Series interoperability and limits information
Not all Data ONTAP releases support the same features, configurations, storage system models, and
storage array models for V-Series systems. When planning your configuration, you need to check
sources 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 in
the V-Series Support Matrix, and array LUN-specific limits were also provided in the V-Series
Limits Reference for Third-Party Storage and the V-Series Support Matrix. This information is now
divided into two different tools that are the authoritative sources for this information, as shown in the
following table:
For information about... You should look here...
Data ONTAP working with devices, including
the following:
Supported storage arrays and storage array
firmware
Supported switches and switch firmware
Whether your storage array supports
nondisruptive (live) upgrade of the storage
array firmware
Whether a MetroCluster configuration is
supported 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 for
the root volume and spare core array LUNs
Minimum aggregate size for aggregates with
array LUNs
Supported block size
Minimum and maximum capacity
Neighborhood limits
Hardware Universe at hwu.netapp.com
38 | Release Notes
Data ONTAP-v requirements and support information
Not all Data ONTAP features or configurations are supported when running on a Data ONTAP-v
platform (including the Data ONTAP Edge and Data ONTAP Edge-T products). This is because of
differences when Data ONTAP is running in a virtual machine on a host system instead of running
on NetApp storage controllers.
See the Data ONTAP-v supported and unsupported functionality section in the Data ONTAP Edge
Installation 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 the
Interoperability Matrix at support.netapp.com/matrix.
Requirements for running Data ONTAP 8.2 | 39
Important cautions
Before upgrading to this release of Data ONTAP, you need to read the important cautions to identify
and resolve issues that might affect the operation of your storage systems.
To request more information about an individual bug and to explore other bug-related tools, see Bugs
Upgrade cautions
If you are upgrading to this Data ONTAP release, you should review the cautions 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.
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 ONTAP
8.2.
The Data ONTAP management software affected by this change includes, but is not limited to, the
SnapDrive 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 API
Documentation page on the NetApp Community.
Third-party applications or scripts written to use the license-list-info ZAPI will fail after the upgrade
to Data ONTAP 8.2. Therefore, if you use third-party applications, you should contact the vendors to
obtain an update that is supported for Data ONTAP 8.2.
If you are using synchronous SnapMirror, upgrading to Data ONTAP 8.2
can cause performance degradation
If you have deployed synchronous SnapMirror in Data ONTAP 8.1.x for 7-Mode, upgrading to Data
ONTAP 8.2 can cause performance degradation. To avoid this issue, you should remain in Data
ONTAP 8.1.x.
For more information, see the knowledgebase article 2017591 on the NetApp Support Site.
40 | Release Notes
3210 and 3140 systems with Flash Cache modules not supported
3210 and 3140 storage systems with Flash Cache modules are not supported in Data ONTAP 8.2 and
later 8.2.x releases operating in 7-Mode. You cannot upgrade to Data ONTAP 8.2 or later 8.2.x
releases 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 can
cause storage system disruption
If you are upgrading to Data ONTAP 8.2 from a release earlier than Data ONTAP 8.1, you must
perform an intermediate upgrade. During the intermediate upgrade if you modify the state of
deduplication 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 to
Data ONTAP 8.1.x. You might disable deduplication before upgrading from Data ONTAP 7.3.x and
then enable deduplication after upgrading to Data ONTAP 8.1.x. If the next scheduled volume
efficiency operation runs on the volume before upgrading to Data ONTAP 8.2 , then storage system
disruption can occur. However, if you upgrade to Data ONTAP 8.1.2 and enable deduplication on the
volume, 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 intermediate
upgrade.
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 2008
and Windows Server 2012 interpret the LUNs with new revision numbers as new disks and set them
offline after a host reboot; this status is shown in Windows management interfaces after the upgrade.
Windows Server 2003 ignores LUN revision numbers.
If the disks are offline, bring them online by using Windows disk management tools or SnapDrive
functionality.
You can work around this problem by setting the SAN policy to "Online All" prior to upgrading Data
ONTAP. Use the Windows diskpart command to change the SAN policy. After you upgrade Data
ONTAP, 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 the
raid.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. To
avoid 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 to
insufficient space
In Data ONTAP 8.2.x releases, you must ensure that there is sufficient space on the aggregate and on
the volume to upgrade the deduplication metadata. You can use the df command to check the space
available on the aggregate and on the volume.
Deduplication metadata can occupy up to 7 percent of the total physical data contained within the
volume, as follows:
In an aggregate, deduplication metadata can occupy up to 3 percent of the total physical data
contained within the volume.
In a volume, deduplication metadata can occupy up to 4 percent of the total amount of data
contained within the volume.
42 | Release Notes
In case of insufficient space, the upgrade will succeed but deduplication will be disabled on the
volume and no further deduplication will be carried out on the volume until you explicitly enable
deduplication on the volume.
Stale metadata not automatically removed during deduplication operations
on volume
Stale deduplication-related metadata can exist in the FlexVol volumes and aggregates on your
system, 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 prior
to 8.1.2P4, if deduplication is enabled on any FlexVol volume, and if a FlexVol volume or the
associated aggregate is more than 70 percent full. If these conditions exist, see bug ID 657692, before
proceeding 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 to
Data ONTAP 8.2.
Manageability cautions
If you are a storage system administrator, you should familiarize yourself with these manageability
issues.
If you reinstall a license key in Data ONTAP 8.2, you must use the new
license key format
Starting with Data ONTAP 8.2, all license keys are 28 characters in length. Licenses installed prior to
Data ONTAP 8.2 continue to work after you upgrade to Data ONTAP 8.2. However, if you need to
reinstall 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. You
can find license keys for your initial or add-on software orders at the NetApp Support Site under My
Support > Software Licenses. For instance, you can search with the serial number of a system to
find all license keys associated with the system. If you cannot locate your license keys from the
Software 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 ONTAP
image. By default, the SP automatic update functionality is enabled. You have the option to manually
trigger 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 SP
firmware becomes subsequently available, you have the option to download it from the System
Firmware and Diagnostics Download page on the NetApp Support Site and update the SP firmware
to the downloaded version without upgrading the Data ONTAP version. For information about
manually downloading and updating the SP firmware, see the SP Firmware Download and
Installation 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 be
automatically updated in the following scenarios:
When you upgrade to a new version of Data ONTAP
The Data ONTAP upgrade process automatically includes the SP firmware update, provided
that the SP firmware version bundled with Data ONTAP is newer than the SP version running
on the system.
When you download a version of the SP firmware from the NetApp Support Site and the
downloaded 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 node
service-processor image modify command. However, it is best to leave the functionality
enabled. Disabling the functionality can result in suboptimal or nonqualified combinations
between the Data ONTAP image and the SP firmware image.
Data ONTAP enables you to trigger an SP update manually and specify how the update should
take 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 file
name. 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 currently
running 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, and
forensics logs (-clear-logs)
44 | Release Notes
For information about the system node service-processor image update command, see
the man page.
Data ONTAP enables you to display the status for the latest SP firmware update by using the
system 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 the
case whether the SP firmware update is automatic or manually triggered.
Related information
Network protocol cautions
You 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 file
are not in the recommended order
You should ensure that the entries in the /etc/rc file are in the recommended order. The incorrect
order 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 System
Administration Guide for 7-Mode.
Storage management cautions
You should review these issues and take appropriate action before upgrading or reinstalling.
Disk failures might increase for some disk models after upgrading to this
version of Data ONTAP
Starting with Data ONTAP 8.1.2, the software install or upgrade includes new disk shelf firmware
versions for DS14mk2 AT and DS4243 disk shelves that provide enhanced disk error detection and
prediction capabilities. Therefore, after upgrading to this version of Data ONTAP, you might
experience 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. You
should follow standard best practices for spares when you upgrade, to ensure that sufficient spares
are always available.
The following table shows the disk shelf and disk models that might show an increased failure rate
after 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 cautions
If your storage system is deployed in a NAS environment, you should review the important cautions
regarding file access and protocols management and take appropriate action before upgrading or
reinstalling.
For more information about these cautions, see the Data ONTAP File Access and Protocols
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 vFiler
units are present, they might not be initialized for the duration of the CIFS startup time. The delay in
CIFS startup is typically due to network infrastructure issues related to domain controllers and LDAP
servers.
About this task
To ensure that the domain controllers, DNS servers, and LDAP servers are accessible, it is
recommended that you run the following tests on the partner node for which giveback is to be
initiated before initiating a giveback. Successful execution of these commands does not guarantee
that CIFS startup during giveback will occur quickly. The servers that are responding now might fail
later 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 then
discovers 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 entering
the 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 proceed
with giveback.
Setup cautions
If 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 local
administrator account password for CIFS.
CIFS setup requires a new root password. You can either specify a new password or reuse the same
password by changing the password history settings. For more information, see the Data ONTAP
Software 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 System
Revert and downgrade cautions
If you are reverting or downgrading from this release to an earlier release, you should review the
cautions 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 to
install licenses for some features
If you gained access to licensed or entitled features by upgrading to Data ONTAP 8.2 or later and
these features required a license prior to Data ONTAP 8.2, you might need to install a license after
reverting. 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 that
required a license prior to Data ONTAP 8.2 might be available for free or as part of a package that
you are licensed to install in Data ONTAP 8.2 or later. If you did not install a license for the
functionality prior to Data ONTAP 8.2 and you revert to the earlier release, you might need to install
a 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 upgrade
to Data ONTAP 8.2 or later, SyncMirror is available to you without a license. If you revert to a
release 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 NetApp
Support 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 the
NetApp Support Site.
Licensing implications for reverting a system that is shipped with Data
ONTAP 8.2 to an earlier release
You need to be aware of the licensing implications if you have a system that is shipped with Data
ONTAP 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 Data
ONTAP 8.1 release family, you must install a key for the desired license package in the format
supported 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 Data
ONTAP 8.1 7-Mode FAQ on the NetApp Support Site.
Downgrading or reverting to Data ONTAP 8.1 or earlier with a Flash Pool
aggregate root aggregate disables the system
If you configure a Flash Pool aggregate (an aggregate that contains both HDDs and SSDs) as your
root 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, your
system will not boot after the downgrade or revert.
SP firmware might require a downgrade if you revert or downgrade to an
earlier Data ONTAP release
If your current SP firmware version is not supported for the Data ONTAP release you are
downgrading or reverting to, you must install a supported SP firmware version for the earlier Data
ONTAP release.
After the Data ONTAP revert or downgrade process is complete, you must take the action to install
an SP firmware version that is supported for the Data ONTAP version you reverted or downgraded
to. To learn which SP firmware versions are supported by each Data ONTAP release, see the BIOS
Service Processor Support Matrix on the NetApp Support Site. For instructions about downloading
and installing an SP firmware version, see the System Firmware and Diagnostics Download page on
the NetApp Support Site.
Reverting to an earlier release of Data ONTAP when 32-bit volumes or
aggregate are converted to 64-bit format
After an upgrade, if you have converted the 32-bit volumes or aggregate to the 64-bit format, you
cannot revert the source and destination systems to an older version of Data ONTAP until you delete
all 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 a
previous release family requires action if you have NFSv4 ACLs in your environment that contain
more than 400 ACEs.
If you perform a file system revert to a Data ONTAP 8.1 release, any ACLs containing more than
400 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.
Known problems and limitations
Some unexpected and potentially undesired post-upgrade behaviors, and in some cases workarounds
to avoid these behaviors, have been identified.
To request more information about an individual bug and to explore other bug-related tools, see Bugs
Manageability issues
You should be familiar with the known issues and limitations in the management interface that affect
your ability to manage the storage system.
These issues include problems with command behavior, command output, or error messages
presented in the Data ONTAP CLI or web interface and problems with UNIX or operating system
commands used to interface with your storage system.
Command typed in from one connection might be executed by a
concurrent connection
If the telnet.distinct.enable option is set to off, a command typed in from a console
connection that is initiated through the remote management device (the RLM or the SP) might be
executed 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 existing
console session that is initiated through the remote management device, pressing Enter on your
Telnet or SSH session might execute a command that has just been typed in but not yet executed
from the concurrent console session. This behavior might happen even if you do not see the
command name on your Telnet or SSH session. This behavior might occur if the
telnet.distinct.enable option is set to off.
Storage resource management issues
You 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 to
initiate tasks between different sub-systems within Data ONTAP. The number of asynchronous
messages per storage system is limited.
Deduplication operations use the asynchronous messages to send information to the block-sharing
state 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 and
when 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 those
many deduplication operations to drain all the messages.
You can fix this issue by rebooting the storage system. All the asynchronous messages are
reallocated 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 or
Data 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 application
accessing data residing in the volume could experience a data outage if the volume is out of free
space, even with the volume guarantee set to volume, when any of the following technologies and
Data 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 prevent
errors that can arise from running out of spaceand you must use all of the following configuration
settings 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 of
Snapshot copies needing to be deleted automatically. If you enable the autogrow capability, you must
monitor the free space in the associated aggregate. If the aggregate becomes full enough that the
volume is prevented from growing, more Snapshot copies will probably be deleted as the free space
in 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, but
guarantees that data modification operations will succeed even when the technologies listed
previously 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 when
creating or adding to aggregates. When you specify a disk type with the -T parameter, if disk-type
mixing is enabled, Data ONTAP might use an equivalent disk type rather than the type you specified.
Read performance for mirrored aggregates not in a MetroCluster
configuration might be degraded
The cf_remote license is installed by default on all new 32xx and 62xx storage systems for versions
of Data ONTAP earlier than 8.2. If you upgraded to Data ONTAP 8.2 and are using mirrored
aggregates that are not in a MetroCluster configuration, the presence of this license can reduce read
performance because data is read from only one plex.
You can recover from this situation by using the following command to disable the license (on both
nodes 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 ACP
for the local SAS expander
If you configure ACP to use a different port than e0P (the default) on a FAS2240 system, the internal
ACPP module IOM6E becomes unresponsive, disabling ACP for the local SAS expander. Unless
you are experiencing hardware issues on port e0P, always use the default port for ACP for the
FAS2240 system.
Incorrect error message when FlexClone volume creation fails on a storage
system that is halting
When you try creating a FlexClone volume on a storage system that is halting because of a reboot or
a 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, the
particular error message appears only when the first attempt at creating a FlexClone volume fails on
the storage system that is halting. Subsequent attempts at creating FlexClone volumes fail with the
correct error message: License DB currently unavailable.
52 | Release Notes
Issues with V-Series systems working with LUNs from
storage arrays
You should understand the known problems and limitations related to using V-Series systems with
storage 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 ports
before the storage array parameters are set and the LUNs are mapped to the host groups, you might
not 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 force
a 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 if
zoning is configured before setting the host persona
If V-Series system FC initiator ports are zoned with HP 3PAR array target ports before the correct
host persona is set on the 3PAR storage array, Data ONTAP reports some of the LUNs as unknown
devices. 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 is
configured before setting the host persona, the storage array might report a Product ID of SES and
identify 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 device
problem by doing path re-initialization to force a rediscovery of the array LUNs that are mapped
from a 3PAR storage array. See Workaround for the unknown device (L254) problem with 3PAR
storage 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 on
some Hitachi and HP storage arrays
Starting in Data ONTAP 8.2, Data ONTAP verifies that the REPORT LUNs response data contents
matches the number bytes transferred by the device. A mismatch in the number of bytes transferred
might occur with Hitachi 9970, VSP, USP-V, and HP 9500 storage arrays when fewer than 16 LUNs
are visible in a host group.
This mismatch of transferred data to response data contents prevents the LUNs from being visible to
Data 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 more
information about this issue, see Bug 705779 in Bugs Online.
Related information
Network protocol issues
You 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 the
interface.blocked.mgmt_data_traffic option
In a single path SnapMirror transfer, you cannot use the
interface.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 source
storage system.
To block traffic from e0M, all the storage systems must use a consistent configuration. You must
ensure that routes to the destination storage systems do not use e0M, and that neither SnapMirror nor
NDMP 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 an
interface 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 in
the /etc/hosts file, and the interface name is used in an ifconfig command, the host name gets
resolved in the local host context and not the partner context, resulting in unavailability of the partner
node during takeover.
For example, while configuring the partner interface, the command fails during controller failover in
the 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 local
host'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
Disabling fast path in some network environments
Fast path is enabled by default on all storage systems. However, you might have to disable fast path
in 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 the
response by bypassing a routing table lookup. Fast path is enabled by default for all TCP and NFS
over UDP connections.
You might have to disable fast path if you are working in configurations of Cisco vPC, HP NIC
teaming, 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 issues
If your storage system is deployed in a NAS environment, you should review the known problems
and 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 256
characters (excluding the initial \\ in the UNC path), then the Security tab in the Windows
Properties 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 after
upgrade
When you upgrade a storage system from Data ONTAP 8.1.x to 8.2 or later, and then use the lock
status -n command, the resulting output might display a larger number of current locks than the
maximum 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 larger
than the new maximum limit of allowed locks.
4. You use the lock status -n command. Data ONTAP displays the amount of reclaimed locks
which 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 client
eventually releases locks, the number of current locks continues to drop until it is below the
maximum limit. After that, the number of new current locks can no longer exceed the maximum
limit.
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 storage
system, the authentication fails.
The storage system log records the following error message: AUTH:SPNEGO-Could not unpack
NTLMSSP 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 that
it complies with NetBIOS specifications.
Related information
Excessive pending CIFS authentication requests can cause service
disruption
If domain controllers become unavailable to a vFiler unit, pending CIFS authentication requests
accumulate on the storage system. If the issue is not resolved, this can prevent other vFiler units on
the 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 vFiler
units.
Data ONTAP enables you to monitor pending CIFS authentication requests and take corrective
action 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 and
directories
When a Microsoft Windows 7 or Windows 8 client accesses an SMB share with widelinks enabled, it
can fail intermittently to rename files and directories on the mapped share. This can lead to a
situation 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 is
available from Microsoft. The bug is described and information about how to obtain the hot fix is
provided 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 KB
articles also provide information about a workaround for this issue if you do not want to apply the
hot 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 is
displayed.
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 vscan
alerts requires NetBIOS over TCP to be enabled in Data ONTAP.
Similarly, NetBIOS over TCP must be enabled on Windows clients and the Windows Messenger
service must be running.
By default, the Windows Messenger service is disabled on Windows 2003 and Windows XP SP2
clients.
Effective style of qtrees created on an NTFS volume before configuring
CIFS
On a newly installed storage controller without CIFS configured, if you create a qtree on a volume
that has security style set to NTFS, the resulting qtree has NTFS as the security style and UNIX as
the effective style. This means that UNIX clients can set attributes on the NTFS volumes, which
normally would not be allowed.
The effective style of these qtrees does not change even after CIFS is configured for NTFS only. You
must avoid setting the security style of a volume to NTFS before configuring CIFS on a newly
installed storage system.
58 | Release Notes
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 information
about setting the security styles for qtrees, see the Data ONTAP File Access and Protocols
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 attempt
fails. Widelinks are not accessible from Mac OS X clients.
Windows clients make a Distributed File System (DFS) referral request after Data ONTAP returns
the special error code STATUS_PATH_NOT_COVERED. The CIFS widelink feature uses this
behavior in its implementation. In its DFS response, Data ONTAP can provide a referral that is
configured 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 the
way they handle the special DFS error code. Apple bug 13870704 has been created to document and
track the issue. Customers encountering this issue with Mac support for widelinks should contact
Apple 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 the
actual flag
Data ONTAP supports certain VMware vStorage APIs for Array Integration (VAAI) features in an
NFS environment, such as copy offloading. However, VMware vStorage over NFS has a copy
offloading 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 component
for 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 SIS
enabled
The copy offload feature provided by the NFS Plug-in for VMware VAAI results in a block copy if a
FlexVol volume that backs an NFS datastore has never had SIS enabled, or if the sis undo
command has been run against it. Normally, the NFS VAAI copy offload feature uses a FlexClone
copy operation to perform a fast and space-efficient copy. If SIS is not enabled on the volume
containing 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 the
volume has SIS enabled. When you create a volume with Virtual Storage Console for VMware
vSphere, 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 offloading
and deduplication. It then uses the vol status command to verify the change and show that
sis is listed for the volume VAAI_SIS:
NetApp1> sis on /vol/VAAI_SIS
NetApp1> vol status
Volume State Status Options
vol0 online raid_dp, flex root
64-bit
VAAI_SIS raid_dp, flex
sis
64-bit
Data protection issues
If you use data protection products that include Snapshot technology (such as SnapRestore,
SnapVault, SnapMirror, and SnapManager), you might have to familiarize yourself with relevant
data protection issues.
For more information about these issues, see the Data ONTAP Data Protection Online Backup and
Recovery Guide for 7-Mode and the Data ONTAP Data Protection Tape Backup and Recovery
Guide for 7-Mode.
60 | Release Notes
SnapVault cannot be enabled on vFiler units when relationships are
present in vfiler0
When you create in vfiler0, you also manually set the snapvault.lockvault_log_volume option
to the name of a log volume. After this option is set, SnapVault cannot be enabled on any vFiler units
on the storage system. For more information about the snapvault.lockvault_log_volume
option, see the na_snapvault(1) man page.
SMTape operations abort if you turn off SnapMirror
If you turn off SnapMirror while performing SMTape backup and restore operations, SMTape
operations 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 that
offline volume.
SAN administration issues
If your storage systems are part of a SAN environment, you might need to familiarize yourself with
SAN 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 groups
when upgrading Data ONTAP
After upgrading to Data ONTAP 8.0.4 and 8.1.1, 8.2.0 or later releases, some Oracle Linux-based
systems using ASMlib can fail to recognize disk groups.
This problem is due to a change made in Data ONTAP's SCSI READ CAPACITY (16) parameter
data, 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 inconsistent
sector 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-size
option 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 on
very large fabrics
Running the fcp topology show -v|z command on a target port connected to a very large fabric
might 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 zoned
options. This returns concise output only.
More detailed fabric information can be obtained from the fabric switches.
Data ONTAP-v platform issues
There are certain issues and restrictions you should be aware of when using products based on the
Data 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 the
functionality of Data ONTAP compared to when it is running on a hardware controller. See the "Data
ONTAP-v supported and unsupported functionality" section in the Data ONTAP Edge Installation
and Administration Guide for more information.
MultiStore issues
You 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 Flash
Pools 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 this
release were published. The information should be used in conjunction with the guides provided with
this release of Data ONTAP.
Changes to the Commands Manual Page Reference
New 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 to
prompt for confirmation when
deleting unsaved core files
off
ldap.fast_timeout.enabl
e
Controls the timeout behavior
of LDAP client operations
on
ldap.retry_delay Sets the time, in seconds, to
wait before trying to connect to
LDAP servers after a failed
attempt
120
licensed_feature.snaplo
ck_enterprise.enable
Enterprise functionality
off
licensed_feature.snaplo
ck.enable
Compliance functionality
off
nfs.authsys.extended_gr
oups_ns.queue_max
Controls the maximum number
of requests that can be queued
at any given time to obtain the
GIDs from the name service
80
Note: The maximum limit for nfs.authsys.extended_groups_ns.queue_max was changed
to 640.
63
Changes to the File Access and Protocols Management
Guide
New information has become available since the previous revision of the Data ONTAP File Access
and 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 Protocols
Management 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 to
the /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 Protocols
Changes to the Software Setup Guide
Additional information has become available since the last revision of the Data ONTAP Software
Setup 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-alone
mode, 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 state
can 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 a
configuration validation and health check tool for NetApp systems. Support for Config Advisor is
limited, 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 using
option four of the Data ONTAP boot menu (Clean configuration and initialize all
disks), HA mode is enabled by default, and the system's nonvolatile memory (NVRAM or
NVMEM) is split. If you plan to use the controller in standalone mode, you must configure the node
as non-HA. Reconfiguring the node as non-HA mode enables full use of the system's nonvolatile
memory.
Note: Configuring the node as standalone removes the availability benefits of the HA
configuration and creates a single point of failure.
For information on using the boot menu to manage the storage system, see the Data ONTAP System
Choices
If the cf status output displays Non-HA mode, then the node is configured for non-HA mode
and you are finished:
Example
node > cf status
Non-HA mode.
If the cf status output directs you to reboot, you must reboot the node to enable full use of the
system's nonvolatile memory:
Example
node> cf status
Non-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's
nonvolatile memory:
Example
node> cf status
Controller 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
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 of
the system's nonvolatile memory:
Example
node> cf status
Controller 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
Changes to the Data ONTAP Storage Management Guide for
7-Mode
New information has become available since the previous revision of the Data ONTAP Storage
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 currently
supported by Data ONTAP. The numbers shown are in Mebibytes (MiBs). This unit of measure is
equivalent 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 by
manufacturer. The technical documentation for your disks contains the exact physical disk capacities.
Disk size as described by
manufacturer
Physical capacity (MiBs,
approximate)
Usable capacity (MiBs)
300 GB Performance 280,104 272,000
66 | Release Notes
Disk size as described by
manufacturer
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 Guide
Additional information has become available since the last revision of the Data ONTAP System
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 Implementation
Guide 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 not
listed 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 the
3PAR storage array families topic.
P10000 - V400
P10000 - V800
3PAR StoreServ 7200
3PAR StoreServe 7400
Workaround for the unknown device (L254/SES) problem with 3PAR
storage 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 the
V-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 ONTAP
cannot use.
When Data ONTAP discovers 3PAR array LUNs as LUN 254 and product type SES, newly mapped
3PAR LUNs cannot be assigned to V-Series systems and some 3PAR LUNs that might have already
been added to an aggregate cannot be used because Data ONTAP sees a LUN 254. Data ONTAP
generates EMS messages for the LUN it discovered as LUN 254 and product type SES, reporting
some LUNs as unknown devices.
If zoning was configured before the host definition, you can resolve the LUN 254/SES unknown
device problem by forcing a rediscovery of the array LUNs that are mapped from a 3PAR storage
array. The procedure you use depends on whether aggregates with 3PAR array LUNs have already
been configured on the V-Series system. (In the following procedures, assume that Node-1 and
Node-2 are the names of the V-Series nodes.)
If aggregates with 3PAR 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-Series
systems:
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 status
Node-1 has taken over Node-2
Node-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-Series
system
1. Run the following command to list all of the V-Series FC initiator ports that are connected to the
3PAR 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 storage
arrays
The storage array parameters specified in the V-Series Implementation Guide for Third-Party Storage
should be set and LUNs should be mapped to the host groups before the switch is zoned to connect
the 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 path
reinitialization forces a rediscovery of the array LUNs that are mapped from a Hitachi or HP XP
storage array.
The procedure you use depends on whether aggregates with Hitachi or HP XP array LUNs have
already been configured on the V-Series system. (In the following procedures, assume that Node-1
and 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-Series
systems:
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 status
Node-1 has taken over Node-2
Node-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 the
Hitachi 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 and
Reference Guide
New information has become available since the last revision of the V-Series Installation
Requirements 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 Installation
Requirements and Reference Guide shows the required space as 0.1%. This is not correct. The
required space for a core dump for array LUNs less than or equal to 2 TiB is 1%.
Where to find product documentation and other
information
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
Access & Order Product Documentation: support.netapp.com/knowledge/docs/docs.shtml
NetApp Library: Technical Reports: www.netapp.com/library
Searching online information
The NetApp Support Site includes a natural language search tool so that you can search easily for
many 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 Site
You 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
Copyright information
Copyright
19942013 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 an
electronic retrieval systemwithout prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
73
Trademark information
NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,
ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, Campaign
Express, ComplianceClock, Cryptainer, CryptoShred, CyberSnap, Data Center Fitness, Data
ONTAP, 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, the
StoreVault logo, SyncMirror, Tech OnTap, The evolution of storage, Topio, VelocityStak, vFiler,
VFM, Virtual File Manager, VPolicy, WAFL, Web Filer, and XBB are trademarks or registered
trademarks of NetApp, Inc. in the United States, other countries, or both.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. A complete and current list of
other IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United States
and/or other countries. Microsoft is a registered trademark and Windows Media is a trademark of
Microsoft 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 other
countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.
74 | Release Notes
How to send your comments
You can help us to improve the quality of our documentation by sending us your feedback.
Your feedback is important in helping us to provide the most accurate and high-quality information.
If you have suggestions for improving this document, send us your comments by email to
doccomments@netapp.com. To help us direct your comments to the correct division, include in the
subject 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

Data ONTAP 8.2 Release Notes For 7mode

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Data ONTAP 8.2 Release Notes For 7mode

Hochgeladen von

Copyright:

Verfügbare Formate

Data ONTAP

19942013 NetApp, Inc. All rights reserved. Printed in the U.S.

Das könnte Ihnen auch gefallen