NetApp NCDA Exercise Guide

NETAPP UNIVERSITY

Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode

Exercise Guide

Course Number: STRSW-ILT-ANCDA-D87M Catalog Number: STRSW-ILT-ANCDA-D87M-EG Content Version: 1.0

NetApp University - Do Not Distribute

E-2 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Welcome

© 2010 NetApp, Inc. This material is intended for training use only. Not authorized for reproduction purposes.

ATTENTION The information contained in this guide is intended for training use only. This guide contains information and activities that, while beneficial for the purposes of training in a closed, non-production environment, can result in downtime or other severe consequences and therefore are not intended as a reference guide. This guide is not a technical reference and should not, under any circumstances, be used in production environments. To obtain reference materials, please refer to the NetApp product documentation located at http://now.netapp.com/ for product information.

COPYRIGHT © 2010 NetApp, Inc. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice.

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

NetApp reserves the right to change any products described herein at any time and without notice. NetApp assumes no responsibility or liability arising from the use of products or materials described herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product or materials does not convey a license under any patent rights, trademark rights, or any other intellectual property rights of NetApp.

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

RESTRICTED RIGHTS LEGEND NetApp Documentation is protected by Copyright and is provided to U.S. Government Agencies with LIMITED RIGHTS as defined at FAR 52.227-14(a). Use, duplication, or disclosure by the U.S. Government is subject to the restrictions as set forth therein. In the event of use by a DOD agency, the Government's rights in Documentation are governed by the restrictions in the Technical Data Commercial Items clause at DFARS 252.227-7015 and the Commercial Computer Software and Commercial Computer Software Documentation clause at DFARS 252.227-7202.

TRADEMARK INFORMATION

NetApp, the NetApp logo, Go Further, Faster, Data ONTAP, Appliance Watch, ASUP, AutoSupport, Bolt Design, Center-to-Edge, ComplianceClock, ComplianceJournal, ContentDirector, Cryptainer, Data Motion, DataFabric, DataFort, Decru, Decru DataFort, Evolution of Storage, Exec-Vault, FAServer, FilerView, FlexCache, FlexClone, FlexShare, FlexVol, FPolicy, Get Successful, gFiler, LockVault, Manage ONTAP, MultiStore, NearStore, NetApp Availability Assurance, NetApp IT As A Service, NetApp ProTech Expert, NetCache, NOW, NOW (NetApp on the Web), ONTAPI, Raid-DP, Replicator-X, SANscreen, SecureAdmin, SecureShare, Shadow Tape, Simulate ONTAP, SmartClone, SnapCache, SnapCopy, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, Snapshot, SnapStore, SnapSuite, SnapValidator, SnapVault, Spinnaker Networks, Spinnaker Networks logo, SpinCluster, SpinFlex, SpinFS, SpinHA, SpinMove, SpinServer, SpinStor, StoreVault, SyncMirror, Tech OnTap, Topio, vFiler, VFM, VFM (Virtual File Manager), WAFL, and Web Filer are either trademarks, registered trademarks, or service marks of NetApp, Inc. in the United States and/or other countries.

Not all common law marks used by NetApp are listed on this page. Failure of a common law mark to appear on this page does not mean that NetApp does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market.

Apple and QuickTime are either trademarks or registered trademarks of Apple Computer, Inc. in the United States and/or other countries.

Microsoft and Windows Media are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.

RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, RealVideo, RealMedia, RealProxy, and SureStream are either trademarks or registered trademarks of RealNetworks, Inc. in the United States and/or other countries.

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

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


E-3 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Welcome


TABLE OF CONTENTS

MODULE 1: NCDA OVERVIEW ....................................................................................................................... E1-1

MODULE 2: NFS OVERVIEW .......................................................................................................................... E2-1

MODULE 3: NFS SETUP .................................................................................................................................. E3-1

MODULE 4: EXPORTS AND MOUNTS ........................................................................................................... E4-1

MODULE 5: CIFS OVERVIEW ......................................................................................................................... E5-1

MODULE 6: CIFS WORKGROUPS .................................................................................................................. E6-1

MODULE 7: CIFS SHARES AND SESSIONS ................................................................................................. E7-1

MODULE 8: CIFS ACCESS CONTROL ........................................................................................................... E8-1

MODULE 9: CIFS DOMAINS ............................................................................................................................. E9-1

MODULE 10: NAS MULTIPROTOCOL .......................................................................................................... E10-1

MODULE 11: NAS TROUBLESHOOTING ..................................................................................................... E11-1

MODULE 12: SAN OVERVIEW ...................................................................................................................... E12-1

MODULE 13: FC CONNECTIVITY ................................................................................................................. E13-1

MODULE 14: ISCSI CONNECTIVITY ............................................................................................................. E14-1

MODULE 15: LUN ACCESS .......................................................................................................................... E15-1

MODULE 16: AVAILABILITY OVERVIEW ..................................................................................................... E16-1

MODULE 17: SNAPSHOT COPIES ............................................................................................................... E17-1

MODULE 18: SNAPRESTORE ...................................................................................................................... E18-1

MODULE 19: SNAPVAULT ............................................................................................................................ E19-1

MODULE 20: OPEN SYSTEMS SNAPVAULT .............................................................................................. E20-1

MODULE 21: HIGH AVAILABILITY ............................................................................................................... E21-1

MODULE 22: METROCLUSTER .................................................................................................................... E22-1

MODULE 23: SNAPMIRROR ......................................................................................................................... E23-1

MODULE 24: PERFORMANCE ...................................................................................................................... E24-1

APPENDIX A: ANSWERS ................................................................................................................................ EA-1

APPENDIX B: MASTER CONFIGURATION WORKSHEET .......................................................................... EB-1


E1-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: NCDA Overview


MODULE 1: NCDA OVERVIEW

EXERCISE

OVERVIEW

In this exercise, you will identify your primary client machine for the course and install NetApp® System Manager on that machine.

OBJECTIVES

By the end of this exercise, you should be able to:

Identify the exercise environment Log in to the exercise environment Install NetApp System Manager within your exercise environment

TIME ESTIMATE

15 minutes




EXERCISE 1: NCDA OVERVIEW

To prepare for the exercise environment, you will identify your main client machine, log in to the machine, and install NetApp System Manager.

TASK 1: IDENTIFY THE EXERCISE ENVIRONMENT

In this task, you will log in to your assigned exercise environment. You will perform all other actions starting from this assigned machine.

STEP ACTION

1. Your instructor will assist you in identifying your main Windows® Server. NOTE: This machine might be a virtual machine.

With the assistance of your instructor, identify the following essential equipment:

DESKTOP CONNECTION

Name: _____________________________

IP address: __________________________

Local Administrator

Password: ___________________________

Domain Administrator

Password: ___________________________

2. Task complete.

Windows Server




TASK 2: LOG IN TO THE EXERCISE ENVIRONMENT

In this task, you will log in to your assigned exercise environment. You will perform all other actions starting from this assigned machine.

STEP ACTION

1. In this task, you will log in to your assigned exercise environment by way of Remote Desktop Connection. From this remote Windows environment, you will then have access to your exercise environment.

On your local Windows machine, log in to the remote Windows machine through the Remote Desktop Connection tool.

Click the Remote Desktop Connection link on your desktop. If this link is not available, then ask your instructor where to find the tool.

Type your IP address in to the Computer combo box and click the Connect button.

You might be asked to authenticate. If so, provide the user name and password given to you by your instructor.

You should see the desktop of the remote machine. All other tasks will be initiated from this remote machine.

2. Task complete.




TASK 3: INSTALL NETAPP SYSTEM MANAGER

In this task, you will install NetApp System Manager on your Windows Server machine.

STEP ACTION

1. On your assigned Windows Server machine, open Windows Explorer and navigate to C:\_files\ANCDA. You might have a shortcut on your desktop to facilitate this step. Double-click system-manager-setup-1-1.exe. If prompted with a security warning, confirm by clicking Run.

The installation wizard should begin.

Click Next to start the wizard.

2. On the license agreement, select the I Agree radio button, and then click Next.

3. Select the default installation location and click Everyone to ensure that any user on this machine can run this program and click Next.

4. Confirm the installation by clicking Next again.




STEP ACTION

5. After the installation has completed, you should see a dialog window indicating that the install was successful.

Click Close to close the installation dialog window.

6. The Launch System Manager window should appear.

Click Cancel so that NetApp System Manager does not launch.

7. Task complete.

END OF EXERCISE


E2-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: NFS Overview


MODULE 2: NFS OVERVIEW

EXERCISE

OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current NFS exercise environment.

OBJECTIVES


Identify the exercise environment Log in to your assigned storage system Log in to NetApp® System Manager and add your storage system

TIME ESTIMATE

15 minutes




EXERCISE 2: NFS OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current NFS exercise environment with the assistance of your instructor.


This task familiarizes you with the exercise environment you will use for all exercises in this course. NOTE: Your Windows® client was identified in the previous module.

STEP ACTION

1. With the assistance of your instructor, identify the following essential equipment:

STORAGE SYSTEM CONNECTION

Name: ______________________________

Internal IP address: __________________________

Terminal IP address: _________________________

Root Password: ____________________________


UNIX/LINUX CONNECTION

NOTE: This machine might be a virtual machine.

Name: _____________________________

IP address: __________________________

Root

Password: ___________________________

3. Task complete.

Storage System

UNIX/LUNIX Workstation




TASK 2: LOG IN TO YOUR ASSIGNED STORAGE SYSTEM

In this task, you will log in to your assigned storage system and enable SNMP control so NetApp System Manager can manage it.

STEP ACTION

1. Log in to the storage system that has been assigned to you.

Double-click the link to PuTTY on your Windows Server desktop.

Enter the IP address to your assigned storage system and select the Telnet radio button. You use either the NIC interface address or the console address and port if available. NOTE: If you use a NIC interface address, Data ONTAP® 8.0 7-Mode defaults to have SSH enabled. You might need to change the radio button to SSH if Telnet is disabled.

You might want to save this configuration for future use. Type a name in to the Saved Sessions text box and click the Save button.

To open a session with your storage system, click the Open button.

2. On the storage system, type: system> options snmp

If SNMP is not enabled, enter the following to turn it on: system> options snmp.enable on

Verify it is enabled by entering the following: system> options snmp

3. Task complete.




TASK 3: LOG IN TO NETAPP SYSTEM MANAGER AND ADD YOUR STORAGE SYSTEM

In this task, you will set up NetApp System Manager to administer your assigned storage system.

STEP ACTION

1. On your remote Windows Server desktop, double click the NetApp System Manager desktop icon found on your desktop.

NetApp System Manager should launch.

2. Click the Add button to associate your storage system to NetApp System Manager.

Type in the IP address of e0a on storage system and click Add System.




STEP ACTION

3. Your storage system should be added to NetApp System Manager. NOTE: you should refer to the Data ONTAP 8.0 7-Mode Administration course for more details about configuring your storage system with NetApp System Manager.

In the left pane of NetApp System Manager, expand the node that represents your storage system by clicking the plus (+) icon next to the name.

Select the Storage node.

Your storage system is probably not configured yet for storage access. Click the Storage Configuration Wizard link.

The Storage Configuration Wizard should start.

4. We will manually configure storage in this class. Again, see the Data ONTAP 8.0 7-Mode Administration course for more details.

Click Next to continue on with the wizard.

5. On the Configure Aggregates page of the wizard, select Manually create aggregates.

Click Next.

6. Click Finish to end the wizard.

7. The Storage node should now have additional items. Click the plus (+) icon next to the Storage node to expand and view the items available.

If you have never used NetApp System Manager, you might want to explore the items on your own.

8. Task complete.

END OF EXERCISE


E3-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: NFS Setup


MODULE 3: NFS SETUP

EXERCISE

OVERVIEW

Setting up NFS services on a NetApp® storage system is easy. You will configure the NFS services in this exercise as well as allow your assigned UNIX or LINUX machine to be an admin host for your assigned storage system. This will allow your client host to have default access to your root volume’s configuration file.

OBJECTIVES


License and configure NFS service Add an admin host by way of the setup command

TIME ESTIMATE

20 minutes




EXERCISE 3: NFS SETUP

To set up a NetApp storage system for NFS traffic, you will have to license the storage system and verify the settings.

START OF EXERCISE

TASK 1: LICENSE AND CONFIGURE THE NFS SERVICE

In this task, you will license and verify the current configuration of the NFS service.

STEP ACTION

1. Open a PuTTY session to your storage system.

2. Check whether NFS is licensed on your system with the license command. system> license If NFS is not licensed, license the NFS protocol on your storage system. system> license add XXXXXXX (obtain license code from your instructor)

3. Open up NetApp System Manager; notice that under the Configuration node and Licenses node that the NFS license was added. Other changes caused by adding the NFS license include: Storage > Shared Folders > Exports Configuration > Protocols > NFS

4. From the Configuration > Protocols > NFS page within NetApp System Manager, select the Edit button. The Edit NFS Configuration should appear.




STEP ACTION

5. NOTE: The NFS versions are available from the Versions tab.

6. NOTE: View the Transport Protocols that are currently configured by selecting the Transport Protocols tab.

7. NOTE: Other settings are available by selecting the Miscellaneous tab.

8. From the PuTTY sessions, verify the NFS protocol setting using the command-line interface: system> options nfs In the following steps, we will verify individual settings.




STEP ACTION

9. Determine which transport portal NFS is using: system> options nfs.tcp What is the status of NFS running over TCP? ________ system> options nfs.udp What is the status of NFS running over UDP? ________

10. Determine the NFS version running: system> options nfs.v3 What is the status of NFS running the v3 protocol? ________ system> options nfs.v4 What is the status of NFS running the v4 protocol? ________ What is the status of NFS running the v2 protocol? ________ How can you tell? ________

11. Task complete.

TASK 2: ADD AN ADMIN HOST BY WAY OF THE SETUP COMMAND

In this task, you will configure your storage system’s admin host setting with your assigned UNIX or LINUX host. This will allow your UNIX or LINUX host to mount the root volume of your storage system so that you can configure the storage system.

STEP ACTION

1. Establish a console connection to the storage system by way of the terminal server and execute the setup command. Enter the following highlighted information when prompted: NOTE: Your output may differ depending on the hardware you are utilizing. system> setup

The setup command will rewrite the /etc/rc, /etc/exports, /etc/hosts, /etc/hosts.equiv, /etc/dgateways, /etc/nsswitch.conf, and /etc/resolv.conf files, saving the original contents of these files in .bak files (e.g. /etc/exports.bak).

Are you sure you want to continue? [yes]

Enter Yes or Return to start the wizard.




STEP ACTION

2. Press Enter to accept the default value for the following questions: Please enter the new hostname [system]:

Do you want to configure interface groups? [n]:

Please enter the IP address for Network Interface e0a [10.254.134.35]:

Please enter the netmask for Network Interface e0a [255.255.252.0]:

Should interface e0a take over a partner IP address during failover? [n]:

Please enter media type for e0a {100tx-fd, tp-fd, 100tx, tp, auto (10/100/1000)} [auto]:

Please enter flow control for e0a {none, receive, send, full} [full]:

Do you want e0a to support jumbo frames? [n]:

Please enter the IP address for Network Interface e0b []:

Should interface e0b take over a partner IP address during failover? [n]:

Please enter the IP address for Network Interface e0c []:

Should interface e0c take over a partner IP address during failover? [n]:

Please enter the IP address for Network Interface e0d []:

Should interface e0d take over a partner IP address during failover? [n]:

Would you like to continue setup through the web interface? [n]:

Please enter the name or IP address of the default gateway [10.254.132.1]:

3. The admin host questions are next. Enter the name of your UNIX or LINUX machine and then enter its primary IP address: The administration host is given root access to the filer's /etc files for system administration. To allow /etc root access to all NFS clients enter RETURN below.

Please enter the name or IP address of the administration host: LINUX_VM

Please enter the IP address for LINUX_VM: XXX.XXX.XXX.XXX




STEP ACTION

4. Continue through the wizard by pressing Enter for the remainder of the questions: Please enter timezone [GMT]:

Where is the filer located? [Classroom]:

Do you want to run DNS resolver? [y]:

Please enter DNS domain name [development.netappu.com]:

You may enter up to 3 nameservers

Please enter the IP address for first nameserver [216.240.23.25]:

Do you want another nameserver? [y]:

Please enter the IP address for alternate nameserver [10.254.132.10]:

Do you want another nameserver? [n]:

Do you want to run NIS client? [n]: The Shelf Alternate Control Path Management process provides the ability

to recover from certain SAS shelf module failures and provides a level of

availability that is higher than systems not using the Alternate Control

Path Management process.

Do you want to configure the Shelf Alternate Control Path Management interface for SAS shelves [n]:

5. Now, let’s reboot the storage system to make our changes take effect. NOTE: Because we only added the admin host setting, we don’t really need to reboot. If this was a production storage system, you might make the change take effect without rebooting by using the source command. system> reboot The setup command automatically updates the following files:

/etc/exports – allowing the admin host to mount the root volume.

/etc/hosts.equiv – allowing the admin host to be trusted on the storage system (allows rsh commands).

/etc/hosts – allowing IP resolution of the admin host.

options admin.host – which displays the name of the admin host that was provided during the setup command. If volumes are automatically exported (a feature described later in the course), this setting determines “who” should receive access to the server-generated export.

We will now explore these changes.

6. After the reboot, log in to your storage system. What volumes exist on your storage system? ______________________

Which command did you use to discover the volumes?_______________




STEP ACTION

7. List the content of the /etc/exports file in the space provided: HINT: There is a command-line interface command, but you might be able to do it another way. If you issued a command-line interface command, what command did you run?_____________ How do you list what exports are presently in memory? __________________ Remember this file was populated during the storage system’s setup.

8. Record the IP address and hostname for each entry in the /etc/hosts file as follows: Host1: IP Address:

9. List the content of the /etc/rc file in the space provided: HINT: Again, there might be more than one way to accomplish this. The /etc/rc file sets up interfaces and loads exports, as well as other configurations, during boot up of the storage system. You modify the /etc/rc file by running setup but you can modify it directly. The /etc/rc file is only executed at boot up. To execute any modification to the /etc/rc, use the source command. system> source /etc/rc

This executed the /etc/rc file again. To learn more about the source command, see the manual (man) page. system> man source

10. Task complete.

END OF EXERCISE


E4-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Exports and Mounts


MODULE 4: EXPORTS AND MOUNTS

EXERCISE

OVERVIEW

This lab allows you to practice what you learned in class regarding file sharing. You will create volumes, qtrees, and files. The volumes, qtrees, and files will be exported on the storage system and mounted to a mountpoint on the NFS client. It is assumed that you are familiar with the exportfs, mount, mkdir, and cd commands. If not, refer to the lecture notes during this lab exercise.

OBJECTIVES


Mount the root volume of the storage system on an admin host Export a volume using the command-line interface Rename a volume and verify the automatic export Export and mount a qtree Export to a subnet Export to a netgroup Export a qtree using NetApp® System Manager Mount an export from an admin host

