ibm system storage n series data ontap 8.2.1 rc1 release ...€¦ · iv ibm system storage n...

IBM System Storage N series

Data ONTAP 8.2.1 RC1 Release Notes for7-Mode

SC27-5938-04

��

Release Candidate Documentation - Contents Subject To Change

Contents

Data ONTAP 8.2 Release Notes for 7-Mode. . . . . . . . . . . . . . . . . . . . . 1

Changes introduced since Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . 3Changes in Data ONTAP 8.2.1 for 7-Mode . . . . . . . . . . . . . . . . . . . . . . . . . 3

Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Functionality changes in future releases. . . . . . . . . . . . . . . . . . . . . . 9

New and changed features in the Data ONTAP 8.2 release family for 7-Mode . . . . . 11New and changed platform and hardware support . . . . . . . . . . . . . . . . . . . . . . 11

N6210 and N6040 systems with Flash Cache modules not supported . . . . . . . . . . . . . . . 11Support for Flash Cache 2 modules . . . . . . . . . . . . . . . . . . . . . . . . . . 11Support for 800-GB SSDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Support for 1.2-TB performance disks. . . . . . . . . . . . . . . . . . . . . . . . . . 11Support for SAS optical cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Support for shelf hot-remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Manageability enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12The system node service-processor commands now support the RLM . . . . . . . . . . . . . . . 12Licensing changes for the Data ONTAP 8.2 release family . . . . . . . . . . . . . . . . . . . 13New command family for managing the SP from Data ONTAP . . . . . . . . . . . . . . . . . 14AutoSupport enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Enhancements to health monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 15Messages in the /etc/messages file now include the system name . . . . . . . . . . . . . . . . 15Options for specifying uppercase and lowercase requirements in user passwords . . . . . . . . . . . 15

High-availability pair enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Support for SSDs in a MetroCluster configuration . . . . . . . . . . . . . . . . . . . . . 16New cf.mode option replaces the cf license . . . . . . . . . . . . . . . . . . . . . . . . 16Support for unidirectional port mirroring in a MetroCluster configuration . . . . . . . . . . . . . 16Support for ISL encryption in a MetroCluster configuration . . . . . . . . . . . . . . . . . . 16

Storage resource management enhancements . . . . . . . . . . . . . . . . . . . . . . . . 16Aggregates can be expanded to 64-bit format without adding storage . . . . . . . . . . . . . . . 17Increased maximum Flash Pool cache sizes for N3150, N3220, and N3240 systems. . . . . . . . . . . 17Automated Workload Analyzer tool for Flash Pool cache sizing . . . . . . . . . . . . . . . . . 17Increased maximum aggregate size for some platforms . . . . . . . . . . . . . . . . . . . . 17Multi-disk carrier and single-disk carrier disk shelves can be combined in the same stack . . . . . . . . 17Flash Pool aggregates support different RAID types and group sizes for SSD cache . . . . . . . . . . 17Flexibility for calculating maximum Flash Pool SSD cache size in HA configurations . . . . . . . . . . 18Aggregate Snapshot copy automatic deletion is always enabled . . . . . . . . . . . . . . . . . 18Disabled volume guarantees no longer reenabled automatically . . . . . . . . . . . . . . . . . 18Fractional reserve setting can be set only to 0 or 100. . . . . . . . . . . . . . . . . . . . . 18

Storage efficiency enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Support for detecting incompressible data in files. . . . . . . . . . . . . . . . . . . . . . 18

File access protocol enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Support for VMware vStorage over IPv6 . . . . . . . . . . . . . . . . . . . . . . . . 19Maximum ACE limit for NFSv4 ACLs has increased. . . . . . . . . . . . . . . . . . . . . 19Support for SMB 2.x authentication with CIFS workgroup mode . . . . . . . . . . . . . . . . 19Enhancements for management of unresponsive LDAP servers . . . . . . . . . . . . . . . . . 19Enabling new EMS messages to help troubleshoot Kerberos issues . . . . . . . . . . . . . . . . 20CIFS TCP window size increased to 64240 bytes . . . . . . . . . . . . . . . . . . . . . . 20

Data protection enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Support for multipath tape access . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Support for Single SnapVault license . . . . . . . . . . . . . . . . . . . . . . . . . . 21SyncMirror is enabled by default . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

© Copyright IBM Corp. 2014 iii


Options for enabling the SnapLock functionality . . . . . . . . . . . . . . . . . . . . . . 21Automatic resizing of SnapMirror destination for a FlexVol volume . . . . . . . . . . . . . . . 21Users cannot perform certain Qtree SnapMirror and SnapVault tasks during the post-upgrade operations . . . 21Serial numbers used for tape aliasing . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Summary of new and changed commands and options in the Data ONTAP 8.2 releasefamily operating in 7-Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 23New commands in Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Changed commands in Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . 24Replaced or removed commands in Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . . 28New options in Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Changed options in the Data ONTAP 8.2 release family . . . . . . . . . . . . . . . . . . . . 30

Requirements for running Data ONTAP 8.2 . . . . . . . . . . . . . . . . . . . . 33Supported systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Unsupported systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Where to get the latest firmware versions . . . . . . . . . . . . . . . . . . . . . . . . . 33

Important cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Upgrade cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Release Candidate 1 not recommended for systems with high disk count . . . . . . . . . . . . . . 35Change in how Data ONTAP handles file names containing UTF-16 supplementary characters . . . . . . 36Compatible versions of management software are required . . . . . . . . . . . . . . . . . . 36If you are using synchronous SnapMirror, upgrading to Data ONTAP 8.2 can cause performance degradation 36N6210 and N6040 systems with Flash Cache modules not supported . . . . . . . . . . . . . . . 36Modifying the state of deduplication during an intermediate upgrade can cause storage system disruption . . 37Disks offline in Windows Server 2008 and 2012 after Data ONTAP upgrade . . . . . . . . . . . . . 37Stale metadata not automatically removed during deduplication operations on volume . . . . . . . . . 37

Manageability cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37If you reinstall a license key in Data ONTAP 8.2 or later, you must use the new license key format . . . . . 38Changes to SP firmware update methods . . . . . . . . . . . . . . . . . . . . . . . . 38

Storage management cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Disk failures might increase for some disk models after upgrading to this version of Data ONTAP . . . . . 39

File access and protocols cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39CIFS startup might take several minutes after HA failover and giveback . . . . . . . . . . . . . . 40

Revert and downgrade cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Reverting to a release earlier than Data ONTAP 8.2 might require installation of licenses for some features . . 41Licensing implications for reverting a system that is shipped with Data ONTAP 8.2 or later to an earlier release 41Downgrading or reverting to Data ONTAP 8.1 or earlier with a Flash Pool aggregate root aggregate disablesthe system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42SP firmware might require a downgrade if you revert or downgrade to an earlier Data ONTAP release . . . 42Reverting to an earlier release of Data ONTAP when 32-bit volumes or aggregate are converted to 64-bit format 42ACLs containing more than 400 ACEs are dropped during revert . . . . . . . . . . . . . . . . 42

Known problems and limitations . . . . . . . . . . . . . . . . . . . . . . . . 43Manageability issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Command typed in from one connection might be executed by a concurrent connection. . . . . . . . . 43Storage resource management issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Storage system disruption due to unavailability of asynchronous messages . . . . . . . . . . . . . 44Out of space errors could be returned when fractional reserve is set to zero . . . . . . . . . . . . . 44Disk-type mixing might occur even when disk type is specified . . . . . . . . . . . . . . . . . 45Read performance for mirrored aggregates not in a MetroCluster configuration might be degraded . . . . . 45

Network protocol issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Error messages observed during change in the state of network interface groups . . . . . . . . . . . 45SNMPv3 access might fail for an existing user . . . . . . . . . . . . . . . . . . . . . . . 46Existing traphosts fail to receive SNMP traps . . . . . . . . . . . . . . . . . . . . . . . 46The first VLAN configured over a port might bring the port down temporarily . . . . . . . . . . . 46SnapMirror transfer cannot be blocked by using the interface.blocked.mgmt_data_traffic option . . . . . . 46Partner node might be unavailable during controller failover . . . . . . . . . . . . . . . . . . 47Disabling fast path in some network environments . . . . . . . . . . . . . . . . . . . . . 47

iv IBM System Storage N series: Data ONTAP 8.2.1 RC1 Release Notes for 7-Mode


File access and protocols issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Windows Security tab unavailable for shares with long UNC paths. . . . . . . . . . . . . . . . 48Number of existing locks larger than the maximum allowed limit after upgrade . . . . . . . . . . . 48CIFS client authentication fails if host name exceeds 16 characters . . . . . . . . . . . . . . . . 49Excessive pending CIFS authentication requests can cause service disruption . . . . . . . . . . . . 49Microsoft Windows 7 and Windows 8 clients fail to rename files and directories . . . . . . . . . . . 49Domain user unable to execute CLI commands . . . . . . . . . . . . . . . . . . . . . . 50Client notification messages in Windows domains require NetBIOS. . . . . . . . . . . . . . . . 50CIFS widelinks are not accessible from Mac clients . . . . . . . . . . . . . . . . . . . . . 50Effective style of qtrees created on an NTFS volume before configuring CIFS . . . . . . . . . . . . 50Data ONTAP permits deleting a file when an alternate data stream of the file is in use . . . . . . . . . 51VAAI copy offload limitations when exporting datastore volumes with the actual flag . . . . . . . . . 51NFS VAAI copy offload uses block copy if the volume does not have SIS enabled . . . . . . . . . . . 51

Data protection issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52SnapVault cannot be enabled on vFiler units when SnapLock for SnapVault relationships are present in vfiler0 52SMTape operations abort if you turn off SnapMirror. . . . . . . . . . . . . . . . . . . . . 52SMTape restore to an offline volume overwrites the data on that volume . . . . . . . . . . . . . . 53DAR fails if the file and the LUN have the same name on the destination volume. . . . . . . . . . . 53

SAN administration issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Some Oracle Linux systems using ASMlib fail to recognize disk groups when upgrading Data ONTAP. . . . 53

MultiStore issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Online migration of vFiler units is not supported on Flash Pools . . . . . . . . . . . . . . . . 54

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

Missing options in the 7-Mode Command Reference Guide . . . . . . . . . . . . . . . . . . 55Changes to the File Access and Protocols Management Guide . . . . . . . . . . . . . . . . . . 55

Managing anonymous FTP access requires additional step. . . . . . . . . . . . . . . . . . . 55Kerberos configuration topic mentions outdated encryption algorithm . . . . . . . . . . . . . . . 56Terminating and restarting CIFS on a volume . . . . . . . . . . . . . . . . . . . . . . . 56

