Celerra CLI Lab Guide

NAS Operations and Management Lab Guide Using the CLI 103006
Overview
NAS Operations and Management Lab Guide (Using the CLI)
Education Services October 2006
NAS Operations and Management
Student Lab Guide
Copyright:
Copyright 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC, ICDA (Integrated Cached Disk Array), and EMC2 (the EMC logo), and Symmetrix, are registered trademarks of EMC Corporation. EMC and SRDF are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.
Copyright 2006 EMC Corporation. All Rights Reserved.
Version 5.5
Page 2 of 116
Student Lab Guide
Trademark Information:
EMC2, EMC, Symmetrix, Celerra, CLARiiON, CLARalert, Connectrix, Dantz, EMC Trademarks Documentum, HighRoad, Legato, Navisphere, PowerPath, ResourcePak, SnapView/IP, SRDF, TimeFinder, VisualSAN, and where information lives are registered trademarks and EMC Automated Networked Storage, EMC ControlCenter, EMC Developers Program, EMC OnCourse, EMC Proven, EMC Snap, Access Logix, AutoAdvice, Automated Resource Manager, AutoSwap, AVALONidm, C-Clip, Celerra Replicator, Centera, CentraStar, CLARevent, CopyCross, CopyPoint, DatabaseXtender, Direct Matrix, Direct Matrix Architecture, EDM, E-Lab, Enginuity, FarPoint, FLARE, GeoSpan, InfoMover, MirrorView, NetWin, OnAlert, OpenScale, Powerlink, PowerVolume, RepliCare, SafeLine, SAN Architect, SAN Copy, SAN Manager, SDMS, SnapSure, SnapView, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX, Universal Data Tone, and VisualSRM are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners. Third Party AIX is a registered trademark of International Business Machines Trademarks Corporation. Brocade, SilkWorm, SilkWorm Express, and the Brocade logo are trademarks or registered trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Compaq and the names of Compaq products referenced herein are either trademarks and/or service marks or registered trademarks and/or service marks of Compaq. Hewlett-Packard, HP, HP-UX, OpenView, and OmniBack are trademarks, or registered trademarks of Hewlett-Packard Company. McDATA, the McDATA logo, and ES-2500 are registered trademarks of McDATA Corporation. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. NobleNet is a registered trademark of Rogue Wave Software, Inc. SANbox is a trademark of QLogic Corporation. Sun, Sun Microsystems, the Sun Logo, SunOS and all Sun-based trademarks and logos, Java, the Java Coffee Cup Logo, and all Java-based trademarks and logos, Solaris, and NFS, are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group.
Document Revision History:

Rev # C File Name NAS_Operations_and_Management Date 04-07-2006 10-25-2006
Version 5.5
Page 3 of 116
Student Lab Guide
Table of Contents: NAS Operations and Management Student Lab Guide - CLI
Copyright: ........................................................................................................................... 2 Trademark Information: ...................................................................................................... 3 Document Revision History: ............................................................................................... 3 Table of Contents: NAS Operations and Management Student Lab Guide.................... 4 CLI Lab Guide .................................................................................................................... 6 Lab 1: Celerra File Server: Basic Configuration................................................................ 7 Lab 1: Exercise 1: Plan and Configure Data Mover Failover.............................................. 8 Lab 1: Exercise 2: Configure Data Movers Network Interface Cards................................. 9 Lab 1: Exercise 3: Configure File Systems for Celerra..................................................... 11 Lab 1: Exercise 4: Configure Data Movers to Mount and Export File Systems ................ 12 Lab 1: Exercise 5: Managing File Systems ...................................................................... 14 Lab 2: Securing NFS.......................................................................................................... 17 Lab 2: Exercise 1: Exporting File Systems: Assigning root to Another Host..................... 18 Lab 2: Exercise 2: Configure Celerra File System with Read Mostly Permission........... 22 Lab 2: Exercise 3: Integrating Celerra File Server with NIS ............................................. 24 Lab 3: CIFS in a Microsoft-only Environment.................................................................. 29 Lab 3: Exercise 1: Configuring Data Mover for CIFS........................................................ 30 Lab 3 Exercise 2: Move a VDM to a Different Data Mover .............................................. 39 Lab 3: Exercise 3: Configuration Cleanup ........................................................................ 41 Lab 3: Exercise 4: Removing CIFS .................................................................................. 40 Lab 3: Exercise 5: Remove a VDM .................................................................................. 41 Lab 4: CIFS with NFS......................................................................................................... 43 Lab 4: Exercise 1: Migrate Users and Groups for use in passwd and group Files ........... 44 Lab 4: Exercise 2: Configure a CIFS Server on Celerra Data Mover in a Domain ........... 46 Lab 4: Exercise 3: Configure a Celerra File System for your Data Mover ........................ 47 Lab 4: Exercise 4: Cleanup CLI........................................................................................ 51 Lab 5: Implementing Quotas............................................................................................. 53 Lab 5 :Exercise 1: Configure Hard and Soft Quotas Using Windows 2000 GUI - CLI ...... 54 Lab 5 :Exercise 2: Configuring Unix File System Quotas on Celerra ............................... 58 Lab 5: Exercise 3: Configuring file system Tree Quotas on Celerra ................................. 61 Lab 5 :Exercise 4: Windows Cleanup............................................................................... 64 Lab 6: Celerra CIFS Features ............................................................................................ 65 Lab 6: Exercise 1: Configure a CIFS Server on your Celerra Data Mover ....................... 66 Lab 6: Exercise 2: Configuring CIFS for Home Directories .............................................. 68 Lab 6: Exercise 3: File Extension Filtering (exclude .mpg files) ....................................... 70 Lab 6: Exercise 4: File Extension Filtering (Include only .pdf files)................................... 73 Lab 6: Exercise 5: Configure and Implement a DFS Root File System - GUI ONLY ........ 75 Lab 6: Exercise 6: Removing CIFS .................................................................................. 82
Version 5.5
Page 4 of 116
Student Lab Guide
Table of Contents: NAS Operations and Management Student Lab Guide - CLI (Cont.)
Lab 7: EtherChannel, Fail Safe Network .......................................................................... 85 Lab 7: Exercise 1: Configuring EtherChannel .................................................................. 86 Lab 7: Exercise 2: Configuring an FSN ............................................................................ 88 Lab 8: iSCSI on Celerra ..................................................................................................... 91 Lab 8 : Exercise 1: Configure iSCSI Target on the Celerra .............................................. 92 Lab 8 : Exercise 2: Configure the Windows iSCSI Initiator............................................... 94 Lab 8 : Exercise 3: Removing iSCSI Configuration ........................................................ 101 Lab 9: Configuring a Nested Mountpoint File System.................................................. 103 Lab 9 : Exercise 1: Configuring a Nested Mountpoint File System................................. 104 Lab 10: SnapSure............................................................................................................. 107 Lab 10 Exercise 1: Configuring SnapSure ..................................................................... 108 Lab 11: Celerra Replicator .............................................................................................. 113 Lab 11 Exercise 1: Configuring Celerra Replicator......................................................... 114 Appendix............................................................................................................................117
Version 5.5
Page 5 of 116
Student Lab Guide
CLI Lab Guide

This Lab Guide introduces Celerra Manager v5.5. The CLI commands can be executed from one of three places: 1. Putty on your workstation 2. CLI Command in the Celerra Manager tree hierarchy CLI from the GUI supports most CLI commands. However, it does not support interactive commands, such as nas_quotas. It also does not support running vi or other text editors. 3. Tools in the tree hierarchy > SSH shell This option gives you full access to all CLI commands, including interactive commands and text editors. This is the option we recommend throughout this lab. When logging in to SSH from Celerra Manager, be sure to log in as nasadmin. You can su to root from there if required. As always, be careful when logged in as root.
Version 5.5
Page 6 of 116
Lab 1
Student Lab Guide
Lab 1: Celerra File Server: Basic Configuration

Scenario:
Hurricane Marine, LTD has just received shipment of their new EMC Celerra File Server. The Celerra has been set up and installed by EMC Customer Service. Before going into production, Ira Techi the head of Hurricane Marines IT department, would like to test the capabilities and features of the Celerra. In this lab you will set up the most basic Celerra configurations. When you have completed the lab your Celerra should be on the network with an exported file system accessible to Hurricane Marines UNIX clients. In this lab you will examine the components of your Data Mover to determine if they are compatible for Data Mover failover. Then you will configure server_2 to use server_3 as its standby Data Mover. Later in this course you will test the functionality of the setup. Depending on the back-end storage being used, the Data Movers may already be configured with a standby. For example, an NSX00/NSX initial setup configures one Data Mover as a primary and one as a standby.
Purpose:
Objectives:
Configure Data Mover failover Configure Celerra Data Movers Network Interface Cards Configure file systems for Celerra. Configure Data Movers to mount and export file systems. Managing file systems.
References:
Configuring Celerra Quick Start P/N 300-002-677 Rev A01 Version 5.5 March 2006 Celerra Network Server System Operations P/N 300-002-702 Rev A01 Version 5.5 March 2006
Version 5.5
Page 7 of 116
Student Lab Guide
Lab 1 Exercise 1: Plan and Configure Data Mover Failover

Step
1
Action
Configure Data Mover failover standby relationships: SSH to your Celerra Control Station, logging on as nasadmin View the server table for your Celerra and record the following information for each Data Mover: $ nas_server -list id type slot name _________________________________ _________________________________ _________________________________ _________________________________ _________________________________
Confirm that server_2 and server_3 have the same hardware components. $ server_sysconfig server_2 Platform Record the following information from server_2: Processor speed (MHz) _____________ Total main memory (MB) ___________ Mother board _____________________ Bus speed (MHz)__________________ $ server_sysconfig server_2 pci |more Make note of all of the PCI devices in your Data Mover. Now issue the same commands for server_3 and compare the results. Do your two Data Movers have the same hardware components? ______
Verify your configuration. $ nas_server info server_2 Does the output from this command identify server_3 as the standby server? ______ $ nas_server info server_3 Does the output of this command indicate that server_3 is a standby for server_2? ______ If server_3 is already configured then go to the next exercise, ignoring steps 5 and 6.
Use the server_standby command to configure server_2 to use server_3 as its standby Data Mover; Use the auto policy. $ server_standby server_2 c mover=server_3 policy auto After server_3 reboots, view the server table once again. $ nas_server list What has changed? __________________________________
Version 5.5
Page 8 of 116
Student Lab Guide
Lab 1 Exercise 2: Configure Data Movers Network Interface Cards

In this lab you will be configuring Celerra with basic networking settings. The tasks in this lab will likely be required for most Celerra configurations. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Preparation: Before you begin, you will want to confirm the following key information from the Lab IP Address Schema appendix: Hurricane Marines DNS domain name is: hmarine.com The DNS IP address is: 10.127.*.161 Hurricane Marines NIS domain name is: hmarine.com The NIS IP address is 10.127.*.163 The IP address of your Control Station: ______ . ______ . ______ . ______ The IP address information for server_2 & server_3. server_2: IP address: ______ . ______ . ______ . ______ Subnet mask: ______ . ______ . ______ . ______ Broadcast address: ______ . ______ . ______ . ______ Default gateway: ______ . ______ . ______ . ______
server_3: IP address: Subnet mask: Broadcast address: Default gateway: 2
______ . ______ . ______ . ______ ______ . ______ . ______ . ______ ______ . ______ . ______ . ______ ______ . ______ . ______ . ______
Configure the network interface card for server_2: SSH to your Celerras Control Station.
Configure the Fast Ethernet card in server_2 to use a transmission speed of 100Mbs, and full duplex mode. $ server_sysconfig server_2 pci x o speed=100,duplex=full where x is the device name, for example cge0 (or ana0) Repeat step 3 for the following Fast Ethernet 10/100 ports: cge1(ana1), cge2(ana2), cge3(ana3).
Version 5.5
Page 9 of 116
Student Lab Guide
Step
4
Action
Configure the IP address for the 10/100 FastEthernet NIC (port cge0) for server_2. $ server_ifconfig server_2 c D cge0 n cge0-1 p IP 3 IP params for server_2 Test the network interface by pinging the external IP address of your Control Station. $ server_ping server_2 <IP address of Control Station> This step should work. Was this successful? ______ Ping the IP address of your Windows workstations. This should fail, see next step
Configure the default gateway, DNS server address, and the NIS server address for server_2: Configure server_2 to use the default gateway recorded in step 1. $ server_route server_2 a default <IP_Addr>
Test your configuration by pinging from your Data Mover to your Windows workstation. $ server_ping server_2 <IP_Addr of Windows Workstation> Note: You may also want to ping back from the Windows workstation to your Data Mover by connecting to your Windows workstation and issuing the Ping command.
Configure server_2 to use the names and addresses of the DNS and NIS servers that you recorded in step 1. $ server_dns server_2 hmarine.com <IP_Addr> $ server_nis server_2 hmarine.com <IP_Addr>
Answer the following questions using the Celerra man pages as a resource.
How would you shut down the network interface temporarily? (See man page for server_ifconfig.) ________________________________________________ How would you delete this configuration? (See man page for server_ifconfig.) ________________________________________________ ________________________________________________
Version 5.5
Page 10 of 116
Student Lab Guide
Lab 1 Exercise 3: Configure File Systems for Celerra

In this lab you will be configuring Celerra file systems. These file systems will be used in additional exercises. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Preparation: SSH to your Celerras Control Station.
In this exercise you will be configuring file systems. First check to see if there are disks available. $ nas_disk l How many standard (STD/CLSTD) disk volumes are available (not in use)? __________________ Create a file system using AVM: Create a 1Gig file system called fs1 using AVM with the proper storage pool depending on the backend storage. $ nas_fs n fs1 -create size=1G pool=storage_pool o slice=Y Where storage_pool would be symm_std (Symmetrix) or clar_r5_performance (CLARiiON)
Confirm that your file system was created. $ nas_fs i fs1 Which disks were used to create the file system? ______________________________ Confirm that your file system is not in use. $ nas_fs l (Reference second column for in use status.)
Version 5.5
Page 11 of 116
Student Lab Guide
Lab 1 Exercise 4: Configure Data Movers to Mount and Export File Systems
The purpose of this exercise is to make your Celerra file systems available for access from the network. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Mount your file system to a mountpoint called /mp1 using the default mounting settings. $ server_mount server_ x fs1 /mp1 (Where x is the number of your Data Mover.) Export this file system for the NFS protocol, assigning anonymous users root access: Export this file system for the NFS protocol, assigning anonymous users root access, UID 0 (zero). $ server_export server_x o anon=0 /mp1 (Where x is the number of your Data Mover.) NOTE: This step is for verification purposes only. It should not be used for production file systems unless directly requested.
Confirm that you exported file system is in the export table: Confirm the status of your exported file system. $ server_export server_x (Where x is the number of your Data Mover) Perform the following logged on to a UNIX workstation.
Make an NFS mount to the exported file system on your Data Mover: Log on to the UNIX workstation as root
5 6
Confirm that you are at the root file system. # cd / Make a directory for your NFS mount. # mkdir studentx (Where x is your Celerra number.) Check the contents of your /studentx directory. # ls studentx (Where x is your Celerra number.) What is in this directory? ______________________________________ NFS mount this directory to the exported file system on your Data Mover. # mount z:/mp1 /studentx (Where z is the IP address of the FastEthernet port of your Data Mover, and x is your Celerra number.) Check the contents of your /studentx directory. # ls studentx (Where x is your Celerra number.)
8 9
10
Version 5.5
Page 12 of 116
Student Lab Guide
Step
11
Action
What is in this directory now? ______________________________________ (By default a new directory is empty. In comparison, a new file system contains a lost+found directory. Therefore, when you created your /studentx directory it should have been empty. However, after NFS mounting it to your Data Mover /studentx is now being redirected to a file system.)
12
Change directory to /studentx and create a new file. # cd /studentx # touch filex (Where x is your Celerra number.) Were you able to create a new file? ____________
13
Version 5.5
Page 13 of 116
Student Lab Guide
Lab 1 Exercise 5: Managing File Systems

In this lab, you work with existing file systems to check their status, and extend existing file systems. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Managing file systems: SSH to your Celerras Control Station. Obtain a list of all Celerra file systems $ nas_fs list
Display detailed information on fs1. Which disks are being used for the respective file system? $ nas_fs info fs1 ___________________________________________ What percentage of fs1 has been utilized? $ nas_fs size fs1 _______________________________________________ Extending a file system: Extend the file system, fs1, by the specified size of 10 GB using Symmetrix STD disk volumes or CLARiiON CLSTD disk volumes in 4+1 RAID 5. $ nas_fs -xtend fs1 size=10G pool=storage_pool Where storage_pool would be symm_std (Symmetrix) or clar_r5_performance (CLARiiON)
5 6
Check the detailed information on your file system. $ nas_fs size fs1 What is the size of your file system now? _______________________________________________ If necessary take turns with your lab partner to perform the following tasks.
Unmount the NFS mountpoint on the UNIX workstation: Log on to the UNIX workstation as root
Unmount the NFS mountpoint. # cd / # umount /studentx (Where x is your Celerra number.) Removing exports, mounts, mountpoints, file systems, and volumes: Log onto the Celerra Control Station as nasadmin
10 11
Permanently unexport your file system. $ server_export server_x u p /mp1 Permanently unmount your file system. $ server_umount server_x p /mp1
Version 5.5
Page 14 of 116
Student Lab Guide
Step
12
Action
Using the Celerra man pages if needed, delete all of the following: - file systems $ nas_fs delete fs1 - mountpoints on Data Movers $ server_mountpoint server_x delete /mp1
Answer the following question using the Celerra man pages as a resource.
How did you unexport and unmount your file systems permanently? ____________________________________________________________________ ____________________________________________________________________ ____________________________________________________________________
Version 5.5
Page 15 of 116
Student Lab Guide
Version 5.5
Page 16 of 116
Lab 2
Student Lab Guide
Lab 2: Securing NFS

