Steps creating VFiler

Steps creating VFiler

The following conditions must be met before you can create a vFiler unit :

• You must create at least one unit of storage (qtrees, volumes - traditional or flexible) before creating
vfiler

• The storage unit that contains vFiler unit configuration information must be writable volume. It must
not be a read-only file system.

sysntax: vfiler create <vfiler name> -i <ip address> <Volume or Qtree path>

Below red colors are input to configure vfiler.

3070-1> vfiler create vfiler_name -i 10.100.201.120 -i /vol/vol1

Tue Nov 9 03:03:39 GMT [Vfiler_name@useradmin.added.deleted:info]: The role 'compliance' has been
added.
Tue Nov 9 03:03:39 GMT [Vfiler_name@export.file.backup.notDone:warning]: Could not read from file
/etc/exports.
Tue Nov 9 03:03:39 GMT [Vfiler_name@export.file.missing:warning]: Could not open '/etc/exports' for
reading.
The etc configuration directory for vfiler "Vfiler_name" is /vol/vol1/etc.
Tue Nov 9 03:03:39 GMT [Vfiler_name@cmds.vfiler.info:notice]: vFiler unit Vfiler_name initialized.
Setting up vfiler Vfiler_name
Configure vfiler IP address 10.100.201.120? [y]: y
Interface to assign this address to {e0a, e0b, e0c, e0d}: e0b
Netmask to use: [255.255.255.0]:
Configure vfiler IP address 10.100.201.121? [y]: y
Interface to assign this address to {e0a, e0b, e0c, e0d}: e0c
Netmask to use: [255.255.255.0]:
The administration host is given root access to the filer's
/etc files for system administration. To allow /etc root access
to all NFS clients enter RETURN below.
Please enter the name or IP address of the administration host: 10.100.200.9 (Base netapp filer ip)
Do you want to run DNS resolver? [n]:
Do you want to run NIS client? [n]:
e0b: flags=0x2f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 10.100.201.77 netmask 0xffffff00 broadcast 10.100.201.255
ether 00:a0:98:0d:20:be (auto-1000t-fd-up) flowcontrol full
e0c: flags=0x2f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500
inet 10.100.201.67 netmask 0xffffff00 broadcast 10.100.201.255
ether 00:a0:98:0d:20:bd (auto-1000t-fd-up) flowcontrol full
Tue Nov 9 03:04:39 GMT [Vfiler_name@useradmin.added.deleted:info]: The user 'root' has been added.
Default password for root on vfiler Vfiler_name is "".
New password:
Retype new password:
Tue Nov 9 03:04:47 GMT [Vfiler_name@passwd.changed:info]: passwd for user 'root' changed.
Do you want to setup CIFS? [y]:
This process will enable CIFS access to the filer from a Windows(R) system.
Use "?" for help at any prompt and Ctrl-C to exit without committing changes.
Your filer does not have WINS configured and is visible only to
clients on the same subnet.
Do you want to make the system visible via WINS? [n]:
A filer can be configured for multiprotocol access, or as an NTFS-only
filer. Since multiple protocols are currently licensed on this filer,
we recommend that you configure this filer as a multiprotocol filer
(1) Multiprotocol filer
(2) NTFS-only filer
Selection (1-2)? [1]: 1
CIFS requires local /etc/passwd and /etc/group files and default files
will be created. The default passwd file contains entries for 'root',
'pcuser', and 'nobody'.
Enter the password for the root user []:
Retype the password:
The default name for this CIFS server is 'VFILER_NAME'.
Would you like to change this name? [n]: n
Data ONTAP CIFS services support four styles of user authentication.
Choose the one from the list below that best suits your situation.
(1) Active Directory domain authentication (Active Directory domains only)
(2) Windows NT 4 domain authentication (Windows NT or Active Directory domains)
(3) Windows Workgroup authentication using the filer's local user accounts
(4) /etc/passwd and/or NIS/LDAP authentication
Selection (1-4)? [1]: 3
What is the name of the Workgroup? [WORKGROUP]:
CIFS - Starting SMB protocol...
It is recommended that you create the local administrator account
(VFILER_NAME\administrator) for this filer.
Do you want to create the VFILER_NAME\administrator account? [y]:
Enter the new password for VFILER_NAME\administrator:
Retype the password:
Welcome to the WORKGROUP Windows(R) workgroup
Tue Nov 9 03:05:09 GMT [vfiler_name@passwd.changed:info]: passwd for user 'root' changed.
Tue Nov 9 03:05:19 GMT [vfiler_name@cifs.startup.local.succeeded:info]: CIFS: CIFS local server is
running.

3070-1> vfiler status

vfiler0 running
vifiler_name running

Note : vfiler0 is the default (once we enable the license default will create)

Steps creating VFiler DR(disaster

recovery)

Related Topic

VFILER COMMANDS
Vfiler

Enable Security tab in windows 2003

1. For windows 2003 server

 Click Start --> run

Type Regsvr32 rshx32.dll and enter

2. For windows 2003 server

 Start--> run
 Type regedit
 Locate the following key in the
registry: HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAd
min
 On the Edit menu, click Add Value, and then add the following registry
