SnapDrive 5.0.1 for UNIX Release Notes - IBM

IBM System Storage N series

SnapDrive 5.0.1 for UNIX Release Notes

GC26-7877-15

��

Contents

SnapDrive 5.0.1 for UNIX Release Notes . . . . . . . . . . . . . . . . . . . . . 1

Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Fixed issues in SnapDrive 5.0.1 for UNIX. . . . . . . . . . . . . . . . . . . . . 5SnapDrive takes longer to start in storage systems with a large number of volumes . . . . . . . 5SnapDrive for UNIX prevents a clone volume from inheriting the exportfs option of the parent volumein NFS environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5SnapDrive does not allow you to create clones from the secondary host system in NFS environment . 6Volume-based SnapRestore fails for live filespecs with multiple host vols on dg in SFRACenvironment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6When you clone a file specification using -devicetype shared options and after reboot you cannottelnet or ssh the host in an SFRAC environment . . . . . . . . . . . . . . . . . . . 6SnapDrive daemon fails to start if there are mixed or upper case variable values in the snapdrive.conffile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6SnapDrive may fail to start due to invalid format of the comment in the snapdrive.conf file . . . . 7SnapDrive storage show -all command fails on Red Hat Enterprise Linux and Oracle Enterprise Linux 8

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Known issues related to all hosts . . . . . . . . . . . . . . . . . . . . . . . . 9Known issues with AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Where to find additional information . . . . . . . . . . . . . . . . . . . . . . 19

Websites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Copyright and trademark information . . . . . . . . . . . . . . . . . . . . . 23Trademark information . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

© Copyright IBM Corp. 2012 iii

iv IBM System Storage N series: SnapDrive 5.0.1 for UNIX Release Notes

SnapDrive 5.0.1 for UNIX Release Notes

These release notes provide detailed information about new features,enhancements, and known issues.

New enhancements in SnapDrive 5.0.1 for UNIXv When snap management operations such as clone and restore are attempted

to create a Snapshot copy by using NFSv3, the snap management operationfails in a pure NFSv4 environment. To overcome this issue, a newconfiguration variable enable-migrate-nfs-version is added in thesnapdrive.conf file, that allows to clone/restore by using the higherversion of NFS. By default, this variable is off. During this migration, onlythe protocol version is considered and other options such as rw and largefiles are not taken into account by SnapDrive for UNIX. Therefore, only theNFS version for the corresponding NFS filespec is added in the /etc/fstabfile.Ensure that the appropriate NFS version is used to mount the filespecification by using -o vers=3 for NFSv3 and -o vers=4 for NFSv4.If the user wants to migrate the NFS file specification with all the mountoptions, it is recommended to use -mntopts in the snap managementoperations.

v A new variable ping-interfaces-with-same-octet is introduced inSnapDrive 5.0.1 for UNIX to avoid unnecessary pings through all theavailable interfaces in the host that might have different subnet IPsconfigured. If this variable is set to on, SnapDrive for UNIX considers onlythe same subnet IPs of the storage system and pings the storage system toverify address response. If this variable is set to off, SnapDrive takes all theavailable IPs in the host system and pings the storage system to verifyaddress resolution through each subnet, which may be locally detected as aping attack.

v SnapDrive for UNIX does not allow to clone if there is no exportpermission for a volume in an NFS entity. To overcome this situation,disable the variable check-export-permission-nfs-clone in thesnapdrive.conf file. As a result of the cloning operation, SnapDriveprovides appropriate access permissions on the cloned volume.

v SnapDrive for UNIX supports Brocade FC HBA and CNAs.

New features

SnapDrive 5.0 for UNIX contains the following new features andenhancements:

© Copyright IBM Corp. 2012 1

v SnapDrive operations are supported after the storage system hostname ischanged.

v -mntopts option is introduced for snap connect and snap restore operations.v -dump and -dump all options are added to SnapDrive operations to

automatically collect logs for a specific operation or for all availableoperations.

v Ext4 support is available from RHEL 6 and OEL 6 onwards.v SnapDrive 5.0 for UNIX transparently handles the SnapDrive failures

during the cutover phase in Data ONTAP features, such as volumemigration and Data Motion for vFiler units. SnapDrive for UNIX uses theappropriate configuration variables for these failures.

v Support for Data ONTAP 8.1 operating in 7-Mode is available only withData ONTAP 8.1 RC3 release and later.

Note: The Data ONTAP 8.1 7-Mode features documented in the SnapDrive5.0 for UNIX Installation and Administration Guide are supported from DataONTAP 8.1 RC3 release and later.