Changes to the System Administration Guide . . . . . . . . . . . . . . . . . . . . . . . . 56Changes to troubleshooting AutoSupport over SMTP . . . . . . . . . . . . . . . . . . . . 57

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . . 59Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Contents v


vi IBM System Storage N series: Data ONTAP 8.2.1 RC1 Release Notes for 7-Mode


Data ONTAP 8.2 Release Notes for 7-Mode

The release notes describe new features, enhancements, and known issues for thisrelease, as well as additional information related to running this release on specificstorage systems.

About the Data ONTAP 8.2 release

Data ONTAP 8.2 is a major release; the first General Availability (GA) release inthe Data ONTAP 8.2.x release family. For more information about Data ONTAPreleases, refer to the following publication:

IBM System Storage N series Data ONTAP Release Model

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

Attention: If you have N6210 or N6040 storage systems with Flash Cachemodules installed, do not upgrade to clustered Data ONTAP 8.2. Flash Cachemodules are not supported on N6210 or N6040 systems running clustered DataONTAP 8.2.

For a complete list of functionality changes introduced in this release, see New andChanged features in the Data ONTAP 8.2 7-Mode Release Family.

Some Data ONTAP features are not supported in this release. For moreinformation, see Unsupported features.

About these release notes

All the information in this document applies to the Data ONTAP 8.2 release andlater Data ONTAP 8.2.x releases operating in 7-Mode for IBM N series storagesystems, unless noted.

It is a best practice for all Data ONTAP users to review these release notes.v If Data ONTAP is already running on storage systems in your environment, you

should familiarize yourself with relevant topics before upgrading to Data ONTAP8.2.

v If this is the first deployment of storage systems running Data ONTAP in yourenvironment, you should also refer to the Data ONTAP Information Librarypage for this release on the IBM N series support site.

v For more information about all Data ONTAP releases, see the Data ONTAPRelease Model on the IBM N series support site.

Websites

IBM maintains pages on the World Wide Web where you can get the latesttechnical information and download device drivers and updates. The followingweb pages provide N series information:v A listing of currently available N series products and features can be found at

the following web page:

© Copyright IBM Corp. 2014 1


http://www.ibm.com/support/docview.wss?rs=1147&uid=ssg1S7001721

www.ibm.com/storage/nasv The IBM System Storage N series support website requires users to register in

order to obtain access to N series support content on the web. To understandhow the N series support web content is organized and navigated, and to accessthe N series support website, refer to the following publicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well as otherimportant N series product resources.

v IBM System Storage N series products attach to a variety of servers andoperating systems. To determine the latest supported attachments, go to the IBMN series interoperability matrix at the following web page:www.ibm.com/systems/storage/network/interophome.html

v For the latest N series hardware product documentation, including planning,installation and setup, and hardware monitoring, service and diagnostics, see theIBM N series Information Center at the following web page:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

2 IBM System Storage N series: Data ONTAP 8.2.1 RC1 Release Notes for 7-Mode


http://www.ibm.com/storage/nas

http://www.ibm.com/storage/support/nseries/

http://www.ibm.com/systems/storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Changes introduced since Data ONTAP 8.2

You can find information about the changes that were introduced with each releasesince Data ONTAP 8.2 in this section.

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

New platform and hardware support

This release includes support for the following new platform hardware:v Support for SAS optical cablesv Support for shelf hot-remove

For more information, see New platform and hardware support.

New and changed features

This release includes the following new and changed features:

Manageability enhancementsv The system node service-processor commands now support the RLM

High-availability pair enhancementsv Support for SSDs in a MetroCluster configurationv Support for Unidirectional port mirroring in a MetroCluster configurationv Support for ISL encryption in a MetroCluster configuration

Storage resource management enhancementsv Aggregate expansion to 64-bit format without adding storagev Automated Workload Analyzer tool for Flash Pool cache sizingv Increased maximum Flash Pool cache sizes for FAS22xx systems

File access protocol enhancementsv Support for VMware vStorage over IPv6v CIFS TCP window size increased to 64240 bytes

New and changed commands and options

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

New commandsv system node service-processor

Manages the Remote LAN Module.v ic unidirectional_mirroring

Enables or disables the unidirectional port mirroring.



Changed commandsv aggr 64bit-upgrade start

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

The -fs-block-format option has been added. This option enables theadministrator to determine whether 32-bit format Snapshot copies are present.

v sysconfig

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

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

Changed optionsv raid.disk.timeout.enable

This option was removed.

New cautions

The following caution is new in this release:

Upgrade cautionsv Release Candidate 1 not recommended for systems with high disk countv Change in how Data ONTAP handles file names containing UTF-16

supplementary characters (7-Mode)

Removed cautions

The following cautions that were included in the Data ONTAP 8.2 Release Noteshave been removed in this release:v Upgrade cautions

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

v Networking cautionsSystem might panic if the network configuration entries in the /etc/rc file arenot in the recommended order

v Setup cautionsCIFS setup overwrites the storage system password

New known problems and limitations

There are new known issues in this release:v Network protocol issues

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

temporarilyv File access and protocols issues

Deleting the base file of an open stream file is permissible in Data ONTAP



v Data protection issuesDAR fails if the file and LUN have the same name on the destination volume

Removed problems and limitations

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

Storage resource management issuesv Configuring ACP to use a different port on an N3220 or an N3240 system

disables ACP for the local SAS expanderv Incorrect error message when FlexClone volume creation fails on a storage

system that is halting

SAN Administration issuesv The fcp topology show command with the verbose or zoned option fails on very

large fabrics

Documentation changes

The following new or changed information supplements the documentationavailable for this release:v Kerberos configuration topic mentions outdated encryption algorithmv Terminating and restarting CIFS on a volume

For more information about other important documentation updates, see Changesto published documentation.

Changes introduced since Data ONTAP 8.2 5


Unsupported features

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

NDMP v3

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



Functionality changes in future releases

Support for some features will be discontinued in a future release of Data ONTAP.v Volume guarantees of type file

In a future release of Data ONTAP, volume guarantees of type file will not besupported. Any existing volumes with guarantees of type file will be updated toanother guarantee type when you upgrade to that release.



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

A number of new features and enhancements have been introduced in the DataONTAP 8.2 release family.

Some enhancements in this release might also be introduced in a maintenancerelease of an earlier Data ONTAP release family. Before upgrading, be sure toconsult with your IBM N series representative about new Data ONTAPfunctionality to determine the best solution for your business needs.

Additional changes are described here. For other important information aboutchanges to the product made by these releases, see the release notes topicSummary of new and changed commands and options in the Data ONTAP 8.2release family operating in 7-Mode.

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

For information about the supported systems in Data ONTAP 8.2 for 7-Mode, seeSupported systems. For information about the unsupported systems in DataONTAP 8.2, see Unsupported systems.

N6210 and N6040 systems with Flash Cache modules notsupported

N6210 and N6040 storage systems with Flash Cache modules are not supported inData ONTAP 8.2 and later 8.2.x releases operating in 7-Mode. You cannot upgradeto Data ONTAP 8.2 or later 8.2.x releases if you have Flash Cache modules enabledin your N6210 or N6040 systems.

Support for Flash Cache 2 modulesData 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.

Support for 800-GB SSDsIn Data ONTAP 8.2 and later releases, 800-GB SSDs are supported for SSD-onlyaggregates and Flash Pool aggregates.

For information about which platforms and shelf types support these drives andaggregate types, see IBM System Storage N series Introduction and Planning Guide.

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



Support for SAS optical cablesData ONTAP 8.2.1 and later 8.2.x releases support SAS optical cables on N6200series and N7x50T series storage systems with SAS disk shelves using IOM6. DataONTAP 8.2.1 is the first release in the Data ONTAP 8.2 release family on whichSAS optical cables are supported.

More information can be found in the Hardware and Service Guides for EXN3000,EXN3200, and EXN3500, and in the Configuring a stretch MetroCluster system withSAS disk shelves and SAS optical cables document.

Support for shelf hot-removeData ONTAP 8.2.1 and later 8.2.x releases support the hot removal of diskshelves—the physical removal of disk shelves that have had the dataevacuated—in multipath HA or single-controller-dual-path (multipath) storagesystems that are up and serving data. You can hot remove one or more SAS or FCdisk shelves from anywhere within a stack or loop of disk shelves, or an entirestack or loop of disk shelves.

The following supported configurations and documents containing the shelfhot-remove procedure can be found on the IBM N series support site.:v Multipath HA and single-controller-dual-path storage systems with SAS disk

shelves: Hardware and Service Guides for EXN3000, EXN3200, and EXN3500v Stretch MetroCluster systems with SAS disk shelves and SAS optical cables:

Configuring a stretch MetroCluster system with SAS disk shelves and SAS opticalcables

v MetroCluster systems with FC disk shelves: Data ONTAP High Availability andMetroCluster Configuration Guide for 7-Mode

Manageability enhancementsThis release of Data ONTAP provides new and changed manageability capabilities.v “The system node service-processor commands now support the RLM”v “Licensing changes for the Data ONTAP 8.2 release family” on page 13v “New command family for managing the SP from Data ONTAP” on page 14v “AutoSupport enhancements” on page 14v “Enhancements to health monitoring” on page 15v “Messages in the /etc/messages file now include the system name” on page 15v “Options for specifying uppercase and lowercase requirements in user

passwords” on page 15

The system node service-processor commands now supportthe RLM

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

You can use the system node service-processor commands to perform thefollowing RLM management tasks:v Set up or modify the RLM network configuration (system node

service-processor network modify)



v Display the RLM network configuration (system node service-processornetwork show)

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

backup) to use (system node service-processor reboot-sp)v Display the details of the currently installed RLM firmware image (system node

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

service-processor image update-progress show)

Licensing changes for the Data ONTAP 8.2 release familyData ONTAP 8.2 introduces licensing changes that affect how you manage thelicenses of your storage system.

The following licensing changes apply to the Data ONTAP 8.2 release family:v How licensed features are mapped to packages has changed.

Data ONTAP feature licenses are issued as packages, each of which containsmultiple features or a single feature. A package requires a license key, andinstalling 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 thesystem to use all SnapManager products in the package.

v Data ONTAP no longer displays license states for individual features that arepart of a license package; instead, Data ONTAP manages and displaysentitlements at the license package level.

v A standard Data ONTAP license, also known as a node-locked license, is issued fora system with a specific serial number and is not valid on other systems.Installing a standard, node-locked license entitles the system to the licensedfunctionality.The Data ONTAP 8.2 release family treats a license installed prior to DataONTAP 8.2 as a standard license. Therefore, a system running Data ONTAP 8.2automatically has the standard license for the package that the previouslylicensed functionality is part of.

