data ontap 8.1.2 release notes for 7-mode - ibm · 2016-03-14 · appliances and gateway systems,...

IBM System Storage N series

Data ONTAP 8.1.2 Release Notes for7-Mode

GA32-1032-07

��

Contents

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

Changes introduced since Data ONTAP 8.1 . . . . . . . . . . . . . . . . . . . . 3Changes in Data ONTAP 8.1.2 for 7-Mode . . . . . . . . . . . . . . . . . . . . . 3Changes in Data ONTAP 8.1.1 for 7-Mode . . . . . . . . . . . . . . . . . . . . . 6

Unsupported features . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

New and changed features in the Data ONTAP 8.1 release family. . . . . . . . . . . . 15New and changed platform and hardware support . . . . . . . . . . . . . . . . . . 16

Support for the N3220 and N3240 platforms . . . . . . . . . . . . . . . . . . . 16Support for systems with only SSDs . . . . . . . . . . . . . . . . . . . . . . 16Support for 900-GB SAS disks . . . . . . . . . . . . . . . . . . . . . . . . 16Support for IOM6 (FC2099) for the EXN3000 storage expansion unit . . . . . . . . . . . 16Support for the EXN3200 storage expansion unit . . . . . . . . . . . . . . . . . 16Support for SAS tape drives . . . . . . . . . . . . . . . . . . . . . . . . 16Systems including EXN2000 storage expansion units with ESH2 modules . . . . . . . . . 17Support for FC/SAS bridge (ATTO for IBM FibreBridge 6500N) . . . . . . . . . . . . 17

Manageability enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 18Storage resource management enhancements . . . . . . . . . . . . . . . . . . . . 27High-availability pair (formerly active/active configuration) enhancements . . . . . . . . . . 30Networking and security protocol enhancements . . . . . . . . . . . . . . . . . . 32File access protocol enhancements . . . . . . . . . . . . . . . . . . . . . . . 35SAN enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Data protection enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 41Storage efficiency enhancements . . . . . . . . . . . . . . . . . . . . . . . . 43MultiStore enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . 45Gateway enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

New and changed features in the Data ONTAP 8.0 release family. . . . . . . . . . . . 49New and changed platform and hardware support . . . . . . . . . . . . . . . . . . 50

Support for the N6200 series . . . . . . . . . . . . . . . . . . . . . . . . 50Support for the N7x50T system . . . . . . . . . . . . . . . . . . . . . . . 50Support for 1-TB Flash Cache modules . . . . . . . . . . . . . . . . . . . . . 50Support for 512-GB and 256-GB Performance Acceleration Module (PAM II) . . . . . . . . 50Support for SSDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Supported tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . 51Support for 3-TB SATA disks . . . . . . . . . . . . . . . . . . . . . . . . 51Support for 2-TB SATA disks . . . . . . . . . . . . . . . . . . . . . . . . 51

Changes in storage expansion unit support . . . . . . . . . . . . . . . . . . . . 52Support for EXN3500 storage expansion units . . . . . . . . . . . . . . . . . . 52Support for EXN3000 storage expansion units . . . . . . . . . . . . . . . . . . 52

Manageability enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 53Reversion and downgrade support . . . . . . . . . . . . . . . . . . . . . . 53Default security settings for manageability protocols . . . . . . . . . . . . . . . . 53

© Copyright IBM Corp. 2013 iii

Requirement to set root account password. . . . . . . . . . . . . . . . . . . . 54Uses of the systemshell and the diagnostic account . . . . . . . . . . . . . . . . . 54Boot menu enhancements and changes . . . . . . . . . . . . . . . . . . . . . 55Supported OpenSSH client versions . . . . . . . . . . . . . . . . . . . . . . 55Root aggregate Snapshot reserve values reduced . . . . . . . . . . . . . . . . . 55

Storage resource management enhancements . . . . . . . . . . . . . . . . . . . . 56Support for 64-bit aggregates . . . . . . . . . . . . . . . . . . . . . . . . 56Data compression support . . . . . . . . . . . . . . . . . . . . . . . . . 56File space utilization report . . . . . . . . . . . . . . . . . . . . . . . . . 57Upgrading to Data ONTAP 8.0.1 increases volume capacity after deduplication . . . . . . . 57Maximum simultaneous FlexClone file or FlexClone LUN operations per storage system . . . . 57Support for FlexClone files and FlexClone LUNs on vFiler units . . . . . . . . . . . . 57Increased maximum RAID group size for SATA disks . . . . . . . . . . . . . . . . 57Ability to decrease maxfiles. . . . . . . . . . . . . . . . . . . . . . . . . 57

High-availability pair enhancements . . . . . . . . . . . . . . . . . . . . . . . 58HA pair terminology changes . . . . . . . . . . . . . . . . . . . . . . . . 58

Networking and security protocol enhancements . . . . . . . . . . . . . . . . . . 58Ability to block data traffic on the e0M interface . . . . . . . . . . . . . . . . . 58Support for CDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Port-based load-balancing option for multimode interface groups . . . . . . . . . . . . 59TSO in NICs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6064-bit SNMP object identifiers (OIDs) are supported . . . . . . . . . . . . . . . . 60Configuration for receiving untagged traffic on VLAN tagged interfaces. . . . . . . . . . 60Vifs are now known as interface groups . . . . . . . . . . . . . . . . . . . . 61

File access protocol enhancements . . . . . . . . . . . . . . . . . . . . . . . 61Support for multiple open instances of the SMB named pipe on an FPolicy server . . . . . . 61

Block protocol enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 61iSCSI RADIUS support . . . . . . . . . . . . . . . . . . . . . . . . . . 62Support for Data Motion for Volumes . . . . . . . . . . . . . . . . . . . . . 62VMware VAAI features for ESX hosts support . . . . . . . . . . . . . . . . . . 62igroup scalability limits . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Data protection enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 63SnapVault update schedules for volume SnapMirror destination backups . . . . . . . . . 63Support for 840 disk drives on fabric-attached MetroCluster configuration . . . . . . . . . 64Support for out-of-order frame delivery for SnapMirror over Fibre Channel . . . . . . . . 64Support for SnapMirror relationship between two FlexClone volumes . . . . . . . . . . 64Support for SnapMirror network compression . . . . . . . . . . . . . . . . . . 65Support for designated range of ports for NDMP data connections . . . . . . . . . . . 65If volumes with deduplication exceed the maximum supported size . . . . . . . . . . . 65NearStore license is not required for deduplication . . . . . . . . . . . . . . . . . 65Maximum concurrent deduplication operations supported . . . . . . . . . . . . . . 65Prerequisite for backing up data to tape using NDMP services . . . . . . . . . . . . . 65Snapshot copy schedules . . . . . . . . . . . . . . . . . . . . . . . . . 66SnapMirror support for 64-bit volumes . . . . . . . . . . . . . . . . . . . . . 66SnapVault support for 64-bit volumes . . . . . . . . . . . . . . . . . . . . . 66

Changes to the Data ONTAP and gateway libraries. . . . . . . . . . . . . . . . . . 67

New and changed commands and options in the Data ONTAP 8.1 release family operating in7-Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69New commands in the Data ONTAP 8.1 release family . . . . . . . . . . . . . . . . 69

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

Changed commands in the Data ONTAP 8.1 release family . . . . . . . . . . . . . . . 74Replaced or removed commands in the Data ONTAP 8.1 operating in 7-Mode release family. . . . 80New options in the Data ONTAP 8.1 release family. . . . . . . . . . . . . . . . . . 80Changed options in Data ONTAP 8.1 release family . . . . . . . . . . . . . . . . . 86

New and changed commands and options in the Data ONTAP 8.0 7-Mode release. . . . . . 89New commands in Data ONTAP 8.0 7-Mode . . . . . . . . . . . . . . . . . . . . 89Changed commands in the Data ONTAP 8.0 7-Mode release family . . . . . . . . . . . . 93Replaced or removed commands in the Data ONTAP 8.0 7-Mode release family . . . . . . . . 96New options in the Data ONTAP 8.0 7-Mode release family . . . . . . . . . . . . . . . 97Changed options in the Data ONTAP 8.0 7-Mode release family . . . . . . . . . . . . . 99

Requirements for running Data ONTAP 8.1 7-Mode . . . . . . . . . . . . . . . . 101Storage system firmware . . . . . . . . . . . . . . . . . . . . . . . . . . 102Gateway requirements and support information . . . . . . . . . . . . . . . . . . 103

Important cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Upgrade and revert cautions . . . . . . . . . . . . . . . . . . . . . . . . . 106Setup cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Manageability cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Storage management cautions . . . . . . . . . . . . . . . . . . . . . . . . 116Network protocol cautions. . . . . . . . . . . . . . . . . . . . . . . . . . 119File access and protocols cautions . . . . . . . . . . . . . . . . . . . . . . . 120SAN administration cautions . . . . . . . . . . . . . . . . . . . . . . . . . 122Data protection cautions . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Known problems and limitations. . . . . . . . . . . . . . . . . . . . . . . 125Manageability issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Storage resource management issues . . . . . . . . . . . . . . . . . . . . . . 130Network protocol issues . . . . . . . . . . . . . . . . . . . . . . . . . . 132File access protocol issues . . . . . . . . . . . . . . . . . . . . . . . . . . 134SAN administration issues . . . . . . . . . . . . . . . . . . . . . . . . . 139Data protection issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Third-party storage issues (Gateway systems only) . . . . . . . . . . . . . . . . . 143MultiStore issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Changes to published documentation . . . . . . . . . . . . . . . . . . . . . 145

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 153Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Contents v

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

Data ONTAP 8.1.2 for 7-Mode Release Notes

These Release Notes describe new features, enhancements, and known issuesfor this release of Data ONTAP, as well as additional information related torunning this release on specific storage systems.

About the Data ONTAP 8.1.2 release

Data ONTAP 8.1.2 is a General Availability (GA) release and the secondmaintenance release in the Data ONTAP 8.1.x release family. For moreinformation about Data ONTAP releases, refer to the following publication:

IBM System Storage N series Data ONTAP Release Model

For up to date information regarding the latest release of Data ONTAP, referto the following publication:

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

Attention: If you have an N6210 or an N6040 storage system with FlashCache modules, Data ONTAP 8.1.2 reenables the 256-GB Flash Cache moduleon the N6210 or N6040 storage systems using the full capacity forwear-leveling and cache storage. However, to deliver on the full value of DataONTAP 8.1.2, the maximum working dataset in the 256-GB Flash Cachemodule on N6210 or N6040 storage systems is 128 GB.

For more information, see “N6210 series and N6040 series storage systemswith Flash Cache modules are supported” on page 110.

For a complete list of functionality changes introduced in this release, see“New and changed features in the Data ONTAP 8.1 release family” on page15. If you are upgrading from a Data ONTAP 7.3.x release, see also “New andchanged features in the Data ONTAP 8.0 release family” on page 49.

Some Data ONTAP features are not supported in this release. For moreinformation, see “Unsupported features” on page 13.

About these release notes

All the information in this document applies to the Data ONTAP 8.1.2 releaseand later for N series storage systems, also sometimes called filers or

© Copyright IBM Corp. 2013 1

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

appliances and gateway systems, except where otherwise indicated.

It is a best practice for all Data ONTAP users to see the following sections:v If Data ONTAP is already running on storage systems in your environment,

you should familiarize yourself with relevant topics before upgrading toData ONTAP 8.1.2.This information helps you identify and resolve issues that might affect theavailability of your systems. Check the online version of the Release Notesperiodically for new cautions or updates that might have been posted sinceyou downloaded your software.

v “Changes to published documentation” on page 145 in these Release Notes.This release information became available after the set of guides providedwith this release were published.

Websites

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

at the following web page:www.ibm.com/storage/nas

v The IBM System Storage N series support website requires users to registerin order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important 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 theIBM N 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, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

2 IBM System Storage N series: Data ONTAP 8.1.2 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.1

You can find information about the changes that were introduced with eachrelease since Data ONTAP 8.1.

Note: If you are new to the Data ONTAP 8.1 family, go directly to “New andchanged features in the Data ONTAP 8.1 release family” on page 15.

Changes in Data ONTAP 8.1.2 for 7-Mode

This release includes support for new enhancements.

New and changed features in Data ONTAP 8.1.2

New and changed features include the following:v “Manageability enhancements” on page 18

– “Options for specifying uppercase and lowercase requirements in userpasswords” on page 18

v “High-availability pair (formerly active/active configuration)enhancements” on page 30– “Automatic giveback after takeover due to panic” on page 30

v “File access protocol enhancements” on page 35– “SMB 2.1 disabled by default in Data ONTAP 8.1.2” on page 35– “Support for the “Manage Auditing and Security Logs” GPO” on page

35– “Support for the Windows “Owner Rights” security principal” on page

36– “Enabling new EMS messages to help troubleshoot Kerberos issues” on

page 36v “Gateway enhancements” on page 47

– “Support for EMC VNX storage arrays” on page 47– “Support for third-party storage array advanced features” on page 47

For information about all new and changed features in this release, see “Newand changed features in the Data ONTAP 8.1 release family” on page 15.

New commands in Data ONTAP 8.1.2

The following new commands are added to this release:


v bmc battery-info

v nfs vstorage stats

For more information, see “Changed commands in the Data ONTAP 8.1release family” on page 74

Changed commands in Data ONTAP 8.1.2

The following commands changed in this release:v halt

v setup

New options in Data ONTAP 8.1.2

The following new options are added to this release:v cf.giveback.auto.after.panic.takeover

v nfs.rpcsec.trace

v security.passwd.rules.minimum.lowercase

v security.passwd.rules.minimum.uppercase

For more information, see “New options in the Data ONTAP 8.1 releasefamily” on page 80

Changed options in Data ONTAP 8.1.2

The following options changed in this release:v cf.giveback.auto.attempts.minutes

v cf.giveback.auto.attempts.count

v cf.giveback.auto.delay.seconds

v nfs.authsys.extended_groups_ns.queue_max

v nfs.v4.id.allow_numerics

New cautions in Data ONTAP 8.1.2

The following new cautions are added in this release:v “Upgrade and revert cautions” on page 106

– “Upgrade from 7.3.x to 8.1.x through intermediate upgrade withdeduplication disabled can cause a system panic” on page 109

– “Revert from Data ONTAP 8.1.x to Data ONTAP 8.0.x fails if fingerprintdatabase size exceeds 256 GB” on page 114

– “Downgrading to Data ONTAP 8.1 or earlier with a Flash Pool rootaggregate disables the system” on page 114


v “Storage management cautions” on page 116– “Disk failures might increase for some disk models after upgrading to

this version of Data ONTAP” on page 117– “Accessing data in a Snapshot copy causes a system disruption under

certain conditions” on page 118

Cautions removed in Data ONTAP 8.1.2

The following cautions have been removed in this release:v Automatic background disk firmware updates not enabled for non-mirrored

RAID4 aggregatesv System panics when Flash Cache is full and the root volume is a traditional

volumev Preventing service disruption when expanding an aggregate with volumes

using quotasv Changing the language of a FlexVol volume when expansion scanner is

running could result in system disruptionv CIFS setup via ONTAPI may lead to removal of already existing user

created cifs sharesv CIFS SID and Credential leak impacts cache memory availabilityv Storage system might panic when not specifying an export path

New known problems and limitations in Data ONTAP 8.1.2

New known issues include the following:v “File access protocol issues” on page 134

– “Value of the option nfs.ifc.rcv.high is unexpectedly reset” on page 134v “SAN administration issues” on page 139

– “Disks offline in Windows Server 2008 and 2012 after Data ONTAPupgrade” on page 139

For more information about all the limitations in the Data ONTAP 8.1 releasefamily for 7-Mode, see Known problems and limitations.

Limitations removed in Data ONTAP 8.1.2

The following limitations have been removed in this release:v Files might not be able to be deleted using NFS in a full FlexVol volumev Disks might be silently left unassigned for multi-disk carrier shelvesv CIFS users cannot rename or delete home directoriesv Storage system requests to Windows Server 2008 might fail

Changes introduced since Data ONTAP 8.1 5

v ADIC Quantum tape libraries are not discovered by Data ONTAPv Tape devices behind Decru DataFort are not detected unless a known SCSI

device is mapped to LUN 0v Possible giveback failure during controller or NVRAM8 replacement on

N7x50T series or N6200 series systems

Documentation changes for Data ONTAP 8.1.2

The following information is new in this release:v “Changes to the System Administration Guide” on page 145v “Changes to the High Availability Configuration Guide” on page 149v “Changes to the Commands Manual Page Reference” on page 149v “Changes to the File Access and Protocols Management Guide” on page 150v “Changes to the Software Setup Guide ” on page 151

Changes in Data ONTAP 8.1.1 for 7-Mode

This release includes support for new hardware and software enhancements.

New platform and hardware support in Data ONTAP 8.1.1

New support includes the following:v Support for systems with only SSDsv Support for the EXN3500 disk shelf

For more information, see New platform and hardware support.

New and changed features in Data ONTAP 8.1.1

New and changed features include the following:v Manageability enhancements

– Role-based access control for LDAP users' system access– Support of core segments– SP SSH access control and automatic timeout– RLM SSH access control and automatic timeout– “SSH port forwarding for the SP is disabled by default” on page 20– SSH port forwarding for the RLM is disabled by default– Changes in aggregate Snapshot copy management– Free space reallocation of aggregates– SSH server version for Data ONTAP

v Storage resource management enhancements


– “Support for Flash Pools” on page 27– “Support for the Advanced Zone Checksum type (AZCS)” on page 27– Support for sanitizing SSDs

v “High-availability pair (formerly active/active configuration)enhancements” on page 30– MetroCluster support for Cisco switches

v File access protocol enhancements– Support for SMB 2.1– Support for BranchCache– Support for lease oplocks– Enhancements to procedure for computer account password change– Support for VMware vStorage over NFS

v “SAN enhancements” on page 39– “Windows Server 2012 support ” on page 40

v Data protection enhancements– Support for SnapVault with nondefault vFiler units– Support for incremental and differential backups using SMTape engine– Support for restore to volumes in 64-bit aggregates using SMTape engine

v Storage efficiency enhancements– Changes to deduplication

For information about all new and changed features in this release, see “Newand changed features in the Data ONTAP 8.1 release family” on page 15.

New commands in Data ONTAP 8.1.1

The following new commands were added to this release:v cifs branchcache hash stat

v cifs branchcache set key

v coredump segment config modify

v coredump segment config show

v coredump segment delete

v coredump segment delete-all

v coredump segment show

v coredump segment start

v coredump segment status

v coredump segment stop

v storage shelf identify


Changed commands in Data ONTAP 8.1.1

The following commands are changed in this release:v aggr options

v aggr status

v cifs shares

v df

v lock status

v qtree oplock

v storage show disk

v sysconfig

v vol status

For more information, see “Changed commands in the Data ONTAP 8.1release family” on page 74.

New options in Data ONTAP 8.1.1

New options include the following:v cifs.smb2_1.branch_cache.enable

v cifs.smb2_1.branch_cache.hash_time_out

v cifs.W2K_password_change

v cifs.W2K_password_change_interval

v cifs.W2K_password_change_within

v nfs.mount_rootonly

v nfs.v2.enable

v nfs.v4.id.allow_numerics

v nfs.vstorage.enable

v rlm.autologout.enable

v rlm.autologout.timeout

v rlm.ssh.access

v snapmirror.vsm.volread.smtape_enable

v sp.autologout.enable

v sp.autologout.timeout

v sp.ssh.access

For more information, see “New options in the Data ONTAP 8.1 releasefamily” on page 80.

Changed options in Data ONTAP 8.1.1


The following options changed in this release:v cifs.oplocks.enable

v cifs.smb2.client.enable

v cifs.smb2.durable_handle.enable

v cifs.smb2.durable_handle.timeout

v cifs.smb2.enable

v cifs.smb2.signing.required

v cifs.weekly_W2K_password_change

v security.admin.nsswitchgroup

For more information, see “Changed options in Data ONTAP 8.1 releasefamily” on page 86.

Requirement for running Data ONTAP 8.1.1

New requirements include the following:v Gateway system limits information

For more information, see “Requirements for running Data ONTAP 8.17-Mode” on page 101.

New cautions in Data ONTAP 8.1.1

New cautions include the following:v “Upgrade and revert cautions” on page 106

– “iSCSI target adapters not supported in Data ONTAP 8.1 and later” onpage 107

– If you revert to a release earlier than Data ONTAP 8.1 you might need toinstall licenses for some products

– N6210 and N6040 storage systems with Flash Cache modules aresupported

– Downgrade to 8.1 not allowed for N6210 and N6040 systems with FlashCache modules

– MultiStore license and vFiler units removed when reverting to DataONTAP 8.0.x

v “Setup cautions” on page 115– “CIFS setup overwrites the storage system password” on page 115

v “Manageability cautions” on page 116– System panics when Flash Cache is full and the root volume is a

traditional volumev Storage management cautions


– Preventing service disruption when expanding an aggregate withvolumes using quotas

– Changing the language of a FlexVol volume when expansion scanner isrunning could result in system disruption

v File access and protocols cautions– “CIFS startup might take several minutes after cluster failover giveback”

on page 120– CIFS setup via ONTAPI may lead to removal of already existing user

created cifs shares– CIFS SID and Credential leak impacts cache memory availability

For more information about all important cautions in the Data ONTAP 8.1release family, see Important cautions.

Cautions removed in Data ONTAP 8.1.1

The following cautions have been removed in this release:v Non-ASCII characters in the comment string of the lun setup command

result in system panicv Mirroring a ZCS aggregate is not supported for this release of Data ONTAPv N6210 and N6040 systems with Flash Cache modules are not supportedv Oplock breaks might cause panic when using durable handlesv Storage Encryption preconfiguration requirementsv Write operations might fail or LUNs might go offline if deduplication

metadata increases—moved to the Limitations sectionv Storage system panic due to nonresponsive key management serverv Retrieving authentication keys might cause storage system panic

New known problems and limitations in Data ONTAP 8.1.1

New known issues include the following:v “Manageability issues” on page 126

– “Cached data in a Flash Cache module is cleared during upgrade to DataONTAP 8.1 release family” on page 126

v Storage resource management issues– Files might not be able to be deleted using NFS in a full FlexVol volume– Disks might be silently left unassigned for multi-disk carrier shelves– You cannot assign ownership and checksum type for spare disks or array

LUNs in the same operation– Configuring ACP to use a different port on N3220 and N3240 storage

systems disables ACP for the local SAS expander


v Network protocol issues– “Partner node might be unavailable during controller failover when an

interface name is used as an alternate host name in the /etc/hosts file”on page 132

– Static routes are not retargeted to a network interface with a newautoconfigured IPv6 address

v File access protocol issues– “Microsoft Windows 7 clients fail to rename files and directories” on

page 136– “File copy operation on a widelink path inside a CIFS share might fail

when using SMB 2.x” on page 136– “CIFS client authentication fails if host name exceeds 16 characters” on

page 135– Domain Controller responds with an access denied error to SMB2 tree

connect request– CIFS users unable to rename or delete home directories

v Data protection issues– ADIC Quantum tape libraries are not discovered by Data ONTAP

For more information about all the limitations in the Data ONTAP 8.1 releasefamily for 7-Mode, see Known problems and limitations.

Limitations removed in Data ONTAP 8.1.1

The following limitations have been removed in this release:v CIFS access to SnapVault or qtree SnapMirror destination can cause system

panicv Issues with exportfs commands in noninteractive SSH sessionsv SSD spare blocks consumed limit reported as N/Av Entering dummy network addresses during ACP setup can cause a system

panicv CIFS shares with comment ending with backslash disappearv Error NFS4_BADOWNER when NFSv4 client passes UID as stringv CIFS clients must reopen files after you break locksv File screening requests fail due to FPolicy server connection timeoutv Large number of locks might cause temporary performance degradationv User mapping fails for users in a trusted domainv Reboot required after updating the krb5.conf filev Specification of the default keytab file


fileaccessprotocolissues.dita#fileaccessprotocolissues/CIFSUsersCannotRenameOrDeleteHomeDi

v Aggregate snapshot copy creation and aggr copy commands fail with anaggregate Snapshot reserve of 0 percent

v Exceeding the maximum number of assigned devices results in a panic

Documentation changes for Data ONTAP 8.1.1

The following information is new in this release:v “Changes to the System Administration Guide” on page 145v “Changes to the Commands Manual Page Reference” on page 149v “Changes to the SAN Administration Guide ” on page 150v “Changes to the Software Setup Guide ” on page 151v “Changes to the SAN Configuration Guide for 7-Mode” on page 152

For more information about other important documentation changes, seeChanges to published documentation.


Unsupported features

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

Features not available or discontinued in Data ONTAP 8.1and later releases operating in 7-Modev FilerView

FilerView is no longer available on systems running Data ONTAP 8.1 orlater releases. You can use OnCommand System Manager as a web-basedgraphical management interface to manage common storage systemfunctions from a web browser.For more information about OnCommand System Manager, see the IBM Nseries support website, which is accessed and navigated as described in“Websites” on page 2.

v Support for EXN2000 is discontinued. For additional information, see“Systems including EXN2000 storage expansion units with ESH2 modules”on page 17.

v UPS management is not supported. For additional information, see “UPSmanagement is no longer supported” on page 25.

v 2-Gb FC target ports are not supported. For additional information, see“2-Gb FC ports not supported as targets” on page 122.