value: Value Name:
ShowSecurityPage. Data Type:
REG_DWORD Radix:
Binary Value: 1
 Quit Registry Editor.

VFILER COMMANDS
TO CREATE A VFILER UNIT:
> vfiler create <vfiler name> -i <ip address> <Volume or Qtree path>

Fas2050> vfiler create vfiler1 -i 10.10.x.x /vol/vol1

 After command executed vfiler1 is installed in volume1

 vfiler install is same like ONTAP installation.

TO GO TO A VFILER CLI:

> vfiler context <vfiler name>

Fas2050> vfiler context vfiler1

 This is the command to enter in vfiler unit.

TO GO TO NON DEFAULT VFILER UNIT:

> vfiler context <vfiler0>

Fas2050> vfiler context vfiler0

 Vfiler0 is the main filer

 If this command is execute vfiler come to Physical filer(FAS2050)

TO RENAME A VFILER:

> vfiler rename <old name> <new name>

Fas2050> vfiler rename old_vfiler1 to new_vfiler

TO DESTROY A VFILER:
> vfiler stop <vfiler name> and then vfiler destroy <vfiler name>

 we cannot destroy vfiler directly

Fas2050> vfiler stop vfiler1

Fas2050> vfiler destroy viler1

TO CONFIGURE DISASTER RECOVERY FOR A VFILER:
> vfiler dr configure –l <remote_login:remote_passwd>

TO ADD RESOURCES TO A VFILER:

 Resources is nothing, its is another volume or qtree

 if we need to increase vfiler space, we can add another volume or qtree

> vfiler add <vfiler name> -I <ip address> <path>

Fas2050>
TO REMOVE RESOURCES FROM A VFILER:
 if added more than enough volume or qtree means,
 we can remove resources from vfiler

> vfiler remove <vfiler name> -I <ip address> <path>

TO MIGRATE A VFILER:
> vfiler migrate start –l <remote_login:remote_passwd>
remote_vfiler@remote_filer

Fas2050>

TO MOVE RESOURCES FROM ONE VFILER TO OTHER IS:

> vfiler move <vfiler_from> <vfiler_to> -I <ip address> <path>

Fas2050>

To START A VFILER:
> vfiler start <vfiler name>

Fas2050> vfiler start vfiler1

TO STOP A VFILER:
> vfiler stop <vfiler name>

Fas2050> vfiler stop vfiler1

TO CHECK THE STATUS OF A VFILER:

> vfiler status

Fas2050> vfiler status

TO RUN A COMMAND ON A VFILER:

> vfiler run <vfiler name> command

Fas2050>

TO ALLOW USE OF A PROTOCOL ON A VFILER:

 Using vfiler allow command, we can allow need protocols

> vfiler allow <vfiler name> <proto=cifs| nfs| rsh| iscsi| ftp
| http>

Fas2050> viler allow vfiler1 cifs

TO DISALLOW USE OF A PROTOCOL ON A VFILER:

 Using vfiler disallow command, we can remove unwanted protocols.
> vfiler disallow <vfiler name> <proto=cifs| nfs| rsh| iscsi| ftp
| http>

Fas2050> viler disallow vfiler1 cifs

TO SET NUMBER OF VFILER UNIT:

 Maximum of 65 vfiler unit and 65th is viler0 for one filer.
 we can limit vfiler unit creation for the physical filer
 if we limited vfiler means we cannot create more than limited value

> vfiler limit <number>

Fas2050> vfiler limit 15

LICENSING THE VILER:

> license add <Multistore license>

Fas2050> license add xxxxxxxxxxxxx

Related Topic

VFILER COMMANDS
VFILER

Vfiler
MultiStore
1. MultiStore is a software product you can use optionally.
2. MultiStore enables you to partition the storage and network resources of a single
storage system so that it appears as multiple storage systems on the network.
3. Each "storage system" created as a result of the partitioning is called a vFiler unit.
4. A vFiler unit, using the resources assigned, delivers file services to its clients as a
storage system does.The storage resource assigned to a vFiler unit can be one or more
qtrees or volumes. The network resource assigned can be one or more base IP addresses or
IP aliases associated with network interfaces.
5. You can add or remove resources at any time.
6. we don't need additional license for the vfiler unit, we can use physical filer license to
vfiler unit.
Reasons for using MultiStore
MultiStore has many features that you can use for your provisioning needs.
1. To consolidate multiple servers to one storage system.
2. To use the storage system to host data for multiple customers, such as clients of a
service provider or different organizations within an enterprise.
3. To use the SnapMirror technology for migrating data from one storage system to
another
transparently.
Some limitations of MultiStore
1. You can have a maximum of 65 vFiler units on a storage system. You can create 64
vFiler units on a storage system. The 65th vFiler unit is vfiler0, which is created automatically
when MultiStore is licensed on the storage system.
2. In an active/active configuration, you can create up to 64 vFiler units on each node of
the active/active configuration, for a maximum of 130 vFilers in the active/active configuration.
3. Only Ethernet interfaces are supported for vFiler units
4. Only the NFS, CIFS, iSCSI, HTTP, and FTP protocols are supported for the vFiler
units. However, protocols not supported on vFiler units are supported on vfiler0, the default
vFiler unit.