TIME ESTIMATE

60 minutes




EXERCISE 4: EXPORTS AND MOUNTS

In this exercise, you will create new resources, export them to various targets and mount them from an NFS client.

START OF EXERCISE

TASK 1: MOUNT THE ROOT VOLUME OF THE STORAGE SYSTEM ON AN ADMIN HOST

In the previous exercise, you configured a UNIX or LINUX host as an admin host. Now, mount the root volume so you can modify configuration files from the admin host.

STEP ACTION

1. Launch NetApp System Manager and navigate to:

Storage > Shared Folders > Exports

2. Notice that the root volume is exported by default just like you observed from the command-line interface in the previous exercise.

2. Log in to your UNIX or LINUX machine with a PuTTY client. NOTE: Your UNIX or LINUX machine might use SSH. Check with your instructor if you have any questions.

3. Create a mountpoint using the name of your assigned storage system. # mkdir /mnt/<system> Replace <system > with the name of your storage system. Create a vol0 directory under /mnt/<system>: # mkdir /mnt/<system>/vol0




STEP ACTION

4. Mount /vol/vol0 to this mountpoint. # mount <system>:/vol/vol0 /mnt/<system>/vol0

5. Change the directory to the mountpoint and list the contents. # cd /mnt/<system>/vol0 # ls –la What are the contents of the directory? _____

6. Notice that under /mnt/<system >/vol0 there is an etc directory. Is this the etc directory for your local UNIX host or your storage system?_________ There is also an etc directory under /. Is this the etc directory for your local host or your storage system? ____________ NOTE: It is easy to get them confused and to modify the wrong system.

7. Task complete.

TASK 2: EXPORT A VOLUME USING THE COMMAND-LINE INTERFACE

In this task, you will create a new aggregate and volume and verify the volume was exported automatically.

STEP ACTION

1. Examine the contents of the /etc/exports file with the rdfile command. system> rdfile /etc/exports Compare the output from above with the output from using the exportfs command. system> exportfs What is the difference between the outputs?

2. Create an aggregate and a flexible volume with the following commands: The following command will create an aggregate with three disks with a single parity disk. system> aggr create aggr1 –t raid4 3 The following command will create a flexible volume called NFStest: system> vol create NFStest aggr1 10g




STEP ACTION

3. Verify the volume is created and exported using the rdfile and exportfs commands: system> rdfile /etc/exports Using the exportfs command, verify the volume is exported: system> exportfs What option allows a newly created volume to be exported automatically? HINT: Look at system> options nfs

4. Note the access permission for the exported volume and record it here:

5. Task complete.

TASK 3: RENAME A VOLUME AND VERIFY THE AUTOMATIC EXPORT

In this task, you will rename a volume that was automatically exported and verify the export after the renaming operation. Then you will mount the newly renamed volume from a host.

STEP ACTION

1. At the storage system command-line interface, rename the volume from NFStest to NFSvol: system> vol rename NFStest NFSvol

2. At the storage system command-line interface, view the exported file systems: system> exportfs Notice that the /etc/exports file has been modified and that the exports have been automatically updated.

3. Create a mountpoint on the UNIX host and mount the volume: # mkdir /mnt/<system>/NFSvol # mount <system>:/vol/NFSvol /mnt/<system>/NFSvol Verify the mount operation: # cd /mnt/<system>/NFSvol # ls

4. Task complete.




TASK 4: EXPORT AND MOUNT A QTREE

In this task, you will create a qtree. You will then export it by editing the /etc/exports file and then reload the persisted exports. You will then mount the qtree export.

STEP ACTION

1. At the storage system command-line interface, use the qtree create command to create a qtree named unix_tree on NFSvol: system> qtree create /vol/NFSvol/unix_tree

2. Verify that the security style is set to UNIX: system> qtree security /vol/NFSvol/unix_tree unix




STEP ACTION

3. Let us now export this new qtree. Connect to your UNIX host and edit the /etc/exports file on the storage system. Grant access to /vol/NFSvol/unix_tree by adding the following line: /vol/NFSvol/unix_tree -rw=<UNIX/LINUX HOST>,root=<UNIX/LINUX HOST> To edit the file, you can use vi. If you are not familiar with this technique, refer to the following: Verify your current location # pwd /mnt/system/vol0 If you are not here, within the vol0 mount point, change your directory to this location. Change directory into your assigned storage system’s etc directory. # cd etc Run vi on the exports file. # vi exports Your exports file will now be available in the vi editor and the editor will be in command mode. Scroll down to the last line. Type Shift-A, capital A, to append to the end of the line you are currently on. Enter Return to move to the next line. Type in the following line: /vol/NFSvol/unix_tree -rw=<UNIX/LINUX HOST>,root=<UNIX/LINUX HOST> replacing the <UNIX/LINUX HOST> with your assigned UNIX/LINUX hostname or IP address. Click the ESC button to move out of append mode and back to command mode. Enter :wq to write the file and quit vi. Verify your changes using the cat command. # cat exports ... /vol/NFSvol/unix_tree -rw=host1,root=host1

4. At the storage system command-line interface, run the following command to export the new entry to memory: system> exportfs –a system> exportfs




STEP ACTION

5. Create the following mountpoint on the UNIX host: # mkdir /mnt/<system>/unix_tree

6. Mount the new export: # mount <system>:/vol/NFSvol/unix_tree /mnt/<system>/unix_tree Verify unix_tree is mounted from the storage system: # mount

7. Change your current directory to the new mountpoint: # cd /mnt/<system>/unix_tree # touch unix_file Verify that you created a new file with the touch command: # ls –l

8. Task complete.

TASK 5: EXPORT TO A SUBNET

In this task, you will export a resource to a subnet.

STEP ACTION

1. Create the following qtree: system> qtree create /vol/NFSvol/subnet




STEP ACTION

2. Export this qtree to the subnet. Use the subnet address of the current training environment in one of the following ways: /vol/NFSvol/subnet -rw=<current_subnet>/24,root=<current_subnet>/24 or /vol/NFSvol/subnet -rw=”<current_subnet> <subnet_mask>”,root=”<current_subnet> <subnet_mask> NOTE: Use your assigned UNIX host’s IP address and the correct subnet mask. For example: /vol/NFSvol/subnet -rw=10.10.10.0/24,root=10.10.10.0/24 or /vol/NFSvol/subnet -rw=”10.10.10.0 255.255.255.0”, root=”10.10.10.0 255.255.255.0 Export the file system after editing the /etc/exports file.

3. Mount the subnet qtree to the following location: /mnt/<system>/subnet # mkdir /mnt/<system>/subnet # mount <system>:/vol/NFSvol/subnet /mnt/<system>/subnet Change the directory to the mountpoint and create a file named subnet_file using the touch command.

4. Task complete.




TASK 6: EXPORT TO A NETGROUP

In this task, you will identify targets and resources, create the /etc/netgroup file, create the /etc/nsswitch.conf file, and verify content of the /etc/rmtab and /etc/hosts files.

STEP ACTION

1. Verify the existence of the netgroup file from the host with the ls command or from the storage system with the rdfile command. From the admin host: # cd /mnt/<system>/vol0/etc # ls –l net* # more netgroup From the storage system: system> rdfile /etc/netgroup Does the file exist? ________________________________________ If no, what error message did you receive? ______________________ NOTE: If it doesn’t exist, we will have to create it.




STEP ACTION

2. Use a UNIX or LINUX host or the wrfile command to create three groups. The groups are: trustedhosts, untrustedhosts, and allhosts. Add your assigned UNIX admin host to the trustedhost group and create other ‘dummy’ hosts for the untrustedhosts. Place the trustedhosts and untrustedhosts in the allhosts folder. See the WRFILE METHOD below for an example. VI METHOD: From the UNIX host: # cd /mnt/<system>/vol0/etc # vi netgroup Use the WRFILE METHOD for the correct data. WRFILE METHOD From the storage system command-line interface, use the wrfile command to create the netgroup file. system> wrfile /etc/netgroup Enter the following netgroups: trustedhosts (adminhost,,) (name_of_your_station,,) untrustedhosts (host1,,) (host2,,) allhosts trustedhosts untrustedhosts (Make sure to press Enter after the last line.) Press Ctrl-C to save entries NOTE: Disregard the error message generated; this message will always appear. CAUTION: Use the wrfile command sparingly. If available, use vi editor or other equivalent commands instead. Verify your entries with the rdfile command again: system> rdfile /etc/netgroup NOTE: It may take up to 60 seconds for modifications of the netgroup file to take effect.

3. The rmtab file records a list of all the hosts mounted the storage system since boot up. Check to see if the rmtab file exists and identify the contents of the file. # ls –l /mnt/<storage_system>/vol0/etc/rmtab # more /mnt/<storage_system>/vol0/etc/rmtab # more !$ Or, from the storage system: system> rdfile /etc/rmtab




STEP ACTION

4. The nsswitch.conf file contains information on the order of the mechanism to resolve hostname-to-IP, passwords, netgroups, as well as other configurations. Verify the existence of the nsswitch.conf file on the storage system: # ls –l /mnt/<system>/vol0/etc/nsswitch.conf # more !$ Or, from the storage system, use the rdfile command to verify the existence of the nsswitch.conf file: system> rdfile /etc/nsswitch.conf

5. Using the rdfile command, view the contents of the /etc/hosts file: system> rdfile /etc/hosts What is the output of this command? ____________________________________________________ ____________________________________________________ Make sure your assigned UNIX host is on the list.

6. Create a qtree in the NFSvol volume named netgroupA.

7. Export netgroupA to the trusted targets (the netgroup trustedhosts) with rw permissions.

8. Mount the netgroupA qtree to the following location /mnt/<system>/netgroupA (where <system> is the name of your storage system).

9. Change the directory to the mountpoint and create a file named netgroup_file. You have successfully exported a resource to a netgroup.

10. Task complete.

TASK 7: EXPORT A QTREE USING NETAPP SYSTEM MANAGER

In this task, you will export a qtree using NetApp System Manager and change the logical name of the export.

STEP ACTION

1. Using System Manager, create a qtree by navigating to Storage > Qtrees.

Click Create button within the main windows.




STEP ACTION

2. Add the following infromation to the Create Qtree window:

Name: readTree

Volume: NFSVol

Enable oplocks: [unchecked]

Securtiy Style: unix

Click the Create button to create the new qtree.

3. Now, let us create an export for this new qtree.

Click Storage > Shared Folders > Exports.

4. Click Create to start the Create Share and Export wizard.

Click Next.

5. Within the Shared Folder Location, click Browse and the Browse For Folder dialog should appear.

Expand aggr1 and the select NFSvol. Select the readTree folder.

Verify that the folder path to export is /vol/NFSvol/readTree and click OK.

6. Click Next in the Shared Folder Location.

The Share Protocols dialog appears.

NOTE: We only have NFS licensed currently, so only NFS exports are only available.

Change the Export Name to /readTree.

Click Next.




STEP ACTION

7. In the NFS Permissions dialog, change the default permissions by selecting the current default and clicking Edit.

Within Edit Host Permissions, change the permissions for All hosts to Allow Read-Only.

Click OK.

8. Verify the permissions.

Click Next.

9. Review the Share Summary dialog and click Next.


11. Observe you new export under Storage > Shared Folders > Exports.

12. Task complete.

TASK 8: MOUNT AN EXPORT FROM AN ADMIN HOST

In this task, you will mount the export created earlier in this exercise.

STEP ACTION

1. Establish a PuTTY session to the admin host and create a directory for your storage system.

2. Create the readTree directory under the system_name directory:

# mkdir /mnt/<system_name>/readTree




STEP ACTION

3. Mount the storage system’s root volume to the directory you just created and view the contents. When mounting the root volume, use the storage system name or IP address. # mount <IP_address>:/readTree /mnt/<system_name>/readTree

# cd /mnt/<system_name>/readTree

4. You should now be able to view the directory structure of your storage system’s root volume. # ls –al /mnt/<system_name>/readTree

How does this compare with the local clients root?

(Hint # ls –al /) _______________________________________________

5. Try to create a file at the root of the storage system: # touch foo

Was it successful? ______________________

6. Task complete.

END OF EXERCISE


E5-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: CIFS Overview


MODULE 5: CIFS OVERVIEW

EXERCISE

OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current CIFS exercise environment.

OBJECTIVES


Identify the hardware available in your exercise configuration

TIME ESTIMATE

15 minutes




EXERCISE 5: CIFS OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current CIFS exercise environment with the assistance of your instructor.

START OF EXERCISE


This task familiarizes you with the exercise environment you will use for all exercises in this course.

STEP ACTION

1. With the assistance of your instructor, identify the following essential equipment: Windows Server


ALSO NOTE: When login into the Windows Server, authenticate with the domain.

Name: ______________________________

IP address: _________________________

Domain

Administrator

Password: __________________________

Local

Administrator

Password: __________________________

Domain Controller

Domain Name: _______________________

Controller

IP address: _________________________

DNS: ____________________________

IP address: _________________________




STEP ACTION

Storage System

Name: ___________________________________

Type: ___________________________________

Internal

IP address: _______________________________

Terminal

IP address: _______________________________

Root

Password: _______________________________

2. Task complete.

END OF EXERCISE


E6-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: CIFS Workgroups


MODULE 6: CIFS WORKGROUPS

EXERCISE

OVERVIEW

The goal of this lab is to give you an opportunity to configure a storage system for a Windows® workgroup environment. In a future exercise, you will repurpose the storage system for an Active Directory domain environment.

OBJECTIVES


Configure a storage system for a Windows workgroup environment Review the results of cifs setup in a Windows workgroup environment

TIME ESTIMATE

30 minutes




EXERCISE 6: CIFS WORKGROUPS

Windows workgroup is a fast ad-hoc method of associating a group of machines. NetApp® storage systems can participate in this loose association of machines. In this exercise, you will configure your assigned storage system to work in a Windows workgroup environment using the command-line interface. We will use NetApp System Manager when we convert the workgroup configuration to an Active Directory domain.

START OF EXERCISE

TASK 1: CONFIGURE A STORAGE SYSTEM FOR A WINDOWS WORKGROUP ENVIRONMENT

In this task, you will log in to your assigned storage system and configure the CIFS services within Data ONTAP®.

STEP ACTION

1. Open a PuTTY interface to your assigned storage system.

2. Type license at the storage system’s command prompt to view the current list of licenses registered. License CIFS by entering the following command and using the CIFS license code provided by your instructor: system> license add xxxxxx

Confirm the license was successfully added by reissuing the license command at the prompt.

3. Before configuring the CIFS services, at the storage system prompt (in your Telnet session), enter the following command and view the default storage system security style and NT administrator privileges: system> options wafl

Look at the wafl.default_security_style option. What is the volume (and all qtrees on the volume) default security style? ______________ Look at the wafl.nt_admin_priv_map_to_root option. Does the NT (Windows) administrator have privileges to map to the UNIX root user? ___________________

4. Enter the following command and view the security style of the root volume:

system> qtree status

What is the security style of your root volume? _________




STEP ACTION

5. Configure the CIFS services by entering the following command: system> cifs setup

NOTE: Steps 6 through 13 will assist you in entering the correct parameters.

6. Answer no [n] to WINS.

7. Configure the security style as (2) NTFS-only filer. NOTE: Normally, if we use both NFS and CIFS on the same storage system you should select (1) Multiprotocol, but we want to observe the resulting effect on the storage system.

8. Type in a root password and press Enter key. Repeat. NOTE: By default, Data ONTAP 8.0 7-Mode requires a harden password. The root password must be at least 8 characters, 2 alphabetic characters, and 1 number.

9. Press Enter to keep default CIFS server (storage system) name. (Obtain the storage system name from your instructor.)

10. Choose 3 for Windows workgroup authentication using the storage system’s local user accounts.

11. Press Enter to keep the default name for the workgroup [WORKGROUP].

12. Answer yes [y] to create the local administrator (system\administrator) account.

13. Enter the password twice for the local administrator password. NOTE: The name and password for the local administrator on the storage system must match the Windows workstation administrator and password for pass-through authentication to work.




STEP ACTION

14. CIFS should now be configured. Verify CIFS configuration using NetApp System Manager by navigating to:

Configuration > Protocols > CIFS

15. After configuring the CIFS services, enter the following command and view the default storage system security style and NT administrator privileges: system> options wafl

What is the volume (and all qtrees on the volume) default security style? ___________________

Does the NT (Windows) administrator have automatic privileges to map to the UNIX root user? _______________

16. Enter the following command and view the security style of the root volume:


After configuring the CIFS services, what is the security style of your root volume? __________________ After configuring the CIFS services, what is the security style of your NFSvol volume? __________________




STEP ACTION

17. Change NFSvol back to a unix security style using the following command: system> qtree security /vol/NFSvol unix

Verify:


18. Task complete.

TASK 2: REVIEW THE RESULTS OF CIFS SETUP IN A WINDOW WORKGROUP ENVIRONMENT

In this task, you will review the files modified during the process of configuring the storage system’s CIFS server for a Windows Workgroup environment. All commands in the lab are entered at the storage system prompt.

STEP ACTION

1. At the storage system prompt, review the CIFS configuration file with the rdfile command by typing: system> rdfile /etc/cifsconfig_setup.cfg

Notice how this file holds all the configurations entered during the wizard questions of the cifs setup command.

2. At the storage system prompt, review the following files with the rdfile command: /etc/usermap.cfg /etc/passwd /etc/nsswitch.conf /etc/cifsconfig_share.cfg




STEP ACTION

3. As you recall, cifs setup created a local administrator. We will now verify this new user was created.

system> useradmin user list administrator

Now, we will verify that this user was added to the lclgroups.cfg file under the BUILTIN\Administrators group.

system> rdfile /etc/lclgroups.cfg

Notice there is a SID under the BUILTIN\Administrators group. Because the lclgroups.cfg file is a newly created file, there should only be one SID. Now, let’s verify that this SID is the same as the administrator that we saw with the useradmin command: system> cifs lookup {copy the SID here}

This SID should resolve to the storage system’s local administrator that was created with cifs setup.

4. Task complete.

END OF EXERCISE


E7-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: CIFS Shares and Sessions


MODULE 7: CIFS SHARES AND SESSIONS

EXERCISE

OVERVIEW

The purpose of this activity is to perform routine CIFS administration procedures on your storage system in a Windows® Workgroup environment. You will view the current list of shares, add a new share, verify access to the share, and display session information.

OBJECTIVES


View current shares Create new shares using the command-line interface Verify shares access and display session information

TIME ESTIMATE

15 minutes




EXERCISE 7: CIFS SHARES AND SESSIONS

Now that your storage system is configured for CIFS, you will view the default shares, add new shares, and access the shares.

START OF EXERCISE

TASK 1: VIEW CURRENT SHARES

In this task, you will log in to the storage system and work with the default shares.

STEP ACTION

1. If you are not already logged in, use the Remote Desktop connection to log in to your Windows workstation as “Administrator.”

NOTE: Use the IP address and password provided by the instructor.

2. On your Windows workstation, go to StartRun. In the Run window, enter the following to browse the shares on your storage system, and click OK: \\IP_Address_of _Your_Storage_System

What share(s) display? _________________________

3. In the address bar of the Web browser, change the address to the following:

\\IP_Address_of _Your_Storage_System\C$

What folder(s) display? __________________________

4. At your storage system prompt, view the CIFS sessions by entering the following command: system> cifs sessions

What user currently has a session with the storage system? __________________________________________________

What account is the user mapped to? _______________________




STEP ACTION

5. At the storage system prompt, verify the user mapping by entering the following command: system> options wafl.nt_admin_priv_map_to_root

Is this option set to “on”? _________________

If wafl.nt_admin_priv_map_to_root is on, then the local administrator’s user mapping is “root.”

Verify the default UNIX user name by entering the following command: system> options wafl.default_unix_user

Is there a default UNIX user? If yes, what is the user name?

________________________________

If the wafl.default_unix_user is set to a user name (for example, pcuser), then this is the default user mapping for any Windows user that is not explicitly mapped.

Verify that the default UNIX user name is in the /etc/passwd file by entering the following command: system> rdfile /etc/passwd

Is the default UNIX user name in the /etc/passwd file? _____________

6. Task complete.

TASK 2: CREATE A NEW SHARE USING THE COMMAND-LINE INTERFACE

In this task, you will create a new share using the command-line interface.

STEP ACTION

1. At your storage system prompt, create a qtree named wintree in NFSvol:

system> qtree create /vol/NFSvol/wintree

Normally, a qtree created in NFSvol would be a unix security type because it would inherit the security style from its containing volume. NOTE: We will discuss security styles in the next module. For now, change the security style to ntfs by entering:

system> qtree security /vol/NFSvol/wintree ntfs

2. Create a new share called winshare (for the qtree wintree) on the storage system by entering the following command at the storage system prompt:

system> cifs shares –add winshare /vol/NFSvol/wintree

Answer yes if you are asked whether you want to use this share name.




STEP ACTION

3. View the newly created winshare share by entering the following command at the storage system prompt: system> cifs shares winshare

Which group has access to this share? _______________________

What are the share permissions? _______________________

4. Task complete.

TASK 3: VERIFY SHARE ACCESS AND DISPLAY SESSION INFORMATION

In this task, you access the new share that you created previously and check the session information.

STEP ACTION

1. On the Windows Server, open Windows Explorer and, as the administrator, map a network drive to the new share winshare.

NOTE: Depending on the environment, you might want to create a share using the storage system’s IP address instead of the hostname.

2. After mapping the network drive to winshare in Windows Explorer:

a) Right-click the winshare share mapping and choose Properties.