If you require these features in your business environment, contact your IBMN series support to evaluate the best upgrade path.

Features not available in Data ONTAP 8.0 and later releasesoperating in 7-Modev Netboot

Netboot is not a supported function unless you are restoring the DataONTAP image on the boot device, such as a PC CompactFlash card. Forinformation about how to replace a PC CompactFlash card or restore theData ONTAP image on the card, see the Replacing a CompactFlash Card flyerthat is applicable to your version of Data ONTAP.

v SnapValidator for OracleSnapValidator for Oracle is not supported in Data ONTAP 8.0 7-Mode andlater 7-Mode releases. For more information, contact technical support.

v IPsecIPsec is not supported. If IPsec is enabled on your storage system, be awarethat it will be automatically disabled during the upgrade.


v TOETOE functionality is not supported. There is no adverse effect on theperformance of your storage system because TOE is disabled.

If you require these features in your business environment, contact your IBMN series support to evaluate the best upgrade path.

Features discontinued in the Data ONTAP 8.1 release familyoperating in 7-Mode

Beginning in Data ONTAP 8.1 operating in 7-Mode, the following features arediscontinued:v “Systems including EXN2000 storage expansion units with ESH2 modules”

on page 17v “UPS management is no longer supported” on page 25v “2-Gb FC ports not supported as targets” on page 122

Beginning in Data ONTAP 8.0 operating in 7-Mode, the following features arediscontinued:v “Upgrade process changes with Data ONTAP 7-Mode software images” on

page 107v Hardware-based disk ownershipv SnapVault for NetBackup

Features discontinued in a future release of Data ONTAP

Support for NDMPv3 will be discontinued in a future release of Data ONTAP.When that occurs, only NDMPv4 will be supported.


New and changed features in the Data ONTAP 8.1 releasefamily

A number of features and enhancements have been added or changed in theData ONTAP 8.1 release family. Features that were present in the DataONTAP 7.x release family are now supported in this release.

Note: Some new and changed features in this release might also beintroduced in a maintenance release of an earlier Data ONTAP release family.Before upgrading, be sure to consult with your IBM representative about newData ONTAP functionality to determine the best solution for your businessneeds.

Additional major changes made in Data ONTAP 8.1 are described as follows:v “New and changed platform and hardware support” on page 16v “Manageability enhancements” on page 18v “Storage resource management enhancements” on page 27v “High-availability pair (formerly active/active configuration)

enhancements” on page 30v “Networking and security protocol enhancements” on page 32v “File access protocol enhancements” on page 35v “Data protection enhancements” on page 41v “Storage efficiency enhancements” on page 43v “MultiStore enhancements” on page 45


New and changed platform and hardware support

This Data ONTAP release supports new and changed hardware.

For information about supported systems, see “Supported systems” on page101.v “Support for the N3220 and N3240 platforms”v “Support for systems with only SSDs”v Support for 900-GB SAS disksv “Support for IOM6 (FC2099) for the EXN3000 storage expansion unit”v “Support for the EXN3200 storage expansion unit”v “Support for SAS tape drives”v “Systems including EXN2000 storage expansion units with ESH2 modules”

on page 17v “Support for FC/SAS bridge (ATTO for IBM FibreBridge 6500N)” on page

17

Support for the N3220 and N3240 platformsData ONTAP 8.1.1 and later releases support N3150, N3220, and N3240storage systems.

Support for systems with only SSDsData ONTAP 8.1.1 and later releases support SSD-only configurations for moststorage system models. For these models, the presence of HDDs is notrequired.

To see which models support SSD-only configurations, see the IBM SystemStorage N series Introduction and Planning Guide.

Support for 900-GB SAS disksIn Data ONTAP 8.1.1 and later releases, 900-GB disks are supported forEXN3500 SAS expansion units. These are performance disks (rather thancapacity disks) and their speed is 10K.

Support for IOM6 (FC2099) for the EXN3000 storage expansion unitData ONTAP 8.1.1 and later releases support the EXN3000 storage expansionunits with IOM3 and IOM6.

Support for the EXN3200 storage expansion unitData ONTAP 8.1.1 and later releases support the EXN3200 storage expansionunit.

Support for SAS tape drivesStarting with Data ONTAP 8.1, SAS tape drives are supported.


Systems including EXN2000 storage expansion units with ESH2 modulesBeginning with Data ONTAP 8.1, IBM N series EXN2000 Storage ExpansionUnit with ESH2 storage I/O modules are no longer supported. If even one ofthese devices is attached to your storage system, do not upgrade to DataONTAP 8.1 or later until after you replace the devices.

Upgrading a system with these devices attached to it results in anunsupported system configuration and shelf configuration errors.

If you want to upgrade to Data ONTAP 8.1 or a later release and your storageenvironment includes the obsolete EXN2000 units with ESH2 devices, youshould contact your IBM representative to discuss upgrading to IBM N seriesEXN3000 Storage Expansion Unit or IBM N series EXN3500 StorageExpansion Unit.

Support for FC/SAS bridge (ATTO for IBM FibreBridge 6500N)Starting with Data ONTAP 8.1, the FC/SAS bridge (ATTO for IBMFibreBridge 6500N Feature Code 2100), which is a Fibre Channel-to-SASbridge that allows SAS disk shelves (with SAS or SATA disk drives) to beused in stretch and fabric MetroCluster configurations, is supported.

New and changed features in the Data ONTAP 8.1 release family 17

Manageability enhancements

You can find information about the new and changed manageabilitycapabilities.v “Options for specifying uppercase and lowercase requirements in user

passwords”v “Role-based access control for LDAP users' system access” on page 19v “Support of core segments” on page 19v “SP SSH access control and automatic timeout” on page 19v “RLM SSH access control and automatic timeout” on page 20v “SSH port forwarding for the SP is disabled by default” on page 20v “SSH port forwarding for the RLM is disabled by default” on page 20v “Changes in aggregate Snapshot copy management” on page 20v “SSH server version for Data ONTAP” on page 21v “Free space reallocation of aggregates” on page 21v “Cache rewarming for Flash Cache modules” on page 21v “Enhancements to reallocation scans, read reallocation, and extents” on

page 22v “System health monitoring” on page 23v “AutoSupport enhancements” on page 24v “Default 64-bit root aggregate for new systems” on page 25v “UPS management is no longer supported” on page 25v “Changes to default aggregate Snapshot reserve for newly created

nonmirrored aggregates” on page 25v “IPv6 support for SP and RLM” on page 25v “Support for Transport Layer Security protocol” on page 26v “Licensing changes” on page 26

Options for specifying uppercase and lowercaserequirements in user passwords

Starting with Data ONTAP 8.1.2, you can specify the minimum number ofuppercase or 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 mustcontain.

v The default is 0, which does not require that a password contain uppercasecharacters.


v The security.passwd.rules.minimum.lowercase option specifies theminimum number of lowercase alphabetic characters that a password mustcontain.

v The default is 0, which does not require that a password contain lowercasecharacters.

Role-based access control for LDAP users' system access

Starting with Data ONTAP 8.1.1, the security.admin.nsswitchgroup optionenables you to map LDAP groups to specified roles on the system andmanage LDAP users’ access to the system.

Mapping an LDAP group to a role enables users in that group to have onlythe capabilities granted by the mapped role. The role can be a predefined roleor one that you create by using the useradmin role add command. If you donot specify a role for an LDAP group, users in that group are grantedcapabilities of the “admin” role and have full administrative access to thestorage system.

For more information about mapping an LDAP group to a role on the storagesystem, see the Data ONTAP System Administration Guide for 7-Mode. Forinformation about the security.admin.nsswitchgroup option, see thena_options(1) man page.

Support of core segments

A core dump file can be very large, making it time consuming to upload totechnical support when you need to. Starting with Data ONTAP 8.1.1, you cansegment a saved core dump file into core segments for easier handling.

You use the coredump segment config commands to configure the automaticsegmenting of core dump files.

You use the coredump segment commands to manage core segments.

For more information about segmenting core dump files, see the Data ONTAPSystem Administration Guide for 7-Mode.

SP SSH access control and automatic timeout

Starting with Data ONTAP 8.1.1, you can configure the SP to accept SSHrequests from only the administration hosts that you specify. You can alsoconfigure the automatic logout settings so that an SSH connection to the SP isautomatically terminated after the connection has been idle for the number ofminutes you specify.


These enhancements are supported on N6200 series and N7x50T seriessystems that are running SP firmware 1.3 or later and N3220 and N3240systems that are running SP firmware 2.1 or later.

For information about configuring SP SSH access control and automaticlogout, see the Data ONTAP System Administration Guide for 7-Mode.

RLM SSH access control and automatic timeout

Starting with Data ONTAP 8.1.1, you can configure the RLM to accept SSHrequests from only the administration hosts that you specify. You can alsoconfigure the automatic logout settings so that an SSH connection to the RLMis automatically terminated after the connection has been idle for the numberof minutes you specify.

These enhancements are supported on systems that are running RLMfirmware 4.1 or later.

For information about configuring RLM SSH access control and automaticlogout, see the Data ONTAP System Administration Guide for 7-Mode.

SSH port forwarding for the SP is disabled by default

On N6200 series and N7x50T series systems that are running SP firmware 1.3or later and N3220 and N3240 systems that are running SP firmware 2.1 orlater, SSH port forwarding for the SP is disabled by default.

SSH port forwarding for the RLM is disabled by default

On systems that are running RLM firmware 4.1 or later, SSH port forwardingfor the RLM is disabled by default.

Changes in aggregate Snapshot copy management

Starting with Data ONTAP 8.1.1, how you manage aggregate Snapshot copycreation and the aggregate Snapshot reserve has changed.

For aggregate Snapshot copy creation and the aggr copy commands tosucceed, you no longer need to increase the aggregate Snapshot reserve to anon-zero percentage.

In addition, if you want to create aggregate Snapshot copies but the aggregatehas an aggregate Snapshot reserve of 0 percent and automatic aggregateSnapshot copy deletion is enabled, the operation to create aggregate Snapshotcopies still succeeds if both of the following conditions are met:v The aggregate has at least 10 percent of free space.


For Snapshot copy creation, the space that is reserved in the aggregate tohonor a FlexVol volume's guarantee is considered free space in theaggregate.

v The aggregate Snapshot copies do not exceed the current aggregateSnapshot reserve by more than 5 percent of the size of the aggregate.

SSH server version for Data ONTAP

The SSH server version running on Data ONTAP is Data ONTAP SSH version1.0.

For information about the Common Vulnerabilities and Exposures (CVE) fixesimplemented in Data ONTAP, see the IBM Systems Storage N seriesSuspected Security Vulnerabilities tech note at the following link:

www.ibm.com/support/entdocview.wss?uid=ssg1S1003795

Free space reallocation of aggregates

Starting in Data ONTAP 8.1.1, you can enable free space reallocation onaggregates to improve write performance. Free space reallocation improveswrite performance by optimizing the free space within an aggregate.

Free space reallocation works best on workloads that perform a mixture ofsmall random overwrites and sequential or random reads. You can expectadditional CPU utilization when you enable free space reallocation. Youshould not enable free space reallocation if your storage system has sustained,high CPU utilization.

You use the aggr options command with the free_space_realloc option toenable free space reallocation.

For more information about free space reallocation, see the Data ONTAPSystem Administration Guide for 7-Mode.

Cache rewarming for Flash Cache modules

Starting in Data ONTAP 8.1, the WAFL external cache preserves the cache in aFlash Cache module during a graceful shutdown.

When a storage system powers down, the WAFL external cache takes asnapshot of the data in a Flash Cache module. When the system powers up, ituses the snapshot to rebuild the cache. After the process completes, thesystem can read data from the cache. This process, called cache rewarming,


https://www.ibm.com/support/entdocview.wss?uid=ssg1S1003795

helps to maintain system performance after a planned shutdown. Forexample, you might shut down a system to add hardware or upgradesoftware.

Cache rewarming is enabled by default if you have a Flash Cache moduleinstalled. Cache rewarming is available when both nodes in an HA pair arerunning Data ONTAP 8.1.

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

Enhancements to reallocation scans, read reallocation, andextents

Starting in Data ONTAP 8.1, you can use reallocation scans, read reallocation,and extents to optimize the layout of specific types of volumes.

Optimizing the layout of volumes can improve the read performance of hostapplications that access data on the storage system.

For more information about reallocation scans, read reallocation, and extents,see the Data ONTAP System Administration Guide for 7-Mode.

Reallocation scans, read reallocation, and extents with FlexVol volumescontained in mirrored aggregates

In prior releases, you could enable reallocation scans, read reallocation, andextents on FlexVol volumes contained in mirrored aggregates. However, somecommand options were not supported with this type of volume.

Starting in Data ONTAP 8.1.1, you can use the following command options tooptimize the layout of FlexVol volumes that are contained in mirroredaggregates:

Reallocation scansYou can use the -p option when you run the reallocate startcommand. The -p option (also called physical reallocation) reallocatesuser data on the physical blocks in the aggregate while preserving thelogical block locations within a FlexVol volume.

Read reallocationYou can set the read_realloc option to space_optimized when yourun the vol options command. space_optimized conserves space butresults in degraded Snapshot read performance.

ExtentsYou can set the extent option to space_optimized when you run the


vol options command. space_optimized conserves space but resultsin degraded Snapshot read performance.

Reallocation scans, read reallocation, and extents with deduplicatedvolumes

Starting in Data ONTAP 8.1, reallocation scans, read reallocation, and extentscan optimize the layout of a deduplicated volume.

You use the following command options to optimize the layout of adeduplicated volume:

Reallocation scansUse the -p option when you run the reallocate start command.Reallocation scans skip deduplicated data if you do not specify the -poption.

Read reallocationSet the read_realloc option to space_optimized when you run thevol options command. Read reallocation skips deduplicated data ifyou set the read_realloc option to on.

ExtentsSet the extent option to space_optimized when you run the voloptions command. Extents skip deduplicated data if you set theextent option to on.

System health monitoring

You can proactively manage your system by monitoring a single, integratedhealth status.

If the status is degraded, you can view details about the problem, includingthe probable cause and recommended recovery actions. After you resolve theproblem, the system health status automatically returns to OK.

The system health status reflects multiple separate health monitors. Adegraded status in an individual health monitor causes a degraded status forthe overall system health.

Currently, there are two health monitors: an overall System Health Monitorand a Node Connectivity health monitor for the Storage subsystem.

For information about monitoring your system's health, see the Data ONTAPSystem Administration Guide for 7-Mode and the man pages for the systemhealth commands.


AutoSupport enhancements

Starting in Data ONTAP 8.1, AutoSupport messages contain more targeteddata, are easier to manage, and offer better protocol and privacy support.

The content of AutoSupport messages is more focused and compact becauseof the following changes:v The data sent in event-triggered AutoSupport messages is now specific to

the trigger event.v Many log files that are sent in AutoSupport messages now contain only

new lines added since the last AutoSupport message.v The content of each message is all compressed into a single file attachment

in 7z file format.

Managing AutoSupport is easier in the following ways:v You have more visibility into past messages and their content, as well as

the content that will be sent in future messages.v You can add more data to future messages sent in response to specific

triggers, and you can control whether your internal support organizationreceives messages for specific triggers.

v If an AutoSupport message is not successfully transmitted, you canmanually resend it.

v By default, the system collects AutoSupport information and stores it locallyeven if AutoSupport is disabled.Local collection of AutoSupport files provides valuable historicalinformation that technical support staff can use to quickly solve futureproblems.

Protocol support for AutoSupport has improved in the following ways:v IPv6 is supported.v HTTPS certificates are validated.v HTTP(S) uses PUT requests, enabling failed messages to restart from where

they left off.POST is also still supported.

v Message size limits are available for HTTP(S) and SMTP.

Privacy is improved when you use the autosupport.content minimal option.Instead of omitting all private data, some private data is now masked andencoded. Also, by default, the message subject line contains the server'ssystem ID instead of its host name.

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


Default 64-bit root aggregate for new systems

Starting with Data ONTAP 8.1, newly created aggregates are 64-bit by default,and new systems are shipped with the root volume in a 64-bit aggregate.

FilerView is no longer available

FilerView is no longer available on systems running Data ONTAP 8.1 or laterreleases. You can use OnCommand System Manager as a web-based graphicalmanagement interface to manage common storage system functions from aweb browser.

UPS management is no longer supported

As of Data ONTAP 8.1, uninterruptible power supply (UPS) management (byusing the ups command) is no longer supported.

Changes to default aggregate Snapshot reserve for newlycreated nonmirrored aggregates

Beginning with Data ONTAP 8.1, a newly created nonmirrored aggregate hasthe aggregate Snapshot reserve set to 0 percent by default. A newly createdmirrored aggregate continues to have the aggregate Snapshot reserve set to 5percent by default.

For information about managing aggregate Snapshot copies andconsiderations for increasing the aggregate Snapshot reserve, see the DataONTAP System Administration Guide for 7-Mode.

IPv6 support for SP and RLM

The Data ONTAP 8.1 release family supports IPv6 for SP and RLM.

To send SP traffic over IPv6, you must be running SP version 1.2 or later, SPmust be configured for IPv6, and the storage system must also have IPv6enabled.

To send RLM traffic over IPv6, you must be running RLM version 4.0 or later,RLM must be configured for IPv6, and the storage system must also haveIPv6 enabled.

Note: BMC supports IPv4 only.


Support for Transport Layer Security protocol

The Data ONTAP 8.1 release family supports Transport Layer Security (TLS)version 1.0, which provides better security protections than previous SSLversions did.

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

TLS is disabled by default, and setting up SSL does not automatically enableTLS. For information about how to enable TLS, see the Data ONTAP SystemAdministration Guide for 7-Mode.

Licensing changes

Starting with Data ONTAP 8.1, you no longer need to add license keys onyour system for most features that are distributed free of cost.

In addition, some features are now grouped together so that only one licensekey is required to add a pack of features to a system. Also, some features andproducts are enabled when you add certain other license keys.

For information about Data ONTAP 8.1 licensing models and whether alicense key must be added for a particular feature or pack, see the DataONTAP 7-Mode System Administration Guide and the man pages for thelicense commands or the Technote FAQ at the following link:

Using License Keys with Data ONTAP 8.1 7-Mode



Storage resource management enhancements

This Data ONTAP release provides improved performance, resiliency, andmanagement capabilities for storage resources.v “Support for Flash Pools”v “Support for the Advanced Zone Checksum type (AZCS)”v “Support for sanitizing SSDs”v “Enhancements to aggregates” on page 28v “N6210 systems now support 500 FlexVol volumes” on page 28v “Limit on number of subdirectories has been removed” on page 28v “Enhancements to FlexClone files and FlexClone LUNs” on page 28

Support for Flash Pools

Data ONTAP 8.1.1 and later releases provide support for FlashPools—aggregates that incorporate both HDDs and SSDs. The HDDs are usedfor primary storage, and the SSDs provide a highperformance read and writecache to boost aggregate performance. For information about creating andmanaging Flash Pools, see the Data ONTAP Storage Management Guide for7-Mode and Technical Report 4070: NetApp Flash Pool Design andImplementation Guide.

Support for the Advanced Zone Checksum type (AZCS)

Data ONTAP 8.1.1 and later releases provide support for a new checksumtype, AZCS. AZCS delivers greater usable capacity per disk for large capacitydisks (for example, SATA).

For information about using AZCS, see the Data ONTAP Storage ManagementGuide for 7-Mode.

Support for sanitizing SSDs

Data ONTAP 8.1.1 and later releases provide support for sanitizing most SSDmodels.

For information about which SSD models support sanitization, see the SystemConfiguration Guide.

For information about disk sanitization, see the Data ONTAP StorageManagement Guide for 7- Mode.


http://media.netapp.com/documents/tr-4070.pdf

http://media.netapp.com/documents/tr-4070.pdf

Enhancements to aggregates

Data ONTAP 8.1 and later releases support several enhancements foraggregates.

Starting in Data ONTAP 8.1, aggregates support the following enhancements:v You can nondisruptively expand 32-bit aggregates to the 64-bit format,

without requiring data to be copied or moved.For more information about expanding 32-bit aggregates to the 64-bitformat, see the Data ONTAP Storage Management Guide for 7-Mode.

v 64-bit aggregates are now the default aggregate format.v The SnapMirror relationship is supported between 64-bit and 32-bit

aggregates.For more information about SnapMirror, see the Data ONTAP DataProtection Online Backup and Recovery Guide for 7-Mode.

v The maximum aggregate size is increased for some platforms.To determine the maximum aggregate size for your platform, see the IBMSystem Storage N series Introduction and Planning Guide.

N6210 systems now support 500 FlexVol volumes

In Data ONTAP 8.0, the N6210 systems supported 200 volumes. In DataONTAP 8.1 and later releases, N6210 systems support 500 FlexVol volumes.

For information about how many FlexVol volumes are supported on otherstorage system models, see the IBM System Storage N series Introduction andPlanning Guide.

Limit on number of subdirectories has been removed

In earlier versions of Data ONTAP, you could not create more than 99,998subdirectories in any directory. In Data ONTAP 8.1 and later versions, there isno limit on the number of subdirectories you can create.

Enhancements to FlexClone files and FlexClone LUNs

Starting with Data ONTAP 8.1, you can create instantaneous clones of filesand LUNs present in a FlexVol volume. In addition, you can create FlexClonefiles from Snapshot copies of parent files present in the FlexVol volume.

You can create a maximum of 32,767 FlexClone files or FlexClone LUNs froma parent file or LUN without creating a physical copy of the parent entity. Ifyou try to create more than 32,767 clones, Data ONTAP automatically createsa new physical copy of the parent file or LUN.


For more information, see the Data ONTAP Storage Management Guide for7-Mode.


High-availability pair (formerly active/active configuration) enhancements

This Data ONTAP release includes new features and enhancements forhigh-availability. This section provides an overview of these features andenhancements.

For more information about these features, see the Data ONTAP 7-ModeHigh-Availability Configuration Guide.v “Automatic giveback after takeover due to panic”v “MetroCluster system support for shared-switches configuration”v “MetroCluster support for Cisco switches”

For more information, see the MetroCluster Compatibility Matrix which isaccessed and navigated as described in “Websites” on page 2.

Automatic giveback after takeover due to panic

Beginning with Data ONTAP 8.1.2, Data ONTAP will, by default,automatically giveback to the partner after a takeover due to the partnerpanicking. This giveback can be disabled or reenabled using the newcf.giveback.auto.after.panic.takeover option. The automatic givebackreduces the amount of time the HA pair operates with a node in takeovermode.

MetroCluster system support for shared-switchesconfiguration

Beginning with Data ONTAP 8.1, MetroCluster system supportsshared-switches configuration. In a shared-switches configuration, twofabric-attached MetroCluster systems share the same four switches and theISLs between them.

For more information about the cabling and setting the ports inshared-switches configuration, see the Data ONTAP High-Availability andMetroCluster Configuration Guide.

MetroCluster support for Cisco switches

Beginning with Data ONTAP 8.1.1, the fabric-attached MetroClusterconfiguration support Cisco switches also.

The following Cisco switches are supported:v Cisco MDS 9148v Cisco MDS 9222i


Note: The Cisco MDS 9148 switch can be installed in the IBM N seriescabinet, however, the Cisco MDS 9222i needs to be installed in a separaterack.

For more information about Cisco switch configuration, see theFabric-attached MetroCluster Cisco Switch Configuration Guide available onthe IBM N series support website, which is accessed and navigated asdescribed in “Websites” on page 2.

Also, see the IBM N series interoperability matrix, which is accessed andnavigated as described in “Websites” on page 2, for more information.


Networking and security protocol enhancements

This Data ONTAP 8.1 and later releases include a number of new features andenhancements for networking and security protocol enhancements. Thissection provides an overview of these features and enhancements.v “Support for IPv6”v “Improving TCP network congestion with Appropriate Byte Counting” on

page 34

Support for IPv6

Starting with Data ONTAP 8.1, IPv6 addressing is supported. You can enableIPv6 on your storage system or on an HA pair and perform various taskssuch as configuring network interfaces, VLANs, and interface groups. IPv6 issupported over the CIFS, NFS, HTTP, and FTP protocols.

You can enable IPv6 on your storage system during setup. For moreinformation, see the Data ONTAP Software Setup Guide for 7-Mode.

You can also enable IPv6 on your storage system during operation by settingthe options ip.v6.enable option to on. For more information, see the DataONTAP Network Management Guide for 7-Mode.

IPv6 features in Data ONTAP 8.1

The following IPv6 features are supported in Data ONTAP 8.1:v IPv6 dual stack mechanism to enable communication over IPv4 and IPv6v Neighbor Discovery that includes Router Discovery and Duplicate Address

Detectionv IPv6 stateless address autoconfiguration, requiring minimal manual

configuration of hostsv Internet Control Message Protocol version 6 (ICMPv6)v Path MTU discovery for IPv6v Transmission of IPv6 packets over Ethernet linksv IPv6 static routes and router alert optionv Network administration commands, such as the traceroute6, ping6,

netdiag, and pktt commandsv Telnet server to accept IPv6 connection requestsv Syslog for the IPv6-related eventsv Host name and address resolution with DNS, DDNS, and NIS over IPv6v Configuration of VLANs with IPv6 addressesv Configuration of base VLAN interfaces with IPv6 addresses


v Network Time Protocol (NTP)v Configuration of single-mode, static multimode, and dynamic multimode