Related Topic

VFILER COMMANDS
Steps creating VFiler and Dr

NetApp Maxfiles
Maxfiles
1. Using maxfiles command we can increase the number of inodes in the respective
volume, so that we create additional files.
2. We may not decrease the inode value because you might not be able to run
WAFL_check.
3. One file is one inodes

The below examples show how to inodes increase:

STEP :1

fas3070> aggr create aggr1 10

Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.24 Shelf
1 Bay 8 [NETAPP VD-100MB 0042] S/N [50125907] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.36 Shelf
2 Bay 4 [NETAPP VD-100MB 0042] S/N [50130017] to aggregate aggr1 has completed successfully
Creation of an aggregate with 10 disks has completed.
fas3070> Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk
/aggr1/plex0/rg0/v4.22 Shelf 1 Bay 6 [NETAPP VD-100MB 0042] S/N [50125906] to aggregate aggr1
has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.35 Shelf
2 Bay 3 [NETAPP VD-100MB 0042] S/N [50130016] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.21 Shelf
1 Bay 5 [NETAPP VD-100MB 0042] S/N [50125905] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.34 Shelf
2 Bay 2 [NETAPP VD-100MB 0042] S/N [50130015] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.20 Shelf
1 Bay 4 [NETAPP VD-100MB 0042] S/N [50125904] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.33 Shelf
2 Bay 1 [NETAPP VD-100MB 0042] S/N [50130014] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.19 Shelf
1 Bay 3 [NETAPP VD-100MB 0042] S/N [50125903] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.32 Shelf
2 Bay 0 [NETAPP VD-100MB 0042] S/N [50125913] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:17 GMT [wafl.vol.add:notice]: Aggregate aggr1 has been added to the system.
fas3070> Fri Aug 31 06:29:20 GMT [nbt.nbns.registrationComplete:info]: NBT: All CIFS name
registrations have completed for the local server.

STEP:2

CREATE THE NEW VOLUME FOR 100MB

fas3070>
fas3070> vol create vol1 aggr1 1.2g
Creation of volume 'vol1' with size 1.2g on containing aggregate
'aggr1' has completed.
fas3070>

STEP:3

CHECK THE VOL1 & VOL1 INODE VALUE

fas3070> maxfiles
Volume vol0: maximum number of files is currently 19990 (6096 used)
Volume vol1: maximum number of files is currently 322,122547 (52870 used)
fas3070>

STEP:4

NOW THE CHECK THE USED AND FREE INODE OF VOL1

fas3070> df -i /vol/vol1
Filesystem iused ifree %iused Mounted on
/vol/vol0 52870 322,122547 97% /vol/vol0
fas3070>

STEP:5

INCREASING THE INODE VAULE 3033 TO 5000

fas3070> maxfiles vol1 422,122547

The new maximum number of files specified is more than twice as big as it needs to be, based on
current usage patterns. Increasing the maximum number of files consumes disk space, and the
number can never
be decreased. Configuring a large number of inodes can also result in less available memory after an
upgrade, which means you might not be able to run WAFL_check.

The new maximum number of files will be rounded to 422,122540.

Are you sure you want to increase the maximum number of files? y
fas3070>

fas3070> maxfiles
Volume vol0: maximum number of files is currently 19990 (6154 used).
Volume vol1: maximum number of files is currently 422,122540 (52870used).
fas3070>

NOW THE INODE VALUE IS 4988 AT MAXIMUM OF VOLUME1

FINISHED
All General Commands
General Commands

1. setup (Re-Run initial setup)

2. halt (Reboots controller into bootrom)
3. reboot (Reboots controller back to Data Ontap)
4. sysconfig -a (System configuration and information)
5. java netapp.cmds.jsh (limited freebsd cli)
6. storage show disk (show physical information about disks)
7. passwd (Change password for logged in user)
8. sasadmin shelf (shows a graphical layout of your shelves with occupied disk slots)
9. options trusted.hosts x.x.x.x or x.x.x.x/nn (hosts that are allowed telnet, http, https
and ssh admin access. x.x.x.x = ip address, /nn is network bits)
10. options trusted.hosts * (Allows all hosts to the above command)
11. sysstat -s 5 (Displays operating statistics every 5 seconds i.e. CPU, NFS, CIFS, NET,
DISK, etc)
12. options autologout.console.enable on (Turns on autologout for the console)
13. options autologout.console.timeout 300 (300 second autologout for the console)
14. options autologout.telnet.enable on (Turns on autologout for telnet)
15. options autologout.telnet.timeout 300 (300 second autologout for the console)

Diagnostics

1. Press DEL at boot up during memory test followed by boot_diags and select all
(Diagnostic tests for a new install)
2. priv set diags (Enter diagnostics CLI mode from the Ontap CLI)
3. priv set (Return to normal CLI mode from diagnostics mode)

Software

1. software list (Lists software in the /etc/software directory)