b) Click the Security tab and view the NTFS file permissions.

3. On the Windows workstation, create a text file with WordPad and save the file to the new share winshare.

a) Go to Start > Programs > Accessories > WordPad.

b) Open WordPad and type something to create a text document.

c) Save the file to the winshare share.

4. On the Windows workstation using Windows Explorer, go to the mapped network drive for the winshare share to view the newly created text file:

a) Right-click the text file and choose Properties.

b) Click the Security tab and view the NTFS file permissions for the text file.

c) What group has access to this file? ____________________________

List the file access permissions for the text file:__________________

d) Close all the open windows.




STEP ACTION

5. At the storage system prompt, view the CIFS sessions by entering the following command: system> cifs sessions

From your Windows workstation, who has a session with the storage system? __________________________________________________

6. Task complete.

END OF EXERCISE


E8-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: CIFS Access Control


MODULE 8: CIFS ACCESS CONTROL

EXERCISE

OVERVIEW

The purpose of this activity is to perform routine CIFS administration procedures on your storage system in a Windows® workgroup environment. You will create a local user account and administer user access, add a new share, map a network drive to the new share and verify access to the share, and create a local group.

OBJECTIVES


Add a new local user account and configure user access Access a network drive and work with access control Create a local group

TIME ESTIMATE

30 minutes




EXERCISE 8: CIFS ACCESS CONTROL

Currently, the storage system’s CIFS service is configured in a Windows Workgroup mode. We will create a local user account and configure local access control.

START OF EXERCISE

TASK 1: ADD A NEW LOCAL USER ACCOUNT AND CONFIGURE USER ACCESS

In this task, you will create a local user account on your storage system. All commands in the lab are entered at the storage system prompt.

STEP ACTION

1. Verify that you have a PuTTY session with your assigned storage system.

2. Recall that the storage system currently is in a Windows workgroup. To verify that the storage system is a server in a Windows workgroup, enter the following command: system> cifs sessions

Is the storage system in a Windows workgroup? ________________

3. Before adding a local user to the storage system, check the current security options to determine password rules by entering the following command: system> options security

What is the value for the security.passwd.rules.enable? _________ If the security.passwd.rules.enable option is “on,” then in order to create a local user, you will need to come up with a password using the following rules: It must be at least eight characters long It must contain at least two alphabetic characters It must contain at least one digit If security.passwd.rules.enable.option is “off,” then the restrictions will not be enforced when you create a password.

4. Add a local user (your name) in the predefined Guests group to the storage system by entering the following command: User names are case insensitive. system> useradmin user add your_name –g Guests

Remember your password._________________________

5. Verify that the local user (you) was added to the storage system by entering the following command: system> useradmin user list your_name

What are the capabilities of your new local user?

_______________________________________________




STEP ACTION

6. Check the allowed capabilities for the local administrator account by entering the following command: system> useradmin user list administrator

What are the capabilities of the local administrator?

_______________________________________________

7. View the list of all local storage system users by entering the following command: system> useradmin user list

What local users are listed? _____________________________________

8. Task complete.

TASK 2: ACCESS A NETWORK DRIVE AND WORK WITH ACCESS CONTROL

In this task, you will map a network drive to a share. Recall that in a Windows workgroup, user authentication is performed locally on the storage system.

STEP ACTION

1. On your assigned Windows server, map a drive to a storage system share \\IP_Address_of _Your_Storage_System\C$.

2. At the storage system prompt in your Telnet session, view the CIFS sessions by entering the following command: system> cifs sessions

Who has a session with the storage system? __________________________________________________ You logged in to the Windows as “Administrator” with a password. This “Administrator” was authenticated locally on the storage system with the local Administrator account (note that the user names match). The local Administrator account has the same password as the Windows Administrator.

This is called “pass-through” user authentication, and it works only if the names and passwords match on both the storage system and Windows workstation.

The Administrator account has permission to view the hidden C$ share.

3. On the Windows workstation, open Windows Explorer and disconnect all network drives attached to your storage system.




STEP ACTION

4. On the Windows workstation, log off as the Administrator and then log back in as the Administrator to clear the share cache.

a) Go to Start > Log Off administrator… and click the Log off button when you are asked if you are sure that you want to log off.

b) Use the Remote Desktop connection to log back in to your Windows workstation as the Administrator with the Administrator password.

5. On your Windows workstation, map a drive to a storage system share for a different local user (your name) by opening Windows Explorer and click Map network drive. The Map Network Drive window appears.

a) In the Drive list box, select any unused letter.

b) In the Folder list box, enter the following:

\\IP_Address_of _Your_Storage_System\C$

c) Click Connect using a different credentials.

d) Click Finish.

e) The Windows Security window appears.

Enter your User name. (Name_of _Your_Storage_System \your_name).

f) Enter your Password. (password for your_name).

g) Click the OK button.

h) Click the Finish button.

i) The Connect to …window appears.

j) The user name matches Name_of _Your_Storage_System \your_name.

k) In the password text box, enter your password.

l) Click the OK button.

Are you able to connect to C$ share? _____________________ If not, go to Step 5 b), and in the Folder list box, enter \\IP_Address_of _Your_Storage_System\Home and proceed again to map the network drive to the share.

The Guests group has no capabilities and, therefore, you cannot access the C$ share, but you can access the Home share because it is available to the Everyone group.




STEP ACTION

6. At the storage system prompt, view the CIFS sessions by entering the following command: system> cifs sessions

From your Windows workstation, who has a session with the storage system? __________________________________________________

7. Task complete.

TASK 3: CREATE A LOCAL GROUP

In this task, you will create a new local group on your storage system.

STEP ACTION

1. Before creating a new local group on your storage system, view the current groups on the storage system by entering the following command at the storage system prompt: system> useradmin group list

2. At the storage system prompt, create a local group on the storage system called “friends” with the Data ONTAP® predefined role “power” by entering the following command: system> useradmin group add friends –r power

3. At the storage system prompt, verify the newly created group by entering the following command: system> useradmin group list friends

How many capabilities are assigned to the “power” role for the friends group? __________________________




STEP ACTION

4. On the Windows workstation, change the security properties of the text file on the winshare share.

a) Open Windows Explorer and go to the mapped winshare drive to view the text file.

b) Right-click the text file and choose Properties.

c) Select the Security tab and under Group or user names, click Edit and then click the Add button.

d) In the Enter the object names to select text box, enter friends.

e) Click the OK button.

f) Click the friends group. What permissions are displayed for the friends group? _____________________________

g) Click the Everyone group. How do the friends permissions differ from the permissions in the Everyone group? ___________________________________________________

h) Now, click the Apply button on the Security tab, and then click the OK button. Click the OK button.

5. At the storage system prompt, modify the local user (your name) and add the friends group to the user by entering the following command: system> useradmin user modify your_name –g Guests,friends

6. At the storage system prompt, verify the groups and capabilities of the newly changed local user (your name) by entering the following command: system> useradmin user list your_name

To which groups does the local user (your name) now belong?________________ Have the local user (your name) capabilities changed? If yes, how? ________________________________________________

7. Task complete.

END OF EXERCISE


E9-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: CIFS Domains


MODULE 9: CIFS DOMAINS

EXERCISE

OVERVIEW

The purpose of this activity is to reconfigure the storage system’s CIFS server for an Active Directory environment. You will then create a domain user, create shares, and administrate those shares.

OBJECTIVES


Terminate CIFS services using NetApp® System Manager Configure DNS using NetApp System Manager Configure the time services using NetApp System Manager Reconfigure the CIFS services using NetApp System Manager Create a 32-bit aggregate using NetApp System Manager Create a volume using NetApp System Manager Create shares and manage the permissions of the shares Create a domain user Create a share with Computer Management Map shares to drive letters Display CIFS sessions

TIME ESTIMATE

60 minutes




EXERCISE 9: CIFS DOMAINS

Up to now, you have worked with Data ONTAP® CIFS services in the Workgroup mode. But most Windows® environments use Microsoft® Active Directory technology, which centralizes all resources in a Windows domain. In this exercise, you will reconfigure your storage system for a Windows domain environment.

START OF EXERCISE

TASK 1: TERMINATE CIFS SERVICES USING NETAPP SYSTEM MANAGER

In this task, you will terminate CIFS services using NetApp System Manager.

STEP ACTION

1. Open up NetApp System Manager and navigate to:

Configuration > Protocols > CIFS

2. On the Configuration tab of the CIFS configuration window, click the Stop button to terminate all CIFS sessions and shut down the CIFS services.

Click Stop to accept this action.

3. Verify that the CIFS services status is stopped.

4. Task complete.




TASK 2: CONFIGURE DNS WITH NETAPP SYSTEM MANAGER

In this task, you will configure your assigned storage system’s DNS service using NetApp System Manager.

STEP ACTION

1. From the left pane, click the appropriate storage system to display a subtree of management features.

2. Click Configuration > Network > DNS.

3. Click the Edit button.

Verify that DNS is enabled with the appropriate nameserver(s) for your environment. If not, check the Enable DNS.

Add the DNS domain name that is appropriate in your environment.

Type in the server IP address of your first DNS and click Add. Repeat for the number of DNS servers that you have in your environment.

4. Task complete.

TASK 3: CONFIGURE THE TIME SERVICES WITH NETAPP SYSTEM MANAGER

In this task, you will configure your assigned storage system’s time services using NetApp System Manager.

STEP ACTION

1. From the left pane, click the appropriate storage system to display a subtree of management features.

2. Click Configuration > System Tools > Date/Time/Timezone. Click Edit.




STEP ACTION

3.

Set the time zone to be the same as your Domain Controller.

Either set the time manually or point it to a SNTP server that is linked with your Domain Controller. NOTE: This could be your domain controller if configured.

Click OK when finished.

4. Task complete.

TASK 4: RECONFIGURE THE CIFS SERVICES USING NETAPP SYSTEM MANAGER

In this task, you will reconfigure the CIFS services using NetApp System Manager to join your storage system to a Windows Active Directory domain.

STEP ACTION

1. Go to Protocols > CIFS within System Manager.

Click Set up to start the CIFS Setup wizard.




STEP ACTION

2. Because you have previously configured the CIFS services, you are presented with a warning message:

Click the OK to stop CIFS service during setup check box and click Next.

3. We are using both NFS and CIFS on this storage system so within the Security Style dialog, check the security style as Multiprotocol.

Click Next.

4. We will connect this storage system to an Active Directory domain.

Verify that the Active Directory radio button is selected and click Next.

5. Enter the domain name and domain administrator’s credentials as provided by your instructor.

Click Next.

6. Keep the default Name of the system and do not enter any WINS server addresses.

Click Next.

7. Review the CIFS Setup Summary.

Click Next.

8. Verify that CIFS Setup Wizard was successful and Click Finish.

9. Review the Configuration tab within NetApp System Manager.

10. Review the Domain tab within NetApp System Manager.

11. Task complete.




TASK 5: CREATE A 32-BIT AGGREGATE USING NETAPP SYSTEM MANAGER

In this task, you will create a 32-bit aggregate using NetApp System Manager.

STEP ACTION

1. Using NetApp System Manager, from the console tree, click the appropriate storage system to display a subtree of management features.

2. Click Storage > Aggregates.

3. Click Create to start the Create Aggregate wizard.

4. Type or select information as requested by the wizard.

Aggregate Name: aggr2

RAID Type: RAID 4

Disk selection: Allow system to select disks automatically based on the required aggregate size

Disk Type: FCAL or SAS

Maximum size: [unchecked]

Click Next.

5. In the Aggregate Size page, create an aggregate with three disks.

Click Next.

6. Verify the settings are correct in the Aggregate Summary page and click Next.

7. After the wizard completes successfully, click Finish.

8. Verify that the aggregate you created is included in the list of aggregates in the Aggregate window.

9. This aggregate has three disks. Is the available space two-thirds of the total disk space? Explain why or why not.

_____________________________

10. Task complete.




TASK 6: CREATE A VOLUME USING NETAPP SYSTEM MANAGER

In this task, you will create a new flexible volume in the aggr1 aggregate using NetApp System Manager.

STEP ACTION

1. From the console tree, click the appropriate storage system to display a subtree of management features.

2. Click Storage > Volumes to display the Volumes window.

3. Click Create to display the Create Volume dialog box.

4. Add the following information:

Name: NASvol

Storage type: NAS

Aggregate: aggr2

Select the size of a volume. Although flexible volumes can grow as needed, you will want to start with a reasonable size. For our lab environment, 10 GB (tiny in a real-life scenario) will work fine.

NOTE: Your instructor may modify this value to a smaller volume size for simulated environments.

Leave the default Snapshot™ reserve at 20%.

Click Create to add your new volume.

5. What is the amount of space available for data? ______________________

6. Task complete.

TASK 7: CREATE SHARES AND MANAGE THE PERMISSIONS OF THE SHARES

In this task, you will display all the current shares, sessions, local groups, and users on your storage system using NetApp System Manager.

STEP ACTION

1. View the shares on the storage system by entering the following command: system> cifs shares

or within NetApp System Manager at Storage > Shared Folders > Shares/Exports.




STEP ACTION

2. Create a qtree named cifs_tree1 in NASvol and change security to ntfs using NetApp System Manager:

a. Navigate to Storage > Qtrees b. Click Create

c. Within the Create Qtree dialog, enter the following:

Name: cifs_tree1

Volume: NASvol

Enable oplocks: [checked]

Security style: NTFS

Click the Create button.

3. Within NetApp System Manager, navigate to Storage > Shared Folders > Shares/Exports.

4. Notice the default shares created. Explore the C$ share by clicking Edit when the C$ share is highlighted.

Observe the default Share permissions for this share by looking at the Share permission tab.

Click Cancel to close the Edit C$ setting dialog.

5. Click Create on top of the main panel.

The Create Share and Export Wizard should appear.

Click Next.




STEP ACTION

6. Click Browse and navigate until you see the cifs_tree1 folder.

Select it and click OK. Back in the Shared Folder Location, click Next.

7. This qtree will be used only for CIFS access so we will uncheck NFS but otherwise accept the defaults.

Click Next.

8. Review the Share Summary and click Next.


Notice the new share within the list.

10. Task complete.




TASK 8: CREATE A DOMAIN USER

In this task, you will configure Microsoft’s Server Manager to administer Active Directory credentials and create a domain user.

STEP ACTION

1. If you have not done so before now, log in to your assigned Windows Server using the domain administrator’s account. If your assigned Windows Server is not on the Active Directory domain, add it to your Windows domain.

To verify or add the Windows Server to the domain, click Start > Control Panel > System and Security > System. The current status of the Windows Server is found in the Computer name, domain, and workgroup settings section. To add your machine, click the Change Settings.

2. Next, we need to install the Remote Server Administration Tools feature within Server Manager. Open Server Manager by clicking the Server Manager icon next to the Start button.

Server Manager should appear.




STEP ACTION

3. Select Features from the list in the left pane. Currently, your system has 2 features installed. We will now install the Remote Server Administration Tools feature.

Click Add Features to launch the Add Features Wizard.

4. With the Select Features window, select Remote Server Administration Tools. When the Add Features indicates that you cannot install the Remote Server Administration Tools unless you added the required Web Server role services, click Add Required Role Services.

Select Next within the Add Features Wizard.

5. The wizard indicates the changes to the Web Server (IIS) services. After reading it, confirm by clicking Next.

6. From the Select Role Services page, click Next to select the changes to IIS.

7. From the Confirm Installation Selections, click Install.

8. After the wizards completes, continue with the install by clicking Close and then Yes to reboot.




STEP ACTION

9. Wait a few minutes and log back into your assigned Windows Server using your Domain Administrator credentials.

The Installation progress should indicate a successful install of the Remote Server Administration Tools.

Click Close to exit the wizard.

You can close Server Manager as well.

10. Open an interface to your domain’s Active Directory resources by clicking:

Start > All Programs > Administrative Tools > Active Directory Users and Computers

If the Active Directory Users and Computers option is not present, check with your instructor.

11. Select your domain with the left pane of the tool.




STEP ACTION

12. Select Users with the right pane of the tool. The current Active Directory users and groups should appear.

13. Click Action, select New, and then select User.

Create UserX, where X is the number of your storage system. (For example, if your storage system name is Storage System10, create User10.)

NOTE: Do not create “UserX” without replacing the X with a number. If you are not sure what user to create, ask your instructor.

