Products That Work . Com

3) Change password.

4) Clean configuration and initialize all disks.

5) Maintenance mode boot.

6) Update flash from backup config.

7) Install new software first.

Reboot node.

Selection (1-8)?

• Normal Boot – continue with the normal boot operation
• Boot without /etc/rc – boot with only default options and disable some services
• Change Password – change the storage systems password
• Clean configuration and initialize all disks – cleans all disks and reset the filer to factory default settings
• Maintenance mode boot – file system operations are disabled, limited set of commands
• Update flash from backup config – restore the configuration information if corrupted on the boot device
• Install new software first – use this if the filer does not include support for the storage array
• Reboot node – restart the filer

• boot_ontap – boots the current Data ONTAP software release stored on the boot device
• boot primary – boots the Data ONTAP release stored on the boot device as the primary kernel
• boot_backup – boots the backup Data ONTAP release from the boot device
• boot_diags – boots a Data ONTAP diagnostic kernel

Note: there are other options but NetApp will provide these as when necessary

halt [-t <mins>] [-f]

-t = shutdown after minutes specified

-f = used with HA clustering, means that the partner filer does not take over

-s = clean reboot but also power cycle the filer (like pushing the off button)

-r = bypasses the shutdown (not clean) and power cycles the filer

-f = used with HA clustering, means that the partner filer does not take over

-q = quiet suppresses warning messages

## Then unlock and reset the diag users password

useradmin diaguser unlock

useradmin diaguser password

## Now you should be able to access the systemshell and use all the standard Unix

## commands

systemshell

login: diag

password: ********

## Adding a license

license add <code1> <code2>

## Disabling a license

license delete <service>

wrfile -a /etc/test1 This is line 6 # comment here

wrfile -a /etc/test1 “This is line \”15\”.”

sysconfig -a (detailed)

environment chassis Fans

environment chassis CPU_Fans

environment chassis Power

environment chassis Temperature

environment chassis [PS1|PS2]

fcstat device_map

sasstat expander_phy_state

storage show expander

storage show fabric

storage show fault

storage show hub

storage show initiators

storage show mc

storage show port

storage show shelf

storage show switch

storage show tape [supported]

storage show acp

storage array show

storage array show-ports

storage array show-luns

storage array show-config

storage power_cycle shelf completed

disk_list

sysconfig -r

sysconfig -d

## list all unnassigned/assigned disks

disk show -n

disk show -a

## Assign all disk to pool 0, by default they are assigned to pool 0 if the “-p”

## option is not specififed

disk assign all -p 0

Note: uses Rapid RAID Recovery to copy data from the specified file system to the specified spare disk, you can stop this process using the stop command

disk sanitize status

disk sanitize release <disk_list>

Note: the release modifies the state of the disk from sanitize to spare. Sanitize requires a license.

disk maint list

disk maint status

Note: you can test the disk using maintain mode

Note: it stalls all SCSI I/O until you physically replace or add a disk, can used on SCSI disk only.

## Example

ontap1> disk simpush -l

The following pulled disks are available for pushing:

v0.16:NETAPP__:VD-1000MB-FZ-520:14161400:2104448

ontap1> disk simpush v0.16:NETAPP__:VD-1000MB-FZ-520:14161400:2104448

aggr status <aggregate> [-v]

## create aggregate called newaggr that can have a maximum of 8 RAID groups

aggr create newaggr -r 8 -d 8a.16 8a.17 8a.18 8a.19

## create aggregated called newfastaggr using 20 x 15000rpm disks

aggr create newfastaggr -R 15000 20

## create aggrgate called newFCALaggr (note SAS and FC disks may bge used)

aggr create newFCALaggr -T FCAL 15

Note:

-f = overrides the default behavior that does not permit disks in a plex to belong to different disk pools

-m = specifies the optional creation of a SyncMirror

-n = displays the results of the command but does not execute it

-r = maximum size (number of disks) of the RAID groups for this aggregate

-T = disk type ATA, SATA, SAS, BSAS, FCAL or LUN

-R = rpm which include 5400, 7200, 10000 and 15000

## add an additonal disk to aggregate pfvAggr, use “aggr status” to get group name

aggr status pfvAggr -r

aggr add pfvAggr -g rg0 -d v5.25

## Add 4 300GB disk to aggregate aggr1

aggr add aggr1 4@300

## change a aggregates raid group

aggr options <aggregate> raidtype raid_dp

## change a aggregates raid size

aggr options <aggregate> raidsize 4

## Start a copy

aggr copy start <aggregate source> <aggregate destination>