2. software get http://x.x.x.x/8.0_e_image.zip 8.0_e_image.zip (Copy software from http
to software directory)
3. software delete (Deletes software in the /etc/software directory)
4. software update 8.0_e_image.zip -r (Install software. The -r prevents it rebooting
afterwards)
Baseboard Management Controller BMC

1. bmc status (shows the status of the BMC remote management interface)
2. bmc setup (BMC remote management interface setup)

Service Port SP

1. sp status (shows the status of the SP remote management interface)

2. sp setup (SP remote management setup)

ACP (Alternate Control Path)

1. options acp.enabled on (Turns on ACP)

2. storage show acp -a (show ACP status)

Root Volume

1. If you have a 32-bit root volume that you wish to convert to 64-bit, the best way I
found is to snapmirror the root volume to a 64-bit aggregate, break the snapmirror, set the
new root volume as root, and either failover and failback the filer, or reboot.

Aggregates

1. aggr create aggregate_name (Creates an Aggregate)

2. aggr destroy aggregate_name (removes an Aggregate)
3. aggr offline aggregate_name (takes an Aggregate offline)
4. aggr online aggregate_name (bring an Aggregate online)
5. aggr options aggregate_name root (makes an Aggregate root|Only use if your Root
Aggregate is damanged)
6. aggr status (shows status of all aggregates)
7. aggr status aggregate_name (show status of a specific Aggregate)
8. aggr status -r aggr0 (shows the root volume on aggr0 and the disk layout)
9. aggr status -s aggr0 (shows spare disks on aggr0)
10. aggr status -v aggr0 (MUST BE DONE IN PRIV SET DIAG MODE. Shows more
detailed information of the aggregate status)
11. aggr show_space aggregate_name (shows specific aggregate space information)
12. aggr options aggregate_name nosnap=on (Disable snapshot autocreation)
13. aggr options aggregate_name raidsize=x (x being the number of drives in the RAID)
14. aggr scrub status -v (MUST BE DONE IN PRIV SET DIAG MODE. Shows scrub
status of the aggregate)
15. aggr scrub resume (MUST BE DONE IN PRIV SET DIAG MODE. Resumes a
susepended scrub)
16. aggr scrub suspend (MUST BE DONE IN PRIV SET DIAG MODE. Suspends a
current scrub process)
 17. aggr scrub start (MUST BE DONE IN PRIV SET DIAG MODE. Starts a new scrub
process)
18. snap reserve -A aggregate_name 0 (Set Aggregate snap reserve to 0% or any
number you enter)
19. snap list -A aggregate_name (Lists snapshots on specified aggregate)
20. snap delete -A aggregate_name (Deletes a snapshot on a specified aggregate)
21. snap sched -A aggregate_name x x x@x,x,x (Creates a snapshot shedule in weeks
days hours@time ie 0 2 1@9 means no weekly snaps, 2 daily, 1 hourly @ 9am)

Volumes

1. vol create volume_name (Creates a volume)

2. vol autosize volume_name (Shows autosize settings for a given volume)
3. vol autosize volume_name on|off (Turns Volume autosize on or off)
4. vol options volume_name (Lists volume options)
5. vol size volume_name + size k|m|g|t (increase volume size by KB, MB, GB or TB)
6. vol status -f (lists broken or failed disks)
7. vol scrub status -v (Shows the scrubbing status of volumes)
8. vol options nosnapdir on|off (enables or disables snapshot visibility from the volume
or LUN level)

Qtree’s

1. qtree create /vol/volume_name/qtree_name (Create a qtree within a volume)

2. qtree security /vol/volume_name/qtree_name unix|ntfs|mixed (Change security
settings of a qtree)
3. qtree stats qtree_name (Shows CIFS or NFS ops/sec for a given qtree)
4. qtree status (Displays all your Qtree’s)

Snapshots

1. snap create volume_name snapshot_name (create a snapshot)

2. snap list volume_name (List snapshots for a volume)
3. snap delete volume_name snapshot_name (delete a snapshot on a volume)
4. snap delete -a volume_name (Deletes all snapshots for a volume)
5. snap autodelete volume_name show (Shows snapshot autodelete settings for a
volume)
6. snap restore -s snapshot_name volume_name (Restores a snapshot on the specified
volume name)
7. snap sched volume_name weeks days hours@time (Creates a snapshot schedule on
a volume i.e. snap sched volume 4 5 1@07 Weekly Snapshots are created at midnight on
each Sunday, Daily snapshots are created each day except Sunday at midnight)
8. snap delta volume_name (Shows delta changes between snapshots for a given
volume)
9. snap reserve volume_name (Shows the snap reserve for a given volume)
10. snap reclaimable volume_name snapshot_name (Shows the amount of space
reclaimable if you remove this snapshot from the volume)
 11. options cifs.show_snapshot on (Allows snapshot directory to be browse-able via
CIFS)
12. options nfs.hide_snapshot off (Allows snapshot directory to be visible via NFS)

SnapMirror

1. options snapmirror.enable on (turns on SnapMirror. Replace on with off to toggle)