(LACP) vifs with IPv6 across multiple NICsv SNMPv1, SNMPv2c, and SNMPv3v MIB for TCP, UDP, ICMPv6, and IPv6v HA configuration, which includes takeover and giveback of IPv6 addresses

and routes, mapping partner IPv6 interfaces, and executing commands withIPv6 addresses in the partner context.For more information, see the Data ONTAP High-Availability andMetroCluster Configuration Guide for 7-Mode.

v IPv6 addresses in the vFiler commands.For more information, see the Data ONTAP MultiStore Management Guide for7-Mode.

v iSCSI over IPv6For more information, see the Data ONTAP SAN Administration Guide for7-Mode.

v File access protocols—CIFS, FTP, HTTP, NFSv2, NFSv3, and NFSv4—overIPv6For more information, see the Data ONTAP File Access and ProtocolsManagement Guide for 7-Mode.

v LDAP and Kerberos version 5 with IPv6v HTTPS over IPv6 addresses

HTTPS can be used for secure administrative access; however, SecureAdminSSL must be enabled before you can issue HTTPS requests to the storagesystem.

v SSH protocol version 2 over IPv6If IPv6 is enabled on your storage system, SecureAdmin SSH must beenabled before you can issue SSH requests to the storage system.

v SNMP traphosts with IPv6 addressesYou should specify only IPv6 addresses, and not host names, to identifyIPv6 traphosts

v Fast path over IPv6For more information, see the Data ONTAP Network Management Guide for7-Mode.

v RLM over IPv6If IPv6 is enabled on your storage system, then you must ensure that theRLM firmware version is 4.0 or later. Disabling IPv6 on Data ONTAP alsodisables IPv6 on the RLM.

Note: You cannot use IPv6 to connect to the BMC.


For information about installing and updating the RLM firmware, see theData ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.For information about configuring the RLM, see the Data ONTAP SystemAdministration Guide for 7-Mode.

v Hardware-assisted takeover over IPv6The cf.hw_assist.enable option should be set to on and RLM must beenabled.For more information about the hardware-assisted takeover, see the DataONTAP High-Availability and MetroCluster Configuration Guide for 7-Mode.

v MetroCluster configurations over IPv6For more information about MetroCluster configuration, see the DataONTAP High-Availability and MetroCluster Configuration Guide for 7-Mode.

v RSH protocol over IPv6To connect to the storage system over the RSH protocol, you must ensurethat the rsh.enable option and the ip.v6.enable option are set to on.

v Dump, restore, and ndmpcopy commands over IPv6For more information about the commands, see the Data ONTAP DataProtection Tape Backup and Recovery Guide for 7-Mode.

v SnapMirror, SnapVault, and volume copy operations over IPv6For more information, see the Data ONTAP Data Protection Online Backupand Recovery Guide for 7-Mode.

Improving TCP network congestion with Appropriate ByteCounting

Appropriate Byte Counting (ABC) is an algorithm implemented in the TCPstack of Data ONTAP that enables you to improve TCP performance andsecurity. Starting from Data ONTAP 8.1, ABC is enabled by default on all thestorage controllers.


File access protocol enhancements

This Data ONTAP release includes a number of new features andenhancements for file access and protocols management. This section providesan overview of these features and enhancements.

For more information about these features, see the Data ONTAP File Access andProtocols Management Guide for 7-Mode.v “SMB 2.1 disabled by default in Data ONTAP 8.1.2”v “Support for the “Manage Auditing and Security Logs” GPO”v “Support for the Windows “Owner Rights” security principal” on page 36v “Enabling new EMS messages to help troubleshoot Kerberos issues” on

page 36v “Support for SMB 2.1” on page 37v “Support for BranchCache” on page 37v “Support for lease oplocks” on page 38v “Enhancements to procedure for computer account password change” on

page 38v “Support for VMware vStorage over NFS” on page 38v “Support for SFTP” on page 39v “Support for SMB 2.0” on page 39v “Support for FTPS” on page 39

SMB 2.1 disabled by default in Data ONTAP 8.1.2

SMB 2.1 is disabled by default in Data ONTAP 8.1.2. CIFS clients can stillnegotiate SMB 2.0 connections with the storage system.

Support for the “Manage Auditing and Security Logs” GPO

Data ONTAP 8.1.2 and later releases in the 8.1 release family add support forthe “Manage Auditing and Security Logs” user right Group Policy Object(GPO) to the list of supported GPOs.

With the addition of support for the “Manage Auditing and Security Logs”user right GPO, the list of GPOs supported on your storage system includethe following:v Startup and shutdown scriptsv Group Policy refresh interval for computer (includes random offset)v File System security policyv Restricted Groups security policyv Event Log policy


v Auditing policyv Take Ownership user rightv Manage Auditing and Security Logs user right

For information about installing, configuring, and managing GPOs on yourstorage system, see the Data ONTAP File Access and Protocols ManagementGuide for 7-Mode.

Support for the Windows “Owner Rights” security principal

Data ONTAP 8.1.2 and later releases support the “Owner Rights” securityprincipal. You can add this security principal to a file or directory DACL(discretionary access-control list) to override the default behavior of owners offiles or directories.

“Owner Rights” is a well-known security principal with the well-knownsecurity identifier (SID) S-1-3-4 that is available with Windows 2008 serverand Windows Vista and later releases. By default, when a user creates a file ordirectory, that user is the owner of the file and directory, and the owner hascertain default rights. The administrator can override the default rights byadding the “Owner Rights” principle to a file or directory's DACL, and thenspecifying the desired permissions by assigning ACEs (Access Control Entries)to the “Owner Rights” security principal.

You can use either of the following methods to manage the “Owner Rights”security principal for files or directories residing within volumes:v By using the Security tab on the Windows Properties windowv By using the secedit utility, available as a software download from the

support site

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 followingcommand:

options nfs.rpcsec.trace on

After you finish troubleshooting, disable the EMS message for Kerberos byentering the following command:

options nfs.rpcsec.trace off


Support for SMB 2.1

Data ONTAP 8.1.1 and later releases in the 8.1 release family support SMB 2.1.SMB 2.1 is a minor revision of the SMB 2.0 protocol and introduces severalenhancements.

The following enhancements are supported:v Lease oplocks

When SMB 2.1 is enabled, Data ONTAP uses SMB 2.1 lease oplocks, whichis a new oplock model that provides advantages over traditional oplocks.

v Retrieval of content hashes used by BranchCacheBranchCache-enabled storage systems use content hashes to provide clientswith information about cached content.

Data ONTAP does not support the following SMB 2.1 enhancements:v Resilient handlesv Large MTUv Write-through

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

Support for BranchCache

Data ONTAP 8.1.1 and later releases in the 8.1 release family supportBranchCache caching. BranchCache was developed by Microsoft to enablecaching of content on computers local to requesting clients. The Data ONTAPimplementation of BranchCache can reduce wide-area network (WAN)utilization and provide improved access response time when users in a branchoffice access content stored on a Data ONTAP storage system using CIFS.

With BranchCache enabled, Windows BranchCache clients first retrievecontent from the storage system and then cache the content on a computerwithin the branch office. If another client in the branch office requests thesame content, the storage system determines whether the cached content isstill up-to-date and, if it is, sends the client metadata about the cachedcontent. The client then uses the metadata to retrieve content directly from thelocally based cache.

BranchCache enabled storage systems use content hashes to provide clientswith the metadata information about cached content. SMB 2.1 provides thecontent hash retrieval enhancement needed for BranchCache.


For more information about using BranchCache with Data ONTAP, see theData ONTAP File Access and Protocols Management Guide for 7-Mode.

Support for lease oplocks

Data ONTAP 8.1.1 and later releases in the 8.1 release family support leaseoplocks, which provide enhanced locking over traditional oplocks. Availablewith SMB 2.1, the lease oplock model is based on a key called a lease keyrather than a file handle that is used with traditional oplocks.

Lease oplocks allow a client that is making multiple file open calls to obtainand preserve client caching state across the file open calls that it originates.The client generates a lease key and uses it to link together multiple handlesto the same file. Operations on handles with the same lease key do not affectthe oplock state. If the client and storage system connect using SMB 2.1, leaseoplocks are used instead of traditional oplocks.

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

Enhancements to procedure for computer account passwordchange

Data ONTAP 8.1.1 and later releases in the 8.1 release family enableadministrators to manage the timing for password changes so that passwordchanges for storage systems across the enterprise do not occur at the sametime.

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

Support for VMware vStorage over NFS

Data ONTAP supports certain VMware vStorage APIs for Array Integration(VAAI) features in an NFS environment.

The following features are supported:

copy offload Enables an ESXi host to copy virtual machines or virtual machinedisks (VMDKs) directly between the source and destination datastore location without involving the host. This conserves ESXihost CPU cycles and network bandwidth. Copy offload preservesspace efficiency if the source volume is sparse.

space reservation Guarantees storage space for a VMDK file by reserving space forit.


Note the following limitations when using VMware vStorage over NFS:v vStorage is not supported with FlexCache.v Copy offload is not supported across vFiler units and across storage

systems.v Copy offload operations can fail in the following scenarios:

– While running wafliron on the source or destination volume because ittemporarily takes the volume offline

– While moving either the source or destination volume– While performing takeover or giveback operations

Support for SFTP

Beginning in Data ONTAP 8.1, clients can use the Secure File TransferProtocol (SFTP) to access files on the storage system.


Support for SMB 2.0

Beginning in Data ONTAP 8.1, clients can use the SMB 2.0 protocol to accessfiles on the storage system.


Support for FTPS

Beginning in Data ONTAP 8.1, clients can use the FTP over SSL (FTPS)protocol to access files on the storage system.


SAN enhancements

This Data ONTAP release includes a number of new SAN features andenhancements that you should be familiar with.

For details about any of the features and enhancements introduced in thefollowing sections, see the Data ONTAP SAN Administration Guide for 7-Mode.


Windows Server 2012 support

Data ONTAP now supports Windows Server 2012 hosts in SAN environments.When you create LUNs for hosts that run Windows Server 2012, specifywindows_2008 as the value for the ostype (LUN multiprotocol type).

Use the Interoperability Matrix to find a supported combination of hardwarecomponents, software versions, firmware, and drivers.


Data protection enhancements

This Data ONTAP release includes a number of new features andenhancements for data protection enhancements. This section provides anoverview of these features and enhancements.

For more information about these features, see the Data ONTAP DataProtection Online Backup and Recovery Guide for 7-Mode and the Data ONTAPData Protection Tape Backup and Recovery Guide for 7-Mode.v “SnapVault support for nondefault vFiler units”v “Support for volume SnapMirror replication between 32-bit and 64-bit

volumes”v “Changes to default FlexVol volume Snapshot reserve value”v “Support for concurrent volume SnapMirror and SMTape backup

operations” on page 42v “Protection of data at rest through Storage Encryption” on page 42v “Support for SnapLock” on page 42v “Support for incremental and differential backups using SMTape engine” on

page 42v “Support for restore to volumes in 64-bit aggregates using SMTape engine”

on page 43

SnapVault support for nondefault vFiler units

Starting with Data ONTAP 8.1.1, you can create and modify SnapVaultrelationships and schedules at the SnapVault secondary volume from thedefault vFiler unit (vfiler0) and the nondefault vFiler unit.

For more information about managing the SnapVault secondary volumes, seethe Data ONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.

Support for volume SnapMirror replication between 32-bitand 64-bit volumes

Starting with Data ONTAP 8.1, you can replicate volumes by usingSnapMirror technology between 32-bit and 64-bit volumes. For bothsynchronous and asynchronous volume replication, the SnapMirror sourceand destination volumes can be either 32-bit or 64-bit.

Changes to default FlexVol volume Snapshot reserve value

Starting with Data ONTAP 8.1, a newly created FlexVol volume has theSnapshot reserve set to 5 percent by default. However, the default Snapshotreserve for a traditional volume remains 20 percent.


Support for concurrent volume SnapMirror and SMTapebackup operations

Starting with Data ONTAP 8.1, you can make an SMTape backup of a volumeSnapMirror destination when SnapMirror transfers are in progress. You canrun volume SnapMirror and SMTape backup operations concurrently byenabling the vsm.smtape.concurrent.cascade.support option on a volumeSnapMirror destination system.

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

Protection of data at rest through Storage Encryption

Data ONTAP 8.1 7-Mode introduces the new Storage Encryption feature thatallows you to protect your data at rest by automatically encrypting all datawritten to disk. The feature is available on certain supported storagecontrollers and disk shelves that contain disks with built-in encryptionfunctionality.

For detailed information about feature requirements, configuration, andmanagement, see the Data ONTAP Software Setup Guide for 7-Mode and theData ONTAP Storage Management Guide for 7-Mode.

Support for SnapLock

Data ONTAP 8.1 7-Mode supports the SnapLock feature. Several significantimprovements are made to the SnapLock feature in this release.

Following are the key enhancements:v System ComplianceClockv Volume ComplianceClockv Volume-level autocommit

For more information about these enhancements, see the Data ONTAP Archiveand Compliance Management Guide for 7-Mode.

Support for incremental and differential backups usingSMTape engine

Starting with Data ONTAP 8.1.1, you can use the SMTape engine to performincremental and differential backup and restore operations. If you want toperform an incremental or differential backup, you must perform bothbaseline and the incremental or differential backups by using only theNDMP-compliant backup applications.


When you perform SMTape operations, the NDMP-compliant backupapplications create and manage Snapshot copies for these operations.

Support for restore to volumes in 64-bit aggregates usingSMTape engine

Using SMTape engine, you can restore data backed up in Data ONTAP 8.0.xfrom 32-bit or 64-bit aggregates to volumes in 64-bit aggregates in DataONTAP 8.1.x and later. You can restore this data to volumes created across upto two major consecutive Data ONTAP releases only.

Storage efficiency enhancements

This Data ONTAP release includes a number of new features andenhancements for storage efficiency enhancements. This section provides anoverview of these features and enhancements.v “Changes to deduplication”v “Changes to data compression” on page 44

Changes to deduplication

Starting with Data ONTAP 8.1.1, the change log file size limit is set to 1percent of the volume size to manage the deduplication metadata overhead.The change log file size is related to the maximum volume size. The spaceallocated for the change log files in a volume is not reserved.

Starting with Data ONTAP 8.1, you can enable the deduplication featurewithout adding a license. For deduplication, no limit is imposed on thesupported maximum volume size. The maximum volume size limit isdetermined by the type of storage system regardless of whether deduplicationis enabled.

You can run deduplication operations on volumes from either of the nodesduring takeover in an HA pair.

For each volume, two copies of the fingerprint database are maintained,where one copy of the database resides in the volume and the other copy inthe aggregate.

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


Changes to data compression

Starting with Data ONTAP 8.1, data compression is supported on SnapLockvolumes and in stretch and fabric-attached MetroCluster configurations. Forcompression, no limit is imposed on the supported maximum volume size.The maximum volume size limit is determined by the type of storage systemregardless of whether compression is enabled.

For more information about SnapLock, see the Data ONTAP Archive andCompliance Management Guide for 7-Mode and for MetroCluster configurations,see the Data ONTAP High-Availability and MetroCluster Configuration Guide for7-Mode.


MultiStore enhancements

This Data ONTAP 8.1 and later releases include a number of new features andMultiStore enhancements.v “Online migration support for vFiler units”v “Interactive SSH support for vFiler units” on page 46v “Data compression support on vFiler units” on page 47

Online migration support for vFiler units

Starting with Data ONTAP 8.1, you can perform online migration of vFilerunits (also called Data Motion for vFiler) from one storage system to anotherwithout experiencing any disruption in data availability. You must be awareof the storage system models and disks that support online migration ofvFiler units.

You must use the N series Management Console interface to perform onlinemigration of vFiler units.

For more information about online migration, see the OnCommand UnifiedManager Guide to Common Provisioning and Data Protection to Common Workflowsfor 7-Mode and the OnCommand Unified Manager Provisioning and DataProtection Online Help for 7-Mode.

Supported storage systems

v High-end storage systems, such as N7000 series and N7x50Tv Mid-range storage systems, such as N5000 series, N6000, and N6200 seriesv Low-end storage systems, such as N3220, N3240, and N3400

Note: For gateway systems, online migration of vFiler units is supportedwith native disks and array LUNs on storage arrays only if both the sourceand destination are type LUN.

Table 1. Supported source and destination storage systems with number of volumes for migration

Source storage system Destination storage systemNumber of volumes formigration

v N7x50T

v N7000 series

v N7x50T

v N7000 series

20

Note: If the source or destination storage system is either N7600 or N7700, then you can migrate only 8volumes.

v N7x50T

v N7000 series

v N6200 series

v N6000 series

v N5000 series

8


Table 1. Supported source and destination storage systems with number of volumes formigration (continued)

Source storage system Destination storage systemNumber of volumes formigration

v N6200 series

v N6000 series

v N5000 series

v N7x50T

v N7000 series

v N6200 series

v N6000 series

v N5000 series

8

v N3220

v N3240

v N3400

v N7x50T

v N7000 series

v N6200 series

v N6000 series

v N5000 series

v N3220

v N3240

v N3400 series

4

Note: You cannot perform online migration of vFiler units when the sourcestorage system is a high-end system or a mid-range system and thedestination storage system is a low-end system.

Supported disk types

v FCv SATAv SASv BSAS

Interactive SSH support for vFiler units

Starting with Data ONTAP 8.1, you can establish interactive SSH sessions withvFiler units. A vFiler unit can have only one active interactive SSH sessionestablished at a time. You can also use IPv6 addresses to establish interactiveSSH sessions.

Depending on the number of vFiler units allowed on that storage system,there are limits on the number of concurrent interactive SSH sessions that youcan run on a storage system.

For more information about limits on the number of interactive SSH sessions,see the Data ONTAP MultiStore Management Guide for 7-Mode.


Data compression support on vFiler units

Starting with Data ONTAP 8.1, data compression is supported on vFiler units.You can perform data compression operations from the CLI of all vFiler units,in addition to the CLI of vfiler0.

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

Gateway enhancements

The Data ONTAP 8.1.x release family includes a number of new features andenhancements for gateway systems.

Support for EMC VNX storage arrays

Starting with Data ONTAP 8.1.1, EMC VNX storage arrays are supported withV-Series systems. Supported has been added for the VNX5100, VNX5300,VNX5500, VNX5700, and VNX7500 models.

For more information about these storage arrays, including configurationrequirements, restrictions and any supported array features, see the GatewaySupport Matrix.

Support for third-party storage array advanced features

A number of advanced third-party storage array features are supported foruse with gateway systems.

Advanced array features that are supported include the following:v Virtual provisioning is supported on EMC CLARiiON CX4 storage arrays.v Virtual provisioning is supported on IBM DS87xx and DS88xx storage

arrays.v Thick LUNs on Storage Pools are supported on CX4 and VNX storage

arrays.v SSDs are supported on EMC Symmetrix VMAX storage arrays.v FAST-VP and FAST tiering are supported on EMC V-MAX and V-MAXe

storage arrays.v Array controller-based encryption is supported on Hitachi Data Systems

USP-V, USP-VM, and VSP storage arrays.v Array controller-based encryption is supported on HP XP 20000, XP 24000,

and P9500 storage arrays.v Array controller-based encryption is supported on Fujitsu DX400, DX8000,

DX400 S2, and DX8700 S2 storage arrays.


v Array controller-based encryption is supported on Fujitsu DX400, DX8000,DX400 S2, and DX8700 S2 storage arrays.

v Self-encrypting drives are supported on Fujitsu DX400 S2 and DX8700 S2storage arrays.

Note: Not all features are supported on all gateway platforms or on all DataONTAP releases. See the Gateway Support Matrix for configurationrequirements and any restrictions.

Removed gateways environment variable requirement forData ONTAP 8.1

Starting in Data ONTAP 8.1, the fc-non-array-adapter-list environmentvariable is no longer required for gateway systems with native disk shelvesthat use Multipath Storage.

If you revert from Data ONTAP 8.1 to an earlier release, Data ONTAPautomatically configures this environment variable for you. It is required inreleases prior to 8.1.


New and changed features in the Data ONTAP 8.0 releasefamily

This section covers features that were added or changed in the Data ONTAP8.0 7-Mode release family. If you are upgrading to Data ONTAP 8.1 or laterfrom a 7.3.x release, these changes will apply to your system in addition tothose introduced in the 8.1 release family.

Note: Some new and changed features in this release might also beintroduced in a maintenance release of an earlier 7G release family. Beforeupgrading, be sure to consult with your IBM representative about new DataONTAP functionality to determine the best solution for your business needs.

Data ONTAP 8.0 and later Data ONTAP 8.0.x releases provide a newaggregate type, 64-bit aggregates, with larger maximum aggregate and FlexVolvolume sizes, as well as improved performance, resiliency, and managementcapabilities for storage resources.

For more information about 64-bit aggregates, see “Support for 64-bitaggregates” on page 56.

Data ONTAP 8.0 and later Data ONTAP 8.0.x releases also provide newplatform and hardware support as described in “New and changed platformand hardware support” on page 50, additional management capabilities suchas SSL security improvements, additional capabilities using iSCSI and FCprotocols for N series SAN environments, and enhanced data protectiontechnologies such as SnapMirror and SnapVault.

Additional major changes made in the Data ONTAP 8.0 release family aredescribed as follows:v “New and changed commands and options in the Data ONTAP 8.0 7-Mode

release” on page 89v “New and changed platform and hardware support” on page 50v “Changes in storage expansion unit support” on page 52v “Manageability enhancements” on page 53v “Storage resource management enhancements” on page 56v “High-availability pair enhancements” on page 58v “Networking and security protocol enhancements” on page 58v “File access protocol enhancements” on page 61v “Block protocol enhancements” on page 61


v “Data protection enhancements” on page 63v “Changes to the Data ONTAP and gateway libraries” on page 67

New and changed platform and hardware support

This Data ONTAP release supports new and changed hardware as listed inthis section.

For information about supported systems, see “Supported systems” on page101.v “Support for the N6200 series”v “Support for the N7x50T system”v “Support for 1-TB Flash Cache modules”v “Support for 512-GB and 256-GB Performance Acceleration Module (PAM

II)”v “Support for SSDs” on page 51v “Supported tape drives” on page 51v “Support for 3-TB SATA disks” on page 51v “Support for 2-TB SATA disks” on page 51

Support for the N6200 seriesData ONTAP 8.0.1 and later releases support the N6200 series.

Support for the N7x50T systemData ONTAP 8.0.1 and later releases support the N7x50T series.

Support for 1-TB Flash Cache modulesData ONTAP 8.0.2 and later releases support the 1-TB PCI-e-attached FlashCache module that uses Flash technology.

The addition of Flash Cache optimizes the performance of randomread-intensive workloads such as file services, messaging, virtualinfrastructure, and OLTP databases without using more high performancedisk drives.

For more information about Flash Cache modules supported with yourstorage system models, see the IBM System Storage N series Introduction andPlanning Guide.

Support for 512-GB and 256-GB Performance Acceleration Module (PAMII)

Data ONTAP 8.0.1 operating in 7-Mode and later releases support thePCIe-attached Performance Acceleration Module (PAM II, also known as FlashCache module) that uses Flash technology.


The addition of PAM II optimizes the performance of random read-intensiveworkloads such as file services, messaging, virtual infrastructure, and OLTPdatabases without using more high-performance disk drives.

For more information about PAM II modules supported with your storagesystem models, see IBM System Storage N series Introduction and Planning Guide.

Support for SSDsData ONTAP 8.0.1 7-Mode and later Data ONTAP 8.0.x releases supportsolid-state disks (SSDs). SSDs are flash memory-based storage devices thatprovide better overall performance than hard disk drives, or HDDs, which aremechanical devices using rotating media.

For more information about SSDs, see the Data ONTAP Storage ManagementGuide for 7-Mode. For information about which storage system models supportSSDs, see IBM System Storage N series Introduction and Planning Guide.

Supported tape drivesData ONTAP 8.0.1 and later releases support Quantum LTO-4, QuantumLTO-5, Hewlett-Packard LTO-4, Hewlett-Packard LTO-5, and IBM LTO-5 tapedrives.

Support for 3-TB SATA disksIn Data ONTAP 8.0.2 and later releases, 3-TB SATA disks are supported forthe SAS disk connection type.

Support for 2-TB SATA disksIn Data ONTAP 8.0 and later releases, 2-TB SATA disks are supported for boththe SAS and FC disk connection types. With these larger disks and 64-bitaggregates, you can create larger aggregates before being affected by spindleand aggregate size limits.

For more information about 64-bit aggregates, see “Support for 64-bitaggregates” on page 56.


Changes in storage expansion unit support

The Data ONTAP 8.0 7-Mode release includes a number of new features andenhancements for storage expansion unit support.v “Support for EXN3500 storage expansion units”v “Support for EXN3000 storage expansion units”

Support for EXN3500 storage expansion unitsIn Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports theEXN3500 storage expansion unit. The EXN3500 storage expansion unitcontains external SAS disk drives and 6-Gb I/O modules.

EXN3500 storage expansion units are also supported on the following DataONTAP 8.x and 7.x releases:v Data ONTAP 8.x releases: Data ONTAP 8.0P1 or later, except N3400 storage

systems, 8.0.1 or later.v Data ONTAP 7.x releases: Data ONTAP 7.3.3P2 or later, except N3400 and

N3600 storage systems, 7.3.4 or later.