Click Next.




STEP ACTION

14. Set the user password the same as the user name.

Additionally, unselect the first option and select the second and third options.

Click Next to continue.

15. Click Finish to create the user.

16. Task complete.

TASK 9: CREATE A SHARE WITH COMPUTER MANAGEMENT

In this task, you will view and create shares using Microsoft’s Computer Management tool.

STEP ACTION

1. Create another NTFS qtree called cifs_tree2 in NASvol by using either the command-line interface or NetApp System Manager.

2. Open Computer Management by clicking:

Start > Control Panel > Administrative Tools > Computer Management

NOTE: If you don’t see Administrative Tools within Control Panel, change the View By option to Large Icons.

3. Click Action, and then select Connect to another computer. Highlight the name of your storage system using the Browse feature or type the IP address.

4. In the left pane, click:

System Tools > Shared folders > Shares

5. Observe the list of currently shared directories on the right.

6. Right-click the Shares folder, and then select New Share. Click Next to start the wizard.

7. Enter the following information:

Folder path: C:\vol\NASvol\cifs_tree2

Click Next.




STEP ACTION

8. Enter the following information:

Share name: cifs_tree2

Share Description: Share for cifs_tree2

Click Next.

9. Select the option, Customize permissions, and then click the Custom button.

10. Add UserX from the previous exercise with Full Control.

Click OK.

11. Click Finish. Notice that the selection is displayed in the Share Permissions window.

12. Select No to create another share.

13. Notice that the new shared directory, cifs_tree2, is displayed in the shared directories for the storage system.

14. Close the Computer Management dialog box.

15. Task complete.

TASK 10: MAP SHARES TO DRIVE LETTERS

In this task, you will map the shares you just created to drive letters.

STEP ACTION

1. Map a network drive for cifs_tree1 within Windows.

Enter the following information in the appropriate fields:

Drive: <an unused letter>

Path: \\Storage_System_name\cifs_tree1

Click Finish to accept the changes and close the window.

2. Map another network drive for cifs_tree2.

3. Copy some files from your Windows machine to cifs_tree1 and cifs_tree2.

Was it successful to cifs_tree1? ________

Was it successful to cifs_tree2? ________

Why or why not? ___________________

4. Task complete.




TASK 11: DISPLAY CIFS SESSIONS

In this task, we will observe the CIFS sessions from NetApp System Manager, Computer Management, and the command-line interface.

STEP ACTION

1. From NetApp System Manager, navigate to:

Storage > Shared Folders > Sessions

Observe that you have at least one session.

2. Now, let us observe the sessions using Computer Management. Open Computer Management and connect to your storage system.

3. Select System Tools > Shared Folders > Sessions.

4. Finally, let us observe the sessions using the command-line interface. Verify the open sessions from the storage system. system> cifs sessions

5. Compare the output of the cifs sessions command with the output from NetApp System Manager and Computer Management.

6. Task complete.

END OF EXERCISE


E10-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: NAS Multiprotcol


MODULE 10: NAS MULTIPROTOCOL

EXERCISE

OVERVIEW

In this exercise, you will work with NTFS, UNIX® and mixed-styled qtree, configuring a storage system to authenticate users regardless of the client accessing the qtree.

OBJECTIVES

By the end of this exercise, you should be able to: Configure your storage system for multiprotocol access

TIME ESTIMATE

30 minutes




EXERCISE 10: NAS MULTIPROTOCOL

In this exercise, you will log in to the exercise environment and configure your storage system for multiprotocol NAS access.

START OF EXERCISE

TASK 1: CONFIGURE YOUR STORAGE SYSTEM FOR MULTIPROTOCOL ACCESS

In this task, you will configure the storage system for multiprotocol access, and then view file permissions for files in an NTFS qtree, UNIX qtree, and mixed qtree.

STEP ACTION

1. Using NetApp® System Manager or the command-line interface, create a new qtree with the following parameters:

Name: ntfstree Volume: NASvol Security Style: NTFS Oplocks: None

2. Using NetApp System Manager or the command-line interface, create a new qtree with the following parameters:

Name: unixtree Volume: NASvol Security Style: unix Oplocks: None

3. Using NetApp System Manager or the command-line interface, create a new qtree with the following parameters:

Name: mixedtree Volume: NASvol Security Style: mixed Oplocks: None




STEP ACTION

4. Before configuring your storage system for multiprotocol access, perform the following from your Windows Server:

a) Create a share on the storage system called ntfsshare (for your ntfstree qtree on NASvol) and map a network drive to the share.

b) Create a share on the storage system called unixshare (for your unixtree qtree on NASvol) and map a network drive to the share.

c) Create a share on the storage system called mixedshare (for your mixedtree qtree on NASvol) and map a network drive to the share.

NOTE: You might need to disconnect all map drives, log out, and log back in to the Windows machine to clear the security cache. Windows does not allow you to map two separate shares with different security accounts.

5. At the storage system prompt, view the current default security style by entering the following command: system> options wafl.default_security_style

What is the current default security style? ______________________

6. At the storage system prompt, enter the following command to view the security style for each qtree on NASvol: system> qtree status NASvol




STEP ACTION

7. On the Windows Server, open Windows Explorer, go to the mapped network drive for ntfsshare, and view the security of the ntfsshare by performing the following:

a) From Windows Explorer, click on Computers within the left pane. You should see a list of your local and mapped drives.

b) Right-click the drive that is mapped to ntfsshare and choose Properties.

c) Click the Security tab.

Who has access to the qtree, and what are the NTFS permissions on the file system?

___________________________________________________________

d) Click the Cancel button.

e) Double-click the ntfsshare in the console tree to view the contents of the share.

f) Create a new text file in this share by right-clicking in the right windowpane and choosing New > Text Document.

g) Right-click the previously created text file and choose Properties.

h) Click the Security tab.

Who has access to the file and what are the file permissions?

_______________________________________________

i) Click the Cancel button.

Recall that the ntfstree qtree has a designated security style of NTFS. This means that files have Windows NTFS ACLs (permissions).




STEP ACTION

8. On the Windows workstation, open Windows Explorer, go to the mapped network drive for the unixshare share, and view the security of the unixshare by performing the following:


b) Right-click on the drive associated with unixshare and choose Properties.

Is there a Security tab? ________________________

c) Click the Cancel button.

d) Double-click the unixshare in the console tree to view the contents of the share.

e) Create a new text file in this share by right-clicking in the right windowpane and choosing New > Text Document.

f) Right-click the New Text Document.txt file and choose Properties.

Is there a Security tab? ________________________

g) Click the Cancel button.

Recall that the unixtree qtree has a designated security style of UNIX, and that files and directories have UNIX permissions. You are a Windows user accessing a UNIX qtree and a UNIX file. The Properties window (in Microsoft® Windows) is not designed to interpret the UNIX permissions on the share and file and hence the Security tabs are missing. However, starting with Data ONTAP® 7.2, changes have been made to the multiprotocol functionality. Now administrators can both display and change UNIX permissions from the Windows Security tab. You will set this in step 10 of this lab.




STEP ACTION

9. On the Windows workstation, open Windows Explorer, go to the mapped network drive for mixedshare, and view the security of the mixedshare by performing the following:


b) Right-click on the drive associated with mixedshare and choose Properties.

c) Click the Security tab.

Who has access to the qtree, and what are the NTFS permissions on the file system?

__________________________________________________

d) Click the Cancel button.

e) Double-click the mixedshare in the console tree to view the contents of the share.

f) Create a new text file in this share by right-clicking in the right windowpane and choosing New > Text Document.

g) Right-click the New Text Document.txt file and choose Properties.

h) Click the Security tab.

Who has access to the file, and what are the file permissions?

_______________________________________________

i) Click the Cancel button.

Recall that the mixedtree qtree has a designated security style of mixed. This means that the default security style of a file is the style most recently used to set permission on that file. With mixed security style, the volume or qtree can have UNIX or NTFS file security in play. Because the mixedtree qtree was created when the storage system was multiprotocol mode, the mixed qtree initially inherited the effective security style of the parent volume.

10. To view the UNIX permissions on the files in this multiprotocol environment, enter the following option at the storage system prompt: system> options cifs.preserve_unix_security on Enabling this option allows you to manipulate a file’s UNIX permissions using the Security tab on a Windows client, or using any application that can query or set Windows ACLs. When enabled, this option causes UNIX qtrees to appear as NTFS volumes. The default for this option is “off.”

11. On the Windows workstation, open Windows Explorer, go to the mapped network drive for ntfsshare, and view the security of the previously created text file by performing the following:

a) Right-click the previously created text file and choose Properties.

b) Click the Security tab and view the permissions for the Everyone.





STEP ACTION

12. On the Windows workstation, open Windows Explorer, go to the mapped network drive for unixshare, and view the security of the New Text Document.txt file by performing the following:

a) Right-click the New Text Document.txt file and choose Properties.

b) Click the Security tab and view the UNIX group, user names, and permissions for this file whose file security is UNIX.

In the Group or user names list box, list the first four entries: ____________________________________________________

c) Click the Advanced button in the lower-right corner in the Security tab.

d) Click Change Permissions.

e) In the Advanced Security Settings window in the Permissions tab, select pcuser and click the Edit button. (Do not actually edit the permissions.)

In the Permission Entry window, what permissions does pcuser have? ______________________________________________________

f) Click the Cancel button in the Permission Entry window.

g) In the Advanced Security Settings window, click the Owner tab.

Who are the owners for this text file? ___________________________________________________

h) Click the Cancel button in the Advanced Security Settings window.

i) Click the Cancel button in the Properties window. You are a Windows user accessing this UNIX file with your mapped UNIX credentials. Your UNIX credentials are used when evaluating your access requests by comparing your credentials against the file or folder UNIX access permissions.

13. On the Windows workstation, open Windows Explorer, go to the mapped network drive for mixedshare, and view the security of the New Text Document.txt file by performing the following:

a) Right-click New Text Document.txt file and choose Properties.

b) Click the Security tab. What are the current permissions and why? _____________________________________________________


The effective Windows NTFS ACLs (permissions) are shown in the Security tab. The effective security style of the qtree, folders with the qtree, or files may be changed if a UNIX administrator sets permissions on the qtree, subfolders, or files by issuing the chmod (to change file permissions) or chown (to change the file or group ownership) command from a UNIX host.

14. Task complete.

END OF EXERCISE


E11-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: NAS Troubleshooting


MODULE 11: NAS TROUBLESHOOTING

EXERCISE

There is no exercise for this module.


E12-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: SAN Overview


MODULE 12: SAN OVERVIEW

EXERCISE

OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current SAN exercise environment.

OBJECTIVES


Identify the components of your SAN exercise environment

TIME ESTIMATE

15 minutes


E12-2 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: SAN Overview


EXERCISE 12: SAN OVERVIEW

In this exercise, you will verify the equipment used in the SAN exercises.

START OF EXERCISE

TASK 1: IDENITFY THE COMPONENTS OF YOUR SAN EXERCISE ENVIRONMENT

In this task, you will identify the hardware that you will use for your SAN exercise environment.

STEP ACTION

1. Because we will be using iSCSI only within the exercise environment, you will be using the same exercise equipment as used in the NFS and CIFS exercises.


STORAGE SYSTEM CONNECTION

Name: ______________________________

Internal IP address: __________________________

Terminal IP address: _________________________

Root Password: ____________________________

3. Your instructor will assist you in identifying your main Windows® Server.


DESKTOP CONNECTION

Name: _____________________________

IP address: __________________________

Local Administrator

Password: ___________________________

Domain Administrator

Password: ___________________________



Name: _____________________________

IP address: __________________________

Root

Password: ___________________________

5. Task complete.

END OF EXERCISE


Storage System

Windows Server

UNIX/LINUX Server


E13-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: FC Connectivity


MODULE 13: FC CONNECTIVITY

EXERCISE



E14-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: iSCSI Connectivity


MODULE 14: ISCSI CONNECTIVITY

EXERCISE

OVERVIEW

In this exercise, you will verify iSCSI connectivity on your assigned Linux® machine and Windows® machine.

OBJECTIVES


Configure iSCSI on a storage system Configure Windows for Multipath I/O Install NetApp® DSM on Windows Install the Host Utilities Kit on Windows Configure iSCSI on Windows Confirm an iSCSI session on a storage system Configure the second iSCSI session on Windows Confirm the second iSCSI session on a storage system Install the Host Utilities Kit on Linux Install the iSCSI software initiator for Linux Configure iSCSI software initiator on Linux Confirm iSCSI session(s) on a storage system

TIME ESTIMATE

90 minutes




EXERCISE 14: ISCSI CONNECTIVITY

iSCSI is rapidly become the SAN protocol of choice for many IT administrators. In this exercise, you will log in to the exercise environment and configure iSCSI on both storage systems as well as on your assigned Windows and Linux platform.

START OF EXERCISE

TASK 1: CONFIGURE ISCSI ON A STORAGE SYSTEM

In this task, you will log in to your assigned storage system and configure the iSCSI services.

STEP ACTION

1. Use PuTTY to log in to storage system that has been assigned to you by your instructor.

Double-click on the link to PuTTY on your Windows desktop.

Enter the IP address to the console of your assigned storage system and select the Telnet radio button. Then enter the port number of the console of your assigned storage system.

You might want to save this configuration for future use. Type a name into the Saved Sessions text box and click the Save button.

To open a session with your storage system, click the Open button.

2. Within your assigned storage system PuTTY Telnet window, enter the following command to investigate whether the iSCSI service is running: system> iscsi status

If it is not running, determine whether the service is properly licensed. system> license

Look for the license titled: iscsi.

If it is not licensed, enter the license code as provided by your instructor. system> license add XXXXX

Start up the iSCSI services: system> iscsi start

The iSCSI service should now be started.

Look at the subcommands for iSCSI: system> iscsi




STEP ACTION

3. In order to communicate with the iSCSI protocol, we will need to have a properly functioning interface. Enter the following command to investigate storage system’s IP interfaces:

system> ifconfig -a

e0a: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500inet 10.254.144.71 netmask 0xfffffc00 broadcast 10.254.147.255 ether 00:a0:98:08:1a:fa (auto-1000t-fd-up) flowcontrol full

e0b: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500inet 10.254.144.75 netmask 0xfffffc00 broadcast 10.254.147.255 ether 00:a0:98:08:1a:fb (auto-1000t-fd-up) flowcontrol full

e0c: flags=948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500inet 10.254.144.81 netmask 0xfffffc00 broadcast 10.254.147.255 ether 00:a0:98:08:1a:f8 (auto-1000t-fd-up) flowcontrol full

e0d: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 150 ether 00:a0:98:08:1a:f9 (auto-unknown-cfg_down) flowcontrol full

lo: flags=1948049<UP,LOOPBACK,RUNNING,MULTICAST,TCPCKSUM> mtu 8160 inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1 ether 00:00:00:00:00:00 (VIA Provider)

In a production environment, you should assign one or more dedicated interfaces to your iSCSI configuration. In this exercise environment we will use the configured interface e0a and e0b. For a high-availability configuration, you would use at least two interfaces on different physical interfaces.

Record the interface name and IP addresses on the Master Configuration Worksheet (see Appendix B).

4. Verify whether iSCSI service has been enabled for the e0a and e0b interface: system> iscsi interface show

If it is not enabled, enable e0a and e0b to work with the iSCSI service by entering the following command: system> iscsi interface enable e0a

system> iscsi interface enable e0b

Disable iSCSI access to e0c and e0d interfaces: system> iscsi interface disable e0c

system> iscsi interface disable e0d




STEP ACTION

5. Identify storage system’s WWNN.system> iscsi nodename

Record storage system’s WWNN on the Master Configuration Worksheet.

6. Verify the target portal groups on storage system by entering the following: system> iscsi tpgroup show

Record the TPGTag for e0a_default: _____________________________________

Record the TPGTag for e0b_default: _____________________________________

NOTE: We will be doing MPIO and not MCS, so there is no need to change the default target portal groups.

7. Task complete.

TASK 2: CONFIGURE WINDOWS FOR MULTIPATH I/O

In this task, you will log in to your assigned Windows Server 2008 machine and configure Multipath I/O.

STEP ACTION

1. From your remote desktop Windows Server 2003 machine, establish a remote desktop connection to your Windows Server 2008 machine.

Open the Remote Desktop Connection tool on the remote Windows Server 2003. Type in the IP address of the Windows Server 2008.

You might want to change your display of the remote desktop size to something less than the terminal server client to the remote Windows Server 2003 by clicking Options and the Desktop. This will create a smaller window for the Windows Server 2008 machine within the remote Windows Server 2003 machine.

Click Connect to open the terminal session to Windows Server 2008.

2. Click the Switch User button. Then select the Other User item and enter the domain Administrator account (such as DOMAIN\Administrator) and password provide by your instructor.

Log in to Windows Server 2008 by clicking the arrow button.




STEP ACTION

3. Open Server Manager (if it doesn’t automatically appear) by clicking the Server Manager button next to Start on the Windows Server 2008 desktop.


4. Select Features from the list in the left pane. Currently, your system has two features installed. We will now install the Multipath I/O feature.

Click Add Features to launch the Add Features Wizard.




STEP ACTION

5. With the Select Features window, select Multipath I/O and then select Next.

From the Confirm Installation Selections, click Install.

After the feature installs, you should see the Results window, which indicates that the install was successful. NOTE: You might get a warning if Windows automatic updating is disabled.

Click Close to exit the dialog box.

6. Task complete.




TASK 3: INSTALL NETAPP DSM ON WINDOWS

In this task, you will install NetApp Multipath I/O Device Specific Module (DSM) on your Windows Server 2008 system.

STEP ACTION

1. On your Windows Server 2008 system, click the shortcut on your desktop called “ANCDA class files.” This shortcut should take you to C:\_files\ANCDA.

Launch the DSM 3.3.1 installer by double-clicking: ntap_win_mpio_3.3.1_setup_x64.msi

If a security warning appears, click the Run button to continue.

2. After a while the DSM Wizard will appear with the title page; click Next to continue.

Agree to the EULA and click Next.

3. Add the license provided by your instructor and click Next.

4. In the Data ONTAP® DSM Management Service Credentials wizard page, add the administrator’s login and password as provided by your instructor and click Next to continue.

5. Observe the driver information and click Next to continue.

6. Accept the default destination folder by clicking Next. Finally, click the Install button to continue.

7. After the install is completed, click the Finish button and answer No at the prompt to restart. We will restart the system after the Windows Host Utilities Kit installation.

8. Open Server Manager (if it doesn’t automatically appear) by clicking the Server Manager button next to Start.

Expand the Diagnostics node in the left pane. Click Device Manager. Expand the System devices node and verify that Data ONTAP DSM was installed.

Right-click the Data ONTAP DSM node within the list and select Properties. Within the Properties dialog box, select the Driver tab and observe the current driver version.

9. Task complete.

TASK 4: INSTALL THE HOST UTILITIES KIT ON WINDOW