2. rdfile /etc/snapmirror.allow (Performed on the Source Filer. You should see you
destination filers in this file.)
3. wrfile /etc/snapmirror.allow (Performed on the Source Filer. Overwrites the file with
the specified destination filer name and ip address)
4. vol restrict volume_name (Performed on the Destination. Makes the destination
volume read only which must be done for volume based replication. Don’t use for Qtree
based replication)
5. snapmirror initialize -S srcfiler:source_volume dstfiler:destination_volume (Performed
on the destination. This is for full volume mirror. For example snapmirror initialize -S
filer1:vol1 filer2:vol2)
6. snapmirror initialize -S srcfiler:/vol/vol1/qtree dstfiler:/vol/vol1/qtree (Performed on the
destination. Performs the same as the command above but for Qtree’s only)
7. snapmirror initialize -S srcfiler/vol/vol1/- dstfiler:/vol/vol1/qtree (Performed on the
destination. Performs volume to qtree replication. Includes all luns, exports on the source
volume)
8. snapmirror status (Shows the status of snapmirror and replicated volumes or qtree’s)
9. snapmirror status -l (Shows much more detail that the command above, i.e. snapshot
name, bytes transferred, progress, etc)
10. snapmirror quiesce volume_name (Performed on Destination. Pauses the SnapMirror
Replication. If you are removing the snapmirror relationship this is the first step.)
11. snapmirror break volume_name (Performed on Destination. Breaks or disengages
the SnapMirror Replication. If you are removing the snapmirror relationship this is the second
step followed by deleting the snapshot)
12. snapmirror resync volume_name (Performed on Destination. When data is out of
date, for example working off DR site and wanting to resync back to primary, only performed
when SnapMirror relationship is broken)
13. snapmirror update -S srcfiler:volume_name dstfiler:volume_name (Performed on
Destination. Forces a new snapshot on the source and performs a replication, only if an initial
replication baseline has been already done)
14. snapmirror release volume_name dstfiler:volume_name (Performed on Destination.
Removes a snapmirror destination)
15. /etc/snapmirror.conf (edit or wrfile this file on the destination filer or vfiler to enter in a
snapmirror schedule. i.e. srcfiler:vol1 dstfiler:vol1 – 15 * * * This will replicate every 15
minutes. Each * represents a value. Starting from right to left you have day of week, month,
day of month, hour minute. Minute 0-59, hours 0-23, day-of-month 1-31, day-of-week 0 for
Sunday – 6 Saturday) Each value can only be a number.)
16. /vol/vfiler_vol/etc/snapmirror.conf (read or write this file for snapmirror configurations
on a vfiler. vfiler_vol being the first volume with the /etc in the vfiler)
17. “priv set diag” followed by “snapmirror break -h ” followed by “priv set”. (If for some
reason you snapmirror relationship has been orphaned, meaning it doesn’t exist in snapmirror
status on the source but does exist on the destination, you can use these three commands to
force the destination to become read/write. You can then do “snap list” and find the baseline
snapshot for the destination. Followed by snap delete of the baseline snapshot. This will
remove the snapmirror relationship if all else fails. Lastly don’t forget to remove the entry from
snapmirror.conf)
Cluster

1. cf enable (enable cluster)

2. cf disable (disable cluster)
3. cf takeover (take over resources from other controller)
4. cf giveback (give back controller resources after a take over)

vFiler – Multistore

1. vfiler limit (Performed on the host to see what the limit of vfilers is)
2. vfiler limit 16 (Performed on the host to change the limit of vfilers to 16 or any number
you specify. Check the documentation for Memory Requirements before doing this)
3. vfiler status (Displays the status of the vfiler i.e. running or stopped)
4. vfiler status -r (On the host system. Shows which volumes are running on each vfiler)
5. vfiler rename old_vfiler_name new_vfiler_name (Renames a vfiler)
6. vfiler run vfiler_name setup (Runs the vfiler setup wizard)
7. vfiler run vfiler_name cifs setup (Runs the cifs setup wizard for a vfiler)
8. ipspace create ipspacename (Creates an ipspace – needed when 2 or more vfilers
use the same network subnets)
9. ipspace list (Lists the available ipspace’s)
10. ipspace assign ipspacename interface_name (Assigns the interface to an ipspace.)
11. ipspace destroy ipspace_name (Removes/Deletes an ipspace)
12. vfiler create vfiler_name -s ipspace_name -i x.x.x.x /vol/volume_name or qtree_name
(Creates a vfiler name with ip address x.x.x.x and assigns the volume or qtree to the vfiler.
The -s is optional)
NOTE:
Creating a qtree as the base vfiler does not allow you to enable snapmirror. You must create
the
base as a volume!
1. vfiler add vfiler_name -i x.x.x.x /vol/volume_name (Adds an ip address and additional
volume (can be qtree) to an existing vfiler name)
2. vfiler remove vfiler_name -i x.x.x.x /vol/volume_name (Removes an IP address and
volume from an existing vfiler)
3. vfiler destroy vfiler_name (Deletes/removes a vfiler)
4. vfiler rename vfiler_name_old vfiler_name_new (Renames a vfiler from old name to
new name)
5. vfiler context vfiler_name (Changes CLI into the context of the vfiler name)
6. vfiler allow vfiler_name proto=cifs proto=nfs proto=iscsi (Allows the following
protocols cifs, nfs and iscsi. Disallows rsh, ssh, ftp and http)
7. vfiler stop vfiler_name (Stops a vfiler instance)
8. vfiler start vfiler_name (Starts a vfiler instance)
9. vfiler run vfiler_name route add default x.x.x.x 1 (Adds a default route to a vfiler.
Performed from vfiler0)
10. route add x.x.x.x/x x.x.x.x 1 (Adds a route in a vfiler)
11.
12. To add extra vlans to a vfiler you must do the following:
13. Check the ip space that the vfiler is using by typing ipspace list
14. Create the vlan interface on the host i.e. vif0-360 for vlan 360
 15. Assign the interface to the ip space of the vfiler i.e. ipspace assign ipspace_name