For more information about which disk drives and storage system models aresupported with the EXN3500 storage expansion unit, see the IBM SystemStorage N series Introduction and Planning Guide. For more information aboutthe EXN3500 storage expansion unit, see the EXN3500 Storage Expansion UnitInstallation and Service Guide.

Support for EXN3000 storage expansion unitsData ONTAP 8.0.2P3 and later Data ONTAP 8.0.x releases, and Data ONTAP7.3.6 and later Data ONTAP 7.3.x releases, support EXN3000 storageexpansion units.

The EXN3000 storage expansion unit contains external SAS disk drives and3-Gb I/O modules. The EXN3000 storage expansion unit is also supported onData ONTAP 7.3.3P2 and later releases.

For more information about which disk drives and storage system models aresupported with the EXN3000 storage expansion unit, see the IBM SystemStorage N series Introduction and Planning Guide. For more information aboutthe EXN3000 storage expansion unit, see the EXN3000 Storage Expansion UnitInstallation and Service Guide.


Manageability enhancements

You can find information about the new and changed manageabilitycapabilities.v “Reversion and downgrade support”v “Default security settings for manageability protocols”v “Requirement to set root account password” on page 54v “Uses of the systemshell and the diagnostic account” on page 54v “Boot menu enhancements and changes” on page 55v “Supported OpenSSH client versions” on page 55v “Root aggregate Snapshot reserve values reduced” on page 55

Reversion and downgrade supportBeginning in Data ONTAP 8.0.2 7-Mode, you can revert to a Data ONTAPrelease in an earlier release family or downgrade to an earlier Data ONTAPrelease in the same family. You can perform these operations withoutassistance from technical support when transitioning new or test systems toearlier releases.

However, you must call technical support if you have problems during orafter upgrading. If you need to transition to an earlier release, see the DataONTAP Upgrade and Revert/Downgrade Guide for 7-Mode for Data ONTAP 8.0 tohelp determine the correct action in your environment.

Default security settings for manageability protocolsOn storage systems shipped with Data ONTAP 8.0 or later, secure protocolsare enabled and nonsecure protocols are disabled by default.

SecureAdmin is set up automatically on storage systems shipped with DataONTAP 8.0 or later. For these systems, the following are the default securitysettings:v Secure protocols (including SSH, SSL, and HTTPS) are enabled by default.v Nonsecure protocols (including RSH, Telnet, FTP, and HTTP) are disabled

by default.

On storage systems shipped with Data ONTAP 8.0 or later, the following arethe default option settings for SSH and SSL:v options ssh.enable on

v options ssh2.enable on

v options ssh1.enable off

v options ssh.passwd_auth.enable on

v options ssh.pubkey_auth.enable on

v options httpd.admin.ssl.enable on


Also on storage systems shipped with Data ONTAP 8.0 7-Mode or later, thefollowing are the default option settings for the nonsecure protocols:v options ftpd.enable off

v options httpd.admin.enable off

v options httpd.enable off

v options rsh.enable off

v options telnet.distinct.enable on

v options telnet.enable off

Note: These default settings apply only to storage systems shipped with DataONTAP 8.0 or later. For storage systems upgraded from an earlier version toData ONTAP 8.0 release family, the above default settings do not apply.Instead, for those upgraded systems, the settings remain unchanged after theupgrade. Also, if you make security setting modifications after upgrading toData ONTAP 8.0 or later, the modifications are preserved even if the systemreverts back to the previous Data ONTAP version.

For more information about the default security settings, see the Data ONTAP8.0 System Administration Guide for 7-Mode.

Requirement to set root account passwordDuring the initial setup of a storage system shipped with Data ONTAP 8.0 orlater, you are prompted to set a password for the root account.

The following are the default password rules for all accounts whensecurity.passwd.rules.enable is set to on (the default):v The password must be at least eight characters long.v The password must contain at least one number.v The password must contain at least two alphabetic characters.v The password must not contain the Ctrl-c or Ctrl-d key combination or the

two-character string ^D.

Note: Subsequent invocations of the setup command do not prompt you toset up a password for the root account.

For more information about setting up the storage system, see the DataONTAP 8.0 Software Setup Guide for 7-Mode.

Uses of the systemshell and the diagnostic accountA diagnostic account, named "diag", is provided with your storage systemrunning Data ONTAP 8.0 or later. You can use the 'diag' account to performtroubleshooting tasks in the systemshell. The 'diag' account and thesystemshell are intended only for low-level diagnostic purposes and should beused only with guidance from technical support.


The 'diag' account is the only account that can be used to access thesystemshell, through the advanced command systemshell. The 'diag' accountis disabled by default. You must enable the account and set up its passwordbefore using it for the first time. Neither the 'diag' account nor the systemshellis intended for general administrative purposes.

Boot menu enhancements and changesStarting with Data ONTAP 8.0, the boot menu includes menu options thatallow you to restore the configuration information from the root volume tothe boot device, to install new software, or to reboot the storage system.

Data ONTAP 8.0 and later releases allow you to create a new root FlexVolvolume but not a new traditional root volume from the boot menu. However,preexisting traditional root volumes are still supported.

For information about the boot menu, see the na_floppyboot(1) man page andthe Data ONTAP 8.0 System Administration Guide for 7-Mode.

Supported OpenSSH client versionsData ONTAP 8.0.2 7-Mode and later releases support OpenSSH client version4.4p1 only. To enhance security, OpenSSH client version 3.8p1 is no longersupported because it does not contain the latest security fix.

Root aggregate Snapshot reserve values reducedThe root aggregate and root volume Snapshot reserve values for new storagesystems have been reduced starting with Data ONTAP 8.0.1.

To increase the amount of usable space on the storage system while stillretaining all the benefits of volume Snapshot copies, IBM ships all newsystems running Data ONTAP 8.0.1 or later with the following new Snapshotreserve values:v Snapshot reserve for the root aggregate is set to 0%.

The previous value was 5%.v Snapshot reserve for the root volume is set to 5%.

The previous value was 20%.

Existing systems, and systems configured at the factory to run MetroCluster,are not affected by this change.

Attention: If you later configure MetroCluster, or use RAID SyncMirror orthe aggregate copy capability on the root aggregate, the root aggregateSnapshot reserve must be increased to 5% by using the snap reservecommand.

For more information about using the snap reserve command, see thena_snap (1) man page.


Storage resource management enhancements

This Data ONTAP release provides improved performance, resiliency, andmanagement capabilities for storage resources.v “Support for 64-bit aggregates”v “Data compression support”v “File space utilization report” on page 57v “Upgrading to Data ONTAP 8.0.1 increases volume capacity after

deduplication” on page 57v “Maximum simultaneous FlexClone file or FlexClone LUN operations per

storage system” on page 57v “Support for FlexClone files and FlexClone LUNs on vFiler units” on page

57v “Increased maximum RAID group size for SATA disks” on page 57v “Ability to decrease maxfiles” on page 57

Support for 64-bit aggregatesIn Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports a newtype of aggregate, the 64-bit aggregate. 64-bit aggregates have a largermaximum size than 32-bit aggregates. In addition, volumes contained by64-bit aggregates have a larger maximum size than volumes contained by32-bit aggregates.

The maximum size of a 64-bit aggregate and the volumes it contains dependson the model of your storage system. To determine the maximum 64-bitaggregate size for your storage system model, see the IBM System Storage Nseries Introduction and Planning Guide. The maximum size of a volumecontained by a 64-bit aggregate corresponds to the maximum size of itscontaining aggregate.

The maximum size for 32-bit aggregates remains 16 TB.

For more information, see the Data ONTAP 8.0 Storage Management Guide for7-Mode and the na_aggr(1) man page.

Data compression supportStarting with Data ONTAP 8.0.1, you can compress data within a FlexVolvolume using the data compression technology. You can use data compressiononly on FlexVol volumes that are created on 64-bit aggregates on primary,secondary, and tertiary storage tiers.

After you enable data compression on a FlexVol volume, all subsequent writesto the volume are compressed inline. However, existing data remainsuncompressed. You can use the data compression scanner to compress theexisting data.


File space utilization reportThe file space utilization report enables you to see the files and the amount ofspace that they occupy in a deduplicated volume. You can choose to eithermove or delete the files to reclaim the space.

This report provides a view of the total number of blocks in a file and thenumber of blocks that are shared by non-deduplicated or non-cloned files.

Note: Total blocks refer to the number of blocks in a file, including blocksthat are required for storing the file metadata.

Upgrading to Data ONTAP 8.0.1 increases volume capacity afterdeduplication

After you upgrade to Data ONTAP 8.0.1 and later from an earlier release ofData ONTAP, you can increase the deduplicated volume size up to 16 TB forall platform models that support Data ONTAP 8.0.1.

Maximum simultaneous FlexClone file or FlexClone LUN operations perstorage system

Starting in Data ONTAP 8.0 7-Mode and later, you can simultaneously run amaximum of 500 FlexClone file or FlexClone LUN operations on a storagesystem.

For more information about FlexClone files and FlexClone LUNs, see the DataONTAP 8.0 Storage Management Guide for 7-Mode.

Support for FlexClone files and FlexClone LUNs on vFiler unitsIn Data ONTAP 8.0.1 and later releases of the 8.0 release family, the FlexClonefile and FlexClone LUN commands are available in the default vFiler context.

You can use the FlexClone files and FlexClone LUNs feature to createwritable, space-efficient clones of parent files and parent LUNs within a vFilerunit. Storage owned by a vFiler unit cannot be accessed or discovered fromother vFiler units by using the FlexClone file or FlexClone LUN commands.

For more information about FlexClone files and FlexClone LUNs, see the DataONTAP 8.0 Storage Management Guide for 7-Mode.

Increased maximum RAID group size for SATA disksStarting in Data ONTAP 8.0.1, the maximum RAID group size allowed forATA, BSAS, and SATA disks has increased from 16 to 20 disks. The defaultsize remains the same, at 14 disks.

Ability to decrease maxfilesStarting in Data ONTAP 8.0, you can decrease the value of the maxfilesparameter for a volume, as long as you do not decrease it below the currentnumber of files stored in the volume.


In previous versions of Data ONTAP, you could increase the value of themaxfiles parameter, but not decrease it.

High-availability pair enhancements

This Data ONTAP release includes new features and enhancements relating toHA pairs.

For more information about these features, see the Data ONTAP 8.0High-Availability Configuration Guide for 7-Mode.v “HA pair terminology changes”

HA pair terminology changesThe HA functionality referred to as an HA pair in Data ONTAP 8.0 was calledan active/active configuration in the Data ONTAP 7.2 and 7.3 release families.In the Data ONTAP 7.1 release family and earlier releases, an HA pair wascalled a cluster. HA functionality is a distinct, separate feature from DataONTAP 8.0 Cluster-Mode clustering. For more information about thesefeatures, see the Data ONTAP 8.0 High-Availability and MetroClusterConfiguration Guide for 7-Mode.

Networking and security protocol enhancements

Data ONTAP 8.1 and later releases include a number of new features andenhancements for networking and security protocol enhancements. Thissection provides an overview of these features and enhancements.

For more information about these features, see the Data ONTAP 8.0 7-ModeNetwork Management Guide.v “Ability to block data traffic on the e0M interface”v “Support for CDP” on page 59v “Port-based load-balancing option for multimode interface groups” on page

59v “TSO in NICs” on page 60v “64-bit SNMP object identifiers (OIDs) are supported” on page 60v “Configuration for receiving untagged traffic on VLAN tagged interfaces”

on page 60v “Vifs are now known as interface groups” on page 61

Ability to block data traffic on the e0M interfaceIn Data ONTAP 8.0.2 and later releases, you can block certain types of trafficfrom the e0M interface, including SnapMirror transfers, SnapVault transfers,and data transfers that use CIFS, NFS, and NDMP protocols. This featureallows you to optimize system performance.


Data ONTAP 8.0.2 introduces a new optioninterface.blocked.mgmt_data_traffic to control the blocking of data transferon the e0M interface. New systems that are shipped with Data ONTAP 7.3.6,Data ONTAP 8.0.2 and later releases have the default value of this option setto on, which prevents data transfer on the e0M interface. Systems upgraded toData ONTAP 8.0.2, and later releases have the default value of the option setto off, which allows data transfer on the e0M interface.

Note: Data transfers that use the iSCSI protocol are always blocked onsystems upgraded to Data ONTAP 8.0 and later, and the data transfers are notaffected by the option interface.blocked.mgmt_data_traffic setting.

The e0M port is a low-bandwidth interface that should be used only formanagement traffic that uses SSH and other management protocols.Configuring e0M to serve data traffic can cause performance degradation androuting problems. Therefore, e0M should be configured on a dedicatedmanagement LAN or it should be configured down. If an e0M interface isserving management traffic, it should be partnered with another e0Minterface.

It is a best practice to set the option interface.blocked.mgmt_data_traffic toon, and to use the e0M interface only for management traffic. For moreinformation about the e0M interface, see the Data ONTAP SystemAdministration Guide for 7-Mode and the Data ONTAP Software Setup Guide for7-Mode.

Note: Blocking of data traffic on e0M is supported over IPv6.

Support for CDPCisco Discovery Protocol (CDP) is supported in Data ONTAP 7.3.3 and laterreleases of the 7.x release family, and in Data ONTAP 8.0.1 and later. CDPenables you to automatically discover and view information about directlyconnected CDP-enabled devices in a network.

For more information about CDP, see the Data ONTAP 8.0 NetworkManagement Guide for 7-Mode.

Port-based load-balancing option for multimode interface groupsPort-based load balancing is supported for multimode interface groups inData ONTAP 7.3.2 and later releases of the 7.x release family, and in DataONTAP 8.0.1 and later. On a multimode interface group, you can uniformlydistribute outgoing traffic based on the transport layer (TCP or UDP) portsand network layer addresses (IPv4 or IPv6) by using the port-basedload-balancing method.


The port-based load-balancing method uses a fast hashing algorithm on thesource and destination IP addresses along with the transport layer (TCP orUDP) port number.

For more information about port-based load balancing, see the Data ONTAP8.0 Network Management Guide for 7-Mode.

TSO in NICsTCP segmentation offload (TSO) is a hardware feature supported on NICs toincrease the host CPU's efficiency.

Starting in Data ONTAP 8.0.1 and later, the network interface cards thatsupport TSO are as follows:v Dual 10G Ethernet Controller T320E-SFP+ and T320-XFPv 10 Gigabit Ethernet Controller IX1-SFP+

Starting in Data ONTAP 8.0.2, the following network interface card alsosupports TSO:v Dual 10G Ethernet Controller CNA-SFP+

For more information about TSO and the statistics displayed by the NICs, seethe Data ONTAP 8.0 Network Management Guide for 7-Mode.

64-bit SNMP object identifiers (OIDs) are supportedIn Data ONTAP 7.2 and 7.3 release families, some OIDs in the netapp.mib filehave low and high 32-bit values. In Data ONTAP 8.0 7-Mode and later, theseOIDs are replaced with 64-bit values. You should use SNMPv2 or SNMPv3 toquery your storage system by using the 64-bit OIDs.

For example, the miscHighNfsOps and miscLowNfsOps OIDs have been replacedwith the 64-bit OID misc64NfsOps. In the netapp.mib file, miscHighNfsOps andmiscLowNfsOps are marked as deprecated.

Configuration for receiving untagged traffic on VLAN tagged interfacesIn Data ONTAP 8.0 7-Mode and later, you can configure an IP address for anetwork interface with VLANs. Any untagged traffic goes to the baseinterface, and the tagged traffic goes to the respective VLAN.

For more information about this feature, see the Data ONTAP 8.0 NetworkManagement Guide for 7-Mode.

For information about reverting with a configuration for receiving tagged anduntagged frames on the same network interface, see the Data ONTAP 8.0Upgrade and Revert/Downgrade Guide for 7-Mode.


Vifs are now known as interface groupsStarting with Data ONTAP 8.0 7-Mode and later, vifs are known as interfacegroups. An interface group refers to a single virtual interface that is created bygrouping together multiple physical interfaces. In the Data ONTAP 7.2 and 7.3release families, this functionality is referred to as a vif.

You can use the ifgrp command to create and configure interface groups. Formore information about interface groups and the ifgrp command, see theData ONTAP 8.0 Network Management Guide for 7-Mode.

File access protocol enhancements

This Data ONTAP release includes a number of new features andenhancements for file access and protocols management. This section providesan overview of these features and enhancements.

For more detailed information about these features, see the Data ONTAP 8.0File Access and Protocols Management Guide for 7-Mode.v “Support for multiple open instances of the SMB named pipe on an FPolicy

server”

Support for multiple open instances of the SMB named pipe on anFPolicy server

In Data ONTAP 8.0 7-Mode, you can enable multiple open instances of theSMB named pipe on an FPolicy server by using the fpolicy.multiple_pipesoption.

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

Block protocol enhancements

This Data ONTAP release includes a number of new features andenhancements for block protocol enhancements. This section provides anoverview of these features and enhancements.

For more information about these features, see the IBM System Storage N seriesData ONTAP SAN Administration Guide for 7-Mode.v “iSCSI RADIUS support” on page 62v “Support for Data Motion for Volumes” on page 62v “VMware VAAI features for ESX hosts support” on page 62v “igroup scalability limits” on page 63


iSCSI RADIUS supportData ONTAP 8.0 operating in 7-Mode introduces support for iSCSI RADIUS,which enables you to centrally manage iSCSI initiator authentication centrally.

RADIUS still uses CHAP to authenticate iSCSI initiators, but it enables you tomanage the authentication process from a central RADIUS server, rather thanmanage them manually on each storage system. In larger SAN environments,this can greatly simplify iSCSI initiator management and provide addedsecurity.

In addition to simplifying CHAP password management, RADIUS alsoreduces the load on your storage system. The RADIUS client service runs onthe storage system and communicates with the RADIUS server and initiators,but most of the authentication processing is handled by the RADIUS server.

For more information, see the Data ONTAP SAN Administration Guide for7-Mode.

Support for Data Motion for VolumesData ONTAP 8.0.1 7-Mode or later supports Data Motion for Volumes, whichenables you to nondisruptively move a volume from one aggregate to anotherwithin the same controller to satisfy service-level agreements and capacityutilization and improved performance. In a SAN environment, FlexVolvolumes and the LUNs in the volumes are moved nondisruptively from oneaggregate to another.

The volume move occurs in three phases: setup phase, data copy phase, andcutover phase.

For more information about the volume move, see Data ONTAP SANAdministration Guide for 7-Mode.

VMware VAAI features for ESX hosts supportData ONTAP 8.0.1 and later supports certain VMware vStorage APIs forArray Integration (VAAI) features when the ESX host is running ESX 4.1 orlater. These features help offload operations from the ESX host to the storagesystem and increase the network throughput.

The ESX host enables the features automatically in the correct environment.You can determine the extent to which your system is using the VAAI featuresby checking the statistics contained in the VAAI counters.

For more information about the VMware VAAI features for ESX hosts, seeData ONTAP SAN Administration Guide for 7-Mode.


igroup scalability limitsData ONTAP 8.0.1 introduces support to expand the host side scalability byexpanding the number of igroups supported on N6000 series and N7000 seriessystems from 512 per controller to 1024 per controller.

Data protection enhancements

This section provides an overview of data protection features andenhancements Data ONTAP 8.0 7-Mode release family.

For more information about these features, see the Data ONTAP DataProtection Online Backup and Recovery Guide for 7-Mode and the Data ONTAPData Protection Tape Backup and Recovery Guide for 7-Mode.v “SnapVault update schedules for volume SnapMirror destination backups”v “Support for 840 disk drives on fabric-attached MetroCluster configuration”

on page 64v “Support for out-of-order frame delivery for SnapMirror over Fibre

Channel” on page 64v “Support for SnapMirror relationship between two FlexClone volumes” on

page 64v “Support for SnapMirror network compression” on page 65v “Support for designated range of ports for NDMP data connections” on

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

page 65v “NearStore license is not required for deduplication” on page 65v “Maximum concurrent deduplication operations supported” on page 65v “Prerequisite for backing up data to tape using NDMP services” on page 65v “Snapshot copy schedules” on page 66v “SnapMirror support for 64-bit volumes” on page 66v “SnapVault support for 64-bit volumes” on page 66

SnapVault update schedules for volume SnapMirror destination backupsWhen backing up a volume SnapMirror destination using SnapVault in DataONTAP 8.0.2, the snapvault.snapshot_for_dr_backup option allows you tochoose the SnapVault behavior for updating the destination system.

You can set the following values for the snapvault.snapshot_for_dr_backupoption:v named_snapshot_only: Schedules the SnapVault updates from the most

recent Snapshot copy with the scheduled base name for scheduled backup.


v named_snapshot_preferred: Schedules the SnapVault updates from the mostrecent Snapshot copy created by volume SnapMirror if the scheduledSnapshot copy is not available.

v vsm_base_only: Schedules the SnapVault updates from the most recentSnapshot copy created by volume SnapMirror. This is the default value.

In Data ONTAP 8.0 and Data ONTAP 8.0.1 7-Mode, SnapVault uses a namedSnapshot copy and not the Snapshot copy created by volume SnapMirror toupdate the destination system.

Support for 840 disk drives on fabric-attached MetroCluster configurationIn Data ONTAP 7.3.5 and later releases of 7.x release family, and Data ONTAP8.0.1 and later releases of 8.x release family, fabric-attached MetroClusterconfigurations can support up to 840 disk drives.

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

Support for out-of-order frame delivery for SnapMirror over Fibre ChannelData ONTAP 8.0.1 and later support out-of-order frame delivery forSnapMirror over Fibre Channel.

When enabled, out-of-order frame delivery for SnapMirror over Fibre Channeleliminates the requirement to deliver all the frames in the same sequence inwhich the frames were transmitted. This feature ensures the uninterruptedSnapMirror transfers regardless of the order in which the frames aredelivered.

For more information about out-of-order frame delivery, see Data ONTAP 8.0Data Protection Online Backup and Recovery Guide for 7-Mode.

Support for SnapMirror relationship between two FlexClone volumesData ONTAP 8.0.1 and later support SnapMirror relationship between twoFlexClone volumes.

The SnapMirror relationship between two FlexClone volumes that have acommon base Snapshot copy can be established without transferring thecommon Snapshot data again to the destination system.

For more information about SnapMirror relationship between two FlexClonevolumes, see Data ONTAP 8.0 Data Protection Online Backup and Recovery Guidefor 7-Mode.


Support for SnapMirror network compressionData ONTAP 7.3.2 and later releases of the 7.x release family, and DataONTAP 8.0.1 and later releases of the 8.x release family support SnapMirrornetwork compression. This feature is supported only for asynchronousvolume SnapMirror.

Note: The SnapMirror destination system should be using a Data ONTAPrelease that supports SnapMirror network compression.

The SnapMirror network compression feature compresses the data stream onthe source system, transfers the compressed data stream over the network,and uncompresses the data stream on the destination system before writing itto disk. It helps in optimizing network bandwidth utilization betweenSnapMirror source and destination systems. This feature can be especiallyuseful for connections that have relatively low bandwidth, such as WANconnections.

For more information about SnapMirror network compression, see the DataONTAP 8.0 Data Protection Online Backup and Recovery Guide for 7-Mode.

Support for designated range of ports for NDMP data connectionsData ONTAP 8.0.1 and later releases support designated range of ports thatcan be used for NDMP data connections in response toNDMP_DATA_LISTEN and NDMP_MOVER_LISTEN operations. Therefore,you can perform data migration by using the ndmpcopy command andthree-way tape backups even in environments where the source anddestination networks are separated by a firewall.

If volumes with deduplication exceed the maximum supported sizeVolumes continue to be online when they exceed the maximum supportedsize. For more information about the maximum volume size allowed fordifferent storage systems, with and without deduplication, see the DataONTAP Storage Management Guide for 7-Mode.

NearStore license is not required for deduplicationStarting with Data ONTAP 8.0.1, you do not have to enable the NearStorepersonality license to use deduplication.

Maximum concurrent deduplication operations supportedYou can run a maximum of eight concurrent deduplication operations on allstorage systems.

Prerequisite for backing up data to tape using NDMP servicesStarting from Data ONTAP 8.0 7-Mode, NDMP users must have thelogin-ndmp capability for successfully authenticating NDMP sessions.


A predefined role, named backup, has the login-ndmp capability by default.To provide a user with the login-ndmp capability, the backup role can beassigned to the group to which the user belongs. However, when a group isassigned the backup role, all users within the group get the login-ndmpcapability. Therefore, it is best to group all NDMP users into a single groupthat has the 'backup' role.

Snapshot copy schedulesScheduled Snapshot copy creation might fail for various reasons, such as avolume being offline. When the volume becomes online again, Data ONTAPdetects the scheduled Snapshot copy creation that has failed and automaticallycreates a Snapshot copy for that schedule. This feature is available in DataONTAP 8.0 7-Mode and later releases in the Data ONTAP 8.0 7-Mode releasefamily.

For more information about this feature, see the Data ONTAP 8.0 DataProtection Online Backup and Recovery Guide for 7-Mode.

SnapMirror support for 64-bit volumesData ONTAP 8.0 and later releases support 64-bit volumes in addition to32-bit volumes. SnapMirror supports replication between 64-bit volumes andalso between 32-bit volumes. However, in Data ONTAP 8.0, there are certainconsiderations when replicating volumes and qtrees using SnapMirror.