Scenario:
In Lab 1 you exported a file system for NFS access. However, there was no real security to the file system. A production system, on the other hand, requires the ability to manage security of the file systems that are available to the network. In this lab you will perform some of the options for securing a file system that is exported to the NFS clients. You will demonstrate three of these methods
Purpose:
In this lab you will export a file system and assign root privileges to another UNIX host.
Objectives:
Exporting file systems: Assigning root to another host Exporting file systems: Read mostly. Integrating with NIS
References:
Configuring NFS on Celerra P/N 300-002-693 Rev A01 Version 5.5 March 2006
Version 5.5
Page 17 of 116
Student Lab Guide
Lab 2 Exercise 1: Exporting File Systems: Assigning root to Another Host

In this lab you will export a file system and assign root privileges to another UNIX host. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Preparation: Before you begin this exercise you will want to record the following information: The IP address of your UNIX workstation: 10.127. ______. ______ The IP address of another UNIX workstation (See below): 10.127. ______. ______ Use the following table to learn which other UNIX workstation to use for this exercise: If you are at: sun1 sun2 sun3 sun4 sun5 sun6 sun2 sun1 sun4 sun3 sun6 sun5 Use:
Create a 10Gig file system called fs2 using AVM with the proper storage pool depending on the backend storage. To conserve and manage disk space, we will set slice option to yes $ nas_fs -name fs2 -create size=10G pool=storage_pool o slice=y Where: storage_pool would be symm_std (Symmetrix) or clar_r5_performance (CLARiiON)
Mount your file system (fs2) to your Data Mover. note: AVM will create the mountpoint for you $ server_mount server_x fs2 /mp2 (Where x is the number of your Data Mover.)
Export the file system, assigning root permission to your UNIX workstation: Use the server_export command to assign root permission to your UNIX workstation. $ server_export server_x o root=y /mp2 (Where x is the number of your Data Mover, and y is the IP address of your UNIX workstation.)
Version 5.5
Page 18 of 116
Student Lab Guide
Step
5
Action
Exchange places with your lab partner. (Unless you have been working individually.) Make an NFS mount to the exported file system on your Data Mover from 2 locations: Log on to the UNIX workstation as root.
6 7
Confirm that you are at the root file system. # cd / Verify that the /studentx directory is still present (ls command). If it is missing make a directory for your NFS mount. # mkdir /studentx (Where x is the number of your Celerra.) NFS mount this directory to the exported file system on your Data Mover. # mount z:/mp2 /studentx (Where z is the IP address of the FastEthernet port of your Data Mover, and x is your Celerra number.) Change to the /studentx directory and create a new directory and create a new file in that directory. # cd /studentx # mkdir dirx # cd dirx # echo THIS IS A TEST >filex (Where x is the number of your Celerra.) Were you able to create a new directory and file? ____________ Telnet to another UNIX workstation as root. # telnet 10.127.*.x (Where x is the IP address of the other UNIX workstation that you recorded in step 1.) Create a directory off of the root file system of your UNIX workstation and name the directory /remotestudentx. (Where x is the number of your Celerra.) # cd / # mkdir /remotestudentx NFS mount the above directory to the file system that you exported in step 5. # mount <IP_Addr_of_data_mover>:/mp2 /remotestudentx (Where x is your Celerra.)
10
11
12
13
Can you navigate to and read the file that you created in step 10? __________________ # cd /remotestudentx/dirx # cat filex (Where x is the number of your Celerra.) # touch filex (Where x is the number of your Celerra) Do you have write permissions? _____________
14
15
Exit your telnet session to your other UNIX workstation. # exit
Version 5.5
Page 19 of 116
Student Lab Guide
Step
16
Action
Administer the permissions of the Data Movers file system from you UNIX workstation: Verify that you are logged on to your UNIX workstation as root. # who am i # hostname
17
Navigate to the NFS mounted directory # cd /studentx Assign all users full access to dirx # chmod 777 dirx (Where x is the number of your Celerra.) Telnet to the other UNIX workstation. Change user to Selma Witt #su switt Navigate (change directory) to /remotestudentx/dirx suny% cd /remotestudentx/dirx (Where x is the number of your Celerra) suny% mkdir swittx (Where x is the number of your Celerra) Can you create a subdirectory in dirx? _____________ Change user to Earl Pallis suny% su epallis password: epallis suny% cd swittx suny% mkdir epallisx (Where x is the number of your Celerra) Can you get into swittx, and create another subdirectory? ______ suny% cd .. suny% mkdir epallisx (Where x is the number of your Celerra) Can Earl Pallis create a subdirectory inside dirx? _______ Answer the following question(s). What were the effective permissions in dirx when you exported the file system? (Who had write access?) __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ What were the effective permissions after you changed mod to 777 of dirx? __________________________________________________________________ __________________________________________________________________ __________________________________________________________________
18
19 20
21
22
23
24
25
Version 5.5
Page 20 of 116
Student Lab Guide
Step
26
Action
Remove the current configuration: Exit from user epallis. suny% exit suny% Exit from user switt. suny% exit #
27
Unmount /remotedstudentx at the remote workstation. # cd / # umount /remotestudentx (Where x is the number of your Celerra.) Exit from telnet session to your other UNIX workstation. # exit Unmount /studentx at your UNIX workstation. # cd / # umount /studentx (Where x is the number of your Celerra.) Log on to your Celerras Control Station as nasadmin. Permanently unexport your file system. $ server_export server_x u p /mp2
28
29
30 31
Version 5.5
Page 21 of 116
Student Lab Guide
Lab 2 Exercise 2: Configure Celerra File System with Read Mostly Permission
The purpose of this exercise is to provide a Read-Write permission to some users, while allowing Read-only to others. (Referred to in Celerra documentation as Read mostly.) If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Provide Read-Write permission to your UNIX workstation, while giving Read-only access to everyone else: Log on to your Celerras Control Station as nasadmin.
Export your file system as Read mostly. Give your UNIX workstation read-write permission, and everyone else read-only permission. $ server_export server_x o anon=0,rw=10.127.*.z /mp2 (Where x is the number of your Data Mover, and z is the IP address of your UNIX workstation.) Test Read-Write permission from your workstation: Log on to your UNIX workstation as root
4 5
Mount the /studentx directory to the file system exported in step 2 of this exercise. (See Exercise 1, Step 9 for details) Verify that you have read-write permission by creating a directory named unixz. (Where z is the number of your UNIX workstation.) # cd /studentx # mkdir unixz (Where x is the number of your Celerra, and z is the number of your UNIX workstation.) Were you able to create the directory? ________________________
Verify that you have Read-only access from other locations: Log onto your other UNIX workstation as root. (See Exercise 1, Step 1)
7 8
Mount your /remotestudentx directory to the file system that you exported in step 2 Verify that you have read-only permission by trying to create a directory named remoteunixz. (Where z is the number of the remote UNIX workstation.) # cd /remotestudentx # mkdir remoteunixz (Where x is the number of your Celerra, and z is the number of your other UNIX workstation.) Were you able to create the directory? ________________________
Can you read the directory created in step 5? ______________ # cd unixz # ls al (Where unixz is the directory that was created in step 5.)
Version 5.5
Page 22 of 116
Student Lab Guide
Step
Action
Answer the following question. In step 2, how would you have provided read-write access to all hosts in your subnet? (man server_export) __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Clean Up.
10
Unmount your UNIX workstations from /mp2 and unexport all file systems from your Data Mover: Umount /remotestudentx. # cd / # umount /remotestudentx
11
End your telnet session to your other UNIX workstation # exit Connection closed Umount /studentx. # cd / # umount /studentx Log on to your Control Station as nasadmin. Permanently remove all exports from your Data Mover. $ server_export server_x u p a
12
13 14
Version 5.5
Page 23 of 116
Student Lab Guide
Lab 2 Exercise 3: Integrating Celerra File Server with NIS

Mr. Techi would ultimately like to administer security on the Celerra by integrating it with NIS. In this exercise you will configure your Data Mover to use NIS. You will also test this configuration by providing certain users access to his or her own directories on the Data Movers file system. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Preparation: Before you begin this exercise you will want to record the following information: The IP address of your Hurricane Marines NIS server 10.127. ______.163 The IP address of another UNIX workstation (See below): 10.127. ______ . ______ Use the following table to learn which other UNIX workstation to use for this exercise: If you are at: sun1 sun2 sun3 sun4 sun5 sun6 Use: sun2 (10.127.*.12) sun1 (10.127.*.11) sun4 (10.127.*.14) sun3 (10.127.*.13) sun6 (10.127.*.16) sun5 (10.127.*.15)
Configure your Data Mover to use NIS: Log on to your Celerras Control Station as nasadmin
Verify and/or configure your Data Mover to integrate with Hurricane Marines NIS server. Verify: $ server_nis server_x If required configure: $ server_nis server_x hmarine.com 10.127.*.163 (Where x is the number of your Data Mover.)
Export your file system, assigning root privilege to your UNIX workstation: Verify that file system fs2 is still mounted to /mp2 on server_2 $ server_mount server_2
Export your file system, assigning root privilege to your UNIX workstation. $ server_export server_x o root=10.127.*.z /mp2 (Where x is the number of your Data Mover, and z is the IP address of your UNIX workstation.)
Version 5.5
Page 24 of 116
Student Lab Guide
Step
6
Action
Mount the file system from your UNIX workstation: Log on to your UNIX workstation as root Verify that your /studentx directory is no longer mounted. # mount Mount the /studentx directory to the file system exported in step 5. # cd / # mount <IP_of_data_mover>:/mp2 /studentx (Where x is the number of your Celerra.) Test permissions for the file system: Still as root of your UNIX workstation, change to the /studentx directory, and try to create a subdirectory. Name the subdirectory root.unixz. (Where z is the number of your UNIX workstation.) # cd /studentx # mkdir root.unixz (Where x is the number of your Celerra, and z is the number of your UNIX workstation.) Were you able to create the subdirectory? _____________
10 11
Telnet to the other UNIX workstation (See Lab 2 Exercise 1 Step 1) and log on as root. Verify that your /remotestudentx directory is still present and is not mounted. # cd / # ls # mount NFS mount /remotestudentx to your Data Movers file system that you exported in step 5. # cd / # mount <IP_of_data_mover>:/mp2 /remotestudentx (Where x is the number of your Celerra.) Change directory to /remotestudentx # cd /remotestudentx Can you read the directory root.unixz? __________________ # cd root.unixz Try to create a new directory inside /remotestudentx? # cd .. # mkdir root.unixy (Where y is the number of the other UNIX workstation to which you have a telnet session.) Were you able to create the directory? _________________ Why, or why not? __________________________________________
12
13
14
15
16
Exit your telnet session. (You should now be logged on to your local UNIX workstation as root.)
Version 5.5
Page 25 of 116
Student Lab Guide
Step
17
Action
Can Etta Place create a directory inside /studentx? # su eplace sunz% cd /studentx sunz% mkdir eplace Could she create the directory? __________
18
As root, create a directory for Etta Place and assign her ownership. sunz% exit # cd /studentx # mkdir eplace # chown eplace eplace Does Etta now have write permission in /studentx/eplace? # su eplace sunz% cd /studentx/eplace sunz% mkdir eplace2 Etta should now have read-write access to her own directory
19
20
Using the commands illustrated in this exercise, telnet to the other UNIX workstation again. This time switch user to Etta Place. Verify that she has read-write access from the other workstation as well
21 Exit out of any user prompts to get back to a root prompt (Do not su to root). As root, unmount /remotestudentx. (Note: If your umount command returns a message that /remotestudentx is busy, then one of your users still as a process associated with this mountpoint.) 22 Exit your telnet session to the other UNIX workstation. 23 Try accessing your Data Movers exported file system as different users, experimenting to see what kind of permissions users have with each others directories. (See Appendix 4 for a list of users. Passwords are the same as the usernames in UNIX.) If necessary take turns with your lab partner to perform the following tasks. 24 Unmount the NFS mountpoint on the UNIX workstation: Log on to the UNIX workstation as root. Unmount the NFS mountpoint # cd / # umount /studentx (Where x is your Celerra number.) Removing exports, mounts, mountpoints, file systems, and volumes: Log onto the Celerra Control Station as nasadmin.
25
26
Version 5.5
Page 26 of 116
Student Lab Guide
Step
27
Action
Permanently unexport your file system. $ server_export server_x u p /mp2 Permanently unmount your file system. $ server_umount server_x p /mp2 Using the Celerra man pages if needed, delete all of the following: - file systems - meta volumes - stripe volumes - slice volumes - mountpoints on Data Movers
28
29
Version 5.5
Page 27 of 116
Student Lab Guide
Version 5.5
Page 28 of 116
Lab 3
Student Lab Guide
Lab 3: CIFS in a Microsoft-only Environment

Scenario:
The IS department of Hurricane Marine requires that all of Hurricane Marines Microsoft clients be able to store their data on the Celerra. Ultimately, all users in the enterprise (both UNIX and Microsoft clients) will store their data in one location. At the present time, you will test how the Celerra supports only Microsoft users.
Purpose:
In this lab, you will configure a directory in a file system on the Celerra that will be available to Hurricane Marines users. All users are accessing the file system from a Microsoft network. Usermapper will map Windows users to UNIX IDs. You will establish that your Celerra environment is ready for working with VDMs, be creating a VDM, and moving it and its CIFS server to another Data Mover. You will also create Local Groups on the CIFS server and manage permissions from the Windows network.
Objectives:
Configure a Data Mover for CIFS Configure a CIFS server on a VDM Move a VDM to a different Data Mover Access a Celerra file system from a CIFS client Administer permissions on a CIFS share from Windows
References:
Configuring CIFS on Celerra P/N 300-002-678 Rev A01 Version 5.5 March 2006 Configuring Virtual Data Movers for Celerra P/N 300-002-726 Rev A01 Version 5.5 March 2006
Version 5.5
Page 29 of 116
Student Lab Guide
Lab 3: Exercise 1: Configuring Data Mover for CIFS