vif0-360
16. Add the ip address you wish to use on the vlan interface to the vfiler i.e. vfiler add
vfiler_name -i 192.168.1.1
17. Once the vfiler has this ip address in it’s config we can add it onto the interface i.e.
ifconfig vif0-360 192.168.1.1 netmask 255.255.255.0
Autosupport

1. options autosupport.support.enable on (Turns Autosupport on)

2. options autosupport.support.enable off (Turns Autosupport off)
3. autosupport.doit “description” (creates an autosupport alert with a user defined
description)

Hot Spares

1. Any functioning disk that is not assigned to an aggregate but is assigned to a

controller functions as a hot spare disk
2. disk show
3. vol status -r (displays which disks are allocated as spare)

Disks

1. disk show (Show disk information)

2. disk show -n (Show unowned disks)
3. disk assign 0d.02.0 -s unowned (Changes ownership from owned to unowned or to
other cluster member)
4. disk assign 0d.02.0 (assigns the disk to the controller you perform the command on)
5. options disk.auto_assign off (turns auto assign of unowned disks to controllers to off)
6. options disk.auto_assign on (turns auto assign of unowned disks to controllers to on)
7. storage show disk -p (displays primary, secondary port, shelf and bay in a metro
cluster)

Luns

1. lun setup (runs the cli lun setup wizard)

2. lun create -s 10g -t windows_2008 -o noreserve /vol/vol1/lun1 (creates a lun of 10GB
with type Windows 2008, sets no reservation and places it in the following volume or qtree)
3. lun offline lun_path (takes a lun offline)
4. lun online lun_path (brings a lun online)
5. lun show -v (Verbose listing of luns)
6. lun move /lun_path_source /lun_path_destination (Move lun from source to
destination)
7. lun resize -f lun_path +|- new_size k|m|g|t (Resizes a lun by adding space (+) or
subtracting space (-) Note: a lun can only ever grow 10x it’s original size)
8. lun map /vol/vol1/lun1 igroup_name (Maps lun1 to the igroup_name)
9. lun alignment show (MUST BE DONE IN PRIV SET DIAG MODE. Shows which luns
are aligned and which are not)
Fiber FCP

1. fcadmin config -t taget 0a (Changes adapter from initiator to target)

2. fcadmin config (lists adapter state)
3. fcadmin start (Start the FCP service)
4. fcadmin stop (Stop the FCP service)
5. fcp show adapters (Displays adapter type, status, FC Nodename, FC Portname and
slot number)
6. fcp nodename (Displays fiber channel nodename)
7. fcp show initiators (Show fiber channel initiators)
8. fcp wwpn-alias set alias_name (Set a fiber channel alias name for the controller)
9. fcp wwpn-alias remove -a alias_name (Remove a fiber channel alias name for the
controller)
10. igroup show (Displays initiator groups with WWN’s)

iSCSI

1. iscsi start (Start the iscsi service)

2. iscsi stop (Stop the iscsi server)
3. iscsi status (Show whether iscsi server is running or not running)
4. iscsi interface show (Show which interfaces are enabled or disabled for iscsi)
5. iscsi interface enable interface_name (Enable an interface for iscsi)
6. iscsi interface disableinterface_name (Disable an interface for iscsi)
7. iscsi nodename (Display the controllers iscsi nodename)
8. igroup show (Displays iSCSI initiators)
9. igroup create -i -t vmware sqlcluster_igroup (Creates an Initiator Group called
sqlcluster_igroup with OS type vmware)
10. igroup add sqlcluster_igroup iqn.1991-05.com.microsoft:sqlcluster1.vmlab.local
(Assigns the following iscsi initiator to the sqlcluster_igroup. This can also be FCP addresses)

Cifs

1. cifs setup (cifs setup wizard)

2. cifs terminate (terminate the cifs service)
3. cifs restart (restarts cifs)
4. cifs shares (displays cifs shares)
5. cifs status (show status of cifs)
6. cifs lookup SID|name (Either displays the SID if you type in the name or name if you
type in the SID)
7. cifs sessions (Show you current cifs sessions)
8. cifs sessions -s username (Shows the current session for a user)
9. cifs broadbast -v volume_name “message” (Broadcast a message to all users
connected to volume_name)
10. cifs shares -add share_name /vol/volume_name/qtree_name (Create a cifs share on
a specific volume or qtree)
 11. cifs shares -delete share_name (Deletes a share name)