In this task, you will install the NetApp Windows Host Utilities Kit (HUK).

STEP ACTION 1. On your Windows Server 2008 system, click the shortcut on your desktop called “ANCDA class

files.” This shortcut should take you to C:\_files\ANCDA. Double-click netapp_windows_host_utilities_5.2_x64.msi. If prompted with a security warning, confirm and continue.

2. Click Next at the title page of the install wizard.

Confirm the license agreement and click Next.

3. Under the Support for Multipathing step, choose “Yes, install support for Multipath I/O,” and click Next.




STEP ACTION

4. Confirm the destination folder and click Next.

5. Click the Install button to execute the install. After the install is complete, click Yes to restart the Windows Server 2008 system.

6. Wait about two minutes and attempt to reconnect to your Windows Server 2008 system. Open a command prompt window by clicking the shortcut on your desktop.

Navigate to the install folder for the Windows HUK: C:\> cd “C:\Program Files\NetApp\Windows Host Utilities”

List the files in this directory: C:\Program Files\NetApp\Windows Host Utilities> dir

Check the version with the following command: C:\Program Files\NetApp\Windows Host Utilities> san_version

Windows® Host Utilities 5.2.3297.2229

NetApp version: 5.2

7. Task complete.




TASK 5: CONFIGURE ISCSI ON WINDOWS

In this task, you will log in to your assigned Windows machine and configure iSCSI for the first iSCSI session.

STEP ACTION

1. To begin configuration on the iSCSI service, open Server Manager (if it doesn’t automatically appear) by clicking the Start button, and then Server Manager

Expand the Configuration tab in the left pane and select Services. Locate the Microsoft® iSCSI Initiator Service.

Right-click it and select Properties. The Microsoft iSCSI Initiator Service Properties should appear.

Ensure the Startup type says Automatic.

Next, click the Start button to start the service.

Click OK to close the dialog.

The iSCSI service should start up every time Windows is started.




STEP ACTION

2. There are several methods to configure the iSCSI service but we will use the iSCSI Initiator method.

Click the Start button and in the Search programs and files textbox and enter iscsi initiator.

Under the programs category, click the iSCSI Initiator to launch the dialog.

The iSCSI Initiator Properties box should appear.




STEP ACTION

3. First, let us identify the WWNN for your assigned Windows machine.

Select the Configuration tab.

Record the Windows Server 2008 WWNN on the Master Configuration Worksheet.




STEP ACTION

4. We will now configure the iSCSI service to see storage system’s e0a target portal group.

Select the Discovery tab and click the Discover Portal button.

The Discover Target Portal dialog box should appear.




STEP ACTION

5. Enter the IP address of e0a of storage system that you recorded on the Master Configuration Worksheet. Leave the port as 3260.

Click the Advanced button and specify the Local Adapter as Microsoft iSCSI Initiator and the first interface on your Windows Server 2008 machine under Source IP.

Click OK.

Click OK to add the target port.




STEP ACTION

6. Click the Targets tab.

You now should see one discovered target.

What is the status of this target currently? ___________________________

Make sure the target is highlighted, and then click the Properties button.

How many current sessions are there? _________________________________

Select the Portal Groups tab.

How many portal groups has Windows identified? _______________________

Close the Properties dialog by clicking OK.

7. We will now bind to the storage system and create a session.

From the Targets tab, make sure that storage system’s IQN is highlighted and click the Connect button.

The Connect to Target dialog box appears. Select Enable multi-path. Then click the Advanced button.

Specify the Local Adapter as Microsoft iSCSI Initiator, the first interface on your Windows Server 2008 machine under Initiator IP, and the first target portal IP.




STEP ACTION

Click OK.

Click OK. Back in the iSCSI Initiator Properties dialog box, the status should now show as Connected.

Select the Properties button again.

The Properties dialog box should appear.

What is the target portal group tag of the connect session? _________________

What storage system and interface is this target portal group tag associated with? _____________________________________




STEP ACTION

8. Because we accepted the default and made this a favorite target, storage system’s target appears in the Favorite Targets tab.

You have now successfully established connectivity between the Windows initiator and the targets on storage system.

9. Task complete.

TASK 6: CONFIRM ISCSI SESSION ON A STORAGE SYSTEM

In this task, you will log in to your assigned storage system and confirm an iSCSI session.

STEP ACTION

1. Within your assigned storage system PuTTY Telnet window, enter the following command to investigate the current iSCSI sessions: system> iscsi session show

Does the storage system have an iSCSI session? _____________________________

How can you tell it is connected to your Windows machine?

__________________________

2. Task complete.




TASK 7: CONFIRM THE SECOND ISCSI SESSION ON WINDOWS

In this task, you will log in to your assigned Windows machine and configure iSCSI for the second iSCSI session.

STEP ACTION

1. On your assigned remote Windows machine, make sure the iSCSI Initiator Properties dialog box is open to the Targets tab.

2. From the Targets tab, make sure that storage system’s IQN is highlighted and click the Properties button. Then click the Add session button.

The Connect to Target dialog box appears. Select Enable multi-path. Then click the Advanced button.

Specify the Local Adapter as Microsoft iSCSI Initiator, the second interface on your Windows Server 2008 machine under Initiator IP, and the second target portal IP.

Click OK.

Click OK again.




STEP ACTION

3. Let us investigate the new session.

Making sure that the IQN of storage system is selected in the Discovered target’s list box, click the Properties button.

Verify that there are two sessions with the Properties dialog.

Select the second session. Verify that the target portal group should be the TPGTag for e0b_default target portal group on storage system.

We are done. Close the iSCSI Initiator Properties by clicking OK.

4. Finally, let us confirm the configurations within Windows Server 2008 R2’s Storage Explorer tool.

Click the Start button and in the Search programs and files textbox, enter Storage Explorer.

Under the programs category, click the Storage Explorer icon to launch the tool.

Select Servers in the middle pane and then the name of your Windows server.

Finally select the IQN of your Windows Software Initiator.




STEP ACTION

Investigate this interface. You will notice that you can perform similar tasks with Storage Explorer that you could also perform with the iSCSI Initiator Properties dialog box.

5. Task complete.

TASK 8: CONFIRM THE SECOND ISCSI SESSION ON A STORAGE SYSTEM

In this task, you will log in to your assigned storage system and confirm an iSCSI session.

STEP ACTION

1. Verify the iSCSI sessions by entering the following commands: system> iscsi session show

How many sessions does storage system have with your assigned Windows machine?

__________________

2. Verify the iSCSI connections by entering the following commands: system> iscsi connection show

How many connections does each session have with your assigned Windows machine?

__________________

3. Task complete.




TASK 9: INSTALL THE HOST UTILITIES KIT ON LINUX

In this task, you will install the NetApp Host Utility Kit for your Red Hat Linux system.

STEP ACTION

1. Log in to your assigned Red Hat using PuTTY.

2. Your exercise environment has been configured with the all files you will need for these exercises (/_files/ANCDA).

We will now copy these files from their source location to a different location to work with them.

Copy the files to the new working directory: # cp /_files/ANCDA/* /tmp

3. Change to your working directory: # cd /tmp

4. Extract the HUK package: # tar zxf netapp_linux_host_utilities_5_0.tar.gz

5. Change directory to the install directory of the HUK software, and install it: # cd netapp_linux_host_utilities_5_0

# ./install

6. Verify the HUK was installed correctly: # cd /opt/netapp/santools

# ./san_version

Example Output: NetApp Linux Host Utilities version 5.0

NOTE: At this point, it would be advisable to add the path, /opt/netapp/santools, for the HUK tools to your PATH env variable in your /etc/profile file. In the following steps you will be told to change to this directory to run several of the tools. If you set your profile with this directory, you can skip these steps.

7. Use the HUK sanlun tool: # ./sanlun version

Example Output: sanlun version 5.0.90.3515

8. Task complete.




TASK 10: INSTALL THE ISCSI SOFTWARE INITIATOR FOR LINUX

In this task, you will install the iSCSI software initiator package on your Red Hat Linux system.

STEP ACTION

1. Log in to your assigned Red Hat Linux system.

2. Change the directory to your class working directory: # cd /tmp

3. Install the iSCSI software initiator package: # rpm -ivh iscsi-initiator-utils-6.2.0.868-0.18.el5.x86_64.rpm

4. Task complete.

TASK 11: CONFIGURE ISCSI SOFTWARE INITIATOR ON LINUX

In this task, you will determine the WWNN for your Red Hat Linux system, examine the iscsid.conf configuration file, start the iSCSI daemon (service), configure Ethernet adapters to be used by the iSCSI initiator, assign Ethernet interfaces for iSCSI usage, and configure and establish iSCSI target discovery and sessions.

STEP ACTION

1. Record the WWNN for the RHEL machine on the Master Configuration Sheet: # cat /etc/iscsi/initiatorname.iscsi

You can record it here as well: __________________________________________________

2. Examine the contents of the iscsid.conf configuration file: # cat /etc/iscsi/iscsid.conf | more

Notice that you would use this file to configure iSNS, CHAPs, and iSCSI settings. We will leave all these as default.

3. Start the iSCSI daemon (service): # service iscsi start

Verify the daemon is running: # service iscsi status




STEP ACTION

4. Next, examine the current configuration of the Ethernet adapters on your Red Hat Linux system.

Determine the current NIC configuration: # ifconfig -a

Example output: eth0 Link encap:Ethernet HWaddr 00:21:5E:6F:18:C4

inet addr:10.254.132.63 Bcast:10.254.135.255 Mask:255.255.252.0

inet6 addr: fe80::221:5eff:fe6f:18c4/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:11779 errors:0 dropped:0 overruns:0 frame:0

TX packets:3965 errors:0 dropped:0 overruns:0

collisions:0 txqueuelen:1000

RX bytes:1092477 (1.0 MiB) TX bytes:412740 (403.0 KiB)

Interrupt:106 Memory:c8000000-c8012100

5. Next, configure the iSCSI initiator to use these Ethernet interfaces.

Determine if there are any current interfaces configured: # iscsiadm -m iface

Example output: iscsiadm: No interfaces found.

6. Configure an interface definition (iface0): # iscsiadm -m iface -I iface0 --op=new

7. Assign the Ethernet interface eth0 to the iSCSI configured name iface0: # iscsiadm -m iface -I iface0 --op=update -n iface.net_ifacename -v eth0




STEP ACTION

8. Verify the configured iSCSI interface definitions: # iscsiadm -m iface

Example output: iface0 tcp,default,eth0

These definitions can be found in config files at the following location: # cd /var/lib/iscsi/ifaces

# ls -l

Example output: total 16

-rw------- 1 root root 147 Sep 23 04:18 iface0

Examine the contents of these config files: # cat iface0

Example output: # BEGIN RECORD 2.0-868

iface.iscsi_ifacename = iface0

iface.net_ifacename = eth0

iface.hwaddress = default

iface.transport_name = tcp

# END RECORD

9. To configure and manage the iSCSI initiator/daemon, we will be using the iscsiadm tool. To become familiar with the syntax and options of this tool, consider doing the following:

To view syntax and options: # iscsiadm -h

To get a description of the options take a quick look at: # man iscsiadm




STEP ACTION

10. In this step, we will configure the iSCSI initiator/daemon to do target discovery using iface0 from your Red Hat Linux system, and the IP address of the target portal associated with the e0a Ethernet interface on your storage system.

Now we can attempt to discover the NetApp storage system as an iSCSI target. Switch to your assigned Red Hat command-line interface. # iscsiadm -m discovery -t st -p 10.254.133.239 -I iface0

NOTE: The IP address in your command will be e0a of your assigned storage system.

Example output: 10.254.133.239:3260,1000 iqn.1992-08.com.netapp:sn.101201757

11. With the Red Hat Linux iSCSI software, use the following command to list the nodes and portals discovered and their TPG number: # iscsiadm -m node

Example output: 10.254.133.239:3260,1000 iqn.1992-08.com.netapp:sn.101201757

12. Observe the details of target node and portal: # iscsiadm -m node -T <iqn_returned_from_last_step>

13. On your storage system: system> iscsi session show

On the Red Hat Linux system: # iscsiadm -m session

Are there any current sessions with Linux? _____

Log in: # iscsiadm -m node -l

On the storage console (if you have a command-line interface session open you will see), for example: system> ... ISCSI: New session from initiator iqn.1994-05.com.redhat:6d9443554d at IP addr 10.254.132.63

Now are there sessions on the storage system? ______________ system> iscsi session show

14. Observe the current iSCSI session(s) from the initiator side: # iscsiadm -m session




STEP ACTION

15. Observe the details about a specific session: # iscsiadm -m session -i -r <session_id_from_last_step>

16. Task complete.

TASK 12: CONFIRM ISCSI SESSION(S) ON A STORAGE SYSTEM

In this task, you will confirm the existence of iSCSI session(s) established from your Red Hat Linux system.

STEP ACTION

1. Determine if the iSCSI sessions observed on your Red Hat Linux system are also observable from your storage system: system> iscsi session show

Example output:

... Session 38

Initiator Information

Initiator Name: iqn.1994-05.com.redhat:6d9443554d

ISID: 00:02:3d:01:00:00

Initiator Alias: dev05s2.development.netappu.com

How many session(s) do you have from your Red Hat Linux system? _______

Does this match the number observed on your Red Hat Linux system? ______

Look into the details of one of your sessions: system> iscsi session show -v <session_number>

Do the IP addresses from the initiator and target correspond to IPs on your Linux and storage system? ___

What Ethernet interface is being used on your storage system? ____ Is this an iSCSI enable interface? ______

2. Task complete.

END OF EXERCISE


E15-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: LUN Access


MODULE 15: LUN ACCESS

EXERCISE

OVERVIEW

In this exercise, you will provision LUNs on a storage system and access them on your assigned Windows® Server and Red Hat® machine.

OBJECTIVES


Create a LUN with separate commands Initialize a LUN with Disk Management Provision a LUN with Disk Management Persist the mounting of a LUN Create iSCSI-attached LUNs for Red Hat Linux® Discover iSCSI-accessible LUNs from Red Hat Linux Prepare an individual LUN and mount it on Red Hat Linux

TIME ESTIMATE

45 minutes




EXERCISE 15: LUN ACCESS

Connectivity is great, but if there is not anything on the other end, it is not much good. In this exercise, you will log in to the exercise environment and configure several LUNs and configure your assigned Windows platform to access those LUNs.

START OF EXERCISE

TASK 1: CREATE A LUN WITH SEPARATE COMMANDS

In this task, you will log in to your assigned storage system and create a LUN for the Windows machine to connect by way of iSCSI.

STEP ACTION

1. Create a 10-GB flexible volume called lun1 to contain a new LUN by entering the following command: system> vol create lun1 aggr1 10g

Set the Snapshot™ reserve in the vol_SAN1 volume to zero: system> snap reserve lun1 0

Turn off the default Snapshot copies schedule: system> snap sched lun1 0 0 0

2. Within your assigned storage system PuTTY window, enter the following command to create an igroup: system> igroup create -i -t windows iWIN_iscsi <iqn_of_windows_machine>

Replace <iqn_of_windows_machine> with the IQN of your assigned Windows Server machine.

Verify: system> igroup show

Example output: iWIN_iscsi (iSCSI) (ostype: windows):

iqn.1991-05.com.microsoft:win (logged in on: e0a)




STEP ACTION

3. Create the LUN with the following command: system> lun create -s 2g -t windows /vol/lun1/lun1

Example output: lun create: created a LUN of size: 2.0g (2155023360)

Verify: system> lun show

Example output: /vol/lun1/lun1 2.0g (2155023360) (r/w, online)

4. Map the LUN to the igroup with the following command: system> lun map /vol/lun1/lun1 iWIN_iscsi 1

Example output: [system: lun.map:info]: LUN /vol/lun1/lun1 was mapped to initiator group iWIN_iscsi=1

5. Verify the LUN with the following command: system> lun show -m

Example output: LUN path Mapped to LUN ID Protocol

--------------------------------------------------------

/vol/lun1/lun1 iWIN_iscsi 1 iSCSI

6. Task complete.




TASK 2: INITIALIZE A LUN WITH DISK MANAGEMENT

In this task, you will log in to your assigned Windows platform and initialize the new lun0.

STEP ACTION

1. On your assigned remote Windows Server 2008 R2 machine, open the Disk Management tool:

Open Server Manager.

Expand the Storage node from the tree pane. Disk Management should be visible.

Select the Disk Management icon within the tree.




STEP ACTION

2. If one or more LUNs are not visible, right-click the Disk Management icon within the tree and select Rescan Disks from the menu.

After a while, one or more LUNs should appear.

3. Select lun1 and make it online by right-clicking the Disk # and select Online.

4. Next, we will initialize the LUN. Right-click the Disk # and select Initialize.

Choose the MBR partition style because that was type of LUN we created in the previous application and click OK.

5. Task complete.




TASK 3: PROVISION A LUN WITH DISK MANAGEMENT

In this task, you will log in to your assigned Windows platform and provision the new lun0 with Disk Management.

STEP ACTION

1. Now is the time to provision the LUN. You can use either the New Simple Volume method or the Provisioning Storage Wizard from the Share and Storage Management tool. This task will analyze the New Simple Volume method.

Right-click the new unallocated disk and select New Simple Volume from the menu. The New Simple Volume Wizard should begin.

2. Click Next from the title page of the wizard. Within the Specify Volume Size page, choose to make the LUN as large as it can be and click Next.




STEP ACTION

3. Assign an available drive letter such as E, and then click Next. If drive letter E is not available, choose another available drive letter.

4. Format the LUN as NTFS and select Next.

5. On the Completing the New Simple Volume Wizard page, review the values and click Finish if all entries are correct.

6. After a moment, the LUN should be available. Navigate to the drive letter of the LUN and write a test file to the LUN to verify that it is working correctly.

7. Task complete.




TASK 4: PERSIST THE MOUNTING OF A LUN

In this task, you will log in to your assigned Windows Server 2008 R2 platform and persist the mapping of lun1.

STEP ACTION

1. We can bind the volume (or device before we initialize and format the LUN) so that on Windows Server 2008 R2 restart it is more readily available for use by programs and services. NOTE: The associated target must be on the Favorite Targets list.

2. Open the iSCSI Initiator Properties dialog box. If you don’t remember how, check the Start menu and look for the most recently run programs.

3. On the Targets tab, click the Devices button. Lun1 should appear as a disk in the Devices dialog box.

Click OK.




STEP ACTION

4. Select the Volumes and Devices tab. Notice there are no current volumes in the Volume List.

Click Auto Configure. The drive letter associated with the iSCSI target should now appear in the list of the Volume List.

Now, if the Windows system is rebooted, lun1 will be available on the associated mountpoint (in this example C:\Data\CLI).

5. Task complete.




TASK 5: CREATE ISCSI-ATTACHED LUNS FOR RED HAT LINUX

In this task, you will set up an iSCSI accessible LUN for your Red Hat Linux system using NetApp® System Manager.

STEP ACTION

