8.1.1 7M 215-07092_A0 ur003.pdf

Data ONTAP® 8.1.1 Release Notes For 7-Mode

NetApp, Inc.495 East Java DriveSunnyvale, CA 94089 USATelephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 463-8277Web: www.netapp.comFeedback: [email protected]

Part number: 215-07092_A0 ur003October 2012

Contents

Data ONTAP 8.1.1 Release Notes for 7-Mode ......................................... 13Changes introduced since Data ONTAP 8.1 ............................................ 15

Changes in Data ONTAP 8.1.1 for 7-Mode .............................................................. 15

Unsupported features ................................................................................. 22New and changed features in the Data ONTAP 8.1 release family ....... 23

New and changed platform and hardware support .................................................... 23

Support for the FAS2220 platform ................................................................ 23

Support for the FAS2240 platform ................................................................ 23

Support for the Data ONTAP-v platform ...................................................... 23

Support for systems with only SSDs ............................................................. 24

Support for 900-GB SAS disks ..................................................................... 24

Support for the DS4246 disk shelf ................................................................ 24

Support for the DS4486 disk shelf ................................................................ 24

Support for SAS tape drives .......................................................................... 25

Support for ATTO FibreBridge 6500N ......................................................... 25

Systems including DS14mk2 shelves with ESH2 modules .......................... 25

Manageability enhancements .................................................................................... 25

Free space reallocation of aggregates ............................................................ 25

Role-based access control for LDAP users' system access ........................... 26

Support of core segments .............................................................................. 26

SP SSH access control and automatic timeout .............................................. 26

RLM SSH access control and automatic timeout .......................................... 26

SSH port forwarding for the SP is disabled by default ................................. 27

SSH port forwarding for the RLM is disabled by default ............................. 27

Changes in aggregate Snapshot copy management ....................................... 27

SSH server version for Data ONTAP ........................................................... 27

Cache rewarming for Flash Cache modules .................................................. 28

Enhancements to reallocation scans, read reallocation, and extents ............. 28

System health monitoring .............................................................................. 29

AutoSupport enhancements ........................................................................... 29

Default 64-bit root aggregate for new systems ............................................. 30

FilerView is no longer available ................................................................... 30

Table of Contents | 3

UPS management is no longer supported ..................................................... 31

Changes to default aggregate Snapshot reserve for newly created

nonmirrored aggregates ........................................................................... 31

IPv6 support for SP and RLM ....................................................................... 31

Support for Transport Layer Security protocol ............................................. 31

Licensing changes ......................................................................................... 31

Storage resource management enhancements ........................................................... 32

Support for Flash Pools ................................................................................. 32

Support for the Advanced Zone Checksum type (AZCS) ............................. 32

Support for sanitizing SSDs .......................................................................... 32

Enhancements to aggregates ......................................................................... 32

3210 systems now support 500 FlexVol volumes ......................................... 33

Limit on number of subdirectories has been removed .................................. 33

Enhancements to FlexClone files and FlexClone LUNs ............................... 33

High-availability pair enhancements ......................................................................... 33

MetroCluster configuration supports 8-Gb host bus adapter ........................ 33

MetroCluster system support for shared-switches configuration .................. 34

MetroCluster support for Cisco switches ...................................................... 34

Networking and security protocol enhancements ..................................................... 34

Support for IPv6 ............................................................................................ 34

Improving TCP network congestion with Appropriate Byte Counting ........ 36

File access protocol enhancements ........................................................................... 36

Support for SMB 2.1 ..................................................................................... 36

Support for BranchCache .............................................................................. 37

Support for lease oplocks .............................................................................. 37

Enhancements to procedure for computer account password change ........... 38

Support for VMware vStorage over NFS ...................................................... 38

Support for SMB 2.0 ..................................................................................... 39

Support for FTPS .......................................................................................... 39

Support for SFTP .......................................................................................... 39

SAN enhancements ................................................................................................... 39

Windows Server 2012 support ...................................................................... 39

Data protection enhancements .................................................................................. 40

SnapVault support for nondefault vFiler units .............................................. 40

Support for volume SnapMirror replication between 32-bit and 64-bit

volumes .................................................................................................... 40

4 | Data ONTAP 8.1.1 Release Notes For 7-Mode

Changes to default FlexVol volume Snapshot reserve value ........................ 40

Support for concurrent volume SnapMirror and SMTape backup

operations ................................................................................................ 40

Protection of data at rest through Storage Encryption .................................. 40

Support for SnapLock ................................................................................... 41

Support for incremental and differential backups using SMTape engine ..... 41

Support for restore to volumes in 64-bit aggregates using SMTape

engine ...................................................................................................... 41

Storage efficiency enhancements .............................................................................. 42

Changes to deduplication .............................................................................. 42

Changes to data compression ........................................................................ 42

MultiStore enhancements .......................................................................................... 42

Online migration support for vFiler units ..................................................... 42

Interactive SSH support for vFiler units ....................................................... 44

Data compression support on vFiler units ..................................................... 45

V-Series enhancements ............................................................................................. 45

Removed V-Series environment variable requirement for Data ONTAP

8.1 ............................................................................................................ 45

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

Support for 1-TB Flash Cache modules ........................................................ 46

Support for the 32xx platform ....................................................................... 47

Support for the 62xx platform ....................................................................... 47

Support for 512-GB and 256-GB Performance Acceleration Module

(PAM II) .................................................................................................. 47

Support for SSDs ........................................................................................... 47

Supported tape drives .................................................................................... 47

Support for 3-TB SATA disks ...................................................................... 47

Support for 2-TB SATA disks ...................................................................... 48

Support for SA320 platform .......................................................................... 48

Changes to disk shelf support .................................................................................... 48

Support for DS2246 disk shelves .................................................................. 48

Support for DS4243 disk shelves .................................................................. 49

Manageability enhancements .................................................................................... 49

Reversion and downgrade support ................................................................ 49

Default security settings for manageability protocols ................................... 49


Requirement to set root account password .................................................... 50

Uses of the systemshell and the diagnostic account ...................................... 50

Boot menu enhancements and changes ......................................................... 51

Supported OpenSSH client versions ............................................................. 51

Root aggregate Snapshot reserve values reduced ......................................... 51

Storage resource management enhancements ........................................................... 51

Support for 64-bit aggregates ........................................................................ 52

Data compression support ............................................................................. 52


File space utilization report ........................................................................... 53

Upgrading to Data ONTAP 8.0.1 increases volume capacity after

deduplication ........................................................................................... 53

Maximum simultaneous FlexClone file or FlexClone LUN operations

per storage system ................................................................................... 53

Support for FlexClone files and FlexClone LUNs on vFiler units ............... 53

Increased maximum RAID group size for SATA disks ................................ 54

Ability to decrease maxfiles .......................................................................... 54

High-availability pair enhancements ......................................................................... 54

HA pair terminology changes ....................................................................... 54

Networking and security protocol enhancements ..................................................... 54

Ability to block data traffic on the e0M interface ......................................... 54

Support for CDP ............................................................................................ 55

Port-based load-balancing option for multimode interface groups ............... 55

TSO in NICs .................................................................................................. 55

64-bit SNMP object identifiers (OIDs) are supported .................................. 56

Configuration for receiving untagged traffic on VLAN tagged interfaces ... 56

Vifs are now known as interface groups ....................................................... 56

File access protocol enhancements ........................................................................... 56

Support for multiple open instances of the SMB named pipe on an

FPolicy server .......................................................................................... 57

Block protocol enhancements ................................................................................... 57

iSCSI RADIUS support ................................................................................ 57

Support for NetApp DataMotion for Volumes ............................................. 57

VMware VAAI features for ESX hosts support ............................................ 58

igroup scalability limits ................................................................................. 58

Data protection enhancements .................................................................................. 58


SnapVault update schedules for volume SnapMirror destination backups ... 58

Support for 840 disk drives on fabric-attached MetroCluster

configuration ............................................................................................ 59

Support for out-of-order frame delivery for SnapMirror over Fibre

Channel .................................................................................................... 59

Support for SnapMirror relationship between two FlexClone volumes ....... 59

Support for SnapMirror network compression .............................................. 59

Support for designated range of ports for NDMP data connections ............. 60


If volumes with deduplication exceed the maximum supported size ............ 61

NearStore license is not required for deduplication ...................................... 61

Maximum concurrent deduplication operations supported ........................... 61

Prerequisite for backing up data to tape using NDMP services .................... 61

Snapshot copy schedules ............................................................................... 61

SnapMirror support for 64-bit volumes ........................................................ 61

SnapVault support for 64-bit volumes .......................................................... 62

Changes to the Data ONTAP and V-Series libraries ................................................ 62

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

New commands in the Data ONTAP 8.1 release family ........................................... 63

Changed commands in the Data ONTAP 8.1 release family .................................... 69

Replaced or removed commands in the Data ONTAP 8.1 release family ................ 74

New options in the Data ONTAP 8.1 release family ................................................ 75

Changed options in the Data ONTAP 8.1 release family ......................................... 82

Summary of new and changed commands and options in the DataONTAP 8.0 release family ..................................................................... 85

New commands in Data ONTAP 8.0 7-Mode release family ................................... 85

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

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

family ................................................................................................................... 92

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

New option for the vfiler dr configure command ......................................... 95

Changed options in the Data ONTAP 8.0 7-Mode release family ............................ 95

Requirements for running Data ONTAP 8.1 ........................................... 98Supported systems ..................................................................................................... 98

Unsupported systems ................................................................................................. 99


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

V-Series requirements and support information ..................................................... 100

V-Series limits information ..................................................................................... 100

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

Important cautions ................................................................................... 102Upgrade and revert cautions .................................................................................... 102

iSCSI target adapters not supported in Data ONTAP 8.1 and later ............ 102

Change in nondisruptive upgrade procedure ............................................... 102

Upgrade process changes with Data ONTAP 7-Mode software images .. . . 103

DS14mk2 shelves with ESH2 modules no longer supported ...................... 103

License updates required before upgrading ................................................ 104

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

to install licenses for some products ...................................................... 104

3210 and 3140 storage systems with Flash Cache modules are supported . 105

NDU not available for SAN systems with some versions of Linux hosts

running high-speed interconnects .......................................................... 106

IPv6 address entries in /etc/exports file missing brackets after upgrading . 106

Automatic background disk firmware updates not enabled for non-

mirrored RAID4 aggregates .................................................................. 107

Erroneous reboot message during Data ONTAP reversion ........................ 107

Reverting to an earlier release on a 3210 with more than 200 volumes

can cause a system panic ....................................................................... 108

Validation of LUNs fails when reverting from Data ONTAP 8.1 to some

earlier releases ....................................................................................... 108

Downgrade to 8.1 not allowed for 3140 and 3210 systems with Flash

Cache modules ....................................................................................... 108

MultiStore license and vFiler units removed when reverting to Data

ONTAP release earlier than 8.1 ............................................................. 108

Setup cautions ......................................................................................................... 109

Cannot continue setup using the web interface ........................................... 109

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

Manageability cautions ........................................................................................... 110

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

traditional volume .................................................................................. 110

Certificates signed with MD5 could cause loss of connectivity to secure

clients ..................................................................................................... 110


If your root FlexVol volume does not meet the new size requirements ..... 111

Storage management cautions ................................................................................. 111

Growing a volume while its associated aggregate is expanding to 64 bit

can cause system disruption .................................................................. 111

Initiating aggregate expansion to 64-bit using a larger disk can cause

system disruption ................................................................................... 111

Accessing data in a Snapshot copy causes a system disruption under

certain conditions ................................................................................... 112

Preventing service disruption when expanding an aggregate with

volumes using quotas ............................................................................ 112

Changing the language of a FlexVol volume when expansion scanner is

running could result in system disruption ............................................. 113

Some 32-bit operations cannot be performed on a Flash Pool .................... 113

Requirements for converting an aggregate to a Flash Pool ......................... 113

Network protocol cautions ...................................................................................... 114

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

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

Reconfiguring the losk interface results in system outage .......................... 115

File access and protocols cautions .......................................................................... 115

CIFS startup might take several minutes after cluster failover giveback .... 115

CIFS setup using ONTAPI library might lead to the removal of already

existing user-created CIFS shares ......................................................... 116

CIFS SID and credential leak impacts cache memory availability ............. 116

Storage system might panic when not specifying an export path ............... 117

SAN administration cautions .................................................................................. 117

2-Gb FC ports not supported as targets ....................................................... 117

Data protection cautions .......................................................................................... 117

Reversion requirements with volume ComplianceClock and autocommit

period of SnapLock volumes ................................................................. 117

SnapLock API not supported ...................................................................... 118

Known problems and limitations ............................................................ 119Manageability issues ............................................................................................... 119

Cached data in a Flash Cache module is cleared during upgrade to Data

ONTAP 8.1 release family .................................................................... 119

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

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


Features with the ENABLED keyword in the license command output

might require setting the options ........................................................... 120

vFiler DR configuration with the snapmirror.checkip.enable option on

fails, if SnapMirror fails to authenticate destination IPv6 address ........ 120

NTP version used to communicate with a newly configured NTP server

defaults to v3 ......................................................................................... 120

If your system uses rtc or rdate as the protocol for time synchronization . . 121

Obsolete timed options ................................................................................ 121

Issues regarding the timed log ..................................................................... 122

Storage resource management issues ...................................................................... 122

Files might not be able to be deleted using NFS in a full FlexVol

volume ................................................................................................... 122

Disks might be silently left unassigned for multi-disk carrier shelves ....... 122

Write operations might fail or LUNs might go offline if deduplication

metadata increases ................................................................................. 123

You cannot assign ownership and checksum type for spare disks or

array LUNs in the same operation ......................................................... 123

Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded ........................................................... 123

Aggregate expansion or deduplication of a FlexCache origin volume

running Data ONTAP 8.1 can cause system panic ................................ 124

After changing the port assigned to ACP, a reboot is required to regain

use of the original port ........................................................................... 124

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

ACP for the local SAS expander ........................................................... 124

Network protocol issues .......................................................................................... 124

Partner node might be unavailable during controller failover when an

interface name is used as an alternate host name in the /etc/hosts file .. 124

Static routes are not retargeted to a network interface with a new

autoconfigured IPv6 address ................................................................. 125

SnapMirror transfer cannot be blocked by using the

interface.blocked.mgmt_data_traffic option ......................................... 125

File access protocol issues ....................................................................................... 126

Value of the option nfs.ifc.rcv.high is unexpectedly reset .......................... 126

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

Microsoft Windows 7 clients fail to rename files and directories ............... 127


File copy operation on a widelink path inside a CIFS share might fail

when using SMB 2.x ............................................................................. 127

Domain controller responds with an access denied error to an SMB 2.x

tree connect request ............................................................................... 127

CIFS users cannot rename or delete home directories ................................ 128

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

Storage system requests to Windows Server 2008 might fail ..................... 128

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

Configuration issue for clients that mount NFS shares using a non-

reserved port .......................................................................................... 129

Certain special characters are case sensitive ............................................... 129

Widelinks are not accessible from Mac clients ........................................... 129

SAN administration issues ...................................................................................... 129

I/O delays sometimes seen after controller failover on Linux hosts with

ALUA .................................................................................................... 129

If you use the automatic sizing feature on thinly provisioned LUNs

when snap reserve is set to a non-zero value ......................................... 130

Data protection issues .............................................................................................. 131

Read performance for mirrored aggregates not in a MetroCluster

configuration might be degraded ........................................................... 131

ADIC Quantum tape libraries are not discovered by Data ONTAP ........... 131

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

Restore engine does not honor any mandatory or advisory locks on files . . 132

Tape devices behind DataFort are not detected unless a known SCSI

device is mapped to LUN 0 ................................................................... 132

Third-party storage issues (V-Series systems only) ................................................ 132

Restrictions for V-Series system upgrade to Data ONTAP 8.1 or later ...... 132

MultiStore issues ..................................................................................................... 133

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

Platform maintenance issues ................................................................................... 133

Possible giveback failure during controller or NVRAM8 replacement on

62xx or 32xx systems ............................................................................ 133

Data ONTAP-v platform issues .............................................................................. 133

savecore command does not work .............................................................. 134

Some error messages contain "VSA" instead of "Data ONTAP-v" ............ 134

Changes to published documentation ..................................................... 135


Changes to the System Administration Guide ........................................................ 135

Changes to information about the /etc/rc file .............................................. 135

Corrections to the timed options ................................................................. 135

Changes to the High-Availability Configuration Guide ......................................... 135

Virtual channel rules are not required ......................................................... 135

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

Commands not supported in Data ONTAP 8.1.1 ........................................ 136

The nvfail_rename command does not exist in Data ONTAP 8.1.x ........... 136

Changes to the Storage Management Guide ........................................................... 136

Combining SAS HDDs and SSDs in the same disk shelf is not supported

................................................................................................................ 136

4-TB SATA disks are not supported for this version of Data ONTAP ....... 136

Changes to the SAN Administration Guide ............................................................ 136

Block Access Management Guide has a new title ...................................... 136

Volume moves between 32-bit aggregates and 64-bit aggregates .............. 137

Changes to the Software Setup Guide ..................................................................... 137

Changes to DHCP requirements for remote access .................................... 137

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

The Fibre Channel and iSCSI Configuration Guide has a new name ......... 137

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

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

Copyright information ............................................................................. 139Trademark information ........................................................................... 140How to send your comments .................................................................... 141


Data ONTAP 8.1.1 Release Notes for 7-Mode

The release notes describe new features, enhancements, and known issues for Data ONTAP 8.1.1operating in 7-Mode, as well as additional information related to running this release on specificstorage systems.

About the Data ONTAP 8.1.1 release

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

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

Attention: If you have a 3140 storage system with Flash Cache modules, Data ONTAP 8.1.1reenables the 256-GB Flash Cache module on the 3140 storage systems using the full capacity forwear-leveling and cache storage. However, to deliver on the full value of Data ONTAP 8.1.1 , themaximum working dataset in the 256-GB Flash Cache module on 3140 storage systems is 128 GB.For additional information, see 3210 and 3140 storage systems with Flash Cache modules aresupported on page 105.

For a complete list of functionality changes introduced in this release, see New and changed featuresin the Data ONTAP 8.1 release family on page 23. If you are upgrading from a Data ONTAP 7.3.xrelease, see also New and changed features in the Data ONTAP 8.0 release family on page 46.

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

About these release notes

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

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

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

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

• Changes to published documentation on page 135 contains information that has becomeavailable after the library provided with this release was published.

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

13

Related information

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


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

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

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


Changes introduced since Data ONTAP 8.1

You can find information about the changes that were introduced with each release since DataONTAP 8.1.

Note:

• If you are new to the Data ONTAP 8.1 family, go directly to New and changed features in theData ONTAP 8.1 release family on page 23.

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

Changes in Data ONTAP 8.1.1 for 7-ModeThis release includes support for new hardware, software enhancements, and bug fixes.

New platform and hardware support in Data ONTAP 8.1.1

New support includes the following:

• Support for the FAS2220 platform on page 23• Support for systems with only SSDs on page 24• Support for the Data ONTAP-v platform on page 23• Support for 900-GB SAS disks on page 24• Support for the DS4246 disk shelf on page 24• Support for the DS4486 disk shelf on page 24

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

New and changed features in Data ONTAP 8.1.1

• Manageability enhancements on page 25

• Free space reallocation of aggregates on page 25• Role-based access control for LDAP users' system access on page 26• Support of core segments on page 26• SP SSH access control and automatic timeout on page 26• RLM SSH access control and automatic timeout on page 26• SSH port forwarding for the SP is disabled by default on page 27• SSH port forwarding for the RLM is disabled by default on page 27• Changes in aggregate Snapshot copy management on page 27

15

http://support.netapp.com/

• SSH server version for Data ONTAP on page 27

• Storage resource management enhancements on page 32

• Support for Flash Pools on page 32• Support for the Advanced Zone Checksum (AZCS) checksum type on page 32• Support for sanitizing SSDs on page 32

• High-availability pair enhancements on page 33

• MetroCluster support for 8-Gb FC INIT card on page 33• MetroCluster support for Cisco switches on page 34

• File access protocol enhancements on page 36

• Support for SMB 2.1 on page 36• Support for BranchCache on page 37• Support for lease oplocks on page 37• Enhancements to procedure for computer account password change on page 38• Support for VMware vStorage over NFS on page 38

• SAN enhancements on page 39

• Windows Server 2012 support on page 39

• Data protection enhancements on page 40

• Support for SnapVault with nondefault vFiler units on page 40• Support for incremental and differential backups using SMTape engine on page 41• Support for restore to volumes in 64-bit aggregates using SMTape engine on page 41

• Storage efficiency enhancements on page 42

• Changes to deduplication on page 42

• MultiStore enhancements on page 42

• Online migration of vFiler units is not supported on Flash Pools on page 133

For information about all new and changed features in this release, see New and changed features inthe Data ONTAP 8.1 7-Mode release family on page 23.

New commands in Data ONTAP 8.1.1

• cifs branchcache hash stat

• cifs branchcache set key

• coredump segment config modify

• coredump segment config show

• coredump segment delete

• coredump segment delete-all

• coredump segment show


• coredump segment start

• coredump segment status

• coredump segment stop

• storage shelf identify