v 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 workafter you upgrade to Data ONTAP 8.2. However, if you need to reinstall alicense in Data ONTAP 8.2 (for example, you deleted a previously installedlicense and want to reinstall it in Data ONTAP 8.2, or you perform a controllerreplacement procedure for a system running Data ONTAP 8.2), Data ONTAPrequires that you enter the license key in the new, 28-character format.

Note: If you wipe clean a system and reinstall it with a version that is earlierthan Data ONTAP 8.2, you need to use a license key format that is supported forthe release that you are installing.

v Starting with Data ONTAP 8.2, the following functionality no longer requires alicense, 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 optionscf.mode to ha.

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


– SyncMirrorThere is no option that you need to enable.

v The task of replacing or upgrading a controller running Data ONTAP 8.2 mustbe done by an IBM System Services representative so that the license keys canbe properly transferred. You can validate that the license keys were properlytransferred by using the license show command.

v 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 SystemAdministration Guide for 7-Mode.

New command family for managing the SP from Data ONTAPStarting with Data ONTAP 8.2, the system node service-processor commands areavailable for managing the Service Processor (SP) from Data ONTAP. The sp andsoftware install commands are deprecated in favor of the new commands.

The system node service-processor commands replace the sp commands for thefollowing tasks:v Set up or modify the SP network configuration (system node service-processor

network modify)v Display the SP network configuration (system node service-processor network

show)v Display the SP information (system node service-processor show)v Reboot the SP and optionally specify the SP firmware image (primary or

backup) to use (system node service-processor reboot-sp)v Display the details of the currently installed SP firmware image (system node

service-processor image show)v Enable or disable the SP automatic firmware update (system node

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

service-processor image update)v 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 SPfirmware update. It is replaced by the system node service-processor imageupdate command.

AutoSupport enhancementsData ONTAP 8.2 supports several enhancements to the delivery of AutoSupportmessages.

AutoSupport On Demand enhances delivery of AutoSupportmessages

AutoSupport On Demand is a new AutoSupport feature that ensures that technicalsupport has the data it needs to provide quick incident resolution and preventativesupport.



AutoSupport On Demand periodically sends HTTPS requests to technical supportto obtain delivery instructions. The delivery instructions can include requests togenerate new AutoSupport messages, retransmit previously generated messages,and disable delivery of messages for specific trigger events. The requests go to thesame technical support location that AutoSupport messages are sent.

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

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

The fully qualified domain name is now sent to SMTP mailservers

When sending connection requests to SMTP mail servers, AutoSupport nowspecifies the fully qualified domain name of the node, if you configured DNS. Inprevious releases, AutoSupport specified only the host name.

Enhancements to health monitoringThe node connectivity health monitor now monitors SMB connections to ensurenon-disruptive operations to Hyper-V applications.

For more information about health monitoring, see the Data ONTAP SystemAdministration Guide for 7-Mode.

Messages in the /etc/messages file now include the systemname

Staring with Data ONTAP 8.2, messages in the /etc/messages file include thestorage system name. This change helps administrators of multiple systems seewhich system a given message came from.

Options for specifying uppercase and lowercase requirementsin user passwords

Starting with Data ONTAP 8.2, you can specify the minimum number of uppercaseor lowercase alphabetic characters that a password must contain.

You can use the following options to specify the requirements of uppercase orlowercase alphabetic characters in user passwords:v 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 uppercasecharacters.

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



High-availability pair enhancementsThis Data ONTAP release includes new features and enhancements relating to HApairs .v “Support for SSDs in a MetroCluster configuration”v “New cf.mode option replaces the cf license”v “Support for unidirectional port mirroring in a MetroCluster configuration”v “Support for ISL encryption in a MetroCluster configuration”

Support for SSDs in a MetroCluster configurationAggregates composed only of solid-state disks (SSDs) are supported inMetroCluster configurations.

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

New cf.mode option replaces the cf licenseIn Data ONTAP 8.2, the new cf.mode option replaces the requirement for the cflicense.

Support for unidirectional port mirroring in a MetroClusterconfiguration

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

To learn more about using unidirectional port mirroring, see the Data ONTAP HighAvailability and MetroCluster Configuration Guide for 7-Mode.

Support for ISL encryption in a MetroCluster configurationStarting with Data ONTAP 8.2.1, the MetroCluster configuration supports ISLencryption on Brocade 6510 switches.

For more information about ISL encryption, see the Data ONTAP High Availabilityand MetroCluster Configuration Guide for 7-Mode and Fabric-attached MetroClusterSystems Brocade Switch Configuration Guide.

Storage resource management enhancementsThis Data ONTAP release includes a number of enhancements for performance,resiliency, and management capabilities for storage resources.v “Aggregates can be expanded to 64-bit format without adding storage” on page

17v “Increased maximum Flash Pool cache sizes for N3150, N3220, and N3240

systems” on page 17v “Automated Workload Analyzer tool for Flash Pool cache sizing” on page 17v “Increased maximum aggregate size for some platforms” on page 17v “Multi-disk carrier and single-disk carrier disk shelves can be combined in the

same stack” on page 17



v “Flash Pool aggregates support different RAID types and group sizes for SSDcache”

v “Flexibility for calculating maximum Flash Pool SSD cache size in HAconfigurations” on page 18

v “Aggregate Snapshot copy automatic deletion is always enabled” on page 18v “Disabled volume guarantees no longer reenabled automatically” on page 18v “Fractional reserve setting can be set only to 0 or 100” on page 18

Aggregates can be expanded to 64-bit format without addingstorage

Starting with Data ONTAP 8.2.1, you can expand a 32-bit aggregate to the 64-bitformat without adding storage to the aggregate. Converting to the 64-bit formatenables you to use Data ONTAP features that require 64-bit aggregates, such ascompression and Flash Pool aggregates.

Increased maximum Flash Pool cache sizes for N3150, N3220,and N3240 systems

The maximum size for Flash Pool caches has increased in Data ONTAP 8.2.1. Todetermine the maximum Flash Pool cache size for your system model, see IBMSystem Storage N series Introduction and Planning Guide.

Automated Workload Analyzer tool for Flash Pool cache sizingStarting with Data ONTAP 8.2.1, the Automated Workload Analyzer (AWA) tool isavailable at the advanced privilege level. The AWA tool is enabled on an aggregateand provides real-time workload analysis to estimate the recommended Flash Poolcache size and to predict cache hit rates.

The AWA tool can be used on both Flash Pool aggregates and HDD-onlyaggregates. It can be used on a controller with a Flash Cache module installed.

Increased maximum aggregate size for some platformsThe maximum aggregate size has increased for some platforms in Data ONTAP8.2. For more information, see IBM System Storage N series Introduction and PlanningGuide.

Multi-disk carrier and single-disk carrier disk shelves can becombined in the same stack

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

Flash Pool aggregates support different RAID types and groupsizes for SSD cache

For earlier versions of Data ONTAP, the SSD cache always had the same RAIDtype 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 fromthe HDD RAID groups.



Flexibility for calculating maximum Flash Pool SSD cache sizein 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 asa whole, and can be split arbitrarily between the two nodes, provided that the totallimit for the HA configuration is not exceeded.

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

For more information about how Flash Pool cache capacity is calculated, see theData ONTAP Storage Management Guide for 7-Mode.

Aggregate Snapshot copy automatic deletion is alwaysenabled

In previous versions of Data ONTAP, you could disable aggregate Snapshot copyautomatic deletion. Starting in Data ONTAP 8.2, aggregate Snapshot copyautomatic deletion is always enabled and cannot be disabled.

You can control how many aggregate Snapshot copies are preserved by adjustingthe size of the aggregate Snapshot reserve. By default, the aggregate Snapshotreserve is set to 0 percent for newly created aggregates. If you are usingSyncMirror, you should keep your aggregate Snapshot reserve for that aggregateset to 5 percent or higher.

Disabled volume guarantees no longer reenabledautomatically

Starting with Data ONTAP 8.2, after more space becomes available Data ONTAPno longer automatically reenables the guarantee for volumes with disabledguarantees. This gives the administrator control over when a volume with adisabled guarantee consumes space to enable its guarantee.

Fractional reserve setting can be set only to 0 or 100In previous versions of Data ONTAP, you could set the fractional reserve settingfor 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 fractionalreserve settings are between 1 and 99, the fractional reserve setting for thosevolumes is set to 0.

Storage efficiency enhancementsThis Data ONTAP release includes a new enhancement for storage efficiencyenhancements. This section provides an overview of the enhancement.v “Support for detecting incompressible data in files”

Support for detecting incompressible data in filesData ONTAP 8.2 introduces the ability to check if a file is incompressible and forlarge files, you can check if a compression group within a file is incompressible.Incompressible data detection saves the system resources used by inlinecompression to compress incompressible data.



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

File access protocol enhancementsThis Data ONTAP release includes a number of new features and enhancementsfor file access and protocols management.v “Support for VMware vStorage over IPv6”v “Maximum ACE limit for NFSv4 ACLs has increased”v “Support for SMB 2.x authentication with CIFS workgroup mode”v “Enhancements for management of unresponsive LDAP servers”v “Enabling new EMS messages to help troubleshoot Kerberos issues” on page 20v “CIFS TCP window size increased to 64240 bytes” on page 20

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

Support for VMware vStorage over IPv6Beginning with Data ONTAP 8.2.1, VMware vStorage is also supported over IPv6networks.

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

Maximum ACE limit for NFSv4 ACLs has increasedThe maximum number of ACEs for each ACL has been increased to 1,024. Thisenables you to add significantly more ACEs to ACLs than in previous versions ofData ONTAP.

Support for SMB 2.x authentication with CIFS workgroupmode

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

For information about CIFS workgroup mode and CIFS authentication, see theData ONTAP File Access and Protocols Management Guide for 7-Mode.

Enhancements for management of unresponsive LDAPservers

Data ONTAP 8.2 and later releases enable administrators to better manage issuesrelated to unresponsive LDAP servers. Two new options are available.

All servers in the list of LDAP servers are contacted serially, and the first one tomake a successful connect and bind is used by the storage system. By default, ifthe LDAP server becomes unresponsive, LDAP requests fails after the bindtimeout. The default is a timeout of 30 seconds with three retries. If theldap.fast_time_out.enable option is on and an LDAP request times out, allrequests that have been in the queue longer than the bind timeout are failed. Thisallows Data ONTAP to quickly identify a complete LDAP failure and send errorresponses to its CIFS or NFS clients.