When replicating volumes by using SnapMirror, synchronously orasynchronously, the source and destination volumes must be of the same type.Both the source and destination volumes must be 64-bit volumes or they mustboth be 32-bit volumes.

When replicating qtrees by using SnapMirror, the source and destinationvolumes can be of different types. Either the source and or destination volumecan be 64 bit or 32 bit.

SnapVault support for 64-bit volumesData ONTAP 8.0 and later releases support 64-bit volumes. SnapVaultsupports replication between 64-bit volumes, in addition to supportingreplication between 32-bit volumes. When replicating qtrees by usingSnapVault, the source and destination volumes can be of different types. Thesource and destination volumes can be either 64-bit or 32-bit.

For more information about SnapVault replication, see the Data ONTAP 8.0Data Protection Online Backup and Recovery Guide for 7-Mode.


Changes to the Data ONTAP and gateway libraries

The Data ONTAP Software Setup Guide for 7-Mode now provides informationfor basic setup of all systems that run Data ONTAP, including gatewaysystems.

Starting in Data ONTAP 7.3.2, much of the information about using DataONTAP features with gateway systems was integrated into the general DataONTAP guides. This effort was continued in Data ONTAP with theintegration of gateway system setup instructions into the Data ONTAPSoftware Setup Guide for 7-Mode. As of Data ONTAP 8.0 7-Mode, there is nolonger a separate setup guide for gateway.

The gateway documents now focus primarily on information aboutimplementation with the back-end storage arrays.


New and changed commands and options in the DataONTAP 8.1 release family operating in 7-Mode

This section provides information about the commands, options, andconfiguration files that have been changed or added to the Data ONTAP 8.1release family. These changes are described in the following topics:v “New commands in the Data ONTAP 8.1 release family”v “Changed commands in the Data ONTAP 8.1 release family” on page 74v “Replaced or removed commands in the Data ONTAP 8.1 operating in

7-Mode release family” on page 80v “New options in the Data ONTAP 8.1 release family” on page 80v “Changed options in Data ONTAP 8.1 release family” on page 86

New commands in the Data ONTAP 8.1 release family

Many new commands have been added in the Data ONTAP 8.1 in thisrelease.

For each command family and 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

autosupportdestinations show

Lists a summary of alladdresses and URLs thatreceive AutoSupport messages.

Data ONTAP SystemAdministration Guide for7-Mode

autosupport destinationsshow man page

8.1

autosupport historyretransmit

Retransmits a locally storedAutoSupport message,identified by its AutoSupportsequence number.


autosupport historyretransmit man page

8.1



autosupport historyshow

Displays information aboutone or more of the 50 mostrecent AutoSupport messages.


autosupport history showman page

8.1

autosupport manifestshow

Lists the information in theAutoSupport messages,including the name and size ofeach file collected for themessage along with any errors.


autosupport manifestshow man page

8.1

autosupport triggermodify

Enables and disablesAutoSupport messages to yourinternal support organizationfor individual trigger events,and specify additionalsubsystem reports to includein messages sent in responseto individual trigger events.


autosupport triggermodify man page

8.1

autosupport triggershow

Displays the system eventsthat can trigger AutoSupportmessages.


autosupport trigger showman page

8.1

bmc battery-info Displays battery information,for example, battery name,charging status, serial number,part number, firmware andhardware versions, chemistrytype, manufacturer, and dateof manufacture.

na_bmc(1) man page 8.1.2

cifs branchcache hashstat

Displays information aboutBranchCache hash statistics.

Data ONTAP File Accessand Protocols ManagementGuide for 7- Mode cifsbranchcache man page

8.1.1

cifs branchcache setkey

Sets the BranchCache secretkey pass phrase that is used togenerate hashes.

Data ONTAP File Accessand Protocols ManagementGuide for 7- Mode cifsbranchcache man page

8.1.1

coredump segmentconfig modify

Configures the automaticsegmenting of core dump files.


8.1.1



coredump segmentconfig show

Shows the currentconfiguration of automaticcore segmenting.


8.1.1

coredump segmentdelete

Deletes a specified coresegment from the system.


8.1.1

coredump segmentdelete-all

Deletes all core segments fromthe system.


8.1.1

coredump segment show Displays information about thecore segments on the system.


8.1.1

coredump segmentstart

Starts a core segmenting job. Data ONTAP SystemAdministration Guide for7-Mode

8.1.1

coredump segmentstatus

Displays the status of a coresegmenting job.


8.1.1

coredump segment stop Cancels a core segmenting job. Data ONTAP SystemAdministration Guide for7-Mode

8.1.1

disk encrypt destroy Cryptographically destroysself-encrypting disks on aStorage Encryption enabledsystem.

Data ONTAP StorageManagement Guide for7-Mode

8.1

disk encrypt lock Locks self-encrypting disks ona Storage Encryption enabledsystem.


8.1

disk encrypt rekey Rekey self-encrypting disks ona Storage Encryption enabledsystem.


8.1

disk encrypt sanitize Cryptographically erasesself-encrypting disks on aStorage Encryption enabledsystem.


8.1

disk encrypt show Displays self-encrypting diskson a Storage Encryptionenabled system.


8.1

key_manager add Adds key management serversto the storage system.

Data ONTAP StorageManagement Guide

8.1

New and changed commands and options in the Data ONTAP 8.1 release family operating in 7-Mode 71


key_manager query Displays key IDs stored on thekey management servers.


8.1

key_manager rekey Changes the authenticationkey of self-encrypting disks.


8.1

key_manager remove Removes key managementservers from the storagesystem.


8.1

key_manager restore Restores authentication keysstored on key managementservers to the storage system.


8.1

key_manager setup Runs the Storage Encryptionsetup wizard.

Data ONTAP Software SetupGuide for 7-Mode

8.1

key_manager show Displays key managementservers registered with thestorage system.


8.1

key_manager status Displays the communicationstatus of key managementservers registered with thestorage system.


8.1

nfs nsdb flush Removes entries from thename server database cache.

Data ONTAP File Accessand Protocols ManagementGuide for 7-Mode

nfs man page

8.1

nfs vstorage stats Displays statistics for VMwarevStorage over NFS.

Data ONTAP File Accessand Protocols ManagementGuide for 7- Mode

8.1.2

sftp stat Displays SFTP statistics. Data ONTAP File Accessand Protocols ManagementGuide for 7-Mode

sftp man page

8.1

storage shelfidentity

Causes the specified disk shelfto flash its LEDs to help youlocate the shelf.

na_storage(1) man page 8.1.1

storage show bridge Displays information aboutFC-to-SAS bridges.


8.1



system health alertdefinition show

Displays information about thealerts that a health monitorcan potentially generate.


system health alertdefinition show man page

8.1

system health alertdelete

Deletes an alert that was notautomatically cleared


system health alertdelete man page

8.1

system health alertmodify

Suppresses or acknowledgesan alert.


system health alertmodify man page

8.1

system health alertshow

Displays information aboutgenerated alerts, such as theresource and node where thealert was triggered, and thealert's severity and probablecause.


system health alert showman page

8.1

system healthautosupport triggerhistory show

Displays information about theAutoSupport messages thatalerts triggered within the lastweek—for example, todetermine whether an alerttriggered an AutoSupportmessage.


system healthautosupport triggerhistory show man page

8.1

system health configshow

Displays information abouthealth monitors, such as theirnodes, names, subsystems, andstatus.


system health configshow man page

8.1

system healthnode-connectivityadapter show

Displays the status ofadapters, along with otherinformation, such as the ownernode, whether they are usedand enabled, and the numberof shelves attached.


system healthnode-connectivityadapter show man page

8.1



system healthnode-connectivitydisk show

Displays the status of disks,along with other information,such as the owner node, diskname and bay number, andthe number of paths to thedisk.


system healthnode-connectivity diskshow man page

8.1

system healthnode-connectivityshelf show

Displays the status of shelvesfrom the node-level view,along with other information,such as the owner node, shelfname, and how many disksand paths the shelf has.


system healthnode-connectivity shelfshow man page

8.1

system health policydefinition modify

Enables or disables the policythat controls whether a specificresource state raises a specificalert.


system health policydefinition modify manpage

8.1

system health policydefinition show

Displays information abouthealth monitor policies, whichdetermine when alerts areraised.


system health policydefinition show man page

8.1

system health statusshow

Displays the status of theentire system.


system health statusshow man page

8.1

snaplock clockinitialize

Initializes the systemComplianceClock.

Data ONTAP Archive andCompliance ManagementGuide for 7-Mode

8.1

snaplock clock status Displays the systemComplianceClock and volumeComplianceClock time.


8.1

Changed commands in the Data ONTAP 8.1 release family

A number of commands have been changed in this release.


The table provides following information for each command family and eachcommand:v The change in the commandv The location of documentation about the commandv The Data ONTAP 8.1 release in which the change was introduced

Command Change Documentation

Releasecommandchanged in

aggr add The 64 bit-upgrade optionhas been added. This optionenables the administrator toupgrade an aggregate from32-bit to 64-bit format byadding enough storage toexceed the 16-TB maximum32-bit aggregate size.

na_aggr(1) man page andData ONTAP StorageManagement Guide for7-Mode

8.1

aggr create The -c option has beenadded. This option enablesthe administrator to selectdisks or array LUNs with aspecific checksum type whencreating an aggregate.

na_aggr(1) man page 8.1

aggr options The free_space_reallocoption has been added. Thisoption enables or disables freespace reallocation, whichimproves write performanceby optimizing the free spacewithin an aggregate.

na_aggr(1) man page andthe Data ONTAP SystemAdministration Guide for7-Mode

8.1.1

aggr options The hybrid_enabled optionhas been added. This optiondetermines whether anaggregate can be converted toa Flash Pool.

na_aggr(1) man page andthe Data ONTAP SystemAdministration Guide for7-Mode

8.1

aggr status The -R option has beenadded. This option displaysthe serial number and otherinformation used by technicalsupport for the disks in anaggregate.


aggr status For the r option, the numberof blocks for failed disks isnow displayed as "-".





aggr status The -s option now displaysthe checksum types thatspares can be used with.

na_aggr(1) man page 8.1.1

cifs shares The -brachcache has beeadded to the cifs shares-addand cifs shares changecommands. This optionenables BranchCache cachingfor the share.

na_cifs_shares(1) manpage and Data ONTAP FileAccess and ProtocolsManagement Guide for7-Mode

8.1.1

df The hybrid option has beenadded. Used with the Aoption, it displays the size ofthe SSD tier for a Flash Pool.

na_df(1) man page 8.1.1

disk assign The -shelf option has beenadded. This option enablesthe administrator to assign allunassigned disks on a specificshelf to the specifiedcontroller.

na_disk(1) man page 8.1

flexcache eject The -i option has beenadded. This option enablesthe administrator to specifythe inode rather than the filename (for example, flexcacheeject -i /vol/foo/inode:24529). The -i optioncan be useful if the file nameis unknown or the path to thefile name cannot be resolved.

na_flexcache(1) man page 8.1

flexcache fstat The -i option has beenadded. This option enablesyou to specify the inoderather than the file name (forexample, flexcache fstat-i /vol/foo/inode:24529).The -i option can be useful ifthe file name is unknown orthe path to the file namecannot be resolved.

na_flexcache(1) man page 8.1




halt The -s option no longerpowers off the controller.Instead, it halts at theLOADER prompt. Forplatforms that have FRU faultLEDs on the motherboard,Data ONTAP also clears theLEDs when subsequentlybooted.

na_halt(1) man page 8.1.2

lock status The output of this commandnow shows durable lockstates for SMB 2.x and leaseoplock information for SMB2.1 locks.

na_lock(1) man page andData ONTAP File Access andProtocols Management Guidefor 7-Mode

8.1.1

qtree oplock Enables or disables both leaseoplocks and traditionaloplocks. Lease oplocks areavailable if SMB 2.1 isenabled.

na_qtree(1) man page andData ONTAP File Access andProtocols Management Guidefor 7-Mode

8.1.1

setup The prompt to continue setupusing the web interface hasbeen removed from the setupcommand. Starting with DataONTAP 8.1, the web interfacehas been removed and youcannot use OnCommandSystem Manager for initialsetup of the storage system.

Data ONTAP Software SetupGuide for 7- Mode

8.1.2

sis config The manual value for the -soption has been added. Thisoption can be used only onSnapVault destinationvolumes that have qtrees.This option ensures that thededuplication operation is nottriggered automatically afterevery update to thedestination volumes.

na_sis(1) man page andData ONTAP StorageManagement Guide for7-Mode

8.1

sis config The -I option has beenadded. This option allows theadministrator to enable ordisable in-line compression.

na_sis(1) man page 8.1




sis config The -C option has beenadded. This option enablesthe administrator to enable ordisable post-processcompression.


sis start The -p option has beenadded. This option enablesthe deduplication operation touse the previous check point.


8.1

sis start The -q option has beenadded. This option enablesthe administrator to queuethe deduplication operations.


sis status The -l option has beenmodified. The output of thesis status -l command nowincludes the status ofinline-compression andpost-process compression fora volume.


8.1

snap autodelete The file_clone value for thedestroy_list option has beenadded. This value is used todelete Snapshot copies thatare locked by file clones.

na_snap(1) man page and

Data ONTAP Data ProtectionOnline Backup and RecoveryGuide for 7-Mode

8.1

snapmirror resync The -c has been added. Thisoption creates a Snapshotcopy (with the name,snapshot_name) on thedestination after theresynchronization transfer iscomplete. This is done toensure that the transfer doesnot coincide with anyongoing updates.Note: This option is validonly for a qtree.

na_snapmirror(1) manpage and Data ONTAP DataProtection Online Backup andRecovery Guide for 7- Mode

8.1

storage show disk The dongle revision has beenadded to the commandoutput.

8.1.1




storage show disk The serial number of thecarrier has been added to theoutput for disks in multi-diskcarrier disk shelves.

8.1.1

sysconfig The -a option now includesinformation about anyFC-to-SAS bridges present.The -P option enumerates thePCI hierarchy of the system,enabling the support anddebug of errors from the PCIsubsystem. The -P option isnot supported on allplatforms.

na_sysconfig(1) man page 8.1

sysconfig The -P option displaysinformation about thephysical host machine and itsmapping to the virtualmachine.

na_sysconfig(1) man page 8.1.1

vol modify The space-mgmt-try-firstoption has been added. Thisoption enables theadministrator to choosebetween the autogrowfunctionality and autodeletesnapshot as the first choicefor providing more free spacefor a volume.

na_vol(1) man page andData ONTAP StorageManagement Guide for7-Mode

8.1

vol options Thesnaplock_autocommit_periodoption is added to set theautocommit period.


8.1

vol status The output of this commandnow includes the format(32-bit or 64-bit) of thevolume.

na_vol(1) man page andData ONTAP StorageManagement Guide for7-Mode

8.1

vol status With the -v option specified,the output of this commandnow includes the read andwrite caching eligibility forvolumes associated with aFlash Pool.


8.1.1


Replaced or removed commands in the Data ONTAP 8.1 operating in 7-Moderelease family

The following information lists replaced or removed commands in DataONTAP 8.1 7-Mode.

Support for the following commands will be discontinued in a future versionof Data ONTAP. To perform the equivalent operations, use the aggr command.v vol add

v vol media_scrub

v vol migrate

v vol mirror

v vol scrub

v vol split

v vol verify

v vol wafliron

The following commands are removed from Data ONTAP 8.1:v vol compress

v date -c

v date -c initialize

v filestats

v ups

New options in the Data ONTAP 8.1 release family

This release includes new options that you can use with the optionscommand. The table gives the following information:v Purpose of the optionv Default value for the optionv The Data ONTAP release in which the option was introduced

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

Option Purpose Default value Release added

autosupport.local_collection Enables or disables localstorage of AutoSupportfiles when sending ofAutoSupport messages isdisabled.

on 8.1



autosupport.max_http_size Specifies the maximumfile size for HTTP andHTTPS transfers ofAutoSupport messages.

10 MB 8.1

autosupport.max_smtp_size Specifies the maximumemail message size forSMTP (email) transfers ofAutoSupport messages.

5 MB 8.1

autosupport.payload_format Specifies the file format ofthe compressed file thatcontains AutoSupportdata.

7z 8.1

autosupport.support.put_url Indicates whereAutoSupport messagesfor IBM technical supportare sent ifautosupport.support.transport is http orhttps and the serverreceiving the messagesupports HTTP PUTrequests. Read only.

eccgw01.boulder.ibm.com/support/electronic/nas

8.1

autosupport.validate_digital_certificate Determines whether thestorage system validatesthe remote digitalcertificates that it receives.Applies only whenautosupport.support.transport is set tohttps.

on 8.1

cf.giveback.auto.after.panic.takeover Enables or disablesautomatic giveback aftera takeover-on-panic.

on 8.1.2

cifs.smb2.client.enable Enables or disables thestorage system's SMB 2.0client capability.

off 8.1

cifs.smb2.durable_handle.enable Enables or disables SMB2.0 durable handles.

on 8.1

cifs.smb2.durable_handle.timeout Specifies the maximumlifetime of SMB 2.0durable handles beforethey expire.

960 seconds 8.1

cifs.smb2.enable Enables or disables theSMB 2.0 protocol.

on 8.1

cifs.smb2.signing.required Enforces the requirementfor clients to sign SMB 2.0messages.

off 8.1



cifs.smb2_1.branch_cache.enable Enables or disablesBranchCache on thestorage controller.

off 8.1.1

cifs.smb2_1.branch_cache.hash_time_out Sets the time (in seconds)that an unusedBranchCache hash for afile can be kept in thestorage system's memory.

3600s 8.1.1

cifs.W2K_password_change Enables or disablesautomatic storage systemdomain account passwordchange.

off 8.1.1

cifs.W2K_password_change_interval Sets the time duration (inweeks) after which DataONTAP triggers a domainpassword change. Appliesonly whencifs.W2K_password_changeis set to on.

4w 8.1.1

cifs.W2K_password_change_within Sets the time duration (inweeks) after which DataONTAP triggers a domainpassword change. Appliesonly whencifs.W2K_password_change is set to on.

1h 8.1.1

flexscale.rewarm Determines whether theWAFL external cachepreserves the cache in aFlash Cache moduleduring a gracefulshutdown.

on 8.1

ftpd.explicit.allow_secure_data_conn Allows or prevents theopening of explicit FTPSdata connections in securemode.

on 8.1

ftpd.explicit.enable Enables or disablesexplicit FTPS.

off 8.1

ftpd.implicit.enable Enables or disablesimplicit FTPS.

off

ip.tcp.abc.enable Enables or disables theuse of Appropriate ByteCounting (ABC) in TCPcongestion control.

on 8.1

ip.tcp.abc.l_limit Specifies the value of theL limit used to increasethe congestion windowduring the slow startphase in TCP.

22 8.1



ip.tcp.rfc3390.enable Enables or disables theuse of RFC 3390 toincrease the initialwindow used by TCPconnections.

on 8.1

licensed_feature.disk_sanitization.enable Enables or disables thedisk sanitization featureon all systems. Note thatafter you enable disksanitization on yoursystem, it cannot bedisabled.

off 8.1

licensed_feature.fcp.enable Enables or disables theuse of iSCSI on N3400,N5000 series, N6000series, and N7000 seriessystems. For all othersystems, you mustpurchase a license to usethis protocol andadminister it by using thelicense commands.

off 8.1

licensed_feature.flexcache_nfs.enable Enables or disables theuse of FlexCache withNFS clients on allsystems.

off 8.1

licensed_feature.iscsi.enable Enables or disables theuse of the iSCSI protocolon N3400, N5000, N6000,and N7000 series systems.For all other systems, youmust purchase a licenseto use this protocol andadminister it by using thelicense commands.

off 8.1

licensed_feature.multistore.enable Enables or disablesMultiStore on N3220,N3240, N3400, N6200series, and N7x50Tsystems. For all othersystems, you mustpurchase a license to usethis feature andadminister it by using thelicense commands.

off 8.1

licensed_feature.nearstore_option.enable Enables or disables theNearStore feature on allsystems.

off 8.1

licensed_feature.vld.enable Enables or disables VLDon all systems.

off 8.1



nfs.always.deny.truncate Controls whether NFSv2and NFSv3 clients cantruncate files in UNIXqtrees that are alsoopened from a CIFS clientwith DENY writepermissions.

on 8.1

nfs.nfs_rootonly Controls NFS requestsfrom non-reserved ports

on 8.1.1

nfs.rpcsec.trace Enables EMS messagesfor troubleshootingKerberos issues.

off 8.1.2

nfs.v2.enable Enables or disablesNFSv2.

on 8.1.1

nfs.v3.snapshot.active.fsid.enable Specifies the file systemID handling behavior forNFSv3.

on 8.1

nfs.v4.id.allow_numerics Allows or disallowsNFSv4 user and groupIDs as strings.

on 8.1.1

nfs.v4.snapshot.active.fsid.enable Specifies the file systemID handling behavior forNFSv4.

off 8.1

nfs.vstorage.enable Enables or disablesVMware vStorage overNFS.

off 8.1.1

rlm.autologout.enable Enables or disables theautomatic logout of idleRLM SSH connections.

on 8.1.1

rlm.autologout.timeout Specifies the number ofminutes after which RLMSSH idle connections aredisconnected ifrlm.autologout.enableison.

60 8.1.1

rlm.ssh.access Restricts SSH access tothe RLM.

* 8.1.1

security.passwd.rules.minimum.lowercase Controls the minimumnumber of lowercasealphabetic characters ("a"to "z") that a passwordmust contain. This optionis ignored if thesecurity.passwd.rules.enable option isnot set to on.

0 8.1.2



security.passwd.rules.minimum.uppercase Controls the minimumnumber of uppercasealphabetic characters ("A"to "Z") that a passwordmust contain. This optionis ignored if thesecurity.passwd.rules.enable option isnot set to on.

0 8.1.2

sftp.auth_style Specifies the SFTPauthentication style.

mixed 8.1

sftp.bypass_traverse_checking Enables or disables SFTPbypass traverse checking.

off 8.1

sftp.dir_override Specifies the SFTPoverride path for userhome directories.

" " (null) 8.1

sftp.dir_restriction Enables or disables SFTPuser home directoryrestrictions.

off 8.1

sftp.enable Enables or disables SFTP. off 8.1

sftp.idle_timeout Specifies the maximumSFTP connection idle timebefore termination inseconds.

900 8.1

sftp.locking Enables or disables SFTPfile locking.

none 8.1

sftp.log_enable Enables or disables SFTPevent logging.

on 8.1

sftp.log_filesize Specifies the maximumsize of the SFTP log files.

512K 8.1

sftp.log_nfiles Specifies the maximumnumber of SFTP log files.

6 8.1

sftp.max_connections Specifies the maximumnumber of SFTPconnections.

15 8.1

sftp.max_connections_threshold Specifies when togenerate a maximumSFTP connection warningin percent.

75 8.1

sftp.override_client_permissions Enables or disables UNIXpermissions specified bySFTP clients.

off 8.1

snapmirror.volume.local_nwk_bypass.enable Determines whether localSnapMirror transferoptimization is enabled.

on 8.1



snapmirror.vsm.volread.smtape_ enable Enables or disables thenew SMTape engine thatprovides a betterperformance to write totape devices.

on 8.1.1

sp.autologout.enable Enables or disables theautomatic logout of idleSP SSH connections.

on 8.1.1

sp.autologout.timeout Specifies the number ofminutes after which SPSSH idle connections aredisconnected ifsp.autologout.enable ison.

60 8.1.1

sp.ssh.access Restricts SSH access tothe SP.

* 8.1.1

tftpd.enable Enables or disables theTFTP server.

off 8.1

tftpd.max_connections Specifies the maximumnumber of TFTPconnections.

8 8.1

vsm.smtape.concurrent.cascade.support Enables or disablesconcurrent volumeSnapMirror and SMTapebackup operations

off 8.1

Changed options in Data ONTAP 8.1 release family

This table lists options that have changed or become obsolete.

For each option, the following table gives this information:v Name of the changed optionv Nature of the changev Data ONTAP 8.1 7-Mode release in which the change was introduced


Option ChangeReleasechanged

autosupport.content The minimal setting encodes and maskscertain private data, instead of omittingit.

8.1

autosupport.local.nht_data.enable Removed 8.1



autosupport.local.performance_data.enable Removed 8.1

autosupport.mailhost, autosupport.proxy,and autosupport.support.url

Support IPv6 addresses, as well as IPv4addresses.

8.1

autosupport.support.url Applies only to HTTP POST requests, notto HTTP PUT requests, which areconfigured usingautosupport.support.put_url

8.1

cf.giveback.auto.attempts.minutes The default for this option has beenchanged to 60.

8.1.2

cf.giveback.auto.attempts.count The default for this option has beenchanged to 2.

8.1.2

cf.giveback.auto.delay.seconds The default for this option has beenchanged to 600.

8.1.2

cf.giveback.auto.terminate.bigjobs The default for this option has beenchanged to off.

8.1

cifs.max_mpx The default for this option has beenchanged to 253.

8.1

cifs.oplocks.enable Enables or disables both lease andopportunistic locks. Lease locks areavailable when SMB 2.1 is enabled.

8.1.1

cifs.smb2.client.enable Removed 8.1.1

cifs.smb2.durable_handle.enable Removed 8.1.1

cifs.smb2.durable_handle.timeout Removed 8.1.1