## Abort a copy – obtain the operation number by using “aggr copy status”

aggr copy abort <operation number>

## Throttle the copy 10=full speed, 1=one-tenth full speed

aggr copy throttle <operation number> <throttle speed>

aggr scrub status

## start a scrub operation

aggr scrub start [ aggrname | plexname | groupname ]

## stop a scrub operation

aggr scrub stop [ aggrname | plexname | groupname ]

## suspend a scrub operation

aggr scrub suspend [ aggrname | plexname | groupname ]

## resume a scrub operation

aggr scrub resume [ aggrname | plexname | groupname ]

Note: Starts parity scrubbing on the named online aggregate. Parity scrubbing compares the data disks to the

parity disk(s) in their RAID group, correcting the parity disk’s contents as necessary. If no name is

given, parity scrubbing is started on all online aggregates. If an aggregate name is given, scrubbing is

started on all RAID groups contained in the aggregate. If a plex name is given, scrubbing is started on

all RAID groups contained in the plex.

Look at the following system options:

raid.scrub.duration 360

raid.scrub.enable on

raid.scrub.perf_impact low

raid.scrub.schedule

## start a verify operation

aggr verify start [ aggrname ]

## stop a verify operation

aggr verify stop [ aggrname ]

## suspend a verify operation

aggr verify suspend [ aggrname ]

## resume a verify operation

aggr verify resume [ aggrname ]

Note: Starts RAID mirror verification on the named online mirrored aggregate. If no name is given, then

RAID mirror verification is started on all online mirrored aggregates. Verification compares the data in

both plexes of a mirrored aggregate. In the default case, all blocks that differ are logged, but no changes

are made.

status is printed for all RAID groups currently running a media scrub. The status includes a

percent-complete and whether it is suspended.

Look at the following system options:

raid.media_scrub.enable on

raid.media_scrub.rate 600

raid.media_scrub.spares.enable on

vol status -l (display language)

vol decompress stop <vol_name>

Mirrors the currently-unmirrored traditional volume volname, either with the specified set of disks or with the contents of another unmirrored traditional volume victim_volname, which will be destroyed in the process.

The vol mirror command fails if either the chosen volname or victim_volname are flexible volumes. Flexible volumes require that any operations having directly to do with their containing aggregates be handled via the new aggr command suite.

## Change maximum number of files

maxfiles <vol_name> <max_num_files>

status is printed for all RAID groups currently running a media scrub. The status includes a

percent-complete and whether it is suspended.

Look at the following system options:

raid.media_scrub.enable on

raid.media_scrub.rate 600

raid.media_scrub.spares.enable on

## Create a 200MB volume using the english character set

vol create newvol -l en aggr1 200M

## Create 50GB flexvol volume

vol create vol1 aggr0 50g

aggr add flexvol1 -g rg0 -d v5.25

vol size flexvol1 + 100m

vol autosize flexvol1 -m 500m -I 10m on

If you specify volume_grow, Data ONTAP attempts to increase the volume’s size before deleting any Snapshot copies. Data ONTAP increases the volume size based on specifications you provided using the vol autosize command.

If you specify snap_delete, Data ONTAP attempts to create more free space by deleting Snapshot copies, before increasing the size of the volume. Data ONTAP deletes Snapshot copies based on the specifications you provided using the snap autodelete command.

vol clone split stop

vol clone split estimate

vol clone split status

Note: The vol clone create command creates a flexible volume named clone_vol on the local filer that is a clone of a “backing” flexible volume named par_ent_vol. A clone is a volume that is a writable snapshot of another volume. Initially, the clone and its parent share the same storage; more storage space is consumed only as one volume or the other changes.

vol copy abort <operation number>

vol copy throttle <operation_number> <throttle value 10-1>

## Example – Copies the nightly snapshot named nightly.1 on volume vol0 on the local filer to the volume vol0 on remote ## filer named toaster1.

vol copy start -s nightly.1 vol0 toaster1:vol0

Note: Copies all data, including snapshots, from one volume to another. If the -S flag is used, the command copies all snapshots in the source volume to the destination volume. To specify a particular snapshot to copy, use the -s flag followed by the name of the snapshot. If neither the -S nor -s flag is used in the command, the filer automatically creates a distinctively-named snapshot at the time the vol copy start command is executed and copies only that snapshot to the destination volume.

The source and destination volumes must either both be traditional volumes or both be flexible volumes. The vol copy command will abort if an attempt is made to copy between different volume types.