Two new options are available to manage the timeout settings. Both options takeeffect immediately and are persistent across reboots.v 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 failedLDAP server. The storage system waits for the number of seconds configured bythe ldap.retry_delay option before making another attempt to connect to LDAPservers. The default is on.

v ldap.retry_delay

The time, in seconds, to wait before trying to connect to LDAP servers after afailed attempt. Effective only if ldap.fast_timeout.enable is on. The range forthis 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 andProtocols Management Guide for 7-Mode.

Enabling new EMS messages to help troubleshoot Kerberosissues

New EMS messages have been added to Data ONTAP to help troubleshootKerberos 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 byentering the following command:options nfs.rpcsec.trace off

CIFS TCP window size increased to 64240 bytesIn Data ONTAP 8.2.1, the default CIFS TCP window size has increased from 17520bytes to 64240 bytes. For a new 8.2.1 installation, the TCP window size is 64240.This enhancement improves performance on high-bandwidth networks.

If you upgrade the physical storage system (vFiler0) to 8.2.1 or later, the defaultTCP window size is set to 64240 on all of the vFiler units, unless the value hasbeen modified explicitly.

If you revert the storage system to 8.2 or earlier, the default TCP window size isset to the previous default value unless the value has been modified explicitly.

The administrator can modify the default values to customized values. Forexample, if the administrator modifies the TCP window size to 28672 bytes byusing the cifs.tcp_window_size option, that value is retained across Data ONTAPupgrades and reversions.

Data protection enhancementsThis release of Data ONTAP provides new data protection features andenhancements.v “Support for multipath tape access” on page 21v “Support for Single SnapVault license” on page 21v “SyncMirror is enabled by default” on page 21v “Options for enabling the SnapLock functionality” on page 21



v “Automatic resizing of SnapMirror destination for a FlexVol volume”v “Users cannot perform certain Qtree SnapMirror and SnapVault tasks during the

post-upgrade operations”v “Serial numbers used for tape aliasing” on page 22

For more information about the new features and enhancements, see the DataONTAP Data Protection Tape Backup and Recovery Guide for 7-Mode and the DataONTAP Data Protection Online Backup and Recovery Guide for 7-Mode .

Support for multipath tape accessYou can configure multiple paths from the storage system to access tape drives in atape library. If one path fails, then the storage system can use the other paths toaccess tape drives without having to immediately repair the failed path. Thisensures that tape operations can be restarted.

For more information about multipath tape access, see the Data ONTAP DataProtection Tape Backup and Recovery Guide for 7-Mode

Support for Single SnapVault licenseStarting with Data ONTAP 8.2, you need not use separate license to enableSnapVault primary and SnapVault secondary. You must use the same SnapVaultlicense to enable both the SnapVault primary and SnapVault secondary.

SyncMirror is enabled by defaultStarting with Data ONTAP 8.2, you do not have to install the SyncMirror license asit is enabled by default.

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

For more information about enabling the SnapLock functionality, see the DataONTAP Archive and Compliance Management Guide for 7-Mode.

Automatic resizing of SnapMirror destination for a FlexVolvolume

Starting with Data ONTAP 8.2, if you increase the size of a SnapMirror sourceFlexVol volume and perform a SnapMirror transfer, the size of the SnapMirrordestination FlexVol volume automatically increases to that of the SnapMirrorsource FlexVol volume.

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

Users cannot perform certain Qtree SnapMirror and SnapVaulttasks during the post-upgrade operations

When you upgrade to Data ONTAP 8.2, Qtree SnapMirror and SnapVault performcertain post-upgrade tasks, as part of which, all restart checkpoints are cleared and



uninitialized relationships and qtrees are deleted. During this time, users will notbe able to perform any tasks on uninitialized relationships and qtrees, or onvolumes containing these qtrees.

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

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

Serial numbers used for tape aliasingA 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 insteadof the WWN. The alias remains the same regardless of the multiple connectionspaths to the tape drive or medium changer. This helps storage systems to track thesame tape drive or medium changer in a tape library configuration.

For more information about serial numbers, see the Data ONTAP Data ProtectionTape Backup and Recovery Guide for 7-Mode



Summary of new and changed commands and options in theData ONTAP 8.2 release family operating in 7-Mode

You need to know information about the commands, options, and configurationfiles that have been added to the Data ONTAP 8.2 release family operating in7-Mode.

These listings are not exhaustive. For detailed information about specificcommands and options, see the corresponding man pages.

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

For each command family and each command, the following table gives thisinformation:v The purpose of the commandv The location of documentation about the commandv The release in which the command was introduced

Command Purpose Documentation Release added

license show Displays information aboutinstalled licenses; replaces thelicense command.

Data ONTAP SystemAdministration Guide for 7-Mode

na_license(1) man page

8.2

nfs vstorage stats Displays various counters aboutVMware vStorage over NFSactivity on the storage system.

Data ONTAP File Access andProtocols Management Guide for7-Mode

8.2

rlm update-status Displays the RLM updateprogress.

na_rlm(1) man page 8.2

system health subsystemshow

Displays the health status ofsubsystems.

system_health_subsystem(1)man page

8.2



Command Purpose Documentation Release added

system nodeservice-processor

Manages the Service Processor (SP)and the Remote LAN Module(RLM):

v Setting up or modifying theremote management firmwarenetwork configuration

v Displaying the remotemanagement firmware networkconfiguration

v Displaying the remotemanagement device information

v Rebooting the remotemanagement device andoptionally specifying the remotemanagement firmware image(primary or backup) to use

v Displaying the details of theremote management firmwareimage that is currently installed

v Enabling or disabling the remotemanagement automaticfirmware update (supported forthe SP only)

v Manually updating the remotemanagement firmware andspecifying the update settings

v Displaying the status for thelatest remote managementfirmware update

man pages for system nodeservice-processor

8.2 for the SPsupport

8.2.1 for the RLMsupport

vol autosize grow_shrink Supports the volume autoshrinkcapability.

Data ONTAP StorageManagement Guide for 7-Mode

na_vol(1) man page

8.2

icunidirectional_mirroring

Allows you to enable or disablethe unidirectional port mirroring.

Data ONTAP High Availabilityand MetroCluster ConfigurationGuide for 7-Mode

na_vol(1) man page

8.2.1

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

For each command family and each command, the table provides the followinginformation:v Change in the commandv Location of documentation about the commandv Release in which the change was introduced



Command Change DocumentationRelease commandchanged in

aggr 64bit-upgrade start This command is nowavailable at theadvanced privilegelevel.

Data ONTAP Storage Management Guidefor 7-Mode

na_aggr(1) man page

8.2.1

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

na_aggr(1) man page 8.2

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


na_aggr(1) man page

8.2

aggr status The -S option wasadded. This optiondisplays detailedinformation abouthow space is used inthe aggregate.


na_aggr(1) man page

8.2

autosupport history show The -generated-onoption has beenadded. This optiondisplays AutoSupportmessages that weregenerated at aparticular time.

na_autosupport(1) man page 8.2

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

na_df(1) man page 8.2

license Deprecated andreplaced by thelicense showcommand.

na_license(1) man page 8.2

license add Accepts a list of 28digit upper-casealphanumericcharacter keys.