cifs.smb2.enable Enables and disables both SMB 2.0 andSMB 2.1. Since enabling SMB 2.1 is arequirement for BranchCache, disablingthis option also disables BranchCache.

8.1.1

cifs.smb2.signing.required Applies to SMB 2.1, as well as SMB 2.0. 8.1.1

cifs.weekly_W2K_ password_change Removed. Replaced with three newoptions: cifs.W2K_password_change,cifs.W2K_password_change_interval, andcifs.W2K_password_change_within

8.1.1

nfs.authsys.extended_groups_ns.queue_max The maximum value for this option hasbeen changed to 640.

8.1.2

nfs.v4.id.allow_numerics The default for this option has beenchanged to off.

8.1.2



snaplock.autocommit_period This system-level option can be used onlyfor viewing the autocommit time periodof the SnapLock volumes that wereupgraded. This option is now inread-only state.

8.1

security.admin.nsswitchgroup This option now enables you to mapLDAP groups to specified roles on thesystem.

8.1.1


New and changed commands and options in the DataONTAP 8.0 7-Mode release

This section provides information about the commands, options, andconfiguration files that have been changed or added to the Data ONTAP 8.07-Mode release family. If you are upgrading to Data ONTAP 8.1 or later froma 7.3.x release, these changes will apply to your system in addition to thoseintroduced in the 8.1 release family.v “New commands in Data ONTAP 8.0 7-Mode”v “Changed commands in the Data ONTAP 8.0 7-Mode release family” on

page 93v “Replaced or removed commands in the Data ONTAP 8.0 7-Mode release

family” on page 96v “New options in the Data ONTAP 8.0 7-Mode release family” on page 97v “Changed options in the Data ONTAP 8.0 7-Mode release family” on page

99

New commands in Data ONTAP 8.0 7-Mode

Many new commands have been added in the Data ONTAP 8.0 7-Moderelease family.

The table gives the following information for each command family andcommand:v The purpose of the commandv The location of documentation about the commandv The Data ONTAP 8.0 7-Mode release in which the command was

introduced

Command Purpose Documentation Release introduced

acpadmin configure Configures the ACPsubsystem.

Data ONTAPStorage ManagementGuide for 7-Mode

na_acpadmin(1)man page

8.0



acpadmin list_all Displays information aboutthe ACP (Alternate ControlPath) storage subsystem.



8.0

bmc battery-info Displays battery information,for example, battery name,charging status, serial number,part number, firmware andhardware versions, chemistrytype, manufacturer, and dateof manufacture.

na_bmc(1) manpage

8.0.4

cdpd Displays information aboutdevices that advertisethemselves by using theCDPv1 protocol.

Data ONTAP 8.0NetworkManagement Guidefor 7-Mode

8.0.1

du Displays the files and amountof space that they occupy in adeduplicated volume.


8.0.1

ifgrp Manages interface groups onyour storage system.

This command replaces thevif command. However, theoptions remain the same.

Data ONTAPNetworkManagement Guidefor 7-Mode

8.0

revert_to Transitions Data ONTAP to arelease in an earlier releasefamily

Data ONTAPUpgrade andRevert/DowngradeGuide for 7-Mode

revert_to(1) manpage

8.0

smtape abort Aborts a backup or restore jobinitiated by the SMTapeengine.

Data ONTAP DataProtection TapeBackup and RecoveryGuide for 7-Mode

na_smtape manpage

8.0



smtape backup Backs up blocks of data totape.


na_smtape manpage

8.0

smtape continue Continues an SMTape-initiatedbackup or restore operationafter it has reached the end ofcurrent tape and is in the waitstate to write output to oraccept input from a new tape.


na_smtape manpage

8.0

smtape restore Restores blocks of data fromtape.


na_smtape manpage

8.0

smtape status Display the status ofSMTape-initiated backup andrestore operations


na_smtape manpage

8.0

sp help Displays the Data ONTAP spcommands that you can enterat the storage system prompt.

Data ONTAP SystemAdministration Guidefor 7-Mode

na_sp(1) man page

8.0.1

sp reboot Reboots the SP and causes theSP to perform a self-test.


na_sp(1) man page

8.0.1

sp setup Initiates the interactive SPsetup script.


na_sp(1) man page

8.0.1

New and changed commands and options in the Data ONTAP 8.0 7-Mode release 91


sp status Displays the current statusand the network configurationof the SP.


na_sp(1) man page

8.0.1

sp test autosupport Sends a test email to allrecipients specified with theautosupport.to option.


na_sp(1) man page

8.0.1

sp test snmp Performs SNMP test on the SP,forcing the SP to send a testSNMP trap to all trap hostsspecified in the snmp traphostcommand.


na_sp(1) man page

8.0.1

sp update Updates the SP firmware. Data ONTAPUpgrade andRevert/DowngradeGuide for 7-Mode

na_sp(1) man page

8.0.1

storage array modify Modifies attributes of arrayprofile records.

na_storage(1) manpage

8.0

storage arraypurge-database

Removes all records from thecontroller's array profiledatabase.


8.0

storage array remove Removes records for thespecified array from thecontroller’s array profiledatabase.


8.0

storage arrayremove-port

Removes ports associated withan array profile.


8.0

storage array show Lists all array profile recordsknown to the controller.


8.0

storage arrayshow-config

Provides a summary of theconnectivity to SAN-attachedarrays connected to thegateway system's FC initiatorports.

Gateway InstallationRequirements andReference Guide


8.0

storage array show-lunsarray-name

Lists all array LUNs exportedfrom a named storage array.


8.0



storage array show-ports Lists all target ports for allstorage arrays known to thegateway system.


8.0

storage show acp Displays information aboutthe ACP (Alternate ControlPath) storage subsystem.



8.0

Changed commands in the Data ONTAP 8.0 7-Mode release family

This table lists the commands that have been changed in the Data ONTAP 8.07-Mode release family.

The table gives the following information for each command family and eachcommand:v The change in the commandv The location of documentation about the commandv The Data ONTAP 8.0 7-Mode release in which the change was introduced



aggr create The -B option has beenadded. This option is usedto create a 64-bit aggregate.

na_aggr(1) man pageand Data ONTAPStorage ManagementGuide for 7-Mode

8.0

df The -x option has beenadded. This optionsuppresses the display ofthe .snapshot lines.

na_df(1) man page 8.0

disk assign You can no longer use thiscommand to change theownership of a disk orarray LUN that is alreadyowned unless you arerunning the command onthe system that owns thedisk already.

na_disk(1) man page 8.0




environment shelf The ComplexProgrammable Logic Device(CPLD) version has beenadded to the output.

na_environment(1)man page

8.0

flexcache fstat The -inode-file optionhas been added. Thisoption displays the numberof blocks used by theFlexCache volume's inodefile.

na_flexcache(1) manpage

8.0.3

halt The -s option no longerpowers off the controller.Instead, it halts at theLOADER prompt. Forplatforms that have FRUfault LEDs on themotherboard, Data ONTAPalso clears the LEDs whensubsequently booted.

na_halt(1) man page 8.0.4

ifgrp create multi The port value (port-basedload-balancing) for the -boption has been added.

Data ONTAP NetworkManagement Guide for7-Mode

8.0.1

software update The -r option, whichsuppresses automaticreboot, is now the default.To request an automaticreboot, you now mustspecify the -R option.

na_software(1) manpage

Data ONTAP Upgradeand Revert/DowngradeGuide for 7-Mode

8.0.1

storage show acp A column for "Moduletype" has been added to theoutput. This shows the typeof the I/O module.


8.0.1

storage show expander The system interconnectlink (SIL) ports (the lastfour rows of output) arenow shown as [SIL0]through [SIL3]. Previouslythey were shown as [DIS0]through [DIS3].


8.0




storage show expander The EXN3000 and EXN3500storage expansion unitports are now listed as[SQR0]-[SQR3] for thesquare ports and[CIR4]-[CIR7] for the circleports. Previously theseports were listed as [IO0]-[IO7].


8.0

storage show fault You can now specify astorage expansion unitname for this command tosee information about aspecific storage expansionunit.


8.0.1

sysconfig When the -r option is usedto display disk informationfor SAS-connected disks,the CHAN (channel)column now displays theport as "A" or "B", just as itdoes for FC-connecteddisks. Previously, "1" and"2" were used.

na_sysconfig(1) manpage

8.0

sysconfig When the -a option is used,the output includes statusand power information forany IOXM modules present.


8.0.1

sysconfig When the -v option is used,any disabled ports show"N/A" for the data linkrate.


8.0.2

vif This command has beenreplaced by the ifgrpcommand.

Data ONTAP NetworkManagement Guide for7-Mode

8.0

vol options The extent option enablesextents but can only beused on FlexVol volumes.

na_vol(1) man pageand the Data ONTAPSystem AdministrationGuide for 7-Mode

8.0

vol options The read_realloc optionenables read reallocationbut can only be used onFlexVol volumes.

na_vol(1) man pageand the Data ONTAPSystem AdministrationGuide for 7-Mode

8.0




vol status When the -r option is usedto display disk informationfor SAS-connected disks,the CHAN (channel)column now displays theport as "A" or "B", just as itdoes for FC-connecteddisks. Previously, "1" and"2" were used.

na_vol(1) man page 8.0

Replaced or removed commands in the Data ONTAP 8.0 7-Mode release family

The following information lists replaced or removed commands in DataONTAP 8.0 7-Mode.

Support for the following commands will be discontinued in a future versionof Data ONTAP. To perform the equivalent operation, use the aggr command.v vol add

v vol media_scrub

v vol migrate

v vol mirror

v vol scrub

v vol split

v vol verify

v vol wafliron

These commands are removed in Data ONTAP 8.0 7-Mode.v snapmirror store

v snapmirror use

v snapmirror retrieve

In Data ONTAP 8.0 7-Mode release, the vif command has been replaced bythe ifgrp command. For more information, see the Data ONTAP 8.0 NetworkManagement Guide for 7-Mode.


New options in the Data ONTAP 8.0 7-Mode release family

The table gives the following information for each new option that can beused with the options command:v Description of the option's purposev Default value for the optionv Data ONTAP 8.0 7-Mode release in which the option was introduced


Option PurposeDefault valueor example

Releaseintroduced

autosupport.performance_ data.doitany_string

Triggers a performance snapshotAutoSupport message when anystring is added.

Not available 8.0

autosupport.periodic.tx_ window time Specifies the randomized delaywindow for periodic AutoSupportmessages.

60 minutes 8.0.1

cf.takeover.on_panic Triggers a takeover if the partnermode panics.

On 8.0

cf.takeover.on_reboot Triggers a takeover if the partnernode reboots.

on, unless FCPor iSCSI islicensed, inwhich case thedefault is off.

8.0

cf.givegack.auto.delay.seconds Adjusts the giveback delay time forautomatic giveback.

300 seconds 8.0

lun_ic_alua_changed Disables ALUA State Change UnitAttention on interconnect up ordown events.

off 8.0.1 and8.0.3Note: Thisoption isnotavailable inDataONTAP8.0.2.

interface.blocked.mgmt_data_traffic Blocks or allows data traffic on themanagement interface, e0M

off for systemsupgraded froman earlierrelease; on fornew systems

8.0.2

ndmpd.data_port_range Specifies a port range on which theNDMP server can listen for dataconnections.

all 8.0.1


Option PurposeDefault valueor example

Releaseintroduced

nfs.always.deny.truncate Controls whether NFSv2 and NFSv3clients can truncate files in UNIXqtrees that are also opened from aCIFS client with DENY writepermissions.

on 8.0.2

nfs.max_num_aux_ groups Specifies the maximum number ofauxiliary UNIX groups that a usercan be a member of.

32 8.0

nfs.rpcsec.trace Enables EMS messages fortroubleshooting Kerberosauthentication and connectivityissues.

off 8.0.4

nfs.v3.snapshot.active.fsid.enable Determines whether the FSID ofobjects in a Snapshot copy matchesthe FSID of the active file system forNFSv3.

on 8.0.1

nfs.v4.snapshot.active.fsid.enable Determines whether the FSID ofobjects in a Snapshot copy matchesthe FSID of the active file system forNFSv4.

off 8.0.1

fpolicy.multiple_ pipes Enables multiple open instances ofthe SMB named pipe on an FPolicyserver.

on 8.0

snapvault.snapshot_for_dr_backup Enables you to specify the Snapshotcopy to use for updating thedestination system when backing upa volume SnapMirror destinationusing SnapVault.

vsm_base_only 8.0.2

sp.setup Displays whether the SP has beenconfigured.

Not available 8.0.1

ssl.v2.enable Enables or disables SSLv2. on 8.0.1

ssl.v3.enable Enables or disables SSLv3. on 8.0.1

New option for the vfiler dr configure command

Data ONTAP 8.0.3 and later provide a new option -u for the vfiler drconfigure command. This option enables you to set up a disaster recoveryvFiler unit without reinitializing the existing SnapMirror relationship betweenthe source and the destination storage systems.

If there is no SnapMirror relationship set between the source and destinationstorage systems, and you run the vfiler dr configure command with the -uoption, then the SnapMirror relationship is in the uninitialized state. If yourun the vfiler dr activate command when the SnapMirror relationship is inthe uninitialized state, the activation of the disaster recovery vFiler unit fails.


To initialize the SnapMirror relationship between the source and destinationstorage systems, you must run the vfiler dr resync command on thedestination storage system.

For more information about using this option, see the na_vfiler(1) man page.

Changed options in the Data ONTAP 8.0 7-Mode release family

This table lists options that have changed or become obsolete.

The table gives the following information for each option:v Name of the changed optionv Nature of the changev Data ONTAP 8.0 7-Mode release in which the change was introduced


Option Change Release changed

autosupport.minimal.subject.id The default for this option has beenchanged to systemid for systemsshipped with Data ONTAP 8.0.27-Mode or later.

8.0.2

cifs.max_mpx The default for this option has beenchanged to 253.

8.0.2

flexscale.max_io_qdepth This option has become obsolete. 8.0

httpd.admin.enable The default for this option has beenchanged to off for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

httpd.admin.ssl.enable The default for this option has beenchanged to on for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

rsh.enable The default for this option has beenchanged to off for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

ssh.enable The default for this option has beenchanged to on for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0


Option Change Release changed

ssh2.enable The default for this option has beenchanged to on for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

security.passwd.rules.everyone The default for this option has beenchanged to on for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

security.passwd.rules.history The default for this option has beenchanged to 6 for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

telnet.distinct.enable The default for this option has beenchanged to on for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

telnet.enable The default for this option has beenchanged to off for systems shippedwith Data ONTAP 8.0 7-Mode orlater.

8.0

timed.log This option has become obsolete. 8.0

timed.max_skew This option has become obsolete. 8.0

timed.min_skew This option has become obsolete. 8.0

timed.proto This option supports only the ntpprotocol.

8.0

timed.sched This option has become obsolete. 8.0

timed.window This option has become obsolete. 8.0


Requirements for running Data ONTAP 8.1 7-Mode

You can use the information in this section to verify whether you have thestorage systems and firmware needed to run 7-Mode software for the DataONTAP 8.1 release family.

To find out your storage system model's capacity and maximum volume size,see the IBM System Storage N series Introduction and Planning Guide.

Supported systems

You need a supported storage systems listed in this section to run a release inthe Data ONTAP 8.1 family operating in 7- Mode.

The following models of storage systems are supported:v N5300 and N5600 storage systemsv N3220 and N3240 storage systemsv N3150v N3400 storage systemsv N6000 series systemsv N6200 series systemsv N7000 series systemsv N7x50T

All systems supported by Data ONTAP 8.1 release family operating in 7-Modecan be configured as an HA pair.

For additional information about supported storage systems in the DataONTAP 8.1 operating in 7-Mode release family, see the IBM System Storage Nseries Introduction and Planning Guide.

Unsupported systems

The following N series storage systems models are not supported in DataONTAP 8.1 release family operating in 7-Mode:v N3300 and N3600 storage systemsv N5200 and N5500 storage systemsv N3700 storage systems


Storage system firmware

You need to confirm that you have the latest firmware for your storagesystem, disks, and storage expansion units.

The following storage system components have firmware that sometimesrequires upgrading: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 supportwebsite, which is accessed and navigated as described in “Websites” on page2.

Note: The latest system firmware is included with Data ONTAP upgradepackages. For more information, see the Data ONTAP 8.1 Upgrade andRevert/Downgrade Guide 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 page2.

Note: New disk firmware is sometimes included with Data ONTAP upgradepackages. For more information, see the Data ONTAP 8.1 Upgrade andRevert/Downgrade Guide for 7-Mode.

Disk storage expansion unit and ESH firmware

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


Gateway requirements and support information

Not all Data ONTAP releases support the same features, configurations,storage system models, and storage array models for gateway systems. TheGateway Support Matrix is the final authority on supported configurations,storage array firmware and microcode versions, switches, and so on.

See the Gateway Support Matrix, located on the IBM N series supportwebsite, which is accessed and navigated as described in “Websites” on page2, for complete information about supported gateway models and storagearrays, as well as supported microcode, license code, and storage arrayfirmware versions. The Gateway Support Matrix also identifies switchconnectivity and topology that can be used with gateway systems.

Gateway system limits information

The Gateway System Limits Reference for Third-Party Storage is beingreleased for the first time with Data ONTAP 8.1.1. This document providesinformation about limits that you need to be aware of when planning agateway system configuration with third-party storage.

This document includes the following information:v Minimum and maximum array LUN size that Data ONTAP supportsv Minimum root volume size for array LUNsv Minimum size for aggregates with array LUNsv Maximum number of devices in a gateway neighborhoodv System capacities

This document covers the Gateway system limits for all platforms and all theData ONTAP 8.x releases.

Requirements for running Data ONTAP 8.1 7-Mode 103

Important cautions

Before upgrading to this release of Data ONTAP, make sure that you read thefollowing items to identify and resolve issues that might affect the operationof your storage systems.v “Upgrade and revert cautions” on page 106v “Manageability cautions” on page 116v “Storage management cautions” on page 116v “Network protocol cautions” on page 119v “File access and protocols cautions” on page 120v “SAN administration cautions” on page 122v “Data protection cautions” on page 123


Upgrade and revert cautions

If you are upgrading to this Data ONTAP release or reverting from thisrelease to an earlier release, you should review these issues, and if any applyin your environment, take appropriate action.

For more information about procedures and planning, see the Data ONTAP 8.1Upgrade and Revert/Downgrade Guide for 7-Mode.v “iSCSI target adapters not supported in Data ONTAP 8.1 and later” on page

107v “Change in nondisruptive upgrade procedure” on page 107v “Upgrade process changes with Data ONTAP 7-Mode software images” on

page 107v “EXN2000 storage expansion units with ESH2 modules no longer

supported” on page 108v “License updates required before upgrading” on page 109v “Upgrade from 7.3.x to 8.1.x through intermediate upgrade with

deduplication disabled can cause a system panic” on page 109v “If you revert to a release earlier than Data ONTAP 8.1, you might need to

install licenses for some products” on page 110v “N6210 series and N6040 series storage systems with Flash Cache modules

are supported” on page 110v “NDU not available for SAN systems with some versions of Linux hosts

running high-speed interconnects” on page 111v “IPv6 address entries in /etc/exports file missing brackets after upgrading”

on page 112v “Erroneous reboot message during Data ONTAP reversion” on page 112v “Reverting to an earlier release on a N6210 with more than 200 volumes

can cause a system panic” on page 113v “Validation of LUNs fails when reverting from Data ONTAP 8.1 to some

earlier releases” on page 113v “Downgrade to 8.1 not allowed for N6040 and N6210 systems with Flash

Cache modules” on page 113v “MultiStore license and vFiler units removed when reverting to Data

ONTAP release earlier than 8.1” on page 114v “Revert from Data ONTAP 8.1.x to Data ONTAP 8.0.x fails if fingerprint

database size exceeds 256 GB” on page 114v “Downgrading to Data ONTAP 8.1 or earlier with a Flash Pool root

aggregate disables the system” on page 114


iSCSI target adapters not supported in Data ONTAP 8.1 andlater

The iSCSI target adapter cards Emulex LPe100i-D1 (Feature Code 1020),Emulex LP100i-D1 (Feature Code 1010), Emulex LPe100i-F1 (Feature Code1021), and Emulex LP100i-F1 (Feature Code 1011) are not supported in DataONTAP 8.1 and later. iSCSI targets are still supported on Ethernet and unifiedtarget adapter ports.

These adapters are reported as Emulex LPe100i-D1, Emulex LP100i-D1,Emulex LPe100i-F1, and Emulex LP100i-F1 in the sysconfig command output.

Before upgrading to Data ONTAP 8.1 or later, move all iSCSI traffic to otherports and remove these adapters from the storage controllers.

Change in nondisruptive upgrade procedure

When you upgrade to this Data ONTAP release, you should be aware ofchanges in the software update command syntax and the requirement forboot environment access.

Beginning with 7.3.5 and 8.0.1, system firmware is updated automatically. It isno longer necessary to access the boot environment for upgrades from a DataONTAP 8.0.x release to a later release.

Note: This change only refers to minor nondisruptive upgrades (within arelease family). When upgrading to a Data ONTAP 8.0.x release from anearlier release family, you must enter the boot environment during thetakeover phase to ensure that the Data ONTAP 8.0.x release is running thecorrect firmware release.

Beginning with 7.3.5 and 8.0.1, the -r option (no automatic reboot) is thedefault for the software update command.

Note: However, when you first upgrade to Data ONTAP 7.3.5 or 8.0.1 or alater release in the 8.0 family, you must specify the -r option fornondisruptive upgrades. In subsequent major and minor nondisruptiveupgrades, it will no longer be required to specify the option.

Upgrade process changes with Data ONTAP 7-Mode softwareimages

When you upgrade to Data ONTAP 8.0 and later releases, you must obtainData ONTAP software images from the IBM N series support website, whichis accessed and navigated as described in “Websites” on page 2 and copythem to your storage system. Media kits, including CD-ROMs with Data

Important cautions 107

ONTAP software images, are no longer available, and the process of installingupgrade images from UNIX or Windows clients is no longer supported.

Beginning with Data ONTAP 8.0, media kits including CD-ROMs are nolonger available. You must obtain software images from the IBM N seriessupport website, which is accessed and navigated as described in “Websites”on page 2 and copy them to your storage system or to an HTTP server inyour environment.

Beginning with Data ONTAP 8.0, the following processes are no longersupported for extracting and installing Data ONTAP upgrade images:v Using the tar command from UNIX clientsv Using the setup.exe file and WinZip from Windows clients

For the upgrade to Data ONTAP 8.0 and later releases, .exe images are nolonger available. You must use one of the following image types dependingon the upgrade you are performing:v .zip images, for upgrades from an earlier release family to Data ONTAP 8.0v .tgz images, for upgrades from any Data ONTAP 8.0 release to a later

release

After you have upgraded to Data ONTAP 8.0 or later, you can only use .tgzimages for further upgrades.

After you have copied the .zip or .tgz image to your storage system, you caninstall it with the software update command. Alternatively, you can make the.zip or .tgz image available from an HTTP server in your environment, thenuse the software update command to copy the upgrade image from the HTTPserver, extract and install the system files, and download the files to the bootdevice with one command.

For more information about upgrade images, see the Data ONTAP Upgrade andRevert/Downgrade Guide for 7-Mode.

EXN2000 storage expansion units with ESH2 modules nolonger supported

Beginning with Data ONTAP 8.1, EXN2000 storage expansion units with ESH2storage I/O modules are no longer supported. If even one of these devices isattached to your storage system, do not upgrade to Data ONTAP 8.1 or lateruntil after you replace the devices. For more information, see “Systemsincluding EXN2000 storage expansion units with ESH2 modules” on page 17.


License updates required before upgrading

If you are upgrading the N3400, N6200 series, or N7x50T storage systemsfrom a Data ONTAP 8.0.x release to a Data ONTAP 8.1.x release, you mustrelicense certain features. This requirement does not apply to the N6000 andN7000 series storage systems.

Beginning in the Data ONTAP 8.1 release family, features are packagedtogether so that only one license key is required to add a group of features toN3220, N3240, N3400, N6200, or N7x50T.

If you were using a feature in a Data ONTAP 8.0.x release and you upgradeto Data ONTAP 8.1.x, the action you take depends on how your features werelicensed in the Data ONTAP 8.0.x release.v You purchased a license pack, but you added individual feature keys only.

You must add the license key for the packs that include any individualfeature key you were using previously.

v You acquired your individual feature keys before license packs wereavailable and have not yet purchased a license pack.You must contact your IBM representative to purchase and install licensepacks that include the features you were using.

To ensure continued access to a feature that requires a license, you should addthe pack license key before you upgrade to Data ONTAP 8.1.x. If you do notadd the pack license key before upgrading, the features are not availablewhen you boot into the new Data ONTAP release, and you must add the keyafter upgrading.

For information about Data ONTAP 8.1 licensing models and whether alicense key must be added for a particular feature or pack, see the DataONTAP System Administration Guide for 7-Mode and the man pages for thelicense commands or the Technote FAQ at the following link:


Upgrade from 7.3.x to 8.1.x through intermediate upgradewith deduplication disabled can cause a system panic

If you perform an intermediate upgrade from Data ONTAP 7.3.x to DataONTAP 8.0.2 or 8.0.3 to Data ONTAP 8.1.x with deduplication disabled andenable deduplication after upgrading to Data ONTAP 8.1.x, the storage systempanics when the next scheduled or manual deduplication operation runs.