1. From NetApp System Manager, navigate to:

Storage > LUNs

NOTE: If the LUN is not visible, right-click the name of your storage system and select Refresh to update the interface.

The LUN Management interface should appear.

2. Select the Initiator Groups tab and click Add at the top to create a new iGroup.

Enter the following information:

Group Name: iRHEL_iscsi

Group Type: iSCSI

Operating System: Linux

Click Add to create the empty iGroup.




STEP ACTION

3. Within the Initiator IDs section, click Add to add the Red Hat IQN to the new iGroup.

Group Type: iSCSI

Group Name: iRHEL_iscsi

IQN: [Obtained from Red Hat]

NOTE: This can be obtained using the following command: # cat /etc/iscsi/initiatorname.iscsi

Click Add when finished.

4. Create a LUN in your new volume named lun2 with the following attributes:

LUN size: 2G

LUN type: Linux

Space Reserved: Yes

LUN ID: 0

Click the Create button from the LUN Management tab.

The Create LUN Wizard should appear. Click Next to continue.




STEP ACTION

5. Verify the following settings:

Name: lun2

Size: 2 GB

Type: Linux


6. On the LUN Container page, verify that the wizard is going to create lun2 in a new lun2 volume within aggr1.





STEP ACTION

7. On the Initiator Mapping page, the new igroup (iRHEL_iscsi) should appear.

Select the igroup and click >.

Click Next to continue with the wizard.

8. On the summary page, review the settings and click Next when finished.

9. Verify that the LUN Wizard completed successfully. Click Finish when done.

10. Task complete.

TASK 6: DISCOVER ISCSI-ACCESSIBLE LUNS FROM RED HAT LINUX

In this task, you will scan and discover the two newly created LUNs that are accessible using the iSCSI protocol.

STEP ACTION

1. Check for the LUN on Red Hat:

# fdisk -l

Most likely you will not see your new LUN without scanning for new SCSI devices.

2. To specifically scan for devices from a given iSCSI target over iSCSI, use the following command: # iscsiadm -m node -T iqn.1992-08.com.netapp:sn.101201757 -R

Remember to substitute the WWN target IQN name for your assigned storage system.

3. Check for “disk” again: # fdisk -l

How many new disks do you have? __________




STEP ACTION

4. Verify the LUNs as well using the sanlun utility from the Host Utilities Kit: # cd /opt/netapp/santools

# sanlun lun show -p

Do you see your new iSCSI LUN? ________________

5. Task complete.

TASK 7: PREPARE AN INDIVIDUAL LUN AND MOUNT IT ON RED HAT LINUX

In this task, you will prepare your FC-attached LUN for a file system, and mount it onto a Red Hat Linux systems hierarchy.

STEP ACTION

1. In this task, we will be using the LUN that you created on your storage system as /vol/lun2/lun2, which was discovered using the iSCSI protocol. Using the NetApp sanlun utility, determine the local path of this LUN. # sanlun lun show –p

How many paths do you have to lun2? __________

Local Path: ______________

The local path for this device would be: /dev/sdX (where “X” is the letter assigned to your LUN). NOTE: That we would normally setup DM-Multipath. You can find out more about DM-Multipath in the SAN Implementation Workshop course. In this class, we will not configure multipathing.

2. You will now label and format the LUN using fdisk utility on the Red Hat Linux system.

Example: # fdisk /dev/sdb

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disk label.

Building a new DOS disk label. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)




STEP ACTION

3. You will be prompted for a command. If you are not familiar with fdisk, you can see a list of commands by entering m:

Command (m for help): m

Command action

a toggle a bootable flag

b edit bsd disklabel

c toggle the dos compatibility flag

d delete a partition

l list known partition types

m print this menu

n add a new partition

o create a new empty DOS partition table

p print the partition table

q quit without saving changes

s create a new empty Sun disklabel

t change a partition's system id

u change display/entry units

v verify the partition table

w write table to disk and exit

x extra functionality (experts only)

4. The initial message stated that the device does not have a label or partition table. We can check this again with the p command:

Command (m for help): p

Disk /dev/sdb: 2147 MB, 2147483648 bytes

67 heads, 63 sectors/track, 1009 cylinders

Units = cylinders of 4154 * 512 = 2126848 bytes

Device Boot Start End Blocks Id System




STEP ACTION

5. We will now add a single primary partition n and p:

Command (m for help): n

Command action

e extended

p primary partition (1-4)

p

Partition number (1-4): 1 (Create partition 1)

First cylinder (1-1009, default 1): 1 (Start at cylinder 1)

Last cylinder or +size or +sizeM or +sizeK (1-1009, default 1009): 1009 (End at the last cylinder)

6. We will now select a partition type, and write it to disk:

Command (m for help): t (Use type)

Selected partition 1

Hex code (type L to list codes): L : : : :

