DOT 7 0 Cook Book_Rev1_0.doc Page 118 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
Data ONTAP 7.0 Cook Book
Revision: 1.0
David ThiessenNetApp PSEAustralia
Table of Contents
1 Volume Creation & Exporting..................................................................................................... 4
1.1 Creating Volumes .......................................................................................................................... 4
1.1.1 Software Disk Ownership......................................................................................................... 4
1.1.2 Traditional Volumes ................................................................................................................. 4
1.1.3 Create Aggregates ................................................................................................................... 5
1.1.4 Flex Volumes............................................................................................................................ 5
1.1.5 Create Qtrees........................................................................................................................... 6
1.2 Sharing Volumes & Qtrees ............................................................................................................ 6
1.2.1 NFS exports ............................................................................................................................. 6
1.2.2 CIFS shares ............................................................................................................................. 7
1.3 Using Quotas ................................................................................................................................. 8
2 SAN Implementation.................................................................................................................... 9
2.1 Fiber Channel SAN........................................................................................................................ 9
2.1.1 Enable the Fibre Channel Protocol .......................................................................................... 9
2.1.2 Create a LUN ......................................................................................................................... 10
2.1.3 Access LUNs on a Solaris Host ............................................................................................. 10
2.1.4 Access LUNs on a Windows Host.......................................................................................... 12
2.2 iSCSI SAN ................................................................................................................................... 12
2.2.1 Enable the iSCSI Protocol...................................................................................................... 12
2.2.2 Install SnapDrive for Windows ............................................................................................... 13
2.2.3 Connecting Windows Server to Storage Appliance ............................................................... 13
2.2.4 Create a LUN using SnapDrive.............................................................................................. 14
2.3 Resize a LUN............................................................................................................................... 14
2.4 Access LUN with NFS/CIFS protocols......................................................................................... 14
2.5 Clone a LUN ................................................................................................................................ 15
DOT 7 0 Cook Book_Rev1_0.doc Page 218 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
3 Networking and Appliance Access .......................................................................................... 16
3.1 Creating VLANS........................................................................................................................... 16
3.2 Virtual Interfaces (VIF) ................................................................................................................. 16
3.2.1 Create a VIF ........................................................................................................................... 16
3.2.2 Delete a VIF interface or VIF.................................................................................................. 17
3.3 Using SecureAdmin ..................................................................................................................... 17
3.3.1 Managing SSH ....................................................................................................................... 17
3.3.2 Managing SSL........................................................................................................................ 17
3.4 Using the RLM ............................................................................................................................. 18
3.4.1 Configure the RLM ................................................................................................................. 18
3.4.2 Use the RLM .......................................................................................................................... 18
3.5 Create Local User Accounts ........................................................................................................ 18
4 Snap Applications...................................................................................................................... 20
4.1 Snapshots .................................................................................................................................... 20
4.2 SnapRestore ................................................................................................................................ 20
4.3 Asynchronous SnapMirror ........................................................................................................... 20
4.3.1 Create an Asynchronous Volume SnapMirror Relationship .................................................. 20
4.3.2 Convert a read-only SnapMirror Volume to read-write .......................................................... 21
4.3.3 Resync a Broken Volume SnapMirror Relationship............................................................... 21
4.3.4 Create an Asynchronous Qtree SnapMirror........................................................................... 22
4.3.5 Convert read-only Qtree SnapMirrror to writeable ................................................................. 22
4.3.6 Purging Asynchronous Mirrors............................................................................................... 23
5 Backup & Recovery ................................................................................................................... 24
5.1 Network Data Management Protocol (NDMP) Copy ................................................................... 24
5.1.1 Enable NDMP......................................................................................................................... 24
5.2 ndmpcopy .................................................................................................................................... 24
5.3 Volume Copy ............................................................................................................................... 24
6 Cluster Failover Implementation .............................................................................................. 26
6.1 Enable clustering ......................................................................................................................... 26
6.2 Setup takeover interfaces ............................................................................................................ 26
6.3 Perform cluster takeover/giveback .............................................................................................. 28
6.3.1 Perform Takeover................................................................................................................... 28
6.3.2 Perform Giveback................................................................................................................... 28
7 MultiStore (Vfiler) Implementation ........................................................................................... 30
7.1 MultiStore (Vfiler) Configuration................................................................................................... 30
7.2 MultiStore (Vfiler) Administration ................................................................................................. 30
DOT 7 0 Cook Book_Rev1_0.doc Page 318 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
7.2.1 MultiStore(Vfiler) Stop/Destroy............................................................................................... 31
8 Sample Configuration Files ...................................................................................................... 32
8.1 /etc/quota ..................................................................................................................................... 32
8.2 /etc/rc ........................................................................................................................................... 32
8.3 /etc/exports .................................................................................................................................. 33
8.4 /etc/snapmirror.conf ..................................................................................................................... 33
9 Troubleshooting Commands.................................................................................................... 34
9.1 General Troubleshooting ............................................................................................................. 34
9.2 NFS Troubleshooting ................................................................................................................... 34
9.3 CIFS Troubleshooting .................................................................................................................. 34
9.4 Network Troubleshooting ............................................................................................................. 35
9.5 NDMP Troubleshooting................................................................................................................ 35
9.6 SAN Troubleshooting................................................................................................................... 36
9.6.1 Filer SAN Utilities ................................................................................................................... 36
9.6.2 Solaris SAN Utilities ............................................................................................................... 36
9.6.3 Windows SAN Utilities............................................................................................................ 37
9.6.4 Common SAN Switch Commands ......................................................................................... 37
9.7 Test & Simulation Tools ............................................................................................................... 37
DOT 7 0 Cook Book_Rev1_0.doc Page 418 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
1 Volume Creation & Exporting
1.1 Creating VolumesThe following section describes the procedures to create a traditional and an aggregate volume.
1.1.1 Software Disk OwnershipThe FAS270, FAS6000 series, and V-Series (“gateway”) appliances rely on ownership labels written todisk rather than physical connections. The following section describes how to assign and remove diskownership.
NOTE: Unowned disks cannot be used for data or as spares without being assigned ownership.
Step Command/Action Description
1 NA> disk show -v Display all visible disks and whether theyare owned or not
2 NA> disk show –n Show all unassigned disks
3 NA> disk assign 0b.43 0b.41 Assigns the listed disks to current filerhead
4 NA> disk assign 2a.18 2a.21 –o toaster1 Assigns listed disks to filer namedtoaster1
4NA> disk assign allWarning: Use with caution. Not restricted by Aand B loop in clusters
Assign all unowned disks to current filerhead
5 NA> disk assign <lun_id_list> –c {block | zoned} Assign LUNs to a V-Series
6 NA> disk remove_ownership [ disk_id | all ] Remove disk ownership.
disk assign syntax:disk assign {disk_name | all | -n count } [-p pool] [-o ownername] [-s sysid] [-c block|zoned] [-f]
1.1.2 Traditional VolumesCreate a traditional volume on the storage appliance.
Step Command/Action Description
1NA> vol create vol1 -t raid_dp -r 14 9 Create a volume called "vol1" using
raid_dp, a maximum raid size of 14 diskswith an initial size of 9 disks.
Traditional Volume Syntax:vol create <vol-name> [ -l <language_code> ] [-f] [-n] [-m] [-L] [-t raid4 | raid_dp][-r <raid-group-size>] [-R <rpm>] <disk-list>
1.1.2.1 Add disks to a Traditional Volume
Step Command/Action Description
DOT 7 0 Cook Book_Rev1_0.doc Page 518 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
1 NA> vol status –s Display list of available spare disks and theirdisk IDs
NA> vol add vol2 –d 7.17 7.26 Add disks 7.17 and 7.26 to the volume “vol2”2
NA> vol add vol2 4@72 Add four 72GB disks to volume “vol2”
3 reallocate on
Enable block reallocationOPTIONAL: Temporarily affects performanceand significantly increases snapshotconsumption, but recommended when adding3 or more disks
4 reallocate start –f /vol/vol2 Distributes data evenly across the expandedvolume
1.1.3 Create Aggregates
Step Command/Action Description
1NA> aggr create aggr0 -t raid_dp -r 14 9 Create an aggregate called "aggr0" using
raid_dp, a maximum raid size of 14 diskswith an initial size of 9 disks
Aggregate Syntax:aggr create <aggr-name> [-f] [-n] [-m] [-L] [-t raid4 | raid_dp] [-r <raid-group-size>][-R <rpm>] [-l <language_code>] <disk-list>
1.1.3.1 Add disks to Aggregates
Step Command/Action Description
1 NA> aggr status –s Display list of available spare disks andtheir disk IDs
NA> aggr add aggr0 –d 7.17 7.26 Add disks 7.17 and 7.26 to theaggregate named "aggr0"
2NA> aggr add aggr0 4@72 Add four 72GB disks to aggregate
named “aggr0”
3 reallocate on
Enable block reallocationOPTIONAL: Temporarily affectsperformance and significantly increasessnapshot consumption, butrecommended when adding 3 or moredisks
4 reallocate start –f /vol/vol2 Distributes data evenly across theexpanded aggregate
1.1.4 Flex VolumesCreate a flexible volume on the storage appliance.
DOT 7 0 Cook Book_Rev1_0.doc Page 618 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
Step Command/Action Description
1 NA> df –A aggr0 Displays available free space inaggregate aggr0
2 NA> vol create flex1 aggr0 7g Create a flexible volume called "flex1" onaggregate "aggr0" of size 7GB.
Flexible Volume Syntax:vol create <vol-name> [ -l <language_code> ] [ -s none | file | volume ] <hosting-aggr-name><size>[k|m|g|t]
1.1.4.1 Change size of a FlexVol
Step Command/Action Description
1NA> df –A aggr0 Check size and available space in the
containing aggregate named “aggr0”
NA> vol size vol4 150G Set the size of flexVol “vol4” to 150GB2
NA> vol size vol4 [+ | -] 30G Add or remove 30GB from flexVol “vol4”
1.1.5 Create QtreesCreate a Qtree on the flexible volume.
Step Command/Action Description
1 NA> qtree create /vol/flex1/qt_alpha Create a Qtree called "qt_alpha" onflexible volume flex1
2 NA> qtree security /vol/flex1/qt_alpha [ ntfs | unix]
Configure the security profile for the Qtreeto be NTFS or Unix
1.2 Sharing Volumes & QtreesThe following section describes procedures to export volumes or qtrees via NFS or CIFS.
1.2.1 NFS exports1. On Filer: Create new NFS volume and export it:
Step Command/Action Description
1 NA> vol create flex2 aggr0 size 7g Create new volume for Unix Share
2 NA> qtree security /vol/flex2 unix Configure Qtree Security Settings
NA> exportfs -i -o rw,root=adminhost /vol/flex2 Immediately create export.3 Edit /etc/exports file:
/vol/flex1 -rw,root=adminhostMake export persistent
4 NA> exportfs -a Activate all entries in /etc/exports file
DOT 7 0 Cook Book_Rev1_0.doc Page 718 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2. On UNIX Server: Create new mount point and mount export:
Step Command/Action Description
6 # showmount -e fbfiler2 Verify available mounts on FBFiler2
7 # mkdir /mnt/fbfiler2/unix_vol Create a mount point
8 # mount fbfiler2:/vol/flex2 /mnt/fbfiler2/unix_vol Mount the Unix export from filer FBFiler2
9 # cd /mnt/fbfiler2/unix_vol Change to new mount point
10 # ls -al Verify mount was successful
11 Add mount command and options to /etc/vfstab(Solaris) or /etc/fstab (HP-UX, Linux)
Make mount persistent
Note: If you change the name of the exported volume or qtree you must update /etc/exports on thefiler and the /etc/fstab or /etc/vfstab file on the host.
1.2.2 CIFS shares1. On Filer: Create new CIFS volume and export it:
Step Command/Action Description
1 NA> vol create flex_cifs aggr0 size 7g Create new volume for CIFS Share
2 NA> qtree security /vol/flex_cifs ntfs Configure Qtree Security Settings
3 NA> cifs setup Run CIFS setup wizard
* Configure WINS* Enter hostname for storage appliance* Set CIFS authentication (Domain, Workgroupor local)* Enter Windows Domain name* Enter Windows 2000 user ([email protected])* Enter Administrator password* Accept default AD container account
4 NA> cifs testdc Establish connection with Domaincontrollers.
5 NA> cifs shares -add cifs_share /vol/flex_cifs -comment 'New CIFS Share'
Create a CIFS share called "cifs_share"
6 (NA> cifs access cifsTeam Full Control) Set access rights to provide the cifsTeamwith full control rights to the share
2. On Windows Server:
Step Command/Action Description
7 * Log into Windows 2000 domain controller asAdministrator
Create a new user in the Domain ifapplicable
DOT 7 0 Cook Book_Rev1_0.doc Page 818 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
Administrator* Start -> Programs -> Administrative Tools ->Active Directory Users and Computers. Click on"Action", select "New" then "User"* Create a new user to access the filer.
applicable
8
* Open Computer Management:Start -> Programs -> Administrative Tools ->Computer Management* Click on Action and select "Connect to anothercomputer…". Enter the name of the storageappliance* System Tools -> Shared Folders -> Shares
View the available shares on the storageappliance
9* At the Windows desktop, right click on MyNetwork Places, select Map Network Drive* \\fbfiler2\cifs_share
Map the storage appliance's cifs_sharefolder to the server
Note: If you change the name of the shared volume or qtree the share will still be accessible becauseCIFS tracks an unique SSID rather than the pathname.
1.3 Using QuotasThe following section describes the commands uses to manage qtree and volume quotas.
Step Command/Action Description
1 quota on /vol/vol2
Enables quotas if /etc/quotas exists orimplements changes in /etc/quotas forvol2(See section 8 for example /etc/quotas)
2 quota resize Implements changes made to /etc/quotas
3 quota reportprints the current file and spaceconsumption for each user or group with aquota and for each qtree.
DOT 7 0 Cook Book_Rev1_0.doc Page 918 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2 SAN ImplementationThe following section provides a summary of the procedures to enable access to a LUN on the storageappliance using either the Fibre Channel Protocol or iSCSI protocol.
2.1 Fiber Channel SANThe following section describes how to access a LUN using the Fibre Channel Protocol.
2.1.1 Enable the Fibre Channel Protocol1. Enabling the Fibre Channel Protocol on a Storage Appliance
Step Command/Action Description
1 NA> license add <license_key> Add FCP License
2 NA> fcp start Start the FCP service
3NA> sysconfig -v Locate Fibre Channel Target Host
Adapter. Note FC Nodename and FCPortname for each.
4 NA> fcp show cfmode Display the Fibre Channel interface mode
2. Enabling the Fibre Channel Protocol on a Solaris Server
Step Command/Action Description
1 # /driver_directory/install Install the Fibre Channel Card driverapplication
2 # reboot -- -r Restart the Solaris server to enable thenew hardware device
3 # sanlun fcp show adapter -v Show full details of the Fibre Channelcard on the server
4# /usr/sbin/lpfc/lputil Light Pulse Common Utility to get
information regarding Emulux hostadapters.
3. Enabling the Fibre Channel Protocol on a Windows Server
Step Command/Action Description
1 Locate the host adapter driver and install on theWindows server
Install the Host Adapter driver
2 Start -> Shutdown -> Restart Restart the Windows Server
3C:\WINNT\system32\lputilnt.exe Run Light Pulse Common Utility to gather
detailed information regarding the hostadapter
DOT 7 0 Cook Book_Rev1_0.doc Page 1018 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2.1.2 Create a LUN1. Creating a LUN on the Storage Appliance
Step Command/Action Description
1
Create a LUN:* lun create, igroup create, lun map* lun setup* FilerView -> LUNs -> Wizard
Create a LUN on the storage appliancemanually, via a CLI script, or throughFIlerView.
2
Enter LUN details during setup process:* LUN Path: /vol/flex1/QTUser/UserLun* LUN Size: 2g* Space-reserved: Yes* Protocol: Solaris* Description: User LUNa* iGroup Name: UserIG* iGroup Type: FCP* OS: Solaris* Add Initiator to iGroup: WWNN of Solarishost adapter
* Add LUN ID for iGroup Initiator
Enter the appropriate details for the LUN
Note: NA> fcp show adaptersNA> fcp show initiators
2.1.3 Access LUNs on a Solaris Host
Step Command/Action Description
1 # cd /opt/NTAPsanlun/bin Change to the directory of the NetAppHBA Attach Kit
2
# ./create_binding.pl -l root -n <filer_ip> Run the Perl script to locate the portsavailable on the filer.Note: Do not reboot the server at thecompletion of the script.
3 # cat /kernel/drv/lpfc.conf | more View the file to verify the bindingscreated.
4# /usr/sbin/lpfc/lputil
- Select "5. Persistent Bindings"- Select "1. Display Current Bindings"
View the persistent bindings
5# vi /kernel/drv/sd.conf
Entry e.g:name="sd" parent="lpfc" target="0" lun=1;
Update the sd.conf file with newly boundLUN target and LUN ID values.
6 # reboot -- -r Reboot the Solaris server.
7# sanlun lun show Verify the new LUN can be viewed from
the Solaris server. Locate and record thecontroller, target, disk and slice
DOT 7 0 Cook Book_Rev1_0.doc Page 1118 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
information of the LUN.
8# devfsadm# sanlun lun show
If the devices are not located, re-scan fordevices. Check again for the LUN.
9 # reboot -- -r If required, reboot the Solaris server.
10
# format* Select the appropriate disk* Disk not labeled. Label it now? Y* format> partition* partition> modify* "1. All Free Hog"* Create the new partition? <CR>* Free Hog partition [6]? <CR>* Enter size of partition '0': 1c (1 Cylinder)* Enter size of partition '1': <CR>
…* Enter size of partition '7': <CR>* Okay to make this the current partitiontable [yes]? <CR>
* Enter table name: "multiprotocol"* Ready to label disk, continue? Y* partition> print* partition> quit* format> quit
Run the Solaris format command tocreate Solaris file system on the newLUN.
11# sanlun lun show Display a list of available LUNs. Locate
and record the controller, target, disk andslice information of the LUN.
12 # newfs /dev/rdsk/c1t1d0s6 Construct a new file system on the newLUN.
13 # mkdir /mnt/slu2-luna Create a mount directory for the LUN
14 # mount /dev/dsk/c1t1d0s6 /mnt/slu2-luna Mount the new LUN
15 # cd /mnt/slu2-luna Change to the mount point directory andverify the new
DOT 7 0 Cook Book_Rev1_0.doc Page 1218 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2.1.4 Access LUNs on a Windows HostOption 1: Use Computer Management to search for a pre-defined LUN.
Step Command/Action Description
1Open Computer Management:Start -> Programs -> Administrative Tools ->Computer Management
Use the Computer Management consoleto view available LUNs
2 Storage -> Disk Management View current local disks
3Right click on Disk Management and select"Rescan Disks"
Rescan for any new disks. The filer's LUNshould appear automatically in the list ofavailable drives.
4 Right click on the new disk and select CreatePartition and format the new disk
Create a partition and format it.
Option 2: Use SnapDrive to create and attach to an FCP LUN.
Step Command/Action Description
1Open Computer Management:Start -> Programs -> Administrative Tools ->Computer Management
Use the Computer Management console
2 Storage -> SnapDrive -> Disks View the available disks via theSnapDrive manager
3 Right click on Disk and select "Create disk" Create a new LUN via SnapDrive
4 Via the SnapDrive wizard, enter the details of thenew LUN
Enter the details of the new LUN
2.2 iSCSI SANThe following section describes how to access a LUN on a storage appliance using the iSCSI Protocol.
2.2.1 Enable the iSCSI Protocol1. Enabling the iSCSI Protocol on a Storage Appliance
Step Command/Action Description
1 NA> license add <license_key> Add iSCSI License
2 NA> iscsi start Start the iSCSI service
3 NA> ifconfig -a Determine the IP address that theappliance will be using for iSCSI
4 NA> iscsi interface show Display iSCSI network interfaceinformation for the appliance
5 NA> iscsi initiator show Display iSCSI initiator information for theappliance
DOT 7 0 Cook Book_Rev1_0.doc Page 1318 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2. Enabling the iSCSI Protocol on the Windows Server
Step Command/Action Description
1 Download the "Microsoft iSCSI Initiator" driverand install on the Windows server
Install the "Microsoft iSCSI Initiator" driver
2 Start -> Shutdown -> Restart Restart the Windows Server
2.2.2 Install SnapDrive for WindowsThe following section provides instructions to install and use the SnapDrive snap-in for MicrosoftWindows.
Step Command/Action Description
1 Locate the "NetApp SnapDrive for MicrosoftWindows" application and install it on theWindows server
Install the "NetApp SnapDrive forMicrosoft Windows" application
2 Start -> Programs -> Administrative Tools ->Computer Management
Load Computer Management
3 Computer Management (Local) -> Storage ->SnapDrive
Access SnapDrive
2.2.3 Connecting Windows Server to Storage ApplianceThe following section provides procedures to connect from the Windows Server to the StorageAppliance using the iSCSI protocol.
Step Command/Action Description
1Start the "Microsoft iSCSI Initiator" applicationvia the desktop shortcut.
MS iSCSI Initiator provides local serverInitiator details and enables connectionsto remote Target adapters.
2
Target Portals panel: Click Add and enter:* Storage Appliance IP Address* Socket (3260)* Adapter (default)* Port (default)
Configure Storage Appliance IP addressand port details.
3Available Targets panel: Storage Appliancetarget adapter should be listed. Click "Log On" toconnect to the Storage Appliance
Connect to the Storage Appliance
4Persisten Target panel: Storage Appliance targetadapter should now be visible in the persistenttargets list.
Storage Appliance should now be apersistent connection
5Active Targets panel: Storage Appliance targetadapter should now be visible in the persistenttargets list and "Connected" to.
Storage Appliance should now be anActive connection
6 NA> iscsi show initiator Windows host server initiator shold nowbe available from the Storage Appliance
DOT 7 0 Cook Book_Rev1_0.doc Page 1418 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
2.2.4 Create a LUN using SnapDriveOnce the Windows server is connected to the Storage Appliance via iSCSI, use SnapDrive to create anew LUN.
Step Command/Action Description
1NA> qtree create /vol/vol1/LunQTreeNA> cifs shares -add LunQTree
/vol/vol1/LunQTree
Create a Qtree for the new Windows LUNto be defined and create a share for it.
2
Using SnapDrive, right click on "Disks" andselect "Create Disk". Enter the following details:
* Virtual Disk UNC Path: /vol/vol1/LunQTree* Virtual Disk (LUN) Name: Xluna* Virtual Disk Type: Dedicated* Disk Space to Accommodate Snapshot(Space-reserved): Yes
* Lun Size: 2g* Driver Letter: <any>* Select initiator for Windows Host
Create a LUN using SnapDrive
3 NA> lun show -m Verify the LUN wa created on the StorageAppliance
4Use Windows Explorer to verify the disk isavailable. If not, log off and then back on to theserver again.
Verify the drive is ready for use. Note:SnapDrive auto-formats the drive, nofurther management should be required.
2.3 Resize a LUNThe following section describes the procedure to change the size of a LUN
Step Command/Action Description
1 NA> df –k /vol/data Check free space available in the volumecontaining the LUN
2 NA> lun offline /vol/data/qtree1/lun2 Offline the LUN named lun2
3 NA> lun resize /vol/data/qtree1/lun2 15g Changes the size of the LUN to 15 GB
4 On the host, rescan or rediscover the LUN
2.4 Access LUN with NFS/CIFS protocolsThe following section describes the procedure to access a LUN from an NFS mount or CIFS share.
NOTE: By default the LUN is read-only. The LUN must be unmapped from FCP/iSCSI targets andtaken offline to be writeable.
Step Command/Action Description
1 NA> lun share /vol/data/lun2 [none|read|write|all] Makes the LUN named lun2 accessible byNFS or CIFS and assigns the designated
DOT 7 0 Cook Book_Rev1_0.doc Page 1518 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
NFS or CIFS and assigns the designatedpermissions.
2.5 Clone a LUNThe following section describes the procedure to clone a LUN using Data ONTAP 7.0.
Step Command/Action Description
1 NA> lun show -v Display list of current LUNs
2 NA> snap create vol1 mysnap Take a snapshot of the volume containingthe LUN to be cloned.
3NA> lun clone create
/vol/vol1/LunQTree/Xluna.clone -b/vol/vol1/LunQTree/Xluna mysnap
Clone the existing LUN, entering thedestination LUN name, source LUN nameand most recent snapshot.
4NA> lun clone split start
/vol/vol1/LunQTree/Xluna.cloneSplit the clone from the source Snapshot.
5NA> lun create status
/vol/vol1/LunQTree/Xluna.cloneVerify LUN cloning progress
6 NA> snap delete vol1 mysnap Delete source snapshot
DOT 7 0 Cook Book_Rev1_0.doc Page 1618 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
3 Networking and Appliance Access
3.1 Creating VLANSThe following section describes the process of spanning an interface across multiple networks or sub-domains with a VLAN.
NOTE: VLAN commands are NOT persistent across a reboot and must be added to the /etc/rc file tobe permanently configured. See the example /etc/rc in section 8.2.
Step Command/Action Description
1 NA> ifconfig –a show configuration of all networkinterfaces
2 NA> vlan create e4 10 20 30 Create three VLAN identifiers on interfacee4
3 NA> vlan add e4 40 Add fourth VLAN identifier to interface e4
4 NA> ifconfig e4-10 172.25.66.11 netmask255.255.255.0
Configure the VLAN interface e4-10
5 NA> vlan delete e4 e4-40 Delete VLAN identifier e4-40 frominterface e4
6 NA> vlan delete e4 Delete all VLANs on interface e4
3.2 Virtual Interfaces (VIF)The following section describes the process of trunking multiple network interfaces (link aggregation)into a virtual interface.
NOTE: VIF commands are NOT persistent across a reboot and must be added to the /etc/rc file to bepermanently configured. See the example /etc/rc in section 8.2.
3.2.1 Create a VIFThe commands in this section should be run from a console connection because they require downingnetwork interfaces prior to aggregating them.
Step Command/Action Description
1Ensure the network port switches are configuredto support trunking
On a Cisco Catalyst switch use setport channel commands
2 NA > ifconfig <interfaces> down Down the network interfaces to trunk
NA> vif create {single | multi} <vif_name><interface_list>
3e.g.:
vif create multi MultiTrunk1 e0 e1
Create a single or multi-mode VIF fromthe list of network interfaces.single – only one interface activemulti – all interfaces are active
4 NA> ifconfig MultiTrunk 172.25.66.10 Assign an IP address to the VIF
DOT 7 0 Cook Book_Rev1_0.doc Page 1718 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
5 NA> vif favor e0 Set the interface e1 to be theprimary/active VIF interface
6 NA> vif nofavor e1 e1 became active when e0 failed. Now e0is repaired and should be the primary.
7 NA> vif stat <vif_name> <interval> Display usage statistics of a VIF
3.2.2 Delete a VIF interface or VIFNote: Remove or edit the VIF creation entries in /etc/rc to make these changes persistent
Step Command/Action Description
1 NA> ifconfig Trunk1 down Down the VIF named “Trunk1”
2 NA> vif delete Trunk1 e4 remove interface e4 from the VIF “Trunk1”
3 NA> vif destroy Trunk1 Delete the entire VIF
3.3 Using SecureAdminSecure Admin is included in ONTAP 7.x and provides for secure network connections to a storageappliance for the CLI and FilerView.
3.3.1 Managing SSHThe following section describes configuring SSH to provide secure connections to the CLI.
Step Command/Action Description
1 NA> secureadmin setup ssh Configures the SSH protocol
2 NA> secureadmin enable {ssh1 | ssh2} Turn on the SSH protocols
3 NA> secureadmin disable {ssh1 | ssh2} Turn off the SSH protocols
3.3.2 Managing SSLThe following section describes configuring SSH to provide secure HTTP connections to FilerView.
Step Command/Action Description
1 NA> secureadmin setup ssl Configures the SSL protocol
2 NA> secureadmin addcert ssl <directory_path> OPTIONAL: Install a certificate-authority-signed certificate
3 NA> secureadmin enable ssl Turn on the SSL protocol
4 NA> secureadmin disable ssl Turn off the SSL protocol
DOT 7 0 Cook Book_Rev1_0.doc Page 1818 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
3.4 Using the RLMThe following sections describes configuring and using the Remote LAN Module (RLM) on newerseries storage appliances (FAS3000, FAS6000)
3.4.1 Configure the RLM
Step Command/Action Description
1 NA> rlm setup Configure the network interface
2 NA> rlm status Verify proper functioning
3NA> options autosupport.to
options autosupport.mailboxCheck for autosupport addressees andmail server information
4 NA> rlm test autosupport Send a test ASUP to verify networksettings
5 NA> rlm reboot Reset RLM and force self-test
3.4.2 Use the RLMThe following section describes how to perform remote management of a problematic or down storageappliance.
Step Command/Action Description
1 Telnet or SSH to the RLM network port The RLM port is active even when anappliance is halted or without power
2 RLM NA> rlm sensors –c Get current values of environmentalsensors
3 RLM NA> system console Access the system console CLI
4 RLM NA> system core Dump system core and reset theappliance
5 RLM NA> system reset {primary | backup |current}
Reset the appliance using the specifiedfirmware image
6 RLM NA> system power { on | off | cycle } Turn power on, off, or off and back on(performs a dirty shutdown)
3.5 Create Local User AccountsThe following section describes how to create user accounts on a storage appliance such as for useby a Support Console or for NDMP backups.
Step Command/Action Description
1 NA> useradmin user list Display list of current user accounts
2 NA> useradmin user add sc200 -gAdministrators
Create a new user account named sc200
DOT 7 0 Cook Book_Rev1_0.doc Page 1918 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
3 NA> useradmin user delete ndmp Remove the user account named “ndmp”
4 NA> passwd Change a local user account password
DOT 7 0 Cook Book_Rev1_0.doc Page 2018 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
4 Snap ApplicationsThe following section will introduce some of the available snap-applications.
4.1 SnapshotsThe following section describes the creation of a snapshot and the snap restore of a file or volume.
Step Command/Action Description
1 NA> snap create vol1 mysnap Create a snapshot of volume vol1
2 NA> snap list vol1 List all snapshots for vol1
3NA> snap delta vol1 [snap1 snap2] Show the amount of change between
snapshots on vol1 (or between 2snapshots)
4 NA> snap reclaimable vol1 snap1 [snap2 …] List amount of space freed if listedsnapshot(s) were deleted
5 NA> snap rename vol1 old_name new_name Rename a snapshot in vol1
6 NA> snap delete vol1 snap1 Delete snapshot snap1 in vol1
4.2 SnapRestoreThe following sections describes how to do restores with the licensed product SnapRestore
Warning: All file changes and snapshots created after the snapshot used for the snap restore will bepermanently lost
Step Command/Action Description
1 NA> snap restore -t file /vol/vol1/etc/rc Snap Restore specific file from snapshot
2 NA> snap restore -t vol vol1 –s weekly.1 Snap Restore entire volume from aweekly Snapshot
Command syntax:snap restore [ -t file|vol] [-s snapshot_name] [ -r restore_as_path] vol_name
4.3 Asynchronous SnapMirror
4.3.1 Create an Asynchronous Volume SnapMirror RelationshipThe following section describes the procedure to set up asynchronous Volume SnapMirror betweentwo Storage Appliances.
Step Command/Action Description
1 NA> license add <snapmirror_code> License snapmirror on the source anddestination Storage Appliance.
2NA-1> df –k vol1NA-2> df –k vol1
Ensure destination volume is equal to orlarger than source volume. In thisexample, NA-1 is the source and NA-2 is
DOT 7 0 Cook Book_Rev1_0.doc Page 2118 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
the destination filer.
3 NA-1> vol options vol1 convert_ucode on Set the source volume to Unicode ON forsource volumes that support CIFS clients
4 NA-1> vol status vol1 Verify volume status and unicode setting
5 NA-2> vol restrict vol1 Restrict the destination volume
6 NA-2> vol status vol1 Verify volume is now restricted
7NA-1> options snapmirror.access host=NA-2NA-2> options snapmirror.access host=NA-1
Allow snapmirror access by each filer tothe other.
8
NA-2> wrfile /etc/snapmirror.confNA-1:vol1 NA-2:vol1 - * * * *orNA-1:vol1 NA-2:vol1 – 0-55/5 * * *(every 5 mins of every hour)
Create a snapmirror schedule on thedestination filer defining when tosynchronise (Min of Hr, Hr of Day, Day ofMth, Day of Wk)
9NA-1> snapmirror onNA-2> snapmirror on
Enable snapmirror on both the source anddestination filers
10NA-2> snapmirror initialize -S NA-1:vol1 NA-2:vol1
Initialize transfer of files from source todestination filer and create a baselinefrom which to mirror.
11 NA-2> snapmirror status -l Verify status of transfer or of mirror
4.3.2 Convert a read-only SnapMirror Volume to read-writeThe following section will describe the procedure to convert the read-only destination copy of a mirrorinto a stand-alone copy.
Step Command/Action Description
2NA-1> snapmirror status (if possible)NA-2> snapmirror status
Verify the status of the snapmirrors
3 NA-2> snapmirror break NA-2:vol1 Break volume vol1 from the snapmirrorrelationship
4.3.3 Resync a Broken Volume SnapMirror RelationshipThe following section describes the steps to re-synchronise a broken snapmirror relationship.
Step Command/Action Description
1 NA-2> rdfile /etc/snapmirror.conf Verify snapmirror schedule is still valid
2NA-1> vol status vol1NA-2> vol status vol1
Verify both volumes are online and read-writeable.
3NA-1> snapmirror onNA-2> snapmirror on
Turn on SnapMirror for both filers
4 Ensure all client activities to the volumes arehalted
All applications and users accessing thefilers must be stopped.
DOT 7 0 Cook Book_Rev1_0.doc Page 2218 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
5NA-1> snapmirror resync -S NA-2:vol1 NA-1:vol1 From the original source filer, perform a
resync of the data from the originaldestination filer
6 NA-1> snapmirror update -S NA-2:vol1 NA-1:vol1
Update any changes since the baselinesnapshot of the resync
7NA-1> snapmirror break NA-1:vol1 Break the current snapmirror relationship
so it can be reversed and set to itsoriginal direction.
7aNA-1> snapmirror quiesce NA-1:/vol/vol1/mytreeNA-1> snapmirror break NA-1:/vol/vol1/mytree
For Qtrees, the snapmirror must be firstquiensced and then broken.
8 NA-2> snapmirror resync -S NA-1:vol1 NA-2:vol1 Perform a second resync, setting NA-1 asthe source again.
8aNA-2> snapmirror resync -SNA-1:/vol/vol1/mytree NA-2:/vol/vol1/mymirror
Perform a second resync on a Qtree.
4.3.4 Create an Asynchronous Qtree SnapMirrorThe following section describes the procedure to set up asynchronous Qtree SnapMirror between twoStorage Appliances.
Step Command/Action Description
1 NA> license add <snapmirror_code> License snapmirror on the source anddestination Storage Appliance.
2NA-1> options snapmirror.access host=NA-2NA-2> options snapmirror.access host=NA-1
Allow snapmirror access by each filer tothe other.
3NA-1> snapmirror onNA-2> snapmirror on
Enable snapmirror on both the source anddestination filers
4NA-2> snapmirror initialize -S
NA-1:/volvol1/mydataNA-2:/vol/backup_vol/mydata_copy
Initialize transfer of files from source todestination filer and create a baselinefrom which to mirror.
5 NA-2> snapmirror status -l Verify status of transfer or of mirror
6
NA-2> wrfile /etc/snapmirror.confNA-1:/volvol1/mydataNA-2:/vol/backup_vol/mydata_copy - 10 * * *
Create a snapmirror schedule on thedestination filer defining when tosynchronise (Min of Hr, Hr of Day, Day ofMth, Day of Wk)
4.3.5 Convert read-only Qtree SnapMirrror to writeableThe following section describes the process of making a destination qtree writeable.
Step Command/Action Description
1 NA-2> snapmirror status Verify the status of the snapmirrors.SnapMirror must be on.
2 NA-2> snapmirror quiesce /vol/vol0/mymirror Finishes any write activity and thendisables further updates
DOT 7 0 Cook Book_Rev1_0.doc Page 2318 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
3 NA-2> snapmirror break NA-2:/vol/vol0/mymirror Break the snapmirror relationship
4.3.6 Purging Asynchronous MirrorsThe following section describes how to purge asychronous snapmirror sessions.
Step Command/Action Description
1 NA> wrfile /etc/snapmirror.conf Remove redundant entries
2NA> snapmirror quiesce <dst_qtree>NA> snapmirror break <dst_vol_or_qtree>
Quiesce any qtree snapmirrors and breakSnapMirror relationships.
3 NA> snapmirror destinations Display any snapmirror destinations
4 NA> snapmirror release <src_path><dst_filer>:<dst_path>
Release the source associated withsnapmirror relationships.
5NA> snap list <vol>NA> snap delete <vol> <snapshot>
List and delete any snapshots that are forredundant snapmirror relationships.
6 NA> snapmirror off Disable snapmirror on source anddestination filers if appropriate.
DOT 7 0 Cook Book_Rev1_0.doc Page 2418 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
5 Backup & Recovery
5.1 Network Data Management Protocol (NDMP) CopyNDMP is an open standard allowing backup applications to control native backup and recoveryfunction in NetApp and other NDMP servers.
5.1.1 Enable NDMPThe following describes the steps to enable NDMP on a filer.
Step Command/Action Description
1NA> ndmpd on ORNA> options ndmpd.enable on
Enable NDMP on the filer
2 NA> options ndmpd.connectlog.enable on Enable the NDMP Connection Log
3 NA> options ndmpd.access host=10.20.20.16 List the hosts that may access the filer viaNDMP
4NA> options ndmpd.authtype Configure the authorisation method for
NDMP access (Challenge and/orplaintext)
Note: Debugging NDMP connection: "ndmpd debug 50"
5.2 ndmpcopyThe following section describes how to copy volumes, qtrees or single files between filers or on asingle filer (to migrate data between traditional and flexvols)
Step Command/Action Description
1NA> ndmpcopy NA1:/vol/data/my_stuffNA2:/vol/users/
Copies the qtree my_stuff on filer NA1 tothe volume /vol/users on filer NA2
5.3 Volume CopyVolume copy is a block-level copy of a volume, and optionally its SnapShots, to another volume ofequal or greater size. The destination volume may be on the same filer or a remote filer.
Step Command/Action Description
1 NA-2> vol restrict destination_vol Restrict the destination volume
2 NA-2> options rsh.enable on Enable RSH on the destination filer
3 - Add an entry in /etc/hosts.equiv on both filersfor the other filer
Create a trusted relationship between thefilers
4
NA> vol copy start [-S] source_volNA2:destination_vol ORNA> vol copy start [-S] source_voldestination_vol
Start copying the source volume (and it’sSnapShots with –S) to the destinationvolume on a local or remote filer
DOT 7 0 Cook Book_Rev1_0.doc Page 2518 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
5 NA> vol copy status Check on progress of vol copy operation
6NA> options vol.copy.throttle [value] Optional: Set the speed of the copy from
1 (10%) to 10 (100%) to reduce impact onnetwork traffic
7 NA> vol copy abort [operation_number] Cancel one or more volume copyoperations
DOT 7 0 Cook Book_Rev1_0.doc Page 2618 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
6 Cluster Failover ImplementationThe following section will demonstrate a basic cluster setup and failover using a Shared interfaceconfiguration. See Netapp® Hardware Cluster Guide and Netapp® System Administration Guidefor more details.
6.1 Enable clusteringThese are the necessary steps to enable clustering.
Step Command/Action Description
1NA-1> license add <cluster_code>NA-2> license add <cluster_code>
Add cluster license to both clusterpartners (“nodes”)
2NA-1> rebootNA-2> reboot
Reboot both partners
3 NA-1> cf enable Enable clustering
4NA-1> cf statusCluster enabled, filer 2 is up.
Check status of cluster
5NA-1> fcstat device_mapNA-2> fcstat device_map
Ensure both partners can access theother partner’s disks
6.2 Setup takeover interfacesThis section will describe two methods to setup the network interfaces with the partner’s IPinformation.
Option 1: Use setup command
Step Command/Action Description
1
Gather network information on both nodes
IP address for local and partner node
Netmask for local and partner node
Example:Local IP/Netmask:
10.41.72.103/255.255,255.0Partner IP/Netmask:
10.41.72.104/255.255.255.0
2
NA-1> setupPlease enter IP address for Network Interfaces e0 [n.n.n.n]: 10.41.72.103Please enter netmask [255.255.255.0]:Should Interface e0 take over a partner IP address during failover? [y]: yPlease enter the IP address to take over: [m.m.m.m]: 10.41.72.104
Setup Local node’s takeoverinterface information.n.n.n.n = local node ip addressm.m.m.m = partner node ipaddress
3
NA-2> setupPlease enter IP address for Network Interfaces e0 [n.n.n.n]: 10.41.72.104Please enter netmask [255.255.255.0]:Should Interface e0 take over a partner IP address during failover? [y]: yPlease enter the IP address to take over: [m.m.m.m]: 10.41.72.103
Setup partner’s takeoverinterface information.
DOT 7 0 Cook Book_Rev1_0.doc Page 2718 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
4
NA-1> ifconfig e0e0:flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM>mtu 1500
inet 10.41.72.103 netmask 0xffffff00 broadcast 10.41.72.255partner inet 10.41.72.104 (not in use)ether 00:0e:0c:2e:f8:54 (auto-1000t-fd-up) flowcontrol full
Check interface for partnerconfiguration
Option 2: Use ifconfig command. Typically used if setup has already been completed.
Step Command/Action Description
1
Gather network information on both nodes
IP address for local and partner node
Netmask for local and partner node
Example:Local IP/Netmask:
10.41.72.103/255.255.255.0Partner IP/Netmask:
10.41.72.104/255.255.255.0
2
NA-1> ifconfig e0 10.41.72.103 partner 10.41.72.104NA-2> ifconfig e0 10.41.72.104 partner 10.41.72.103orNA-1> ifconfig e0 partner 10.41.72.104NA-2> ifconfig e0 partner 10.41.72.103
Setup local and partner nodeinterfaces for partner takeover
3Modify /etc/rcifconfig e0 `hostname`-e0 mediatype auto flowcontrol full netmask255.255.255.0 partner 10.41.72.104
Make change in step 2persistent across reboots
4
NA-1> If config e0e0:flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 10.41.72.103 netmask 0xffffff00 broadcast 10.41.72.255partner inet 10.41.72.104 (not in use)ether 00:0e:0c:2e:f8:54 (auto-1000t-fd-up) flowcontrol full
NA-2> if config e0e0:flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 10.41.72.103 netmask 0xffffff00 broadcast 10.41.72.255partner inet 10.41.72.103 (not in use)ether 00:0e:0c:2e:f8:54 (auto-1000t-fd-up) flowcontrol full
Check interfaces for partnerconfiguration
DOT 7 0 Cook Book_Rev1_0.doc Page 2818 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
6.3 Perform cluster takeover/giveback
6.3.1 Perform Takeover
Step Command/Action Description
1NA-1> cf takeover[lots of console messages]takeover completed
Local node takes over partnernode
2 Make sure clients can still access data Verify data access via licensedprotocols
3
NA-1> ifconfig e0e0:flags=9e8043<UP,BROADCAST,RUNNING,MULTICAST,MULTIHOST,PARTNER_UP,TCPCKSUM> mtu 1500
inet 10.41.72.103 netmask 0xffffff00 broadcast 10.41.72.255partner inet 10.41.72.104 (e0)ether 00:0e:0c:2e:f8:54 (auto-1000t-fd-up) flowcontrol full
Check interface
4
NA-1> cf statusfiler1(takeover)> cf statusfiler1 has taken over filer2.Takeover due to negotiated failover, reason: operator initiated cftakeover
Check cluster failover status
5NA-1> partner Switch to partner’s CLI context
6
filer2/filer1> sysconfig -v*** This system has been taken over by filer3
NetApp Release 7.1: Fri Dec 23 02:32:04 PST 2005System ID: 9950393031 (filer4); partner ID: 9950393390 (filer3)System Serial Number: 9990073 (filer2); partner Serial
Number: 9990079 (filer1)System Rev: C2
No hardware device information is available.
Simple check to verify filer 1has taken over partner
6.3.2 Perform Giveback
Step Command/Action Description
1
filer1(takeover)> cf giveback[lots of console messages]Cluster monitor: takeover of filer2 enabled
Partner node reboots and functions normallyNote: It is sometimes necessary to run cf giveback–f to terminate certain services that will prevent agiveback. Read docs for more details.
2 Make sure clients can still access data Verify data access via licensed protocols
3 NA-1> cf statusCluster enabled, filer2 is up.
Check cluster failover status
DOT 7 0 Cook Book_Rev1_0.doc Page 2918 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
Cluster enabled, filer2 is up.
DOT 7 0 Cook Book_Rev1_0.doc Page 3018 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
7 MultiStore (Vfiler) ImplementationThis section will introduce a simple MultiStore implementation of a Vfiler. A Vfiler is logical partitioningof the resources of a storage appliance. Each Vfiler has its own security domain.
7.1 MultiStore (Vfiler) ConfigurationThis section will demonstrate how to create a vfiler.
Step Command/Action Description
1 license add <multistore_code> License MultiStore
2ifconfig e0 0.0.0.0ifconfig e0 down
interfaces used with vfilersmust not be assigned an ipaddress and must be down
3 ipspace create vfiler1-ipspace Create an IPspace
4 ipspace assign vfiler1-ipspace e0 Assign an interface to theIPSpace
5 vol create vol1 Create storage to assign tothe Vfiler
6 vfiler create vfiler1 –s vfiler1-ispace –i 10.41.72.113 /vol/vol1 Create a Vfiler
7* ifconfig e0 10.41.72.113 up netmask 255.255.255.0mediatype 100tx-fd
Assign appropriate IP toassigned interface
8* vfiler run vfiler1 route add default 10.41.72.1 Assign a default route to theVfiler
9
Add the ifconfig and default route commands to /etc/rcifconfig e0 10.41.72.113 up netmask 255.255.255.0mediatype 100tx-fdvfiler run vfiler1 route add default 10.41.72.1
Add the ifconfig and vfilercommands to the hostingfiler’s /etc/rc (ie:/vol/vol0/etc/rc) to make thempersistent
* Note: Data ONTAP 7.1+ does not require steps 7-8 as vfiler create asks all the necessary questions.
7.2 MultiStore (Vfiler) AdministrationThis section will demonstrate how to administrate a vfiler.
Step Command/Action Description
1vfiler status [-a|-r]vfiler1 running
Check vfiler status [-a shows Allowed protocols]
2 ipspace list Display IPspaces configured
3 vfiler disallow vfiler1 proto=nfs Disallow nfs protocol on a per-Vfiler basis
4vfiler context vfiler1* Switch context of the CLI to vfiler. All
subsequent commands will be run on thespecified Vfiler.
5 vfiler1> setup Setup Vfiler
DOT 7 0 Cook Book_Rev1_0.doc Page 3118 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
6vfiler1> cifs setup Setup CIFS on Vfiler. Be sure to give the filer a
unique default name in the domain beingconfigured.
7 vfiler1> qtree create eng /vol/vol1/eng Create a qtree in the volume. Only possible ifthe vfiler is assigned to a volume.
8 vfiler1> cifs shares –add eng /vol/vol1/eng Create share in the vfiler
9 Verify clients in the same IPspace canaccess the share within this Vfiler
Verify everything worked
* To return to the root filer, type vfiler context vfiler0. Additionally, you may type vfiler run beforeevery command to run the command on the specified Vfiler’s context.
7.2.1 MultiStore(Vfiler) Stop/DestroyThis section will show how to stop and destroy a vfiler.
Step Command/Action Description
1 vfiler stop vfiler1 Stops Vfiler from receiving incomingpackets
2ifconfig e0 downorifconfig –alias <alias interface>
Down the interface associated with theVfiler’s IPspace-alias if the interface is an alias
3vfiler destory vfiler1[...]Resources for vfiler vfiler1 moved to hosting filer.
Disassociate resources from a Vfiler.This will not destroy any of the user data.All resources return to vfiler0.
4 vfiler status vfiler1 Check status of vfilers.
DOT 7 0 Cook Book_Rev1_0.doc Page 3218 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
8 Sample Configuration Files
8.1 /etc/quota
#Quota Target type disk files thold sdisk sfiles* user 50M - - - -/vol/home/user/joe user 500M 10K 450M - -21 group 750M 75K 700M 700M -/vol/eng/proj tree 750M 75K 700M - -writers group@/vol/eng 300M 50K 250M 45K [email protected] user - - - - -netapp\sxia user@/vol/vol2 200M - 150M - -rsaklikar user@/vol/vol2 200M - 150M - -“[email protected]” user 100M - 50M - -S-1-5-32-544 user@/vol/vol2 200M - 150M - -
Note: Important Quota Commands:
- quota resize <vol>
- quota off <vol> / quota on <vol>
8.2 /etc/rc
#Auto-generated by setup Mon Mar 14 08:18:30 GMT 2005hostname fbfiler2ifconfig e5a `hostname`-e5a mediatype auto flowcontrol full netmask 255.255.255.0 partner10.41.72.101route add default 10.41.72.1 1routed onvlan create e4 10 20 30ifconfig e4-10 172.25.66.11 netmask 255.255.255.0vif create multi MultiTrunk1 e0 e1ifconfig MultiTrunk 172.25.66.10vif favor e0options dns.domainname firebird.netapp.comoptions dns.enable onoptions nis.enable offsavecore
DOT 7 0 Cook Book_Rev1_0.doc Page 3318 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
8.3 /etc/exports
#Auto-generated by setup Mon Mar 14 08:18:30 GMT 2005/vol/vol0 -sec=sys,ro,rw=fbsun1,root=fbsun1,nosuid/vol/vol0/home -sec=sys,rw,root=fbsun1,nosuid/vol/perf -sec=sys,rw,root=fbsun1,nosuid/vol/perf/qtree -sec=sys,rw=Adminhost:fbsun1/vol/vol0/unix_tree -sec=sys,rw=Adminhost:fbsun1,root=fbsun1/vol/vol0/mktg -sec=sys,ro/vol/perf/subnet -sec=sys,rw=10.41.72.0/24,root=10.41.72.0/24/vol/perf/netgroup -sec=sys,rw=trusted-hosts/vol/cifsvol1 -sec=sys,rw,root=fbsun1,nosuid/vol/flex1 -sec=sys,rw,root=fbsun1,nosuid/vol/flex2 -sec=sys,rw,root=fbsun1,nosuid
8.4 /etc/snapmirror.confThe snapmirror.conf file uses the same syntax as the Unix crontab file. The following examples showdifferent ways to set up snapmirror schedules.
The following entry indicates that filer fridge's qtree home, in volume vol2 will mirror qtree home, involume vol1 from the filer toaster. Transfer speed is set at a maximum rate of 2,000 kilobytes persecond. The four asterisks mean transfers to the mirror are initiated every minute, if possible. (If aprevious transfer is in progress at the minute edge, it will continue; a new transfer will be initiated atthe first minute edge after the transfer has completed.)
toaster:/vol/vol1/home fridge:/vol/vol2/home kbs=2000 * * * *
The following entry, between the db volumes on fridge-gig dev and icebox, is kicked off every fiveminutes, starting at 0. (Note fridge-gig is just a network interface name. In this case, a gigabit ethernetlink on fridge.)
fridge-gig:db icebox:db - 0-55/5 * * *
The following entry makes transfers every half hour, with the first at 8:15 a.m., and the last at 6:45 p.m.The asterisks mean that the data replication schedule is not affected by the day of month or week; inother words, this series of transfers are initiated every day.
filer1:build filer2:backup - 15,45 8,9,10,11,12,13,14,15,16,17,18 * *
DOT 7 0 Cook Book_Rev1_0.doc Page 3418 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
9 Troubleshooting CommandsThe following section contains a list of general commands for troubleshooting various storageappliance issues.
9.1 General Troubleshooting
1. Define the problem.2. Gather facts related to the problem.3. Identify potential cause of problem.4. Create an action plan.5. Test the plan.6. Implement the plan.7. Observe results.8. Document solution.
The following commands describe generic storage appliance troubleshooting commands.
Command Description
statit –b, statit -e Storage Appliance statistics printout
wafl_susp -w Display WAFL Statistics
perfstat Collects performance statistics(Note: May increase load on system)
sysstat 1 Display total system statistics every second
sysconfig -v System hardware configuration information
sysconfig -r System raid group information
sysconfig -c Checks config levels of hardware against DOTsoftware requirement.
9.2 NFS TroubleshootingThe following section describes NFS specific troubleshooting commands.
Command Description
Nfsstat Display NFS statistics
exportfs Display currently exported volumes or qtrees
rdfile /etc/exports Display persistent volume or qtree exports
showmount -e <filer_ip> Run from Unix server to display a list of currentlyavailable exported volumes or qtrees
9.3 CIFS TroubleshootingThe following section describes CIFS specific troubleshooting commands.
DOT 7 0 Cook Book_Rev1_0.doc Page 3518 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
Command Description
cifs domaininfo Display Domain Controller information
cifs stat Display CIFS statistics
cifs stat -h <Domain_Controller_IP> ORcifs stat -f <Workstation_IP>
Review CIFS per client statistics
options cifs.per_client_stats.enable on Enable per client CIFS statistics
wcc {-u uname | -s ntname} Diagnose security checking for both UNIX-style(uname) and NT-style security (ntname)
options cifs.trace_login on Monitor CIFS login attempts.
cifs testdc Test domain controller communications
Ssaccess.exe SecureShare Access application for windows. ShowsUNIX/NTFS ACLs
9.4 Network TroubleshootingThe following sections describes IP network issue troubleshooting commands
Command Description
ifconfig -a Display all ethernet interfaces, configuration andstatus
netstat -rn Display Routing Table
netstat -s Packet statistics per protocol
netstat -i Packet statistics per Ethernet port
netstat -m Network interface memory buffer utilisation
ping Node accessibility check over IP network
netdiag Network Diagnostics command
ifinfo Print interface driver information
ifstat Print interface driver statistics
net use From Windows server - displays network connections
pktt Gathers network traffic information
Ethereal Analyze pktt output
9.5 NDMP TroubleshootingThe following section describes NDMP troubleshooting commands
Command Description
ndmpd debug 50 Increase the debug level to view connection attemptsand NDMP communications with the filer
ndmpd status View the status of connections
DOT 7 0 Cook Book_Rev1_0.doc Page 3618 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
ndmpd probe
ndmpd kill
pktt Packet tracing on the filer
9.6 SAN TroubleshootingThe following section provides a brief introduction to SAN troubleshooting commands.
9.6.1 Filer SAN Utilities
Command Description
fcp nodename If returns all zeros, then this adapter is not a target butan initiator
fcp show adapter Display the WWPN for the HBA adapter on the filer
fcp show initiator Display FCP initiators connected to filer
iscsi initiator show Display ISCSI initiators connected to filer
lun show -m Display information about lun_path to initiator_groupmappings
igroup show Check for correct WWPN -> Initiator name mappings
iswt interface Check appropriate interfaces are enabled for ISCSI(7.0 and below)
Data ONTAP 7.1+> iscsi interface Check appropriate interfaces are enabled for ISCSI(7.1+)
iscsi security Check and reconfigure initiator security settings
9.6.2 Solaris SAN Utilities
Command Description
lputil Configure/view/verify HBA bindings
sanlun fcp show adapters -v Display information about host HBAs
sanlun lun show Display LUNs that are mapped to host
reboot -- -r Reboot reconfigure option. Used after changes to/kernel/drv files.
devfsadm Discovery of new LUNs
solaris_info/filer_info/brocade_info Utilities installed as part of the FCP attach kit. Usedto collect all config info on the respective devices.
modinfo | grep lpfc Check if lpfc driver is loaded
DOT 7 0 Cook Book_Rev1_0.doc Page 3718 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
9.6.3 Windows SAN Utilities
Command Description
SnapDriveDC Gathers Windows and filer information
C:\>lputilnt Light Pulse Utility used to view Revision/Firmware,Persistent Bindings, configuration data (WWNN,WWPN), status of adapters
Control Panel->ISCSI ISCSI Control Panel used to set/verify persistentbindings, login and logoff from targets
9.6.4 Common SAN Switch Commands
Command Description
Brocade> switchshow Displays switch and port status information
Brocade> cfgshow Displays all zone configuration information
Brocade> portperfshow Displays port throughput numbers for all ports on theswitch
Brocade> portdisable/portenable Used to test filer port response
Brocade> portshow <port number> Show port information
9.7 Test & Simulation ToolsThe following section provides a brief introduction to test and simulation tools that are available for usewith a Network Appliance storage appliance.
Tool Description
sio_ntap_win32 Simulated I/O tool for Windows
sio_ntap_sol Simulated I/O tool for Unix
perfstat.sh Performance Statistics
DOT 7 0 Cook Book_Rev1_0.doc Page 3818 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
DOT 7 0 Cook Book_Rev1_0.doc Page 3918 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
DOT 7 0 Cook Book_Rev1_0.doc Page 4018 July 2006 © Network Appliance Australia Pty Ltd ABN 14 092 499 431
CreditsName Email Date Description
David ThiessenAustralia PSE
3/24/2005 Original author
Eli RodriguezRTP – TSE
[email protected] 5/1/2006 Added Clustering, MultiStore, SANTroubleshooting, Updated Version to 0.5.Most information was taken from NHTT v2.1training guides and Data ONTAP docs.
Michael CopeSan Diego PSE
[email protected] 5/4/2006 Networking and Access chapter, increase sizeof Aggregate, Traditional Volumes andFlexvols, Software Ownership. Incrementversion to 0.6
Michael Cope 6/5/2006 Added SnapShot utilities and Volume Copy.Increment version to 0.7
Michael Cope 7/10/2006 LUN resize, ndmpcopy, expand software diskownership procedures. Increment version 0.8
Michael Cope 7/15/2006 Quotas, added more command syntax,snapmirror.conf examples, corrected typos.Increment version to 1.0
Top Related