However, if you upgrade to Data ONTAP 8.1.2, then Data ONTAP generatesan error message indicating the workaround.



The storage system panics because the deduplication metadata is inconsistent.As a workaround for this issue, you must run the sis start -s command onthe volume to initialize the deduplication metadata and prevent future systempanics.

If you revert to a release earlier than Data ONTAP 8.1, youmight need to install licenses for some products

If you acquire licensed or entitled products by upgrading to Data ONTAP 8.1or later and these products required a license prior to Data ONTAP 8.1, youmight need to install a license after reverting. This is the case if a license wasnot previously installed for the release you revert to.

Starting with Data ONTAP 8.1, some products are grouped together so thatonly one license key is required to add a pack of software products to asystem. Also starting with Data ONTAP 8.1, some products are automaticallyentitled without requiring a license key. These products might have required alicense in earlier releases. If you did not install a license for these products ina release earlier than Data ONTAP 8.1 and you revert to a release earlier thanData ONTAP 8.1, you might need to install a license so that you can continueto use the products after the revert.

For example, you have a N6200 system, which requires a license forMultiStore prior to Data ONTAP 8.1, but you did not install a MultiStorelicense. After upgrading to Data ONTAP 8.1 or later, you automatically getMultiStore with the Data ONTAP Essentials license pack without requiring aseparate license. If you revert to a release earlier than Data ONTAP 8.1, youmust install a MultiStore license to continue to use MultiStore on your N6200system.

For information about Data ONTAP 8.1 licensing models, see theknowledgebase article: Using License Keys with Data ONTAP 8.1 7-Mode

N6210 series and N6040 series storage systems with FlashCache modules are supported

Data ONTAP 8.1.1 and later releases operating in 7-Mode support N6210series and N6040 storage systems with 256-GB Flash Cache modules.

If you have a N6040 storage system with the 256 GB Flash Cache modules,Data ONTAP 8.1.1 and later releases support the full 256 GB capacity of theFlash Cache module for wear-leveling and cache storage. However, to deliveron the full value of Data ONTAP, the maximum working dataset in the 256GB Flash Cache module is 128 GB.



After upgrading to Data ONTAP 8.1.1 and later releases on N6210 series andN6040 series storage systems, you must verify that the WAFL external cachefunctionality is enabled.

Verifying that WAFL external cache functionality is enabled

After upgrading to Data ONTAP 8.1.1 and later 8.1.x releases on N6210 seriesand N6040 series storage systems with 256 GB Flash Cache modules, youmust verify that the WAFL external cache functionality is enabled.1. Verify that the WAFL external cache functionality is enabled by entering

the following command:options flexscale.enable

For 7-Mode single-controller configurations, run this command from thesystem console prompt.For 7-Mode HA pairs, run this command from each node.The output shows on if WAFL external cache functionality is enabled. Theoutput shows off if WAFL external cache functionality is not enabled.

2. If necessary, enable WAFL external cache functionality by entering thefollowing command:options flexscale.enable on

3. Configure the WAFL external cache option.You can set the WAFL external cache configuration option now or later,but it is recommended that you set the option now to ensure optimalperformance for the system's workload. The option descriptions andcommands are in the Data ONTAP System Administration Guide for 7-Mode.For 7-Mode HA pairs, you must configure the option on each node.

NDU not available for SAN systems with some versions ofLinux hosts running high-speed interconnects

For some versions of Linux, you cannot upgrade to Data ONTAP 8.1 or earlierusing the nondisruptive upgrade (NDU) method with SAN hosts that haveALUA enabled and have high-speed interconnects (8 Gb or faster).

The following versions of Linux running on hosts can encounter host hangs orlong delays in I/O operations during the failover phase of the Data ONTAP(NDU), which causes disruption of services to the hosts:v Red Hat Enterprise Linux 6.x or 5.x prior to 5.8v SUSE Linux Enterprise Server 10.x and 11.xv Oracle Linux 5.x and 6.x


To perform a NDU with Red Hat Enterprise Linux, you must ensure you areusing Red Hat Enterprise Linux 5.8. Otherwise, you need to plan for adisruptive Data ONTAP upgrade.

For more information, see I/O delays sometimes seen after controller failoveron Linux hosts with ALUA.

IPv6 address entries in /etc/exports file missing bracketsafter upgrading

If you are upgrading from the Data ONTAP 7.3.x release family to DataONTAP 8.1 7-Mode and you have IPv6 enabled, you must manually updatethe /etc/exports file and add the missing square brackets around each IPv6address.

After finishing the upgrade, check each entry in the /etc/exports file thatcontains an IPv6 address. In the following example, the IPv6 addresses aremissing the required square brackets ([ ]):

/vol/vol3 -sec=sys,rw=FD20:81BE:B255:4136:10.72.58.30,root=FD20:81BE:B255:4136:10.72.58.30

If your IPv6 address entries are missing these brackets, you must manuallyupdate the file and add the square brackets around each IPv6 address so thatthe entry looks similar to the following example:

/vol/vol3 -sec=sys,rw=[FD20:81BE:B255:4136:10.72.58.30],root=[FD20:81BE:B255:4136:10.72.58.30]

You can update the /etc/exports file either by using a text editor or theexportfs command. For more information, see the Data ONTAP File Accessand Protocols Management Guide for 7-Mode.

Erroneous reboot message during Data ONTAP reversion

When reverting from Data ONTAP 8.1 to an 8.0.x release, you might see ascreen message directing you to enter the reboot command. That direction isincorrect, you should enter the revert_to command instead.

Here is an example of the incorrect message:software: installation of image.tgz completed.Please type "reboot" for the changes to take effect.


The correct message will be displayed when the problem is fixed in a futureData ONTAP release.

Reverting to an earlier release on a N6210 with more than200 volumes can cause a system panic

Data ONTAP 8.1 and later releases support 500 volumes on the N6210. Forprevious Data ONTAP release families, only 200 volumes are supported. Ifyou attempt to revert a N6210 with more than 200 volumes to an earlierrelease of Data ONTAP, not all of your volumes will come online.

To avoid this issue, ensure that you have 200 or fewer volumes beforereverting to an earlier release family on a N6210.

Validation of LUNs fails when reverting from Data ONTAP 8.1to some earlier releases