12. cifs shares share_name (Displays full path and permissions of the share)
13. cifs access share_name -g user_rights (Grants specific user rights to the share)
14. cifs access share_name user_name permission (Grants a specific permission to a
user for a share. Permissions = Full Control, Change, Read, No Access)
15. cifs domain info (Lists information about the filers connected Windows Domain)
16. cifs testdc ip_address (Test a specific Windows Domain Controller for connectivity)
17. cifs prefdc (Displays configured preferred Windows Domain Controllers)
18. cifs prefdc add domain address_list (Adds a preferred dc for a specific domain i.e. cifs
prefdc add netapplab.local 10.10.10.1)
19. cifs prefdc delete domain (Delete a preferred Windows Domain Controllers)
20. cifs gpresult (Displays which Windows Group Policies apply to this filer)
21. cifs gpupdate (Forces an update of Windows Group Policy)
22. cifs top (Performance data for cifs. cifs.per_client_stats.enable option must be on to
use this feature)
23. vscan on (Turns virus scanning on)
24. vscan off (Turns virus scanning off)
25. vscan reset (Resets virus scanning)

NFS

1. nfs setup (Runs the NFS setup wizard)

2. /etc/export (Enter in your export information here and save the file. Then proceed with
exportfs -a to update memory buffer)
3. exportfs (Displays current exports)
4. exportfs -p path (Adds exports to the /etc/exports file)
5. exportfs -uav (Unexports all current exports)
6. exportfs -u path (Unexports a specific export from memory)
7. exportfs -z path (Unexports a specific export and also removes it from /etc/exports)
8. exportfs -a (Updates memory buffer with contents in /etc/exports)
9. nfsstat -d (Displays NFS statistics)

HTTP Admin

1. options httpd.admin.enable on (Turns on http web admin, na_admin)

2. options httpd.admin.access host=x.x.x.x,x.x.x.x (Allows admin access for specific
hosts separated by a comma)

SIS (Deduplication)

1. sis status (Show SIS status)

2. sis config (Show SIS config)
3. sis on /vol/vol1 (Turn on deduplication on vol1)
4. sis config -s mon-fri@23 /vol/vol1 (Configure deduplication to run every monday –
Friday at 11pm on vol1)
5. sis start -s /vol/vol1 (Run deduplication manually on vol1)
 6. sis status -l /vol/vol1 (Display deduplication status on vol1)
7. df -s vol1 (View space savings with deduplication)
8. sis stop /vol/vol1 (Stop deduplication on vol1)
9. sis off /vol/vol1 (Disables deduplication on vol1)

User Accounts

1. useradmin user add user_name -g group_name (Adds a user to a group)

2. useradmin user list (Lists current users)
3. useradmin user list user_name (List specific user information)
4. useradmin group list (Lists current groups)
5. useradmin group delete group_name (Deletes a specific group name)
6. useradmin group modify group_name -g new_group_name (Modify group name)
7. useradmin user delete user_name (Delete a specific user)
8. useradmin user modify user_name -g group_name (Adds a user to a group)
9. useradmin domain user add user_name -g group_name (Adds a Windows Domain
user to a local group)
10. useradmin domain user list -g group_name (List Windows Domain users in a specific
group)

DNS

1. dns flush (Flushes the DNS cache)

2. /etc/resolv.conf (edit this file to change your dns servers)

NDMPD

1. ndmpd status (check status)

2. ndmpd on|off (turns ndmpd on or off)
3. ndmpd version (displays version information)
4. ndmpd version 4 (set ndmpd version to 4)
5. options ndmpd (Display ndmpd options)
6. Reading and Writing Files (Deduplication)

1. rdfile path/file (Reads a file)

2. wrfile path/file (Writes to a file. Warning this method overwrites the file. Make sure
you copy out original contents if you wish to keep it. If you haven’t used this before try on the
simulator.)
3. wrfile -a path/file (Writes to a file by appending the changes)

Logging

1. /etc/messages (All logging is for the system is stored here)

VIF

1. vif status (Displays the status of VIF interfaces)

2. vif create lacp vif0 ip e0a,e0b,e0c,e0d (Create a vif interface named VIF0 using lacp
and a load balancing method of IP, bundled with interface e0a, e0b, e0c, e0d)
3. vif add vif0 e0a (Adds a down interface into an existing VIF)
4. vif destroy vif0 (deletes a VIF interface)

Network

1. vlan create vif0 10 (create a vlan on interface vif0. The interface will be vifo-10)
2. vlan delete vif0 10 (deletes the vlan interface vif0-10)
3. ifconfig vif0-10 x.x.x.x netmask x.x.x.x partner vif0-10 (Sets IP information on the
interface named vif0-10 with a partner interface of vif0-10)
4. route add default 192.168.1.1 1 (Adds a default route of 192.168.1.1 with metric 1)

Performance