Note: There is no updated SnapDrive for UNIX Installation andAdministration Guide. For more information about the existing features, seethe SnapDrive 5.0 for UNIX Installation and Administration Guide.

2 IBM System Storage N series: SnapDrive 5.0.1 for UNIX Release Notes

Limitations

The following is a list of the current known limitations in SnapDrive forUNIX.

Generic Limitations of SnapDrive for UNIXv SnapDrive 5.0.1 for UNIX does not support snap operations on an NFS

mount point when the volume is exported with security type as krb5, krb5i,or krb5p.

v SnapDrive for UNIX does not support symbolic links for any mount points.v Snap operations may be inconsistent if you perform snap restore on a

mount point where a different entity is mounted other than what was takenin the Snapshot copy.

v The snapdrive config prepare luns command cannot be used to prepareany RDM LUNs in the guest operating system.

v SnapDrive clone split operation does not work when HTTPS is enabled fordaemon communication.

Limitations of SnapDrive for UNIX on Linux platformv SnapDrive for UNIX does not support operations on file

specification/LUNs, which span across Data ONTAP operating in 7-Modestorage system.

v Aggregates which contain Vserver volumes must be assigned to theVserver's aggregate list to configure the Vserver and execute SnapDriveoperations.

v SnapDrive 5.0.1 for UNIX does not support RDM LUN in the guest OS.

Limitations of SnapDrive for UNIX on Solaris platformv SnapDrive 5.0.1 for UNIX supports Veritas 5.0 MP2 RP4.v LUNs greater than 1 TB with SMI label is not supportedv SnapDrive for UNIX does not support the EFI and SMI LUNs in the same

disk group.

Limitations of SnapDrive for UNIX on AIX platformv SnapDrive 5.0.1 for UNIX does not support Live Partition Mobility (LPM)

and Live Application Mobility (LAM).v SnapDrive daemon takes a long time to restart if one or more FCP ports

links are down or not available. However, SnapDrive daemon startsirrespective of the state of the FCP ports.



Fixed issues in SnapDrive 5.0.1 for UNIX

The following known issues are fixed in SnapDrive 5.0.1 for UNIX.

SnapDrive takes longer to start in storage systems with a large number ofvolumes

By default, AutoSupport is enabled in SnapDrive 4.2 for UNIX release andlater versions. As part of the host side data collection, the number of LUNs,disk groups, host volumes and file systems, and all the volumes on thestorage system are queried. In a large scale environment, where SnapDrive forUNIX is connected to multiple storage systems with a large number ofvolumes, the SnapDrive for UNIX daemon can take longer to start.

SnapDrive 5.0.1 for UNIX introduces a new configuration variableautosupport-datacollection-enabled in the snapdrive.conf file, which allowsfor data collection such as the number of LUNs, disk groups, host volumesand file systems, and all the storage system volumes. By default, this variableis set to off.

Workaround:

It is recommended to set the autosupport-enabled variable to on in thesnapdrive.conf file.

SnapDrive for UNIX prevents a clone volume from inheriting the exportfs optionof the parent volume in NFS environments

A critical bug has been identified in SnapDrive 5.0 for UNIX, which preventsa clone volume from inheriting the exportfs option of the parent volume inNFS environments.

As an example, if the parent volume has the option root=<hostname/IP>specified, then the root=<hostname/IP> option gets deleted on the clonevolume, which might cause any write operation on the clone volume to fail. Ifyou are using any supported version of SnapManager for Oracle orSnapManager for SAP with SnapDrive 5.0 for UNIX in an NFS environment,then this bug might cause some SnapManager operations to fail.

This defect does not impact you if you have exported the parent volume withthe anon=0 option.


SnapDrive does not allow you to create clones from the secondary host systemin NFS environment

SnapDrive does not allow you to create clones from the secondary host (hostwhich does not have export permissions on the parent volume) system in NFSenvironment.

In the snapdrive.conf file, ensure that the check-export-permission-nfs-cloneconfiguration variable is set to off to create a clone from the secondary hostsystem in a NFS environment. By default, this variable is set to on to disablecloning in the secondary host system.

Volume-based SnapRestore fails for live filespecs with multiple host vols on dgin SFRAC environment

SnapDrive for UNIX works in volume-based SnapRestore in SFRACenvironment. During this condition, the Veritas diskgroup import fails withthe following error message VxVM vxdg ERROR V-5-1-10978 Disk group1245149592.131.hudson: import failed: Cannot find disk on slave node