Changed commands in Data ONTAP 8.1.1

• aggr options

• aggr status

• cifs shares

• df

• lock status

• qtree oplock

• storage show disk• sysconfig

• vol status

For information, see Changed commands in the Data ONTAP 8.1 release family operating in 7-Modeon page 69.

New options in Data ONTAP 8.1.1

New options include the following:

• cifs.smb2_1.branch_cache.enable

• cifs.smb2_1.branch_cache.hash_time_out

• cifs.W2K_password_change

• cifs.W2K_password_change_interval

• cifs.W2K_password_change_within

• nfs.mount_rootonly

• nfs.v2.enable

• nfs.v4.id.allow_numerics

• nfs.vstorage.enable

• rlm.autologout.enable

• rlm.autologout.timeout

• rlm.ssh.access

• snapmirror.vsm.volread.smtape_enable

• sp.autologout.enable

• sp.autologout.timeout

• sp.ssh.access

For more information, see New options in the Data ONTAP 8.1 release family operating in 7-Modeon page 75.

Changes introduced since Data ONTAP 8.1 | 17

Changed options in Data ONTAP 8.1.1

The following options changed in this release:

• cifs.oplocks.enable

• cifs.smb2.client.enable

• cifs.smb2.durable_handle.enable

• cifs.smb2.durable_handle.timeout

• cifs.smb2.enable

• cifs.smb2.signing.required

• cifs.weekly_W2K_password_change

• security.admin.nsswitchgroup

For more information, see Changed options in the Data ONTAP 8.1 release family operating in 7-Mode on page 82.

Requirements for running Data ONTAP 8.1.1

New requirements include the following:

• V-Series limits information on page 100• Data ONTAP-v requirements and support information on page 101• FAS2220 is a new platform listed in Supported systems on page 98.

For more information, see Requirements for running Data ONTAP 8.1 7-Mode on page 98.

New cautions in Data ONTAP 8.1.1

• Upgrade and revert cautions on page 102

• Automatic background disk firmware updates not enabled for nonmirrored RAID4 aggregateson page 107

• iSCSI target adapters not supported in Data ONTAP 8.1 and later on page 102• If you revert to a release earlier than Data ONTAP 8.1 you might need to install licenses for

some products on page 104• 3210 and 3140 storage systems with Flash Cache modules are supported on page 105• Downgrade to Data ONTAP 8.1 not allowed for 3140 and 3210 systems with Flash Cache

modules on page 108• MultiStore license and vFiler units removed when reverting to Data ONTAP 8.0.x on page

108

• Setup cautions on page 109

• CIFS setup overwrites the storage system password on page 109

• Manageability cautions on page 110

• System panics when Flash Cache is full and the root volume is a traditional volume on page110


• Storage management cautions on page 111

• Growing a volume while its associated aggregate is expanding to 64-bit can cause systemdisruption on page 111

• Initiating aggregate expansion to 64-bit using a larger disk can cause system disruption onpage 111

• Accessing data in a qtree in a Snapshot copy can cause system disruption on page 112• Preventing service disruption when expanding an aggregate with volumes using quotas on

page 112• Changing the language of a FlexVol volume when expansion scanner is running could result

in system disruption on page 113• Some 32-bit operations cannot be performed on a Flash Pool on page 113• Requirements for converting an aggregate to a Flash Pool on page 113

• File access and protocols cautions on page 115

• CIFS startup might take several minutes after cluster failover giveback on page 115• CIFS setup might lead to removal of already existing user created CIFS shares on page 116• CIFS SID and credential leak impacts cache memory availability on page 116

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

Cautions removed in Data ONTAP 8.1.1

• Non-ASCII characters in the comment string of the lun setup command result in system panic• 3210 and 3140 systems with Flash Cache modules are not supported• Mirroring a ZCS aggregate is not supported for this release of Data ONTAP• Oplock breaks might cause panic when using durable handles• Storage Encryption preconfiguration requirements• “Write operations might fail or LUNs might go offline if deduplication metadata increases” was

moved to the Limitations section.• Storage system panic due to nonresponsive key management server• Retrieving authentication keys might cause storage system panic

New known problems and limitations in Data ONTAP 8.1.1

• Manageability issues on page 119

• Cached data in a Flash Cache module is cleared during upgrade to the Data ONTAP 8.1release family on page 119

• Storage resource management issues on page 122

• Files might not be able to be deleted using NFS in a full FlexVol volume on page 122• Disks might be silently left unassigned for multi-disk carrier shelves on page 122


• You cannot assign ownership and checksum type for spare disks or array LUNs in the sameoperation on page 123

• Configuring ACP to use a different port on the 22xx platform causes E0P to becomeunresponsive on page 124

• Network protocol issues on page 124

• Partner node might be unavailable during controller failover when an interface name is usedas an alternate host name in the /etc/hosts file on page 124

• Static routes are not retargeted to a network interface with a new autoconfigured IPv6 addresson page 125

• File access protocol issues on page 126

• Value of the option nfs.ifc.rcv.high is unexpectedly reset on page 126• Microsoft Windows 7 clients fail to rename files or directories on page 127• File copy operation on a widelink path inside a CIFS share might fail when using SMB 2.x on

page 127• CIFS client authentication fails if host name exceeds 16 characters on page 126• Domain Controller responds with an access denied error to SMB2 tree connect request on

page 127• CIFS users unable to rename or delete home directories on page 128

• Data ONTAP-v platform issues on page 133

• savecore command not working on page 134• Error messages contain VSA instead of Data ONTAP-v on page 134

• Data protection issues on page 131

• ADIC Quantum tape libraries are not discovered by Data ONTAP on page 131

For more information about all the limitations in the Data ONTAP 8.1 release family for 7-Mode, see Known problems and limitations on page 119.

Limitations removed in Data ONTAP 8.1.1

The following limitations have been removed in this release:

• CIFS access to SnapVault or qtree SnapMirror destination can cause system panic• Issues with exportfs commands in noninteractive SSH sessions• SSD spare blocks consumed limit reported as n/a• Entering dummy network addresses during ACP setup can cause a system panic• CIFS shares with comment ending with backslash disappear• Error NFS4_BADOWNER when NFSv4 client passes UID as string• CIFS clients must reopen files after you break locks• File screening requests fail due to FPolicy server connection timeout• Large number of locks might cause temporary performance degradation


• User mapping fails for users in a trusted domain• Reboot required after updating the krb5.conf file• Specification of the default keytab file• Aggregate snapshot copy creation and aggr copy commands fail with an aggregate

Snapshot reserve of 0 percent• Exceeding the maximum number of assigned devices results in a panic

Documentation changes for Data ONTAP 8.1.1

• Virtual channel rules are not required on page 135• nvfail_rename command does not exist on page 136• Combining SAS and SSDs in the same disk shelf is not supported on page 136• 4-TB SATA disks are not supported for this version of Data ONTAP on page 136• Changes to information about the /etc/rc file on page 135• The Block Access Management Guide has a new title on page 136• Volume moves between 32-bit aggregates and 64-bit aggregates on page 137• Changes to DHCP requirements for remote access on page 137

For more information about important documentation changes, see Changes to publisheddocumentation on page 135.


Unsupported features

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

Features not available or discontinued in Data ONTAP 8.1 and later releasesoperating in 7-Mode

• FilerViewFilerView is no longer available on systems running Data ONTAP 8.1 or later releases. You canuse OnCommand System Manager as a web-based graphical management interface to managecommon storage system functions from a web browser.For more information about OnCommand System Manager, see the NetApp Support Site.

• Support for DS14mk2 shelves is discontinued.For additional information, see Support for DS14mk2 shelves with ESH2 modules on page 25.

• UPS management is not supported.For additional information, see UPS management is no longer supported on page 31.

• 2-Gb FC target ports are not supported.For additional information, see 2-Gb FC ports not supported as targets on page 117.

Features not available in Data ONTAP 8.0 and later releases operating in 7-Mode

• NetbootNetboot is not a supported function unless you are restoring the Data ONTAP image on the bootdevice, such as a PC CompactFlash card. For information about how to replace a PCCompactFlash card or restore the Data ONTAP image on the card, see the Replacing aCompactFlash Card flyer that is applicable to your version of Data ONTAP.

• NetApp SnapValidator for Oracle is not supported.• IPsec

IPsec is not supported. If IPsec is enabled on your storage system, be aware that it will bedisabled automatically during the upgrade.

• TOETOE functionality is not supported. There is no adverse effect on the performance of your storagesystem because TOE is disabled.

Related information

NetApp Support Site: support.netapp.com



New and changed features in the Data ONTAP 8.1release family

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

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

Additional major changes are described here. For other important information in these release notesabout changes to the product made by these releases, see the summary of all new and changedcommands and options in the release family at New and changed commands and options in the DataONTAP 8.1 7-Mode release on page 63. Bugs Online provides a suite of tools to help manage andresolve your bug issues. For more information, see Bugs Online on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

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

For information about the supported systems, see Supported systems on page 98.

Support for the FAS2220 platformData ONTAP 8.1.1 and later releases support the FAS2220 platform.

The FAS22xx Product Datasheet provides a comparative overview of the FAS2240 platforms and theFAS2220 platform.

Support for the FAS2240 platformData ONTAP 8.1 and later releases support the FAS2240 platform.

The FAS22xx Product Datasheet provides a comparative overview of the FAS2240 platforms and theFAS2220 platform.

Support for the Data ONTAP-v platformData ONTAP 8.1.1 provides support for the Data ONTAP-v platform. Data ONTAP-v is a softwareversion of a storage controller that runs Data ONTAP software in a virtual machine. This enablesData ONTAP to run on high-performance servers supported by VMware vSphere to manage storagein virtualized environments.

The two products that are currently available using Data ONTAP-v technology are:

23

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

https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=12070

https://fieldportal.netapp.com/viewcontent.asp?qv=1&docid=12070

• Data ONTAP Edge - This remote office storage solution provides backup capabilities viaSnapVault to centralized NetApp storage hardware.

• Data ONTAP Edge-T - This remote office storage solution provides bidirectional backup andreplication capabilities via SnapMirror and SnapVault to centralized NetApp storage hardware.

The hardware platform on which Data ONTAP-v is installed must meet certain system and virtualmachine requirements in order to work properly. See the Interoperability Matrix at support.netapp.com/NOW/products/interoperability for more information.

To deploy Data ONTAP-v storage software on a host server, and to manage it as a platform, NetApphas developed the Data ONTAP-v administration tool, called dvadmin. dvadmin must be used toinstall Data ONTAP-v storage systems.

The Data ONTAP-v storage software running on the virtual machine (for example, the Data ONTAPEdge product) does not support all the functionality of Data ONTAP when it is running on ahardware controller. See the "Data ONTAP-v supported and unsupported functionality" topic in theData ONTAP Edge Installation and Administration Guide for complete information.

Support for systems with only SSDsData ONTAP 8.1.1 and later releases support SSD-only configurations for most storage systemmodels. For these models, the presence of HDDs is not required.