1. sysstat -x 1 (displays per second statistics for CPU, iSCSI, FCP, CIFS, NFS, Disk
Util, etc)
2. sysstat -m 1 (displays per second statistics for each CPU)
3. sysstat -M 1 (MUST BE DONE IN PRIV SET DIAG MODE. Displays per second
statictics for CPU’s, Kahuna, WAFL, etc)
4. statit b (MUST BE DONE IN PRIV SET DIAG MODE. Starts a performance snapshot)
5. statit e (MUST BE DONE IN PRIV SET DIAG MODE. Stops a performance snapshot
and displays the stats on screen. TIP: Turn on logging in your terminal program before
running this command)

Roles and Responsibilities in NetApp Storage Admin

Roles and Responsibilities in NetApp Storage Admin
Select some important points
 We are doing remote support.
 Checking the storage critical Events.
 Controlling & Monitoring Network Interface.
 Checking the status of aggregate and volume usage using DFM.
 Checking the ticketing tool and mails.
 Configuring and troubleshooting SnapMirror Environment.
 Performing Daily health check to monitor the usage of LUN, Aggregate and volume
utilization.
 Configuring H drive for the users in the environment.
 Restoring the data using snap restore and CIFS shares.
 Dealing with permissions (Adding/removing the security groups to the shares) for share
folders in CIFS.
 Configuring and troubleshooting SnapVault Environment.
 Performed DR test for the environment.
 Snapshot, lunclone, flexclone management.
 Setting up and troubleshooting V-Filer Environment.
 Lun management (LUN creation, LUN snapshots, Manual and automatic igroup management,
LUN restore) using Snapdrive.
 Setting up and troubleshooting NFS, CIFS, and SAN (FC and ISCSI) Environment.
 Configuring windows ISCSI Boot LUN for the environment.
 Ontap OS upgrade from 7.3.3 to 8.0 7 mode.
 Storage remediation like HBA driver and firmware upgrade.
 Adding disk shelf to the existing storage for standalone and High availability controllers.
(involved in ontap upgrade documents team )
 Assigning LUN’s (FC and ISCSI) to distributed server in various environments.
 Resolving the hardware issues in co-ordination with Netapp.
 Managing the reports using operations manager.
 Working with qtree’s for efficient storage utilization for the users.
 Performing Deduplication for the volumes.
 Volume resize, aggregate disk add and lun resize
 Alias, zoning configuration for the servers connected in FC environment in brocade switches.
 Able to create/Expand aggregate, volume, Qtree for NAS environments, LUN’s, Igroups for
SAN environments and also reclamation the LUN’s and SAN ports if any (De-commissioning
projects).

Product/Source Port Protocol Target Direction

SnapDrive dfm
integration 8088 http DFM server bi-directional
SnapDrive dfm
integration - secure 8488 https DFM server bi-directional
snapdrive
webservice 4094 http filer/vfiler bi-directional
snapdrive
webservice - secure 4095 https filer/vfiler bi-directional
Snapdrive
autosupport 25 TCP SMTP server one way
Snapdrive iscsi 3260 TCP filer/vfiler bi-directional
Snapdrive netbios
RPC 137 TCP filer/vfiler bi-directional
138 TCP filer/vfiler bi-directional
139 TCP filer/vfiler bi-directional
1512 TCP filer/vfiler bi-directional
Snapmanager for
SQL 808 TCP SQL server bi-directional
Snapmanager for
Exchange 808 TCP SQL server bi-directional
 OSSV-ndmp 10000 TCP DFM server bi-directional
OSSV-snapvault 10566 TCP filer/vfiler bi-directional
Snapvault-ndmp 10000 TCP DFM server bi-directional
Snapvault-traffic 10566 TCP filer/vfiler bi-directional
Snapmirror Source 10566 TCP filer/vfiler bi-directional
"""" 10569 TCP filer/vfiler bi-directional
Snapmirror
Destination 10565 TCP filer/vfiler bi-directional
"""" 10567 TCP filer/vfiler bi-directional
"""" 10568 TCP filer/vfiler bi-directional
SMVI 8043 TCP filer/vfiler bi-directional

1. Its license futures in NetApp.

2. Flexclone is used for testing purpose.
3. Flexclone need volume snapshot, using that snapshot we can clone that to new
volume.
4. FlexClone volumes always exist in the same aggregate as parent volumes.
5. Clone is in writable copy and without using a lot of disk space. After split the clone
that time only clone will take space from the Aggregate.
Commands :

To Create new clone

fas3070> vol clone create old_vol_name –b new_volume_name snapshot_name

To view clone status

fas3070> vol status new_volume_name

To start a clone split:

fas3070> vol clone split start volname

To stop a clone split:

fas3070> vol clone split stop

To check the status of a clone split:

fas3070> vol clone split status [volname]

To estimate the time of completion:

fas3070> vol clone split estimate [volname]

Description vol copy Ndmp copy Dump/restore
Uses Snapshot Yes Yes, but snapshot No
taken by ndmp is
deleted after copy is
completed
Requires rsh access Yes No No

Destination needs to be Yes No Uses tape drive as

restricted destination
Requirements Similar Trad to Trad and Flex Source and destination Source could be
Type of Volume to Flex copy only can be of either flex /
Trad Vols
Vol size requirement Destination volume No limitation on n/a
size should be equal or destination vol size
more capacity
Directory level copy No Yes Yes
possible