Step Action
Preparation: Consult your IP Appendix to confirm 2 valid IP addresses that you can use to configure two interfaces Verify\Create interfaces on the proper devices: cge0-1 on your Data Mover 2 o This should be already configured cge0-2 on your Data Mover 2 (ask your instructor for an IP address) o This should require your configuration cge0-2 on your Data Mover 3 o This should require your configuration
Note: It is important that the new interfaces have the same name on both Data Mover 2 and Data Mover 3. 1 Before you begin, you will want to note or record the following key information: The IP address of the customers DNS server: 10.127. ____. 161 The Fully Qualified Domain Name (FQDN) of the Windows 2000 domain that will hold the Data Movers computer account. corp.hmarine.com The computer name and IP Address for your Data Mover. (See Appendix E, Hurricane Marine, IP Addresses and Schema). 2 You will require two production Data Movers in this lab with their own network interfaces. Log onto your Celerra Control Station as nasadmin and verify that server_2 and server_3 are type 1 servers (i.e. not standby Data Movers). $ nas_server list Earlier, you assigned one Data Mover a primary role, and the other Data Mover a role as secondary. This lab requires two active Data Movers. To delete the relationship between the primary and standby: $ server_standby server_2 d mover To convert server_3 to primary: $ server_setup server_3 type nas Verify the status of internal Usermapper. Ensure that it is enabled on server_2. $ server_usermapper server_2 If it is not: $ server_usermapper server_2 enable
Version 5.5
Page 30 of 116
Student Lab Guide
Step
3
Action
Create network interfaces on the device cge0 of server_2 and server_3. Use the IP addresses and names that you noted above. $ server_ifconfig server_2 c D cge0 n cge0-2 p IP <IPAdress> <SubnetMask> <BroadcastAddr>
$ server_ifconfig server_3 c D cge0 n cge0-2 p IP <IPAdress> <SubnetMask> <BroadcastAddr> Verify that your routes are configured on BOTH Data Movers. (server_route) Set the time and date of your Data Movers to agree with that of the KDC (Key Distribution Center).You will need to work with the instructor to get the correct time from the Windows 2000 server. $ server_date server_x YYMMDDHHMM Where: x is the number of your Data Mover YY is the current year MM is the current month DD is the current date HH is the current hour is 24-hour format MM is the current minute Example: To set the date and time to Oct. 1, 2006 at 2:05 PM, type: $ server_date server_2 0610011405
Set your Data Movers to synchronize with the KDC as a time server. $ server_date server_2 timesvc start ntp 10.127.*.162 $ server_date server_3 timesvc start ntp 10.127.*.162 Remove the previous DNS configuration for your Data Mover. $ server_dns server_x delete hmarine.com (Where x is the number of your Data Mover.) Confirm with the DNS administrator (your instructor) that the forward (corp.hmarine.com) zone has Allow dynamic updates set to yes.
Version 5.5
Page 31 of 116
Student Lab Guide
Step
8
Action
The following will be demonstrated to you by your instructor INSTRUCTOR: To verify that Allow dynamic updates is set to yes perform the following while logged on to the DC for hmarine.com. Click on Start > Run Type dnsmgmt.msc This should open the Windows 2000 DNS Management Console. Click the + sign to the left of the DNS server under the tree to expand the domain. You should see the forward lookup zone. Click the + sign to the left of Forward Lookup Zones display should look similar to the following:
To verify that Allow dynamic updates is set to yes: You will need to confirm the following zones: hmarine.com Forward Lookup Zone
Click on a zone (for example 10.127.50.x Subnet) to highlight it. Right-click on the same zone to select Properties.
You should see the following window. The Allow dynamic updates option is in the center of the window. It should be set to Yes.
Version 5.5
Page 32 of 116
Student Lab Guide
Step
9
Action
The following is to be performed by the students. Configure both Data Movers for DNS using the corp.hmarine.com domain. Then stop and start DNS. $ server_dns server_x corp.hmarine.com 10.127.*.161 $ server_dns server_x o stop $ server_dns server_x o start (Where x is the number of your Data Mover.) Ask the instructor to reset the Administrators password for corp.hmarine.com. Start the CIFS service on both Data Movers. $ server_setup server_x P cifs o start (Where x is the number of your Data Mover.) Create a CIFS server on Data Mover 2 for use in the Windows 2000 domain corp.hmarine.com. $ server_cifs server_x a compname=celydm2,domain=corp.hmarine.com,interface=cge0-1 (Where y is the number of your Celerra.) Configure the CIFS server to join the Windows 2000 domain. $ server_cifs server_x J compname=celydm2,domain=corp.hmarine.com,admin=administrator <enter> password: (Ask instructor about the correct password) (Where y is the number of your Celerra.)
10 11
12
13
Version 5.5
Page 33 of 116
Student Lab Guide
Step
14
Action
The following is to be performed by the students. Create a Virtual Data Mover on server_2 and name it vdm1. $ nas_server -name vdm1 type vdm -create server_2 Examine the output from the previous command. What is the name of the VDMs root file system? ___________________ What is the status of the VDM? ___________________
15
16
List the mounted file systems for server_2. $ server_mount server_2 Confirm that the root file system of the new VDM is mounted to server_2.
17
Create a CIFS server on vdm1 for use in the Windows 2000 domain corp.hmarine.com. $ server_cifs vdm1 a compname=vdmcifsy,domain=corp.hmarine.com,interface=cge0-2 (Where y is the number of your Celerra.) Configure the CIFS server to join the Windows 2000 domain. $ server_cifs vdm1 J compname=vdmcifsy,domain=corp.hmarine.com,admin=administrator <enter> password: <ask your instructor> (Where y is the number of your Celerra.) Ask your instructor to show the following results to you: The containers that were created EMC Celerra & Computers The computer accounts in that container The DNS entries in the forward lookup zone
18
19
20
Create a file system named fs3 using Automatic Volume Manager. Make the file system at least 5 GB in size. $ nas_fs n fs3 c size=5G pool=clar_r5_performance (or symm_std) This command may take a few minutes to complete. Note: If your class is using Symmetrix storage, the pool will be symm_std. If your class is using Clariion storage, the pool will be clar_r5_perfomance. If you are unsure which pool to use, ask your instructor. Run the command nas_fs size fs3 to discover the actual size of the file system that was made. The actual size of the file system is dependent upon what type of storage pool was used to create the file system and the options associated. Note: When creating a file system using the symm_std or symm_std_rdf_src storage pools, the default is not to slice the volumes. The result is a file system that uses the sum total space derived from the striping of several disk volumes together and may be larger than the requested file system size. This setting may be overridden with the o slice=y option. When the clar_r1, clar_r5_performance, clar_r5_economy, clarata_r3, and clarata_archive pools are specified, the default is to slice the volumes. This option will result in a file system which is the size that was requested. This setting may be overridden with the o slice=n option.
Version 5.5
Page 34 of 116
Student Lab Guide
Step
21
Action
The following is to be performed by the students. Mount the file system to a mountpoint on your Virtual Data Mover; name the mountpoint /win2k. $ server_mount vdm1 fs3 /win2k Export /win2k for CIFS using the share name w2kdata. $ server_export vdm1 P cifs n w2kdata /win2k Logon to your Windows 2000 workstation as administrator of corp.hmarine.com. Connect to one of your CIFS servers using the UNC (Universal Naming Convention) path Start > Run > Type \\celydm2 (Where y is the number of your Celerra.) You should be able to connect using this method, but will be unable to see your exported file system. This is because it was mounted to and exported by the VDM you created. Connect to your other CIFS server using the UNC path Start > Run > Type \\vdmcifsy (Where y is the number of your Celerra.) You should be able to connect using this method, and should be looking at the share of your exported file system. What contents are displayed in the w2kdata share? _________________________ _________________________ You should see the lost&found and .etc directories. What could you have done differently in order to hide these two directories from the CIFS share? __________________________________________________________ ____________________________________________________________ NOTE: The Data Movers CIFS servers do not display in Network Neighborhood because there are no Microsoft Windows computers in that network segment. This is expected behavior. If it is desired that the CIFS servers appear in the browse list, then at least one Microsoft Windows computer must reside in the same network segment. For more information on Network Neighborhood and the browse list see the Microsoft Knowledge Base at http://support.microsoft.com. (See articles Q117633, Q120151, etc.)
22
23
24
NOTE: What follows is an example. The creation of the CIFS Full and CIFS Read-only Local Groups and managing their associated permissions are simply to illustrate basic User/Group/Permissions management concepts. In production settings, you can create groups that suit your own needs or simply use the built-in, default groups. Using the Windows 2000 Computer Management console, create a Local Group on the Data Mover. Start > Run > type compmgmt.msc and click OK.
25
Verify that Computer Management (Local) at the top of the Tree window pane is highlighted. From the menu choose Action > Connect to another computer In the Select Computer dialog box, select the computer name of your VDMs CIFS server and click
Version 5.5
Page 35 of 116
Student Lab Guide
OK. Result: The Computer Management console should now say Computer Management (VDMCIFSy.CORP.HMARINE.COM) at the top of the Tree window pane. (Where y is the number of your Celerra.)
Version 5.5
Page 36 of 116
Student Lab Guide
Step
26
Action
The following is to be performed by the students. In the Tree window pane: a) Expand System Tools b) Expand Local Users and Groups c) Click on the Groups Create a local group for full access on the Data Mover. Add the Domain Admins, Managers and the two engineering Global Groups from Hurricane Marines CORP domain to this local group. a. With the Groups folder highlighted choose Action from the main menu and choose New Group b. In the New Group dialog box enter the Group name CIFS_Full and a description of Permissions Test. c. Click on the Add button. In the Select Users or Groups dialog box, choose corp.hmarine.com from the Look in: drop-down menu. Double-click on the following groups to add them to the group then click OK to return to the New Group dialog box. Domain Admins Propulsion Engineering Structural Engineering Managers d. In the New Group dialog box you should now see these four groups in the list. Click the Create button to complete creation of this Local Group on the Data Mover. The New Group dialog box will remain open for creation of additional groups.
27
28
Repeat the previous step (omitting part a) to create a Local Group named CIFS Read Only and add the East Sales and West Sales groups (from the CORP domain) to the CIFS Read Only group. After clicking the Create button in part d, click the Close button to close the New Group dialog box. You should now see the two groups that you created in the right window pane of the Computer Management console.
29
With the Computer Management console still connected to your CIFS server, expand the Shared Folders object in the Tree window pane. Click on the Shares folder to open the list of shares on the CIFS server. Right-click on your w2kdata share and choose Properties. In the data Properties dialog box choose the Share Permissions tab. Click on the Add button to add users and/or groups to the permissions list. In the Select Users, Computers or Groups dialog box, choose VDMCIFSy.CORP.HMARINE.COM from the Look in: drop-down menu. In the Select Users or Groups dialog box, double-click on the CIFS_Full and CIFS Read Only groups to add them to the list. Then click OK to return to the Share Permissions tab.
30 31 32 33
34
Version 5.5
Page 37 of 116
Student Lab Guide
Step
35
Action
The following is to be performed by the students. In the Share Permissions tab, select each of the groups, one at a time, and assign the following permissions. CIFS_FULL: Full: Selected (checked) Change: Selected (checked) Read: Selected (checked) CIFS Read Only: Full: Not selected (unchecked) Change: Not selected (unchecked) Read: Selected (checked) Select the Everyone group and click on the Remove button to remove this group from the list. Click on the OK button to close the Properties dialog box. You have now completed setting permissions on your CIFS servers share. NOTE: There are many methods to manage permissions. The method you have just performed is only an example and is not better or worse than other methods. Log off of the Windows 2000 workstation as Domain Administrator.
36 37
38
Log back on to the Windows 2000 workstation as Liza Minacci (username lminacci) of the Managers group. (See Windows 2000 Users and Group Memberships in the appendix for a list of usernames.) Connect to your CIFS server using the UNC path. Start > Run > \\vdmcifsy (Where y is the number of your Celerra.) A window should open displaying your w2kdata share, shown as a folder icon. Open the w2kdata folder and try to create a new text document named manager1.txt. Were you able to create the file? ______ Since Liza is in the Managers group, she should be able to create the file.
39
40
41
Repeat the 3 preceding steps logging on as Eddie Pope (username: epope) of the Propulsion Engineering group, and create a file named propulsion.txt. Were you able to create the file? ______ Eddie should also be able to create a file.
Version 5.5
Page 38 of 116
Student Lab Guide
Lab 3 Exercise 2: Move a VDM to a Different Data Mover

Step
1
Action
On your Control Station, examine the information on your VDMs root file system. $ /nas/sbin/rootnas_fs info root_fs_vdm_vdm1 What is the state for the r/w server? _______________________
Prior to moving your VDM, the destination Data Mover (server_3) must have a network interface, a default gateway, DNS configured, and the CIFS service started. Refer to Lab 3, Exercise 1 for assistance. Move vdm1 to server_3 $ nas_server v vdm1 move server_3 Validate that the appropriate records were created in DNS.
Again, examine the information on your VDMs root file system. $ /nas/sbin/rootnas_fs info root_fs_vdm_vdm1 What is the value for the r/w server? _______________________ You should see the r/w server changed from server_2 to server_3.
Verify that the CIFS service is started on server_3. To start $ server_setup server_3 P cifs o start If you get an error Failed to complete command, check the server_log. Chances are the service is already running, so getting an error when you try to turn on a service that is already running should be expected. Log on to your Windows workstation as Sage Early (username searly) of the East Sales group and verify that you can access your CIFS server on your VDM now that it has been moved. Start > Run > \\vdmcifsy\w2kdata You may have to flush the workstation DNS cache. This can be done via cmd prompt on Windows client workstation. At the cmd prompt: type: ipconfig /flushdns In addition to reload remote cache name table; type: nbtstat -R In addition, you may have to resolve the hostname to IP; type: ping a <ip address> When the folder opens, create a file in the w2kdata share, using a file name of sales.txt. Were you able to create the file? ______ Can you read any existing files? ______ Sage should not be able to create a file, but he should be able to read the existing files.
Version 5.5
Page 39 of 116
Student Lab Guide
Lab 3: Exercise 3: Removing CIFS

Step
1
Action
Using the Windows 2000 Computer Management console, delete the CIFS_full and CIFS Read only on the Local Groups. Start > Run > type compmgmt.msc and click OK From the menu choose Action > Connect to another computer In the Select Computer dialog box, select the computer name of your VDMs CIFS server and click OK In the Tree window pane: Expand System Tools Expand Local Users and Groups Click on the Groups Right-Click on CIFS_FULL and click on Delete Right-Click on CIFS Read Only and click on Delete
Logon to the Control Station as nasadmin. Unjoin both CIFS servers from the Windows domain. $ server_cifs server_x U compname=celydm2,domain=corp.hmarine.com,admin=administrator <enter> password: $ server_cifs vdm1 U compname=vdmcifsy,domain=corp.hmarine.com,admin=administrator <enter> password: (Where y is the number of your Celerra.) Stop and delete the CIFS server from the Data Movers configuration. $ server_setup server_x P cifs o stop $ server_cifs server_x d compname=celydm2 $ server_cifs vdm1 d compname=vdmcifsy (Where y is the number of your Celerra.) Remove all CIFS configurations from the Data Mover. $ server_setup server_x P cifs o delete (Where x is the number of your Data Mover.) Explanation of the above steps: In step 2, the Unjoin gracefully removes the CIFS servers computer accounts from Active Directory and from Dynamic DNS. The Data Mover, however still holds the specific configuration information for those particular CIFS servers (celydm2 and vdmcifsy). Step 3 removes the CIFS servers configuration information (for celydm2 and vdmcifsy), however global CIFS configurations remain. This is very useful if a Data Mover has multiple CIFS servers residing on it. Using delete you can remove one CIFS server while leaving the others intact. On the other hand, if you desire to remove all CIFS servers and configurations you could skip step 3 and go directly to step 4. In this step, all CIFS configurations on the Data Mover are removed at once.
Version 5.5
Page 40 of 116
Student Lab Guide
Lab 3: Exercise 4: Configuration Cleanup

Step
1
Action
Permanently unexport all file systems. $ server_export server_x u p -a $ server_export vdm1 u p n w2kdata Permanently unmount all file systems. $ server_umount server_x p a $ server_umount vdm1 p /win2k Remove the created mountpoint. $ server_mountpoint vdm1 d /win2k Delete file systems $ nas_fs d fs3 Stop the Internal Usermapper services. $ server_usermapper server_2 disable
Lab 3 Exercise 5: Remove a VDM

Step
1
Action
Delete the Virtual Data Mover. $ nas_server d vdm1 Configure server_3 back to a standby role. $ server_ifconfig server_3 d cge0-2 $ server_standby server_2 c mover=server_3 policy auto To verify: $ nas_server l Follow up question: What would you have to do to gain access to the file system share via the CIFS server you created on the physical Data Mover? ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________
Version 5.5
Page 41 of 116
Student Lab Guide
Version 5.5
Page 42 of 116
Lab 4
Student Lab Guide
Lab 4: CIFS with NFS