The source and destination volumes can be on the same filer or on different filers. If the source or destination volume is on a filer other than the one on which the vol copy start command was entered, specify the volume name in the filer_name:volume_name format.

aggr create tradvol1 -l en -t raid4 -d v5.26 v5.27

## create traditional volume using vol command

vol create tradvol1 -l en -t raid4 -d v5.26 v5.27

## Create traditional volume using 20 disks, each RAID group can have 10 disks

vol create vol1 -r 10 20

vol add tradvol1 -d v5.28

vol scrub start [volname|plexname|groupname][-v]

vol scrub stop [volname|plexname|groupname][-v]

vol scrub suspend [volname|plexname|groupname][-v]

vol scrub resume [volname|plexname|groupname][-v]

Note: Print the status of parity scrubbing on the named traditional volume, plex or RAID group. If no name is provided, the status is given on all RAID groups currently undergoing parity scrubbing. The status includes a percent-complete as well as the scrub’s suspended status (if any).

vol verify status

## start a verify operation

vol verify start [ aggrname ]

## stop a verify operation

vol verify stop [ aggrname ]

## suspend a verify operation

vol verify suspend [ aggrname ]

## resume a verify operation

vol verify resume [ aggrname ]

Note: Starts RAID mirror verification on the named online mirrored aggregate. If no name is given, then

RAID mirror verification is started on all online mirrored aggregates. Verification compares the data in

both plexes of a mirrored aggregate. In the default case, all blocks that differ are logged, but no changes

are made.

## How to display the options available and what they are set to

vol help options

vol options <flexcache_name>

## Create a FlexCache volume called flexcache1 with autogrow in aggr1 aggregate with the source volume vol1

## on storage netapp1 server

vol create flexcache1 aggr1 -S netapp1:vol1

## Server stats

flexcache stats -S <volume_name> -c <client>

## File stats

flexcache fstat <path>

df -Lh

## create a flexclone called flexclone1 from the parent flexvol1

vol clone create flexclone1 -b flexvol1

## Double check you have the space

df -Ah

## Perform the split

vol clone split start <flexclone_name>

## Check up on its status

vol colne split status <flexclone_name>

## Stop the split

vol clone split stop <flexclone_name>

• Cloning operation ID

• The name of the volume in which the cloning operation was performed

• Start time of the cloning operation

• End time of the cloning operation

• Parent file/LUN and clone file/LUN names

• Parent file/LUN ID

• Status of the clone operation: successful, unsuccessful, or stopped and some other details

## Use previous checkpoint

sis start -sp <path>

Note: schedule lists the days and hours of the day when deduplication runs. The schedule can be of the following forms:

• day_list[@hour_list]If hour_list is not specified, deduplication runs at midnight on each scheduled day.
• hour_list[@day_list]If day_list is not specified, deduplication runs every day at the specified hours.
• • -A hyphen (-) disables deduplication operations for the specified FlexVol volume.

The -i option includes the qtree ID number in the display.

The -v option includes the owning vFiler unit, if the MultiStore license is enabled.

## create a news qtree in the /vol/users volume using 770 as permissions

qtree create /vol/users/news -m 770

## Create the qtree

qtree create /n/joel/vol1/dir1

## Move the contents of the old directory back into the new QTree