Data ONTAP System Administration Guidefor 7-Modena_license(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 25



license delete Requires the packagename when youdelete a license;requires confirmationto delete.

Data ONTAP System Administration Guidefor 7-Modena_license(1) man page

8.2

reallocate start The -u option hasbeen added. Thisoption duplicatesblocks that are sharedbetween files bydeduplication.

na_reallocate(1) man page 8.2

revert_to The -d option hasbeen added. Thisoption enables theadministrator toproceed withreverting DataONTAP after thebacklog ofasynchronous deleteoperations iscompleted.

na_revert_to(1) man page 8.2

sis config The -Q option hasbeen added. Thisoption enables theadministrator toenable or disableincompressible datadetection on avolume.

Data ONTAP Storage Management Guidefor 7-Modena_sis(1) man page

8.2

sis config The -z option hasbeen added. Thisoption enables theadministrator tospecify the minimumfile size to attemptquick check on a file.


8.2

sis start The -m option hasbeen added. Thisoption enables theadministrator to scanexisting data, generatededuplicationmetadata, and skipshared blocks.


8.2

sis start The -o option hasbeen added. Thisoption enables theadministrator to scanexisting data and skipshared blockoptimization.


8.2




snap list The -fs-block-formatoption has beenadded. This optionenables theadministrator todetermine whether32-bit formatSnapshot copies arepresent.

na_snap(1) man page 8.2.1

software install The software installcommand is replacedby the system nodeservice-processorimage updatecommand formanually updatingthe SP firmware.Note: The softwareinstall commandcontinues to supportthe RLM firmwareupdate.

The man page for system nodeservice-processor image update

8.2

sp This command familyhas been deprecatedin favor of the systemnodeservice-processorcommand family.

The man pages for system nodeservice-processor

8.2

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

na_sysconfig(1) man page 8.2

sysconfig This command nowreports unknown andunsupported shelftypes.

na_sysconfig(1) man page 8.2.1

system healthautosupport triggerhistory show

The optional-asup-enableparameter has beenadded. Thisparameter shows thealerts that did or didnot trigger anAutoSupportmessage.

na_system_health_autosupport(1) manpage

8.2




system health policydefinition modify

v The optional-asup-enableparameter has beenadded. Thisparameter specifieswhether the alertsgenerated by thespecified healthpolicy triggers anAutoSupportmessage.

v Changes to the-enable parameterare now persistentacross reboots.

na_system_health_policy(1) man page 8.2

system health policydefinition show

The optional-asup-enableparameter has beenadded. Thisparameter showshealth policies that door do not triggerAutoSupportmessages for alerts.

na_system_health_policy(1) man page 8.2

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


na_vol(1) man page

8.2

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


na_vol(1) man page

8.2

vol status The -F and -S optionswere updated toaccept thespecification of units(KB, MB, GB, TB).

na_vol(1) man page8.2.1

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

The following command is removed in Data ONTAP 8.2:v aggr show_space



Use the aggr status -S command to see space usage in the aggregate. Use thedf -hybrid command to see space usage in the SSD cache of a Flash Poolaggregate.

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

The table provides the following information about each new option that you canuse with the options command:v Purpose of the optionv Default value for the optionv Data ONTAP release in which the option was introduced

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

Option Purpose Default valueReleaseadded

autosupport.support.reminder Enables or disables a reminder message thatappears when autosupport.support.enableis set to off .Note: This option was previously hidden.

on 8.2

cf.giveback.auto.override.vetoes Overrides giveback vetoes. In previousversions of Data ONTAP, this option wasnamed cf.giveback.auto.terminate.bigjobs.

off 8.2

cf.mode Enables HA mode on the controller. The HAmode must be set on both controllers for theHA functionality.

This option replaces the requirement for a cflicense.

None. 8.2

coredump.savecore.warn Enables Data ONTAP to prompt forconfirmation when deleting unsaved corefiles.

off 8.2

disk.auto_assign_shelf Supports shelf-level disk autoassignment. off 8.2

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

off 8.2

ldap.fast_timeout.enable Controls the timeout behavior of LDAPclient operations.

on 8.2

ldap.retry_delay Sets the time, in seconds, to wait beforetrying to connect to LDAP servers after afailed attempt.

120 8.2

licensed_feature.snaplock.enable Enables the SnapLock Compliancefunctionality.

off 8.2

licensed_feature.snaplock_enterprise.enable

Enables the SnapLock Enterprisefunctionality.

off 8.2

nfs.rpcsec.trace Enables new EMS messages to helptroubleshoot Kerberos issues.

off 8.2



Option Purpose Default valueReleaseadded

raid.mix.hdd.disktype.capacity Enables mixing performance disks withdifferent Data ONTAP disk types in thesame aggregate.

on 8.2

raid.mix.hdd.disktype.performance Enables mixing capacity disks with differentData ONTAP disk types in the sameaggregate.

off 8.2

raid.mix.hdd.rpm.capacity Enables mixing capacity disks with differentspeeds when creating or adding toaggregates.

off 8.2

raid.mix.hdd.rpm.performance Enables mixing performance disks withdifferent speeds when creating or adding toaggregates.

on 8.2

snapvault.stale_config_cleanup_enableEnables or disables the cleanup of staleSnapVault configurations.

on 8.2

cf.remote_syncmirror.enable When set to on , enables the MetroClusterfunctionality.

off 8.2

security.passwd.rules.minimum.lowercase

Specifies the minimum number of lowercasealphabetic characters that a password mustcontain

0 8.2

security.passwd.rules.minimum.uppercase

Specifies the minimum number of uppercasealphabetic characters that a password mustcontain

0 8.2

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

For each option, the following table gives this information:v Name of the changed optionv Nature of the changev Release in which the change was introduced

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

Option ChangeReleasechanged

autosupport.cifs.verbose This option was removed. 8.2

cf.giveback.auto.terminate.bigjobs This option has been renamed ascf.giveback.auto.override.vetoes.

8.2

nfs.authsys.extended_groups_ns.queue_max The maximum limit for this option was changedto 640.

8.2

nfs.thin_prov.ejuke The default for this option was changed to on . 8.2

nfs.v4.id.allow_numerics The default for this option was changed to off . 8.2

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



Option ChangeReleasechanged

raid.disktype.enable This option was replaced by the following twooptions:

v raid.mix.hdd.disktype.capacity

v raid.mix.hdd.disktype.performance

8.2

raid.rpm.ata.enable This option was replaced byraid.mix.hdd.rpm.capacity. Setting it to onenables disk speed mixing for capacity disks.

8.2

raid.rpm.fcal.enable This option was replaced byraid.mix.hdd.rpm.performance. Setting it to offdisables disk speed mixing for performance disks.

8.2



Requirements for running Data ONTAP 8.2

You can verify whether you have the storage systems and firmware needed to run7-Mode software for the Data ONTAP 8.2 release family.

To determine the capacity and maximum volume size of your storage systemmodel, see IBM System Storage N series Introduction and Planning Guide.

Supported systemsYou need a supported storage system to run a release in the Data ONTAP 8.2release.

The following storage systems are supported:v N3220 and N3240 storage systemsv N3150v N6000 series systemsv N6200 series systemsv N7000 series systemsv N7x50T

Note: Gateway systems are not supported with the Data ONTAP 8.2.x releasefamily. For any queries related to support for gateway systems, contact your IBMN series sales representative.

All systems supported by the Data ONTAP 8.2 7-Mode release family can beconfigured as an HA pair.

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

The following storage systems are not supported beginning in Data ONTAP 8.2:v N3300 and N3600 storage systemsv N5200 and N5500 storage systemsv N5300 and N5600 storage systemsv N3400 storage systemsv N3700 storage systems

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

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

The following storage system components have firmware that sometimes requiresupgrading:



v Motherboard (also known as system or storage system firmware)v Disk drivesv Disk storage expansion unit

Storage system firmware

It is best to upgrade to the latest version of system firmware for your storagesystem. For the latest firmware, you can go to the IBM N series support website,which is accessed and navigated as described in “Websites” on page 1.

Note: The latest system firmware is included with Data ONTAP upgradepackages. For more information, see the Data ONTAP Upgrade and Revert/DowngradeGuide for 7-Mode.

Disk firmware

For information about the latest disk firmware, see the IBM N series supportwebsite, which is accessed and navigated as described in “Websites” on page 1.

Note: New disk firmware is sometimes included with Data ONTAP upgradepackages. For more information, see the Data ONTAP Upgrade and Revert/DowngradeGuide for 7-Mode.

Disk storage expansion unit and ESH firmware

For information about the latest disk storage expansion unit and ESH (EmbeddedSwitched Hub) firmware, see the IBM N series support website, which is accessedand navigated as described in “Websites” on page 1.



Important cautions

Before upgrading to this release of Data ONTAP, you need to read the importantcautions to identify and resolve issues that might affect the operation of yourstorage systems.v “Upgrade cautions”v “Manageability cautions” on page 37v “Storage management cautions” on page 39v “File access and protocols cautions” on page 39v “Revert and downgrade cautions” on page 41

Upgrade cautionsIf you are upgrading to this Data ONTAP release, you should review the cautionsand take appropriate action for any that apply in your environment.v “Release Candidate 1 not recommended for systems with high disk count”v “Change in how Data ONTAP handles file names containing UTF-16

supplementary characters” on page 36v “Compatible versions of management software are required” on page 36v “If you are using synchronous SnapMirror, upgrading to Data ONTAP 8.2 can

cause performance degradation” on page 36v “N6210 and N6040 systems with Flash Cache modules not supported” on page

11v “Modifying the state of deduplication during an intermediate upgrade can cause

storage system disruption” on page 37v “Disks offline in Windows Server 2008 and 2012 after Data ONTAP upgrade” on

page 37v “Stale metadata not automatically removed during deduplication operations on

volume” on page 37

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

Release Candidate 1 not recommended for systems with highdisk count

Systems with a high disk count are not suitable candidates for installing orupgrading to Data ONTAP 8.2.1 Release Candidate 1 (RC1).

While Data ONTAP 8.2.1 RC1 has additional features and fixes that bring benefitsfor many use cases, systems with a high disk count (greater than 550 disks per HApair) are not suitable candidates for this release. IBM N series advises customers tonot upgrade high disk count systems to 8.2.1 RC1, especially if applications in thatenvironment are sensitive to failover durations. This issue will be addressed by8.2.1 General Availability (GA).



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

Starting with Data ONTAP 8.2.1, there is a change in how Data ONTAP handlesfile names containing UTF-16 supplementary characters that you must be aware ofif your environment uses such file names.

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

When you create file names on the storage system that contain supplementarycharacters, Data ONTAP checks the surrogate pairs. If they are valid, Data ONTAPaccepts the file name. If they are invalid, Data ONTAP now rejects the file nameand returns an invalid file name error.

Compatible versions of management software are requiredAfter you upgrade to Data ONTAP 8.2 or later, the license-list-info ZAPI is nolonger supported. As a result, you must install Data ONTAP management softwareversions that are supported by Data ONTAP 8.2 or later.

The Data ONTAP management software affected by this change includes, but isnot limited to, the SnapDrive and SnapManager products, Virtual Storage Console,and Operations Manager products. For the complete list of affected Data ONTAPmanagement software, specific versions, and alerts, see the IBM N seriesinteroperability matrix website.

For the Data ONTAP API changes, including new and deprecated APIs, seeNMSDK API Documentation.

Third-party applications or scripts written to use the license-list-info ZAPI will failafter the upgrade to Data ONTAP 8.2 or later. Therefore, if you use third-partyapplications, you should contact the vendors to obtain an update that is supportedfor Data ONTAP 8.2 or later.

If you are using synchronous SnapMirror, upgrading to DataONTAP 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 thisissue, you should remain in Data ONTAP 8.1.x.

N6210 and N6040 systems with Flash Cache modules notsupported

N6210 and N6040 storage systems with Flash Cache modules are not supported inData ONTAP 8.2 and later 8.2.x releases operating in 7-Mode. You cannot upgradeto Data ONTAP 8.2 or later 8.2.x releases if you have Flash Cache modules enabledin your N6210 or N6040 systems.



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

Modifying the state of deduplication during an intermediateupgrade can cause storage system disruption

If you are upgrading to Data ONTAP 8.2 from a release earlier than Data ONTAP8.1, you must perform an intermediate upgrade. During the intermediate upgradeif you modify the state of deduplication on a volume, then storage systemdisruption can occur.

You can upgrade from Data ONTAP 7.3.x to Data ONTAP 8.0.2 or Data ONTAP8.0.3 and then to Data ONTAP 8.1.x. You might disable deduplication beforeupgrading from Data ONTAP 7.3.x and then enable deduplication after upgradingto Data ONTAP 8.1.x. If the next scheduled volume efficiency operation runs onthe volume before upgrading to Data ONTAP 8.2 , then storage system disruptioncan occur. However, if you upgrade to Data ONTAP 8.1.2 and enable deduplicationon the volume, then Data ONTAP generates an error message indicating theworkaround.

As a workaround for this issue, after upgrading to Data ONTAP 8.2, you must runthe sis starts -s command on the volume on which deduplication was disabledbefore initiating the intermediate upgrade.

Disks offline in Windows Server 2008 and 2012 after DataONTAP upgrade

During a Data ONTAP upgrade, LUNs are assigned new revision numbers.Windows Server 2008 and Windows Server 2012 interpret the LUNs with newrevision numbers as new disks and set them offline after a host reboot; this statusis shown in Windows management interfaces after the upgrade. Windows Server2003 ignores LUN revision numbers.

If the disks are offline, bring them online by using Windows disk managementtools or SnapDrive functionality.

You can work around this problem by setting the SAN policy to "Online All" priorto upgrading Data ONTAP. Use the Windows diskpart command to change theSAN policy. After you upgrade Data ONTAP, change the policy back to the defaultsetting of "Offline Shared".

Stale metadata not automatically removed duringdeduplication operations on volume

Stale deduplication-related metadata can exist in the FlexVol volumes andaggregates on your system, resulting in slow deduplication processing or yoursystems running out of space.

Your systems can experience this problem if you are upgrading from a DataONTAP 8.1 release prior to 8.1.2P4, if deduplication is enabled on any FlexVolvolume, and if a FlexVol volume or the associated aggregate is more than 70percent full.

Manageability cautionsIf you are a storage system administrator, you should familiarize yourself withthese manageability issues.v “If you reinstall a license key in Data ONTAP 8.2 or later, you must use the new

license key format” on page 38

Important cautions 37


v “Changes to SP firmware update methods”

If you reinstall a license key in Data ONTAP 8.2 or later, youmust use the new license key format

Starting with Data ONTAP 8.2, all license keys are 28 characters in length. Licensesinstalled prior to Data ONTAP 8.2 continue to work after you upgrade to DataONTAP 8.2 or later. However, if you need to reinstall a license when you arerunning Data ONTAP 8.2 or later, the old key is not accepted.

The Data ONTAP 8.2 release family accepts a license key only in the new,28-character format.

Changes to SP firmware update methodsStarting with Data ONTAP 8.2, a baseline SP firmware image is packaged with theData 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 thebaseline image. You do not need to download the baseline SP firmware imageseparately. If a new version of the SP firmware becomes subsequently available,you have the option to download it from the IBM N series support site and updatethe SP firmware to the downloaded version without upgrading the Data ONTAPversion.

Data ONTAP offers the following methods for managing SP firmware updates:v 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 firmwareupdate, provided that the SP firmware version bundled with Data ONTAP isnewer than the SP version running on the system.

– When you download a version of the SP firmware from the IBM N seriessupport site and the downloaded version is newer than the one that the SP iscurrently running

You have the option to disable the SP automatic update functionality by usingthe system node service-processor image modify command. However, it is bestto leave the functionality enabled. Disabling the functionality can result insuboptimal or nonqualified combinations between the Data ONTAP image andthe SP firmware image.

v Data ONTAP enables you to trigger an SP update manually and specify how theupdate should take place by using the system node service-processor imageupdate 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 thepackage file name. The system node image package show command displaysall package files (including the files for the SP firmware package) that areavailable 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 withthe 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 tothe factory default and clear contents of all logs maintained by the SP,including the event logs, IPMI logs, and forensics logs ( -clear-logs )

For information about the system node service-processor image updatecommand, see the man page.

v Data ONTAP enables you to display the status for the latest SP firmware updateby using the system node service-processor image update-progress showcommand.

Any existing connection to the SP is terminated when the SP firmware is beingupdated. This is the case whether the SP firmware update is automatic ormanually triggered.

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

Disk failures might increase for some disk models afterupgrading to this version of Data ONTAP

Starting with Data ONTAP 8.1.2, the software install or upgrade includes new diskshelf firmware versions for EXN1000 and EXN3000 disk shelves that provideenhanced disk error detection and prediction capabilities. Therefore, afterupgrading to this version of Data ONTAP, you might experience an increase in thenumber of disk failures for certain disk shelf and disk models.

Increased disk failures after upgrading to this version of Data ONTAP is expectedbehavior, especially if you are upgrading from a version of Data ONTAP that didnot include the new firmware versions. You should follow standard best practicesfor 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 anincreased failure rate after upgrading:

Storage enclosure Part number Output from sysconfig -a Capacity

EXN1000 45E1427 X269_SMOOS01TSSX 1 TB

95P5168 X268_SMOOST75SSX 750 GB

23R6227 X267_SMOOST50SSX 500 GB

23R2970 X262_SMOOST25SSX 250 GB

EXN3000 45E7973 X302_SMOOS01TSSM 1 TB

45E7969 X310_SMOOST50SSM 500 GB

File access and protocols cautionsIf your storage system is deployed in a NAS environment, you should review theimportant cautions regarding file access and protocols management and takeappropriate action before upgrading or reinstalling.v “CIFS startup might take several minutes after HA failover and giveback” on

page 40



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

CIFS startup might take several minutes after HA failover andgiveback

After an HA failover and giveback, the CIFS protocol might take several minutesto start up. If vFiler units are present, they might not be initialized for the durationof the CIFS startup time. The delay in CIFS startup is typically due to networkinfrastructure issues related to domain controllers and LDAP servers.

About this task

To ensure that the domain controllers, DNS servers, and LDAP servers areaccessible, it is recommended that you run the following tests on the partner nodefor which giveback is to be initiated before initiating a giveback. Successfulexecution of these commands does not guarantee that CIFS startup duringgiveback will occur quickly. The servers that are responding now might fail later torespond when giveback occurs.

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

Procedure1. Test domain controller connectivity and responsiveness by entering the

following command:cifs testdcIf the command fails, reconnect to a domain controller by using the cifsresetdc command. The cifs resetdc command terminates existing domaincontroller connections and then discovers available domain controllers andestablishes new connections.

2. Verify that the cifs resetdc command succeeded by entering the followingcommand:cifs domaininfoIf the command fails, identify and fix the domain connectivity issue beforeproceeding.

3. Test Active Directory LDAP connectivity by entering the following command:cifs adupdateIf the command fails, identify and fix the Active Directory LDAP issues beforeproceeding.

4. Look up the SID of a domain user for the domain to which the CIFS serverbelongs by entering the following command:wcc -s your_domain\user_accountIf the command fails, identify and fix the issue before proceeding.

5. Optional: If LDAP is configured for user mapping, run LDAP queries byentering the following commands:priv set advancedgetXXbyYY getpwbyname_r user_namegetXXbyYY getpwbyuid_r uidIf the commands fail, identify and fix the LDAP issues before initiatinggiveback.



Results

After you verify domain controller, DNS server, and LDAP server accessibility, youcan proceed with giveback.

Revert and downgrade cautionsIf you are reverting or downgrading from this release to an earlier release, youshould review the cautions and take appropriate action for any that apply in yourenvironment.v “Reverting to a release earlier than Data ONTAP 8.2 might require installation of

licenses for some features”v “Licensing implications for reverting a system that is shipped with Data ONTAP

8.2 or later to an earlier release”v “Downgrading or reverting to Data ONTAP 8.1 or earlier with a Flash Pool

aggregate root aggregate disables the system” on page 42v “SP firmware might require a downgrade if you revert or downgrade to an

earlier Data ONTAP release” on page 42v “Reverting to an earlier release of Data ONTAP when 32-bit volumes or

aggregate are converted to 64-bit format” on page 42v “ACLs containing more than 400 ACEs are dropped during revert” on page 42

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

Reverting to a release earlier than Data ONTAP 8.2 mightrequire installation of licenses for some features

If you gained access to licensed or entitled features by upgrading to Data ONTAP8.2 or later and these features required a license prior to Data ONTAP 8.2, youmight need to install a license after reverting. This is the case if a license was notpreviously installed for the release you revert to.

The licensing models for Data ONTAP 8.2 are different from earlier releases. Somefunctionality that required a license prior to Data ONTAP 8.2 might be availablefor free or as part of a package that you are licensed to install in Data ONTAP 8.2or later. If you did not install a license for the functionality prior to Data ONTAP8.2 and you revert to the earlier release, you might need to install a license so thatyou 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 youwithout a license. If you revert to a release earlier than Data ONTAP 8.2, you mustinstall a license to continue to use SyncMirror.

Licensing implications for reverting a system that is shippedwith Data ONTAP 8.2 or later to an earlier release

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

If your system is shipped with Data ONTAP 8.2 or later and you reinstall it with arelease 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 releasefamily. To obtain a license key for the reinstalled system, contact your IBM N seriesrepresentative.

Downgrading or reverting to Data ONTAP 8.1 or earlier with aFlash Pool aggregate root aggregate disables the system

If you configure a Flash Pool aggregate (an aggregate that contains both HDDs andSSDs) as your root aggregate and you want to downgrade or revert to any releaseof Data ONTAP earlier than 8.1.1, including 8.1, you must first move the rootaggregate to an HDD or SSD aggregate. Otherwise, your system will not boot afterthe downgrade or revert.

SP firmware might require a downgrade if you revert ordowngrade to an earlier Data ONTAP release

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

After the Data ONTAP revert or downgrade process is complete, you must takethe action to install an SP firmware version that is supported for the Data ONTAPversion you reverted or downgraded to. To learn which SP firmware versions aresupported by each Data ONTAP release and for instructions about downloadingand installing an SP firmware version, see the IBM N series support site.

Reverting to an earlier release of Data ONTAP when 32-bitvolumes or aggregate are converted to 64-bit format

After an upgrade, if you have converted the 32-bit volumes or aggregate to the64-bit format, you cannot revert the source and destination systems to an olderversion of Data ONTAP until you delete all of the Snapshot copies on both thesource and the destination volumes.

ACLs containing more than 400 ACEs are dropped duringrevert

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 inyour environment that contain more than 400 ACEs.

If you perform a file system revert to a Data ONTAP 8.1 release, any ACLscontaining 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 somecases workarounds to avoid these behaviors, have been identified.v “Manageability issues”v “Storage resource management issues”v “Network protocol issues” on page 45v “File access and protocols issues” on page 48v “Data protection issues” on page 52v “SAN administration issues” on page 53v “MultiStore issues” on page 53

Manageability issuesYou should be familiar with the known issues and limitations in the managementinterface that affect your ability to manage the storage system.v “Command typed in from one connection might be executed by a concurrent

connection”

These issues include problems with command behavior, command output, or errormessages presented in the Data ONTAP CLI or web interface and problems withUNIX or operating system commands used to interface with your storage system.

Command typed in from one connection might be executed bya concurrent connection

If the telnet.distinct.enable option is set to off, a command typed in from aconsole connection that is initiated through the remote management device (theRLM or the SP) might be executed by a concurrent SSH or Telnet connection to thestorage system.

When you access the storage system through a Telnet or SSH connection, and ifthere is an existing console session that is initiated through the remotemanagement device, pressing Enter on your Telnet or SSH session might execute acommand that has just been typed in but not yet executed from the concurrentconsole session. This behavior might happen even if you do not see the commandname on your Telnet or SSH session. This behavior might occur if thetelnet.distinct.enable option is set to off.

Storage resource management issuesYou should familiarize yourself with the storage resource management issues inthis release.v “Storage system disruption due to unavailability of asynchronous messages” on

page 44v “Out of space errors could be returned when fractional reserve is set to zero” on

page 44v “Disk-type mixing might occur even when disk type is specified” on page 45v “Read performance for mirrored aggregates not in a MetroCluster configuration

might be degraded” on page 45



Storage system disruption due to unavailability ofasynchronous messages

Storage system disruption occurs when there are no asynchronous messages thatcan 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 tothe block-sharing state machine. However, these asynchronous messages are notgiven back to the system after a successful deduplication operation. This reducesthe number of available asynchronous messages and when the deduplicationoperations drain all the messages, it leads to a storage system disruption.

Because the asynchronous messages are more in number (in the order ofthousands), it takes those many deduplication operations to drain all the messages.

You can fix this issue by rebooting the storage system. All the asynchronousmessages are reallocated once the storage system finishes rebooting. However, theissue is not completely avoided, because the subsequent deduplication operationsstart draining the asynchronous messages.

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

If you are configuring volumes with zero fractional reserve and you are usingcertain technologies or Data ONTAP features, you must take some extraprecautions to avoid out of space errors.

Setting fractional reserve to zero increases your storage utilization. However, anapplication accessing data residing in the volume could experience a data outage ifthe 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:v Deduplicationv Compressionv FlexClone filesv FlexClone LUNsv Virtual environments

If you are using one or more of these technologies with no fractional reserve, andyou need to prevent errors that can arise from running out of space, you must useall of the following configuration settings for the volume:v Volume guarantee of volume

v File or LUN reservations enabledv Volume Snapshot copy automatic deletion enabled with a commitment level of

destroy

Note: If your rate of change is high, in rare cases the Snapshot copy automaticdeletion could fall behind, resulting in the volume running out of space, evenwith all of the required configuration settings in use.

In addition, you can optionally use the volume autogrow capability to decrease thelikelihood of Snapshot copies needing to be deleted automatically. If you enablethe autogrow capability, you must monitor the free space in the associated



aggregate. If the aggregate becomes full enough that the volume is prevented fromgrowing, more Snapshot copies will probably be deleted as the free space in thevolume is depleted.

If you do not want to monitor aggregate free space or have Snapshot copiesautomatically deleted, you can set the volume's fractional reserve setting to 100.This requires more free space up front, but guarantees that data modificationoperations will succeed even when the technologies listed previously are in use.

Disk-type mixing might occur even when disk type isspecified

You can configure Data ONTAP to allow mixing of capacity or performance disktypes when creating or adding to aggregates. When you specify a disk type withthe -T parameter, if disk-type mixing is enabled, Data ONTAP might use anequivalent disk type rather than the type you specified.

Read performance for mirrored aggregates not in aMetroCluster configuration might be degraded

The cf_remote license is installed by default on all new N6200 series and N7x50Tseries storage systems for versions of Data ONTAP earlier than 8.2. If youupgraded to Data ONTAP 8.2 and are using mirrored aggregates that are not in aMetroCluster configuration, the presence of this license can reduce readperformance because data is read from only one plex.

You can recover from this situation by using the following command to disable thelicense (on both nodes for HA pairs ):options remote_syncmirror.enable off

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

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

For more information about these issues, see Data ONTAP Network ManagementGuide for 7-Mode.v “Error messages observed during change in the state of network interface

groups”v “SNMPv3 access might fail for an existing user” on page 46v “Existing traphosts fail to receive SNMP traps” on page 46v “The first VLAN configured over a port might bring the port down temporarily”

on page 46v “SnapMirror transfer cannot be blocked by using the

interface.blocked.mgmt_data_traffic option” on page 46v “Partner node might be unavailable during controller failover” on page 47v “Disabling fast path in some network environments” on page 47

Error messages observed during change in the state ofnetwork interface groups

If there is change in the state of the network interface groups, error messages aredisplayed multiple times on the Data ONTAP console.

Known problems and limitations 45


When the status of interface groups is up or down , you will see the followingerror messages in the storage system because of the change in the networkinterface state :

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

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

These error messages end with the following notification message:

All CIFS name registrations have completed for the local server.

SNMPv3 access might fail for an existing userSNMPv3 access might fail despite the user having the required permissions. Thisfailure might occur after a hardware change, which changes the System ID of thestorage system.

When you face this issue, perform one of the following tasks:v Change the password for the SNMPv3 userv Re-add the SNMPv3 user to your storage system

Existing traphosts fail to receive SNMP trapsIf an SNMP traphost is added or deleted, the existing SNMP traphosts stopreceiving SNMP traps.

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

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

snmp init 1

The first VLAN configured over a port might bring the portdown temporarily

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

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

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

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

In a single path SnapMirror transfer, you cannot use theinterface.blocked.mgmt_data_traffic option to block SnapMirror traffic frome0M on the destination storage system. You can use this option to blockSnapMirror transfer only on the source storage system.



To block traffic from e0M, all the storage systems must use a consistentconfiguration. You must ensure that routes to the destination storage systems donot use e0M, and that neither SnapMirror nor NDMP is configured to use an IPaddress that is assigned to e0M on a destination storage system.

Partner node might be unavailable during controller failoverWhen an interface name used for configuring the partner interface is applied as ahost name alias in the /etc/hosts file, and the interface name is used in anifconfig command, the host name gets resolved in the local host context and notthe partner context. This causes the partner node to be unavailable duringtakeover.

For example, while configuring the partner interface, the command fails duringcontroller failover in the following scenarios:

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

ifconfig ifgrp1 ifgrp1 netmask <netmask> partner ifgrp1

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

10.10.10.10 toaster ifgrp1

The command fails because the name lookup of the interface group ifgrp1 occursin 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:v

ifconfig ifgrp1 10.10.10.10 netmask <netmask> partner ifgrp1v

ifconfig ifgrp1 hostname-ifgrp1 netmask <netmask> partner ifgrp1You should also make the corresponding entry in the/etc/hosts file:

10.10.10.10 toaster-ifgrp1

Disabling fast path in some network environmentsFast path is enabled by default on all storage systems. However, you might have todisable fast path in certain environments in which fast path does not functionoptimally.

About this task

IP fast path is a mechanism that uses the network interface of an inbound requestto send the response quickly by bypassing a routing table lookup. Fast path isenabled by default for all TCP and NFS over UDP connections.

You might have to disable fast path if you are working in configurations of CiscovPC, HP NIC teaming, or asymmetric routing environments.



Procedure

To disable fast path, enter the following command:options ip.fastpath.enable off

File access and protocols issuesIf your storage system is deployed in a NAS environment, you should review theknown problems and limitations regarding file access and protocols managementand take appropriate action.v “Windows Security tab unavailable for shares with long UNC paths”v “Number of existing locks larger than the maximum allowed limit after

upgrade”v “CIFS client authentication fails if host name exceeds 16 characters” on page 49v “Excessive pending CIFS authentication requests can cause service disruption”

on page 49v “Microsoft Windows 7 and Windows 8 clients fail to rename files and

directories” on page 49v “Domain user unable to execute CLI commands” on page 50v “Client notification messages in Windows domains require NetBIOS” on page 50v “CIFS widelinks are not accessible from Mac clients” on page 50v “Effective style of qtrees created on an NTFS volume before configuring CIFS”

on page 50v “Data ONTAP permits deleting a file when an alternate data stream of the file is

in use” on page 51v “VAAI copy offload limitations when exporting datastore volumes with the

actual flag” on page 51v “NFS VAAI copy offload uses block copy if the volume does not have SIS

enabled” on page 51

Windows Security tab unavailable for shares with long UNCpaths

If the UNC path (\\servername\sharename\filepath) of the share contains morethan 256 characters (excluding the initial “\\” in the UNC path), then the Securitytab in the Windows Properties box is unavailable. This is a Windows client issuerather than a Data ONTAP issue.

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

Number of existing locks larger than the maximum allowedlimit after upgrade

When you upgrade a storage system from Data ONTAP 8.1.x to 8.2 or later, andthen use the lock status -n command, the resulting output might display a largernumber 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.



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

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

This behavior is expected and might only occur temporarily during an upgrade. Asthe client eventually releases locks, the number of current locks continues to dropuntil it is below the maximum limit. After that, the number of new current lockscan no longer exceed the maximum limit.

CIFS client authentication fails if host name exceeds 16characters

If a CIFS client with a NetBIOS name of more than 16 characters attempts toconnect to the storage system, the authentication fails.

The storage system log records the following error message: AUTH:SPNEGO-Couldnot 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 16characters so that it complies with NetBIOS specifications.

Excessive pending CIFS authentication requests can causeservice disruption

If domain controllers become unavailable to a vFiler unit, pending CIFSauthentication requests accumulate on the storage system. If the issue is notresolved, this can prevent other vFiler units on the storage system fromsuccessfully completing CIFS authentication requests.

Because a vFiler unit shares system resources with other vFiler units that are onthe storage system, pending CIFS authentication requests for a vFiler unit couldaffect resources available to other vFiler units.

Data ONTAP enables you to monitor pending CIFS authentication requests andtake corrective action if needed. It generates SNMP traps in the followingsituations:v The amount of pending CIFS authentication requests reaches 50 percent of total

possible requestsv 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 for7-Mode.

Microsoft Windows 7 and Windows 8 clients fail to renamefiles and directories

When a Microsoft Windows 7 or Windows 8 client accesses an SMB share withwidelinks enabled, it can fail intermittently to rename files and directories on the



mapped share. This can lead to a situation where attempts by Microsoft Officeapplications to save documents on the share fail.

This issue is caused by a bug in the Windows 7 and Windows 8 clients for which ahot fix is available from Microsoft. The bug is described and information abouthow to obtain the hot fix is provided in the Microsoft KB articles 2703610(Windows 7) and 2821663 (Windows 8). The KB articles also provide informationabout a workaround for this issue if you do not want to apply the hot fix.

Domain user unable to execute CLI commandsIf you log in to the storage system CLI as a domain user and enter the commandcifs gpupdate, all subsequently entered CLI commands on the currently activesession 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 requireNetBIOS

The Windows client notification feature used for client messaging, shutdownnotices, and vscan alerts requires NetBIOS over TCP to be enabled in Data ONTAP.

Similarly, NetBIOS over TCP must be enabled on Windows clients and theWindows Messenger service must be running.

By default, the Windows Messenger service is disabled on Windows 2003 andWindows XP SP2 clients.

CIFS widelinks are not accessible from Mac clientsWhen a user attempts to connect to a share using widelinks from a Mac OS Xclient, the attempt fails. Widelinks are not accessible from Mac OS X clients.

Windows clients make a Distributed File System (DFS) referral request after DataONTAP returns the special error code STATUS_PATH_NOT_COVERED. The CIFSwidelink feature uses this behavior in its implementation. In its DFS response, DataONTAP can provide a referral that is configured by an administrator. The mappedreferral allows a CIFS client to follow a UNIX symlink.

Although Mac OS supports DFS, Mac OS clients do not behave exactly likeWindows clients in the way they handle the special DFS error code. Apple bug13870704 has been created to document and track the issue. Customersencountering this issue with Mac support for widelinks should contact Appleregarding this bug.

Effective style of qtrees created on an NTFS volume beforeconfiguring CIFS

On a newly installed storage controller without CIFS configured, if you create aqtree on a volume that has security style set to NTFS, the resulting qtree has NTFS



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

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

as the security style and UNIX as the effective style. This means that UNIX clientscan 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 forNTFS only. You must avoid setting the security style of a volume to NTFS beforeconfiguring CIFS on a newly installed storage system.

You can change the effective style of a qtree to NTFS by using the followingcommand:qtree security qtree path ntfs

For more information about setting the security styles for qtrees, see the DataONTAP File Access and Protocols Management Guide for 7-Mode.

Data ONTAP permits deleting a file when an alternate datastream of the file is in use

Data ONTAP differs with Microsoft servers in its handling of deleting a file withalternate data streams attached. Data ONTAP allows deleting a file when analternate data stream of the file is in use.

In contrast, Microsoft servers disallow deleting a file that has any of its datastreams open.

VAAI copy offload limitations when exporting datastorevolumes 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, VMwarevStorage over NFS has a copy offloading limitation when exporting datastorevolumes with the actual flag.

If you export a datastore volume with the actual flag, the export path should havea 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 thefollowing:

sys1> exportfs -p actual=/vol/VAAI,root=192.168.42.227 /vol/VAAI-ALIAS

NFS VAAI copy offload uses block copy if the volume doesnot have SIS enabled

The copy offload feature provided by the NFS Plug-in for VMware VAAI results ina block copy if a FlexVol volume that backs an NFS datastore has never had SISenabled, or if the sis undo command has been run against it. Normally, the NFSVAAI copy offload feature uses a FlexClone copy operation to perform a fast andspace-efficient copy. If SIS is not enabled on the volume containing the source anddestination files, the copy offload defaults to using a block copy.

This issue has been seen only on storage systems running Data ONTAP operatingin 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 VirtualStorage Console for VMware vSphere, it by default enables SIS on datastorevolumes.

Volume with SIS enabled

This example uses the sis on command to enable the VAAI_SIS volume for copyoffloading and deduplication. It then uses the vol status command to verify thechange and show that sis is listed for the volume VAAI_SIS:

NetApp1> sis on /vol/VAAI_SISNetApp1> vol status

Volume State Status Optionsvol0 online raid_dp, flex root

64-bitVAAI_SIS raid_dp, flex

sis64-bit

Data protection issuesIf you use data protection products that include Snapshot technology (such asSnapRestore, SnapVault, SnapMirror, and SnapManager), you might have tofamiliarize yourself with relevant data protection issues.

For more information about these issues, see the Data ONTAP Data ProtectionOnline Backup and Recovery Guide for 7-Mode and the Data ONTAP Data ProtectionTape Backup and Recovery Guide for 7-Mode.v “SnapVault cannot be enabled on vFiler units when SnapLock for SnapVault

relationships are present in vfiler0”v “SMTape operations abort if you turn off SnapMirror”v “SMTape restore to an offline volume overwrites the data on that volume” on

page 53v “DAR fails if the file and the LUN have the same name on the destination

volume” on page 53

SnapVault cannot be enabled on vFiler units when SnapLockfor SnapVault relationships are present in vfiler0

When you create SnapVault relationships for SnapLock secondary volumes invfiler0, you also manually set the snapvault.lockvault_log_volume option to thename of a SnapLock for SnapVault log volume. After this option is set, SnapVaultcannot be enabled on any vFiler units on the storage system. For more informationabout the snapvault.lockvault_log_volume option, see the na_snapvault(1) manpage.

SMTape operations abort if you turn off SnapMirrorIf you turn off SnapMirror while performing SMTape backup and restoreoperations, SMTape operations such as smtape backup and smtape restore areaborted.



SMTape restore to an offline volume overwrites the data onthat volume

If you perform an SMTape restore to an offline volume, the data on tapeoverwrites the data on that offline volume.

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

When DAR (Direct Access Recovery) of a file whose file name is the same as aLUN name on the destination volume is performed, then the DAR fails. For asuccessful restore, perform DAR of the file again.

SAN administration issuesIf your storage systems are part of a SAN environment, you might need tofamiliarize yourself with SAN administration issues in this release.v “Some Oracle Linux systems using ASMlib fail to recognize disk groups when

upgrading Data ONTAP”

For more information about these issues, see the Data ONTAP SAN AdministrationGuide for 7-Mode.

Some Oracle Linux systems using ASMlib fail to recognizedisk groups when upgrading Data ONTAP

After upgrading to Data ONTAP 8.0.4 and 8.1.1, 8.2.0 or later releases, some OracleLinux-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 blockin the LUN.

For more information, see the KB article Oracle ASMlib reports ASM diskgroup hasinconsistent sector size following a Data ONTAP upgrade.

The following two workarounds are available for this issue:v Oracle recommends bypassing ASMlib by setting ASM_DISKSTRING as shown

below:ASM_DISKSTRING = ’/dev/oracleasm/disks/*’

v It is recommended to use the "lun set" command to disable thereport-physical-size option for the affected LUNs. For more information aboutthe report-physical-size option, see the man page for the lun set command.

MultiStore issuesYou should familiarize yourself with the MultiStore issues in this release.v “Online migration of vFiler units is not supported on Flash Pools” on page 54

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



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

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

Online migration of vFiler units is not supported on FlashPools

You cannot perform online migration of vFiler units if a source vFiler unit hasvolumes on Flash Pools or a Flash Pool is selected on the destination storagesystem for online migration.



Changes to published documentation

Some information about this release has become available after the set of guidesprovided with this release were published. The information should be used inconjunction with the guides provided with this release of Data ONTAP.v “Changes to the Commands Manual Page Reference”v “Changes to the File Access and Protocols Management Guide”v “Changes to the System Administration Guide” on page 56

Changes to the Commands Manual Page ReferenceNew information has become available since the previous revision of the DataONTAP Commands: Manual Page Reference.

Missing options in the 7-Mode Command Reference GuideSome options are missing in the Data ONTAP Commands: Manual Page Reference for7-Mode, Volume 1 .

The missing options are as follows:

Option Purpose Default value

coredump.savecore.warn Enables Data ONTAP to prompt forconfirmation when deleting unsavedcore files

off

licensed_feature.snaplock_enterprise.enable Enables the SnapLock Enterprisefunctionality

off

licensed_feature.snaplock.enable Enables the SnapLock Compliancefunctionality

off

nfs.authsys.extended_groups_ns.queue_max Controls the maximum number ofrequests that can be queued at anygiven time to obtain the GIDs fromthe name service

80

Note: The maximum limit for nfs.authsys.extended_groups_ns.queue_max waschanged to 640 .

Changes to the File Access and Protocols Management GuideNew information has become available since the previous revision of the DataONTAP File Access and Protocols Management Guide for 7-Mode.

Managing anonymous FTP access requires additional stepThe instructions for managing anonymous FTP access in the Data ONTAP FileAccess and Protocols Management Guide for 7-Mode require an additional step toauthenticate the anonymous user.

To allow FTP access by the anonymous user, you must also add an entry for theanonymous 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 andProtocols Management Guide for 7-Mode.

Kerberos configuration topic mentions outdated encryptionalgorithm

The topic “Creating and copying Kerberos configuration files” in the Data ONTAPFile Access and Protocols Management Guide for 7-Mode describes how to createKerberos configuration files and provides examples. The examples refer to anoutdated encryption algorithm that should no longer be used.

The CLI command examples used in the topic refer to an encryption algorithm thatis considered insecure and obsolete, and therefore should not be used.

When following these instructions, you should first decide which contemporaryencryption algorithm is best suited for your environment and compose the CLIcommands to configure Kerberos accordingly.

Terminating and restarting CIFS on a volumeYou can terminate and restart CIFS on a volume by using the advanced -vparameter with the cifs terminate and cifs restart commands, respectively.Terminating a volume is not persistent across reboots.

About this task

For example, if you are migrating data in a volume or restoring files from aSnapshot copy, you can terminate and restart CIFS connections on that volumeinstead of on the entire storage system.

For more information, see the man pages for the cifs terminate and cifs restartcommands in the Advanced Commands section. Also see the “Disabling CIFS forthe entire storage system” topic in the Data ONTAP File Access and ProtocolsManagement Guide for 7-Mode.

Procedure1. Set the privilege level to advanced:

priv set advanced

2. To terminate CIFS service for a volume, enter the following command:cifs terminate -v vol

vol is the name of the volume for which you want to terminate CIFS service.3. To restart CIFS service for a volume, enter the following command:

cifs restart -v vol

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



Changes to troubleshooting AutoSupport over SMTPIn the topic titled “Troubleshooting AutoSupport over SMTP,” the informationabout using thedns infocommand should say that you use it to enable and configure the storage system.

Changes to published documentation 57


Copyright and trademark information

This section includes copyright and trademark information, and important notices.

Copyright information

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

Portions copyright © 2014 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restrictedby GSA ADP Schedule Contract with IBM Corp.

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

References in this documentation to IBM products, programs, or services do notimply that IBM intends to make these available in all countries in which IBMoperates. Any reference to an IBM product, program, or service is not intended tostate or imply that only IBM's product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe any ofIBM's or NetApp's intellectual property rights may be used instead of the IBM orNetApp product, program, or service. Evaluation and verification of operation inconjunction with other products, except those expressly designated by IBM andNetApp, are the user's responsibility.

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

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

THIS SOFTWARE IS PROVIDED BY NETAPP “AS IS” AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. IN NO EVENTSHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED 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 IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time,and without notice. NetApp assumes no responsibility or liability arising from theuse 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 anypatent rights, trademark rights, or any other intellectual property rights of NetApp.

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

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) of theRights in Technical Data and Computer Software clause at DFARS 252.277-7103(October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. A complete and current list of other IBM trademarks is available on theWeb at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

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, Gofurther, 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 UnitedStates, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

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

NetApp NetCache is certified RealSystem compatible.



Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe on any IBM intellectual property rightmay be used instead. However, it is the user's responsibility to evaluate and verifythe operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of expressor implied warranties in certain transactions, therefore, this statement may notapply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of those websites. The materials at those web sites are not part of the materials for this IBMproduct and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments may



vary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.



��

NA 210-06399_A0, Printed in USA

SC27-5938-04


ibm system storage n series data ontap 8.2.1 rc1 release ...€¦ · iv ibm system storage n...

Documents