SnapDrive for UNIX works for all live filespecs like -fs, -dg, -hostvol. However,the volume-based SnapRestore fails in diskgroups that has multiple hostvolumes. Thus, the single file SnapRestore must be used.

When you clone a file specification using -devicetype shared options and afterreboot you cannot telnet or ssh the host in an SFRAC environment

In an SFRAC environment, when you clone a file specification using-devicetype shared options, and after reboot you cannot telnet or ssh the hostsystem.

The cause of the failure is due to the boot options set to yes for shared mountpoint in the /etc/vfstab file.

In SnapDrive 5.0.1 for UNIX, the boot options set to no for shared mount pointin the /etc/vfstab file.

SnapDrive daemon fails to start if there are mixed or upper case variable valuesin the snapdrive.conf file

SnapDrive 5.0 for UNIX allowed only lower case entries in thesnapdrive.conf file. In case, you enter any upper or mixed values in thesnapdrive.conf file, snapdrive daemon fails to start while upgrade fromSnapDrive 4.2 for UNIX to SnapDrive 5.0 for UNIX.


SnapDrive 5.0.1 for UNIX accepts all types of cases such as upper, lower, ormixed in the snapdrive.conf file, and thereby does not encounter anySnapDrive daemon failure.

Examples:

v use-https-to-filer=ON #Communication with filer done via HTTPSinstead of HTTP

v use-https-to-dfm=On #Communication with DFM done via HTTPS insteadof HTTP

v use-https-to-dfm=on #Communication with DFM done via HTTPS insteadof HTTP

SnapDrive may fail to start due to invalid format of the comment in thesnapdrive.conf file