To see which models support SSD-only configurations, see the Hardware Universe (formerly theSystem Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml.

Support for 900-GB SAS disksIn Data ONTAP 8.1.1 and later releases, 900-GB disks are supported for DS2246 SAS disk shelves.These are performance disks (rather than capacity disks) and their speed is 10K.

Support for the DS4246 disk shelfData ONTAP 8.1.1 provides support for the DS4246 disk shelf.

For the DS4246 technical specifications, including supported Data ONTAP versions, disk drives, andplatforms, see Disk shelves for FAS and V-Series systems at www.netapp.com/us/products/storage-systems/disk-shelves-and-storage-media/disk-shelves-tech-specs.html.

For information about installing and cabling the DS4246 disk shelf, see the DS4243, DS2246,DS4486, and DS4246 Disk Shelf Installation and Service Guide.

Support for the DS4486 disk shelfData ONTAP 8.1.1 provides support for the multi-disk carrier DS4486 disk shelf.

For the DS4486 technical specifications, including supported Data ONTAP versions, disk drives, andplatforms, see Disk shelves for FAS and V-Series systems at www.netapp.com/us/products/storage-systems/disk-shelves-and-storage-media/disk-shelves-tech-specs.html.


http://support.netapp.com/NOW/products/interoperability/

http://support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml


http://www.netapp.com/us/products/storage-systems/disk-shelves-and-storage-media/disk-shelves-tech-specs.html




For information about installing and cabling the DS4486 disk shelf, see the DS4243, DS2246,DS4486, and DS4246 Disk Shelf Installation and Service Guide. For information about using multi-disk carrier disk shelves with Data ONTAP, see the Data ONTAP Storage Management Guide for 7-Mode.

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

Support for ATTO FibreBridge 6500NStarting with Data ONTAP 8.1, the ATTO FibreBridge 6500N, which is a Fibre Channel-to-SASbridge that allows SAS disk shelves (with SAS or SATA disk drives) to be used in stretch and fabricMetroCluster configurations, is supported.

Systems including DS14mk2 shelves with ESH2 modulesBeginning with Data ONTAP 8.1, DS14mk2 disk shelves with ESH2 storage I/O modules are nolonger supported. If even one of these devices is attached to your storage system, do not upgrade toData ONTAP 8.1 or later until after you replace the devices.

Upgrading a system with these devices attached to it results in an unsupported system configurationand shelf configuration errors.

If you want to upgrade to Data ONTAP 8.1 or a later release and your storage environment includesthe obsolete DS14mk2 with ESH2 devices, you should contact your NetApp representative to discussupgrading to DS4243 or DS2246 disk shelves.

Manageability enhancementsYou can find information about the new and changed manageability capabilities.

Free space reallocation of aggregatesStarting in Data ONTAP 8.1.1, you can enable free space reallocation on aggregates to improve writeperformance. Free space reallocation improves write performance by optimizing the free spacewithin an aggregate.

Free space reallocation works best on workloads that perform a mixture of small random overwritesand sequential or random reads. You can expect additional CPU utilization when you enable freespace reallocation. You should not enable free space reallocation if your storage system hassustained, high CPU utilization.

You use the aggr options command with the free_space_realloc option to enable free spacereallocation.

For more information about free space reallocation, see the Data ONTAP System AdministrationGuide for 7-Mode.

New and changed features in the Data ONTAP 8.1 release family | 25

Role-based access control for LDAP users' system accessStarting with Data ONTAP 8.1.1, the security.admin.nsswitchgroup option enables you tomap LDAP groups to specified roles on the system and manage LDAP users’ access to the system.

Mapping an LDAP group to a role enables users in that group to have only the capabilities granted bythe mapped role. The role can be a predefined role or one that you create by using the useradminrole add command. If you do not specify a role for an LDAP group, users in that group are grantedcapabilities of the “admin” role and have full administrative access to the storage system.

For more information about mapping an LDAP group to a role on the storage system, see the DataONTAP System Administration Guide for 7-Mode. For information about thesecurity.admin.nsswitchgroup option, see the na_options(1) man page.

Support of core segmentsA core dump file can be very large, making it time consuming to upload to technical support whenyou need to. Starting with Data ONTAP 8.1.1, you can segment a saved core dump file into coresegments for easier handling.

You use the coredump segment config commands to configure the automatic segmenting ofcore dump files.

You use the coredump segment commands to manage core segments.

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

SP SSH access control and automatic timeoutStarting with Data ONTAP 8.1.1, you can configure the SP to accept SSH requests from only theadministration hosts that you specify. You can also configure the automatic logout settings so that anSSH connection to the SP is automatically terminated after the connection has been idle for thenumber of minutes you specify.

These enhancements are supported on 32xx and 62xx systems that are running SP firmware 1.3 orlater and FAS22xx systems that are running SP firmware 2.1 or later.

For information about configuring SP SSH access control and automatic logout, see the DataONTAP System Administration Guide for 7-Mode.

RLM SSH access control and automatic timeoutStarting with Data ONTAP 8.1.1, you can configure the RLM to accept SSH requests from only theadministration hosts that you specify. You can also configure the automatic logout settings so that anSSH connection to the RLM is automatically terminated after the connection has been idle for thenumber of minutes you specify.

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


For information about configuring RLM SSH access control and automatic logout, see the DataONTAP System Administration Guide for 7-Mode.

SSH port forwarding for the SP is disabled by defaultOn 32xx and 62xx systems that are running SP firmware 1.3 or later and FAS22xx systems that arerunning SP firmware 2.1 or later, SSH port forwarding for the SP is disabled by default.

SSH port forwarding for the RLM is disabled by defaultOn systems that are running RLM firmware 4.1 or later, SSH port forwarding for the RLM isdisabled by default.

Changes in aggregate Snapshot copy managementData ONTAP 8.1.1 introduces changes about aggregate Snapshot copy creation and its requirementabout aggregate Snapshot reserve.

For aggregate Snapshot copy creation and the aggr copy commands to succeed, you no longer needto increase the aggregate Snapshot reserve to a non-zero percentage.

In addition, if you want to create aggregate Snapshot copies but the aggregate has an aggregateSnapshot reserve of 0 percent and automatic aggregate Snapshot copy deletion is enabled, theoperation to create aggregate Snapshot copies still succeeds if both of the following conditions aremet:

• The aggregate has at least 10 percent of free space.For Snapshot copy creation, the space that is reserved in the aggregate to honor a FlexVolvolume's guarantee is considered free space in the aggregate.

• The aggregate Snapshot copies do not exceed the current aggregate Snapshot reserve by morethan 5 percent of the size of the aggregate.

SSH server version for Data ONTAPThe SSH server version running on Data ONTAP is Data ONTAP SSH version 1.0, which isequivalent to OpenSSH server version 3.4p1.

For information about the Common Vulnerabilities and Exposures (CVE) fixes implemented in DataONTAP, see the Suspected Security Vulnerabilities page on the NetApp Support Site.

Related information

Suspected Security Vulnerabilities page: support.netapp.com/NOW/knowledge/docs/olio/scanner_results


http://support.netapp.com/NOW/knowledge/docs/olio/scanner_results/

http://support.netapp.com/NOW/knowledge/docs/olio/scanner_results/

Cache rewarming for Flash Cache modulesStarting in Data ONTAP 8.1, the WAFL external cache preserves the cache in a Flash Cache moduleduring a graceful shutdown.

When a storage system powers down, the WAFL external cache takes a snapshot of the data in aFlash Cache module. When the system powers up, it uses the snapshot to rebuild the cache. After theprocess completes, the system can read data from the cache. This process, called cache rewarming,helps to maintain system performance after a planned shutdown. For example, you might shut downa system to add hardware or upgrade software.

Cache rewarming is enabled by default if you have a Flash Cache module installed. Cacherewarming is available when both nodes in an HA pair are running Data ONTAP 8.1.

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

Enhancements to reallocation scans, read reallocation, and extentsYou can now use reallocation scans, read reallocation, and extents to optimize the layout of specifictypes of volumes.

Optimizing the layout of volumes can improve the read performance of host applications that accessdata on the storage system.

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

Reallocation scans, read reallocation, and extents with FlexVol volumes contained inmirrored aggregates

In prior releases, you could enable reallocation scans, read reallocation, and extents on FlexVolvolumes contained in mirrored aggregates. However, some command options were not supportedwith this type of volume.

Starting in Data ONTAP 8.1.1, you can use the following command options to optimize the layout ofFlexVol volumes that are contained in mirrored aggregates:

Reallocationscans

You can use the -p option when you run the reallocate start command.The -p option (also called physical reallocation) reallocates user data on thephysical blocks in the aggregate while preserving the logical block locationswithin a FlexVol volume.

Readreallocation

You can set the read_realloc option to space_optimized when you run thevol options command. space_optimized conserves space but results indegraded Snapshot read performance.

Extents You can set the extent option to space_optimized when you run the voloptions command. space_optimized conserves space but results indegraded Snapshot read performance.


Reallocation scans, read reallocation, and extents with deduplicated volumes

Starting in Data ONTAP 8.1, reallocation scans, read reallocation, and extents can optimize thelayout of a deduplicated volume.

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

Reallocationscans

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

Readreallocation

Set the read_realloc option to space_optimized when you run the voloptions command. Read reallocation skips deduplicated data if you set theread_realloc option to on.

Extents Set the extent option to space_optimized when you run the vol optionscommand. Extents skip deduplicated data if you set the extent option to on.

System health monitoringYou can proactively manage your system by monitoring a single, integrated health status.

If the status is degraded, you can view details about the problem, including the probable cause andrecommended recovery actions. After you resolve the problem, the system health statusautomatically returns to OK.

The system health status reflects multiple separate health monitors. A degraded status in anindividual health monitor causes a degraded status for the overall system health.

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

For information about monitoring your system's health, see the Data ONTAP System AdministrationGuide for 7-Mode and the man pages for the system health commands.

AutoSupport enhancementsStarting in Data ONTAP 8.1, AutoSupport messages contain more targeted data, are easier tomanage, and offer better protocol and privacy support.

The content of AutoSupport messages is more focused and compact because of the followingchanges:

• The data sent in event-triggered AutoSupport messages is now specific to the trigger event.• Many log files that are sent in AutoSupport messages now contain only new lines added since the

last AutoSupport message.• 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:

• You have more visibility into past messages and their content, as well as the content that will besent in future messages.


• You can add more data to future messages sent in response to specific triggers, and you cancontrol whether your internal support organization receives messages for specific triggers.

• If an AutoSupport message is not successfully transmitted, you can manually resend it.• By default, the system collects AutoSupport information and stores it locally even if AutoSupport

is disabled.Local collection of AutoSupport files provides valuable historical information that technicalsupport staff can use to quickly solve future problems.

Protocol support for AutoSupport has improved in the following ways:

• IPv6 is supported.• HTTPS certificates are validated.• HTTP(S) uses PUT requests, enabling failed messages to restart from where they left off.

POST is also still supported.• Message size limits are available for HTTP(S) and SMTP.

Privacy is improved when you use the autosupport.content minimal option. Instead ofomitting all private data, some private data is now masked and encoded. Also, by default, themessage subject line contains the server's system ID instead of its host name.

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

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

FilerView is no longer availableFilerView is no longer available on systems running Data ONTAP 8.1 or later releases. You can useOnCommand System Manager as a web-based graphical management interface to manage commonstorage system functions from a web browser.

For more information about OnCommand System Manager, see the NetApp Support Site.

Related information




UPS management is no longer supportedAs of Data ONTAP 8.1, uninterruptible power supply (UPS) management (by using the upscommand) is no longer supported.

Changes to default aggregate Snapshot reserve for newly creatednonmirrored aggregates

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

For information about managing aggregate Snapshot copies and considerations for increasing theaggregate Snapshot reserve, see the Data ONTAP System Administration Guide for 7-Mode.

IPv6 support for SP and RLMThe 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, SP must be configured forIPv6, and the storage system must also have IPv6 enabled.

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

Note: BMC supports IPv4 only.

Support for Transport Layer Security protocolThe Data ONTAP 8.1 release family supports Transport Layer Security (TLS) version 1.0, whichprovides better security protections than previous SSL versions did.

If you enable TLS on a storage system, you can use it with HTTPS, LDAP, and FTPS 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 enable TLS. For informationabout how to enable TLS, see the Data ONTAP System Administration Guide for 7-Mode.

Licensing changesStarting with Data ONTAP 8.1, you no longer need to add license keys on your system for mostfeatures that are distributed free of cost.

In addition, some features are now grouped together so that only one license key is required to add apack of features to a system. Also, some features and products are enabled when you add certainother license keys.

For information about Data ONTAP 8.1 licensing models and whether a license key must be addedfor a particular feature or pack, see the knowledgebase article Using License Keys with Data ONTAP8.1 7-Mode FAQ on the NetApp Support Site.


Related information

Using License Keys with Data ONTAP 8.1 7-Mode FAQ

Storage resource management enhancementsThis Data ONTAP release provides improved performance, resiliency, and management capabilitiesfor storage resources.

Support for Flash PoolsData ONTAP 8.1.1 provides support for Flash Pools—aggregates that incorporate both HDDs andSSDs. The HDDs are used for primary storage, and the SSDs provide a high-performance read andwrite cache to boost aggregate performance.

For information about creating and managing Flash Pools, see the Data ONTAP StorageManagement Guide for 7-Mode and TR 4070: NetApp Flash Pool Design and ImplementationGuide.

Related information

TR 4070: NetApp Flash Pool Design and Implementation Guide

Support for the Advanced Zone Checksum type (AZCS)Data ONTAP 8.1.1 provides support for a new checksum type, AZCS. AZCS is the default type for3-TB disks in the DS4486 disk shelf. AZCS delivers greater usable capacity per disk for largecapacity disks (for example, SATA).

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

Support for sanitizing SSDsData ONTAP 8.1.1 and later releases provide support for sanitizing most SSD models.

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

Enhancements to aggregatesData ONTAP 8.1 and later releases support several enhancements for aggregates.

Starting in Data ONTAP 8.1, aggregates support the following enhancements:

• You can nondisruptively expand 32-bit aggregates to the 64-bit format, without requiring data tobe copied or moved.For more information about expanding 32-bit aggregates to the 64-bit format, see the DataONTAP Storage Management Guide for 7-Mode.

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


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

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

For more information about SnapMirror, see the Data ONTAP Data Protection Online Backupand Recovery Guide for 7-ModeData ONTAP Data Protection Guide for Cluster-Mode.

• The maximum aggregate size increased for some platforms.To determine the maximum aggregate size for your platform, see the Hardware Universe.

3210 systems now support 500 FlexVol volumesIn Data ONTAP 8.0, 3210 systems supported 200 volumes. In Data ONTAP 8.1 and later releases,3210 systems support 500 FlexVol volumes.

For information about how many FlexVol volumes are supported on other storage system models,see the Hardware Universe (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml.

Limit on number of subdirectories has been removedIn earlier versions of Data ONTAP, you could not create more than 99,998 subdirectories in anydirectory. In Data ONTAP 8.1 and later versions, there is no limit on the number of subdirectoriesyou can create.

Enhancements to FlexClone files and FlexClone LUNsStarting with Data ONTAP 8.1, you can create instantaneous clones of files and LUNs present in aFlexVol volume. In addition, you can create FlexClone files from Snapshot copies of parent filespresent in the FlexVol volume.

You can create a maximum of 32,767 FlexClone files or FlexClone LUNs from a parent file or LUNwithout creating a physical copy of the parent entity. If you try to create more than 32,767 clones,Data ONTAP automatically creates a new physical copy of the parent file or LUN.

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

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

MetroCluster configuration supports 8-Gb host bus adapterBeginning with Data ONTAP 8.1.1, MetroCluster configuration supports Quad-Port 8-Gb host busadapter.

For more information, see the MetroCluster Compatibility Matrix available at the NetApp SupportSite at support.netapp.com.





MetroCluster system support for shared-switches configurationBeginning with Data ONTAP 8.1, MetroCluster system supports shared-switches configuration. In ashared-switches configuration, two fabric-attached MetroCluster systems share the same fourswitches and the ISLs between them.

For more information about the cabling and setting the ports in shared-switches configuration, see theData ONTAP High-Availability and MetroCluster Configuration Guide for 7-Mode on the NetAppSupport Site at support.netapp.com.

MetroCluster support for Cisco switchesBeginning with Data ONTAP 8.1.1, the fabric-attached MetroCluster configuration also supportsCisco switches.

The following Cisco switches are supported:

• Cisco MDS 9148• Cisco MDS 9222i

Note: The Cisco MDS 9148 switch can be installed in the NetApp cabinet, however, the CiscoMDS 9222i needs to be installed in a separate rack.

For more information about Cisco switch configuration, see the Fabric-attached MetroCluster CiscoSwitch Configuration Guide and for installing the Cisco 9148 switch into the NetApp cabinet, see theInstalling the Cisco 9148 switch into the NetApp cabinet available on the NetApp Support Site at support.netapp.com.

Networking and security protocol enhancementsData ONTAP 8.1 and later releases include a number of new features and networking and securityprotocol enhancements.

Support for IPv6Starting with Data ONTAP 8.1, IPv6 addressing is supported. You can enable IPv6 on your storagesystem or on an HA pair and perform various tasks such as configuring network interfaces, VLANs,and interface groups. IPv6 is supported on the CIFS, NFS, HTTP, and FTP protocols.

You can enable IPv6 on your storage system during setup. For more information, see the DataONTAP Software Setup Guide for 7-Mode.

You can also enable IPv6 on your storage system during operation by setting the optionsip.v6.enable option to on. For more information, see the Data ONTAP Network ManagementGuide for 7-Mode.

IPv6 features in Data ONTAP 8.1

The following IPv6 features are supported in Data ONTAP 8.1:




• IPv6 dual stack mechanism to enable communication over IPv4 and IPv6• Neighbor Discovery that includes Router Discovery and Duplicate Address Detection• IPv6 stateless address autoconfiguration, requiring minimal manual configuration of hosts• Internet Control Message Protocol version 6 (ICMPv6)• Path MTU discovery for IPv6• Transmission of IPv6 packets over Ethernet links• IPv6 static routes and router alert option• Network administration commands, such as the traceroute6, ping6, netdiag, and pktt

commands• Telnet server to accept IPv6 connection requests• Syslog for the IPv6-related events• Host name and address resolution with DNS, DDNS, and NIS over IPv6• Configuration of VLANs with IPv6 addresses• Configuration of base VLAN interfaces with IPv6 addresses• Network Time Protocol (NTP)• Configuration of single-mode, static multimode, and dynamic multimode (LACP) vifs with IPv6

across multiple NICs• SNMPv1, SNMPv2c, and SNMPv3• MIB for TCP, UDP, ICMPv6, and IPv6• HA configuration, which includes takeover and giveback of IPv6 addresses and routes, mapping

partner IPv6 interfaces, and executing commands with IPv6 addresses in the partner contextFor more information, see the Data ONTAP High-Availability and MetroCluster ConfigurationGuide for 7-Mode.

• IPv6 addresses in the vFiler commandsFor more information, see the Data ONTAP MultiStore Management Guide for 7-Mode.

• iSCSI over IPv6For more information, see the Data ONTAP SAN Administration Guide for 7-Mode.

• File access protocols—CIFS, FTP, HTTP, NFSv2, NFSv3, and NFSv4—over IPv6For more information, see the Data ONTAP File Access and Protocols Management Guide for 7-Mode.

• LDAP and Kerberos version 5 with IPv6• HTTPS over IPv6 addresses

HTTPS can be used for secure administrative access; however, SecureAdmin SSL must beenabled before you can issue HTTPS requests to the storage system.

• SSH protocol version 2 over IPv6If IPv6 is enabled on your storage system, SecureAdmin SSH must be enabled before you canissue SSH requests to the storage system.

• SNMP traphosts with IPv6 addressesYou should specify only IPv6 addresses, and not host names, to identify IPv6 traphosts

• Fast path over IPv6For more information, see the Data ONTAP Network Management Guide for 7-Mode.

• RLM over IPv6


If IPv6 is enabled on your storage system, then you must ensure that the RLM firmware version is4.0 or later. Disabling IPv6 on Data ONTAP also disables IPv6 on the RLM.

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

For information about installing and updating the RLM firmware, see the Data ONTAPUpgrade and Revert/Downgrade Guide for 7-Mode.

For information about configuring the RLM, see the Data ONTAP System Administration Guidefor 7-Mode.

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

• MetroCluster configuration over IPv6For more information about MetroCluster configuration, see the Data ONTAP High-Availabilityand MetroCluster Configuration Guide for 7-Mode.

• RSH protocol over IPv6To connect to the storage system over the RSH protocol, you must ensure that the rsh.enableoption and the ip.v6.enable option are set to on.

• Dump, restore, and ndmpcopy commands over IPv6For more information about the commands, see the Data ONTAP Data Protection Tape Backupand Recovery Guide for 7-Mode.

• SnapMirror, SnapVault, and volume copy operations over IPv6For more information, see the Data ONTAP Data Protection Online Backup and Recovery Guidefor 7-Mode.

Improving TCP network congestion with Appropriate Byte CountingAppropriate Byte Counting (ABC) is an algorithm implemented in the TCP stack of Data ONTAPthat enables you to improve TCP performance and security. Starting from Data ONTAP 8.1, ABC isenabled by default on all the storage controllers.

File access protocol enhancementsThis Data ONTAP release includes a number of new features and enhancements for file access andprotocols management. This section provides an overview of these features and enhancements.

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

Support for SMB 2.1Data ONTAP 8.1.1 and later releases in the 8.1 release family support SMB 2.1. SMB 2.1 is a minorrevision of the SMB 2.0 protocol and introduces several enhancements.

The following enhancements are supported:


• Lease oplocksWhen SMB 2.1 is enabled, Data ONTAP uses SMB 2.1 lease oplocks, which is a new oplockmodel that provides advantages over traditional oplocks.

• Retrieval of content hashes used by BranchCacheBranchCache-enabled storage systems use content hashes to provide clients with informationabout cached content.

Data ONTAP does not support the following SMB 2.1 enhancements:

• Resilient handles• Large MTU• Write-through

For more information about SMB 2.1, see the Data ONTAP File Access and Protocols ManagementGuide for 7-Mode.

Support for BranchCacheData ONTAP 8.1.1 and later releases in the 8.1 release family support BranchCache caching.BranchCache was developed by Microsoft to enable caching of content on computers local torequesting clients. The Data ONTAP implementation of BranchCache can reduce wide-area network(WAN) utilization and provide improved access response time when users in a branch office accesscontent stored on a Data ONTAP storage system using CIFS.

With BranchCache enabled, Windows BranchCache clients first retrieve content from the storagesystem and then cache the content on a computer within the branch office. If another client in thebranch office requests the same content, the storage system determines whether the cached content isstill up-to-date and, if it is, sends the client metadata about the cached content. The client then usesthe metadata to retrieve content directly from the locally based cache.

BranchCache enabled storage systems use content hashes to provide clients with the metadatainformation about cached content. SMB 2.1 provides the content hash retrieval enhancement neededfor BranchCache.

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

Support for lease oplocksData ONTAP 8.1.1 and later releases in the 8.1 release family support lease oplocks, which provideenhanced locking over traditional oplocks. Available with SMB 2.1, the lease oplock model is basedon a key called a lease key rather than a file handle that is used with traditional oplocks.

Lease oplocks allow a client that is making multiple file open calls to obtain and preserve clientcaching state across the file open calls that it originates. The client generates a lease key and uses itto link together multiple handles to the same file. Operations on handles with the same lease key donot affect the oplock state. If the client and storage system connect using SMB 2.1, lease oplocks areused instead of traditional oplocks.


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

Enhancements to procedure for computer account password changeData ONTAP 8.1.1 and later releases in the 8.1 release family enable administrators to manage thetiming for password changes so that password changes for storage systems across the enterprise donot occur at the same time.

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

Support for VMware vStorage over NFSData ONTAP supports certain VMware vStorage APIs for Array Integration (VAAI) features in anNFS environment.

Supported features

The following features are supported:

• copy offloadEnables an ESXi host to copy virtual machines or virtual machine disks (VMDKs) directlybetween the source and destination data store location without involving the host. This conservesESXi host CPU cycles and network bandwidth. Copy offload preserves space efficiency if thesource volume is sparse.

• space reservationGuarantees storage space for a VMDK file by reserving space for it.

Limitations

VMware vStorage over NFS has the following limitations:

• vStorage is not supported with FlexCache.• Copy offload is not supported across vFiler units and across storage systems.• vStorage is not supported over IPv6.• Copy offload operations can fail in the following scenarios:

• While running wafliron on the source or destination volume because it temporarily takes thevolume offline

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


Support for SMB 2.0Beginning in Data ONTAP 8.1, clients can use the SMB 2.0 protocol to access files on the storagesystem.


Support for FTPSBeginning in Data ONTAP 8.1, clients can use the FTP over SSL (FTPS) protocol to access files onthe storage system.

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

Support for SFTPBeginning in Data ONTAP 8.1, clients can use the Secure File Transfer Protocol (SFTP) to accessfiles on the storage system.


SAN enhancementsThis Data ONTAP release includes a number of new SAN features and enhancements that youshould be familiar with.

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

Windows Server 2012 supportData ONTAP now supports Windows Server 2012 hosts in SAN environments. When you createLUNs for hosts that run Windows Server 2012, specify windows_2008 as the value for the ostype(LUN multiprotocol type).

Use the Interoperability Matrix to find a supported combination of hardware components, softwareversions, firmware, and drivers.

Related information

Interoperability Matrix: support.netapp.com/NOW/products/interoperability/



Data protection enhancementsData ONTAP 8.1.1 includes a number of new features and data protection enhancements.

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

SnapVault support for nondefault vFiler unitsStarting with Data ONTAP 8.1.1, you can create and modify SnapVault relationships and schedulesat the SnapVault secondary volume from the default vFiler unit (vfiler0) and the nondefault vFilerunit.

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

Support for volume SnapMirror replication between 32-bit and 64-bitvolumes

Starting with Data ONTAP 8.1, you can replicate volumes by using SnapMirror technology between32-bit and 64-bit volumes. For both synchronous and asynchronous volume replication, theSnapMirror source and destination volumes can be either 32-bit or 64-bit.

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

Support for concurrent volume SnapMirror and SMTape backup operationsStarting with Data ONTAP 8.1, you can make an SMTape backup of a volume SnapMirrordestination when SnapMirror transfers are in progress. You can run volume SnapMirror and SMTapebackup operations concurrently by enabling the vsm.smtape.concurrent.cascade.supportoption on a volume SnapMirror destination system.

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

Protection of data at rest through Storage EncryptionData ONTAP 8.1 7-Mode introduces the new Storage Encryption feature that allows you to protectyour data at rest by automatically encrypting all data written to disk. The feature is available on


certain supported storage controllers and disk shelves that contain disks with built-in encryptionfunctionality.

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

Support for SnapLockData ONTAP 8.1 7-Mode supports the SnapLock feature. Several significant improvements are madeto the SnapLock feature in this release.

Following are the key enhancements:

• System ComplianceClock• Volume ComplianceClock• Volume-level autocommit

For more information about these enhancements, see the Data ONTAP Archive and ComplianceManagement Guide for 7-Mode.

Support for incremental and differential backups using SMTape engineStarting with Data ONTAP 8.1.1, you can use the SMTape engine to perform incremental anddifferential backup and restore operations. If you want to perform an incremental or differentialbackup, you must perform both baseline and the incremental or differential backups by using onlythe NDMP-compliant backup applications.

When you perform SMTape operations, the NDMP-compliant backup applications create andmanage Snapshot copies for these operations.

Support for restore to volumes in 64-bit aggregates using SMTape engineUsing SMTape engine, you can restore data backed up in Data ONTAP 8.0.x from 32-bit or 64-bitaggregates to volumes in 64-bit aggregates in Data ONTAP 8.1.x and later. You can restore this datato volumes created across up to two major consecutive Data ONTAP releases only.


Storage efficiency enhancementsThis Data ONTAP release includes a number of new features and enhancements for storageefficiency enhancements. This section provides an overview of these features and enhancements.

Changes to deduplicationStarting with Data ONTAP 8.1.1, the change log file size limit is set to 1 percent of the volume sizeto manage the deduplication metadata overhead. The change log file size is related to the maximumvolume size. The space allocated for the change log files in a volume is not reserved.

Starting with Data ONTAP 8.1, you can enable the deduplication feature without adding a license.For deduplication, no limit is imposed on the supported maximum volume size. The maximumvolume size limit is determined by the type of storage system regardless of whether deduplication isenabled.

You can run deduplication operations on volumes from either of the nodes during takeover in an HApair.

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

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

Changes to data compressionStarting with Data ONTAP 8.1, data compression is supported on SnapLock volumes and in stretchand fabric-attached MetroCluster configurations. For compression, no limit is imposed on thesupported maximum volume size. The maximum volume size limit is determined by the type ofstorage system regardless of whether compression is enabled.

For more information about SnapLock, see the Data ONTAP Archive and Compliance ManagementGuide for 7-Mode and for MetroCluster configurations, see the Data ONTAP High-Availability andMetroCluster Configuration Guide for 7-Mode.

MultiStore enhancementsData ONTAP 8.1 and later releases include a number of new features and enhancements forMultiStore.

Online migration support for vFiler unitsStarting with Data ONTAP 8.1, you can perform online migration of vFiler units (also calledDataMotion for vFiler) from one storage system to another without experiencing any disruption in


data availability. You must be aware of the storage system models and disks that support onlinemigration of vFiler units.

You must use the NetApp Management Console interface to perform online migration of vFiler units.

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

For more information about the supported platforms and requirements, see the Technical Report-4072: NetApp DataMotion for vFiler.

Supported storage systems

• High-end storage systems, such as 62xx and 60xx• Mid-range storage systems, such as 32xx, 31xx, 3070, and 3040• Low-end storage systems, such as FAS2240, FAS2220 and FAS2040

Note: For V-Series systems, online migration of vFiler units is supported with native disks onlyand not with array LUNs on third-party storage arrays.

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

Supported source and destination storage systems with number of volumes formigration

Source storage system Destination storage system Number of volumes formigration

• 62xx• 60xx

• 62xx• 60xx

20

Note: If the source or destination storage system is either 6030 or 6040, then you can migrateonly 8 volumes.

• 62xx• 60xx

• 32xx• 31xx• 3070• 3040

8


Source storage system Destination storage system Number of volumes formigration

• 32xx• 31xx• 3070• 3040

• 62xx• 60xx• 32xx• 31xx• 3070• 3040

8

• FAS2240• FAS2220• FAS2040

• 62xx• 60xx• 32xx• 31xx• 3070• 3040• FAS2240• FAS2220• FAS2040

4

Supported disk types

• FC• SATA• SAS• BSAS

Related information

NetApp Support Site: support.netapp.comNetApp DataMotion for vFiler: media.netapp.com/documents/tr-4072.pdf

Interactive SSH support for vFiler unitsStarting with Data ONTAP 8.1, you can establish interactive SSH sessions with vFiler units. A vFilerunit can have only one active interactive SSH session established at a time. You can also use IPv6addresses to establish interactive SSH sessions.

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

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



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

Data compression support on vFiler unitsStarting with Data ONTAP 8.1, data compression is supported on vFiler units. You can perform datacompression 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 for 7-Mode.

V-Series enhancementsThe Data ONTAP 8.1.x release family includes a number of new features and enhancements for V-Series.

Removed V-Series environment variable requirement for Data ONTAP 8.1Starting in Data ONTAP 8.1, the fc-non-array-adapter-list environment variable is no longerrequired for V-Series systems with native disk shelves that use Multipath Storage.

If you revert from Data ONTAP 8.1 to an earlier release, Data ONTAP automatically configures thisenvironment variable for you. It is required in releases prior to 8.1.


New and changed features in the Data ONTAP 8.0release family

You can find information about the new and changed features in the Data ONTAP 8.0 release family.If you are upgrading to Data ONTAP 8.1 or later from a 7.3.x release, these changes will apply toyour system in addition to those introduced in the 8.1 release family.

Note: Some new and changed features in this release might also be introduced in a maintenancerelease of an earlier 7G release family. Before upgrading, be sure to consult with your NetApprepresentative about new Data ONTAP functionality to determine the best solution for yourbusiness needs.

Data ONTAP 8.0 and later Data ONTAP 8.0.x releases provide a new aggregate type, 64-bitaggregates, with a larger maximum aggregate and FlexVol sizes, as well as improvedperformance, resiliency, and management capabilities for storage resources.

For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 52.

Data ONTAP 8.0 and later Data ONTAP 8.0.x releases also provide new platform and hardwaresupport as described in New platform and hardware support on page 23,additional managementcapabilities such as SSL security improvements, additional capabilities using iSCSI and FCprotocols for NetApp SAN environments, and enhanced data protection technologies such asSnapMirror and SnapVault.

For other information about the changes made in these releases, see New and changed commandsand options in the Data ONTAP 8.0.1 release on page 85.

For a list of bugs fixed in different releases, see Bugs Online on the NetApp Support Site at support.netapp.com/NOW/cgi-bin/bol.

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

For information about the supported systems, see Supported systems on page 98.

Support for 1-TB Flash Cache modulesData ONTAP 8.0.2 and later releases support the 1-TB PCIe-attached Flash Cache module that usesFlash technology.

The addition of Flash Cache optimizes the performance of random read-intensive workloads such asfile services, messaging, virtual infrastructure, and OLTP databases without using more high-performance disk drives.



For the Flash Cache technical specifications, including supported platforms, see Flash CacheTechnical Specifications at www.netapp.com/us/products/storage-systems/flash-cache/flash-cache-tech-specs.html.

Support for the 32xx platformData ONTAP 8.0.1 and later Data ONTAP releases support the 32xx platform.

For the 32xx technical specifications, see FAS3200 Series Technical Specifications at www.netapp.com/us/products/storage-systems/fas3200/fas3200-tech-specs.html.

Support for the 62xx platformData ONTAP 8.0.1 and later Data ONTAP releases support the 62xx platform.

For the 62xx technical specifications, see FAS6200 Series Technical Specifications at www.netapp.com/us/products/storage-systems/fas6200/fas6200-tech-specs.html.

Support for 512-GB and 256-GB Performance Acceleration Module (PAM II)Data ONTAP 8.0.1 operating in 7-Mode and later Data ONTAP 8.0.x releases operating in 7-Modesupport the PCIe-attached Performance Acceleration Module (PAM II, also known as Flash Cachemodule) that uses Flash technology.

The addition of PAM II optimizes the performance of random read-intensive workloads such as fileservices, messaging, virtual infrastructure, and OLTP databases without using more high-performance disk drives.

For the Flash Cache technical specifications, including supported platforms, see Flash CacheTechnical Specifications at www.netapp.com/us/products/storage-systems/flash-cache/flash-cache-tech-specs.html.

Support for SSDsData ONTAP 8.0.1 7-Mode and later Data ONTAP 8.0.x releases support solid-state disks (SSDs).SSDs are flash memory-based storage devices that provide better overall performance than hard diskdrives, or HDDs, which are mechanical devices using rotating media.

For more information about SSDs, see the Data ONTAP Storage Management Guide for 7-Mode.For information about which storage system models support SSDs, see the Hardware Universe(formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml.

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

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


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


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

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





Support for 2-TB SATA disksIn Data ONTAP 8.0 and later releases, 2-TB SATA disks are supported for both the SAS and FCdisk connection types. With these larger disks and 64-bit aggregates, you can create larger aggregatesbefore being affected by spindle and aggregate size limits.

For more information about 64-bit aggregates, see Support for 64-bit aggregates on page 52.

Support for SA320 platformData ONTAP 8.0.1 7-Mode and later releases support the SA320 platform. SA systems are storagesystems capable of storing only FlexCache volumes.

The SA320 supports the following features:

• One controller and IO expansion module in a chassis• Four full-length PCIe slots and one 3/4-length PCIe slot• Two Gigabit Ethernet ports• Two HA ports• Two 3-Gb or 6-Gb SAS ports• Two 4-Gb Fibre Channel ports• One private management (ACP) port• One remote management port• Service Processor• 16 GB main memory• Support for DS14mk2, DS14mk2 AT, DS14mk4, DS4243, and DS2246 disk shelves

Changes to disk shelf supportThis Data ONTAP release includes a number of new features and enhancements to disk shelfsupport.

Support for DS2246 disk shelvesData ONTAP 8.0P1 and later releases, except 2040 storage systems, and Data ONTAP 8.0.1 or latersupport DS2246 disk shelves. DS2246 disk shelves contain external SAS disk drives and 6-Gb I/Omodules.

For more information about which disks and disk shelves are supported with your storage systemmodel, see the Hardware Universe (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml. For more informationabout DS2246 disk shelves, see the DS4243, DS2246, DS4486, and DS4246 Disk Shelf Installationand Service Guide.



Support for DS4243 disk shelvesData ONTAP 8.0.2P3 and later Data ONTAP 8.0.x releases, and Data ONTAP 7.3.6 and later DataONTAP 7.3.x releases, support DS4243 disk shelves.

For the DS4243 technical specifications, including all supported Data ONTAP versions, disk drives,and platforms, see Disk shelves for FAS and V-Series systems at www.netapp.com/us/products/storage-systems/disk-shelves-and-storage-media/disk-shelves-tech-specs.html.

For information about installing and cabling the DS4243 disk shelf, see the DS4243, DS2246,DS4486, and DS4246 Disk Shelf Installation and Service Guide on the NetApp Support Site at support.netapp.com.

Manageability enhancementsYou can find information about the new and changed manageability capabilities.

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

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

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

SecureAdmin is set up automatically on systems shipped with Data ONTAP 8.0 or later. For thesesystems, the following are the default security settings:

• Secure protocols (including SSH, SSL, and HTTPS) are enabled by default.• Nonsecure protocols (including RSH, Telnet, FTP, and HTTP) are disabled by default.

On systems shipped with Data ONTAP 8.0 or later, the following are the default option settings forSSH and SSL:

• options ssh.enable on• options ssh2.enable on• options ssh1.enable off• options ssh.passwd_auth.enable on• options ssh.pubkey_auth.enable on• options httpd.admin.ssl.enable on





Also on systems shipped with Data ONTAP 8.0 or later, the following are the default option settingsfor the nonsecure protocols:

• options ftpd.enable off• options httpd.admin.enable off• options httpd.enable off• options rsh.enable off• options telnet.distinct.enable on• options telnet.enable off

These default settings apply only to systems shipped with Data ONTAP 8.0 or later. For systemsupgraded from a version earlier than Data ONTAP 8.0, the above default settings do not apply.Instead, for those upgraded systems, the settings remain unchanged after the upgrade. Also, if youmake security setting modifications after upgrading to Data ONTAP 8.0 or later, the modificationsare preserved even if the system reverts back to the previous Data ONTAP version.

For more information about the default security settings, see the Data ONTAP SystemAdministration Guide for 7-Mode.

Requirement to set root account passwordDuring the initial setup of a storage system shipped with Data ONTAP 8.0 or later, you are promptedto 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):

• The password must be at least eight characters long.• The password must contain at least one number.• The password must contain at least two alphabetic characters.• 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 to set a password for theroot account.

For more information about setting up the storage system, see the Data ONTAP Software SetupGuide for 7-Mode.

Uses of the systemshell and the diagnostic accountA diagnostic account, named diag, is provided with your storage system running Data ONTAP 8.0 orlater. You can use the diag account to perform troubleshooting tasks in the systemshell. The diagaccount and the systemshell are intended only for low-level diagnostic purposes and should be usedonly with guidance from technical support.

The diag account is the only account that can be used to access the systemshell, through the advancedcommand systemshell. The diag account is disabled by default. You must enable the account and


set up its password before using it. Neither the diag account nor the systemshell is intended forgeneral administrative purposes.

Boot menu enhancements and changesStarting with Data ONTAP 8.0, the boot menu includes menu options that allow you to restore theconfiguration information from the root volume to the boot device, to install new software, or toreboot the storage system.

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

For information about the boot menu, see the na_floppyboot(1) man page and the Data ONTAPSystem Administration Guide for 7-Mode.

Supported OpenSSH client versionsData ONTAP 8.0.2 7-Mode and later releases support OpenSSH client version 4.4p1 only. Toenhance security, OpenSSH client version 3.8p1 is no longer supported because it does not containthe latest security fix.

Root aggregate Snapshot reserve values reducedThe root aggregate and root volume Snapshot reserve values for new storage systems have beenreduced starting with Data ONTAP 8.0.1.

To increase the amount of usable space on the storage system while still retaining all the benefits ofvolume Snapshot copies, NetApp ships all new systems running Data ONTAP 8.0.1 or later with thefollowing new Snapshot reserve values:

• Snapshot reserve for the root aggregate is set to 0%.The previous value was 5%.

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

Attention: If you later configure MetroCluster, or use RAID SyncMirror or the aggregate copycapability on the root aggregate, the root aggregate Snapshot reserve must be increased to 5% byusing the snap reserve command.

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

Storage resource management enhancementsThis Data ONTAP release provides improved performance, resiliency, and management capabilitiesfor storage resources.


Support for 64-bit aggregatesIn Data ONTAP 8.0 7-Mode and later releases, Data ONTAP supports a new type of aggregate, the64-bit aggregate. 64-bit aggregates have a larger maximum size than 32-bit aggregates. In addition,volumes contained by 64-bit aggregates have a larger maximum size than volumes contained by 32-bit aggregates.

The maximum size of a 64-bit aggregate and the volumes it contains depends on the model of yourstorage system. To determine the maximum 64-bit aggregate size for your storage system model, seethe Hardware Universe. The maximum size of a volume contained by a 64-bit aggregate correspondsto the maximum size of its containing aggregate.

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

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

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

After you enable data compression on a FlexVol volume, all subsequent writes to the volume arecompressed inline. However, existing data remains uncompressed. You can use the data compressionscanner to compress the existing data.









File space utilization reportThe file space utilization report enables you to see the files and the amount of space that they occupyin a deduplicated volume. You can choose to either move or delete the files to reclaim the space.

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

Note: Total blocks refer to the number of blocks in a file, including blocks that are required forstoring 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 of Data ONTAP, you canincrease the deduplicated volume size up to 16 TB for all platform models that support Data ONTAP8.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 a maximum of 500FlexClone file or FlexClone LUN operations on a storage system.

For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP StorageManagement 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 FlexClone file and FlexCloneLUN commands are available in the default vFiler context.

You can use the FlexClone files and FlexClone LUNs feature to create writable, space-efficientclones of parent files and parent LUNs within a vFiler unit. Storage owned by a vFiler unit cannot beaccessed or discovered from other vFiler units by using the FlexClone file or FlexClone LUNcommands.

For more information about FlexClone files and FlexClone LUNs, see the Data ONTAP StorageManagement Guide for 7-Mode.


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

Ability to decrease maxfilesStarting in Data ONTAP 8.0, you can decrease the value of the maxfiles parameter for a volume, aslong as you do not decrease it below the current number of files stored in the volume.

In previous versions of Data ONTAP, you could increase the value of the maxfiles parameter, but notdecrease it.

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

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

Networking and security protocol enhancementsData ONTAP 8.1 and later releases include a number of new features and networking and securityprotocol enhancements.

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

Data ONTAP 8.0.2 introduces a new option interface.blocked.mgmt_data_traffic tocontrol the blocking of data transfer on the e0M interface. New systems that are shipped with DataONTAP 8.0.2 and later releases have the default value of this option set to on, which prevents datatransfer on the e0M interface. Systems upgraded to Data ONTAP 8.0.2 and later releases have thedefault value of the option set to off, which allows data transfer on the e0M interface.

Note: Data transfers that use the iSCSI protocol are always blocked on systems upgraded to DataONTAP 8.0 and later. The transfers are not affected by theinterface.blocked.mgmt_data_traffic option setting.


The e0M port is a low-bandwidth interface that should be used only for management traffic that usesSSH and other management protocols. Configuring e0M to serve data traffic can cause performancedegradation and routing problems. Therefore, e0M should be configured on a dedicated managementLAN or it should be configured down. If an e0M interface is serving management traffic, it should bepartnered with another e0M interface.

It is a best practice to set the interface.blocked.mgmt_data_traffic option to on, and to usethe e0M interface only for management traffic. For more information about the e0M interface, seethe Data ONTAP System Administration Guide for 7-Mode and the Data ONTAP Software SetupGuide for 7-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 later releases of the 7.xrelease family, and in Data ONTAP 8.0.1 and later. CDP enables you to automatically discover andview information about directly connected CDP-enabled devices in a network.

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

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

The port-based load-balancing method uses a fast hashing algorithm on the source and destination IPaddresses along with the transport layer (TCP or UDP) port number.

For more information about port-based load balancing, see the Data ONTAP Network ManagementGuide for 7-Mode.

TSO in NICsTCP segmentation offload (TSO) is a hardware feature supported on NICs to increase the host CPU'sefficiency.

Starting in Data ONTAP 8.0.1 and later, the network interface cards that support TSO are as follows:

• Dual 10G Ethernet Controller T320E-SFP+ and T320-XFP• 10 Gigabit Ethernet Controller IX1-SFP+

Starting in Data ONTAP 8.0.2, the following network interface card also supports TSO:

• Dual 10G Ethernet Controller CNA-SFP+

For more information about TSO and the statistics displayed by the NICs, see the Data ONTAPNetwork 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 file have low and high32-bit values. In Data ONTAP 8.0 7-Mode and later, these OIDs are replaced with 64-bit values. Youshould use SNMPv2 or SNMPv3 to query your storage system by using the 64-bit OIDs.

For example, the miscHighNfsOps and miscLowNfsOps OIDs have been replaced with the 64-bitOID misc64NfsOps. In the netapp.mib file, miscHighNfsOps and miscLowNfsOps are markedas deprecated.

For more information, see the latest netapp.mib file on the NetApp Support Site at support.netapp.com.

Configuration for receiving untagged traffic on VLAN tagged interfacesIn Data ONTAP 8.0 7-Mode and later, you can configure an IP address for a network interface withVLANs. Any untagged traffic goes to the base interface, and the tagged traffic goes to the respectiveVLAN.

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

For information about reverting with a configuration for receiving tagged and untagged frames on thesame network interface, see the Data ONTAP Upgrade Guide for 7-Mode.

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

You can use the ifgrp command to create and configure interface groups. For more informationabout interface groups and the ifgrp command, see the Data ONTAP Network Management Guidefor 7-Mode.

File access protocol enhancementsThis Data ONTAP release includes a number of new features and enhancements for file access andprotocols management. This section provides an overview of these features and enhancements.

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



Support for multiple open instances of the SMB named pipe on an FPolicyserver

In Data ONTAP 8.0 7-Mode, you can enable multiple open instances of the SMB named pipe on anFPolicy server by using the fpolicy.multiple_pipes option.


Block protocol enhancementsThis Data ONTAP release includes a number of new features and block protocol enhancements.

For more information about these features, see the Data ONTAP SAN Administration Guide for 7-Mode.

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

RADIUS still uses CHAP to authenticate iSCSI initiators, but it enables you to manage theauthentication process from a central RADIUS server, rather than manage them manually on eachstorage system. In larger SAN environments, this can greatly simplify iSCSI initiator managementand provide added security.

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

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

Support for NetApp DataMotion for VolumesData ONTAP 8.0.1 7-Mode or later supports NetApp DataMotion for Volumes, which enables you tonondisruptively move a volume from one aggregate to another within the same controller to satisfyservice-level agreements and capacity utilization and improved performance. In a SAN environment,FlexVol volumes and the LUNs in the volumes are moved nondisruptively from one aggregate toanother.

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

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


VMware VAAI features for ESX hosts supportData ONTAP 8.0.1 and later supports certain VMware vStorage APIs for Array Integration (VAAI)features when the ESX host is running ESX 4.1 or later. These features help offload operations fromthe ESX host to the storage system and increase the network throughput.

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

For more information about the VMware VAAI features for ESX hosts, see Data ONTAP SANAdministration Guide for 7-Mode.

igroup scalability limitsData ONTAP 8.0.1 introduces support to expand the host side scalability by expanding the number ofigroups supported on FAS3xxx and FAS6xxx systems from 512 per controller to 1024 per controller.

Data protection enhancementsData ONTAP 8.1.1includes a number of new features and data protection enhancements.

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

SnapVault update schedules for volume SnapMirror destination backupsWhen backing up a volume SnapMirror destination using SnapVault in Data ONTAP 8.0.2, thesnapvault.snapshot_for_dr_backup option allows you to choose the SnapVault behavior forupdating the destination system.

You can set the following values for the snapvault.snapshot_for_dr_backup option:

• named_snapshot_only

Schedules the SnapVault updates from the most recent Snapshot copy with the scheduled basename for scheduled backup.

• named_snapshot_preferred

Schedules the SnapVault updates from the most recent Snapshot copy created by volumeSnapMirror if the scheduled Snapshot copy is not available.

• vsm_base_only

Schedules the SnapVault updates from the most recent Snapshot copy created by volumeSnapMirror. This is the default value.

In Data ONTAP 8.0 and Data ONTAP 8.0.1 7-Mode, SnapVault uses a named Snapshot copy andnot the Snapshot copy created by volume SnapMirror to update the destination system.


Support for 840 disk drives on fabric-attached MetroCluster configurationIn Data ONTAP 7.3.5 and later in the 7.x release family, and Data ONTAP 8.0.1 and later in the 8.xrelease family, fabric-attached MetroCluster configurations can support up to 840 disk drives.

For more information, see the MetroCluster Compatibility Matrix available on the NetApp SupportSite at support.netapp.com.

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

When enabled, out-of-order frame delivery for SnapMirror over Fibre Channel eliminates therequirement to deliver all the frames in the same sequence in which the frames were transmitted. Thisfeature ensures uninterrupted SnapMirror transfers regardless of the order in which the frames aredelivered.

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

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

The SnapMirror relationship between two FlexClone volumes that have a common base Snapshotcopy can be established without transferring the common Snapshot data again to the destinationsystem.

For more information about SnapMirror relationship between two FlexClone volumes, see DataONTAP Data Protection Online Backup and Recovery Guide for 7-Mode.

Support for SnapMirror network compressionData ONTAP 7.3.2 and later releases of the 7.x release family, and Data ONTAP 8.0.1 and laterreleases of the 8.x release family support SnapMirror network compression. This feature is supportedonly for asynchronous volume SnapMirror.

Note: The SnapMirror destination system should be using a Data ONTAP release that supportsSnapMirror network compression.

SnapMirror network compression compresses the data stream on the source system, transfers thecompressed data stream over the network, and uncompresses the data stream on the destinationsystem before writing it to disk. It helps in optimizing network bandwidth utilization betweenSnapMirror source and destination systems. This feature can be especially useful for connections thathave relatively low bandwidth, such as WAN connections.

For more information about SnapMirror network compression, see the Data ONTAP Data ProtectionOnline Backup and Recovery Guide for 7-Mode.



Support for designated range of ports for NDMP data connectionsData ONTAP 8.0.1 and later support designated range of ports that can be used for NDMP dataconnections in response to NDMP_DATA_LISTEN and NDMP_MOVER_LISTEN operations.Therefore, you can perform data migration by using the ndmpcopy command and three-way tapebackups even in environments where the source and destination networks are separated by a firewall.









If volumes with deduplication exceed the maximum supported sizeVolumes continue to be online when they exceed the maximum supported size. For more informationabout the maximum volume size allowed for different storage systems, with and withoutdeduplication, see the Data ONTAP 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 NearStore personality license to usededuplication.

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

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

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

Snapshot copy schedulesScheduled Snapshot copy creation might fail for various reasons, such as a volume being offline.When the volume becomes online again, Data ONTAP detects the scheduled Snapshot copy creationthat has failed and automatically creates a Snapshot copy for that schedule. This feature is availablein Data ONTAP 8.0 7-Mode and later releases in the Data ONTAP 8.0 7-Mode release family.

For more information about this feature, see the Data ONTAP Data Protection Online Backup andRecovery Guide for 7-Mode.

SnapMirror support for 64-bit volumesData ONTAP 8.0 and later releases support 64-bit volumes in addition to 32-bit volumes. SnapMirrorsupports replication between 64-bit volumes and also between 32-bit volumes. However, in DataONTAP 8.0, there are certain considerations when replicating volumes and qtrees using SnapMirror.

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

When replicating qtrees by using SnapMirror, the source and destination volumes can be of differenttypes. Either the source and or destination volume can be 64-bit or 32-bit.


SnapVault support for 64-bit volumesData ONTAP 8.0 and later releases support 64-bit volumes. SnapVault supports replication between64-bit volumes, in addition to supporting replication between 32-bit volumes. When replicatingqtrees by using SnapVault, the source and destination volumes can be of different types. The sourceand destination volumes can be either 64-bit or 32-bit.

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

Changes to the Data ONTAP and V-Series librariesThe Data ONTAP Software Setup Guide for 7-Mode now provides information for basic setup of allsystems that run Data ONTAP, including a V-Series system. Data ONTAP guides and V-Seriesguides are now available on the same Documentation Web page.

Starting in Data ONTAP 7.3.2, much of the information about using Data ONTAP features with V-Series systems was integrated into the general Data ONTAP guides. This effort was continued inData ONTAP with the integration of V-Series system setup instructions into the Data ONTAPSoftware Setup Guide for 7-Mode. As of Data ONTAP 8.0 7-Mode, there is no longer a separatesetup guide for V-Series.

V-Series documents now focus primarily on information about implementation with the back-endstorage arrays.

The Data ONTAP 8.0 7-Mode Documentation page now provides both the general Data ONTAP 8.07-Mode guides and the V-Series specific guides on the same Documentation web page; there is nolonger a separate Documentation page for the V-Series guides. You can access the integrated DataONTAP 8.0 7-Mode Documentation page from the Data ONTAP Information Library page.

Related information

Data ONTAP Information Library page: support.netapp.com/NOW/knowledge/docs/ontap/ontap_index.shtml




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

You need to know information about the commands, options, and configuration files that have beenchanged in or added to the Data ONTAP 8.1 release family.

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

New commands in the Data ONTAP 8.1 release familyMany new commands have been added to this release.

For each command family and each command, the following table gives this information:

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

Command Purpose Documentation Release added

autosupport

destinations show

Views a summary of alladdresses and URLs thatreceive AutoSupportmessages.

Data ONTAP SystemAdministration Guide for7-Mode

autosupport

destinations show

man page

8.1

autosupport

history

retransmit

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


autosupport history

retransmit man page

8.1

autosupport

history show

Displays information aboutone or more of the 50 mostrecent AutoSupportmessages.


autosupport history

show man page

8.1

63


autosupport

manifest show

Views the information in theAutoSupport messages,including the name and sizeof each file collected for themessage along with anyerrors.


autosupport

manifest show manpage

8.1

autosupport

trigger modify

Enables and disablesAutoSupport messages toyour internal supportorganization for individualtrigger events, and specifiesadditional subsystem reportsto include in messages sent inresponse to individual triggerevents.


autosupport trigger

modify man page

8.1

autosupport

trigger show

Displays the system eventsthat can trigger AutoSupportmessages.


autosupport trigger

show man page

8.1

cifs branchcache

hash stat

Displays information aboutBranchCache hash statistics.

Data ONTAP File Accessand ProtocolsManagement Guide for 7-Mode

cifs branchcache

man page

8.1.1

cifs branchcache

set key

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


cifs branchcache

man page

8.1.1

coredump segment

config modify

Configures the automaticsegmenting of core dumpfiles.


8.1.1

coredump segment

config show

Shows the currentconfiguration of automaticcore segmenting.


8.1.1



coredump segment

delete

Deletes a specified coresegment from the system.


8.1.1

coredump segment

delete-all

Deletes all core segmentsfrom the system.


8.1.1

coredump segment

show

Displays information aboutthe core segments on thesystem.


8.1.1

coredump segment

start

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

8.1.1

coredump segment

status

Displays the status of a coresegmenting job.


8.1.1

coredump segment

stop

Cancels a core segmentingjob.


8.1.1

disk encrypt

destroy

Cryptographically destroysself-encrypting disks on aStorage Encryption enabledsystem.

Data ONTAP StorageManagement Guide for 7-Mode

8.1

disk encrypt lock Locks self-encrypting diskson a Storage Encryptionenabled system.


8.1

disk encrypt

rekey

Rekeys self-encrypting diskson a Storage Encryptionenabled system.


8.1

disk encrypt

sanitize

Cryptographically erases self-encrypting disks on a StorageEncryption enabled system.


8.1

disk encrypt show Displays self-encryptingdisks on a Storage Encryptionenabled system.


8.1

key_manager add Adds key managementservers to the storage system.


8.1

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


key_manager query Displays key IDs stored onthe key 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 SoftwareSetup Guide 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.


nfs man page

8.1

sftp stat Displays SFTP statistics. Data ONTAP File Accessand ProtocolsManagement Guide for 7-Mode

sftp man page

8.1

storage shelf

identify

Causes the specified diskshelf to flash its LEDs to helpyou locate the shelf.

na_storage(1) man page 8.1.1

storage show

bridge

Displays information aboutFC-to-SAS bridges.


8.1



system health

alert definition

show

Displays information aboutthe alerts that a healthmonitor can potentiallygenerate.


system health alert

definition show manpage

8.1

system health

alert delete

Deletes an alert that was notautomatically cleared


system health alert

delete man page

8.1

system health

alert modify

Suppresses or acknowledgesan alert.


system health alert

modify man page

8.1

system health

alert show

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


system health alert

show man page

8.1

system health

autosupport

trigger history

show

Displays information aboutthe AutoSupport messagesthat alerts triggered within thelast week—for example, todetermine whether an alerttriggered an AutoSupportmessage.


system health

autosupport trigger

history show manpage

8.1

system health

config show

Displays information abouthealth monitors, such as theirnodes, names, subsystems,and status.


system health

config show man page

8.1



system health

node-connectivity

adapter show

Displays the status ofadapters along with otherinformation, such as theowner node, whether they areused and enabled, and thenumber of shelves attached.


system health node-

connectivity

adapter show manpage

8.1

system health

node-connectivity

disk show

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


system health node-

connectivity disk

show man page

8.1

system health

node-connectivity

shelf show

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


system health node-

connectivity shelf

show man page

8.1

system health

policy definition

modify

Enables or disables the policythat controls whether aspecific resource state raises aspecific alert.


system health

policy definition

modify man page

8.1

system health

policy definition

show

Displays information abouthealth monitor policies,which determine when alertsare raised.


system health

policy definition

show man page

8.1

system health

status show

Displays the status of theentire system.


system health

status show man page

8.1



snaplock clock

initialize

Initializes the systemComplianceClock.

Data ONTAP Archiveand ComplianceManagement Guide for 7-Mode

8.1

snaplock clock

status

Displays the systemComplianceClock andvolume ComplianceClocktime.

Data ONTAP Archiveand ComplianceManagement Guide for 7-Mode

8.1

Changed commands in the Data ONTAP 8.1 release familyA number of commands have been changed in this release.

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

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

Command Change Documentation Releasecommandchanged in

aggr add The 64bit-upgrade option hasbeen added. This option enablesthe administrator to upgrade anaggregate from 32-bit to 64-bitformat by adding enough storageto exceed the 16-TB maximum32-bit aggregate size.

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

8.1

aggr create The -c option has been added.This option enables theadministrator to select disks orarray LUNs with a specificchecksum type when creating anaggregate.

na_aggr(1) man page 8.1



aggr options The free_space_reallocoption has been added. Thisoption enables or disables freespace reallocation, whichimproves write performance byoptimizing the free space withinan aggregate.

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

8.1.1

aggr options The hybrid_enabled optionhas been added. This optiondetermines whether an aggregatecan be converted to a Flash Pool

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

8.1

aggr options The hybrid_enabled optionhas been added. This optiondetermines whether an aggregatecan be converted to a Flash Pool.

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

aggr status The -R option has been added.This option displays the serialnumber and other informationused by technical support for thedisks in an aggregate.


aggr status For the r option, the number ofblocks for failed disks is nowdisplayed as "-".


aggr status The -s option now displays thechecksum types that spares canbe used with.

na_aggr(1) man page 8.1.1

cifs shares The -branchcache option hasbeen added to the cifs shares-add and cifs shares -change commands. This optionenables BranchCache caching forthe share.

na_cifs_shares(1) manpage and Data ONTAPFile Access andProtocols ManagementGuide for 7-Mode

8.1.1

df The hybrid option has beenadded. Used with the A option, itdisplays the size of the SSD tierfor a Flash Pool.

na_df(1) man page 8.1.1



disk assign The -shelf option has beenadded. This option enables theadministrator to assign allunassigned disks on a specificshelf to the specified controller.

na_disk(1) man page 8.1

flexcache eject The ‑i option has been added.This option enables theadmininstrator to specify theinode rather than the file name(for example, flexcacheeject ‑i /vol/foo/inode:24529). The ‑i option can beuseful if the file name isunknown or the path to the filename cannot be resolved.

na_flexcache (1) manpage

8.1

flexcache fstat The ‑i option has been added.This option enables theadministrator to specify theinode rather than the file name(for example, flexcachefstat ‑i /vol/foo/inode:24529). The ‑i option can beuseful if the file name isunknown or the path to the filename cannot be resolved.

na_flexcache (1) manpage

8.1

lock status The output of this command nowshows durable lock states forSMB 2.x and lease oplockinformation for SMB 2.1 locks.

na_lock(1) man pageand Data ONTAP FileAccess and ProtocolsManagement Guide for7-Mode

8.1.1

qtree oplock Enables or disables both leaseoplocks and traditional oplocks.Lease oplocks are available ifSMB 2.1 is enabled.

na_qtree(1) man pageand Data ONTAP FileAccess and ProtocolsManagement Guide for7-Mode

8.1.1



sis config The manual value for the -soption has been added. Thisoption can be used only onSnapVault destination volumesthat have qtrees. This optionensures that the deduplicationoperation is not triggeredautomatically after every updateto the destination volumes.

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

8.1

sis config The -I option has been added.This option enables theadministrator to enable or disablein-line compression.

na_sis(1) man page 8.1

sis config The -C option has been added.This option enables theadministrator to enable or disablepost-process compression.


sis start The -p option has been added.This option enables thededuplication operation to usethe previous check point.


8.1

sis start The -q option has been added.This option enables theadministrator to queue thededuplication operations.


sis status The -l option has beenmodified. The output of the sisstatus -l command nowincludes the status of in-linecompression and post-processcompression for a volume.


8.1

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

na_snap(1) man pageand Data ONTAP DataProtection OnlineBackup and RecoveryGuide for 7-Mode

8.1



snapmirror

resync

The -c has been added. Thisoption creates a Snapshot copy(with the name snapshot_name)on the destination after theresynchronization transfer iscomplete. This is done to ensurethat the transfer does notcoincide with any ongoingupdates.

Note: This option is valid onlyfor a qtree.

na_snapmirror(1) manpage and Data ONTAPData Protection OnlineBackup and RecoveryGuide for 7-Mode

8.1

storage show

disk

The dongle revision has beenadded to the command output.

8.1.1

storage show

disk

The serial number of the carrierhas been added to the output fordisks in multi-disk carrier diskshelves.

8.1.1

sysconfig The -a option now includesinformation about any FC-to-SAS bridges present.

The -P option enumerates thePCI hierarchy of the system,enabling the support and debugof errors from the PCIsubsystem. The -P option is notsupported on all platforms.

na_sysconfig (1) manpage

8.1

sysconfig The –p option displaysinformation about the physicalhost machine and its mapping tothe virtual machine.

na_sysconfig (1) manpage

8.1.1



vol modify The space-mgmt-try-firstoption has been added. Thisoption enables the administratorto choose between theautogrow functionality andautodelete snapshot as thefirst choice for providing morefree space for a volume.

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

8.1

vol options Thesnaplock_autocommit_peri

od option is added to set theautocommit period.

Data ONTAP Archiveand ComplianceManagement Guide for7-Mode

8.1

vol status The output of this command nowincludes the format (32-bit or 64-bit) of the volume.

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

8.1

vol status With the -v option specified, theoutput of this command nowincludes the read and writecaching eligibility for volumesassociated with a Flash Pool.

Data ONTAP StorageManagement Guide for7-Mode

8.1.1

Replaced or removed commands in the Data ONTAP 8.1release family

You need to know which commands have been replaced or removed.

Support for the following commands will be discontinued in a future version of Data ONTAP. Toperform the equivalent operations, you use the aggr command.

• vol add

• vol media_scrub

• vol migrate

• vol mirror

• vol scrub

• vol split

• vol verify

• vol wafliron


The following commands are removed in Data ONTAP 8.1:

• vol compress

• date -c

• date -c initialize

• filestats

• ups

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

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

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

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

Option Purpose Defaultvalue

Releaseadded

autosupport.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) transfersof AutoSupportmessages.

5 MB 8.1

autosupport.payload_format Specifies the file formatof the compressed filethat containsAutoSupport data.

7z 8.1



Releaseadded

autosupport.support.put_url Indicates whereAutoSupport messagesfor NetApp technicalsupport are sent ifautosupport.suppor

t.transport is httpor https and the serverreceiving the messagesupports HTTP PUTrequests. Read only.

support.netapp.com/put/AsupPut

8.1

autosupport.validate_digital_

certificate

Determines whether thestorage system validatesthe remote digitalcertificates that itreceives. Applies onlywhenautosupport.suppor

t.transport is set tohttps.

on 8.1

cifs.smb2.client.enable Enables or disables thestorage system's SMB2.0 client 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 SMB2.0 messages.

off 8.1

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

off 8.1.1



Releaseadded

cifs.smb2_1.branch_cache.hash_

time_out

Sets the time (inseconds) that an unusedBranchCache hash for afile can be kept in thestorage system'smemory.

3600s 8.1.1

cifs.W2K_password_change Enables or disablesautomatic storage systemdomain accountpassword change

off 8.1.1

cifs.W2K_password_change_interval Sets the time duration (inweeks) after which DataONTAP triggers adomain passwordchange. Applies onlywhencifs.W2K_password_

change is set to on.

4w 8.1.1

cifs.W2K_password_change_within Sets the time duration (inhours) within which theData ONTAP attempts adomain passwordchange. Applies onlywhencifs.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 insecure mode.

on 8.1

ftpd.explicit.enable Enables or disablesexplicit FTPS.

off 8.1



Releaseadded

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 Fibre Channel onFAS2040 systems. Forall other systems, youmust purchase a licenseto use this feature andadminister it by usingthe license commands.

off 8.1

licensed_feature.flexcache_nfs.

enable

Enables or disables theuse of FlexCache withNFS clients on allsystems.

off 8.1



Releaseadded

licensed_feature.iscsi.enable Enables or disables theuse of iSCSI onFAS2040, 30xx, 31xx,and 60xx systems. Forall other systems, youmust purchase a licenseto use this protocol andadminister it by usingthe license commands.

off 8.1

licensed_feature.multistore.

enable

Enables or disablesMultiStore on FAS2040,32xx, 62xx, andFAS2240 systems. Forall other systems, youmust purchase a licenseto use this feature andadminister it by usingthe license 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 CIFSclient with DENY writepermissions.

on 8.1

nfs.mount_rootonly Controls NFS requestsfrom non-reserved ports

on 8.1.1

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



Releaseadded

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 whichRLM SSH idleconnections aredisconnected ifrlm.autologout.ena

ble is on.

60 8.1.1

rlm.ssh.access Restricts SSH access tothe RLM.

* 8.1.1

sftp.auth_style Specifies the SFTPauthentication style.

mixed 8.1

sftp.bypass_traverse_checking Enables or disablesSFTP bypass traversechecking.

off 8.1

sftp.dir_override Specifies the SFTPoverride path for userhome directories.

"" (null) 8.1

sftp.dir_restriction Enables or disablesSFTP user homedirectory restrictions.

off 8.1

sftp.enable Enables or disablesSFTP.

off 8.1



Releaseadded

sftp.idle_timeout Specifies the maximumSFTP connection idletime before termination,in seconds.

900 8.1

sftp.locking Enables or disablesSFTP file locking.

none 8.1

sftp.log_enable Enables or disablesSFTP event logging.

on 8.1

sftp.log_filesize Specifies the maximumsize of the SFTP logfiles.

512K 8.1

sftp.log_nfiles Specifies the maximumnumber of SFTP logfiles.

6 8.1

sftp.max_connections Specifies the maximumnumber of SFTPconnections.

15 8.1

sftp.max_connections_threshold Specifies when togenerate a maximumSFTP connectionwarning, in percent.

75 8.1

sftp.override_client_permissions Enables or disablesUNIX permissionsspecified by SFTPclients.

off 8.1

snapmirror.volume.local_nwk_

bypass.enable

Determines whetherlocal SnapMirrortransfer optimization isenabled.

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



Releaseadded

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

le is on.

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 the Data ONTAP 8.1 release familyYou need to know which options have changed or become obsolete.

For each option, the following table gives this information:

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


Option Change Releasechanged

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

8.1



autosupport.local.nht_

data.enable

Removed. 8.1

autosupport.local.

performance_data.enable

Removed. 8.1

autosupport.mailhost,autosupport.proxy, andautosupport.support.url

Support for IPv6 addresses, as well asIPv4 addresses.

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

al, andcifs.W2K_password_change_within

8.1.1



snaplock.autocommit_period This system-level option can be used onlyfor viewing the autocommit time period ofthe SnapLock volumes that wereupgraded. This option is now in read-onlystate.

8.1

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

8.1.1


Summary of new and changed commands andoptions in the Data ONTAP 8.0 release family

You can find information about the commands, options, and configuration files that have beenchanged in or added to the Data ONTAP 8.0 release family. If you are upgrading to Data ONTAP 8.1or later from a 7.3.x release, these changes apply to your system in addition to those introduced in the8.1 release family.

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

New commands in Data ONTAP 8.0 7-Mode release familyYou need to know which new commands have been added in the Data ONTAP 8.0 7-Mode releasefamily.


• The purpose of the command• The location of documentation about the command• The Data ONTAP 8.0 7-Mode release in which the command was introduced

Command Purpose Document Release introduced

acpadmin

configure

Configures the ACPsubsystem.


na_acpadmin(1) manpage

8.0

acpadmin list_all Displays informationabout the ACP(Alternate ControlPath) storagesubsystem.



8.0

cdpd Displays informationabout devices thatadvertise themselvesby using the CDPv1protocol.

Data ONTAP NetworkManagement Guide for7-Mode

8.0.1

85


du Displays the files andamount of space thatthey occupy in adeduplicated volume.


8.0.1

ifgrp Manages interfacegroups on your storagesystem.

This commandreplaces the vifcommand. However,the options remain thesame.

Data ONTAP NetworkManagement Guide for7-Mode

8.0

revert_to Transitions DataONTAP to a release inan earlier releasefamily.

Data ONTAP Upgradeand Revert/DowngradeGuide for 7-Mode

revert_to(1) man page

8.0

smtape abort Aborts a backup orrestore job initiated bythe SMTape engine.

Data ONTAP DataProtection TapeBackup and RecoveryGuide for 7-Mode

na_smtape manpage

8.0

smtape backup Backs up blocks ofdata to tape.


na_smtape manpage

8.0

smtape continue Continues an SMTape-initiated backup orrestore operation afterit has reached the endof current tape and is inthe wait state to writeoutput to or acceptinput from a new tape.


na_smtape manpage

8.0



smtape restore Restores blocks of datafrom tape.


na_smtape manpage

8.0

smtape status Displays the status ofSMTape-initiatedbackup and restoreoperations.


na_smtape manpage

8.0

sp help Displays the DataONTAP sp commandsthat you can enter atthe storage systemprompt.

Data ONTAP SystemAdministration Guidefor 7-Mode

na_sp(1) man page

8.0.1

sp reboot Reboots the SP andcauses the SP toperform a self-test.


na_sp(1) man page

8.0.1

sp setup Initiates the interactiveSP setup script.


na_sp(1) man page

8.0.1

sp status Displays the currentstatus and the networkconfiguration of theSP.


na_sp(1) man page

8.0.1

sp test

autosupport

Sends a test email to allrecipients specifiedwith theautosupport.to

option.


na_sp(1) man page

8.0.1

Summary of new and changed commands and options in the Data ONTAP 8.0 release family | 87


sp test snmp Performs SNMP teston the SP, forcing theSP to send a testSNMP trap to all traphosts specified in thesnmp traphost

command.


na_sp(1) man page

8.0.1

sp update Updates the SPfirmware.


na_sp(1) man page

8.0.1

storage array

modify

Modifies attributes ofarray profile records.

na_storage(1) manpage

8.0

storage array

purge-database

Removes all recordsfrom the controller’sarray profile database.


8.0

storage array

remove

Removes records forthe specified arrayfrom the controller’sarray profile database.


8.0

storage array

remove-port

Removes portsassociated with anarray profile.


8.0

storage array

show

Lists all array profilerecords known to thecontroller.


8.0

storage array

show-config

Provides a summary ofthe connectivity toSAN-attached arraysconnected to the V-Series system FCinitiator ports.

V-Series InstallationRequirements andReference Guide


8.0

storage array

show-luns array-

name

Lists all array LUNsexported from a namedstorage array.


8.0



storage array

show-ports

Lists all target ports forall storage arraysknown to the V-Seriessystem.


8.0

storage show acp Displays informationabout the ACP(Alternate ControlPath) storagesubsystem.



8.0

Changed commands in the Data ONTAP 8.0 7-Mode releasefamily

This table lists the commands that have been changed in the Data ONTAP 8.0 7-Mode releasefamily.


• Change in the command• Location of documentation about the feature• The Data ONTAP 8.0 7-Mode release in which the change was introduced

Command Change Documentation Release commandchanged in

aggr create The -B option hasbeen added. Thisoption is used to createa 64-bit aggregate.

na_aggr(1) man page


8.0

df The -x option hasbeen added. Thisoption suppresses thedisplay ofthe .snapshot lines.

na_df(1) man page 8.0



disk assign You can no longer usethis command tochange the ownershipof a disk or array LUNthat is already ownedunless you are runningthe command on thesystem that owns thedisk already.

na_disk(1) man page 8.0

environment shelf The ComplexProgrammable LogicDevice (CPLD)version has been addedto the output.

na_environment(1) manpage

8.0

flexcache fstat The -inode-fileoption has been added.This option displaysthe number of blocksused by the FlexCachevolume's inode file.

na_flexcache(1) man page 8.0.3

ifgrp create

multi

The port value (port-based load-balancing)for the -b option hasbeen added.

Data ONTAP NetworkManagement Guide for 7-Mode

8.0.1

software update The -r option, whichsuppresses automaticreboot, is now thedefault. To request anautomatic reboot, younow must specify the -R option.

na_software(1) man page


8.0.1

storage show acp A column for Moduletype has been added tothe output. This showsthe type of the I/Omodule.




storage show

expander

The systeminterconnect link (SIL)ports (the last fourrows of output) arenow shown as [SIL0]through [SIL3].Previously they wereshown as [DIS0]through [DIS3].

na_storage(1) man page 8.0

storage show

expander

The DS4243 disk shelfports are now listed as[SQR0]-[SQR3] forthe square ports and[CIR4]-[CIR7] for thecircle ports. Previouslythese ports were listedas [IO 0]-[IO7].

na_storage(1) man page 8.0

storage show

fault

You can now specify ashelf name for thiscommand to seeinformation about aspecific shelf.


sysconfig When the -r option isused to display diskinformation for SAS-connected disks, theCHAN (channel)column now displaysthe port as A or B, justas it does for FC-connected disks.Previously, 1 and 2were used.

na_sysconfig(1) man page 8.0

sysconfig When the -a option isused, the outputincludes status andpower information forany IOXM modulespresent.

na_sysconfig(1) man page 8.0.1



sysconfig When the -v option isused, any disabledports show NA for thedata link rate.

na_sysconfig(1) man page 8.0.2

vif This command hasbeen replaced by theifgrp command.

Data ONTAP NetworkManagement Guide for 7-Mode

8.0

vol options The extent optionenables extents but canonly be used onFlexVol volumes.

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

8.0

vol options The read_reallocoption enables readreallocation but canonly be used onFlexVol volumes.

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

8.0

vol status When the -r option isused to display diskinformation for SAS-connected disks, theCHAN (channel)column now displaysthe port as A or B, justas it does for FC-connected disks.Previously, 1 and 2were used.

na_vol(1) man page 8.0

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

You need to know which Data ONTAP 8.0 7-Mode commands have been replaced or removed.

Support for the following commands will be discontinued in a future version of Data ONTAP. Toperform the equivalent operations, you can use the aggr command.

• vol add

• vol media_scrub

• vol migrate


• vol mirror

• vol scrub

• vol split

• vol verify

• vol wafliron

The following commands are removed in Data ONTAP 8.0 7-Mode.

• snapmirror store

• snapmirror use

• snapmirror retrieve

In Data ONTAP 8.0 7-Mode, the vif command has been replaced by the ifgrp command. For moreinformation, see the Data ONTAP Network Management Guide for 7-Mode.

New options in the Data ONTAP 8.0 7-Mode release familyYou need to know which options you can use with the options command.

For each new option that can be used with the options command, the following table gives thisinformation:

• Description of the option's purpose• Default value for the option• Data ONTAP release in which the option was introduced



Releaseadded

autosupport.performance_

data.doit any_stringTriggers a performanceAutoSupport message when anystring is added.

NA 8.0

autosupport.periodic.tx_

window timeSpecifies 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



Releaseadded

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

on ,unlessFC or iSCSIis licensed,in whichcase thedefault isoff

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

Note:Thisoption isnotavailablein DataONTAP8.0.2.

interface.blocked.

mgmt_data_traffic

Blocks or allows data traffic on themanagement interface, e0M.

off forsystemsupgradedfrom anearlierrelease; onfor newsystems

8.0.2

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

all 8.0.1

nfs.always.deny.truncate Controls whether NFSv2 andNFSv3 clients can truncate files inUNIX qtrees that are also openedfrom a CIFS client with DENYwrite permissions.

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



Releaseadded

nfs.v3.snapshot.active.

fsid.enable

Determines whether the FSID ofobjects in a Snapshot copy matchesthe FSID of the active file systemfor NFSv3.

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

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 theSnapshot copy to use for updatingthe destination system whenbacking up a volume SnapMirrordestination using SnapVault.

vsm_base_

only

8.0.2

sp.setup Displays whether the SP has beenconfigured.

(N/A) 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 commandData ONTAP 8.0.3 and later provide a new option -u for the vfiler dr configure command.This option enables you to set up a disaster recovery vFiler unit without reinitializing the existingSnapMirror relationship between the source and the destination storage systems.

You can use the -u option when the SnapMirror relationship between the volumes of the sourcevFiler unit and the respective volumes on the destination storage system is already initialized.

For more information about using this option, see the na_vfiler(1) man page.

Changed options in the Data ONTAP 8.0 7-Mode releasefamily

You need to know which options have been changed or become obsolete.

For each option, the following table gives this information:

• The name of the changed option


• The nature of the change• The Data ONTAP 8.0 7-Mode release in which the change was introduced


Option Change Release changed

autosupport.minimal.sub

ject.id

The default for this option hasbeen changed to systemid forsystems shipped with DataONTAP 8.0.2 7-Mode or later.

8.0.2

cifs.max_mpx The default for this option hasbeen changed to 253.

8.0.2

flexscale.max_io_qdepth This option has becomeobsolete.

8.0

httpd.admin.enable The default for this option hasbeen changed to off forsystems shipped with DataONTAP 8.0 7-Mode or later.

8.0

httpd.admin.ssl.enable The default for this option hasbeen changed to on for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0

rsh.enable The default for this option hasbeen changed to off forsystems shipped with DataONTAP 8.0 7-Mode or later.

8.0

ssh.enable The default for this option hasbeen changed to on for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0

ssh2.enable The default for this option hasbeen changed to on for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0

security.passwd.rules.e

veryone

The default for this option hasbeen changed to on for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0


Option Change Release changed

security.passwd.rules.h

istory

The default for this option hasbeen changed to 6 for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0

telnet.distinct.enable The default for this option hasbeen changed to on for systemsshipped with Data ONTAP 8.07-Mode or later.

8.0

telnet.enable The default for this option hasbeen changed to off forsystems shipped with DataONTAP 8.0 7-Mode or later.

8.0

timed.log This option has becomeobsolete.

8.0

timed.max_skew This option has becomeobsolete.

8.0

timed.min_skew This option has becomeobsolete.

8.0

timed.proto This option supports only thentp protocol.

8.0

timed.sched This option has becomeobsolete.

8.0

timed.window This option has becomeobsolete.

8.0


Requirements for running Data ONTAP 8.1

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

To know the capacity and maximum volume size of your storage system model, see the HardwareUniverse (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml.

Supported systemsYou need a supported storage system to run a release in the Data ONTAP 8.1 family operating in 7-Mode.

The following FAS and V-Series systems are supported:

• 6280• 6240• 6210• 6080• 6070• 6040• 6030• 3270• 3240• 3210• 3170• 3160• 3140• 3070• 3040• FAS2240• FAS2040• FAS2220

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

The following FlexCache systems are supported:

• SA600• SA320




• SA300

The following Data ONTAP-v systems are supported:

• CBvM100• DOvM100• FDvM100

All systems supported by the Data ONTAP 8.1 release family operating in 7-Mode can be configuredas an HA pair, except for Data ONTAP-v systems.

For more information about supported storage systems in the Data ONTAP 8.1 release familyoperating in 7-Mode, see the Hardware Universe (formerly the System Configuration Guide) at support.netapp.com/knowledge/docs/hardware/NetApp/syscfg/index.shtml.

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

The following storage systems are not supported:

• 3050• 3020• FAS2050• FAS2020• 9xx• 2xx• GF900• GF270c• R200• SA200

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

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

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

Requirements for running Data ONTAP 8.1 | 99


Storage system firmware

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

Disk firmware

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

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

Disk shelf firmware

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

V-Series requirements and support informationNot all Data ONTAP releases support the same features, configurations, storage system models, andstorage array models for V-Series systems. The V-Series Support Matrix is the final authority onsupported configurations, storage array firmware and microcode versions, switches, and so on.

See the V-Series Support Matrix for complete information about supported V-Series models andstorage arrays, as well as supported microcode, license code, and storage array firmware versions.The V-Series Support Matrix also identifies switch connectivity and topology that can be used withV-Series systems. You can access the V-Series Support Matrix on the NetApp Support Site.

V-Series limits informationThe V-Series Limits Reference for Third-Party Storage is being released for the first time with DataONTAP 8.1.1. This document provides information about limits that you need to be aware of whenplanning a V-Series configuration with third-party storage.

This document includes the following information:

• Minimum and maximum array LUN size that Data ONTAP supports• Minimum root volume size for array LUNs• Minimum size for aggregates with array LUNs• Storage arrays for which Data ONTAP supports multiple LUN groups• Maximum number of devices in a V-Series neighborhood• System capacities


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

http://now.netapp.com/NOW/download/tools/diskfw/

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

This document covers the V-Series limits for all platforms and all Data ONTAP 8.x releases. It willbe reposted on support.netapp.com on a monthly basis if any updates are necessary.

Data ONTAP-v requirements and support informationNot all Data ONTAP features or configurations are supported when running on a Data ONTAP-vplatform (including the Data ONTAP Edge and Data ONTAP Edge-T products). This is because ofdifferences when Data ONTAP is running in a virtual machine on a host system instead of runningon a NetApp storage controller.

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

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

Requirements for running Data ONTAP 8.1 | 101



Important cautions

Before upgrading to this release of Data ONTAP, you need to read the important cautions to identifyand resolve issues that might affect the operation of your storage systems.

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

Upgrade and revert cautionsIf you are upgrading to this Data ONTAP release or reverting from this release to an earlier release,you should review these issues, and if any apply in your environment, take appropriate action.

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

iSCSI target adapters not supported in Data ONTAP 8.1 and laterThe iSCSI target adapter cards Emulex LPe100i-D1 (X1129A-R5), Emulex LP100i-D1 (X1029B-R5), Emulex LPe100i-F1 (X1136A-R5), and Emulex LP100i-F1 (X1036B-R5) are not supported inData ONTAP 8.1 and later. iSCSI targets are still supported on Ethernet and unified target adapterports.

These adapters are reported as Emulex LPe100i-D1, Emulex LP100i-D1, Emulex LPe100i-F1, andEmulex LP100i-F1 in the sysconfig command output.

Before upgrading to Data ONTAP 8.1 or later, move all iSCSI traffic to other ports and remove theseadapters from the storage controllers.

Change in nondisruptive upgrade procedureWhen you upgrade to this Data ONTAP release, you should be aware of changes in the softwareupdate command syntax and the requirement for boot environment access.

Beginning with 7.3.5 and 8.0.1, system firmware is updated automatically. It is no longer necessaryto access the boot environment for upgrades from a Data ONTAP 8.0.x release to a later release.

Note: This change only refers to minor nondisruptive upgrades (within a release family). Whenupgrading to a Data ONTAP 8.0.x release from an earlier release family, you must enter the bootenvironment during the takeover 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 the default for the softwareupdate command.



Note: However, when you first upgrade to Data ONTAP 7.3.5 or 8.0.1 or a later release in the 8.0family, you must specify the -r option for nondisruptive upgrades. In subsequent major and minornondisruptive upgrades, it will no longer be required to specify the option.

Upgrade process changes with Data ONTAP 7-Mode software imagesWhen you upgrade to Data ONTAP 8.0 and later releases, you must obtain Data ONTAP softwareimages from the NetApp Support Site and copy them to your storage system. Media kits, includingCD-ROMs with Data 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 no longer available. You mustobtain software images from the NetApp Support Site and copy them to your storage system or to anHTTP server in your environment.

Beginning with Data ONTAP 8.0, the following processes are no longer supported for extracting andinstalling Data ONTAP upgrade images:

• Using the tar command from UNIX clients• Using the setup.exe file and WinZip from Windows clients

For the upgrade to Data ONTAP 8.0 and later releases, .exe images are no longer available. Youmust use one of the following image types depending on the upgrade you are performing:

• .zip images, for upgrades from an earlier release family to Data ONTAP 8.0• .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 .tgz images for furtherupgrades.

After you have copied the .zip or .tgz image to your storage system, you can install it with thesoftware update command. Alternatively, you can make the .zip or .tgz image available from anHTTP server in your environment, then use the software update command to copy the upgradeimage from the HTTP server, 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 and Revert/DowngradeGuide for 7-Mode.

DS14mk2 shelves with ESH2 modules no longer supportedBeginning with Data ONTAP 8.1, DS14mk2 disk shelves with ESH2 storage I/O modules are nolonger supported. If even one of these devices is attached to your storage system, do not upgrade toData ONTAP 8.1 or later until after you replace the devices.

For more information, see Systems including DS14mk2 shelves with ESH2 modules on page 25.

Important cautions | 103

License updates required before upgradingIf you are upgrading FAS2040, FAS2240, 32xx, or 62xx systems from a Data ONTAP 8.0.x releaseto a Data ONTAP 8.1.x release, you must relicense certain features. This requirement does not applyto 31xx and 60xx systems.

Beginning in the Data ONTAP 8.1 release family, features are packaged together so that only onelicense key is required to add a group of features to FAS2040, FAS2240, 32xx, or 62xx systems.

If you were using a feature in a Data ONTAP 8.0.x release and you upgrade to Data ONTAP 8.1.x,the action you take depends on how your features were licensed in the Data ONTAP 8.0.x release.

• You purchased a license pack, but you added individual feature keys only.You must add the license key for the packs that include any individual feature key you were usingpreviously.

• You acquired your individual feature keys before license packs were available and have not yetpurchased a license pack.You must contact your NetApp representative to purchase and install license packs that includethe features you were using.

To ensure continued access to a feature that requires a license, you should add the pack license keybefore you upgrade to Data ONTAP 8.1.x.

If you do not add the pack license key before upgrading, the features are not available when you bootinto the new Data ONTAP release, and you must add the key after upgrading.

For information about Data ONTAP 8.1 licensing models and whether a license key must be addedfor a particular feature or pack, see the knowledgebase article Using License Keys with Data ONTAP8.1 7-Mode FAQ on the NetApp Support Site.

Related information

Using License Keys with Data ONTAP 8.1 7-Mode FAQ

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

If you acquire licensed or entitled products by upgrading to Data ONTAP 8.1 or later and theseproducts required a license prior to Data ONTAP 8.1, you might need to install a license afterreverting. This is the case if a license was not previously installed for the release you revert to.

Starting with Data ONTAP 8.1, some products are grouped together so that only one license key isrequired to add a pack of software products to a system. Also starting with Data ONTAP 8.1, someproducts are automatically entitled without requiring a license key. These products might haverequired a license in earlier releases. If you did not install a license for these products in a releaseearlier than Data ONTAP 8.1 and you revert to a release earlier than Data ONTAP 8.1, you mightneed to install a license so that you can continue to use the products after the revert.

For example, you have a 32xx system, which requires a license for MultiStore prior to Data ONTAP8.1, but you did not install a MultiStore license. After upgrading to Data ONTAP 8.1 or later, you



automatically get MultiStore with the Data ONTAP Essentials license pack without requiring aseparate license. If you revert to a release earlier than Data ONTAP 8.1, you must install aMultiStore license to continue to use MultiStore on your 32xx system.

For information about Data ONTAP 8.1 licensing models, see the knowledgebase article UsingLicense Keys with Data ONTAP 8.1 7-Mode FAQ on the NetApp Support Site.

3210 and 3140 storage systems with Flash Cache modules are supportedData ONTAP 8.1.1 operating in 7-Mode supports 3210 and 3140 storage systems with 256-GB FlashCache modules.

If you have a 3140 storage system with Flash Cache modules, Data ONTAP 8.1.1 reenables the 256-GB Flash Cache module on the 3140 storage systems using the full capacity for wear-leveling andcache storage. However, to deliver on the full value of Data ONTAP 8.1.1, the maximum workingdataset in the 256-GB Flash Cache module on 3140 storage systems is 128 GB.

After upgrading to Data ONTAP 8.1.1 on a 3210 or 3140 storage system, you must verify that theWAFL external cache functionality is enabled.

Verifying that WAFL external cache functionality is enabled

After upgrading to Data ONTAP 8.1.1 on a 3210 or 3140 storage system with 256-GB Flash Cachemodules, you must verify that the WAFL external cache functionality is enabled.

Steps

1. Verify that the WAFL external cache functionality is enabled by entering the followingcommand:

options flexscale.enable

For 7-Mode single-controller configurations, run this command from the system console prompt.

For 7-Mode HA pairs, run this command from each node.

2. The next step depends on the system output:

If theoutputshows...

Then...

on The WAFL external cache functionality is enabled and no further action is needed. However,if you did not configure the WAFL external cache option when you enabled the functionality,you can do so now.

You can find the option descriptions and commands in the Data ONTAP SystemAdministration Guide for 7-Mode on the NetApp Support Site at support.netapp.com.

Note: For 7-Mode HA pairs, you must configure the option on each node.





If theoutputshows...

Then...

off a. Enable the WAFL external cache functionality by entering the following command:

options flexscale.enable on

For 7-Mode single-controller configurations, run this command from the system consoleprompt.For 7-Mode HA pairs, run this command from each node.

b. Configure the WAFL external cache option.You can find the option descriptions and commands in the Data ONTAP SystemAdministration Guide for 7-Mode on the NetApp Support Site at support.netapp.com.

Note: For 7-Mode HA pairs, you must configure the option on each node.

Note: You can set the WAFL external cache configuration option now or later, but it isrecommended that you set the option now to ensure optimal performance for thesystem's workload.

NDU not available for SAN systems with some versions of Linux hostsrunning high-speed interconnects

For some versions of Linux, you cannot upgrade to Data ONTAP 8.1 or earlier using thenondisruptive upgrade (NDU) method with SAN hosts that have ALUA enabled and have high-speedinterconnects (8 Gb or faster).

The following versions of Linux running on hosts can encounter host hangs or long delays in I/Ooperations during the failover phase of the Data ONTAP (NDU), which causes disruption of servicesto the hosts:

• Red Hat Enterprise Linux 6.x or 5.x prior to 5.8• SUSE Linux Enterprise Server 10.x and 11.x• Oracle Linux 5.x and 6.x

To perform a NDU with Red Hat Enterprise Linux, you must ensure you are using Red HatEnterprise Linux 5.8. Otherwise, you need to plan for a disruptive Data ONTAP upgrade.

For more information, see I/O delays sometimes seen after controller failover on Linux hosts withALUA on page 129.

IPv6 address entries in /etc/exports file missing brackets after upgradingIf you are upgrading from the Data ONTAP 7.3.x release family to Data ONTAP 8.1 7-Mode andyou have IPv6 enabled, you must manually update the /etc/exports file and add the missingsquare brackets around each IPv6 address.

After finishing the upgrade, check each entry in the /etc/exports file that contains an IPv6address. In the following example, the IPv6 addresses are missing 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 manually update the file and addthe square brackets around each IPv6 address so that the entry looks similar to the followingexample:

/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 the exportfs command. Formore information, see the Data ONTAP File Access and Protocols Management Guide for 7-Mode.

Automatic background disk firmware updates not enabled for non-mirroredRAID4 aggregates

You must manually correct an option setting if your system includes non-mirrored RAID4 aggregatesand you have upgraded from a Data ONTAP 7.3.x release.

In Data ONTAP 8.0.2 and later releases, automatic background disk firmware updates are availablefor non-mirrored RAID4 aggregates, in addition to all other RAID types. However, if you upgradefrom a Data ONTAP 7.3.x release, the raid.disk.background_fw_update.raid4.enableoption is not set to a default of On, as is stated in the options(1) man page. If your system includesnon-mirrored RAID4 aggregates and you have upgraded from a Data ONTAP 7.3.x release, youshould manually set the value for this option to On.

Erroneous reboot message during Data ONTAP reversionWhen reverting from Data ONTAP 8.1 to an 8.0.x release, you might see a screen message directingyou to enter the reboot command. That direction is incorrect, you should enter the revert_tocommand 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 future Data ONTAP release.


Reverting to an earlier release on a 3210 with more than 200 volumes cancause a system panic

Data ONTAP 8.1 and later releases support 500 volumes on the 3210. For previous Data ONTAPrelease families, only 200 volumes are supported. If you attempt to revert a 3210 with more than 200volumes to an earlier release of Data ONTAP, not all of your volumes will come online.

To avoid this issue, ensure that you have 200 or fewer volumes before reverting to an earlier releasefamily on a 3210.

Validation of LUNs fails when reverting from Data ONTAP 8.1 to someearlier releases

Validation of LUNs created in Data ONTAP 8.1 might fail when you revert from Data ONTAP 8.1to some earlier releases. In Data ONTAP 8.1 and later releases, LUN serial numbers can containcharacters, such as number sign (#) and ampersand (&), which are not supported in some earlierreleases.

Data ONTAP 8.1 supports the following characters in LUN serial numbers: number sign (#),ampersand (&), dollar sign ($), percent (%), asterisk (*), plus sign (+), 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 or later, you cannot revertto Data ONTAP releases earlier than version 8.0.3 in the 8.0.x release family or version 7.3.7 in the7.3.x release family.

Downgrade to 8.1 not allowed for 3140 and 3210 systems with Flash Cachemodules

If you want to downgrade a 3140 or 3210 storage system that has a Flash Cache module to DataONTAP 8.1, you need to disable the Flash Cache modules before you can downgrade the system.The downgrade will fail if you do not disable the modules.

Flash Cache modules are not supported on 3140 and 3210 storage systems running Data ONTAP 8.1.

For information about how to disable the Flash Cache modules before you downgrade to DataONTAP 8.1, see the Data ONTAP Upgrade and Revert/Downgrade Guide for 7-Mode.

MultiStore license and vFiler units removed when reverting to Data ONTAPrelease earlier than 8.1

If you revert to a Data ONTAP release earlier than 8.1 and your system has the Multistore featureenabled, the MultiStore license and vFiler units are removed in certain cases. The affected storagesystems are 62xx, 32xx, FAS2240, FAS2220, and FAS2040.

The MultiStore license and vFiler units are removed when you perform the revert operation in thefollowing scenarios:


• The storage system has a new installation of Data ONTAP 8.1.• 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 upgrading to 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 vfilerstatus -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 modified or deleted.

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

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

Cannot continue setup using the web interfaceStarting with Data ONTAP 8.1, the web interface has been removed and you cannot useOnCommand System Manager for initial setup of the storage system. This means that you mustrespond to system setup prompts differently from previous releases.

When prompted to continue setup using the web interface, you must enter n to continue setup usingthe command-line interface. Starting with Data ONTAP 8.1, the web interface has been removed andyou cannot use OnCommand System Manager for initial setup of the storage system.

If you enter y to continue setup using the web interface, a few errors appear on the screen and thelinks provided result in browser errors. You can ignore these errors, as the setup script continues tothe next prompt regardless of what you enter.

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

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

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


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

System panics when Flash Cache is full and the root volume is a traditionalvolume

If you have a Flash Cache module and the root volume is a traditional volume, the storage systempanics when the Flash Cache reaches its capacity. This issue is related to the cache rewarmingfeature, which was introduced in Data ONTAP 8.1.

When you experience this issue, a message similar to the following appears:

Panic string: ../common/wafl/ext_cache/ec_tagstore.c:2739: Assertionfailure. in SK process wafl_exempt02 on release 8.1

This issue does not affect a storage system if the system's root volume is a FlexVol volume.

Use one of the following two workarounds. If you have not yet upgraded to Data ONTAP 8.1, youshould perform one of the workarounds before you upgrade. If you have already experienced theissue, it will reoccur unless you implement one of the workarounds. If you have an HA pair,implement the workaround on both nodes.

1. Turn off the cache rewarming feature.This is the preferred workaround because it does not result in loss of Flash Cache functionality.By design, the cache rewarming feature does not work if the storage system's root volume is atraditional volume.To turn off the cache rewarming feature, do the following:

a. Enter the following command to halt the system:halt

b. Enter the following command from the LOADER prompt:setenv ext-cache-disable-rewarm? true

c. Enter the following command to boot the system:boot_ontap

2. Turn off the WAFL external cache.Turning off the WAFL external cache disables the Flash Cache module. To turn off the WAFLexternal cache, enter the following command:options flexscale.enable off

Certificates signed with MD5 could cause loss of connectivity to secureclients

To enhance security, starting with Data ONTAP 8.0.2, Data ONTAP uses the SHA256 message-digest algorithm to sign the contents of digital certificates (including certificate signing requests


(CSRs) and root certificates) on the storage system. Use of the MD5 message-digest algorithm,which was used to sign CSRs and root certificates, is no longer officially supported.

Depending on the certificate depth verification, clients might need to use SHA256 to verify digitalcertificates presented by Data ONTAP 8.0.2 and later.

Data ONTAP 8.0 and 8.0.1 use the MD5 message-digest algorithm to sign digital certificates. Due tothe CVE-2004-2761-IETF X.509 certificate MD5 signature collision vulnerability, and to minimizesecurity risks when using a certificate signed with MD5, you should have the CSRs further signed bya certificate authority (CA) using SHA256 or SHA1.

If your root FlexVol volume does not meet the new size requirementsThe minimum required size for root FlexVol volumes has been increased for every system runningthe Data ONTAP 8.0 release family or later. If your root FlexVol volume does not meet the newrequirements, you should increase its size 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 systemproblem occurs, these files are needed to provide technical support.

For more information about root volumes and the root FlexVol volume requirements for yourplatform, see the Data ONTAP System Administration Guide for 7-Mode.

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

Growing a volume while its associated aggregate is expanding to 64 bit cancause system disruption

When an aggregate is expanding to the 64-bit format, it contains inodes of both format types. If acommand or ONTAPI call is issued to grow the volume during this time, it can cause a systemdisruption.

To avoid this issue, do not execute volume grow commands until the associated aggregate is nolonger expanding to the 64-bit format. You can determine whether the expansion is complete byissuing the following command:

aggr 64bit-upgrade status aggr_name

Initiating aggregate expansion to 64-bit using a larger disk can causesystem disruption

When you add a disk to a 32-bit format aggregate that causes the aggregate's size to surpass 16 TB,Data ONTAP expands the aggregate to the 64-bit format. If the new disk is larger than the other disks


in the aggregate, and the disk is added to an existing RAID group, the system experiences adisruption.

If you want to add a larger disk to an aggregate, and doing so will cause the aggregate to expand tothe 64-bit format, add the larger disk to a new RAID group.

Accessing data in a Snapshot copy causes a system disruption undercertain conditions

Under certain conditions, accessing data inside a Snapshot copy causes a system disruption.

All of the following conditions must be met for the disruption to occur:

• The Snapshot copy contains more than 15 qtrees (including the default qtree).• The active file system contains 15 or fewer qtrees.• The volume was previously taken offline and then brought back online.

This disruption can happen for CIFS storage clients starting from Data ONTAP 8.1 operating in 7-Mode, and with both CIFS and NFSv4 storage clients starting from Data ONTAP 8.1 operating inCluster-Mode.

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

Preventing service disruption when expanding an aggregate with volumesusing quotas

Before you expand an aggregate to the 64-bit format, you must check whether any volumesassociated with that aggregate have quotas enabled, and if so, you must disable them before startingthe expansion. Failure to take this step could result in a data service disruption.

About this task

These steps must be completed before initiating the aggregate expansion.

For more information about this issue, see bug ID 624375 in Bugs Online.

Steps

1. Determine which volumes are associated with the aggregate:

aggr status aggr_name

2. Determine which of the associated volumes have quotas enabled:

quota status volume_name

3. For each volume for which quotas are enabled, turn off quotas:

quota off volume_name

You can now initiate the aggregate expansion.

4. After the expansion has started, for each volume for which you disabled quotas, reenable them:

quota on volume_name


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

Before changing the language of an existing FlexVol volume, you must ensure that the expansionscanner is not running. Failure to perform this check could result in a system disruption or datacorruption.

To determine whether the expansion scanner is running, you use the aggr 64bit-upgradestatus command, available from the advanced privilege level, on the associated aggregate. If thiscommand reports that the volume is upgrading, you must wait until the upgrade of the volume isfinished before changing the language of the volume.

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

Related information

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

Some 32-bit operations cannot be performed on a Flash PoolYou cannot create a Volume SnapMirror relationship between a 32-bit source volume and adestination volume in a Flash Pool, and you cannot perform a SnapRestore operation from a 32-bitSnapshot copy on a volume in a Flash Pool. Attempting either of these operations could result in aservice disruption.


Related information


Requirements for converting an aggregate to a Flash PoolBefore you convert an aggregate to a Flash Pool, there are some important requirements that theaggregate must meet. Failure to observe these requirements could result in a service disruption.

Before adding SSDs to an aggregate composed of HDDs to convert the aggregate to a Flash Pool,ensure that the following conditions are met, in the following order:

1. The aggregate has the 64-bit format.You can determine the format of the aggregate by using the aggr status command. If it is nota 64-bit aggregate, you must expand it to the 64-bit format before proceeding.

2. All volumes in the aggregate are online.You can determine whether there are offline volumes in the aggregate by using the vol statuscommand. If there are offline volumes in the aggregate, you must bring them online beforeproceeding.

3. All volumes in the aggregate are 64-bit.You can determine whether there are 32-bit volumes in the aggregate by using the vol statuscommand.


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


The actions you need to take to allow the 32-bit volume to change to the 64-bit format depend onthe reason it could not be changed to 64-bit when the aggregate was expanded. This happeneddue to one of these reasons:

• The volume was offline when the aggregate was expanded to the 64-bit format.Now that the volume is online, it changes automatically to the 64-bit format; you do not needto take any further action.

• The volume is the destination of a Volume SnapMirror relationship where the source volumeis a 32-bit volume.You must break the mirror to allow the destination volume to be changed to the 64-bit format.

• There was not enough free space in the volume when the aggregate was expanded to the 64-bit format.You must provide enough free space to allow the volume to change to the 64-bit format.

When all volumes in the aggregate are displayed with the 64-bit format, you can proceed with theFlash Pool conversion.

For information about Flash Pools and expanding aggregates to the 64-bit format, see the DataONTAP Storage Management Guide for 7-Mode.


Related information


Network protocol cautionsThis information addresses network protocols cautions. Review the following section for importantinformation regarding network management.

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

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

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

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



Reconfiguring the losk interface results in system outageIf you modify the default configuration of the losk interface, it can result in a system outage. If anyIP address or routing configurations related to the losk interface exists in the /etc/rc file, you mustremove these configurations to avoid undesirable behavior of the storage system.

For more information about this issue, see Bug ID 464157 on Bugs Online.

Related information


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

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

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

About this task

To ensure that the domain controllers, DNS servers, and LDAP servers are accessible, it isrecommended that you run the following tests on the partner node for which giveback is to beinitiated before initiating a giveback:

Note: If the storage system contains vFiler units, you must complete the procedure on all vFilerunits running CIFS.

Steps

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

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

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

cifs domaininfo



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

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

cifs adupdate

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

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

wcc -s your_domain\user_account

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

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

priv set advanced

getXXbyYY getpwbyname_r user_name

getXXbyYY getpwbyuid_r uid

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

Result

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

Note: Successful execution of these commands does not guarantee that CIFS startup duringgiveback will occur quickly. The servers that are responding now might fail later to respond whengiveback occurs.

CIFS setup using ONTAPI library might lead to the removal of alreadyexisting user-created CIFS shares

Due to a software bug in Data ONTAP, using the ONTAPI library to execute CIFS setup might leadto the removal of existing user-created shares. The default CIFS shares are not affected.

System Manager 2.x uses the ONTAPI library. To work around this issue, use the CLI to set upCIFS.

CIFS SID and credential leak impacts cache memory availabilityData ONTAP has a software issue that leads to a memory leak of SIDs and user credential datastructures under certain circumstances.

On a busy system susceptible to this issue, the amount of orphaned memory increasingly affectsoperation of Data ONTAP and eventually triggers other issues and bugs related to memory pressure.Symptoms of this issue might be that CIFS becomes unresponsive or CIFS authentication might beslow.

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


Related information


Storage system might panic when not specifying an export pathIf you enter the CLI command exportfs -uf to remove all entries from the access cache andunexport file system paths, the storage system might panic if you do not specify an export path. It isvalid to use the -f option without specifying an export path, but not the -u option.

To avoid this issue, do not use the -u and -f options at the same time. Use the exportfs -fcommand to remove all entries from the access cache. Use the exportfs -ua command to unexportall file system paths. Use the exportfs -u path command to unexport a specific file system path.

SAN administration cautionsIf your storage system is deployed in a SAN environment, you might need to familiarize yourselfwith SAN administration cautions and take appropriate action before upgrading or reinstalling.

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

2-Gb FC ports not supported as targetsData ONTAP 8.1 does not support the onboard 2-Gb Fibre Channel ports in 6030 or 6070 systems astargets.

The 2-Gb FC ports cannot be initialized if they are configured as targets. If you are upgrading a 6030or 6070 system from an earlier release, be sure you have moved any FC target traffic to other portsbefore installing Data ONTAP 8.1.

The onboard 2-Gb Fibre Channel ports can still be used as initiators.

Data protection cautionsIf your storage system is configured with licenses for data protection technologies, you should reviewthese issues and take appropriate action before upgrading or reinstalling.

For more information about these issues, see the Data ONTAP Data Protection Online Backup andRecovery Guide for 7-Mode.

Reversion requirements with volume ComplianceClock and autocommitperiod of SnapLock volumes

If you are reverting to a previous release of Data ONTAP that supports SnapLock, you must considerthe status of the volume ComplianceClock time and autocommit period of the SnapLock volumes.

• Before reverting to a previous release, you must ensure that the volume ComplianceClock valueof the SnapLock volumes does not exceed the date, 19 January 2038.



If it exceeds this date, the revert fails. You can check the volume ComplianceClock time by usingthe snaplock clock status command.

• When reverting to a previous release, if the SnapLock volumes have different autocommitperiods, you have to accept the prompt to set the system-wide autocommit period option to none.You can check the autocommit period of the SnapLock volumes by using the vol status –vcommand.

SnapLock API not supportedStarting with Data ONTAP 8.1, the API snaplock-get-compliance-clock and the inputparameter is-compliance-clock for the API clock-get-clock is no longer supported for SnapLock.

For more information, see the Data ONTAP Archive and Compliance Management Guide for 7-Mode.


Known problems and limitations

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

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

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

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

Cached data in a Flash Cache module is cleared during upgrade to DataONTAP 8.1 release family

Your storage system clears the cached data in a Flash Cache module when you upgrade to the DataONTAP 8.1 release family from a previous Data ONTAP release family (for example, from DataONTAP 8.0.3).

Because there is no cached data in the Flash Cache module, the system serves initial read requestsfrom disk, which results in decreased read performance during this period. The system repopulatesthe cache as it serves read requests.

After both nodes in an HA pair are running Data ONTAP 8.1 or later, the cache rewarming featuremaintains the cached data in a Flash Cache module during a graceful shutdown (for example, duringan upgrade or takeover and giveback).

For more information about cache rewarming, see Cache rewarming for Flash Cache modules onpage 28.

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

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

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

119


Features with the ENABLED keyword in the license command output mightrequire setting the options

Output of the license command displays the ENABLED keyword instead of the license key for somefeatures. Before using the features, you might need to use the options command to enable them.

For features that were not used with previous versions of Data ONTAP but are now provided free ofcost or as part of a software pack for which you have installed a license key, the output of thelicense command displays ENABLED in Data ONTAP 8.1 or later releases. You can enable thefollowing features by using the options command:

• Disk sanitization (licensed_feature.disk_sanitization.enable)• Fibre Channel (licensed_feature.fcp.enable)• FlexCache (licensed_feature.flexcache_nfs.enable)• iSCSi (licensed_feature.iscsi.enable)• MultiStore (licensed_feature.multistore.enable)• NearStore (licensed_feature.nearstore_option.enable)• VLD (licensed_feature.vld.enable)

For more information, see the na_options(1) man page and the knowledgebase article Using LicenseKeys with Data ONTAP 8.1 7-Mode FAQ on the NetApp Support Site.

vFiler DR configuration with the snapmirror.checkip.enable option on fails,if SnapMirror fails to authenticate destination IPv6 address

When you configure vFiler units for disaster recovery, if the snapmirror.checkip.enable optionis set to on on the source storage system and the IPv6 address of the source storage system is used forcommunication, SnapMirror requires the IPv6 address of the destination storage system to set up aSnapMirror relationship.

You must specify the destination storage system’s IPv6 address in the list of allowed addresses forSnapMirror relationship on the source storage system. You can add the destination storage system’sIPv6 address either to the snapmirror.access option, or to the /etc/snapmirror.allow file ifthe snapmirror.access option is set to legacy.

For more information about the snapmirror.checkip.enable option, see the Data ONTAP DataProtection Online Backup and Recovery Guide for 7-Mode.

NTP version used to communicate with a newly configured NTP serverdefaults to v3

Starting with Data ONTAP 8.0.2, the Network Time Protocol (NTP) version to be used forcommunicating with a newly configured NTP server defaults to v3 instead of v4. This change is toaddress situations where certain time servers support only NTP v3.

Releases prior to Data ONTAP 8.0 use Simple NTP v3 (SNTPv3) by default, while Data ONTAP 8.0and 8.0.1 use NTP v4 by default. For Data ONTAP 8.0.2 and later releases, the NTP daemon




continues to use the highest supported version (v4 in this case) to communicate with the time serversthat were configured prior to Data ONTAP 8.0.2.

To reset the time servers to use NTP v3, you can use the options timed.servers command toreconfigure the list of servers.

For NTP troubleshooting information, see the following knowledgebase articles on the NetAppSupport Site:

• How to verify NTP operation in Data ONTAP 8• How to troubleshoot NTP synchronization issues in Data ONTAP 8 and later releases• Data ONTAP 8 and later releases fail to synchronize time with Windows w32time NTP server

Related information

How to verify NTP operation in Data ONTAP 8: kb.netapp.com/support/index?page=content&actp=LIST&id=S:1010058How to troubleshoot NTP synchronization issues in Data ONTAP 8 and later releases:kb.netapp.com/support/index?page=content&actp=LIST&id=S:1012660Data ONTAP 8 and later releases fail to synchronize time with Windows w32time NTP server:kb.netapp.com/support/index?page=content&actp=LIST&id=S:2015314

If your system uses rtc or rdate as the protocol for time synchronizationStarting with Data ONTAP 8.0, the Network Time Protocol (NTP) protocol is the only supportedprotocol for time synchronization. The rtc and the rdate protocols of the timed.proto option areobsolete and no longer take effect after you upgrade to Data ONTAP 8.0 or later.

If your system does not use NTP as the time-synchronization protocol, it will not keep accurate timeafter you upgrade it to Data ONTAP 8.0 or later. Problems can occur when the storage system clockis inaccurate.

If your system does not already use NTP as the protocol for time synchronization, immediately afterupgrading to Data ONTAP 8.0 or later you must set timed.proto to ntp, set timed.servers touse time servers that support NTP, and ensure that timed.enable is set to on.

Note: After you set timed.proto to ntp, the setting remains in effect even if you revert back to arelease prior to Data ONTAP 8.0.

For information about how to synchronize the system time, see the Data ONTAP SystemAdministration Guide for 7-Mode.

Obsolete timed optionsStarting with Data ONTAP 8.0, several timed options are obsolete although they remain visible inthe CLI.

The following timed options have no effect in Data ONTAP 8.0 or later:

• The timed.log option

Known problems and limitations | 121

https://kb.netapp.com/support/index?page=content&actp=LIST&id=S:1010058






• The timed.max_skew option• The timed.min_skew option• The timed.sched option• The timed.window option• The rtc and rdate values of the timed.proto option

If you attempt to set these options when the system is running Data ONTAP 8.0 or later, they have noeffect. However, these settings do take effect if the system is reverted back to a release prior DataONTAP 8.0.

Issues regarding the timed logStarting with Data ONTAP 8.0, the NTP daemon automatically adjusts the storage system time tokeep the system clock synchronized with the specified NTP server. However, time adjustments madeby the NTP daemon are not logged even when the timed.log option is set to on.


Related information


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

Files might not be able to be deleted using NFS in a full FlexVol volumeIf a FlexVol volume is almost full, you might be prevented from freeing up space by deleting filesusing an NFS client. There are actions you can take to regain free space in a full volume, and ways toconfigure the volume to help prevent it from becoming so full again.

You must provide more free space for the volume before you can proceed with the file deletion. Ifyou have free space in the associated aggregate, you can increase the size of the volume.

For information about other ways to free space in the volume, and how to prevent this problem fromreoccurring, see Bug ID 602479 in Bugs Online.

Related information


Disks might be silently left unassigned for multi-disk carrier shelvesData ONTAP prevents disks in the same carrier from being owned by different nodes. If the result ofa disk assign command would result in split ownership, the disk is not assigned and no error




message is displayed. The disks whose assignment did not result in split ownership are assignedsuccessfully.

Write operations might fail or LUNs might go offline if deduplicationmetadata increases

In volumes with deduplication enabled, the deduplication metadata increases if the deduplicationschedule is turned off. The increase in metadata might cause write operations to fail or LUNs to gooffline.

To avoid this issue, you must schedule deduplication to be run periodically by using the sisconfig -s command.

If the metadata in the volume has increased, then you must disable deduplication by using the sisoff command and delete the metadata by using the sis reset command.

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

You cannot assign ownership and checksum type for spare disks or arrayLUNs in the same operation

If you need to change both the checksum type and ownership of a spare disk or array LUN, you mustuse two separate commands.

Example

If you wanted to change the ownership to sys2 and checksum type to block for array LUNvgbr300s20:21.126L14, you would use the following two commands:

disk assign vgbr300s20:21.126L14 -c block disk assign vgbr300s20:21.126L14 -o sys2 -f

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

The cf_ remote license is installed by default on all new 32xx and 62xx storage systems. If you areusing mirrored aggregates that are not in a MetroCluster configuration, the presence of this licensecan reduce read performance, because data is read from only one plex.

You can recover from this situation by using the following command to disable the license (on bothnodes 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 origin volumerunning Data ONTAP 8.1 can cause system panic

A storage system containing a FlexCache can panic if a Data ONTAP 8.1 origin volume or itscontaining aggregate undergo aggregate expansion or deduplication.

This problem can occur on FlexCache volumes running a release earlier than Data ONTAP 7.3.6 inthe 7.3 release family or Data ONTAP 8.0.2 in the 8.0 release family, with an origin volume runningData ONTAP 8.1. The problem is fixed in Data ONTAP 7.3.6, 8.0.2, 8.1, and later. However, boththe FlexCache system and the origin system must have the fix to prevent the problem.

To avoid this problem, take the FlexCache volume offline by using the vol offline commandbefore the deduplication of the origin volume or aggregate expansion. When the deduplication orexpansion is complete, place the FlexCache volume back online by using the vol onlinecommand.

After changing the port assigned to ACP, a reboot is required to regain useof the original port

If you reconfigure ACP to use a new port, the port that was configured for ACP before becomesavailable for use by another subsystem only after you reboot the storage system.

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

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

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

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

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

When the interface name used for configuring the partner interface is present in the /etc/hostsfile, the IP address of the local node is substituted instead of the IP address of the partner node. Thisresults in the partner node being unavailable during takeover.

To avoid this issue, you can use one of the following workarounds:

• Do not use interface names as alternate host names in the /etc/hosts file.


• Use the IP address of the partner node instead of the interface name while configuring the partnerinterface.

Note: You can use the IP address of the partner node while configuring the partner interfaceonly when the interface belongs to the default IPspace.

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

Related information

Bugs Online: support.netapp.com

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

The static routes from a network interface in the down status are not retargeted to another networkinterface with an autoconfigured IPv6 address in the same subnet.

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 following command:

ifconfig interface down

The routes are retargeted to the network interface with the autoconfigured IPv6 address that isconfigured to the up status.


Related information


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

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

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



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


Related information


File access protocol issuesIf your storage systems provide CIFS, NFS, or FTP client services, you might need to familiarizeyourself with file access protocol issues.

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

Value of the option nfs.ifc.rcv.high is unexpectedly resetThe option nfs.ifc.rcv.high value might unexpectedly get reset to a previous value if it ischanged by the option nfs.tcp.recvwindowsize.

The option nfs.ifc.rcv.high controls the high-water mark after which NFS level flow controltakes effect. This option is also controlled by the option nfs.tcp.recvwindowsize. Changing theoption nfs.tcp.recvwindowsize automatically changes the value of the optionnfs.ifc.rcv.high.

However, there are some scenarios in which the option nfs.ifc.rcv.high value gets reset to aprevious value if it is changed by the option nfs.tcp.recvwindowsize.

To avoid the issue, first configure the option nfs.tcp.recvwindowsize, then manually configurethe option nfs.ifc.rcv.high.

Note: The value for the option nfs.ifc.rcv.high should be 1.5 times the value of the optionnfs.tcp.recvwindowsize.

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

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

The connecting client displays the following error message:NT_STATUS_MORE_PROCESSING_REQUIRED.

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


Related information





Microsoft Windows 7 clients fail to rename files and directoriesWhen a Microsoft Windows 7 client accesses an SMB share with widelinks enabled, it can failintermittently to rename files and directories on the mapped share. This can lead to a situation whereattempts by Microsoft Office applications to save documents on the share fail.

This issue is caused by a bug in the Windows 7 client for which a hot fix is available from Microsoft.The bug is described and information about how to obtain the hot fix is provided in the Microsoft KBarticle Microsoft KB 2703610: support.microsoft.com/kb/2703610. This KB article also providesinformation about a workaround for this issue if you do not want to apply the hot fix.

File copy operation on a widelink path inside a CIFS share might fail whenusing SMB 2.x

If you try to copy a large file to a folder that is within a widelink path inside the root of the CIFSshare and the size of the file being copied is greater than the available space at the root of share, thecopy operation fails.

This issue occurs if you are using Windows Explorer for the copy operation on an SMB 2.x capableclient with the SMB 2.x protocol enabled.

This happens because, when calculating whether there is available space for the copy operation tosucceed, the Windows client refers to the root of the share when calculating available space. Thisleads to a condition where the operation fails if there is insufficient space at the root of the share,even if the folder inside the root of the share resides within a widelink to a different volume that hasenough available space for the copy operation to succeed.

The following are possible workarounds for this issue:

• Copy the file using the DOS command prompt.• Copy the file using the Windows PowerShell interface.• 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 copy operation.

Domain controller responds with an access denied error to an SMB 2.x treeconnect request

A domain controller can respond with a 0xc0000022 error (Access Denied) to an SMB 2.x treeconnect request from the storage server on IPC$.

This issue is thought to be due to a race condition between changing the smb2.signing.requiredoption and creating a session setup message.

To avoid this issue, disable SMB 2.x on the storage system by entering the following command:

options cifs.smb2.client.enable off


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

CIFS users cannot rename or delete home directoriesUnder some conditions, one of which is a memory leak of user credentials, a user on a CIFS clientmight be unable to rename or delete a home directory. An error message might be generatedindicating that another user or program is using the directory.

For more information, see Bug ID 509466 and Bug 519891 in Bugs Online.

Related information


Domain user unable to execute CLI commands

If you log in to the storage system CLI as a domain user and enter the command cifs gpupdate,all subsequently entered CLI commands fail with the following error message:

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

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

Storage system requests to Windows Server 2008 might failThe storage system might encounter Vscan or FPolicy failures when sending scan requests to Vscanor FPolicy servers hosted on Windows Server 2008. This issue is caused by an authenticationexpiration timer introduced in SMB 2.0 that times out SMB 2.0 connections.

As a workaround, disable SMB 2.0 on the Windows server hosting the Vscan or FPolicy server, ordisable the storage system's SMB 2.0 client capability by entering the following command:

options cifs.smb2.client.enable off

Client notification messages in Windows domains require NetBIOSThe Windows client notification feature used for client messaging, shutdown notices, and vscanalerts requires NetBIOS over TCP to be enabled in Data ONTAP.

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

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



Configuration issue for clients that mount NFS shares using a non-reserved port

The nfs.mount_rootonly and nfs.nfs_rootonly options must be set to off on a storagesystem that must support clients that mount NFS shares using a non-reserved port even when the useris logged in as root. Such clients include Hummingbird clients and Solaris NFS/IPv6 clients.

If the nfs.mount_rootonly option is set to on, Data ONTAP does not allow NFS clients that usenonreserved ports (that is, ports with numbers higher than 1,023) to mount the NFS shares.

If the nfs.nfs_rootonly option is set to on, Data ONTAP does not allow any NFS requests overnonreserved ports.

Certain special characters are case sensitiveSome special characters do not have a one-to-one mapping between uppercase and lowercase. Suchcharacters are case sensitive.

For example, if the Unicode character U+03C2 (Greek Small Letter Final Sigma) is present in a filename in the file system, a search for the file fails when using the uppercase Sigma (U+03A3).

This happens because the file system forces characters to lowercase before performing a case-insensitive comparison. The uppercase Sigma is transformed to a lowercase non-final Sigma, whichdoes not match.

To avoid this issue, use the same characters without changing the case when accessing the file.Alternatively, avoid using such characters in file names altogether.

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

SAN administration issuesIf your storage systems are part of a SAN environment, you might need to familiarize yourself withSAN administration issues in this release.

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

I/O delays sometimes seen after controller failover on Linux hosts withALUA

During a controller failover (CFO), hosts running versions of Red Hat Enterprise Linux 6.x or 5.xprior to 5.8, SUSE Linux Enterprise Server 10.x and 11.x, or Oracle Linux 5.x and 6.x with ALUA


enabled sometimes encounter either host hangs or long delays in I/O operations. This issue can alsocause problems with nondisruptive upgrades (NDU).

The problem occurs when the recovery from the CFO is delayed. The delay causes the ALUAtransition period on the controller, which is running Data ONTAP, to take longer. The controllerresponds to the requests with the message:NOT READY: Asymmetric Access State Transition

At that point, the Linux host starts continually retrying its requests. The increased number of retriesoverwhelms the target and eventually leads to degraded performance, such as long and sometimesstalled I/O operations or situations 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 some versions of Linux SANhosts running high-speed interconnects on page 106.

If you use the automatic sizing feature on thinly provisioned LUNs whensnap reserve is set to a non-zero value

Generally, before you thinly provision LUNs, you should set snap reserve to zero. However,there are rare exceptions that require you to set snap reserve to a value other than zero. In theseinstances, you must use the automatic sizing feature for thinly provisioned LUNs in FlexVol volumesto work properly.

About this task

Using the automatic sizing feature is required because the space from deleted Snapshot copies canonly be used to fulfill Snapshot space requests. Furthermore, the automatic deletion process will notbegin until the snap reserve 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 a size in k (KB), m (MB), g(GB), or t (TB).

-I size is the increment by which the volume's size increases. Specify a size 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 smaller than its maximumsize, and if there is space available in its containing aggregate, the FlexVol volume's size willincrease by the specified increment.


Data protection issuesIf you use data protection products that include Snapshot technology (such as SnapRestore,SnapVault, SnapMirror, and SnapManager), you might have to familiarize yourself with relevantdata protection issues.

For more information about these issues, see the Data ONTAP Data Protection Online Backup andRecovery Guide for 7-Mode and the Data ONTAP Data Protection Tape Backup and RecoveryGuide for 7-Mode.

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

The cf_ remote license is installed by default on all new 32xx and 62xx storage systems. If you areusing mirrored aggregates that are not in a MetroCluster configuration, the presence of this licensecan reduce read performance, because data is read from only one plex.

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

license delete cf_remote

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

ADIC Quantum tape libraries are not discovered by Data ONTAPIn Data ONTAP 8.1 or later, the tape and medium changer devices on ADIC Quantum tape librariesare not discovered by Data ONTAP because these tape libraries have storage controller devicesmapped at LUN 0 by default.

For more information about this issue, see Bug ID 544197.

Related information


SMTape restore to an offline volume overwrites the data on that volumeIf you perform an SMTape restore to an offline volume, the data on tape overwrites the data on thatoffline volume.



Restore engine does not honor any mandatory or advisory locks on filesThe destination volume for a restore operation might have files with mandatory or advisory locks.When you initiate a restore operation to such a volume, the restore engine does not honor these locks.It ignores these locks and overwrites the files.

Tape devices behind DataFort are not detected unless a known SCSI deviceis mapped to LUN 0

If a known SCSI device is not mapped to LUN 0 when using a DataFort appliance, the tape drivesand media changers behind the DataFort appliance are not detected.

To avoid this issue, you must ensure that the following actions have been performed:

• When configuring a tape library, you must assign LUN 0 to SCSI devices such as, tape drives,media changers, and SCC devices for them to be detected and accessed by the storage system.

• When connecting a tape library through a DataFort appliance, the tape drive, media changer, orSCC device assigned to LUN 0 must also be mapped to a DataFort Cryptainer.This enables the storage system to detect LUN 0 and also the SCSI devices attached to it.


Related information


Third-party storage issues (V-Series systems only)There are certain issues and restrictions you should be aware of when Data ONTAP uses third-partystorage.

Restrictions for V-Series system upgrade to Data ONTAP 8.1 or laterDo not upgrade your V-Series system to run Data ONTAP 8.1 or later unless the V-Series SupportMatrix lists your storage array as supported for that release.

Before starting an upgrade of your V-Series system to run Data ONTAP 8.1 or later, check the V-Series Support Matrix at support.netapp.com to ensure that your storage array is supported for thatrelease. If your storage array is not supported in the Data ONTAP 8.1 release you want to run andyou attempt to upgrade, Data ONTAP generates an error message such as the following:

[sundance1:mlm.array.unsupported:warning]: Array LUN [S/N '60050768019181C8B00000000000004E' vendor 'xxx ' product 'yyy '] is not supported in this version of Data ONTAP.

If you upgrade your V-Series system to run Data ONTAP 8.1 or later and the storage array is notsupported in that release, you must revert Data ONTAP to an earlier release. See the Data ONTAP



http://support.netapp.com

Upgrade and Revert/Downgrade Guide for 7-Mode for information about how to revert your systemto an earlier release.

MultiStore issuesIf MultiStore is licensed on your storage systems, you might need to familiarize yourself with currentMultiStore issues.

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

Online migration of vFiler units is not supported on Flash PoolsYou cannot perform online migration of vFiler units if a source vFiler unit has volumes on FlashPools or a Flash Pool is selected on the destination storage system for online migration.

Platform maintenance issuesYou need to be familiar with the known issues and limitations that affect your ability to performhardware maintenance on the storage system.

Possible giveback failure during controller or NVRAM8 replacement on62xx or 32xx systems

Due to a known issue, when doing a nondisruptive replacement of the NVRAM8 adapter on a 62xxsystem or a controller module on a 32xx system, the cf giveback or storage failovergiveback command might fail after the hardware replacement is complete.

For details about whether you are exposed to this issue, and for a workaround, see TSB-1202-01, The'cf giveback' and 'storage failover giveback' commands fail after replacing NVRAM8 in a FAS62xxor a FAS32xx motherboard, on the NetApp Support Site at support.netapp.com.

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

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



savecore command does not workThe savecore command does not work to save a core dump to a core file. The -l option of thesavecore command is partially supported by listing only saved core images instead of both savedand unsaved images.

Allow about 20 minutes to save a core image after a system panic. Then use savecore -l to checkif a core image has been saved. Contact technical support if there is no core image.

Some error messages contain "VSA" instead of "Data ONTAP-v"Some error messages incorrectly use the name "VSA" instead of "Data ONTAP-v".

For example, you will receive the message Compression is not supported on the VSAplatform if you try to enable compression on a Data ONTAP Edge or Data ONTAP Edge-T storagesystem. The message text should say "...on a Data ONTAP-v platform".


Changes to published documentation

Some information about this release has become available after the set of guides provided with thisrelease were published. The information should be used in conjunction with the guides provided withthis release of Data ONTAP.

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

Changes to information about the /etc/rc fileThe About the /etc/rc file section of the Data ONTAP System Administration Guide for 7-Mode hasupdated information about the commands that the /etc/rc file must not contain.

The /etc/rc file must not contain the following types of commands:

• Commands that are executed by subsystems that are not yet available when the file is executed• Commands that are interactive and would wait for input during the boot process

For example, you must not include the iscsi commands or the wrfile command in the /etc/rcfile. Doing so prevents your storage system from booting successfully.

Corrections to the timed optionsThe timed.log option has been removed from The timed options section of the Data ONTAPSystem Administration Guide for 7-Mode. The option has become obsolete as of Data ONTAP 8.0.

Changes to the High-Availability Configuration GuideThere are some changes to the existing content of the Data ONTAP High-Availability andMetroCluster Configuration Guide for 7-Mode.

Virtual channel rules are not requiredThe topic titled "Virtual channel rules" in the Data ONTAP High-Availability and MetroClusterConfiguration Guide for 7-Mode is no longer applicable. Because the long distance mode “L0” is nolonger supported, and “LE” is the required minimum setting for E_Ports, the virtual channel cablingrules are no longer applicable.

For more information about applying LE, see the Fabric-attached MetroCluster Brocade SwitchConfiguration Guide at the NetApp Support Site.

135

Related information


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

Commands not supported in Data ONTAP 8.1.1The ups and filestats commands are included in the latest version of the Data ONTAPCommands: Manual Page Reference for 7-Mode, Volume 1, but these commands are not supportedin this release.

The nvfail_rename command does not exist in Data ONTAP 8.1.xThe nvfail_rename command, which is included in the latest version of the Data ONTAPCommands: Manual Page Reference for 7-Mode, Volume 2 does not exist in Data ONTAP 8.1.x.

Changes to the Storage Management GuideNew information has become available since the previous revision of the Data ONTAP StorageManagement Guide.

Combining SAS HDDs and SSDs in the same disk shelf is not supportedThe topic titled “Serial-attached SCSI (SAS) disk connection type” incorrectly states that you cancombine SAS HDDs in the same shelf with SSDs when the shelf is used for a Flash Pool. This is notthe case.

4-TB SATA disks are not supported for this version of Data ONTAPThe topic titled “Usable and physical disk capacity by disk size” incorrectly lists 4-TB SATA disks.These disks are not yet supported for this version of Data ONTAP.

Changes to the SAN Administration GuideNew information has become available since the previous revision of the Data ONTAP SANAdministration Guide for 7-Mode.

Block Access Management Guide has a new titleThe new title for the Block Access Management Guide for iSCSI and FC for 7-Mode is DataONTAP SAN Administration Guide for 7-Mode.



Volume moves between 32-bit aggregates and 64-bit aggregatesYou can move a volume from a 32-bit aggregate to a 64-bit aggregate. However, beginning in DataONTAP 8.1.1, you cannot move a volume from a 64-bit aggregate to a 32-bit aggregate. This is anupdate to requirements for a volume move in the Data ONTAP SAN Administration Guide for 7-Mode.

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

Changes to DHCP requirements for remote accessThe first two paragraphs of the DHCP requirements for remote access section have been updated toshow that you cannot use a Web browser to continue software setup.

When you enable Dynamic Host Configuration Protocol (DHCP) to assign a static IP address to anonboard network interface during first-time setup, you can complete the configuration remotely byusing an SSH client.

Changes to the SAN Configuration Guide for 7-ModeNew information has become available since the previous revision of the Data ONTAP SANConfiguration Guide for 7-Mode.

The previous title of this guide was Fibre Channel and iSCSI Configuration Guide for the DataONTAP 8.1 7-Mode Release Family.

The Fibre Channel and iSCSI Configuration Guide has a new nameThe new title for the Fibre Channel and iSCSI Configuration Guide for 7-Mode is Data ONTAPSAN Configuration Guide for 7-Mode .

Changes to published documentation | 137

Where to find product documentation and otherinformation

You can access documentation for all NetApp products and find other product information resources,such as technical reports and white papers, in the NetApp Library on the NetApp Support Site at support.netapp.com.

Related information

NetApp Support Site: support.netapp.comAccess & Order Product Documentation: support.netapp.com/knowledge/docs/docs.shtmlNetApp Library: Technical Reports: www.netapp.com/library/tr

Searching online informationThe NetApp Support Site includes a natural language search tool so that you can search easily formany sources of useful information.

You can search for the following sources of information at support.netapp.com:

• Troubleshooting, including bug tools, and knowledgebase• Documentation, including product documentation, guides and best practices, support

communications, and interoperability/compatibility matrix• Getting started, including navigating the site• Enabling AutoSupport, and using the Support Owner's Manual• Technical assistance, including requesting a part (RMA), opening a case, and contacting technical

support• Downloads, including software, utility ToolChest, and product evaluations

Finding documentation on the NetApp Support SiteYou can access the current Data ONTAP documentation library from the NetApp Support Site.

The documentation roadmap and the latest documentation for this Data ONTAP release are at support.netapp.com/documentation/productsatoz/index.html.




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

http://www.netapp.com/library/tr/


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

Copyright information

Copyright © 1994–2012 NetApp, Inc. All rights reserved. Printed in the U.S.

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

Software derived from copyrighted NetApp material is subject to the following license anddisclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at any time, and without notice.NetApp assumes no responsibility or liability arising from the use of products described herein,except as expressly agreed to in writing by NetApp. The use or purchase of this product does notconvey a license under any patent rights, trademark rights, or any other intellectual property rights ofNetApp.

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

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

139

Trademark information

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo, Akorri,ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePoint Predictor, Bycast, CampaignExpress, 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, Service Builder, 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,Tech OnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager, VPolicy, WAFL,Web Filer, and XBB are trademarks or registered trademarks of NetApp, Inc. in the United States,other countries, or both.

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. A complete and current list ofother IBM trademarks is available on the web at www.ibm.com/legal/copytrade.shtml.

Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the United Statesand/or other countries. Microsoft is a registered trademark and Windows Media is a trademark ofMicrosoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.

All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.

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

NetApp, Inc. NetCache is certified RealSystem compatible.


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

How to send your comments

You can help us to improve the quality of our documentation by sending us your feedback.

Your feedback is important in helping us to provide the most accurate and high-quality information.If you have suggestions for improving this document, send us your comments by email to [email protected]. To help us direct your comments to the correct division, include in thesubject line the product name, version, and operating system.

You can also contact us in the following ways:

• NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.• Telephone: +1 (408) 822-6000• Fax: +1 (408) 822-4501• Support telephone: +1 (888) 463-8277

141

mailto:[email protected]

8.1.1 7M 215-07092_A0 ur003.pdf

Documents

Transcript of 8.1.1 7M 215-07092_A0 ur003.pdf