Validation of LUNs created in Data ONTAP 8.1 might fail when you revertfrom Data ONTAP 8.1 to some earlier releases. In Data ONTAP 8.1 and laterreleases, LUN serial numbers can contain characters, such as number sign (#)and ampersand (&), which are not supported in some earlier releases.

Data ONTAP 8.1 supports the following characters in LUN serial numbers:number sign (#), ampersand (&), dollar sign ($), percent (%), asterisk (*), plussign (+), less than sign (<), equal sign (=), greater than sign (>), question mark(?), at sign (@), open bracket ([), exclamation point (!), close bracket (]), caret(^), and tilde (~).

If your LUN serial numbers contain these characters in Data ONTAP 8.1 orlater, you cannot revert to Data ONTAP releases earlier than version 8.0.3 inthe 8.0.x release family or version 7.3.7 in the 7.3.x release family.

Downgrade to 8.1 not allowed for N6040 and N6210 systemswith Flash Cache modules

If you want to downgrade a N6040 or N6210 storage system that has a FlashCache module to Data ONTAP 8.1, you need to disable the Flash Cachemodules before you can downgrade the system. The downgrade will fail ifyou do not disable the modules.

Flash Cache modules are not supported on N6040 and N6210 storage systemsrunning Data ONTAP 8.1.

For information about how to disable the Flash Cache modules before youdowngrade to Data ONTAP 8.1, see the Data ONTAP Upgrade andRevert/Downgrade Guide for 7-Mode.


MultiStore license and vFiler units removed when revertingto Data ONTAP release earlier than 8.1

If you revert to a Data ONTAP release earlier than 8.1 and your system hasthe Multistore feature enabled, the MultiStore license and vFiler units areremoved in certain cases. The affected storage systems are N7x50T series,N6200 series, N3400, N3150, N3220, and N3240.

The MultiStore license and vFiler units are removed when you perform therevert operation in the following scenarios:v The storage system has a new installation of Data ONTAP 8.1.v The storage system was previously running Data ONTAP 8.0.x or Data

ONTAP 7.3.x, and the MultiStore feature was not licensed before upgradingto Data ONTAP 8.1.

You must perform the following steps to retrieve the vFiler units:1. Before reverting, obtain all the information related to the vFiler units by

using the vfiler status -r command.2. After reverting, license the MultiStore feature by using the license add

command.3. Restore the vFiler units by using the vfiler create -r command.

Note: This method works only if the data in the volumes is not modifiedor deleted.

Revert from Data ONTAP 8.1.x to Data ONTAP 8.0.x fails iffingerprint database size exceeds 256 GB

A revert from Data ONTAP 8.1.x to Data ONTAP 8.0.x fails if the fingerprintdatabase size in the storage system exceeds 256 GB. This can be due to thepresence of up to 20 percent stale fingerprint records in the changelog.

To delete the stale fingerprint records from the changelog, you can run the sischeck command on the volume. This helps to reduce the overall changelogsize to less than 256 GB.

If this workaround fails, you can use the sis revert_to -delete command.Running this command requires the regeneration of the changelog after thedowngrade.

Downgrading to Data ONTAP 8.1 or earlier with a Flash Poolroot aggregate disables the system

If you configure a Flash Pool (an aggregate that contains both HDDs andSSDs) as your root aggregate and you want to downgrade to any release of


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

Setup cautions

If you are setting up a storage system for the first time, you should review thesetup cautions.

For more information about these issues, see the Data ONTAP Software SetupGuide for 7-Mode.v “Cannot continue setup using the web interface”v “CIFS setup overwrites the storage system password”

Cannot continue setup using the web interface

Starting with Data ONTAP 8.1, the web interface has been removed and youcannot use OnCommand System Manager for initial setup of the storagesystem. This means that you must respond to system setup promptsdifferently from previous releases.

When prompted to continue setup using the web interface, you must enter nto continue setup using the command-line interface. Starting with DataONTAP 8.1, the web interface has been removed and you cannot useOnCommand System Manager for initial setup of the storage system.

If you enter y to continue setup using the web interface, a few errors appearon the screen and the links provided result in browser errors. You can ignorethese errors, as the setup script continues to the next prompt regardless ofwhat you enter.

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

CIFS setup overwrites the storage system password

The CIFS setup script resets the storage system password for the root accountto match the local administrator account password for CIFS.

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


Manageability cautions

If you are a storage system administrator, you should familiarize yourselfwith these manageability issues.v “Certificates signed with MD5 could cause loss of connectivity to secure

clients”v “If your root FlexVol volume does not meet the new size requirements”

Certificates signed with MD5 could cause loss ofconnectivity to secure clients

To enhance security, starting with Data ONTAP 8.0.2, Data ONTAP uses theSHA256 message-digest algorithm to sign the contents of digital certificates(including certificate signing requests (CSRs) and root certificates) on thestorage system. Use of the MD5 message-digest algorithm, which was used tosign CSRs and root certificates, is no longer officially supported.

Depending on the certificate depth verification, clients might need to useSHA256 to verify digital certificates presented by Data ONTAP 8.0.2 and later.

Data ONTAP 8.0 and 8.0.1 use the MD5 message-digest algorithm to signdigital certificates. Due to the CVE-2004-2761-IETF X.509 certificate MD5signature collision vulnerability, and to minimize security risks when using acertificate signed with MD5, you should have the CSRs further signed by acertificate authority (CA) using SHA256 or SHA1.

If your root FlexVol volume does not meet the new sizerequirements

The minimum required size for root FlexVol volumes has been increased forevery system running the Data ONTAP 8.0 release family or later. If your rootFlexVol volume does not meet the new requirements, you should increase itssize as soon as you complete the upgrade procedure.

The root volume must have enough space to contain system files, log files,and core files. If a system problem occurs, these files are needed to providetechnical support.

For more information about root volumes and the root FlexVol volumerequirements for your platform, see the Data ONTAP System AdministrationGuide for 7-Mode.

Storage management cautions

Review the following section for important information regarding storagemanagement cautions.


For more information about these issues, see the Data ONTAP 8.1 7-ModeStorage Management Guide.v “Disk failures might increase for some disk models after upgrading to this

version of Data ONTAP”v “Accessing data in a Snapshot copy causes a system disruption under

certain conditions” on page 118

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 newstorage expansion unit firmware versions for EXN1000 and EXN3000 storageexpansion units that provide enhanced disk error detection and predictioncapabilities. Therefore, after upgrading to this version of Data ONTAP, youmight experience an increase in the number of disk failures for certain storageexpansion units and disk models.

Increased disk failures after upgrading to this version of Data ONTAP isexpected behavior. You should follow standard best practices for spares whenyou upgrade, to ensure that sufficient spares are always available.

The following table shows the storage expansion unit and disk models thatmight show an increased failure rate after upgrading:

Storage expansionunit

Partnumber

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

It is strongly recommended to upgrade to Data ONTAP 8.1.2 as soon aspossible. Once the Data ONTAP upgrade is completed, the new firmware willbe updated to all drives nondisruptively in the background.

The combination of Data ONTAP 8.1.2 and the new drive firmware isrequired. Updating to the new drive firmware alone will not provide the fullbenefits. Therefore, this drive firmware is not available on the IBM N seriessupport site.


Accessing data in a Snapshot copy causes a systemdisruption under certain conditions

Under certain conditions, accessing data inside a Snapshot copy causes asystem disruption.

All of the following conditions must be met for the disruption to occur:v The Snapshot copy contains more than 15 qtrees (including the default

qtree).v The active file system contains 15 or fewer qtrees.v The volume was previously taken offline and then brought back online.

This disruption can happen for CIFS storage clients starting from DataONTAP 8.1 operating in 7- Mode.


Network protocol cautions

This information addresses network protocols cautions. Review the followingsection for important information regarding network management.

For more information about these issues, see the Data ONTAP NetworkManagement Guide for 7-Mode.v “System might panic if the network configuration entries in the /etc/rc file

are not in the recommended order”v “Reconfiguring the losk interface results in system outage”

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

You should ensure that the entries in the /etc/rc file are in the recommendedorder. The incorrect order can cause prolonged giveback or system reboottime, which might result in a system panic.

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

Reconfiguring the losk interface results in system outage

If you modify the default configuration of the losk interface, it can result in asystem outage. If any IP address or routing configurations related to the loskinterface exists in the /etc/rc file, you must remove these configurations toavoid any undesirable behavior on the storage system.


File access and protocols cautions

If your storage system is deployed in a NAS environment, you should reviewthe important cautions regarding file access and protocols management andtake appropriate action before upgrading or reinstalling.

For more information about these cautions, see the Data ONTAP 8.0 File Accessand Protocols Management Guide for 7-Mode.v “CIFS startup might take several minutes after cluster failover giveback”

CIFS startup might take several minutes after cluster failovergiveback

After a cluster failover giveback, the CIFS protocol might take several minutesto start up. If vFiler units are present, they might not be initialized for theduration of the CIFS startup time. The delay in CIFS startup is typically dueto network infrastructure issues related to domain controllers and LDAPservers.

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 partnernode for which giveback is to be initiated before initiating a giveback:

Note: If the storage system contains vFiler units, you must complete theprocedure on all vFiler units running CIFS.

Steps

1. Test domain controller connectivity and responsiveness by entering thefollowing command:cifs testdc

If the command fails, reconnect to a domain controller by using the cifsresetdc command. The cifs resetdc command terminates existingdomain controller connections and then discovers available domaincontrollers and establishes new connections.

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

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

3. Test Active Directory LDAP connectivity by entering the followingcommand:cifs adupdate


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

4. Look up the SID of a domain user for the domain to which the CIFSserver belongs by entering the following command:wcc -s your_domain\user_account

If the command fails, identify and fix the issue before proceeding.5. Optional: If LDAP is configured for user mapping, run LDAP queries by

entering the following commands:priv set advanced

getXXbyYY getpwbyname_r user_name

getXXbyYY getpwbyuid_r uid

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

Result

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

Note: Successful execution of these commands does not guarantee that CIFSstartup during giveback will occur quickly. The servers that are respondingnow might fail later to respond when giveback occurs.


SAN administration cautions

If your storage system is deployed in a SAN environment, you should reviewthese issues and take appropriate action before upgrading or reinstalling.

For more information about these issues, see the Data ONTAP SANAdministration Guide for 7-Mode.v “2-Gb FC ports not supported as targets”

2-Gb FC ports not supported as targets

Data ONTAP 8.1 does not support the onboard 2-Gb Fibre Channel ports inN7600 or N7800 systems as targets.

The 2-Gb FC ports cannot be initialized if they are configured as targets. Ifyou are upgrading a N7600 or N7800 system from an earlier release, be sureyou have moved any FC target traffic to other ports before installing DataONTAP 8.1.

The onboard 2-Gb Fibre Channel ports can still be used as initiators.


Data protection cautions

If your storage system is configured with licenses for data protectiontechnologies, you should review these issues and take appropriate actionbefore upgrading or reinstalling.

For more information about these issues, see the Data ONTAP 8.0 DataProtection Online Backup and Recovery Guide for 7-Mode.v “Reversion requirements with volume ComplianceClock and autocommit

period of SnapLock volumes”v “SnapLock API not supported”

Reversion requirements with volume ComplianceClock andautocommit period of SnapLock volumes

If you are reverting to a previous release of Data ONTAP that supportsSnapLock, you must consider the status of the volume ComplianceClock timeand autocommit period of the SnapLock volumes.v Before reverting to a previous release, you must ensure that the volume

ComplianceClock value of the SnapLock volumes does not exceed the date,19 January 2038.If it exceeds this date, the revert fails. You can check the volumeComplianceClock time by using the snaplock clock status command.

v When reverting to a previous release, if the SnapLock volumes havedifferent autocommit periods, you have to accept the prompt to set thesystem-wide autocommit period option to none.You can check the autocommit period of the SnapLock volumes by usingthe vol status –v command.

SnapLock API not supported

Starting with Data ONTAP 8.1, the API snaplock-get-compliance-clock andthe input parameter is-compliance-clock for the API clock-get-clock is nolonger supported for SnapLock.

For more information, see the Data ONTAP Archive and Compliance ManagementGuide for 7-Mode.


Known problems and limitations

Some unexpected and potentially undesired behaviors, and in some cases,workarounds to avoid these behaviors, have been identified after upgradingto this release.v “Manageability issues” on page 126v “Storage resource management issues” on page 130v “Network protocol issues” on page 132v “File access protocol issues” on page 134v “SAN administration issues” on page 139v “Data protection issues” on page 141v “Third-party storage issues (Gateway systems only)” on page 143v “MultiStore issues” on page 143


Manageability issues

This section describes known issues and limitations with the managementinterface that affect your ability to manage the storage system. These issuesinclude problems with command behavior, command output, or errormessages presented in the Data ONTAP CLI or web interface and problemswith UNIX or operating system commands used to interface with yourstorage system.v “Cached data in a Flash Cache module is cleared during upgrade to Data

ONTAP 8.1 release family”v “The wrfile command might fail to capture all input during a cut-and-paste

operation performed through the RLM or SP” on page 127v “vFiler DR configuration with the snapmirror.checkip.enable option on fails,

if SnapMirror fails to authenticate destination IPv6 address” on page 127v “NTP version used to communicate with a newly configured NTP server

defaults to v3” on page 127v “If your system uses rtc or rdate as the protocol for time synchronization”

on page 128v “Obsolete timed options” on page 128v “Issues regarding the timed log” on page 129v “Features with the ENABLED keyword in the license command output

might require setting the options” on page 129

Cached data in a Flash Cache module is cleared duringupgrade to Data ONTAP 8.1 release family

Your storage system clears the cached data in a Flash Cache module whenyou upgrade to the Data ONTAP 8.1 release family from a previous DataONTAP release family (for example, from Data ONTAP 8.0.3).

Because there is no cached data in the Flash Cache module, the system servesinitial read requests from disk, which results in decreased read performanceduring this period. The system repopulates the cache as it serves readrequests.

After both nodes in an HA pair are running Data ONTAP 8.1 or later, thecache rewarming feature maintains the cached data in a Flash Cache moduleduring a graceful shutdown (for example, during an upgrade or takeover andgiveback).

For more information about cache rewarming, see Cache rewarming for FlashCache modules


The wrfile command might fail to capture all input during acut-and-paste operation performed through the RLM or SP

If you access the system console from the RLM or SP and you perform acut-and-paste operation on graphic input that involves using the wrfilecommand, the command might fail to capture all input.

This behavior is a result of the unusually high sustained data rate in thecut-and-paste operation. You can avoid this issue by using an SSH consolesession instead of accessing the system console through the RLM or SP.

vFiler DR configuration with the snapmirror.checkip.enableoption on fails, if SnapMirror fails to authenticate destinationIPv6 address

When you configure vFiler units for disaster recovery, if thesnapmirror.checkip.enable option is set to on on the source storage systemand the IPv6 address of the source storage system is used for communication,SnapMirror requires the IPv6 address of the destination storage system to setup a SnapMirror relationship.

You must specify the destination storage system’s IPv6 address in the list ofallowed addresses for SnapMirror relationship on the source storage system.You can add the destination storage system’s IPv6 address either to thesnapmirror.access option, or to the /etc/snapmirror.allow file if thesnapmirror.access option is set to legacy.

For more information about the snapmirror.checkip.enable option, see theData ONTAP Data Protection Online Backup and Recovery Guide for 7- Mode.

NTP version used to communicate with a newly configuredNTP server defaults to v3

Starting with Data ONTAP 8.0.2, the Network Time Protocol (NTP) version tobe used for communicating with a newly configured NTP server defaults tov3 instead of v4. This change is to address situations where certain timeservers support only NTP v3.

Releases prior to Data ONTAP 8.0 use Simple NTP v3 (SNTPv3) by default,while Data ONTAP 8.0 and 8.0.1 use NTP v4 by default. For Data ONTAP8.0.2 and later releases, the NTP daemon continues to use the highestsupported version (v4 in this case) to communicate with the time servers thatwere configured prior to Data ONTAP 8.0.2.

To reset the time servers to use NTP v3, you can use the optionstimed.servers command to reconfigure the list of servers.

Known problems and limitations 127

If your system uses rtc or rdate as the protocol for timesynchronization

Starting with Data ONTAP 8.0, the Network Time Protocol (NTP) protocol isthe only supported protocol for time synchronization. The rtc and the rdateprotocols of the timed.proto option are obsolete and no longer take effectafter you upgrade to Data ONTAP 8.0 or later.

If your system does not use NTP as the time-synchronization protocol, it willnot keep accurate time after you upgrade it to Data ONTAP 8.0 or later.Problems can occur when the storage system clock is inaccurate.

If your system does not already use NTP as the protocol for timesynchronization, immediately after upgrading to Data ONTAP 8.0 or later youmust set timed.proto to ntp, set timed.servers to use time servers thatsupport NTP, and ensure that timed.enable is set to on.

Note: After you set timed.proto to ntp, the setting remains in effect even ifyou revert back to a release prior to Data ONTAP 8.0.

For information about how to synchronize the system time, see the DataONTAP System Administration Guide for 7-Mode.

Obsolete timed options

Starting with Data ONTAP 8.0, several timed options are obsolete althoughthey remain visible in the CLI and can be modified.

The following timed options have no effect in Data ONTAP 8.0 or later:v The timed.log optionv The timed.max_skew optionv The timed.min_skew optionv The timed.sched optionv The timed.window optionv The rtc and the rdate protocols of the timed.proto option

If you attempt to set the above options when the system is running DataONTAP 8.0 or later, they will have no effect. However, these settings will takeeffect if the system is reverted back to a release prior to the Data ONTAP 8.0release family.


Issues regarding the timed log

Starting with Data ONTAP 8.0, the NTP daemon automatically adjusts thestorage system time to keep the system clock synchronized with the specifiedNTP server. However, time adjustments made by the NTP daemon are notlogged even when the timed.log option is set to on.

Features with the ENABLED keyword in the licensecommand output might require setting the options

Output of the license command displays the ENABLED keyword instead ofthe license key for some features. Before using the features, you might need touse the options command to enable them.

For features that were not used with previous versions of Data ONTAP butare now provided free of cost or as part of a software pack for which youhave installed a license key, the output of the license command displaysENABLED in Data ONTAP 8.1 or later releases. You can enable the followingfeatures by using the options command:v Disk sanitization (licensed_feature.disk_sanitization.enable)v Fibre Channel (licensed_feature.fcp.enable)v FlexCache (licensed_feature.flexcache_nfs.enable)v iSCSi (licensed_feature.iscsi.enable)v MultiStore (licensed_feature.multistore.enable)v NearStore (licensed_feature.nearstore_option.enable)v VLD (licensed_feature.vld.enable)

For more information, see the na_options(1) man page and the Technote FAQat the following link:



https://www-304.ibm.com/support/entdocview.wss?uid=ssg1S1003943

Storage resource management issues

You should familiarize yourself with these storage resource managementissues in this release.v “Write operations might fail or LUNs might go offline if deduplication

metadata increases”v “You cannot assign ownership and checksum type for spare disks or array

LUNs in the same operation”v “Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded” on page 131v “Aggregate expansion or deduplication of a FlexCache origin volume

running Data ONTAP 8.1 can cause system panic” on page 131v “After changing the port assigned to ACP, a reboot is required to regain use

of the original port” on page 131v “Configuring ACP to use a different port on N3220 and N3240 storage

systems disables ACP for the local SAS expander” on page 132

Write operations might fail or LUNs might go offline ifdeduplication metadata increases

In volumes with deduplication enabled, the deduplication metadata increasesif the deduplication schedule is turned off. The increase in metadata mightcause write operations to fail or LUNs to go offline.

To avoid this issue, you must schedule deduplication to be run periodically byusing the sis config -s command.

If the metadata in the volume has increased, then you must disablededuplication by using the sis off command and delete the metadata byusing the sis reset command.

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

You cannot assign ownership and checksum type for sparedisks or array LUNs in the same operation

If you need to change both the checksum type and ownership of a spare diskor array LUN, you must use two separate commands.

Example

If you wanted to change the ownership to sys2 and checksum type to block for arrayLUN vgbr300s20:21.126L14, you would use the following two commands:


Example

disk assign vgbr300s20:21.126L14 -c block diskassign vgbr300s20:21.126L14 -o sys2 -f

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 andN7x50T series storage systems. If you are using mirrored aggregates that arenot in a MetroCluster configuration, the presence of this license can reduceread performance, because data is read from only one plex. You can recoverfrom this situation by using the following command to disable the license (onboth nodes for HA pairs):license delete cf_remote

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

Aggregate expansion or deduplication of a FlexCache originvolume running Data ONTAP 8.1 can cause system panic

A storage system containing a FlexCache can panic if a Data ONTAP 8.1origin volume or its containing aggregate undergo aggregate expansion ordeduplication.

This problem can occur on FlexCache volumes running a release earlier thanData ONTAP 7.3.6 in the 7.3 release family or Data ONTAP 8.0.2 in the 8.0release family, with an origin volume running Data ONTAP 8.1. The problemis fixed in Data ONTAP 7.3.6, 8.0.2, 8.1, and later. However, both theFlexCache system and the origin system must have the fix to prevent theproblem.

To avoid this problem, take the FlexCache volume offline by using the voloffline command before the deduplication of the origin volume or aggregateexpansion. When the deduplication or expansion is complete, place theFlexCache volume back online by using the vol online command.

After changing the port assigned to ACP, a reboot is requiredto regain use of the original port

If you reconfigure ACP to use a new port, the port that was configured forACP before becomes available for use by another subsystem only after youreboot the storage system.


Configuring ACP to use a different port on N3220 and N3240storage systems disables ACP for the local SAS expander

If you configure ACP to use a different port than e0P (the default) on N3220and N3240 storage systems, the internal ACPP module IOM6E becomesunresponsive, disabling ACP for the local SAS expander. Unless you areexperiencing hardware issues on port e0P, always use the default port forACP for the N3220 and N3240 storage systems.

Network protocol issues

You should familiarize yourself with these network protocol issues in thisrelease.

For more information about these issues, see the Data ONTAP 8.1 NetworkManagement Guide for 7-Mode.v Partner node might be unavailable during controller failoverv “Static routes are not retargeted to a network interface with a new

autoconfigured IPv6 address”v “SnapMirror transfer cannot be blocked by using the

interface.blocked.mgmt_data_traffic option” on page 133

Partner node might be unavailable during controller failoverwhen an interface name is used as an alternate host name inthe /etc/hosts file

When the interface name used for configuring the partner interface is presentin the /etc/hosts file, the IP address of the local node is substituted insteadof the IP address of the partner node. This results in the partner node beingunavailable during takeover.

To avoid this issue, you can use one of the following workarounds:v Do not use interface names as alternate host names in the /etc/hosts file.v Use the IP address of the partner node instead of the interface name while

configuring the partner interface.

Note: You can use the IP address of the partner node while configuring thepartner interface only when the interface belongs to the default IPspace.

Static routes are not retargeted to a network interface with anew autoconfigured IPv6 address

The static routes from a network interface in the down status are not retargetedto another network interface with an autoconfigured IPv6 address in the samesubnet.


To avoid this issue, you must perform the following steps:1. Configure the interface from the down status to the up status, by using the

following command:ifconfig interface up

2. Configure the same interface to the down status by entering the followingcommand:ifconfig interface down

The routes are retargeted to the network interface with the autoconfiguredIPv6 address that is configured to the up status.

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 trafficfrom e0M 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 systemsdo not use e0M, and that neither SnapMirror nor NDMP is configured to usean IP address that is assigned to e0M on a destination storage system.


File access protocol issues

If your storage systems provide CIFS, NFS, or FTP client services, you mightneed to familiarize yourself with file access protocol issues.

For more information about these issues, see the Data ONTAP File Access andProtocols Management Guide for 7-Mode.v “Value of the option nfs.ifc.rcv.high is unexpectedly reset”v “CIFS client authentication fails if host name exceeds 16 characters” on

page 135v “Excessive pending CIFS authentication requests can cause service

disruption” on page 135v “Microsoft Windows 7 clients fail to rename files and directories” on page

136v “File copy operation on a widelink path inside a CIFS share might fail

when using SMB 2.x” on page 136v “Domain controller responds with an access denied error to an SMB 2.x tree

connect request” on page 137v “Domain user unable to execute CLI commands” on page 137v “Client notification messages in Windows domains require NetBIOS” on

page 137v “Configuration issue for clients that mount NFS shares using a

non-reserved port” on page 137v “Certain special characters are case sensitive” on page 138v “Widelinks are not accessible from Mac clients” on page 138

Value of the option nfs.ifc.rcv.high is unexpectedly reset

The option nfs.ifc.rcv.high value might unexpectedly get reset to aprevious value if it is changed by the option nfs.tcp.recvwindowsize.

The option nfs.ifc.rcv.high controls the high-water mark after which NFSlevel flow control takes effect. This option is also controlled by the optionnfs.tcp.recvwindowsize. Changing the option nfs.tcp.recvwindowsizeautomatically changes the value of the option nfs.ifc.rcv.high.

However, there are some scenarios in which the option nfs.ifc.rcv.highvalue gets reset to a previous value if it is changed by the optionnfs.tcp.recvwindowsize.

To avoid the issue, first configure the option nfs.tcp.recvwindowsize, thenmanually configure the option nfs.ifc.rcv.high.


Note: The value for the option nfs.ifc.rcv.high should be 1.5 times thevalue of the option nfs.tcp.recvwindowsize.

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-Could not unpack NTLMSSP Authenticate token.

The connecting client displays the following error message:NT_STATUS_MORE_PROCESSING_REQUIRED.

To avoid this issue, you must ensure that the CIFS client name does notexceed 16 characters 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 areon the storage system, pending CIFS authentication requests for a vFiler unitcould affect resources available to other vFiler units.

Data ONTAP enables you to monitor pending CIFS authentication requestsand take 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 Guidefor 7-Mode.


Microsoft Windows 7 clients fail to rename files anddirectories

When a Microsoft Windows 7 client accesses an SMB share with widelinksenabled, it can fail intermittently to rename files and directories on themapped 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 client for which a hot fix isavailable from Microsoft. The bug is described and information about how toobtain the hot fix is provided in the Microsoft KB article Microsoft KB2703610: support.microsoft.com/kb/2703610. This KB article also providesinformation about a workaround for this issue if you do not want to applythe hot fix.

File copy operation on a widelink path inside a CIFS sharemight fail when using SMB 2.x

If you try to copy a large file to a folder that is within a widelink path insidethe root of the CIFS share and the size of the file being copied is greater thanthe available space at the root of share, the copy operation fails.

This issue occurs if you are using Windows Explorer for the copy operationon an SMB 2.x capable client with the SMB 2.x protocol enabled.

This happens because, when calculating whether there is available space forthe copy operation to succeed, the Windows client refers to the root of theshare when calculating available space. This leads to a condition where theoperation fails if there is insufficient space at the root of the share, even if thefolder inside the root of the share resides within a widelink to a differentvolume that has enough available space for the copy operation to succeed.

The following are possible workarounds for this issue:v Copy the file using the DOS command prompt.v Copy the file using the Windows PowerShell interface.v Create a CIFS share mounted on the widelink point, map the share on the

Windows client, and perform the copy operation.

Note: This issue does not occur if SMB 1.0 is used for the file copyoperation.


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

Domain controller responds with an access denied error toan SMB 2.x tree connect request

A domain controller can respond with a 0xc0000022 error (Access Denied) toan SMB 2.x tree connect request from the storage server on IPC$.

To avoid this issue, disable SMB 2.x on the system by entering the followingcommand:

options cifs.smb2.client.enable off

Domain user unable to execute CLI commands

If you log in to the storage system CLI as a domain user and enter thecommand cifs gpupdate, all subsequently entered CLI commands fail withthe following error message:

[useradmin.unauthorized.user:warning] User domain_name\user_name deniedaccess - missing required capability: ’cli-options’.

If you encounter this issue, log out, 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 DataONTAP.

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.

Configuration issue for clients that mount NFS shares usinga non-reserved port

The nfs.mount_rootonly and nfs.nfs_rootonly options must be set to off ona storage system that must support clients that mount NFS shares using anon-reserved port even when the user is logged in as root. Such clientsinclude Hummingbird clients and Solaris NFS/IPv6 clients.

If the nfs.mount_rootonly option is set to on, Data ONTAP does not allowNFS clients that use nonreserved ports (that is, ports with numbers higherthan 1023) to mount the NFS shares.


If the nfs.nfs_rootonly option is set to on, Data ONTAP does not allow anyNFS requests over nonreserved ports.

Certain special characters are case sensitive

Some special characters do not have a one-to-one mapping between uppercaseand lowercase. Such characters are case sensitive.

For example, if the Unicode character U+03C2 (Greek Small Letter FinalSigma) is present in a file name in the file system, a search for the file failswhen using the uppercase Sigma (U+03A3).

This happens because the file system forces characters to lowercase beforeperforming a case-insensitive comparison. The uppercase Sigma istransformed to a lowercase non-final Sigma, which does not match.

To avoid this issue, use the same characters without changing the case whenaccessing the file. Alternatively, avoid using such characters in file namesaltogether.

Widelinks are not accessible from Mac clients

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


SAN administration issues

If your storage systems are part of a SAN environment, you might need tofamiliarize yourself with SAN administration issues in this release.

For more information about these issues, see the Data ONTAP SANAdministration Guide for 7-Mode.v “Disks offline in Windows Server 2008 and 2012 after Data ONTAP

upgrade”v “I/O delays sometimes seen after controller failover on Linux hosts with

ALUA”v “If you use the automatic sizing feature on thinly provisioned LUNs when

snap reserve is set to a non-zero value” on page 140

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; thisstatus is shown in Windows management interfaces after the upgrade.Windows Server 2003 ignores LUN revision numbers.

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

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

I/O delays sometimes seen after controller failover on Linuxhosts with ALUA

During a controller failover (CFO), hosts running versions of Red HatEnterprise Linux 6.x or 5.x prior to 5.8; SUSE Linux Enterprise Server 10.x and11.x; or Oracle Linux 5.x and 6.x with ALUA enabled sometimes encountereither host hangs or long delays in I/O operations. This issue can also causeproblems with nondisruptive upgrades (NDU).

The problem occurs when the recovery from the CFO is delayed. The delaycauses the ALUA transition period on the controller, which is running DataONTAP, to take longer. The controller responds to the requests with themessage:NOT READY: Asymmetric Access State Transition


At that point, the Linux host starts continually retrying its requests. Theincreased number of retries overwhelms the target and eventually leads todegraded performance, such as long and sometimes stalled I/O operations orsituations where the host hangs.

This issue is usually seen in environments that use high-speed interconnects(8 Gb or faster).

This issue is resolved in Red Hat Enterprise Linux 5.8.

For more information, see NDU not available for SAN systems with someversions of Linux hosts running high-speed interconnects.

If you use the automatic sizing feature on thinly provisionedLUNs when snap reserve is set to a non-zero value

Generally, before you thinly provision LUNs, you should set snap reserve tozero. However, there are rare exceptions that require you to set snap reserveto a value other than zero. In these instances, you must use the automaticsizing feature for thinly provisioned LUNs in FlexVol volumes to workproperly.

About this task

Using the automatic sizing feature is required because the space from deletedSnapshot copies can only be used to fulfill Snapshot space requests.Furthermore, the automatic deletion process will not begin until the snapreserve value is exceeded.

Step

1. Enter the following command:vol autosize vol_name [-m size] [-I size] on

-m size is the maximum size to which the volume will grow. Specify asize in k (KB), m (MB), g (GB), or t (TB).-I size is the increment by which the volume's size increases. Specify asize in k (KB), m (MB), g (GB) or t (TB).

Result

If the specified FlexVol volume is about to run out of free space and is smallerthan its maximum size, and if there is space available in its containingaggregate, the FlexVol volume's size will increase by the specified increment.


Data protection issues

If 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 DataProtection Tape Backup and Recovery Guide for 7-Mode.v “Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded”v “SMTape restore to an offline volume overwrites the data on that volume”v “Restore engine does not honor any mandatory or advisory locks on files”v “SnapMirror status entries and softlocks are locked and not deleted from

the source system” on page 142

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 andN7x50T series storage systems. If you are using mirrored aggregates that arenot in a MetroCluster configuration, the presence of this license can reduceread performance, because data is read from only one plex. You can recoverfrom this situation by using the following command to disable the license (onboth nodes for HA pairs):

license delete cf_remote

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

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.

Restore engine does not honor any mandatory or advisorylocks on files

The destination volume for a restore operation might have files withmandatory or advisory locks. When you initiate a restore operation to such avolume, the restore engine does not honor these locks. It ignores these locksand overwrites the files.


SnapMirror status entries and softlocks are locked and notdeleted from the source system

In a volume SnapMirror relationship, if you rename or move the destinationvolume or its vFiler unit and perform a snapmirror update operation, then theSnapMirror status entries and softlocks are locked and not deleted from thesource system. To delete these old SnapMirror status entries and softlocks,you must run the snapmirror release command on the source system.


Third-party storage issues (Gateway systems only)

There are certain issues and restrictions you should be aware of when DataONTAP uses third-party storage.v “Restrictions for gateway system upgrade to Data ONTAP 8.1 or later”

Restrictions for gateway system upgrade to Data ONTAP 8.1or later

Do not upgrade your gateway system to run Data ONTAP 8.1 unless theGateway Support Matrix lists your storage array as supported in DataONTAP 8.1.

Before starting an upgrade of your gateway system to run Data ONTAP 8.1,check the Gateway Support Matrix to ensure that your storage array issupported in Data ONTAP 8.1.

See the Gateway Support Matrix, located on the IBM N series supportwebsite, which is accessed and navigated as described in “Websites” on page2

If your storage array is not supported in Data ONTAP 8.1, and you attempt toupgrade to 8.1, Data ONTAP generates an error message such as thefollowing:[sundance1:mlm.array.unsupported:warning]: Array LUN [S/N’60050768019181C8B00000000000004E’ vendor ’xxx ’ product ’yyy ’] is notsupported in this version of Data ONTAP.

If you upgrade your gateway system to run Data ONTAP 8.1 and the storagearray is not supported in 8.1, you must revert Data ONTAP to an earlierrelease. See the Upgrade Downgrade/Revert Guide for information about how torevert your system to an earlier release.

MultiStore issues

If MultiStore is licensed on your storage systems, you might need tofamiliarize yourself with current MultiStore issues. For more informationabout these issues, see the Data ONTAP MultiStore Management Guide for 7-Mode.v “Online migration of vFiler units is not supported on Flash Pools” on page

144


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 ofguides provided with this release were published. The information should beused in conjunction with the guides provided with this release of DataONTAP.v “Changes to the System Administration Guide”v “Changes to the High Availability Configuration Guide” on page 149v “Changes to the Commands Manual Page Reference” on page 149v “Changes to the File Access and Protocols Management Guide” on page 150v “Changes to the SAN Administration Guide ” on page 150v “Changes to the Software Setup Guide ” on page 151v “Changes to the SAN Configuration Guide for 7-Mode” on page 152

Changes to the System Administration Guide

Additional information has become available since the last revision of theData ONTAP System Administration Guide for 7-Mode.

Changes to information about the root aggregate and root volume

The Data ONTAP System Administration Guide for 7-Mode has updatedinformation about the root aggregate and root volume.

The Managing the root volume section has been amended with the followinginformation:v For systems running virtual storage, the Data ONTAP-v installation process

creates a single aggregate by using all currently defined virtual disks andcreates the root FlexVol volume in that aggregate.For more information about system setup, see the Installation andAdministration Guide that came with your Data ONTAP-v system.

v A Flash Pool (an aggregate that contains both HDDs and SSDs) can be usedas the root aggregate.Attention: If you downgrade to Data ONTAP 8.1 or earlier with a FlashPool configured as your root aggregate, your system will not boot.

The Size requirements for root FlexVol volumes section has been amendedwith the following information: For information about the minimum size forthe root FlexVol volume of your storage system model, see the N seriesIntroduction and Planning Guide.


Changes to password rule management

The Data ONTAP System Administration Guide for 7-Mode has updatedinformation about password rule management. New options enable you tospecify the minimum number of uppercase or lowercase alphabetic charactersthat a password must contain. The How to manage passwords for security sectionis amended with the following information:

You can use the following options to specify the minimum number ofuppercase or lowercase alphabetic characters that a password must contain:v The security.passwd.rules.minimum.uppercase option specifies the

minimum number of uppercase alphabetic characters that a password mustcontain.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.

The table in the Options that manage password rules section is amended with thefollowing information:


This option (used with the options command)... Enables you to...

security.passwd.rules.minimum.alphabetic Specify the minimum number of alphabeticcharacters that a password must contain.

This number includes the required numbers ofuppercase and lowercase characters, which youcan set by usingsecurity.passwd.rules.minimum.uppercase andsecurity.passwd.rules.minimum.lowercase,respectively.

The default value is 2.

If the security.passwd.rules.enable option is setto off, this option is ignored.

If this option has a value smaller than thecombined value ofsecurity.passwd.rules.minimum.uppercase andsecurity.passwd.rules.minimum.lowercase, theuppercase and lowercase rules determine therequired number of alphabetic characters in apassword. In the following examples, the systemensures that a password contains at least twouppercase and four lowercase alphabeticcharacters:

options security.passwd.rules.minimum.alphabetic 0options security.passwd.rules.minimum.uppercase 2options security.passwd.rules.minimum.lowercase 4

options security.passwd.rules.minimum.alphabetic 3options security.passwd.rules.minimum.uppercase 2options security.passwd.rules.minimum.lowercase 4

security.passwd.rules.minimum.lowercase Specify the minimum number of lowercasealphabetic characters (“a” to “z”) that a passwordmust contain.



Changes to published documentation 147

This option (used with the options command)... Enables you to...

security.passwd.rules. minimum.uppercase Specify the minimum number of uppercasealphabetic characters (“A” to “Z”) that a passwordmust contain.



Changes to BMC command information

The Data ONTAP System Administration Guide for 7-Mode is amended withinformation about the bmc battery-info command.

In the Data ONTAP commands for managing the BMC section, the commandtable has been amended with the following information:

If you want to... Use this Data ONTAP command...

Display battery information, for example,battery name, charging status, serialnumber, part number, firmware andhardware versions, chemistry type,manufacturer, and date of manufacture

bmc battery-info

Changes to information about SSH server version on Data ONTAP

The Understanding the SSH protocol section of the Data ONTAP SystemAdministration Guide for 7-Mode has been updated.

The information about the SSH server version running on Data ONTAPshould read as follows: The SSH server version running on Data ONTAP isData ONTAP SSH version 1.0. For information about the CommonVulnerabilities and Exposures (CVE) fixes implemented in Data ONTAP, seethe IBM Systems Storage N series Suspected Security Vulnerabilities tech noteat the following link:

www.ibm.com/support/entdocview.wss?uid=ssg1S1003795

Changes to information about the /etc/rc file

The About the /etc/rc file section of the Data ONTAP System Administration Guidefor 7-Mode has updated information about the commands that the /etc/rc filemust not contain.


http://www.ibm.com/support/entdocview.wss?uid=ssg1S1003795

The /etc/rc file must not contain the following types of commands:v Commands that are executed by subsystems that are not yet available when

the file is executedv Commands that are interactive and would wait for input during the boot

process

For example, you must not include the iscsi commands or the wrfilecommand in the /etc/rc file. Doing so prevents your storage system frombooting successfully.

Corrections to the timed options

The timed.log option has been removed from The timed options section of theData ONTAP System Administration Guide for 7-Mode. The option has becomeobsolete as of Data ONTAP 8.0.

Changes to the High Availability Configuration Guide

New information has become available since the previous revision of the DataONTAP High Availability and MetroCluster Configuration Guide for 7-Mode.

Virtual channel rules are not required

The topic titled "Virtual channel rules" in the Data ONTAP High Availabilityand MetroCluster Configuration Guide for 7-Mode is no longer applicable.Because the long distance mode “L0” is no longer supported, and “LE” is therequired minimum setting for E_Ports, the virtual channel cabling rules are nolonger applicable.

For more information about applying LE, see the Fabric-attached MetroClusterBrocade Switch Configuration Guide at the IBM N series support site.

Changes to the Commands Manual Page Reference

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

The nvfail_rename command does not exist in Data ONTAP 8.1.x

The nvfail_rename command, which is included in the latest version of theData ONTAP Commands: Manual Page Reference for 7-Mode, Volume 2 does notexist in Data ONTAP 8.1.x.

Commands not supported in Data ONTAP 8.1.1


The ups and filestats commands are included in the latest version of theData ONTAP Commands: Manual Page Reference for 7-Mode, Volume 1, but thesecommands are not supported in this release.

Changes to the File Access and Protocols ManagementGuide

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

NFSv4 not required for VMware vStorage over NFS

The topic Support for VMware vStorage over NFS in the Data ONTAP File Accessand Protocols Management Guide for 7-Mode incorrectly states that both NFSv3and NFSv4 must be enabled before you can enable the VMware vStorage APIsfor Array Integration (VAAI) feature in an NFS environment.

NFSv3 is the only requirement. You do not need to enable NFSv4.

Incorrect reference to nonexistent SFTP log files

The Data ONTAP File Access and Protocols Management Guide for 7-Modecontains incorrect references to SFTP log files that do not exist on the storagesystem.

The following two topics mention /etc/log/sftp.xfer log files:v Enabling or disabling SFTP log files

v Specifying the maximum size of the current SFTP log files

However, these log files do not exist on the storage system. These referenceswill be removed in future documentation updates.

Changes to the SAN Administration Guide

New information has become available since the previous revision of the BlockAccess Management Guide for iSCSI and FC for 7-Mode.

Block Access Management Guide has a new title

The new title for the Block Access Management Guide for iSCSI and FC for7-Mode is Data ONTAP SAN Administration Guide for 7-Mode.

Volume moves between 32-bit aggregates and 64-bit aggregates


You can move a volume from a 32-bit aggregate to a 64-bit aggregate.However, beginning in Data ONTAP 8.1.1, you cannot move a volume from a64-bit aggregate to a 32-bit aggregate. This is an update to requirements for avolume move in the Data ONTAP SAN Administration Guide for 7- Mode.

Changes to the Software Setup Guide

Additional information has become available since the last revision of the DataONTAP Software Setup Guide for 7-Mode.

Changes to the setup script

Starting in Data ONTAP 8.1.2, when you run the setup script, you are nolonger prompted to continue setup using the Web interface.

Starting with Data ONTAP 8.1, the web interface has been removed and youcannot use OnCommand System Manager for initial setup of the storagesystem. This update affects the information in the Responding to setup commandprompts and the Providing array LUN ownership and system ID for gatewaysystems sections.

Changing root password during CIFS setup

CIFS setup requires a new root password. You can either specify a newpassword or reuse the same password by changing the password historysettings.

About this task

During CIFS setup, you are prompted for the root password. If you enter theold password, it is not accepted, thereby forcing you to change the password.

Step

1. Perform one of the following actions:

If you want to use... Description

A different root password for CIFS setup Change the root password at the prompt,and then continue with CIFS setup.


If you want to use... Description

The same root password for CIFS setup 1. Before running CIFS setup, set thepassword history to 0:

optionssecurity.passwd.rules.history 0

2. When you are prompted for the rootpassword, enter the same password asbefore.

3. After completing CIFS setup, changethe password history option back tothe default value:

optionssecurity.passwd.rules.history 6

Changes to the SAN Configuration Guide for 7-Mode

New information has become available since the previous revision of the DataONTAP SAN Configuration Guide for 7-Mode.

The previous title of this guide was Fibre Channel and iSCSI Configuration Guidefor the Data ONTAP 8.1 7-Mode Release Family.

The Fibre Channel and iSCSI Configuration Guide has a new name

The new title for the Fibre Channel and iSCSI Configuration Guide for 7-Mode isData ONTAP SAN Configuration Guide for 7-Mode.


Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2013 Net App, Inc. All rights reserved. Printed in theU.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

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

No part of this document covered by copyright may be reproduced in anyform or by any means—graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

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

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty 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) ofthe Rights in Technical Data and Computer Software clause at DFARS252.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, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web 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 andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, 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, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, 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.

Copyright and trademark information 155

Notices

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

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any 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 PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication 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 thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product 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 environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

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


Notices 159

��

NA 210-05957_A0, Printed in USA

GA32-1032-07

data ontap 8.1.2 release notes for 7-mode - ibm · 2016-03-14 · appliances and gateway systems,...

Documents