2 XENIX root 39 Plan 9 82 Linux swap / So c4 DRDOS/sec (FAT-

3 XENIX usr 3c PartitionMagic 83 Linux

4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C:

...

Hex code (type L to list codes): 83 (Use Linux type)

Command (m for help): w (Write)

The partition table has been altered!

Calling ioctl() to re-read partition table.

Syncing disks.




STEP ACTION

7. Now let’s double check: # fdisk /dev/sdb

Command (m for help): p

Disk /dev/sdb: 2147 MB, 2147483648 bytes

67 heads, 62 sectors/track, 1009 cylinders

Units = cylinders of 4154 * 512 = 2126848 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 1 1009 2095662 83 Linux

Command (m for help): q




STEP ACTION

8. You will now install a file system onto your newly prepared “disk.”

Example: # mkfs -t ext3 /dev/sdb1

mke2fs 1.39 (29-May-2006)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

262144 inodes, 524288 blocks

26214 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=536870912

16 block groups

32768 blocks per group, 32768 fragments per group

16384 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912

Writing inode tables: done

Creating journal (16384 blocks): done

Writing superblocks and filesystem accounting information:done

This filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override.

9. Create a mountpoint to which you will mount the files system that you just created in the newly prepared “disk”: # mkdir /mnt/lun2fs

# mount /dev/sdb1 /mnt/lun2fs

Use the mount and df commands to see if your file system was mounted:

# mount

# df




STEP ACTION

10. Change the directory into your new file system, and create a file: # cd /mnt/lun2fs

# touch foo

# ls -l

total 20

-rw-r--r-- 1 root root 0 Jan 23 15:39 foo

drwx------ 2 root root 16384 Jan 23 15:38 lost+found

11. Task complete.

END OF EXERCISE


E16-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Availability Overview


MODULE 16: AVAILABILITY OVERVIEW

EXERCISE

OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current availability exercise environment.

OBJECTIVES


Identify the hardware available in your exercise configuration

TIME ESTIMATE

15 minutes




EXERCISE 16: AVAILABILITY OVERVIEW

The goal of this exercise is to give you an opportunity to identify the current availability exercise environment with the assistance of your instructor.

START OF EXERCISE


This task familiarizes you with the exercise environment that you will use for all exercises in the availability exercises.

STEP ACTION

1. With the assistance of your instructor, identify the following essential equipment: Windows Server


Name: ______________________________

IP address: _________________________

Domain

Administrator

Password: __________________________

Local

Administrator

Password: __________________________

Domain Controller

Domain Name: _______________________

Controller

IP address: _________________________

DNS: ____________________________

IP address: _________________________




STEP ACTION Storage System

Name: ___________________________________

Type: ___________________________________

Internal

IP address: _______________________________

Terminal

IP address: _______________________________

Root

Password: _______________________________

NOTE: During the High-Availability (Module 21) and SnapMirror (Module 23) exercises, your assigned storage system will be paired with another storage system to complete the exercises.




Name: _____________________________

IP address: __________________________

Root

Password: ___________________________

3. Task complete.

END OF EXERCISE



E17-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Snapshot Copies


MODULE 17: SNAPSHOT COPIES

EXERCISE

OVERVIEW

The purpose of this exercise is to give you the opportunity to create and manage Snapshot™ copies, using NetApp® System Manager and the command-line interface.

OBJECTIVES


Create Snapshot copies using NetApp System Manager Restore a Windows® file from a Snapshot copy Restore a UNIX® file from a Snapshot copy Manage Snapshot copies using NetApp System Manager Create a FlexClone using the command-line interface

TIME ESTIMATE

30 minutes




EXERCISE 11: SNAPSHOT COPIES

This task demonstrates methods of creating and managing Snapshot copies on a storage system.

START OF EXERCISE

TASK 1: CREATE A SNAPSHOT COPY USING NETAPP SYSTEM MANAGER

In this task, you will create a Snapshot copy using NetApp System Manager.

STEP ACTION

1. Using NetApp System Manager, click Storage > Volumes

2. Select a volume for which you want to create a Snapshot copy. For this exercise, choose the NFSvol volume.

3. From the Snapshot menu, select Create. A pop-up window will appear.

4. Type the name of your new Snapshot copy. Call this Snapshot copy snapA.

Click Create to take the Snapshot copy.

5. In the lower pane, click the Snapshot Copies tab if it is not visible.

The new Snapshot copy should appear in the list of Snapshot copies.

6. Task complete.




TASK 2: RESTORING A WINDOWS FILE FROM A SNAPSHOT COPY

In this task, you will delete a file within the storage system’s etc directory and recover it from a Snapshot copy.

STEP ACTION

1. Make sure that vol0 has at least one Snapshot copy. system> snap create vol0 snapA

2. From the Windows environment, map the c$ share from your storage system. Use the method of your choice or follow these directions:

Click Start > Run.

In the textbox, enter: \\ip_address_of_storage_system\C$

Click OK.

Navigate to the /etc directory.

Locate the exports.bak file and delete it.

3. If the ~snapshot directory is not displayed, at the storage system console prompt, enable the option to make Snapshot copies visible. system> options cifs.show_snapshot on

You may also need to go to Organize > Folder and Search Options > View. From the View tab, choose “Show hidden files and folders”. If necessary, disconnect the map drive and map it again.

The Snapshot directory will appear at the level the drive is mapped.

4. Navigate to the ~snapshot directory and locate the file in the /etc directory under the snapA Snapshot folder.

5. Copy the file back to its original location at /etc/exports.bak.

6. Task complete.

TASK 3: RESTORING A UNIX FILE FROM A SNAPSHOT COPY

In this task, you will restore a file from a Snapshot copy on your assigned UNIX/LINUX machine.

STEP ACTION

1. From the UNIX/LINUX’s command-line interface, navigate to the storage system /vol/NFSvol/unix_tree and delete unix_file, which was created in a previous exercise. # cd /mnt/<storage_name>/unix_tree

# rm unix_file




STEP ACTION

2. Now restore the unix_file file from the Snapshot copy.

Change directory (cd) to the .snapshot directory at the root of the mountpoint: # cd /mnt/<storage_name>/NFSvol/.snapshot/snapA/unix_tree

# cp unix_file /mnt/<storage_name>/unix_tree

# cd /mnt/<storage_name>/unix_tree

# ls –l unix_file

3. Task complete.

TASK 4: MANAGE SNAPSHOT COPIES USING NETAPP SYSTEM MANAGER

In this task, you will manage Snapshot copies using NetApp System Manager.

STEP ACTION

1. Using NetApp System Manager, go to Storage > Volumes.

Select the NASvol volume. From Snapshot button, click the sub-menu Configure.

The Configure Volume Snapshots dialog box should appear.




STEP ACTION

2. Configure hourly Snapshot copies for the NASvol volume to occur at 10:00 a.m., 12:00 p.m., 2:00 p.m., and 5:00 p.m.

Click OK.

3. Do hourly Snapshot copies occur every hour? ________

4. How can you view the Snapshot copy schedule for the root volume?

__________________________________

5. Can you change the percentage for the Snapshot reserve?

________________________

6. View the amount of space used by a Snapshot copy. Select a volume and click the Snapshot Copies tab. Observe the results.




STEP ACTION

7. Record the totals for snapA on NFSvol below.

snapA Total _______________

8. Task complete.

TASK 5: CREATE A FLEXCLONE USING THE COMMAND-LINE INTERFACE

In this task, you will create a FlexClone of NFSvol called NFSclone using the command-line interface.

STEP ACTION

1. Verify NFSvol exists: system> vol status

Verify the current options of NFSvol: system> vol options /vol/NFSvol

2. Verify the current usage of NFSvol: system> df /vol/NFSvol

Verify the current usage of NFSvol’s supporting aggregate aggr1: system> aggr show_space aggr1

Record the following:

NFSvol Allocated: _______________

Aggr1 Allocated Total Space: _______________

3. License FlexClone (check your instructor your license code): system> license XXXXXXX

4. Create a FlexClone of NFSvol and call it NFSclone: system> vol clone create NFSclone -b NFSvol

5. Verify NFSclone exists: system> vol status

Verify the current options of NFSclone: system> vol options /vol/NFSvol

Compare the volume options of NFSclone and its parent NFSvol.

6. Verify the backing Snapshot for NFSclone: system> snap list NFSvol




STEP ACTION

7. Verify the current usage of NFSclone: system> df /vol/NFSclone

Verify the current usage of NFSclone’s supporting aggregate aggr1: system> aggr show_space aggr1


NFSclone Allocated: _______________


8. Split NFSclone from its backing Snapshot: system> vol clone split start NFSclone

9. Verify the current usage of NFSclone: system> df /vol/NFSclone

Verify the current usage of NFSclone’s supporting aggregate aggr1: system> aggr show_space aggr1


NFSclone Allocated: _______________


Is there any difference after splitting the FlexClone? ______________

10. Task complete.

END OF EXERCISE


E18-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: SnapRestore


MODULE 18: SNAPRESTORE

EXERCISE

OVERVIEW

The purpose of this exercise is to give you practice using the SnapRestore® feature to restore a volume and file.

OBJECTIVES


License and configure SnapRestore Perform a volume SnapRestore Perform a file SnapRestore

TIME ESTIMATE

20 minutes




EXERCISE 18: SNAPRESTORE

Snapshot copies allow nearly instant backups to take of the active file system of a volume. With SnapRestore, storage administrators can very quickly recover a file, a volume, and even an entire aggregate. In this exercise, you will work with SnapRestore to recover a file and volume.

START OF EXERCISE

TASK 1: LICENSE AND CONFIGURE SNAPRESTORE

In this task, you will configure your assigned storage system for SnapRestore.

STEP ACTION

1. License the SnapRestore service: system> license add <code>

2. Check the status of your existing NFSvol. system> vol status NFSvol

3. Create a file named mystuff in your wintree share. system> wrfile /vol/NFSvol/wintree/mystuff

This is new data for the SnapRestore lab.

CTR-C

read: error reading standard input: Interrupted system call

4. Create a Snapshot copy named mystuff that will include your new file. Use either the command line or NetApp® System Manager. system> snap create NFSvol mystuff

5. Create a second file in the same volume. system> wrfile /vol/NFSvol/wintree/mystuff2

This is a second new file.

CTR-C


6. Create a Snapshot copy named mystuff2 that will include your new file. Use either the command line or NetApp System Manager. system> snap create NFSvol mystuff2




STEP ACTION

7. Create a third file in the same volume. system> wrfile /vol/NFSvol/wintree/mystuff3

This is third new file.

This file is not very big.

CTR-C


8. Create a third Snapshot copy named mystuff3 that will include your new file. Use either the command line or NetApp System Manager. system> snap create NFSvol mystuff3

9. Verify that three Snapshot copies exist. system> snap list NFSvol

10. Task complete.

TASK 2: PERFORM A VOLUME SNAPRESTORE

In this task, you will perform a volume SnapRestore of NFSvol.

STEP ACTION

1. Initiate the volume SnapRestore by issuing the command: system> snap restore –t vol /vol/NFSvol

Data ONTAP® displays a warning message and prompts you to confirm your decision to revert the volume. Press Y to confirm that you want to revert the volume.

2. Data ONTAP lists the Snapshot copies available for volume vol2 and prompts you to indicate which Snapshot copy you want to use for the reversion.

Enter mystuff2 and press Y to confirm that you want to proceed.

3. After the reversion is complete, which files are still present in NFSvol?

____________________________________________________________

____________________________________________________________

4. List the Snapshot copies for vol2.

Compare this list to the list of Snapshot copies that were available before the volume reversion.

Do the lists differ? Why?

____________________________________________________________

____________________________________________________________

5. Task complete.




TASK 3: PERFORM A FILE SNAPRESTORE

In this task, you will perform a file SnapRestore of a file called mystuff.

STEP ACTION

1. Overwrite the content of file1 on vol2 by entering the command: system> wrfile /vol/NFSvol/wintree/mystuff

Now I’m overwriting the contents of mystuff.

CTR-C


2. Verify your changes to the file. system> rdfile /vol/NFSvol/wintree/mystuff

3. Revert mystuff1 from the Snapshot copy mystuff1 system> snap restore /vol/NFSvol/wintree/mystuff

When requested, revert the mystuff Snapshot copy.

How did the restore command differ this time from when you restored a volume?

____________________________________________________________

____________________________________________________________

4. What is the timestamp of the reverted file?

____________________________________________________________

____________________________________________________________

5. Verify the contents in the restored file. system> rdfile /vol/NFSvol/wintree/mystuff

6. Task complete.

END OF EXERCISE


E19-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: SnapVault


MODULE 19: SNAPVAULT

EXERCISE

OVERVIEW

In this exercise, you will configure both the primary and secondary storage systems within a SnapVault® relationship.

OBJECTIVES


Identify primary and secondary systems Configure SnapVault on the primary system Configure SnapVault on the secondary system Initialize the transfer Perform a restore Restart the backup relationship

TIME ESTIMATE

30 minutes




EXERCISE 19: SNAPVAULT

In this exercise you will configure SnapVault on primary and secondary systems. Then, you will perform the baseline transfer, schedule incremental updates, and monitor transfer status. Finally, you will perform a SnapVault restore and trigger a manual update.

START OF EXERCISE

TASK 1: IDENTIFY PRIMARY AND SECONDARY SYSTEMS

In this task, you will identify the SnapVault primary storage system and the SnapVault secondary storage system. Students will work in pairs to complete the rest of the exercise.

STEP ACTION

1. SnapMirror® primary storage system Hostname: IP Address:

2. SnapMirror secondary storage system Hostname: IP Address:

3. Task complete.

TASK 2: CONFIGURE SNAPVAULT ON THE PRIMARY SYSTEM

In this task, you will configure SnapVault on the primary system. NOTE: This task should only be completed by the students managing the primary storage systems within the SnapVault relationship.

STEP ACTION

1. Install the sv_ontap_pri license: pri> license add <code>

2. Enable the NDMP service: pri> options ndmpd.enable on

3. Enable SnapVault access permissions with the options command: pri> options snapvault.access host=<secondary_hostname>

4. Create a flexible volume named vol1 in aggregate aggr1: pri> vol create vol1 aggr1 100m

5. Create a qtree named q1 in the volume vol1: pri> qtree create /vol/vol1/q1




STEP ACTION

6. Create a CIFS share to access the vol1 volume: pri> cifs shares –add <sharename> /vol/vol1

7. Map a network drive to the volume vol1.

8. Copy the Dataset1 directory from the C:/_files/ANCDA into the qtree q1.

9. Schedule SnapVault Snapshot™ copy creation using the snapvault snap sched command syntax: pri> snapvault snap sched vol1 sv_hourly 5@mon-fri@9-19

What is the name of the Snapshot copy? ____________________________________

When will SnapVault Snapshot copies creation occur? _________________________

How many Snapshot copies will be retained? ________________________________

10. Task complete.

TASK 3: CONFIGURE SNAPVAULT ON THE SECONDARY SYSTEM

In this task, you will configure SnapVault on the secondary system. NOTE: This task should only be completed by the students managing the secondary storage systems within the SnapVault relationship.

STEP ACTION

1. Install the sv_ontap_sec license: sec> license add <code>

2. Enable the NDMP service: sec> options ndmpd.enable on

3. Enable SnapVault access permissions to all with the options command: sec> options snapvault.access all

4. Create a flexible volume named vol1 in aggregate aggr1: sec> vol create vol1 aggr1 100m

5. Create a CIFS share to access vol1: sec> cifs shares –add <sharename> /vol/vol1

6. Map a network drive to the volume vol1.

7. Task complete.




TASK 4: INITIALIZE THE TRANSFER

In this task, you will perform the baseline transfer. NOTE: This task should only be completed by the students managing the secondary storage systems within the SnapVault relationship.

STEP ACTION

1. Perform the baseline initial transfer for q1 by using the snapvault start command syntax: sec> snapvault start –S pri_hostname:/vol/vol1/q1 sec_hostname:/vol/vol1/q1

2. Verify that the secondary qtree q1 was created in the secondary volume vol1: sec> qtree status

3. Issue the snapvault status –c command and note the values obtained for the retries and the kbs entries: sec> snapvault status –c

kbs: ____________________________

tries: __________________________________________

4. Schedule SnapVault Snapshot copy creation using the command syntax: sec> snapvault snap sched –x vol1 sv_hourly 5@mon-fri@9-19

What did the -x parameter mean when you scheduled Snapshot copies creation?

5. Task complete.

TASK 5: PERFORM A RESTORE

In this task, you will delete a directory from the primary storage system and then perform a restore of the directory from the secondary system back to the primary. NOTE: This task should only be completed by the students managing the primary storage systems within the SnapVault relationship.

STEP ACTION

1. Delete the Dataset1 directory in the primary qtree q1.

2. Restore the qtree from the primary system using the command: pri> snapvault restore –S sec_hostname:/vol/vol1/q1 pri_hostname:/vol/vol1/q1

3. Verify that the Dataset1 directory was restored to the primary qtree q1.

4. Task complete.




TASK 6: RESTART THE BACKUP RELATIONSHIP

In this task, you will restart the backup relationship and trigger a manual update. NOTE: This task should only be completed by the students managing the secondary storage systems within the SnapVault relationship.

STEP ACTION

1. Copy the Dataset2 directory from C:\_files\ANCDA in primary qtree q1.

2. From the secondary, trigger a manual update using the command: sec> snapvault update sec_hostname:/vol/vol1/q1

3. Verify that the Dataset2 directory is present in the secondary qtree q1.

4. Task complete.

END OF EXERCISE


E20-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Open Systems SnapVault


MODULE 20: OPEN SYSTEMS SNAPVAULT

EXERCISE

OVERVIEW

In this exercise, you will install the Open Systems SnapVault® agent software on a Windows® Server client.

OBJECTIVES


Install Open Systems SnapVault for Windows Server Configure the SnapVault Secondary System Configure Windows Server 2008 R2’s firewall for Open System Snapvault Establish the Open Systems SnapVault baseline Perform a restore and resume SnapVault operations

TIME ESTIMATE

30 minutes




EXERCISE 20: OPEN SYSTEMS SNAPVAULT

In this exercise, you will install the Open Systems SnapVault agent software on a Windows Server client. You will then perform Open Systems SnapVault basic operations, such as the initial transfer, triggering a manual update, restoring the backed-up data, and resume SnapVault operations.

START OF EXERCISE

TASK 1: INSTALL OPEN SYSTEMS SNAPVAULT FOR WINDOWS SERVER

In this task, you will log in to your assigned Windows Server and install Open Systems SnapVault.

STEP ACTION

1. Log in to the Windows Server with Administrator privileges.

2. Unzip the Open System Snapvault package found at C:\_files\ANCDA into a temporary directory on the Windows platform.

3. Navigate to the temporary directory where you unzipped the files for the system.

Locate and double-click the Setup.exe file.

4. The Open Systems SnapVault Setup Wizard is launched.

Click Next.

5. The License Agreement window appears.

Click I Agree to accept the license agreement and click Next.

6. The Choose NDMP Username/Password window displays.

The user name and password are used to communicate with NDMP-based application such as Protection Manager for central management of Open Systems SnapVault primary systems. In this exercise, you won’t use Operations Manager; therefore you do not have to specify NDMP credentials.

Click Next.

7. The NDMP Listen Port window appears.

Keep the default listening port setting of 10000, and click Next.

8. The Allowed Secondary Names window appears.

Enter the host name or the IP address of the SnapVault secondary storage system that you want to back up on this primary storage system.




STEP ACTION

9. When the Select Installation Folder window prompts you for the installation directory, accept the default location.

Click Disk Cost to view the available disk space, and click Next.

10. The Install NetApp Host Agent window displays. The Host Agent allows communication with NetApp Protection Manager. We will not use it in this exercise.

Click Next.

11. Click Next to start the installation process and wait until the Installation Complete window appears with the following message:

Open Systems SnapVault has been successfully installed.

Click Close to exit.

12. Restart the Windows workstation.

13. Open the Open Systems SnapVault Configurator: Windows > Start > OSSV Configurator.




STEP ACTION

14. Stop the Open Systems SnapVault service using the Open Systems SnapVault Configurator’s Service tab.

15. Click the SnapVault tab and check the option Enable Restart/resync on restore.

16. Start the Open Systems SnapVault service using the Open Systems SnapVault Configurator’s Service tab.




STEP ACTION

17. Navigate to the bin directory within the install location of the OSSV client.

C:\ > cd C:\Program Files\netapp\snapvault\bin

18. Run the install checker to verify the OSSV client’s install status.

C:\Program Files\netapp\snapvault\bin> svinstallcheck

Review the results.

19. Task complete.

TASK 2: CONFIGURE THE SNAPVAULT SECONDARY SYSTEM

In this task, you will configure the SnapVault secondary system.

STEP ACTION

1. Install the sv_ontap_sec license if not yet installed:

sec> license add <code>

Install the sv_window_pri license:

sec> license add <code>

2. Enable SnapVault access permission to all with the options command:

sec> options snapvault.access all

3. Verify that SnapVault is on:

sec> options snapvault.enable

If it is off, turn it on.

4. Verify NDMP daemon is enabled.

sec> options ndmpd.enable

If it is off, turn it on.

5. Create a flexible volume named vol2 in aggregate aggr1. The volume size will be 100m.

sec> vol create vol2 aggr1 100m

6. Create a CIFS share on the secondary to access vol2:

sec> cifs shares –add <sharename> /vol/vol2




STEP ACTION

7. Map a network drive to the volume vol2 on your Windows server.

8. Task complete.

TASK 3: CONFIGURE WINDOWS SERVER 2008 R2’S FIREWALL FOR OPEN SYSTEM SNAPVAULT

In this task, you will configure Windows 2008 R2’s native firewall for SnapVault traffic.

STEP ACTION

1. Open Server Manager by clicking the Server Manager icon next to the Start button.





STEP ACTION

2. Expand Configuration and then select Windows Firewall with Advanced Security from the left pane. Expand this tool by clicking the + next to the Firewall node in the left pane.

The Windows Firewall with Advanced Security configuration interface should be visible.

3. If you review the main pane, you will notice that the current profile is the domain profile. Record how the profile is configured:

Windows Firewall: ___________

Inbound connections: ________________

Outbound connections: _______________




STEP ACTION

4. There are inbound and outbound rules you can configure. We need to configure a new inbound rule that allows port 10000 and 10566 traffic. We will do that now.

Click Inbound Rules from the left pane.

The Inbound Rules configuration page should appear.




STEP ACTION

5. Click the New Rules action from the right pane if visible or right-click on the Inbound Rules node within the left pane and New Rule… to start the new New Rule wizard.

The wizard should began.

6. Choice Port as the rule type. Click Next.




STEP ACTION

7. On the Protocol and Ports page, ensure that the rule is a TCP type.

Make certain that the Specific local ports is selected and within the textbox, enter the SnapVault required ports with a comma between the two port.

Example: 10000, 10566


8. On the action page, ensure that the option Allow the connection is selected.





STEP ACTION

9. From the Profile page, verify that all profiles are selected and click Next.

10. Name the inbound rule: SnapVault Ports

Provide a description if you like.

Click Finish to create the rule.

You should now the provided provided the proper configuration to the native Windows’ firewall for Open Systems SnapVault.

11. Task complete.

TASK 4: ESTABLISH THE OPEN SYSTEMS SNAPVAULT BASELINE

In this task, you will create the folder to be replicated on your assigned Windows Server and start the initial baseline transfer.

STEP ACTION

1. On the Windows Server, create a folder named ossv on the C drive.

2. With WordPad or Notepad, create a couple of text files that you will save in C:\ossv.

3. Perform the SnapVault initial baseline transfer. At this stage the destination qtree ossv does not exist and will be created by the snapvault start command:

sec> snapvault start –S prim_hostname_or_ip:c:\ossv /vol/vol2/ossv

4. Verify that the secondary qtree ossv was created in the secondary volume of vol2.

sec> qtree status

5. Issue the snapvault status –l command to collect the following information:

State of the relationship: ______________________________________

Snapshot™ copy created for the baseline transfer: ____________________

Last transfer type: ____________________________________________

Transfer size and duration: _____________________________________




STEP ACTION

6. On the Open Systems SnapVault primary, drop down to the bin directory to run and verify the outputs of the following commands:

C:\Program Files\netapp\snapvault\bin\snapvault destinations

C:\Program Files\netapp\snapvault\bin\snapvault status

7. On the primary system, add new files in the ossv directory.

Then from the SnapVault secondary, trigger a manual update:

sec> snapvault update vol/vol2/ossv

8. Check that the changes were applied to the ossv qtree replica.

9. Use the snap list command to display the SnapVault Snapshot copies present in the destination volume vol2.

How many SnapVault Snapshot copies are listed? Why?

______________________________________________________________

______________________________________________________________

10. Task complete.

TASK 5: PERFORM A RESTORE AND RESUME SNAPVAULT OPERATIONS

In this task, because restoring to a directory that is a part of a SnapVault relationship is not allowed, you will restore the contents of the ossv directory to a new location.

STEP ACTION

1. On the Open Systems SnapVault primary, delete the source directory ossv.

2. To restore the contents of the ossv directory to a new location named ossv1, use the command syntax:

C:\Program Files\netapp\snapvault\bin\>snapvault restore –S sec_IP:/vol/vol2/ossv C:\ossv1

NOTE:If during the Open Systems SnapVault agent installation, you specified the IP address of the authorized secondary system, you must enter this IP address in the command syntax.

You do not have to create the ossv1 directory; the snapvault restore command will create it on the C drive.




STEP ACTION

3. We want to now restart the Open System SnapVault relationship. Rename ossv1 to ossv:

C:\> rename ossv1 ossv

4. Resynchronize the relationship from the secondary with the following command:

sec> snapvault start –r –S prim_hostname:C:\ossv /vol/vol2/ossv

5. Which Open Systems SnapVault relationship is now active on the secondary system? (Hint: snapvault status)

______________________________________________________________

6. Display the SnapVault logs from the Open Systems SnapVault client and the secondary system. You should see entries for the initial baseline transfer, the manual update, and the restore operations:

On the secondary: /etc/logs/snapmirror

On the Open Systems SnapVault primary:

C:\Program Files\netapp\snapvault\etc\snapvault

7. Task complete.

END OF EXERCISE


E21-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: High Availability


MODULE 21: HIGH-AVAILABILITY

EXERCISE

OVERVIEW

The purpose of this exercise is to give you an opportunity to enable a high-availability configuration and observe how it works.

OBJECTIVES


License and configure controller failover Perform a controller failover Perform a controller giveback Restart a CIFS client connection after a failover

TIME ESTIMATE

30 minutes




EXERCISE 21: HIGH-AVAILABILITY

Together with a partner’s storage system, you will configure a high-availability pair. NOTE: This exercise needs to be done by coordinating with the partner storage system that is cabled with your own storage system.

START OF EXERCISE

TASK 1: LICENSE AND CONFIGURE CONTROLLER FAILOVER

In this task, you will identify your partner and work together to fail over one of the storage systems. If you have any difficulty identifying your partner, please contact your instructor.

STEP ACTION

1. If available, look at the hardware on your system. Do you see any indication that your storage system is cabled for high availability? ______________________

What command will give you information about the hardware installed on your storage system?

___________________________________________________________

Your instructor will help you identify the system that is cabled as the partner for your system. (HINT: use sysconfig)

Identify which storage system will be system and which system will be system2.

system _______________________________

system2 _______________________________

2. License each system.

system> license add <license>

system> cf status

system2> license add <license>

system2> cf status

What does the cf status command tell you before you reboot?

____________________________________________________________

3. Reboot each system.

system> reboot

system2> reboot




STEP ACTION

4. Enable high availability on one of the systems.

system or system2> cf enable

How does this affect the other system?

____________________________________________________________

Check the status of each system:

system> cf status

system2> cf status

5. On both Windows® environments, use NetApp® System Manager and select the NetApp System Manager node in the left pane.

NOTE: Your partner will do the same for the other system in the high-availability pair.

Click the Refresh button.

What happens? ____________________

Why? ___________________________

If your storage system disappears and you don’t see the new high-availability pair, add your storage systems again to System Manager by clicking the Add button and providing its e0a IP address.

What happens? ____________________




STEP ACTION

6. Be sure to configure the partner interface.

Use NetApp System Manager to navigate to your storage system’s interface configuration. NOTE: Your partner will do the same for the other system in the high-availability pair.

Select the e0b interface. This interface should be cabled to the network properly prior to class.

Right-click and select Edit.

Within the Edit Network Interface dialog, enter the following:

HA failover mode: Standby

Partner Interface: e0a

Click OK to accept the changes.

7. Verify the network configuration.

Verify that e0b is up by entering the following at the console:

system or system2> ifconfig e0b up




STEP ACTION

8. Task complete.

TASK 2: PERFORM A CONTROLLER FAILOVER

In this task, you will fail over the first storage system to the second system (system2). NOTE: This task should be performed using only one NetApp System Manager session.

STEP ACTION

1. On the first system (system), locate the files from a previous lab.

From your Windows host, view the mapped drive for the CIFS share and then view the drive associated with the iSCSI LUN on your storage system. Later you will want to check that you can still access these files during a takeover.

2. Within NetApp System Manager, click the Active/Active Configuration node within the left pane.

Have system2 take over for system by selecting the Takeover button on the appropriate system.

NOTE: The licenses have to match exactly on both nodes of the high-availability pair for takeover to occur. Other requirements might also need to be meant. See the status dashboard for your high-availability pair in NetApp System Manager for any unresolved issues.

The Active/Active Configuration wizard should begin. Click Next to start the wizard.




STEP ACTION

3. Click Normal takeover.

Click Next.

4. Click Next and then close when the takeover is complete.

5. Check the console of system2. How long did it take for system2 to complete the takeover? ______________

6. Observe the results on the clients.

What happens to the Windows client connection? ______________

Check the mountpoint on the UNIX® client. What happens to the UNIX connection?______________

What caused the difference between NFS and CIFS connections during takeover?

___________________________________________________________




STEP ACTION

7. On system2, observe the new prompt:

system2(takeover)>

On system, observe the new prompt:

system> Waiting for giveback

Run the following commands:

system2(takeover)> sysconfig –r

system2(takeover)> sysconfig –v

system2(takeover)> sysstat 1

Use Cotnrol-c to end sysstat command.

Now run the same commands from within the “takeover” system:

system2(takeover)> partner

system2/system> sysconfig –r

system2/system> sysconfig –v

system2/system> sysstat 1

Use Cotnrol-c to end sysstat command.

Was there a difference between the two storage system outputs?

____________________________________________________________

____________________________________________________________

8. Access your CIFS share from your client. Can you still access your data?

____________________________________________________________

____________________________________________________________

How about the LUN? Can you still access the LUN?

____________________________________________________________

____________________________________________________________

9. Task complete.




TASK 3: PERFORM A CONTROLLER GIVEBACK

In this task, you will use the command-line interface or a single NetApp System Manager session to give back control from system2 to the first storage system (system).

STEP ACTION

1. Restore the failover storage system to service.

Example:

From the down system’s console, reboot the system. When you are prompted with the message, “Waiting for giveback,” issue the command:

system2> cf giveback -f

Do you need -f? Why or why not?

___________________________________________________________

___________________________________________________________

Alternatively, you can select the Giveback button within NetApp System Manager:

2. Check the high-availability status:

system> cf status

system2> cf status

Alternatively, you can analyze the status of your high-availability pair with NetApp System Manager.

3. Task complete.

END OF EXERCISE


E22-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: MetroCluster


MODULE 22: METROCLUSTER

EXERCISE



E23-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: SnapMirror


MODULE 23: SNAPMIRROR

EXERCISE

OVERVIEW

In this exercise, you will set up SnapMirror® to perform asynchronous volume replication between two storage systems and then reconfigure SnapMirror asynchronous to a synchronous configuration.

OBJECTIVES


Identify the source and destination systems Set up SnapMirror on the source storage system Set up SnapMirror on the destination storage system Initiate a baseline transfer and schedule updates Break the SnapMirror relationship Reinstate the original SnapMirror relationship Configure synchronous SnapMirror

TIME ESTIMATE

45 minutes




EXERCISE 23: SNAPMIRROR

In this exercise, you will set up SnapMirror to perform asynchronous volume replication between two storage systems. Additionally you will perform advanced operations such as breaking and resynchronizing the SnapMirror relationship. Finally, you will configure SnapMirror for synchronous replication.

START OF EXERCISE

TASK 1: IDENTIFY THE SOURCE AND DESTINATION SYSTEMS

In this task, you will identify the source and destination systems within the SnapMirror relationship. NOTE: If you have difficulty identifying your partner, please ask your instructor.

STEP ACTION

1. SnapMirror source storage system Hostname: IP Address:

2. SnapMirror destination storage system Hostname: IP Address:

3. Task complete.

TASK 2: SET UP SNAPMIRROR ON THE SOURCE STORAGE SYSTEM

In this task, you will configure SnapMirror on the source storage system. NOTE: This task will only be completed if you are managing the source storage system within the SnapMirror relationship.

STEP ACTION

1. License SnapMirror:

source> license add <code>

2. Configure the SnapMirror destination storage system authorized to replicate the source storage system:

source> options snapmirror.access host=<destination_hostname>

3. Create a flexible volume named vol3 in the existing aggregate aggr1. The volume size will be 10g.

source> vol create vol3 –s none aggr1 10g

Set the volume to be ntfs security style.

source> qtree security /vol/vol3 ntfs

Verify.

source> qtree status




STEP ACTION

4. Create a CIFS share for volume vol3:

source> cifs shares –add <sharename> /vol/vol3

5. Map a network drive to volume vol3.

6. Copy the Dataset1 directory from C:\_files\ANCDA to volume vol3.

7. Task complete.

TASK 3: SET UP SNAPMIRROR ON THE DESTINATION STORAGE SYSTEM

In this task, you will configure SnapMirror on the destination storage system. NOTE: This task will only be completed if you are managing the destination storage system within the SnapMirror relationship.

STEP ACTION

1. License SnapMirror:

destination> license add <code>

2. Set SnapMirror access permission by specifying the host name of the source storage system:

destination> options snapmirror.access host=<source_hostname>

3. Create a flexible volume vol3 in the existing aggregate aggr1. The volume size will be 10g.

destination> vol create vol3 aggr1 10g

Set the volume to be ntfs security style.

source> qtree security /vol/vol3 ntfs

Verify.

source> qtree status

4. Create CIFS shares for volume vol3:

destination> cifs shares –add <sharename> /vol/vol3

5. Map a network drive to volume vol3.

6. Task complete.




TASK 4: INITIATE A BASELINE TRANSFER AND SCHEDULE UPDATES

In this task, you will initiate the baseline transfer and schedule updates within SnapMirror. NOTE: This task will only be completed if you are managing the destination storage system within the SnapMirror relationship.

STEP ACTION

1. Restrict the destination volume vol3:

destination> vol restrict vol3

2. Create a baseline initial transfer for volume vol3:

destination> snapmirror initialize –S src_hostname:vol3 dst_hostname:vol3

Example:

system2> snapmirror initialize –S system:vol3 system2:vol3

3. The /etc/snapmirror.conf file does not exist by default. Verify that the file does not exist by using the rdfile command to read the file. You should receive a message stating that there is no such file.

Example:

system2> rdfile /etc/snapmirror.conf

Verify that the Dataset1 directory is present in the destination volume vol3.

4. What is the state of the SnapMirror relationship?

Hint: Use the snapmirror status command.

________________________________________________________

5. What is the status of the destination volume vol3?

Hint: Use the vol status command.

________________________________________________________

6. Note the Snapshot copy name created by the baseline transfer.

Hint: Use the snap list command.

________________________________________________________




STEP ACTION

7. Using a text editor or the Data ONTAP® wrfile command create the /etc/snapmirror.conf file on the destination root volume.

Edit the configuration file to add this entry:

src_hostname:vol3 dst_hostname:vol3 – 30 * * *

What do the four entries in the schedule field mean? And how often will vol3 replicate?

________________________________________________________

________________________________________________________

8. Task complete.

TASK 5: BREAK THE SNAPMIRROR RELATIONSHIP

In this task, you will break the SnapMirror relationship from the destination side. NOTE: This task will only be completed if you are managing the destination storage system within the SnapMirror relationship.

STEP ACTION

1. From the SnapMirror destination storage system, convert the read-only volume replica to a writable file system:

destination> snapmirror break vol3

2. Delete the Dataset1 directory on the SnapMirror destination volume.

Did the operation succeed?

________________________________________________________

3. What is the state of the SnapMirror relationship on the destination storage system?


________________________________________________________

4. Task complete.




TASK 6: RESYNCHRONIZING THE RELATIONSHIP

In this task, you will resynchronize the SnapMirror relationship from the source side. Remember that resync can be initiated from different sides of SnapMirror relationship with different consequences. Please refer to the lecture portion of this module for more information. NOTE: This task will only be completed if you are managing the source storage system within the SnapMirror relationship.

STEP ACTION

1. To replicate only the changed blocks from the source to the destination systems, resynchronize the SnapMirror relationship from its direct source.

source> snapmirror resync -S dst_hostname:vol3 src_hostname:vol3

Answer yes or y when prompted to confirm the command.

2. Is the Dataset1 directory present in the SnapMirror source volume? Why?

________________________________________________________

3. On the source system display all the registered SnapMirror relationships. (Hint: snapmirror status command)

Note the entry for the relationship created by the resync operation.

From: _____________________To: __________________________

4. Copy the Dataset2 directory in the source volume vol3.

Did the operation succeed? Why?

________________________________________________________

5. Break the reverse relation created by the resync operation.

source> snapmirror break vol3

6. Copy the Dataset2 directory in the source volume vol3.

Did the operation succeed?

________________________________________________________

7. Task complete.




TASK 7: REINSTATE THE ORIGINAL SNAPMIRROR RELATIONSHIP

In this task, you will resynchronize the SnapMirror relationship from the destination side. Remember that resync can be initiated from different sides of SnapMirror relationship with different consequences. Please refer to the lecture portion of this module for more information. NOTE: This task will only be completed if you are managing the destination storage system within the SnapMirror relationship.

STEP ACTION

1. To reinstate the original SnapMirror relationship, you have to resync it, but this time you will issue the command from the destination storage system.

destination> snapmirror resync –S src_hostname:vol3 dst_hostname:vol3

Answer yes or y when prompted to confirm the command.

2. Verify that the Dataset2 directory is present in the destination volume.

3. You can check that the original relationship was successfully reinstated by triggering a manual update.

But first, copy the Dataset3 directory into the source volume. After the manual update, we will verify whether Dataset3 was mirrored to the destination volume.

Trigger a SnapMirror update from the destination volume:

destination> snapmirror update vol3

Check that the Dataset3 directory is present in the destination volume vol3.

4. Task complete.

TASK 8: CONFIGURE SYNCHRONOUS SNAPMIRROR

In this task, you will change your asynchronous SnapMirror configuration to a synchronous configuration.

STEP ACTION

1. License SnapMirror for synchronous replication on the source and the destination storage systems.

source> license add <code>

destination> license add <code>

2. Delete the Dataset3 directory on the source volume.

3. Edit the existing snapmirror.conf file and modify the schedule field as follows:

src_hostname:vol3 dst_hostname:vol3 – sync

4. Use the snapmirror status command to ensure that the relationship is in sync.




STEP ACTION

5. Is the Dataset3 directory present in the destination volume?

______________________________________________________

6. On the destination, edit the snapmirror.conf file and comment out, with a pound sign (#), the entry:

src_hostname:vol3 dst_hostname:vol3 – sync

HINT: You can map C$ to edit this file.

7. Review the history of the SnapMirror operations you performed reading from the SnapMirror log file. HINT: Use the rdfile /etc/log/snapmirror command.

8. What is the state of the SnapMirror relationship? __________________________


Does the relationship ever transition into synchronous SnapMirror? __________

NOTE: Depending on your exercise environment, this transition may not occur. Verify that your exercise environment supports a synchronous SnapMirror environment.

9. Task complete.

END OF EXERCISE


E24-1 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Performance


MODULE 24: PERFORMANCE

EXERCISE



NETAPP UNIVERSITY

Appendix A: Answers Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode

Exercise Guide



EA-2 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Appendix A: Answers


Answers

Module 1: NCDA Overview

© 2010NetApp, Inc. All rights reserved.

Check Your Understanding: Answers

How is Data ONTAP 7G and Data ONTAP GX related in Data ONTAP 8.0?– Data ONTAP 7G and Data ONTAP GX are now

merged into a single code under Data ONTAP 8.0, however, a storage system may be only configured one mode at a time

What are the two storage topologies supported by Data ONTAP?– NAS

– SAN

How is SAN different than NAS?– SAN topologies are used for block-based storage– NAS topologies are used for file-based storage




Answers

Module 2: NFS Overview



NFS is based on client-server architecture. True or false?– True

List the three versions of NFS.– Versions 2, 3, and 4

What does stateful mean?– Information is stored (remembered) by the server between separate

calls of a particular user on a client NFS v3 is a stateful protocol. True or false?

– False NFS v4 is a stateful protocol. True or false?

– True What is a netgroup?

– A network-wide group of machines granted identical access to certain network resources for security and organizational reasons




Answers

Module 3: NFS Setup



What command would you use to view configured NFS characteristics?– options nfs

Can you use NFS v4 over UDP?– No, disabling TCP will disable NFS v4.

NFS v4 doesn’t require Kerberos. True or false?– False

Can Data ONTAP be an NIS slave? – Yes

Will Data ONTAP use an NIS+ environment?– Only in NIS compatibility mode

LDAP can be configured to use SSL. True or false?– True




Answers

Module 4: Exports and Mounts



What is a target?– A destination to which resources are exported

What is a resource?– An exported object

Give examples of a target.– Subnet– Netgroup– Client– Subdomain

Give examples of a resource.– Volume– Directory– File– Qtree





Check Your Understanding: Answers (Cont.) Can you specify rw and ro for the same host within a

single export? – Yes, but that entry will result in an error

What must be defined on the target to receive exported resources?– Mountpoint

The /etc/exports file typically resides on the target. True or false?– False

What does exportfs –c 10.0.0.1 /vol/vol2 rw do?– Verifies if the host can mount a path read-write




Answers

Module 5: CIFS Overview



In a network, which two abilities does a Windows client user require?– Find other computers

– Request resources from a server

What is the difference between user authentication and authorization?– User authentication = user identity verification

– User authorization = allows certain functionality at the share or file level





Check Your Understanding: Answers (Cont.)

What are the three types of storage system CIFS service environments?– Windows workgroup

– Non-Windows workgroup

– Windows domain

What is the purpose of a name resolution server?– To resolve machine names to IP addresses



What kind of information is kept in the directory that the domain controller stores and maintains? – Machine accounts

– User names/passwords/rights

– Group membership information

– Group policies

In a Windows workgroup, how does a storage system authenticate users?– Locally






In a Windows domain, how does a storage system authenticate users?– By means of a domain controller

In a non-Windows workgroup, how does a storage system authenticate users?– By way of UNIX mechanisms: Local /etc/passwd file

NIS server

LDAP server




Answers

Module 6: CIFS Workgroups



In cifs setup, what are the two security style choices for which a storage system can be configured?

NTFS-only

Multiprotocol During the initial questions in cifs setup, for which root user

can you enter a password?

The UNIX root user in the /etc/passwd file

Used in a non-Windows workgroup only

What are the three default share volumes created as a result of cifs setup?

C$, ETC$, HOME

What is the name of the NetBIOS alias file?

cifs_nbalias.cfg




Answers

Module 7: CIFS Shares and Sessions



For which storage objects can you create shares?foldersqtreesvolumes

What are three methods to manage CIFS shares?CLINetApp System ManagerMicrosoft tools such as Computer Management

What command would you use to view the connected CIFS users?cifs sessions




Answers

Module 8: CIFS Access Control



What is the purpose of a local administrator account on a storage system, and why does cifs setuprecommend creating one?The local administrator can administer CIFS access to the storage system when the domain controller is down

What does it mean when a storage system is configured for multiprotocol access?Any file can be accessed by NFS (UNIX users) and CIFS (Windows users) protocols; both NFS and CIFS must be licensed

What command adds local users and groups to the storage system?useradmin




Answers

Module 9: CIFS Domains



For which objects can you create shares?FoldersQtreesVolumes

What are three methods used to manage CIFS shares?Command-line interfaceMicrosoft tools such as Computer ManagementNetApp System Manager

CIFS Kerberos-based authentication fails if the time difference between the storage system and the domain controller is more than how many minutes?Five minutes

Which command or commands allow you to configure the preferred domain controllers?cifs prefdc




Answers

Module 10: NAS Multiprotocol



A UNIX user cannot ever access a file with a Windows ACL but a Windows user can access a file with UNIX permissions. True or false?False, if NAS multiprotocol is configured correctly

Windows users are only associated and resolved to a UNIX user if the Windows user is attempting to access a file with UNIX permissions. True or false?False, Windows users are always associated with a UNIX user

Which file is used to associate Windows users and UNIX users?/etc/usermap.cfg

Which command allows administrators to display a cached UNIX user’s mapping to a given Windows user?wwc -s ntname




Answers

Module 11: NAS Troubleshooting



When troubleshooting a NAS protocol on the storage system, what is one of the first steps you should do to verify the appropriate service is available?– Verify that the NAS protocol has a valid license

How do you configure the order of the hostname-to-IP resolution mechanism on the storage system?– Edit /etc/nsswitch.cfg

Which command is used to capture network packet traces on the storage system?– pkkt

What third-party application can be used to read the native packet traces created on the storage system?– Wireshark– Netmon, if converted




Answers

Module 12: SAN Overview



If NAS provides file-level access, then SAN provides what?– Block-level access to data on storage

What is it called when NAS and SAN are both implemented on a NetApp storage system?– Unified storage

The initiator is on the host and the target is on the storage system. True or false? – True




Answers

Module 13: FC Connectivity



Using Data ONTAP 8.0 7-Mode, which cfmode(s) can you configure a new storage system?– single_image

What two FC multipathing software stacks are available for Windows?– Veritas and Native Windows

Which three software libraries are required for the sanluncommand function in the Linux Host Utilities Kit?– HBAnyware and 32-bit and 64-bit version of libnl.so

Administrators should use what tool, provided by NetApp and available on the NOW site, to verify their Red Hat configuration?– Interoperability Matrix Tool




© 2010 NetApp, Inc. All rights reserved.


What is the format for the IQN model of WWNNs naming?– iqn.yyyy-mm.backward_naming_authority:device

What two iSCSI multipathing techniques are available for Windows Server 2003 and 2008?– MCS

– MPIO

What command is used to configure the iSCSI software initiator on Red Hat Enterprise Linux?– iscsiadm

Answers

Module 14: iSCSI Connectivity






What is an igroup?– A group of one or more initiators

How does an FC igroup differ from an iSCSI igroup?– An FC igroup contains initiator’s WWPN

– An iSCSI igroup contains initiator’s WWNN

Can you add a LUN to a different igroup using the LUN ID?– Yes

Answers

Module 15: LUN Access




Answers

Module 16: Availability Overview



Which Data ONTAP solutions would you use for backup and rapid recovery?

– Snapshot copies

– SnapRestore

– SnapVault

Which Data ONTAP solutions would you use for system availability?

– Shelf multipathing

– SyncMirror

– High-availability

– MetroCluster

– SnapMirror




Answers

Module 17: Snapshot Copies



What is a Snapshot copy?– A read-only image of the file system

What are some of the NetApp products that are based on Snapshot technology?– SnapRestore

– SnapMirror

– SnapVault

– SnapManager

– SnapDrive

– FlexClone






What are some of the Snapshot commands?– snap list

– snap create

– snap delete

– snap delta

– snap reclaimable

What is the Snapshot schedule syntax?– snap sched [volume_name[weeks[days[hours[@list]]]]]




Answers

Module 18: SnapRestore



What doesn’t SnapRestore revert?– SnapRestore does not revert volume or

aggregate settings such as RAID group size, RAID type, or volume/aggregate options

Which option would you use in a snaprestore command to perform a file restore? – snap restore -t file -s snapshot_namepath_and_file_name

Snapshot copy deletions are ____________.– Irrevocable; if you delete a Snapshot copy, you

cannot recover it using SnapRestore




Answers

Module 19: SnapVault



What is the basic unit for a SnapVault backup and restore?

– qtree

True or false? In Data ONTAP 7.3 and later, you can install both the sv_ontap_pri and the sv_ontap_sec licenses on the same storage system.

– True Which snapvault command and option would you

use to perform an incremental restore?– pri> snapvault restore -r -S sec:/vol/volname/sec_qtree /vol/volname/pri_qtree




Answers

Module 20: Open Systems SnapVault



What is the basic unit of an Open Systems SnapVault backup?– The directory

True or false? A separate license is required to be able to back up open files on Windows Server platforms.– True: sv_windows_ofm_pri is the required

license

Which command and utility would you use to configure or modify Open Systems SnapVault parameters?– Configurator utility GUI and svsetstanza

command




Answers

Module 13: High-Availability



What are three modes of operation for a high-availability controller configuration?– Normal, Takeover, Giveback

What is the purpose of using a high-availability controller configuration?– Fault tolerance– Nondisruptive software upgrades– Nondisruptive hardware maintenance

What happens during a takeover?– Surviving partner has two identities; each identity can only

access appropriate volumes and networks






True or false?

Options must be set the same on both nodes.– True

The license must be set the same on both nodes.– True

Both nodes must have the same number of disks.– False

Both nodes must be part of the same domain.– False




Module 22: MetroCluster

Answers



MetroCluster may be configured in what three configurations?– Stretch, Fabric, or V-Series

What three special licenses are required to implement a MetroCluster? – cf, syncmirror_local, cf_remote

True or false? With special cables and FC switches, Fabric-attached MetroCluster configurations can span up to 100km. – True




Answers

Module 23: SnapMirror



What are the main differences between volume and qtree SnapMirror?– Volume SnapMirror destination volume is read-

only; with qtree SnapMirror, only the qtree replica is read-only

– Volume SnapMirror is a block-for-block replication; qtree SnapMirror is a logical replication

– Volume SnapMirror replicates all Snapshot copies from the source volume to the destination volume; qtree SnapMirror does not transfer Snapshot copies





Check Your Understanding: Answers (Cont.) True or false? When the visibility_interval is

reached it causes the source system to create a Snapshot copy.

– True True or false? Ethernet and FC interfaces may be

logically combined in multi-mode or failover mode.

– True




Answers

Module 24: Performance



What command provides statistics from the Counter Manager?– stats

What directory holds .xml template files for customizing the output of the statscommand?– etc/stats/preset

True or false? The reallocate command incurs significant overhead and can cause CPU bottlenecks.– False


NETAPP UNIVERSITY

Appendix B: Master Configuration Worksheet Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode

Exercise Guide



EB-2 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Appendix B: Master Configuration Worksheet


NOTE: Use this worksheet to record important information in the class.

Hardware Protocol Item Value

Local Windows

Username:

(If present) Password:

Linux Name:

Console IP Address:

IP Address:

Root Password:

iSCSI Interface Name:

IP Address:

WWN:

Windows

Server

Name:

Console IP Address:

Local Administrator Password:

Domain Administrator Password:

iSCSI 1 Interface Name:

1 IP Address:

2 Interface Name:

2 IP Address:

WWNN:


EB-3 Accelerated NCDA Boot Camp Data ONTAP 8.0 7-Mode: Appendix B: Master Configuration Worksheet


Hardware Protocol Item Value

Storage System

Hostname:

Type of System:

Console IP:

Root password:

iSCSI 1 Interface Name:

1 IP Address:

2 Interface Name:

2 IP Address:

WWNN:


NetApp NCDA Exercise Guide

Documents

Transcript of NetApp NCDA Exercise Guide