In the snapdrive.conf file, a comment must be preceded by a hash mark (#).

The following is an example that displays the valid and invalid formats in thesnapdrive.conf file.

Example 1:

v Valid format: enable-fcp-cache="on" #Enables FCP Cache in Assistants

v Invalid format: enable-fcp-cache="on" Enables FCP Cache in Assistants

You might encounter any one of the following error messages, if there is aninvalid format in the snapdrive.conf file.

Error message 1:

# snapdrive version -vError:------/opt/NetApp/snapdrive/snapdrive.conf failed validation checks.Cause:------Value of Configuration Variable is not recognized.Details-------Variable Name : enable-fcp-cacheAllowed Regex Pattern: (^on$|^off$)Value Given : on" Enable FCP Cache in AssistantsCorrective Action-----------------Set the variable value so that it matches the regex pattern.

Example 2:

v Valid format: trace-log-save=100 #Number of old copies of trace logfile to save

Fixed issues in SnapDrive 5.0.1 for UNIX 7

v Invalid format1: trace-log-save=100 Number of old copies of trace logfile to save

v Invalid format2: trace-log-save=100 #Number of old copies of trace logfile to save #test

Error message 2:

# snapdrived startterminate called after throwing an instance of’boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_lexical_cast> >’what(): bad lexical cast: source type value could not be interpreted as target

IOT/Abort trap (core dumped)

Workaround:

Ensure that the values for any configuration variable is within double quotesand any succeeding characters after the double quotes are preceded with onlyone # mark.

SnapDrive storage show -all command fails on Red Hat Enterprise Linux andOracle Enterprise Linux

If you are using SnapDrive for UNIX on Red Hat Enterprise Linux and OracleEnterprise Linux, the snapdrive storage show -all command fails with theStatus call to SDU daemon failed error message. To avoid this errormessage, set the LVM_SUPPRESS_FD_WARNINGS environment variable to 1in the shell.


Known Issues

To use the SnapDrive for UNIX product more effectively, you should be awareof the following known issues and workaround for some features.

Known issues related to all hosts

Some unexpected and potentially undesired behaviors, as well as, in somecases, workarounds to avoid these behaviors, have been identified in all hostsof this release.

Snap management operation fails in RHEL/OEL 5.x due to anissue with umount command

Snap management operation fails in RHEL/OEL 5.x due to an issue with theumount command. To overcome this, ensure that the NFS entity is mountedusing -o vers=3 in the command line interface.

Special characters in the AutoSupport messages showsgarble values in the EMS log view of the storage system

When AutoSupport is enabled in SnapDrive for UNIX, upon any operationfailure, the error messages are logged in the EMS log view of the storagesystem. If the error message contains any special characters such as (<, >, &, ',", and \r), garble values are displayed in the EMS log view of the storagesystem.

Workaround:

None.

SSL error occurs due to unsupported version

An SSL error occurs, if you have installed an unsupported version of opensslsoftware on the host.

Workaround:

It is recommended to use the supported SSL software package that is bundledwith the Native OS image.


Snapshot copies created on the FlexClone volume aredeleted after the clone split operation

When a clone is split from the parent volume, the Snapshot copies created onthe FlexClone volume are deleted as a result of the clone split operation.

Workaround:

None.

SnapDrive clone split estimate using Snapshot copy namealong with the - volclone option does not display theunderlying volume names

SnapDrive clone split estimate using Snapshot copy with the -volcloneoption displays the resource name as Snapshot copy names, and if there aremultiple volumes, it is difficult to identify the corresponding estimates for theunderlying volumes.

Workaround:

None.

SnapDrive clone split estimate using the -fs or -dg optiondoes not display the underlying multiple LUNs

When you execute the SnapDrive clone split estimate command by usingthe -fs or -dg option on a FlexClone containing multiple LUNs, it displaysthe file specifications instead of the corresponding underlying LUN names.Therefore, it is difficult to identify the clone split estimation for thecorresponding underlying LUNs.

Workaround:

None.

SnapDrive clone split start operation cannot be performedfor a LUN clone that is inside a FlexClone

When you execute the snapdrive clone split start command, the clonesplit start operation fails for a LUN clone that resides inside the FlexClone.

Workaround:


If you want to perform a clone split start for a LUN clone that is inside aFlexClone, you need to first perform the clone split start operation on thestorage system.

SnapDrive clone split cannot be performed for a LUN clone ifan IP address is specified instead of a storage systemhostname

When you execute the snapdrive clone split start command and if an IPaddress is specified instead of a storage system hostname by using the -lunoption, the clone split start operation fails.

Workaround:

Provide the storage system path along with the IP address in the -lun optionof the snapdrive clone split start command as follows:snapdrive clone split start -lun 10.7.122.7:/vol/vol1/lnx200-106_vol1_lun2-splitmode

Autodetect does not work for more than one LUN in asecondary volume

Autodetect does not work for more than one LUN in a secondary volume.

If you delete more than one LUN in a secondary volume, and execute thesnapdrive storage delete command, SnapDrive for UNIX displays the errormessage Could not detect type of the entity... and deletes only the firstLUN in the secondary volume:

# snapdrive storage delete storagesystem:/vol/user/test1 test2/vol/user/test3 test4Auto detection of file_spec(s) in progress ...- ’storagesystem:/vol/user/test1’ detected as LUN- ’test2’ detected as LUN- ’/vol/user/test3’ detected as LUN9000-305 Command error: Could not detect type of the entity test4. Providea specific option (-lun, -dg, -fs or -lvol) if youknow the type of the entity.

Workaround:

None.

Known Issues 11

SnapDrive log files have read-write permissions only for theroot users

SnapDrive for UNIX log files, such as trace, audit, and recovery, haveread-write permissions only for the root users and read permission for allusers.

Workaround:

None.

Storage show for LUNs fail if volume group is unavailable inAIX® and HP-UX

On AIX and HP-UX hosts, the snapdrive storage show -lun lun_name andthe snapdrive storage show -all commands fail if any volume group on thesystem is inactive (HP-UX) or varied off (AIX).

SnapDrive for UNIX cannot determine the volume groups to which the LUNsbelong. This might be because the command specifies one or more LUNsusing the options -lun and -all, and the volume group might not beavailable, thus the command fails. If you use one of the other commandoptions (-dg, -hostvol, or -fs), the command captures the information for thatentity and returns it. Other forms of the snapdrive storage show commandwork without issues if you do not specify an inactive or varied off volumegroup.

Workaround:

If possible, activate the inactive volume group using the varyon command inAIX and vgchange command in HP-UX. If you have a host cluster, activatingall the volumes might not be practical. In this case, use the snapdrive storageshow command with the -dg, -hostvol, or -fs option rather than the -lun or-all option.

Snapdrive storage delete operation for a LUN hangs in DMPconfiguration.

On hosts with FC and DMP configurations, when you execute the snapdrivestorage delete - lun command, the system hangs for more than 10 minutes.

This issue is caused by incorrect installation or configuration of the followingcomponents:v NTAPaslv Veritas stack (storage foundation)


v Multipathing licenses

Workaround:

Refresh the DMP path information after any FC path is enabled, disabled, oradded. To refresh the DMP path, execute the following commands in thefollowing sequence:v For AIX host:

1. cfgmgr

2. vxdisk scandisk

v For HP-UX host:1. ioscan -fnC disk

2. ioinit -i

3. vxdisk scandisks

v For Solaris host:1. devfsadm -Cv

2. vxdisk scandisk

If a SnapDrive for UNIX daemon stop is followed by adaemon start, the start operation might fail

If SnapDrive for UNIX daemon is started immediately after a stop, sometimesthe start may fail due to child processes waiting on the port for a longerperiod. The waiting period usually depends on the TCP timeouts and the lifeof that child process. In such cases, the daemon cannot use that port and thedaemon start might fail.

Workaround:

Wait until processes in the Time Wait state are timed out. This wait period canbe as long as five minutes.

Note: This issue might occur more frequently on Solaris platforms.

If the Operations Manager server fails to discover LUNs,SnapDrive for UNIX commands fail with an error message"Could not check"

SnapDrive for UNIX commands fail, if the operations manager server fails todiscover the LUNs. The following error message is displayed:0002-332 Admin error: Could not check SD.Storage.Write access on lunstorage_array1:/vol/vol1/lun1 for user unix-host\root on Operations Managerserver(s) ops-mngr-server1

Known Issues 13

Workaround:

None.

Access control permissions for a file does not work asintended

The local access control mechanism does not work as intended. This issueoccurs when the storage system does not contain a vol0.

By default, SnapDrive for UNIX expects to find the permissions file for localaccess control at the path /vol/vol0/sdprbac/sd<hostname>.prbac, where<hostname> is the name of the local host. This problem does not occur if thevol0 file is on the storage system.

Workaround:

None.

Restoring the storage stack on the host after removing aLUN

You should always use the SnapDrive storage commands to remove LUNs.Using external commands to remove LUNs can have an unpredictable effecton the host system.

Workaround:

If you remove a LUN without using a SnapDrive storage command, youshould reboot the host to restore the storage system stack to a known state.You can also restore the host system state by entering the snapdrive snaprestore command, and specifying a Snapshot copy that contains an instanceof the destroyed LUN.

Restoring qtrees in NFS-mounted file systems on SnapMirrordestination

SnapDrive for UNIX does not allow you to restore a Snapshot copy of a qtree,which is mounted on Network File (NFS-mounted) system on a SnapMirrordestination. SnapDrive for UNIX allow you to restore LUNs on qtrees on aSnapMirror destination.

Workaround:

None


Restoring NFS directories with symbolic links

SnapDrive for UNIX fails if you use it to restore an NFS directory thatcontains symbolic links.

Restore operation fails with a message that the file system ismounted

If you unmount the file system and attempt to restore the Snapshot copy, theoperation fails and you get a message indicating that the file system ismounted.

Using a Linux host, you can continuously mount the same file system. Youcan then make a Snapshot copy using SnapDrive for UNIX. The Snapshotcopy, though, contains only the first entry in the mount table for the filesystem. When you issue an unmount command, it unmounts the most recentmountpoint, and not the one shown in the Snapshot copy. When you attemptto restore the Snapshot copy, it fails with a message that the volume is alreadymounted. The following example shows an restore operation of a file systemthat is mounted more than once:

Known Issues 15

# mount /dev/dg3/vol1 /var/tmp/mnts/dg3/vol1# mount /dev/dg3/vol4 /mnt/um1# mount /dev/dg3/vol4 /var/tmp/mnts/dg3/vol4# mount |grep dg3/dev/dg3/vol1 on /var/tmp/mnts/dg3/vol1 type ext3 (rw)/dev/dg3/vol4 on /mnt/um1 type ext3 (rw)/dev/dg3/vol4 on /var/tmp/mnts/dg3/vol4 type ext3 (rw)# snapdrive snap create -dg dg3 -snapname dg3_vol2_snapshotsnap create: snapshot dg3_vol2_snapshot contains:disk group dg3 containing host volumesvol1 (filesystem: /var/tmp/mnts/dg3/vol1)vol2vol3vol4 (filesystem: /mnt/um1)snap create: created snapshot eccentric:/vol/vol1:dg3_vol2_snapshot# snapdrive snap show -v -snapname eccentric:/vol/vol1:dg3_vol2_snapshotsnap namehostdate snapped--------------------------------------------------------------------------------eccentric:/vol/vol1:dg3_vol2_snapshot childs Sep 1 14:14 dg3host OS: Linux 2.4.21-9.ELsmp #1 SMP Thu Jan 8 17:08:56 EST 2004snapshot name: dg3_vol2_snapshotVolume Manager: linuxlvm 1.0.3disk group: dg3host volume: vol1host volume: vol2host volume: vol3host volume: vol4file system: vol1 file system type: ext3mountpoint:/var/tmp/mnts/dg3/vol1file system: vol4 file system type: ext3mountpoint: /mnt/um1lunpathdev paths-------------------------------------------------------eccentric:/vol/vol1/swl14 /dev/sds# snapdrive snap restore -dg dg3 -snapname dg3_vol2_snapshotStarting to restore LUNs in disk group dg3WARNING: This can take several minutes.DO NOT CONTROL-C!If snap restore is interrupted, the disk groupbeing restored may have inconsistent or corrupteddata.For detailed progress information, see the log file /var/log/sd-recovery.logImporting dg3Error (Command error 0001-034): mount failed: mount: /dev/dg3/vol4 alreadymounted or/mnt/um1 busymount: according to mtab, /dev/dg3/vol4 is already mounted on /mnt/um1

Workaround:

Ensure that the file system is mounted only once.


Directory access and ownership rights change during theSnapshot restore operation

NFS directory access and ownership rights change during the Snapshotrestore operation. For nonexistent NFS directories on Data ONTAP 7.0 and 7.1,and for existing and nonexistent NFS directories on Data ONTAP 7.2, thedirectory access and permission rights change from user to root user.

Workaround:

To change the ownership rights, enter the following command at thecommand prompt:chown username directory name

To change the access rights, enter the following command at the commandprompt:chmod permission directory name

Known issues with AIX

Some unexpected and potentially undesired behaviors, as well as, in somecases, workarounds to avoid these behaviors, have been identified in AIX foruse with this release of SnapDrive for UNIX.

SnapDrive storage provisioning commands fail when youspecify both the options -nolvm and -nopersist during filesystem creation

When you create or connect a file system by using both the -nolvm and-nopersist options, snapdrive storage create, snapdrive storage connect,and snapdrive host connect command fail in AIX.

Workaround:

It is recommended to use any one of the options, -nolvm and -nopersist,when creating a file system on an AIX platform.

Known Issues 17


Where to find additional information

The following table describes documents with the most current informationabout host requirements, supported configurations, and procedures forinstalling and managing SnapDrive for UNIX.

If you want... Go to...

The latest supportedconfigurations

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

Configuring and managing thestorage system

The following documents for your Data ONTAPrelease in the Data ONTAP information library:

v The Data ONTAP Software Setup Guide

v The Data ONTAP Block Access Management Guidefor iSCSI and FC

v Data ONTAP Release Notes®

v The Data ONTAP Commands: Manual PageReference, Volume 1

v The Data ONTAP Commands: Manual PageReference, Volume 2

v The Data ONTAP Upgrade Guide

Supported Fibre Channel SANtopologies

The FC and iSCSI Configuration Guide

How to download and installSnapDrive for UNIX

The SnapDrive for UNIX Installation andAdministration Guide

Configuring your host for theHost Utilities

The HP-UX Host Utilities Installation and SetupGuide

The Linux Host Utilities Installation and Setup Guide

The AIX Host Utilities Installation and Setup Guide

The Windows Host Utilities Installation and SetupGuide


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


Websites

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

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

v The IBM System Storage® N series support website requires users toregister in order to obtain access to N series support content on the web. Tounderstand how the N series support web content is organized andnavigated, and to access the N series support website, refer to the followingpublicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well asother important N series product resources.

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

v For the latest N series hardware product documentation, includingplanning, installation and setup, and hardware monitoring, service anddiagnostics, see the IBM N series Information Center at the following webpage:http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp


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

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

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

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


Copyright and trademark information

This section includes copyright and trademark information, and importantnotices.

Copyright information

Copyright ©1994 - 2012 Network Appliance, Inc. All rights reserved. Printedin the U.S.A.

Portions copyright © 2012 IBM Corporation. All rights reserved.

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

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means - graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,


INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

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

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

Trademark information

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

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

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

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express®, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,


FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, ServiceBuilder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

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

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

NetApp, Inc. NetCache is certified RealSystem compatible.

Copyright and trademark information 25


Notices

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

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser's responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

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

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

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

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may make


improvements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

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

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

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

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


Notices 29

��

NA 210-05671_A0, Printed in USA

GC26-7877-15

Documents

SnapDrive 5.0.1 for UNIX Release Notes - IBM