mv /n/joel/vol1/olddir/* /n/joel/vol1/dir1

## Remove the old directory name

rmdir /n/joel/vol1/olddir

-z = zero stats

## Change the security style of /vol/users/docs to mixed

qtree security /vol/users/docs mixed

##                                          	hard limit | thres |soft limit
##Quota Target      	type                   	disk  files| hold  |disk  file
##-------------     	-----                  	----  -----  ----- ----- ----
*                    tree@/vol/vol0           -     -      -     -     -     # monitor usage on all qtrees in vol0
/vol/vol2/qtree      tree                    1024K  75k    -     -     -     # enforce qtree quota using kb
tinh                 user@/vol/vol2/qtree1   100M   -      -     -     -     # enforce users quota in specified qtree
dba                  group@/vol/ora/qtree1   100M   -      -     -     -     # enforce group quota in specified qtree

# * = default user/group/qtree
# – = placeholder, no limit enforced, just enable stats collection

Note: you have lots of permutations, so checkout the documentation

-w = return only after the entire quotas file has been scanned

lun show -v

lun show -m

Note: use “-f” to force the mapping

lun unmap /vol/tradvol1/lun1 win_hosts_group1 0

# Create the LUN clone by entering the following command

lun clone create /vol/tradvol1/clone_lun1 -b /vol/tradvol1/tradvol1_snapshot_08122010 lun1

igroup show iqn.1991-05.com.microsoft:xblade

iscsi connection show -v

iscsi security show

iscsi nodename <new name>

iscsi interface disable e0b

igroup show linux-igroup1

fcp nodename [-f]nodename

fcp nodename 50:0a:09:80:82:02:8d:ff

Note: The WWNN of a storage system is generated by a serial number in its NVRAM, but it is stored ondisk. If you ever replace a storage system chassis and reuse it in the same Fibre Channel SAN, it is possible, although extremely rare, that the WWNN of the replaced storage system is duplicated. In this unlikely event, you can change the WWNN of the storage system.

fcp wwpn-alias show -w 10:00:00:00:c9:30:80:2

fcp wwpn-alias remove -w 10:00:00:00:c9:30:80:2

# Create a Snapshot copy of the volume containing the LUN to be cloned by entering the following command

snap create tradvol1 tradvol1_snapshot_08122010

# Create the LUN clone by entering the following command

lun clone create /vol/tradvol1/clone_lun1 -b /vol/tradvol1/lun1 tradvol1_snapshot_08122010

# Delete all the LUNs in the active file system that are displayed by the lun snap usage command by entering the following command

lun destroy /vol/tradvol1/clone_lun1

# Delete all the Snapshot copies that are displayed by the lun snap usage command in the order they appear

snap delete tradvol1 tradvol1_snapshot_08122010

Note: Prior to Data ONTAP 7.3, the system automatically locked all backing Snapshot copies when Snapshot copies of LUN clones were taken. Starting with Data ONTAP 7.3, you can enable the system to only lock backing Snapshot copies for the active LUN clone. If you do this, when you delete the active LUN clone, you can delete the base Snapshot copy without having to first delete all of the more recent backing Snapshot copies.

This behavior in not enabled by default; use the snapshot_clone_dependency volume option to enable it. If this option is set to off, you will still be required to delete all subsequent Snapshot copies before deleting the base Snapshot copy. If you enable this option, you are not required to rediscover the LUNs. If you perform a subsequent volume snap restore operation, the system restores whichever value was present at the time the Snapshot copy was taken.

# create export in memory and write to /etc/exports (use specific options)

exportsfs -io sec=none,rw,root=192.168.0.80,nosuid /vol/nfs1

# create export in memory only using own specific options

exportsfs -io sec=none,rw,root=192.168.0.80,nosuid /vol/nfs1

# Memory and /etc/exportfs

exportfs -z <path>

# The following command enables fencing of cat from /vol/vol0

exportfs -b enable save cat /vol/vol0

# cat moves to the front of the ro= list for /vol/vol0:

-rw=pig:horse:dog,ro=cat:duck,anon=0

Note: use “rdfile” to read the file

cifs terminate <client_name>|<IP Address>

cifs sessions <IP Address>

# Authentication

cifs sessions -t

# Changes

cifs sessions -c

# Security Info

cifs session -s

cifs access sysadmins -g wheel Full Control

cifs access -delete releases ENGINEERING\mary

Note: rights can be Unix-style combinations of r w x – or NT-style “No Access”, “Read”, “Change”, and “Full Control”

cifs stat <IP Address>

# Now you can create your share

cifs shares -add TEST /vol/flexvol1/TEST -comment “Test Share ” -forcegroup workgroup -maxusers 100

cifs shares -change <sharename> -novscan

# Add a home directory

wrfile -a /etc/cifs_homedir.cfg /vol/TEST

# check it

rdfile /etc/cifs_homedir.cfg

# Display for a Windows Server

net view \\<Filer IP Address>

# Connect

net use * \\192.168.0.75\TEST

Note: make sure the directory exists

# delete a domain controller

cifs prefdc delete lab

# List domain information

cifs domaininfo

# List the preferred controllers

cifs prefdc print

# Restablishing

cifs resetdc

sectrace add -ip 192.168.10.23

sectrace add -unixuser foo -path /vol/vol0/home4 -a

# To remove

sectrace delete all

sectrace delete <index>

# Display tracing

sectrace show

# Display error code status

sectrace print-status <status_code>

sectrace print-status 1:51544850432:32:78

Note: To prevent users from modifying files while the FTP server is transferring them, you can enable FTP file locking. Otherwise, you can disable FTP file locking. By default, FTP file locking is disabled.

Note: If the ftpd.bypass_traverse_checking option is set to off, when a user attempts to access a file using FTP, Data ONTAP checks the traverse (execute) permission for all directories in the path to the file. If any of the intermediate directories does not have the “X” (traverse permission), Data ONTAP denies access to the file. If the ftpd.bypass_traverse_checking option is set to on, when a user attempts to access a file, Data ONTAP does not check the traverse permission for the intermediate directories when determining whether to grant or deny access to the file.

# specify the name for the anonymous login

options ftpd.anonymous.name username

# create the directory for the anonymous login

options ftpd.anonymous.home_dir homedir

# specify the max number of logfiles (default is 6) and size

options ftpd.log.nfiles 10

options ftpd.log.filesize 1G

Note: use rdfile to view

ftp stat -z

Note: this is similar to the FTP version

options httpd.log.format alt1

Note: use rdfile to view

httpstat -z[derta]

# Remove a IP Address

ifconfig e3 0

ifconfig e8 flowcontrol none

Note: value is the flow control type. You can specify the following values for the flowcontrol option:

none    - No flow control

receive – Able to receive flow control frames

send    - Able to send flow control frames

full    - Able to send and receive flow control frames

The default flowcontrol type is full.

options cf.takeover.on_network_interface_failure enable

ifconfig interface_name {nfo|-nfo}

nfo   — Enables negotiated failover

-nfo  — Disables negotiated failover

Note: In an HA pair, you can assign a partner IP address to a network interface. The network interface takes over this IP address when a failover occurs

# Remove alias

ifconfig e0 -alias 192.0.2.30

options interface.blocked.cifs e0a,e0b

# Unblock

options interface.blocked.cifs “”

Note: there are many options to both these commands so I will leave to the man pages

# the full /etc/rc file will look like something below

hostname netapp1

ifconfig e0 192.168.0.10 netmask 255.255.255.0 mediatype 100tx-fd

route add default 192.168.0.254 1

routed on

on   — Enables fast path

off  — Disables fast path

on   — Turns on the routed daemon

off  — Turns off the routed daemon

routed status

options dns.enable {on|off}

Note:

on   — Enables DNS

off  — Disables DNS

# To flush the DNS cache

dns flush

# To see dns cache information

dns info

on     — Enables dynamic DNS updates

off    — Disables dynamic DNS updates

secure — Enables secure dynamic DNS updates

options dns.update.ttl 2h

Note: time can be set in seconds (s), minutes (m), or hours (h), with a minimum value of 600 seconds

and a maximum value of 24 hour

vlan create e4 10 20 30

# Configure the VLAN interface e4-10 by using the following command

ifconfig e4-10 192.168.0.11 netmask 255.255.255.0

# Delete All VLANs on a interface

vlan delete e4

vlan stat e4

vlan stat e4 10

# To configure an IP address of 192.168.0.10 and a netmask of 255.255.255.0 on the singlemode interface group SingleTrunk1

ifconfig SingleTrunk1 192.168.0.10 netmask 255.255.255.0

# To specify the interface e1 as preferred

ifgrp favor e1

ifgrp create multi MultiTrunk1 -b mac e0 e1 e2 e3

# To create a dynamic multimode interface group, comprising interfaces e0, e1, e2, and e3 and using IP

# address based load balancing

ifgrp create lacp MultiTrunk1 -b ip e0 e1 e2 e3

ifgrp create multi Firstlev1 e0 e1

ifgrp create multi Firstlev2 e2 e3

ifgrp create single Secondlev Firstlev1 Firstlev2

# To enable failover to a multimode interface group with higher aggregate bandwidth when one or more of

# the links in the active multimode interface group fail

options ifgrp.failover.link_degraded on

Note: You can create a second-level interface group by using two multimode interface groups. Secondlevel interface groups enable you to provide a standby multimode interface group in case the primary multimode interface group fails.

# On StorageSystem1:

ifgrp create multi Firstlev1 e1 e2

ifgrp create multi Firstlev2 e3 e4

ifgrp create single Secondlev1 Firstlev1 Firstlev2

# On StorageSystem2 :

ifgrp create multi Firstlev3 e5 e6

ifgrp create multi Firstlev4 e7 e8

ifgrp create single Secondlev2 Firstlev3 Firstlev4

# On StorageSystem1:

ifconfig Secondlev1 partner Secondlev2

# On StorageSystem2 :

ifconfig Secondlev2 partner Secondlev1

# select a non-favoured interface

ifgrp nofavor e3

Note: You must configure the interface group to the down state before you can delete a network interface

from the interface group

Note: You must configure the interface group to the down state before you can delete a network interface

from the interface group

# Disable ping throttling

options ip.ping_throttle.drop_level 0