-------------------------------------------------------------------------------- Network Appliance Support (888)4-NETAPP now.netapp.com now.netapp.com/NOW/knowledge/docs/docs.shtml -------------------------------------------------------------------------------- 1) r/ssh to console 2) priv set advanced 3) java netapp.cmds.jsh -------------------------------------------------------------------------------- sudo /usr/bin/rsh netapp-server "priv set advanced;cmd" sudo /usr/bin/rsh netapp-server "priv set admin;cmd" sudo /usr/bin/rsh netapp-server "priv set diag;cmd" sudo /usr/bin/rsh netapp-server "priv set diag;?" license vol status vol status -b vol #show size of volume qtree status software sysconfig -d = displays disk info sysconfig -r = displays raid configuration info sysconfig -v = displays overall filer information version = displays the Data ONTAP version (mini-OS version) fail a disk: disk fail shelf:drive disk fail 7.1 unset a failed drive (if you move data between drives) > priv set adv *> disk unfail 7.1 vol status -r if spare are (not zeroed) then <6.5 vol create dufus -n # (where # = some number of disks not zeroed) vol create dufus -n 5 vol status -r they will be zeroing it >6.5 disk zero spares change reconstruct impact options options raid options raid.reconstruct.perf_impact high (low, medium, high) now.netapp.com/now/download/tools/diskqual - to qualify a new disk /etc/qual_devices max 150 volumes in a filer max 254 qtrees in a volume increase max number of files df -i (show inodes used - one-to-one inode to file) maxfiles volX some_number can rename vol vol rename old new vol scan vol scrub raid.scrub.enable pretend vol create vol create volX -n # (some number of disks for vol) displays what disks it will use majordomo@mathworks.com (netapp admin mail list) subscribe toasters measure fragmentation wafl scan measure_layout VOLUME output: 1-100, 1 is smallest frag, 100 is full fragementation should stay below 10 if above 10, then wafl scan reallocate VOLUME wafl scan measure_layout VOLUME route -s netstat -r ifconfig vif status vlan status netdiag [-v] statit [-b] statit [-e] [-r] [-n] #disk stats wafl_susp wafl_check sysstat exportfs [-a|-u] [-v] df hammer #stress test filer DO NOT RUN - USE ONLY in TEST SNAPS snap list [VOLUME] snap reserve [VOLUME] snap reserve [VOLUME] # #where number is a percentage of disk (5,10,15: 20% is default) snap sched snap delete VOLUME SNAPSHOT-NAME snap delete -a VOLUME # deletes all snap for volume vol options VOLUME nosnap on #disable auto snaps (still can do manual) See the ~snapshot and .snapshot vol options [VOLUME] nosnapdir off CIFS also needs options cifs.show_snapshot on and turn on 'show hidden files' in fileexplorer->View /etc/sysconfigtab /etc/usermap.cfg /etc/exports /etc/quotas cifs.snapshots_file_folding.enable - turn on for windows CIFS temp files web filer view: http://filername/na_admin cifs shares cifs access if you cannot see the security tab in windows, then set the security mode to ntfs from unix in the share on the filer -------------------------------------------------------------------------------- boot ^C when prompt goes by to get boot menu At Selection (1-5) enter (22/7) to get extra options -------------------------------------------------------------------------------- read and create a file on the console We fixed the /export for vol0 rdfile /etc/exports wdfile /etc/exports paste in text ... ^C -------------------------------------------------------------------------------- DFM To restart dfmeventd, log in to gemtools1 and run the following commands: prompt> dfm service stop eventd [ Wait one minute ] prompt> dfm service start To verify that all services are running again, run the following command: prompt> dfm service list If the problem persists, contact the Network Appliance customer support. -------------------------------------------------------------------------------- To logon and logoff: 1. telnet to netapp-console enter terminal server password 2. Then enter normal root password, it will not prompt you with a login as only root can login this way. X. To logoff, enter control-D . ------------------------------------------------------------------------ To restore a file 1.) log into netbackup server and launch /usr/openv/netbackup/bin/xbpadm 2.) Under classes H/L NETAPP --> View class , click "Clients button" and note where the file is being backed up to. 3.) Lauch "xbp" from the server from step #2. Note that you need to put in the full path to the file to get any feedback. i.e. /net/netapp-server/vol/vol0/ shows info but /net/ does not! ------------------------------------------------------------------------ To create a new NFS directory: 1. telnet to netapp-console qtree create newname (newname = name of new NFS directory) This will place this on the vol0 volume, as we are only creating one main volume per NetApp box. 3. as root on NIS server vi /net/netapp-server/vol/vol0/etc/quotas Add entry for newname like follows: /vol/vol0/newname tree 10000M 200K This will create a 10Gb quota for the new NFS directory named newname 4. on netapp-server-con turn quota off temporarily - quota off vol0 turn quota back on - quota on vol0 (this should be complete). You can check by typing " quota " 5. as root on NIS server vi /etc/nis/auto.map Make entry for new directory such as follows: newname netapp-server:/vol/vol0/newname Then cd /var/yp; make. Should see NFS directory under /mount-point/newname 6. quota report - to check status of quotas 7. put a note in nis-server:/net/netapp-server/vol/vol0/etc/Readme.system.log as to who it belongs to, who created it, and the date. **************************** MUST DO ' ************************************* 8. update nis-server:/etc/rc3.d/patrol-nfs-volumes with volume name and mount point. **************************** MUST DO ^ ************************************* 9. nis-server:/net/netappserver/vol/vol0/etc/exports update with your entry 10. exportfs -a on netapp-server ------------------------------------------------------------------- To check the interface on our NetApp: ifconfig e0 Should see: e0: flags=43 mtu 1500 inet 10.X.X.X netmask 0xffff0000 broadcast 10.1.255.255 partner inet 10.x.X.X (not in use) ether 00:a0:98:00:78:74 (100tx-fd-up) 100tx-fd-up means 100MB Full Duplex, and the interface is up. The rest is just like unix ------------------------------------------------------------------- To check hardware and configuration: sysconfig -d = displays disk info sysconfig -r = displays raid configuration info sysconfig -v = displays overall filer information version = displays the Data ONTAP version (mini-OS version) ------------------------------------------------------------------- TO backup/restore data: Select manual Backup from class netapp under main xbpadm screen. To restore, select netbackup server then select the NFS share, which would be a directory under /net/netapp-server/vol/vol0 ------------------------------------------------------------------- Managing CIFS (Windows Networking) shares: Filer console commands: cifs shares (displays all shares and their permissions) If the NT Group has spaces, use double quotes around the group name. Creating a CIFS share: ex. We want to share out the /vol/vol0/admin/username/shared as NT-Share-Name: cifs shares -add NT-Share-Name /vol/vol0/admin/username/shared (creates the share) cifs access NT-Share-Name username Full Control (Gives the user username Full Control over the share) cifs access -delete NT-Share-Name everyone (Removes permissions for the NT object "everyone" on the share) ***** Notes: ***** File permissions are maintained on the UNIX side. NT only controls the permissions on the share itself. ------------------------------------------------------------------- To add disks to the filer: 1. 21 is max set on each filer (14 is default) for number of disks for Raid group. You can change this anywhere from 2 to 28, but NetApp recommends only 250Gb per volume. If this ever needs to be changed because of a new shelf or whatever - vol options vol0 raidsize 21 2. Add the disks to the volume via: vol add vol0 1 (1 = add 1 disk) 3. Do a " sysconfig -r " to see progress on disk add, you will see a pending status for the disk you added. ------------------------------------------------------------------- To add a new disk to a Network Appliance: cat> sysconfig -r You will see the current disks, and a section: Spare disks RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) --------- ----- ------------ ---- -------------- -------------- spare 6.19 6 2 3 FC:A 0 17560/35964296 spare 6.17 6 2 1 FC:A 0 17560/35964296 spare 6.16 6 2 0 FC:A 0 17560/35964296 spare 6.1 6 0 1 FC:A 0 1 This means that there are 4 spare disks. You always want one spare, so to add a disk, enter the command: vol add vol0 1 (adds 1 disk to array) -------------------------------------------------------------------- Rename the quota tree (qtree) as for a directory. 1. Verify the qtree and subdirectories in the qtree are not in use. Directories above the qtree can still be used. a. For CIFS, to determine which users may be using the share of the qtree you wish to rename, on the filer enter: cifs sessions To disconnect CIFS users from the share qtree, use the command: cifs terminate -v volname workstation_name To temporarily limit access to the qtree, use the command: cifs shares access b. For NFS, make sure no users are mounting or accessing the qtree. Unmount the volume and deny access to NFS clients who may try to access the qtree. On some NFS clients the 'fuser -u [Filer_volume_mount_point]' will help determine if a qtree is in use. On the filer, see the 'exportfs' man page to temporarily limit access to the qtree. 2. If qtree quotas are used: a. Update the qtree name in the filer's /etc/quotas file. b. Turn quotas off: quota off c. Perform steps 3 and 4. d. Turn quotas on again: quota on e. Renable access to the qtree. 3. Mount or map the volume which contains the qtree. Do not directly mount the qtree. For example, if the path to qtree "tree1" is /vol/vol1/tree1, mount or map the CIFS share associated with /vol/vol1, NOT /vol/vol1/tree1. 4. Rename the qtree, as if it were a directory, by using the UNIX mv command, the DOS ren or rename commands, Windows Explorer, etc. 5. Renable access to the qtree. ------------------------------------------------------- Delete a qtree/directory - NetApp filer ------------------------------------------------------- Delete the qtree the same way you would remove a directory from a client. 1. As a user with administrator/root privileges, mount/map the filer volume that contains the qtree you want to delete. Be sure the actual directory or qtree to be deleted is not directly mounted nor has a CIFS share directly associated with it. If necessary, unmount the NFS volume or remove the share before trying to delete the qtree/directory. a. To determine if the qtree is shared, for CIFS, enter: cifs shares To delete a share, enter: cifs shares -delete qtree/directory_sharename b. For NFS, do not allow NFS clients access to the qtree/directory. 2. Locate the qtree; it will appear as a normal directory at the root of the volume. 3. Verify that the qtree/directory permissions allow you to delete. 4. Delete the qtree/directory using the appropriate method for your client as follows: Example: On a UNIX host to remove a qtree/directory: For an empty qtree/directory, enter: rmdir directory For a qtree/directory that contains files and subdirectories, enter: rm -Rf directory On a Windows host to remove a qtree: For an empty qtree/directory, enter: rmdir directory For a qtree/directory that contains files and subdirectories, enter: rmdir /S directory Windows Explorer may also be used to remove a qtree/directory. Note: CIFS and NFS clients may have other utilities to delete directories, see the respective client documentation for more details. -------------------------------------------------------------------------------- There are a few steps that need to be completed on the filer even if its a NEW install. Primarily, you will need an entry in /etc/hosts on the filer like so: This is done becuase there is no SRV record of the domain itself (found that out the hard way). Essentially, the filer will try to lookup "mydomain.com" in DNS and not find it...we need to it find the IP of the DC. So this is the workaround. The second piece is to manually add the A record for the filer in DNS BEFORE you try to run cifs setup. After that, then just run "cifs setup", and choose the option to add it to a domain, give it the "top-level" domainname of the AD tree and off you go. You will need to give a user and password that has rights to add systems to the domain as well...you will be prompted. From there, choose the container (default probably) that the filer will go in. And thats it...it should fall into the domain pretty effortlessly. They biggest key to changing over to AD is to make sure that the A records are created in DNS for each filer before we re-run CIFS setup. Also that entry for the top level AD domain=the IP of the DC is in /etc/hosts on each filer...otherwise, it will all fail like a bad domino setup...and we'll be scrambling. It also might be helpful to take a look at these white papers (or pass them onto the NT folks...) http://www.netapp.com/tech_library/3124.html http://www.netapp.com/tech_library/3113.html -------------------------------------------------------------------------------- priv set -q advanced ; registry set action.autosupport.doit "Testing" -------------------------------------------------------------------------------- To setup syslog on the filers: configure syslog via the web interface, or edit /vol/vol0/etc/syslog.conf on the filer *.info /dev/console *.info /etc/messages *.err @siempoc kern.* @siempoc -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- --------------------------------------------------------------------------------