Scenario:
Ira Techi, the head of the IS department of Hurricane Marine, has requested that all of Hurricane Marines Microsoft clients be able to store their data on the Celerra. Ultimately, he would like having all users in the enterprise (both UNIX and Microsoft clients) store their data in one location and access that data through a single product. In the preceding lab, you configured the Celerra to support Hurricane Marines Microsoft clients only and employed Usermapper to map the CIFS user/group accounts to UNIX IDs. Now you will configure a single Celerra file system that can be used to support both his NFS and CIFS clients. This will call for using NTMigrate for mapping IDs. Mr. Techi has requested that you configure Celerra to support the following: 1. Migration and merger of Microsoft and NIS users to local passwd and group files on the Data Mover. 2. Mr. Techi would like his UNIX administrator to be the central point of administration. In other words, all access (both CIFS and NFS) to the file system will be controlled via the NFS/UNIX permissions. 3. Create a file system that is exported to both NFS and CIFS clients. 4. Hide the lost&found and /.etc directories that are at the root of the Celerra file system. 5. The initial permissions should be such that any user has full control over the objects he/she creates, and read only access to objects created by other users. Mr. Techi would like to be able to audit attempted failed access to the Celerra file system.
Purpose:
In this lab you will configure a directory in a file system on Celerra such that users will be able to access the file system from both UNIX and Microsoft clients. You will configure the Data Movers with passwd and group files generated using NTMigrate. All permissions will be administered from a single UNIX workstation. Details of your CIFS configuration are as follows: User validation: Security mode: Dialect: Access Checking Policy: File Locking: Passwd and group files on Data Movers NT (default) NT1 (default) UNIX No lock / Opportunistic locks, on (default)
Objectives:
Migrate all Microsoft and NIS users into passwd and group files using NTMigrate. Configure the Data Mover for CIFS Configure a file system for NFS export, to be administered by the UNIX admin Removing CIFS
References:
Managing Celerra for a Multiprotocol Environment P/N 300-002-676 Rev A01 Version 5.5 March 2006
Version 5.5
Page 43 of 116
Student Lab Guide
Lab 4 Exercise 1: Migrate all Microsoft Users and Groups for use in passwd and group Files using NTMigrate
Mr. Techi wants to configure file systems for concurrent access by NFS and CIFS users. Combine the migrated Microsoft users with the list of users and groups from the NIS server. Place the combined information on the Data Mover. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Lab 4 Exercise 1: Migrate all Microsoft Users and Groups for use in passwd and group Files using NTMigrate
Mr. Techi wants to configure file systems for concurrent access by NFS and CIFS users. Combine the migrated Microsoft users with the list of users and groups from the NIS server. Place the combined information on the Data Mover. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time. Note to students: The NTMigrate process can be lengthy if you are unfamiliar with your network surroundings. For the purposes of this lab, the files produced via the NTMigrate process have been created for you.
Version 5.5
Page 44 of 116
Student Lab Guide
Step
1
Action
Copy the necessary files to your Control Station: Logon to Celerra Manager as nasadmin. Select Tools > SSH Shell and login as nasadmin. Then su to root and change to the /home/nasadmin directory
Create a working directory named work, and change to that directory. # mkdir work # cd work
FTP to the instructors FTP server and get the following files: - pass.2 - group.2 # ftp 10.127.50.1 Name : nasadmin Password: (ask instructor for password) ftp> cd /ntmigfiles/ ftp> mget *.2 (Type y each time when prompted to confirm.) ftp> bye
Verify user IDs: Examine /home/nasadmin/work/pass.2 to verify that, although each user has two accounts (Windows and UNIX), they have the same UID for both accounts. # cat pass.2 |grep eplace Etta Place should have two account entries: - eplace - eplace.corp What is the UID for eplace? _________ What is the UID for eplace. corp? _________
Place the passwd and group files in the ./etc directory of the Data Mover: Using the server_file command, FTP pass.2 and group.2 to the Data Mover as passwd and group. $ pwd You should see /home/nasadmin/work $ server_file server_x p pass.2 passwd $ server_file server_x p group.2 group (Where x is the number of your Data Mover.) The user and group information is now in the /.etc directory of your Data Mover. If you would like to confirm this you can type the following command to list the Data Movers list of user accounts. # /nas/sbin/server_user server_x list
Version 5.5
Page 45 of 116
Student Lab Guide
Lab 4 Exercise 2: Configure a CIFS Server on Celerra Data Mover to be a member of corp.hmarine.com domain
If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Preparation: Before you begin, you will want to note or record the following key information: The IP address of the customers DNS server: 10.127. ______ . 161 The Fully Qualified Domain Name (FQDN) of the Windows 2000 domain that will hold the Data Movers computer account. corp.hmarine.com The computer name (compname) for your Data Mover. (See Appendix 5, Hurricane Marine, IP Addresses and Schema)_____________________________
Configure CIFS: Log on to the Control Station as nasadmin. Confirm that your Data Movers DNS configuration is still present. $ server_dns server_ x You should see corp.hmarine.com and 10.127.*.161 in the output. Start the CIFS service on your Data Mover. $ server_setup server_ x P cifs o start Add the compname to your Data Movers CIFS configuration using the information from step 1. $ server_cifs server_2 a compname=celydm2,domain=corp.hmarine.com,interface=cge0-1 (Where y is the number of your Celerra.) Join the Windows 2000 domain. $ server_cifs server_x J compname=celydm2,domain=corp.hmarine.com,admin=administrator (Where y is the number of your Celerra.) password: (ask instructor for password)
Version 5.5
Page 46 of 116
Student Lab Guide
Lab 4 Exercise 3: Configure a Celerra File System for your Data Mover
Assure that the access checking policy is set so that both CIFS and NFS client must satisfy UNIX permissions. Mr. Techi requires that permissions that he sets from UNIX have effect on both NFS and CIFS users. Each user must have full control over his or her own data, yet have read-only access to other users data by default. Additionally, Ira does not want NFS or CIFS users to have access to the lost&found nor the /.etc directories that are at the root of the Celerra file system. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time.
Step
1
Action
Export a new file system with the proper access checking policy: Log on to the Celerra Control Station as nasadmin.
Verify that there are no file systems on any Celerra disks. $ nas_disk l Create a file system named fs5 using Automatic Volume Manager. Make the file system at least 7 GB in size. $ nas_pool -l $ nas_fs n fs5 c size=7G pool=symm_std o slice=y (if using Symmetrix) $ nas_fs n fs5 c size=7G pool=clar_r5_performance (if using CLARiiON) Note: If you are unsure, ask the instructor what backend to use. Can you recall how to check the size of the file system that was created?
Create a mountpoint on your Data Mover. Name the mountpoint /mp5 $ server_mountpoint server_x c /mp5 (Where x is the number of your Data Mover.) Mount the file system fs5 to /mp5 so that both NFS and CIFS clients must satisfy UNIX security. $ server_mount server_x o accesspolicy=UNIX fs5 /mp5 (Where x is the number of your Data Mover.) Export fs5 so that root privilege is assigned to a single UNIX admin workstation. (For now, use the IP address of your UNIX workstation.) $ server_export server_ x o root=IP_Address /mp5 (Where x is the number of your Data Mover.) Create a directory on the file system for export with CIFS: Log on to your UNIX workstation as root. Verify that the /studentx directory is not mounted to anything. # mount If it is still mounted, unmount it. # umount /studentx
Version 5.5
Page 47 of 116
Student Lab Guide
Step
9
Action
Mount /studentx via NFS to the file system that you exported from the Data Mover in Exercise 1 step 6. # mount z:/mp5 /studentx (Where x is the number of your Celerra, and z is the IP address of your Data Mover.) Create a directory inside /studentx for export to all users. Name the directory data. Give all users full access to this directory. Then unmount /studentx. # cd /studentx # mkdir data # chmod 777 data # cd / # umount /studentx (Where x is your student number.) What will be the effective permissions for each user inside the data directory? _______________________________________________ In the data directory, each user will have permission to create their own objects and have full access to what they create. However, they will only have read access to objects created by other users.
10
11
Export the data directory for NFS and CIFS: Log on to the Celerra Control Station as nasadmin. Unexport /mp5, then export the /mp5/data directory for NFS and CIFS. For NFS, export access to your UNIX subnet. For CIFS, use the share name celdata $ server_export server_x u p /mp5 $ server_export server_x o access=10.127.*.0/255.255.255.224 /mp5/data $ server_export server_x P cifs n celdata /mp5/data (Where x is the number of your Data Mover.) (Where * = your subnet) Verification: Log on to you UNIX workstation as root and mount /studentx to /mp5/data. # mount Data_Mover_IP:/mp5/data /studentx Switch user to Etta Place and change to the /studentx/data directory and try to create a directory named eplace. # su eplace sunz% cd /studentx sunz% mkdir eplace (Where x is the number of your Celerra.) Was Etta able to create the directory? _________
12
13
14
15
Create a file named etta.txt inside the eplace directory. Then exit from user eplace. sunz% cd eplace sunz% echo GO TEST >etta.txt sunz% cd / sunz% exit #
Version 5.5
Page 48 of 116
Student Lab Guide
Step
16
Action
Change user to Seve Wassi (user:swassi, password: swassi), and try to read etta.txt. # su swassi sunz% cd /studentx/eplace sunz% cat etta.txt Can Seve read the file? __________
17
Enter the following command to try to create a file. sunz% echo TEST FILE >seve.txt Can Seve write inside Ettas directory? _______ Create a directory in /studentx named swassi, and create the file there. Then exit from user swassi. sunz% cd .. sunz% pwd /studentx sunz% mkdir swassi sunz% cd swassi sunz% echo TEST FILE >seve.txt sunz% cd / sunz% exit # Seve Wassi should be able to write in his own directory. Logon to your Windows workstation as Seve Wassi from the CORP domain. (username:swassi, no password) Using the UNC path, connect to your Data Mover. (Start > Run > \\celydm2) Open the celdata share. You should see the directories that you created from the UNIX workstation. Open seve.txt inside the swassi directory. Try to modify the file and save the changes. Where you able to modify the file? _________ Seve should be able to modify his own file.
18
19
20
21
22
Now try to open, modify, and save changes to etta.txt inside the eplace directory. What happened? _______________________________________ Seve should have read-only access to Ettas file.
23 24
Logoff of Windows, and logon as Eva Song (username: esong, no password Click on Start > Run > \\celydm2\celdata\ (Where y is the number of your Celerra.) Create a new folder in the data share. Name the folder esong. Log on to your UNIX workstation as root and su to Eva Song (esong).
25 26
Version 5.5
Page 49 of 116
Student Lab Guide
Step
27
Action
Can Eva work in her directory that she created from Windows while she is logged on to UNIX? sunz% cd /studentx/esong sunz% touch eva.txt sunz% cd / sunz% exit # (Where x is your student number) Eva should be able to create this file in her directory. Was she successful? _____________________________________
28 29
Log off of UNIX and log off of your Windows workstation as esong. As root, unmount /studentx. # umount /studentx This exercise has established the following objectives: Permission set from UNIX is effective on both NFS and CIFS users. Users cannot see the lost&found or the /.etc directories on the Celerra file system Each user should have full ownership of their own objects regardless of which system through which they login. By default, users have read-only access to other users data.
Version 5.5
Page 50 of 116
Student Lab Guide
Lab 4 Exercise 4: Cleanup CLI

Step
1
Action
Unmount the NFS mountpoint on the UNIX workstation: Log on to the UNIX workstation as root.
Unmount the NFS mountpoint # cd / # umount /studentx (Where x is your Celerra number.) Unjoin domain, stop CIFS , and delete computer account (See Lab 3 for specifics, if necessary) Removing exports, mounts, mountpoints, file systems, and volumes: Log onto the Celerra Control Station as nasadmin.
3 4
Using the server_file command, remove the passwd and group files from your Data Mover by placing blank files. $ cd \home\nasadmin $ touch passblank $ touch groupblank $ server_file server_x p passblank passwd $ server_file server_x p groupblank group (Where x is the number of your Data Mover.) Permanently unexport your file system. $ server_export server_x u p /mp5 Permanently unmount your file system. $ server_umount server_x p /mp5 Using the Celerra man pages if needed, delete all of the following: - file systems - meta volumes - mountpoints on Data Movers Restart the primary usermapper service on server_2. $ server_usermapper server_2 enable
Version 5.5
Page 51 of 116
Student Lab Guide
Version 5.5
Page 52 of 116
Lab 5
Student Lab Guide
Lab 5: Implementing Quotas

Scenario:
Mr. Techi would like to be able to impose quotas on the file system at the user level and directory level. The Hurricane Marine workstations are running Windows and Unix Operating Systems. He has requested that you perform the configuration on both of them, and that you confirm the functionality of the quotas.
Objectives:
Configure hard and soft quotas using the Windows 2000 GUI Configuring Unix file system quotas on Celerra Configuring file system Tree Quotas on Celerra Prepare for upcoming labs remove all CIFS configurations
References:
Using Quotas on Celerra P/N 300-002-686 Rev A01 v5.5 March 2006
Version 5.5
Page 53 of 116
Student Lab Guide
Lab 5 Exercise 1: Configure Hard and Soft Quotas Using Windows 2000 GUI - CLI
Step
1
Action
Preparation: If it is desired for a message to be received by the end user when soft quotas are exceeded, then a param entry must be set and the clients messenger service must be enabled. Use vi to add the following lines to the /nas/server/slot_x/param file of your Data Mover to support soft quota messages. (Where x is the number of your Data Mover.) param quota policy=filesize param cifs sendMessage=3
If the CIFS service has NOT been started in a previous lab, then start CIFS and setup your Data Mover for CIFS in the Windows 2000 domain corp.hmarine.com. Verify usermapper is enabled (not initialized). If it is not please consult earlier labs for instructions. # server_setup server_x -P cifs -o start # server_cifs server_x a compname=celydm2,domain=corp.hmarine.com,interface=ana0-1(or cge0-1) (Where y is the number of your Celerra.)
Configure the Data Mover to join the Windows 2000 domain (If it has not been done in a previous lab). # server_cifs server_x J compname=celydm2,domain=corp.hmarine.com,admin=administrator password: Reboot your Data Mover $ server_cpu server_x r now (Where x is the number of your Data Mover.) Create a 2 Gigabyte File System (fs6), mount it with a mountpoint of /win2k, and export it with a share name of w2kdata. $ nas_pool list (Get the AVM storage pool) $ nas_fs n fs6 c size=2G pool=My_AVM_pool o slice=y $ server_mount server_x fs6 /win2k $ server_export server_x P cifs n w2kdata /win2k (Where x is the number of your Data Mover)
Set default user quotas on your CIFS exported file system using the Windows 2000 GUI: Log on to your Windows 2000 workstation as the Administrator of corp.hmarine.com.
Version 5.5
Page 54 of 116
Student Lab Guide
Step
7
Action
Map a network drive to your w2kdata share Open a DOS prompt on your Win2K system and type the following command: net use z: \\celydm2\w2kdata (Where y is the number of your Celerra.)
Open the Properties of the Z: drive Open My Computer > Right-click w2kdata on celydm2 > Choose Properties > Select the Quotas tab.
9 10 11
Enable quotas by clicking on Enable quota management. Click on Deny disk space to users exceeding quota limit Below the caption Select the default quota limit for new users on this volume: verify that Limit disk space to is selected and set it limit to 10MB, this is the hard quota. Set the soft quota to 5MB in the window labeled Set warning level to. Choose to log both event choices. Test the soft and hard quota limits: Log off of your Windows 2000 workstation and log back in as eping. On the desktop area of eping you should see the file 4MB-file.
12 13
14 15
Right-click on 4MB-file and choose Copy Open a window for your Data Movers w2kdata share. Click on Start > Run Type \\celydm2\w2kdata (Where y is the number of your Celerra.) Create a folder named eping. Click on File > New > Folder and enter the name for the folder. Open the eping folder and, from the menu choose Edit > Paste. 4MB-file should now be copied into the eping folder. Rename the 4MB copy of the file From the menu choose Edit > Copy > Edit > Paste The file Copy of 4MB-file should appear. Log off of your Windows 2000 workstation and log back on as Administrator of CORP. Verify that Z: is still mapped to your w2kdata share. Click on Start > Run and Type net use z: If it is not mapped, map a network drive to your win2k share Click on Start > Run > \\celydm2\w2kdata (Where y is the number of your Celerra.)
16
17
18
19 20
Version 5.5
Page 55 of 116
Student Lab Guide
Step
21
Action
Open the Properties of the Z: drive Open My Computer > Right-click w2kdata on celydm2 > Choose Properties > Select the Quotas tab. Click on the Quotas Entries button to view the current quota entries. What is the status of Elvin Ping for this file system? ______________ What is the amount used for Elvin Ping? _______________________ What is the warning level for Elvin Ping? ______________________ Close all windows and log off of your Windows 2000 workstation and log back on as eping. Open a window for your Data Movers w2kdata share. Click on Start > Run Type \\celydm2\w2kdata (Where y is the number of your Celerra.) Open the eping folder. Copy 4MB-file again. Click on 4MB-file within the share, from the menu choose Edit >Copy > Edit > Paste What is the result? _______________________________________ Read all error messages. Close all windows and log off of Windows 2000 and log back on as Administrator of CORP. Open the Windows 2000 Event View MMC (Microsoft Management Console). Click on Start > Run Type eventvwr.msc Connect Event Viewer to your Data Mover. Right-click on Event View in the left windowpane and choose Connect to another computer In the Select Computer dialog box type \\celydm2 In the left windowpane, select the System log of the Data Mover. In the right windowpane, double-click on the event at the bottom of the list. What is the User listed? __________________________ What is the Description of the event? _________________________________________________________ _________________________________________________________ Click on the up-arrow to view the next event. What is the User listed? __________________________ What is the Description of the event? _________________________________________________________ _________________________________________________________ Repeat this step to view all logged events.
22
23 24
25 26
27
28
29
30
31
32
Examine the effects of quotas from the Celerra: Log on to your Celerra as nasadmin
Version 5.5
Page 56 of 116
Student Lab Guide
Step
33
Action
Display the quota configuration for your file system. $ nas_quotas c r fs fs6 Examine the output of this command to observe how it correlates with the entries that you made earlier.
34
View the report of the quota for your file system. $ nas_quotas r fs fs6 Examine the output of this command to observe how it correlates with the actions that you took earlier.
35
Edit the quota configuration to double the soft and hard quota limits for the Default USER. $ nas_quotas c e fs fs6 You are placed in a vi session. Change: Block Soft: ( 5120), Block Hard: ( To: Block Soft: ( 10240), Block Hard: ( To exit from the vi session press <esc>ZZ.
10240) 20480)
36
View the changes that you have made to the configuration. $ nas_quotas c r fs fs6 Log on to your Windows 2000 workstation as Administrator of CORP. Map a network drive z: to your win2k share \\celydm2\w2kdata (Where y is the number of your Celerra.) Open the Properties of the Z: drive Open My Computer > Right-click w2kdata oncelydm2 > Choose Properties > Select the Quotas tab. What values are now shown for: Limit disk space to? __________________ Set warning level to? ___________________
37 38
39
Version 5.5
Page 57 of 116
Student Lab Guide
Lab 5 Exercise 2: Configuring Unix File System Quotas on Celerra

Purpose of the Exercise: In this lab you will configure Quotas on the file system at the user level. Configuring quotas for 3 users.
Step
1
Action
Preparation: Log on to the Celerra Control Station as nasadmin and confirm that the Data Mover is ready for this lab. a. Verify that NIS is still configured. $ server_nis server_x b. Verify that file system fs6 is still mounted to /win2k $ server_mount server_x c. Export /win2k for NFS (you can use the anon=0 option for the purposes of this lab) $ server_export server_x o anon=0 /win2k d. Log on to your UNIX workstation as root and NFS mount your /studentx directory to /win2k From your UNIX grant full permission to everyone to the file system # cd /studentx (where x is the number of your Celerra) # chmod 777 .
Configure quota limits for Etta Place and Earl Pallis: At the Celerra, configure quota limits for Etta Place, Earl Pallis, and Sarah Emm. Ettas UID is 1014, Earls UID is 1004, Sarah Emms UID is 1005. $ nas_quotas u -e -fs fs6 1014 User id : 1014 fs fs6 blocks(soft=0,hard=0)inodes(soft=0,hard=0) ~ ~ ~ done Change the following values for blocks and inodes: block soft quotas from 0 to 512 block hard quotas from 0 to 1024 inodes soft quotas from 0 to 10 inodes hard quotas from 0 to 20 then exit vi (esc ZZ) Repeat step 2 for UIDs 1004 and 1005. Turn on quotas for fs6. $ nas_quotas u on -fs fs6 Show a quota report for the file system to verify your work. $ nas_quotas u r -fs fs6
3 4
Version 5.5
Page 58 of 116
Student Lab Guide
Step
6
Action
Test the quotas: Log on to your UNIX workstation as Etta Place. Test her quota by the following procedure. # cd / # su eplace sunz% mkdir /studentx/eplace sunz% cd /studentx/eplace sunz% (cd /kernel; tar -cvpf - .) | tar -xvf Watch the progress of the tar command, it should eventually stop when the quota has been exceeded. Then exit back to root. sunz% cd / sunz% exit #
Log on to the Celerra Control Station as nasadmin. Show the quota report, comparing the used blocks to that from step 5. Configure quotas for several users at the same time using a prototype (proto) user: Referring to step 2, Use Earl Pallis as a proto (prototype) user to configure several users with quotas. $ nas_quotas u -e -fs fs6 -proto 1004 1039 1035 1017 1006 1031 1019 1009
Show a quota report for the file system. You should see Earls quota settings replicated to all of users listed in the above command. $ nas_quotas u r -fs fs6 Set the Default quota for new users: Edit the Celerra quota configuration and set the Default limits for the following entries: Block Grace period = 4.0 hours User: Block: Soft=1024; Hard=2048 $ nas_quotas c e fs fs6 Make the necessary edits in vi, then press <esc>ZZ to save changes and exit.
10
11
Log on to your UNIX workstation as root. Create a directory in /studentx for Isabella Tei and assign ownership to itei. Then su to itei. (Note: Isabellas UID is 1017 is should not currently be visible in the quota report from the Control Station.) # cd / # su itei sunz% mkdir /studentx/itei sunz% cd /studentx/itei
Version 5.5
Page 59 of 116
Student Lab Guide
Step
12
Action
As Isabella Tei, create a 1 MB file named file.1m. Then exit back to root. sunz% mkfile 1m file.1m sunz% cd / sunz% exit #
13
Examine the quota status: From the Control Station, show a quota report for the file system. $ nas_quotas u r -fs fs6 Record the status of the following users: Bytes Used Used Soft Etta Place 1014 Earl Pallis 1004 Sarah Emm 1005 Isabella Tei 1017 Did the default quota limit you set get applied to Isabella? ______ Files Used
Hard
14
Turn off user/group quotas: Via your Celerra Control Station, turn off quotas. $ nas_quotas off -fs fs6
15
Can you still view the quota report? _________ $ nas_quotas u r -fs fs6 Remove the quotas. $ nas_quotas u clear -fs fs6 What is the current status of the quotas? $ nas_quotas u r -fs fs6
16
17
Version 5.5
Page 60 of 116
Student Lab Guide
Lab 5 Exercise 3: Configuring file system Tree Quotas on Celerra

Purpose of the exercise: In this lab you will configure Tree Quotas and examine their functionality.
Step
1
Action
Preparation: Tree Quotas require an existing file system. Your Celerra should still have file system fs6 present and it should still be NFS-mounted from your UNIX workstations /studentx directory. Log onto your UNIX workstation as root. After verifying that your /studentx directory is still mounted to /win2k on your Data Mover, create a /studentx/web directory # mkdir /studentx/web
Preparation: Set the parameter to exclude Root users in the Tree Quota File count: From Celerra Managers SSH option, use the vi to add the following line to the /nas/site/slot_param file for your Data Mover to exclude Root Users in the Tree Quota File Count. 1. param quota countRootUsageInQuotaTree=0
Note: if this line does not exist, it means the parameter is currently set to its default value (1), which counts the files and directories of both root and non-root owners in the tree quota file count. Make the necessary changes to exclude Root users in the tree Quota file count. Note: Reboot Data Mover
Version 5.5
Page 61 of 116
Student Lab Guide
Step
3
Action
Configure Tree Quotas: From a SSH Shell, configure Tree Quotas on fs6 for the path /tree1. nas_quotas t -on -fs fs6 path /tree1
Create three more Tree Quotas, all under the directory /web. Name the quota trees sales, engineering, and IS. Example: $ nas_quotas t on fs fs6 p /web/IS
List the Tree Quotas on fs6 to obtain the TreeIDs. $ nas_quotas t list fs fs6
Use the edit command along with the table below to set the specified Tree Quota values. $ nas_quotas t edit fs fs6 TreeID Tree Quota Configuration Quotas Settings Quota Tree Block Soft Hard /tree1 1024 2048 /web/sales 2048 3072 /web/engineering 2048 3072 /web/IS 2048 3072
Inodes Soft 4000 5 0 0
Hard 5000 10 0 0
Test the Tree Quotas: Using the Selma Witt user account, test the soft and hard Tree Quota limits set for the inodes in the /web/sales directory. Log on to your UNIX workstation as root. Change to the /studentx directory and list the contents. # cd /studentx # ls You should see the tree1 and web directories.
Change to the web directory and list the contents. # cd web # ls You should see the engineering, sales, and IS directories. Set following permissions (for lab purposes only). # chmod 777 sales
Version 5.5
Page 62 of 116
Student Lab Guide
Step
9
Action
As switt change to the sales directory and test the inode soft quotas by creating five files. # su switt sunz% cd sales sunz% touch file.1 file.2 file.3 file.4 file.5 From your Celerra, view the Tree Quota report for fs5. $ nas_quotas t report fs fs6 You should see that the Timeleft value has been triggered.
10
11
From you UNIX workstation test the hard quota limit of the Tree Quota by creating another five files. sunz% touch file.6 file.7 file.8 file.9 file.10 This command should fail to create the last file because the quota has been exceeded.
12
Try this: try to create objects in the sales tree as Seiko Wong (username: swong) and then as root. sunz% cd / sunz% exit # su swong sunz% cd /studentx/web/sales sunz% touch file.11 Seiko should not be able to create new objects because the hard quota on the tree has been reached. Now try again as root. sunz% cd / sunz% exit # cd /studentx/web/sales # touch file.11 # cd / Root should be able to create this file because the Tree Quotas are not enforced on users with root access.
13
Unmount your UNIX client and remove your Data Movers file system. From your UNIX workstation unmount /studentx. # cd / # umount /studentx
14 15
Log on to your Control Station as nasadmin Permanently remove all exports, mounts and file system(s). $ server_export server_x u p a $ server_umount server_x p a $ nas_fs d fs6 (Where x is the number of your Data Mover.)
Version 5.5
Page 63 of 116
Student Lab Guide
Lab 5 Exercise 4: Windows Cleanup

Purpose of Lab: To prepare for upcoming labs remove all CIFS configurations.
Step
1
Action
Stop and remove CIFS configuration and unjoin the Windows 2000 domain: Log on to your Celerra as nasadmin
Permanently unexport w2kdata $ server_export server_2 u p a Unjoin the Windows 2000 domain $ server_cifs server_x U compname=celydm2,domain=corp.hmarine.com,admin=administrator (Where y is the number of your Celerra.) Stop CIFS $ server_setup server_x P cifs o stop (Where x is the number of your Data Mover.) Delete your CIFS configuration $ server_setup server_x P cifs o delete (Where x is the number of your Data Mover.) Remove the DNS configuration on your Data Mover # server_dns server_x d corp.hmarine.com 10.127.*.161 Remove any remaining Data Mover (not Control Station) entries from the Windows 2000 DNS server, the KDC for hmarine.com. Open DNS: Click on Start > Run Type dnsmgmt.msc In the Forward Lookup Zones, locate corp. Delete any remaining entries for Data Movers only.
Instructor Cleanup
Version 5.5
Page 64 of 116
Lab 6
Student Lab Guide
Lab 6: Celerra CIFS Features

Scenario
Mr. Techi would like that all Microsoft user use home directories on the network. Mr. Techi would like to configure Celerras ability to store these home directories. Mr. Techi would like to implement file filtering. Mr. Techi would like to group his shared folders located on different servers throughout the network into a logical DFS namespace by implementing a stand-alone DFS root server.
Objectives:
Configure a CIFS server Configure CIFS for home directories File extension filtering (exclude .mpg files) File extension filtering (include only .pdf files) Configure and implement a DFS Root file system Remove CIFS
References:
Managing Celerra for a Multiprotocol Environment P/N 300-002-676 Rev A01 Version 5.5 April 2006
Version 5.5
Page 65 of 116
Student Lab Guide
Lab 6 Exercise 1: Configure a CIFS Server on your Celerra Data Mover

Step
1
Action
Preparation: Before you begin, you will want to note or record the following key information: The IP address of the customers DNS server: 10.127. ______ . 161 The Fully Qualified Domain Name (FQDN) of the Windows 2000 domain that will hold the Data Movers computer account. corp.hmarine.com The computer name (compname) for your Data Mover. (See Appendix 5, Hurricane Marine, IP Addresses and Schema)_____________________________
2 3
Log on to your Control Station as nasadmin (This step may not be required) Set the time and date of your Data Mover to agree with that of the KDC. You will need to work with the instructor to get the correct time from the Windows 2000 server. $ server_date server_x YYMMDDHHMM Where: x is the number of your Data Mover. YY is the current year MM is the current month DD is the current date HH is the current hour is 24-hour format MM is the current minute Example: To set the date and time to Oct. 1, 2003 at 2:05 PM, type: server_date server_2 0310011405 Set your Data Mover to synchronize with the KDC as a time server. (This should have already been done in an earlier lab.) $ server_date server_2 timesvc start ntp 10.127.*.162 Note: If you get an error running this command, check your server_log. The time service may already be running and if so, would result in an error.
Confirm that your Data Movers DNS configuration is still present. $ server_dns server_ x You should see corp.hmarine.com and 10.127.*.161 in the output.
Version 5.5
Page 66 of 116
Student Lab Guide
Start the CIFS service on your Data Mover. (Reminder: This command will fail if the service is already running on your Data Mover.) $ server_setup server_ x P cifs o start
Step
6
Action
Add the compname to your Data Movers CIFS configuration using the information from step 1. $ server_cifs server_2 a compname=celydm2,domain=corp.hmarine.com,interface=ana0-1(or cge0-1) (Where y is the number of your Celerra.) Join the Windows 2000 domain. $ server_cifs server_2 J compname=celydm2,domain=corp.hmarine.com,admin=administrator password: <ask instructor> (Where y is the number of your Celerra.)
Version 5.5
Page 67 of 116
Student Lab Guide
Lab 6: Exercise 2: Configuring CIFS for Home Directories

Step
1
Action
In order to enable home directories you have some restrictions to follow: The home directory feature is not available on CIFS servers configured with SHARE- or UNIX-level security If you have created a share called HOME, you cannot enable the home directory feature. If you have enabled the home directory feature, you cannot create a share called HOME.
From your Control Station login as nasadmin, create and mount a file system using AVM for user home directories. Use the following guidelines: File system size: > 10G File system name: userdata Mountpoint /userdata Note: pool_name is dependent on the type of back-end storage being used. To verify your backend use the nas_storage i a command. After verifying your back-end, you may use the nas_pool l command to get a list of the proper names to be used. $ nas_storage i -a $ nas_pool -l $ nas_fs n userdata c size=10G pool=<pool_name> -o slice=y For SYMM use: <symm_std>, CLARiiON use: <clar_r5_performance> $ server_mountpoint server_x c /userdata $ server_mount server_x userdata /userdata
Using a text editor (Vim) create a map file homedir that contain a mapping of each domain user to the home directory location on Data Mover. Note: The home directory feature is disabled by default and the homedir file does not exist. Use the user name provided for your Celerra when creating your homedir map file. Celerra 1: eplace Celerra 2: epope Celerra 3: ptesca Celerra 4: swoo Celerra 5: swest Celerra 6: switt $ vi homedir *:username:/userdata Save and exit from homedir (Esc, :wq and enter) Put the homedir file in to the Data Mover /.etc directory using the server_file command. $ server_file server_2 put homedir homedir Enable Home Directories feature on Data Mover $ server_cifs server_2 option homedir
Version 5.5
Page 68 of 116
Student Lab Guide
Step
6
Action
Export an administrative share for creating user directories $ server_export server_x P cifs n user1$ /userdata (By appending the share name with $ the share will not be visible in Windows Explorer, but it can be accessed directly from the command line by those who know its name.)
Log onto Windows as the Domain administrator and connect to the administrative share using the UNC path. Start > Run > type \\celydm2\user1$
Create a directory for the user associated with your Celerra from the list below. The name of the users directory must exactly match the users login name in the Windows domain. Celerra 1: eplace Celerra 2: epope Celerra 3: ptesca Celerra 4: swoo Celerra 5: swest Celerra 6: switt Right-click in the share folder > New > Folder Change the name to match the name associated with your Celerra > press enter Set permissions on the folder to allow the domain administrator - full control, the user change control, and remove the group Everyone.
From the Windows client as administrator add the home directory path to user profile. Open a command prompt by clicking: Start > Run > cmd, Then, type net user <User Account> /domain /homedir:\\celydm2\HOME (Pay close attention to the syntax and spaces when you enter the information. You should get a command completed successfully echoed to the screen To test the EMC Celerra for Home Directories feature, log onto the Window client as the user name provided From the Windows client as the user provided Open My computer Is the Home drive mapped for the User? __________________ Log off and log back on as any other user. (Use any other user except those listed in step 8.)
10
Version 5.5
Page 69 of 116
Student Lab Guide
Open My computer Can you see the mapped network drive created in the previous step? __________________
Can you manually map a network drive to the path created in the previous steps?________
Lab 6: Exercise 3: File Extension Filtering (exclude .mpg files)

Step
1
Action
Create a 2GB file system using AVM and name it marketing. Export the file system with the name marketing. Note: pool_name is dependent on the type of back-end storage being used. To verify your backend use the nas_storage i a command. After verifying your back-end, you may use the nas_pool l command to get a list of the proper names to be used. $ nas_storage i -a $ nas_pool -l $ nas_fs n marketing c size=2G pool=<pool_name> For SYMM use: <symm_std>, CLARiiON use: <clar_r5_performance> $ server_mount server_x marketing /marketing $ server_export server_x P cifs n marketing /marketing
Log on to your Windows workstation as administrator and connect to the root file system of the Data Mover Start > run > \\<IP address of your Data Mover>\C$ To ensure that Windows does not add additional file extensions, do the following: Tools > Folder Options > View Uncheck Hide Extensions For Known file types
Version 5.5
Page 70 of 116
Student Lab Guide
Navigate to the \.filefilter directory and use Notepad to create an empty file with the name: mpg@marketing
Version 5.5
Page 71 of 116
Student Lab Guide
Step
5 6 7
Action
Right click the mpg@marketing filter file and select Properties > Security tab > Add Find Sadie Epari in the corp.hmarine.com domain and click Add > OK On the mpg@marketing Properties screen, select Sadi Epari and check the Allow Full Control box.
Sadi Epari and Administrator are now the only users who can store .mpg files on the marketing share.
8
To test the filtering of .mpg files on the marketing share, log off of administrator and back on as Elvin Ping (eping). Create a file and give the file name an extension of .mpg. Map to the marketing share, which you created, and try to save the .mpg file to the marketing share. Were you able to save the file to the marketing share? ______________________ Why or why not? __________________________________________________
9 10
11 12
Log off of the eping account, and log back on as Sadi Epari (separi). Connect to the marketing share that you created. Start > Run > \\<IP address of your Data Mover>\marketing Attempt to save a file with a .mpg file extension to the marketing share. Were you successful? _____________________________________________ Why or why not? ________________________________________________
13
Version 5.5
Page 72 of 116
Student Lab Guide
Lab 6: Exercise 4: File Extension Filtering (Include only .pdf files)

Step
1
Action
Create a 2GB file system using AVM and name it finance. Export the file system with the name finance. $ nas_fs n finance c size=2G pool=<pool_name> Note: pool_name is dependent on back-end storage being used $ server_mount server_x finance /finance $ server_export server_2 P cifs n finance /finance
Log on to your Windows workstation as administrator and connect to the root file system of the Data Mover Start > Run > \\<IP address of your Data Mover>\C$ Navigate to the \.filefilter directory and use Notepad to create the following empty file to allow for the creation and modification of .pdf files only on the \finance share (the ACL will be modified in a subsequent step) pdf@finance Navigate to the \.filefilter directory and use Notepad to create the following empty file to prohibit all file types (except .pdf) from the \finance share allfiles@finance Navigate to the \.filefilter directory and use Notepad to create the following empty file to prohibit files with no extension from the \finance noext@finance Add ACEs to the \finance ACL to grant Everyone privileges on the share. These privileges will allow Everyone rights to .pdf files.
6 7 8
Navigate to the pdf@finance filter file Right click the file and select Properties > Security tab > Add Find Everyone in the corp.hmarine.com domain and click Add > OK
Version 5.5
Page 73 of 116
Student Lab Guide
Step
9
Action
On the pdf@finance Properties screen, select Everyone and check the allow full control box > OK
Everyone can now store .pdf files on the finance share. 10 11 To test the filtering of .pdf files on the marketing share, create a file and give it an extension of .pdf Map to the finance share and try to save the .pdf file to the finance share Were you able to save the .pdf file to the finance share? ____________ Try to save a .doc file to the finance share. Were you successful? _______________________________________
12
Version 5.5
Page 74 of 116
Student Lab Guide
Lab 6: Exercise 5: Configure and Implement a Dfs Root File System

Step
1
Action
Preparation: Create a 100MB file system and name is dfsdata. Start the CIFS service, create a CIFS Server and name it celydm2. (Where y refers to the number of your Celerra.) Note 1: Refer to lab 1 for assistance on creating a file system. Note 2: Starting the CIFS service automatically enables Dfs support. Note 3: Please refer to Lab 4 for assistance on creating a new CIFS share.
Depending on your operating system, Dfs will support either Local Shares or Global shares. Since we are currently on Windows 2000 in our lab, create a local share (one that will belong exclusively to your CIFS server) on your newly created CIFS server and name it DFS_Root_x. Where x refers to the number of your Celerra. Example: $ server_export server_2 -P cifs -n DFS_Root_x -o netbios=celydm2 /dfsdata Use the following table as a guideline:
If you do not select any specific CIFS servers, the share will be accessible from all defined CIFS servers. By making it a local share, it will be accessible only via the selected CIFS servers. 3 From your student Windows server, create a folder name it studentx. (Where x refers to the number of your Celerra.) Then share it out on the network giving everyone full access. Note: There are a couple of network shares already created and located at \\hm-dc1\studentx (unless your class is using the Celerra .52 network, in which case use \\hm-1\studentx) and \\hmdc2\studentx (Where x refers to the number of your Celerra.) You will need these later on during this lab exercise.
Version 5.5
Page 75 of 116
Student Lab Guide
Step
4
Action
From your student Windows server, start the New Root Wizard tool. Select Start > Programs >Administrative Tools > Distributed File Systems The application dialog box below should appear.
From the Distributed File System dialog box, Select Action > New Dfs Root
Version 5.5
Page 76 of 116
Student Lab Guide
Step
6
Action
Click on next > Select Create a stand-alone Dfs Root > Click next
From the Host Server dialog box; Specify the host server for the Dfs root: Browse to your data CIFS servers name (celydm2) and double click it. The fully qualified domain name should appear in the Server name box. Click next
Version 5.5
Page 77 of 116
Student Lab Guide
Step
8
Action
Select use an existing share. From the drop down box: Select the share you created for your cifs server (DFS Root x) and click next. That box will be greyed out now, and you can type a comment in the comment box.
Version 5.5
Page 78 of 116
Student Lab Guide
Step
9
Action
Click next: Notice the Host server, Share name, and Root name. -> click finish.
10
What is your result? Did this work? Why or Why not? If all is working correctly when you type in \\celydm2 (where y is the number of your Celerra) You should see the Dfs Root share named DFS_Root_x (where x is the number of your Celerra).
Version 5.5
Page 79 of 116
Student Lab Guide
Step
11
Action
Right Click on the Dfs root share -> select New Dfs Link -> In the link name box, type the name leaf > In the send user to shared folder box, type the UNC name for the leaf share, and click OK You will create three of these the links will be labeled leaf 1, leaf 2, and leaf 3 see the list below for the corresponding UNC names for each leaf share: Leaf1 - \\w2kx\studentx Leaf2 - \\hm-dc1\studentx (or on the .52 net ONLY \\hm-1\studentx) Leaf3 - \\hm-dc2\studentx
12
Now if you were to navigate over to your Data mover with your DFS Root x share, you would see the new links labeled as leaf1 thru 3.
Note: This enables an administrator to consolidate network shares into one central name space. The locations of these shares are transparent to the users and give the administrator more centralized control. Copyright 2006 EMC Corporation. All Rights Reserved. Version 5.5 Page 80 of 116
Student Lab Guide
Step
13
Action
Reason for this not to work: You have the incorrect share type (global instead of local) and/or you need to unexport the share and re-export the share (delete and re-do the share.) Clean up: Please clean up in the following order: Note: Because this is a standalone Dfs Root when you go to enable the Dfs Dialog box on your Windows server the Root Server may not show. To display it you will have to type in the host server which in this case is your CIFS Server named \\celydm2
14
Using the knowledge acquired, execute the following steps: Remove the Dfs links Remove the Dfs Root Delete the CIFS Share Delete the Dfs File System
Version 5.5
Page 81 of 116
Student Lab Guide
Lab 6: Exercise 6: Removing CIFS

Step
1
Action
Log on to the Windows workstation as Administrator and connect to the root file system of the Data Mover Start > run > \\<IP address of your Data Mover>\C$ Navigate to the ./Filefilter directory and delete the files below mpg@marketing pdf@finance allfiles@finance noext@finance
Logon to the Control Station as nasadmin. Unjoin the Data Mover from the Windows domain. $ server_cifs server_x U compname=celydm2,domain=corp.hmarine.com,admin=administrator password: Stop and delete the CIFS server from the Data Movers configuration. $ server_setup server_x P cifs o stop $ server_cifs server_x d compname=celydm2 Remove all CIFS configurations from the Data Mover. $ server_setup server_x P cifs o delete Explanation of the above steps: In step one the Unjoin gracefully removes the Data Movers computer account from Active Directory and from Dynamic DNS. The Data Mover, however still holds the specific configuration information for that particular CIFS server (celydm2). Step two removes the CIFS server configuration information (for celydm2), however global CIFS configurations remain. This is very useful if a Data Mover has multiple CIFS servers residing on it. Using delete you can remove one CIFS server while leaving the others in tact. On the other hand, if you desire to remove all CIFS servers and configurations you could skip step two and go directly to step three. In step three all CIFS configurations on the Data Mover are removed. Permanently unexport all file systems $ server_export server_x u p -a Permanently unmount all file systems $ server_umount server_x p a Remove the mountpoints. $ server_mountpoint server_x d /marketing $ server_mountpoint server_x d /finance
Version 5.5
Page 82 of 116
Student Lab Guide
Step
8
Action
Delete file systems and its underlying volumes $ nas_fs d marketing o volume $ nas_fs d finance o volume
Version 5.5
Page 83 of 116
Student Lab Guide
Version 5.5
Page 84 of 116
Lab 7
Student Lab Guide
Lab 7: EtherChannel, Fail Safe Network

Hurricane Marine is planning on extending their redundancy to their network devices in addition to storage. Although the site does not currently have a second Ethernet switch, Mr. Techi would like you to test Celerras Fail Safe Network (FSN) with his current equipment.
Scenario:
Purpose:
In this lab you will configure the Celerra Data Mover to support EtherChannel Trunking. You will also be tasked to test Fail Safe Network so that it can be deployed after Hurricane Marine installs a second Ethernet Switch with an ISL (Inter Switch Link) connection established between the two switches.
Objectives:
Configure a Data Mover for EtherChannel Trunking Configure a Data Mover for Fail Safe Network and test Data Mover failover
References:
Configuring and Managing Celerra Network High Availability P/N 300-002-706 Rev A01 Version 5.5 March 2006
Version 5.5
Page 85 of 116
Student Lab Guide
Lab 7 Exercise 1: Configuring EtherChannel

Step
1
Action
Configuration of EtherChannel Trunking involves the correct setup of the Ethernet switch as well as the Data Mover. Before setting up EtherChannel Trunking on the Data Mover, you will want to record some information: The ports on the Data Movers that will be setup as an EtherChannel are ana0 and ana1 (or cge0 and cge1) in this exercise; and ana2 and ana3 (or cge2 and cge3) in Exercise 2. To which physical ports on the Ethernet switch are the Data Movers ports connected? (See appendix E in the Appendices section of the Student guide). Primary Data Mover server_2 DM port Switch port ana0(cge0) ana1(cge1) ana2(cge2) ana3(cge3) Standby Data Mover server_3 DM port Switch port ana0(cge0) ana1(cge1) ana2(cge2) ana3(cge3)
This Ethernet switch should already be configured for EtherChannel. Confirm with your instructor that the appropriate ports are channeled together. 2 Confirm that the Data Mover ports you wish to configure as an EtherChannel trunk are not already being used. $ server_ifconfig server_x a (Where x is the number of your Data Mover.) To delete an existing interface (ex. ana0-1 (or cge0-1)): $ server_ifconfig server_x delete ana0-1(or cge0-1) (Where x is the number of your Data Mover.) 3 Confirm that all interfaces are set for 100Mb/Full Duplex: $ server_sysconfig server_x -pci Configure a virtual device on the Data Mover as an EtherChannel Trunk called trk0. Use ana0 and ana1 (or cge0 and cge1). $ server_sysconfig server_x v n trk0 c trk -o device=ana0,ana1 (or cge0,cge1) (Where x is the number of your Data Mover.) Assign an IP address to the virtual device just as you would a physical device. $ server_ifconfig server_x c D trk0 n trk0 p IP IP_Addr subnet_mask broadcast_address (Where x is the number of your Data Mover.) Use the IP address, subnet mask and broadcast address assigned to your Data Mover in Appendix E.
Version 5.5
Page 86 of 116
Student Lab Guide
Step
6
Action
Test your IP configuration by pinging the Data Movers default gateway. $ server_ping server_x 10.127.*.y (Where x is the number of your Data Mover, and y is the IP address of the Data Movers default gateway.) Create and export a 5G file system named userdata using AVM. Log on to your UNIX workstation as root. NFS mount /studentx to /userdata on your Data Mover. (Where x is the number of your Celerra.) Change to the /studentx directory, copy the directory /opt as /myopt, and run a do-while loop in the directory to test connectivity. # cd /studentx # cp R /opt ./myopt # while true > do > ls al > done (Do not close the window that is running the do-while loop.) In a separate terminal window, log on to the Celerras Control Station, and use server_netstat with a while true loop to identify and monitor which network interface is being used for the connection. $ while true > do > server_netstat server_x i > sleep 1 > done (Where x is the number of your Data Mover.) You should see only one ana (or cge) port with increasing numbers in the input bytes field. Which port is being using for the connection? ________
7 8
10
11 12
Ask your instructor to disable the switch port to which your active Data Mover port is connected. Examine the activity from step 10. You should see the activity has switched to the other Ethernet port. Verify that the do-while loop is still running from your UNIX workstation. Ask your instructor to re-enable the switch port which was disabled in step 11. (The network traffic should be redirected back to the original port). Remove the IP configurations from all EtherChannel trunks. $ server_ifconfig server_x delete interface_name (Where x is the number of your Data Mover.) (Remember, you are just deleting the IP address assigned to the virtual device, not the device itself).
13 14
15
Version 5.5
Page 87 of 116
Student Lab Guide
Lab 7 Exercise 2: Configuring an FSN Comprised of 2 EtherChannel Trunks and Test FSN Functionality
Step
1
Action
(Note: This will be a simulation of an FSN. A true FSN should comprise multiple Ethernet switches connected with an ISL trunk. However, the following configuration actually depicts how to configure the FSN on the Celerra File Server.) Repeat Exercise 1, Step 4 to configure a second EtherChannel Trunk. Name this virtual device trk1. Use ana2 and ana3 (or cge2 and cge3). Create an FSN virtual device from the two EtherChannel Trunk virtual devices. Then assign the IP address for your Data Mover to the FSN virtual device. (Note: If you did not complete Exercise 1 Step 15 the following command will fail with an invalid argument error.) $ server_sysconfig server_x v n fsn0 c fsn o device=trk0,trk1 $ server_ifconfig server_x c D fsn0 n fsn0 p IP IP_Address Subnet_Mask Broadcast_Address (Where x is the number of your Data Mover.) Examine the virtual device configuration for your Data Mover. $ server_sysconfig server_x v Which FSN device is currently active? ________
5 6
Verify that the do-while loop is still running on your UNIX workstation. Log on to your Control Station and check port activity using the server_netstat command. The ports comprising either trk0 or trk1 should not have any activity. In the steps below, ask your instructor to disable both Ethernet connections one at a time and notice which interface is carrying the network traffic. Disable the active port. Does the traffic move to the second device in the active trunk? ______ Disable the new active port. Does the traffic move to one of the devices in what was the standby trunk? ______ Disable the port that is currently active. Does the traffic move to the last remaining port? ______ Is the do-while loop still running? _________________
Log on to your Control Station and determine the status of your virtual devices. You should now see one trunk listed as active and the other is now standby. Have your instructor re-enable all of your Ethernet ports for your Data Mover.
Version 5.5
Page 88 of 116
Student Lab Guide
Step
10 11
Action
Verify that the while-true loop on your UNIX workstation is still active. From your Control Station, activate Data Mover failover. This should cause all traffic to transfer over to your standby Data Mover. $ server_standby server_x activate mover Observe the activity on your UNIX workstation as the failover test takes place.
12
Confirm the failover test. $ nas_server list You should see that server_2 is now listed as server_2.faulted.server_3. The Data Mover that was the standby should now list as server_2.
13
Repeat steps 5 9 on the new server_2 (the former standby) to test that EtherChannel and FSN still function. Restore server_2.faulted.server_3 to primary status. $ server_standby server_2 restore mover Watch the while-true loop on your UNIX workstation to monitor connectivity throughout the process.
14
15
Stop any continuing while-true loops (by pressing Ctrl-c) on the Control Station or your UNIX workstation. Unmount /studentx on your UNIX workstation. (Where x is the number of your Celerra.) Verify that there are no student directories NFS mounted to your Celerra. # mount From your Celerra Control Station, delete your fsn0 interface and remove all virtual network devices (FSN and TRK). $ server_ifconfig server_x delete fsn0 $ server_sysconfig server_2 v d fsn0 $ server_sysconfig server_2 v d trk1 $ server_sysconfig server_2 v d trk0 Remove the standby Data Mover for server_2 and restore the standby to be primary NAS Data Mover. $ server_standby server_2 delete mover $ server_setup server_3 type nas Confirm all Data Movers are NAS servers (type 1). $ nas_server list Delete all file systems. Student Notes: 1) You will have to reconfigure your primary Data Mover with a network interface prior to starting the next lab. 2) After you have completed this lab, inform your instructor so that he/she can remove the EtherChannel configuration on the Ethernet switch. Instructor Note: After all students have completed the lab, remove all EtherChannel configuration from the switch.
16 17
18
19
20
Version 5.5
Page 89 of 116
Student Lab Guide
Version 5.5
Page 90 of 116
Lab 8
Student Lab Guide
Lab 8: iSCSI on Celerra

The Human Resources Department at Hurricane Marine had originally planned to implement a Fibre Channel SAN for their department servers. The storage capacity is required for several new Human Resources applications. Now that the Celerra has been installed, they are investigating the possibility of implementing iSCSI on the Celerra since none of the Fibre Channel equipment has yet been purchased (Fibre Channel switches and HBAs for the servers). In this lab, you will configure the Celerra as an iSCSI target. The Windows iSCSI Initiator has been installed on your Windows workstations. You will configure Windows iSCSI Initiator and validate connectivity to the Celerra..
Scenario:
Purpose:
The purpose of this lab is to configure your Windows workstation to access the Celerra storage using iSCSI. You will learn to configure the Celerra iSCSI target, configure the Windows iSCSI initiator, and validate access to SCSI storage over IP.
Objectives:
Configure iSCSI Target on the Celerra Configure iSCSI Initiator on your Windows workstation Remove iSCSI configuration
References:
Configuring iSCSI Targets on Celerra P/N 300-002-694 Rev A01 Version 5.5 March 2006
Version 5.5
Page 91 of 116
Student Lab Guide
Lab 8 Exercise 1: Configure iSCSI Target on the Celerra

The Human Resources Department at Hurricane Marine would like to use iSCSI on the Celerra.
Step
1
Action
If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time. Validate network interface: Validate that a network interface is configured on your Data Mover $ server_ifconfig server_x -all
Create and mount a file system called iSCSI: Create a 10GB file system called iSCSI using AVM and mount it $ nas_fs n iscsi c size=10G pool=<pool_name> Note: The pool_name is dependent on the back-end storage being used. $ server_mount server_x iscsi /iscsi
Create the Celerra iSCSI target: Create the iSCSI target $ server_iscsi server_x target alias target create 1000:np=<IP address of your Data Mover>
List the iSCSI target just created $ server_iscsi server_x target list Create 3 iSCSI LUNs: Create three, 1GB iSCSI LUNs on target using file system iscsi $ server_iscsi server_x lun number 1 create target size 1000 fs iscsi $ server_iscsi server_x lun number 2 create target size l000 fs iscsi $ server_iscsi server_x lun number 3 create target size 1000 fs iscsi Note: Size is in MB
List the LUNs just created $ server_iscsi server_x lun list List information for all LUNs on target $ server_iscsi server_x lun info all target target
Version 5.5
Page 92 of 116
Student Lab Guide
Step
8
Action
Configure LUN mask: Configure the LUN mask for the iSCSI initiator on the target. To find the fully qualified name of the iSCSI initiator, on your Windows workstation desktop launch Windows iSCSI Initiator > General tab > it is listed as the initiator node name in the middle of the screen. (You can copy and paste the name into the CLI) $ server_iscsi server_x mask set target initiator <fully qualified name of the iSCSI initiator> -grant 1-3 Start the iSCSI service: Start the iSCSI service $ server_iscsi server_x service start The iSCSI target is now configured on the Celerra. In the next exercise, you will configure the Windows iSCSI Initiator and access the disks.
Version 5.5
Page 93 of 116
Student Lab Guide
Lab 8 Exercise 2: Configure the Windows iSCSI Initiator

The Human Resources Department at Hurricane Marine would like to use iSCSI on the Celerra. In Exercise 1, the Celerra iSCSI target and LUNs have been configured. In this exercise, youll configure the Windows iSCSI Initiator and access the Celerra iSCSI LUNs as you would d with any locally attached disk.
Step
1
Action
If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time. Launch the Windows iSCSI Initiator: Log on to your Windows workstation as administrator and launch the Microsoft iSCSI Initiator from the desktop.
Validate initiator registration: The initiators Qualified Name (IQN) must be written to the Windows Registry, otherwise, the browse dialog boxes in the Celerra iSCSI host applications may not be able to find the initiators IQN. This is done in the General tab and has already been done for you.
Version 5.5
Page 94 of 116
Student Lab Guide
Step
3
Action
Configure iSCSI discovery: Before an initiator can establish a session with a target, the initiator must first discover where targets are located and the names of the targets available to it. The initiator obtains this information through the process of iSCSI discovery. There are two methods of discovery which can be used; a. SendTargets discovery where you manually configure the initiator with a targets network portal and then the initiator uses the portal to discover all the targets accessible from that portal. This is the method that will be used in this lab. b. Automatic discovery using an iSNS server where the initiators and targets all automatically register themselves with the iSNS server. The initiator can then query the iSNS server for targets. Click the Discovery tab
At the Target Portal click Add and enter the IP address of the Celerra iSCSI target
Click OK
Version 5.5
Page 95 of 116
Student Lab Guide
Step
4
Action
Log on to the iSCSI target: After you configure the initiator with the targets network portal IP address, it will appear in the initiators Available Targets properties page. In order to access the targets LUNs, the initiator must log in to the target. On the iSCSI Initiator, select the Targets tab.
Select your target > click Log On
Check the checkbox Automatically restore this connection when the system boots Click OK
Version 5.5
Page 96 of 116
Student Lab Guide
Step
5
Action
View session information: List the information about the new iSCSI session Click the Targets tab > Details
View session detail: List the details about your session click the Devices tab.
Version 5.5
Page 97 of 116
Student Lab Guide
Step
7
Action
Configure iSCSI drives: After the initiator logs into a target, the LUNS appear as unknown in Windows Disk Manager. Before you can use the iSCSI LUNs, you must configure each LUN as an accessible disk. Begin by opening Disk Manager on your Windows workstation. Start > Programs > Administrative tools > Computer Management > Disk Management
Right click on the first Unknown disk (in this case, Disk 3) > select Write Signature
Version 5.5
Page 98 of 116
Student Lab Guide
Step
9
Action
Select all three disks and click OK. Notice that the disk description changes from Unknown to Basic.
10
Create a new partition on the new disk: Right click on the unallocated space for the first disk > select Create Partition This will launch the Create Partition Wizard. Complete the prompts choosing Primary partition. (Use the quick format option.)
11
Complete the Create Partition Wizard for all three Celerra LUNs. When the LUNs have completed formatting, close Disk Manager. In the iSCSI Initiator, select the Bound Volumes/Devices tab, and Click Bind All to have the initiator mark all volumes that have been created using iSCSI disks
12
The Windows iSCSI Initiator configuration is now complete. Next, test your configuration.
Version 5.5
Page 99 of 116
Student Lab Guide
Step
13
Action
Test your iSCSI configuration: Before you test your iSCSI configuration you must log off of the Windows workstation and then log back on. This is required if you are using Terminal Services client or ICA client (MetaFrame) to access the Windows workstation. If you do not log off and back on, the disks will not appear in My Computer. Click on Start > Shut Down > Log off Administrator and click OK Note: This is done for lab demonstration purposes only. EMC does not recommend the use of regular mode Terminal Services with the Celerra iSCSI host application. For further information, refer to Installing Celerra iSCSI Host Applications.
14 15
Log on to your Windows workstation as administrator. Open My Computer on your Windows workstation. Do you see your new Celerra iSCSI devices listed? __________________________
16
Create a file and save it to the new Celerra iSCSI device. Were you successful? __________________________________________________
Version 5.5
Page 100 of 116
Student Lab Guide
Lab 8 Exercise 3: Removing iSCSI Configuration

In preparation of the next lab, you will now remove the existing configuration.
Step
1
Action
Log off of the iSCSI target on the Windows workstation: Log on to your Windows workstation as administrator and launch the Microsoft iSCSI Initiator from the desktop. Select the Targets tab > click Details
At Details select your identifier and click Log off
Version 5.5
Page 101 of 116
Student Lab Guide
Step
2 3
Action
Select the Discovery tab > select your available portal and click Remove Select the Bound Volumes/Devices tab > select the volumes and click Remove In the Persistent Target tab, remove your target Delete all iSCSI LUNs and Celerra iSCSI target: Logon to the Control Station as nasadmin
Remove the iSCSI LUNs and the Celerra iSCSI target $ $ $ $ server_iscsi server_2 -lun -delete 1 -target target server_iscsi server_2 -lun -delete 2 -target target server_iscsi server_2 -lun -delete 3 -target target server_iscsi server_2 -target -delete target
Stop the iSCSI service and delete the iSCSI file system: Stop the iSCSI service $ server_iscsi server_2 -service -stop Delete the iSCSI file system $ server_umount server_2 p /iscsi $ nas_fs -delete iscsi
Version 5.5
Page 102 of 116
Lab 9
Student Lab Guide
Lab 9: Configuring a Nested Mountpoint File System (Optional)

In this lab you will create a Nested Mountpoint File System using the CLI. You will also use your assigned UNIX work station. At this time the Celerra GUI is unable to create a NMFS; however, some tasks can be done via the GUI, such as creating a CIFS server, and creating a file system. You are welcome to try it.
Scenario:
Purpose:
The purpose of this lab is to setup a Nested Mountpoint File System, and examine file system and disk usage as the feature is setup. If you are working with a lab partner, one person will be setting up the configuration while the other observes. You should alternate roles from time to time. The Nested Mount File system (NMFS) provides a mechanism to collect together a number of UxFS file systems (cell) [component file systems] and to present a single virtual file system. This allows the administrator to treat the system as a single entity. While the individual components are still visible, the idea is to collect together more than one individual file system and present an abstraction of a single file system.
Objectives:
Create a Nested Mountpoint File System
Version 5.5
Page 103 of 116
Student Lab Guide
Lab 9 Exercise 1: Configuring a Nested Mountpoint File System

Step
1
Action
Create an NMFS file system called nmfs_fs $ nas_fs -n nmfs_fs1 -type nmfs create Mount your nmfs file system to a mountpoint called nmfs_mnt $ server_mount server_2 nmfs_fs1 /nmfs_mnt note 1: It is not necessary to create the mountpoint manually; AVM will create it for you. note 2: the server_mount command will mount the nmfs as ro (default) Export the file system with root permissions set for your assigned UNIX station: $ server_export server_2 -o root=<your UNIX IP> /nmfs_mnt Using AVM, create four (4) component file systems of 50MB each to be nested under /nmfs_fs1. Call them nest1, nest2, nest3 and nest4. $ nas_fs -name nest1 -c size=50M pool=clar_r5_performance -o slice=y Run the nas_fs l command and notice the difference in file system types A nested mountpoint file system will have 102 for its type. Mount all four (4) component file systems under /nmfs_mnt/nestx Where x equals 1,2,3,and 4 Note: AVM will create the mountpoint /nestx $ server_mount server_2 nest1 /nmfs_mnt/nest1 $ server_mount server_2 nest2 /nmfs_mnt/nest2 Export nmfs_fs1/nest1 and nmfs_fs1/nest4 with ro permissions for your assigned SPARCstation Do not export /nmfs_fs1/nest2 and /nmfs_fs1/nest3. Instead, allow them to inherit permissions from the parent file system /nmfs_fs1. $ server_export server_2 -o ro=<Unix Workstation> /nmfs_mnt/nest1 $ server_export server_2 -o ro=<Unix workstation> /nmfs_mnt/nest4 Create a directory on your assigned UNIX work station called NMFS NFS mount this directory to the exported file system on your Data Mover. # mkdir NMFS # mount <ip to your data mover>:/nmfs_mnt /NMFS
3 4
Version 5.5
Page 104 of 116
Student Lab Guide
Step
9
Action
Navigate into /nmfs_fs1 and list its contents. What files of directories do you see?
__________ __________ __________ __________

10 Navigate into component file system nest2 and create a file called file1 # cd nest2 # touch file1 Where you able to create the file?
_____
Explain why or why not_______________________________________
__________________________________________________________
11 Navigate into component file system nest1 and create a file called file1 # cd nest1 # touch file1 Where you able to create the file?
_____
Explain why or why not _______________________________________ __________________________________________________________ 12 13 Try the same steps in the other component file systems Check the free and used disk space on your data mover server_df server_2 server_2 : File system nest4 nest3 nest2 nest1 nmfs_fs1 kbytes 50184 50184 50184 50184 200736 used 576 576 576 576 2304 avail capacity 49608 1% 49608 1% 49608 1% 49608 1% 198432 1% Mounted on /nmfs_mnt/nest4 /nmfs_mnt/nest3 /nmfs_mnt/nest2 /nmfs_mnt/nest1 /nmfs_mnt
The sum of the size of the four component (nested) file systems (nest1 nest 4) is equal to the size of the NMFS. (nmfs_fs1). 14 Permanently unexport all file systems $ server_export server_x u p -a note: this will unexport and delete the share, NMFS_win2k Permanently unmount all file systems $ server_umount server_x p a Remove the mountpoint. $ server_mountpoint server_x d /nmfs_mnt Delete file systems: nmfs_fs1, nest1, nest2, nest3, nest4 $ nas_fs d nestx
15
16
17
Version 5.5
Page 105 of 116
Student Lab Guide
Version 5.5
Page 106 of 116
Lab 10
Student Lab Guide
Lab 10: SnapSure

Purpose:
In this exercise you will configure SnapSure and observe some of its functions. You will also perform various SnapSure management functions such as recovering files and restoring file systems.
Objectives:
Configuring SnapSure
References:
Using SnapSure on Celerra P/N 300-002-720 Rev A01 v5.5 March 2006
Version 5.5
Page 107 of 116
Student Lab Guide
Lab 10 Exercise 1: Configuring SnapSure

Step
1
Action
Prerequisites: In order to complete this lab you will want to confirm that: Confirm that you are using Celerra Manager Advanced Edition Your Data Mover has IP connectivity to your UNIX workstation The speed and duplex are set appropriately on your Data Movers network device ports. Confirm that your UNIX workstation has a /CA-labs directory. If not, notify your instructor so that this directory can be copied to your workstation. (You will not be able to perform this exercise without this directory)
Record the AVM storage pool that will be used for this lab. (If you are unsure of the pool(s) on your system, you can list the pools with the command nas_pool list on the Control Station.) My AVM pool: ____________________________________
From the Control Station CLI, use AVM to create a 1GB file system named pfs12. $ nas_fs n pfs12 c size=1G pool=My_AVM_pool o slice=y
Mount pfs12 to Data Mover 2 using a mountpoint name of /mp12. $ server_mount server_2 pfs12 /mp12 Export pfs12 for NFS access. Assign root access to the IP address of your UNIX workstation. $ server_export server_2 o root=IP_address /mp12 While logged on to your UNIX workstation as root, Mount the /studentx directory to /mp12 on your Data Mover. # mount DM_IP_address:/mp12 /studentx At your UNIX workstation, copy /CA-labs/dir into /studentx. # cp R /CA-labs/dir /studentx/ (This will take several minutes) Use the fs_ckpt command to create a checkpoint file system of pfs12. Make the name of the checkpoint monday". $ fs_ckpt pfs12 -n monday -C The design SnapSure bases the initial size of the SavVol on is the following: a. If PFS > 10 GB, then SavVol = 10 GB. b. If (PFS < 10 GB) and (PFS > 64 MB), then SavVol = PFS size. c. If PFS < 64 MB, then SavVol = 64 MB (minimum SavVol size). Compare the size of the SavVol with the size of the PFS using the commands nas_fs size monday and nas_fs size pfs12 Is monday the same size as pfs12?______
Version 5.5
Page 108 of 116
Student Lab Guide
Step
10
Action
Verify that the checkpoint file system was automatically mounted to the Data Mover. $ server_mount server_2 The output of this command should include the following information pertaining to this exercise. pfs12 on /mp12 uxfs,perm,rw monday on /monday ckpt,perm,ro
11
Verify that the client can see the data in the checkpoint. From your UNIX workstation, cd to the /studentx/.ckpt directory and examine the contents. # cd /studentx/.ckpt # ls Is the checkpoint file system present and named according to the timestamp of the checkpoint? ______ Record the name of the checkpoint directory: ____________________
12
Verify that the contents of the dir directory are consistent in the PFS and the checkpoint. # ls /studentx/.ckpt/*/dir From your UNIX workstation, remove file1.90m from /studentx/dir. # rm /studentx/dir/file1.90m List the contents of the checkpoint view file system and confirm that file1.90m is still present. # ls /studentx/.ckpt/*/dir Recover file1.90m by copying it from the checkpoint to the PFS. # cp /studentx/.ckpt/*/dir/file1.90m /studentx/dir List the contents of the PFS and confirm that file1.90m has been recovered. # ls /studentx/dir From your UNIX workstation, create a file in /studentx/dir named ckpt_file with contents that say Monday data # echo Monday data>/studentx/dir/ckpt_file From your Celerra Control Station, refresh the monday" checkpoint. $ fs_ckpt monday refresh From your UNIX workstation, confirm that the monday" checkpoint shows the text you just entered. # cat /studentx/.ckpt/*/dir/ckpt_file
13
14
15
16
17
18
19
20
Modify the contents of ckpt_file. # echo Tuesday data>>/studentx/dir/ckpt_file From your Celerra Control Station, create another Checkpoint of pfs12 and name it tuesday". $ fs_ckpt pfs12 -n tuesday -C
21
Version 5.5
Page 109 of 116
Student Lab Guide
Step
22
Action
To make it easier to locate the Monday and Tuesday data, rename the CVFSs. Unmount the previously mounted checkpoints and re-mount them with the commands listed below. $ server_mount server_x o cvfsname=Monday monday /Monday $ server_mount server_x o cvfsname=Tuesday tuesday /Tuesday From your UNIX workstation, remove the ckpt_file file, then view the data from the two checkpoints. # rm /studentx/dir/ckpt_file (confirm the deletion when prompted) # cat /studentx/.ckpt/Monday/dir/ckpt_file Record your results here: ______________________ # cat /studentx/.ckpt/Tuesday/dir/ckpt_file Record your results here: ______________________ ______________________ In performing these steps you have seen SnapSures ability to preserve multiple point-in-time views of a file system.
23
24
From your UNIX workstation, delete all of the contents of the /studentx directory. # cd /studentx # rm Rf /studentx/* Confirm the deletion # ls /studentx
25
From the Celerra Control Station, as root, restore the tuesday view of pfs12. $ su Password: nasadmin # /nas/sbin/rootfs_ckpt tuesday -R From your UNIX workstation, confirm that Tuesdays view of the PFS has been restored. # cat /studentx/dir/ckpt_file Do the contents of ckpt_file show the Tuesday data? ______
26
27
From the Celerra Control Station, as root, restore the monday view of pfs12. $ su Password: nasadmin # /nas/sbin/rootfs_ckpt monday -R From your UNIX workstation, confirm that Mondays view of the PFS has been restored. # cat /studentx/dir/ckpt_file Do the contents of ckpt_file show the Monday data? ______
28
Version 5.5
Page 110 of 116
Student Lab Guide
Step
29
Action
From the Celerra Control Station, list the existing file systems. # nas_fs list In addition to pfs12, monday, and tuesday, you should see additional checkpoints created for each time a restore was performed. These additional checkpoints serve as protection against an accidental restore overwriting needed data. What are the names of these checkpoints? ____________________________ ____________________________
30
From your UNIX workstation, view these same checkpoints. # cd /studentx/.ckpt # ls Are these additional checkpoints present? ______
31
Cleanup Start by unmounting the /studentx NFS mount from the UNIX workstation. # cd / # umount /studentx From the Celerra Control Station, unexport and unmount all the file systems from your Data Mover # server_export server_x u p a # server_umount server_x p a Delete all checkpoints and then pfs12. $ nas_fs d pfs12_ckpt2 $ nas_fs d pfs12_ckpt1 $ nas_fs d tuesday $ nas_fs d monday $ nas_fs d pfs12
32
33
Version 5.5
Page 111 of 116
Student Lab Guide
Version 5.5
Page 112 of 116
Lab 11
Student Lab Guide
Lab 11: Celerra Replicator

Purpose:
The purpose of this lab is to setup and configure Celerra Replicator. Also, you will examine file system and disk usage as the feature is setup
Objectives:
Configuring Celerra Replicator
References:
Using Celerra Replicator P/N 300-002-725 Rev A01 v5.5 March 2006
Version 5.5
Page 113 of 116
Student Lab Guide
Lab 11 Exercise 1: Configuring Celerra Replicator

The purpose of this lab is to setup Celerra Replicator and examine file system and disk usage as the feature is setup.
Step
1
Action
Preparation: Before conducting this lab verify that there are no file systems or volumes on your Celerra. Run nas_fs l and nas_volume list and ensure that only root volumes are listed.
Setup the file systems for local replication: Create a primary file system and mount it to server_2 using the following parameters. Name for the primary file system: local_src Size: 5G Mountpoint: local_src note: the mountpoint will be created automatically when issuing the server_mount command. Export for NFS assigning root access to your UNIX workstations IP address $ nas_fs -name local_src -create size=5G pool=clar_r5_performance $server_mount server_2 local_src /local_src $ server_export server_2 -option root=<UNIX host IP address> /local_src
Mount your pfs file system from your UNIX workstation using the /studentx directory. # mount <Data Mover ip>:local_src /student1 Copy the /CA-labs directory into /studentx. Note: It may take several minutes to complete. # cp R /CA-labs /studentx Create a secondary file system as type rawfs and mount it to server_3 using the following parameters. (server_3 will have to be set up as primary if it is defined as a standby. You also need to set up an interface for server_3.) File system name: local_dst File system type: rawfs
$ nas_fs -name local_dst -type rawfs -create samesize=local_src pool=clar_r5_performance o slice=y
Mount the file system as read-only Mountpoint: /local_dst (Do not export at this time) $ server_mountpoint server_3 -create /local_dst $ server_mount server_3 -o ro local_dst /local_dst 6 Note the status: Run nas_volume list again. You will see the volume numbers AVM used to create your file system.
Version 5.5
Page 114 of 116
Student Lab Guide
Step
7
Action
Use nas_fs list to view the existing file systems. File systems local_src and local_dst should be the only file systems at this point. Run nas_volume list again. How many additional volumes have been created? _______________ What is the volume number of the last volume? ______ Configure the checkpoint: Create a checkpoint of the primary file system. $ fs_ckpt local_src C Run nas_volume list again. You should see three additional volumes created below the volume that you previously listed as the last volume. The checkpoint file system is automatically mounted. Once again list the volumes and file systems to monitor what is taking place. List the disk volumes using nas_disk list. How many disk volumes are in use?_____________ Copy the contents of the primary file system to the secondary file: Using the fs_copy command from the Celerra Control Station, copy the contents of the primary file system to the secondary file system via the checkpoint. $ fs_copy start local_src_ckpt1 local_dst option convert=no Note 1: remember to use the convert=no option, you will be converting the rawfs to uxfs in step 17 Note 2: you can use the nas_fs list command to get the name of the checkpoint
10
11 12
13
14
Start Replication: Start the replication service between the primary and secondary file systems.
$ fs_replicate start local_src local_dst o to=600,hwm=600

15 Create another checkpoint of the primary file system. $ fs_ckpt local_src C Set the running parameters for Celerra Replicator and finish setup: Set the running parameters for the timeout and high water mark values for both the local_dst and local_src file systems. $ fs_replicate refresh local_dst o to=500,hwm=50 $ fs_replicate refresh local_src o to=100,hwm=80 NOTE: The numbers are for lab purposes only. See your Student Guide for information on these values. Remember, if the to value is too small then the secondary file system would remain unavailable. 17 Copy incremental changes that exist between the two checkpoints to the destination file system. You are now converting the file system from rawfs to uxfs. $ fs_copy -start local_src_ckpt2 local_dst fromfs local_src_ckpt1
16
Version 5.5
Page 115 of 116
Student Lab Guide
Step
18 19
Action
Unmount and delete the local_src_ckpt1. Export the local_dst file system from server_3 assigning root access to your UNIX workstation. Create a directory on your UNIX workstation named /studentrep and NFS mount this to /local_dst on server_3. Note: for help, see steps 2 and 3 Test Celerra Replicator: From your UNIX workstation, list the contents of /studentx and /studentrep. The contents of these directories should be the same.
20
21
Change to the /studentx directory and create three new files. # cd /studentx # touch file1 file2 file3 Wait approximately a minute and list the contents of /studentrep. These 3 files should be replicated to the secondary file system. Try to delete /studentrep/file3. # rm /studentrep/file3 You should be unable to delete since /local_dst is mounted as read-only by server_3 Now remove /studentx/file3, then check to verify that it is removed from /studentrep
22
23
24 25
Clean up:
From your UNIX workstation, unmount /studentx and /studentrep # cd / # umount /studentx # umount /studentrep
26 27
Permanently unexport all file systems for server_2 and server_3 Abort replication for the local_src file system $ fs_replicate abort local_src Run nas_fs list again. What changes took place? ____________________________________________________
28
Abort replication for the local_dst file system $ fs_replicate abort local_dst Run nas_fs list again. What changes took place? ____________________________________________________
29 30
Unmount all file systems Delete all file systems and associated volumes so that all disk volumes are shown as not in use by nas_disk list.
Version 5.5
Page 116 of 116
Appendix
NAS Management Appendix

Appendix
Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F
Topic
Hurricane Marine, LTD Hurricane Marine Windows Network Design Hurricane Marine Windows User and Group Memberships Hurricane Marine UNIX Users and Groups Hurricane Marine, IP Addresses, and Schema Switch Ports, Router Configuration, IP Addressing
Page
2 4 5 6 9 10
Copyright 2006 EMC Corporation. All rights reserved. Rev 5.5
Appendix A: Hurricane Marine, LTD
Description
Hurricane Marine, LTD is a fictitious enterprise that has been created as a case study for Celerra training. Hurricane Marine, LTD is a world leader in luxury and racing boats and yachts. Their success has been enhanced by EMCs ability to make their information available to all of their staff at the same time.
EMC and Hurricane Marine, LTD
Until recently, EMC data storage has been the only EMC product Hurricane Marine, LTD has utilized. Now, however, they have opted to put an EMC Einfostructure in place. EMC has just installed EMC Connectrix ED-1032, and is now looking to implement EMC Celerra as their key file server.
Environment
Hurricane Marine, LTD computer network consists of both a Microsoft network and UNIX. While their engineering staff does the bulk of their work in a UNIX environment, all employees have Microsoft Widows based applications as well. Thus, Hurricane Marine, LTD has implemented support for both systems. You will find appendixes that outline the design of both the Microsoft and UNIX security structures. Their network runs exclusively on a TCP/IP network. Appendixes have also been provided to assist you with the design of the IP network.
People
Hurricane Marine, LTDs president and founder is Perry Tesca. The head of his IS department is Ira Techi. You will be working closely with Mr. Techi in implementing EMC Celerra into his network. Mr. Techi has some needs that Celerra is required to fulfill, but there are also some potential needs that he may like to explore.
Organization chart
On the following page is the organization chart for Hurricane Marine, LTD.
Continued on next page
Appendix A: Hurricane Marine, LTD Cont.
Hurricane Marine, LTD - Organization Chart

Perry Tesca President Liza Minacci Dir. Marketing
Users Perry Tesca Liza Minacci Edgar South Earl Pallis Sarah Emm Seve Wari Ira Techi Perry Tesca Ellen Sele Eddie Pope Sadie Epari Scott West Iggy Tallis Liza Minacci Eric Simons Etta Place Sal Eammi Seda Weir Isabella Tei Edgar South Eva Song Egan Putter Sage Early Seiko Wong Ivan Teribl Earl Pallis Ed Sazi Eldon Pratt Sam Echo Sema Welles Ira Tech Evan Swailz Elliot Proh Santos Elton Selena Willet Sarah Emm Elvin Ping Saul Ettol Selma Witt Seve Wari Sash Extra Sergio Wall Sean Ewer Seve Wassi Seymore Wai Steve Woo Engineering Propulsion Earl Pallis Eddie Pope Etta Place Egan Putter Eldon Pratt Elliot Proh Elvin Ping Engineering Structural Edgar South Ellen Sele Eric Simons Eva Song Ed Sazi Evan Swailz Sales East Sarah Emm Sadie Epari Sal Eammi Sage Early Sam Echo Santos Elton Saul Ettol Sash Extra Sean Ewer Sales West Seve Wari Scott West Seda Weir Seiko Wong Sema Welles Selena Willet Selma Witt Sergio Wall Seve Wassi Seymore Wai Steve Woo Information Systems Ira Techi Iggy Tallis Isabella Tei Ivan Teribl Managers Perry Tesca Liza Minacci Earl Pallis Edgar South Sarah Emm Seve Wari Ira Tech
Appendix B: Hurricane Marine Microsoft Network Design
Microsoft networking features
DNS Server: 10.127.*.161 DHCP: Not in use, all nodes have static IP addresses (See the IP Appendix).
Windows 2000 domains
The Windows 2000 network in comprised of the following two domains: hmarine.com domain (the root of the forest) corp.hmarine.com (a subdomain of the root) asia.corp.hmarine.com (future expansion)
Though the root domain is present solely for administrative purposes at this time, corp.hmarine.com will hold containers for all users, groups, and computer accounts. A third domain, asia.corp.hmarine.com, is also being planned for future expansion.
Root Domain: hmarine.com Domain Controller: hm-1.hmarine.com
Sub Domain: corp.hmarine.com Domain Controller: hm-dc2.hmarine.com
Computer Accounts: w2k1, w2k2, w2k3, w2k4, w2k5, w2k6 All Data Movers All user accounts
Appendix C: Hurricane Windows 2000 User and Group Memberships

Hurricane Marine Windows 2000 Users & Group Memberships CORP Domain
Username Administrator EPallis EPing EPlace EPope EPratt EProh EPutter ESazi ESele ESimons ESong ESouth ESwailz ITallis ITechi ITei ITeribl LMinacci PTesca SEammi SEarly SEcho SElton SEmm SEpari SEttol SEwer SExtra SWai SWall SWari SWassi SWeir SWelles SWest SWillet SWitt SWong SWoo Earl Pallis Elvin Ping Etta Place Eddie Pope Eldon Pratt Elliot Proh Egan Putter Ed Sazi Ellen Sele Eric Simons Eva Song Edgar South Evan Swailz Iggy Tallis Ira Techi Isabella Tei Ivan Teribl Liza Minacci Perry Tesca Sal Eammi Sage Early Sam Echo Santos Elton Sarah Emm Sadie Epari Saul Ettol Sean Ewer Sash Extra Seymore Wai Sergio Wall Seve Wari Seve Wassi Seda Weir Sema Welles Scott West Selena Willet Selma Witt Seiko Wong Steve Woo Full Name NT Global Group Domain Admins Propulsion Engineers, Managers Propulsion Engineers Propulsion Engineers Propulsion Engineers Propulsion Engineers Propulsion Engineers Propulsion Engineers Structural Engineers Structural Engineers Structural Engineers Structural Engineers Structural Engineers, Managers Structural Engineers IS, DOMAIN ADMINS IS, DOMAIN ADMINS, Managers IS, DOMAIN ADMINS IS, DOMAIN ADMINS Director of Marketing, Managers President, Managers Eastcoast Sales Eastcoast Sales Eastcoast Sales Eastcoast Sales Eastcoast Sales, Managers Eastcoast Sales Eastcoast Sales Eastcoast Sales Eastcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales, Managers Westcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales Westcoast Sales
Appendix D: Hurricane Marine UNIX Users and Groups

Hurricane Marine UNIX Users & Group Memberships NIS Domain hmarine.com
Username & Password epallis eping eplace epope epratt eproh eputter esazi esele esimons esong esouth eswailz itallis itechi itei iteribi lminacci ptesca seammi searly secho selton semm separi settol sewer sextra swai swall swari epallis sweir swelles swest swillet switt swong swoo Full Name Earl Pallis Elvin Ping Etta Place Eddie Pope Eldon Pratt Elliot Proh Egan Putter Ed Sazi Ellen Sele Eric Simons Eva Song Edgar South Evan Swailz Iggy Tallis Ira Techi Isabella Tei Ivan Teribi Liza Minacci Perry Tesca Sal Eammi Sage Early Sam Echo Santos Elton Sarah Emm Sadie Epari Saul Ettol Sean Ewer Sash Extra Seymore Wai Sergio Wall Seve Wari Seve Wassi Seda Weir Sema Welles Scott West Selena Willet Selma Witt Seiko Wong Steve Woo Group
engprop, mngr engprop engprop engprop engprop engprop engprop engstruc engstruc engstruc engstruc engstruc, mngr engstruc infotech infotech, mngr infotech infotech mngr mngr saleseas saleseas saleseas saleseas saleseas, mngr saleseas saleseas saleseas saleseas saleswes saleswes saleswes, mngr saleswes saleswes saleswes saleswes saleswes saleswes saleswes saleswes
Note: Password is the same as username

Appendix D: Hurricane Marine UNIX Users and Groups Cont.
NIS Passwd file
swillet:NP:1030:104:Selena Willet:/home/swillet:/bin/csh epallis:NP:1004:101:Earl Pallis:/home/epallis:/bin/csh swassi:NP:1037:104:Seve Wassi:/home/swassi:/bin/csh separi:NP:1010:103:Sadi Epari:/home/separi:/bin/csh esouth:NP:1003:102:Edgar South:/home/esouth:/bin/csh daemon:NP:1:1::/: swong:NP:1021:104:Seiko Wong:/home/swong:/bin/csh sewer:NP:1036:103:Sean Ewer:/home/sewer:/bin/csh secho:NP:1025:103:Sam Echo:/home/secho:/bin/csh eping:NP:1031:101:Elvin Ping:/home/eping:/bin/csh swai:NP:1038:104:Seymour Wai:/home/swai:/bin/csh itei::1017:105:Isabella Tei:/home/itei:/bin/csh adm:NP:4:4:Admin:/var/adm: iteribl:NP:1022:105:Ivan Teribl:/home/iteribl:/bin/csh ptesca:NP:1001:106:Perry Tesca:/home/ptesca:/bin/csh nobody:NP:60001:60001:Nobody:/: epratt:NP:1024:101:Eldon Pratt:/home/epratt:/bin/csh eplace:NP:1014:101:Etta Place:/home/eplace:/bin/csh swest:NP:1011:104:Scott West:/home/swest:/bin/csh sweir:NP:1016:104:Seda Weir:/home/sweir:/bin/csh nuucp:NP:9:9:uucp Admin:/var/spool/uucppublic:/usr/lib/uucp/uucico esong:NP:1018:102:Eva Song:/home/esong:/bin/csh eproh:NP:1028:101:Elliot Proh:/home/eproh:/bin/csh root:oiOEvBA22p40s:0:1:Super-User:/:/sbin/sh lminacci:NP:1002:106:Liza Minacci:/home/lminacci:/bin/csh nobody4:NP:65534:65534:SunOS 4.x Nobody:/: itallis:NP:1012:105:Iggy Tallis:/home/itallis:/bin/csh sextra:NP:1034:103:Sash Extra:/home/sextra:/bin/csh settol:NP:1032:103:Saul Ettol:/home/settol:/bin/csh selton:NP:1029:103:Santos Elton:/home/selton:/bin/csh searly:NP:1020:103:Sage Early:/home/searly:/bin/csh listen:*LK*:37:4:Network Admin:/usr/net/nls: itechi:NP:1007:105:Ira Techi:/home/itechi:/bin/csh switt:NP:1033:104:Selma Witt:/home/switt:/bin/csh swari:NP:1006:104:Seve Wari:/home/swari:/bin/csh swall:NP:1035:104:Sergio Wall:/home/swall:/bin/csh uucp:NP:5:5:uucp Admin:/usr/lib/uucp: swoo:NP:1039:104:Steve Woo:/home/swoo:/bin/csh semm:NP:1005:103:Sarah Emm:/home/semm:/bin/csh noaccess:NP:60002:60002:No Access User:/: swelles:NP:1026:104:Sema Welles:/home/swelles:/bin/csh eswailz:NP:1027:102:Evan Swailz:/home/swailz:/bin/csh esimons:NP:1013:102:Eric Simons:/home/esimons:/bin/csh eputter:NP:1019:101:Egan Putter:/home/eputter:/bin/csh seammi:NP:1015:103:Sal Eammi:/home/seammi:/bin/csh esele:NP:1008:102:Ellen Sele:/home/esele:/bin/csh esazi:NP:1023:102:Ed Sazi:/home/esazi:/bin/csh epope:NP:1009:101:Eddie Pope:/home/epope:/bin/csh sys:NP:3:3::/: bin:NP:2:2::/usr/bin: lp:NP:71:8:Line Printer Admin:/usr/spool/lp
Appendix D: Hurricane Marine UNIX Users and Groups Cont.
NIS Group file
sysadmin::14: saleswes::104:swari,swest,swong,swelles,swillet,switt,swall,swassi,sw ai,swoo saleseas::103:semm,separi,seammi,searly,secho,selton,settol,sextra,se wer noaccess::60002: infotech::105:itechi,itallis,itei,iteribl, engstruc::102:esouth,esele,esimons,esong,esazi,eswailz nogroup::65534: engprop::101:epallis,epope,eplace,eputter,epratt,eproh,eping nobody::60001: daemon::12:root,daemon staff::10:other::1: nuucp::9:root,nuucp uucp::5:root,uucp root::0:root mngr::106:lminacci,epallis,esouth,semm,swari,itechi,ptesca mail::6:root tty::7:root,tty,adm sys::3:root,bin,sys,adm bin::2:root,bin,daemon adm::4:root,adm,daemon lp::8:root,lp,
Appendix E: Hurricane Marine IP Address and Schema
Host IP Configurations
Host/comp. name sun1 sun2 sun3 sun4 sun5 sun6 W2k1 W2k2 W2k3 W2k4 W2k5 W2k6 cel1cs0 cel1dm2 cel1dm3 cel2cs0 cel2dm2 cel2dm3 cel3cs0 cel3dm2 cel3dm3 cel4cs0 cel4dm2 cel4dm3 cel5cs0 cel5dm2 Cel5dm3 Cel6cs0 Cel6dm2 Cel6dm3 Hm-1 Hm-dc2 Nis-master DNS server Router E. Switch IP address
10.127.*.11 10.127.*.12 10.127.*.13 10.127.*.14 10.127.*.15 10.127.*.16 10.127.*.71 10.127.*.72 10.127.*.73 10.127.*.74 10.127.*.75 10.127.*.76 10.127.*.110 10.127.*.112 10.127.*.113 10.127.*.120 10.127.*.122 10.127.*.123 10.127.*.130 10.127.*.132 10.127.*.133 10.127.*.140 10.127.*.142 10.127.*.143 10.127.*.150 10.127.*.152 10.127.*.153 10.127.*.100 10.127.*.102 10.127.*.103 10.127.*.161 10.127.*.162 10.127.*.163 10.127.*.161 10.127.*.254 10.127.*.253
Subnet mask
255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.224 255.255.255.0 255.255.255.0
Broadcast
10.127.*.31 10.127.*.31 10.127.*.31 10.127.*.31 10.127.*.31 10.127.*.31 10.127.*.95 10.127.*.95 10.127.*.95 10.127.*.95 10.127.*.95 10.127.*.95 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.159 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.191 10.127.*.191 10.127.*.191
Gateway
10.127.*.30 10.127.*.30 10.127.*.30 10.127.*.30 10.127.*.30 10.127.*.30 10.127.*.94 10.127.*.94 10.127.*.94 10.127.*.94 10.127.*.94 10.127.*.94 10.127.*.126 10.127.*.126 10.127.*.126 10.127.*.126 10.127.*.126 10.127.*.126 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.158 10.127.*.126 10.127.*.126 10.127.*.126 10.127.*.190 10.127.*.190 10.127.*.190
Network
10.127.*.0 10.127.*.0 10.127.*.0 10.127.*.0 10.127.*.0 10.127.*.0 10.127.*.64 10.127.*.64 10.127.*.64 10.127.*.64 10.127.*.64 10.127.*.64 10.127.*.96 10.127.*.96 10.127.*.96 10.127.*.96 10.127.*.96 10.127.*.96 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.127 10.127.*.96 10.127.*.96 10.127.*.96 10.127.*.160 10.127.*.160 10.127.*.160
Sw port : VLAN
2/43:10 2/44:10 2/45:10 2/46:10 2/47:10 2/48:10 2/37:30 2/38:30 2/39:30 2/40:30 2/41:30 2/42:30 3/25:41 2/1-4:41 2/5-8:41 3/27:41 2/9-12:41 2/13-16:41 3/29:42 2/17-20:42 2/21-24:42 3/26:42 3/1-4:42 3/5-8:42 3/28:42 3/9-12:42 3/13-16:42 3/30:41 3/17-20:41 3/21-24:41 2/27:43 2/28:43 2/29:43 3/32:Trunk
Info
UNIX UNIX UNIX UNIX UNIX UNIX Win2000 Win2000 Win2000 Win2000 Win2000 Win2000 Celerra 1 Celerra 1 Celerra 1 Celerra 2 Celerra 2 Celerra 2 Celerra 3 Celerra 3 Celerra 3 Celerra 4 Celerra 4 Celerra 4 Celerra 5 Celerra 5 Celerra 5 Celerra 6 Celerra 6 Celerra 6 Root W2k Corp W2K NIS On hm-1
Appendix F: Switch Ports, Router Configuration, IP Addressing

Cisco Systems 2980g Port layout
VLAN 42 11 cel2dm3 W2K 26 V 42 25 c1cs0 c2cs0 c3cs0 c4cs0 c5cs0 c6cs0 26 VLAN 42 V 41 VLAN IP Address Interface VLAN IP Address 28 30 32 T 27 29 31 28 30 32 34 36 38 40 14 VLAN 41 11 cel5dm3 14 16 18 20 22 24 cel6dm2 cel6dm3 13 15 17 19 21 23 16 18 20 22 24 cel3dm2 cel3dm3 W2K W2kW 42 44 NIS 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 VLAN 43 VLAN 20 VLAN 30 43 VLAN 10 45 Sun 46 48 47
Module 2 9 cel2dm2 10 12
VLAN 41
cel1dm2
cel1dm3
Module 3 9 cel5dm2 10 12
VLAN 42
cel4dm2
cel4dm3
Router Configuration
Interface VLAN IP Address Interface
Interface
VLAN
IP Address
0/1 0/0 IP Addressing Subnet B - VLAN 20 Subnet C - VLAN 30

Network Gateway Broadcast 10.127.*.32 10.127.*.62 10.127.*.63
n/a 1
assigned 10.127.*.254
0/0.10 0/0.20
10 20
10.127.*.30 10.127.*.62
0/0.30 0/0.41
30 41
10.127.*.94 10.127.*.126
0/0.42 0/0.43
42 43
10.127.*.158 10.127.*.190
Subnet A - VLAN 10
Subnet D - VLAN 41
Subnet E - VLAN 42
Subnet F - VLAN 43
Network Gateway Broadcast sun1 sun2 sun3 sun4 sun5 sun6 Not in use
10.127.*.0 10.127.*.30 10.127.*.31 10.127.*.11 10.127.*.12 10.127.*.13 10.127.*.14 10.127.*.15 10.127.*.16
Network Gateway Broadcast w2k1 w2k2 w2k3 w2k4 w2k5 w2k6
10.127.*.64 10.127.*.94 10.127.*.95 10.127.*.71 10.127.*.72 10.127.*.73 10.127.*.74 10.127.*.75 10.127.*.76
Network Gateway Broadcast cel6cs0 cel6dm2 cel1cs0 cel1dm2 cel2cs0 cel2dm2 NIS: 10.127.*.163
10.127.*.96 10.127.126 10.127.*.127 10.127.*.100 10.127.*.102 10.127.*.110 10.127.*.112 10.127.*.120 10.127.*.122
Network Gateway Broadcast cel3cs0 cel3dm2 cel4cs0 cel4dm2 cel5cs0 cel5dm2
10.127.*.127 10.127.*.158 10.127.*.159 10.127.*.130 10.127.*.132 10.127.*.140 10.127.*.142 10.127.*.150 10.127.*.152
Network Gateway Broadcast hm-1 hm-dc2 nis-master
10.127.*.160 10.127.*.190 10.127.*.191 10.127.*.161 10.127.*.162 10.127.*.163
DNS: 10.127.*.161
10
* NSNASM-LGCLI-103006 *
Printed in Canada

Celerra CLI Lab Guide

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Celerra CLI Lab Guide

Enviado por

Direitos autorais:

Formatos disponíveis

NAS Operations and Management Lab Guide Using the CLI 103006

NAS Operations and Management Lab Guide (Using the CLI)

Education Services October 2006

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Document Revision History:

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

CLI Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 1: Celerra File Server: Basic Configuration

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 1 Exercise 1: Plan and Configure Data Mover Failover

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 1 Exercise 2: Configure Data Movers Network Interface Cards

server_3: IP address: Subnet mask: Broadcast address: Default gateway: 2

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 1 Exercise 3: Configure File Systems for Celerra

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 1 Exercise 5: Managing File Systems

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 2: Securing NFS

Copyright 2006 EMC Corporation. All Rights Reserved.

NAS Operations and Management

Student Lab Guide

Lab 2 Exercise 1: Exporting File Systems: Assigning root to Another Host