Configuring export volumes

Viewing export volumes from the GUI

This section describes configuring your appliance to export volumes. Before configuring the appliance to export volumes, you must find what, if any, volumes are currently being exported. The examples used in this section contain the following configurations:

NFS server (filer.lan.company.com)
Linux client (client.lan.company.com)
Distributed NFS appliance (dnfs.appliance.company.com)

To check the server to see the volumes being exported on the client, complete the following steps.

Step	Action
1	From the Appliance Manager, select Setup tab > NFS > Exports.
2	View the existing configurations of exported and origin server volumes in the Configure Exported NFS Volumes table.

Viewing export volumes from a UNIX client

Many UNIX distributions include the showmount command. To view export volumes from a UNIX client, enter:

client [~] showmount -e filer.lan.company.com

The preceding command returns:

Export list for filer.lan.company.com: /vol/vol0/home (everyone) /vol/vol0 (everyone)

This shows that the filer (the origin server) is exporting two different volumes.

Again on the client, enter the following commands:

client [~] showmount -e dnfs.appliance

Export list for dnfs.appliance:

The preceding commands return:

Currently, the appliance is not exporting any volumes.

Configuring export volumes from the GUI

Continuing from the previous example, you can configure the appliance to export two volumes from the filer, the origin server.

To configure the appliance to export two volumes from the filer, complete the following steps.

Step	Action
1	Enable the NFS caching service by selecting Setup tab > NFS > General.
2	To configure a new volume, go to Setup tab > NFS > Exports and then click New Volume on the right side of the Configure Exported NFS volumes table. To edit an existing volume, locate the volume in the Configure Exported NFS Volumes table and click Edit.
3	Enter the basic options (these are mandatory). Enter the name of the volume to be exported on the appliance. Format: `/vol/doom` Enter the origin server and volume names. Format: `/vol/build`
4	Enter any advanced options that you want. These options include: Time before reverification of objects UID to use for requests with root UID Hosts allowed to mount this volume Hosts with read/write access to this volume Restrict access for this volume to read only Always use TCP to connect to origin server Cron style entries for scheduling a reverify
5	Click Commit Changes to have the changes take effect.

Configuring exports from the CLI

The config.nfs.exports option is used to create the mapping between volumes that you want the appliance to export and the actual volume on the origin NFS server.

To configure the export volume from the command line, enter

dnfs> set config.nfs.exports=\\

/vol/file filer.lan.company.com:/vol/vol0 anon=0,max-age=30

/vol/file/home filer.lan.company.com:/vol/vol0/home anon=0,max-age=100

\\

dnfs> set config.nfs.enable on

Configuring NFS mount points

To configure the export volume on the client, from the UNIX prompt

client [~] mount -o rw,bg,hard,intr,rsize=8192,wsize=8192

dnfs.appliance:/vol/file /t/dnfs.appliance/file

client [~] cd /t/dnfs.appliance/file

client [/t/dnfs.appliance/file]

To the client, this volume will look the same as /vol/vol0 on filer.lan.company.com. An exception is if there are writes directly to the origin server that bypass the cache in the period between two reverifications.

Status and statistics commands

This section presents some useful commands for working with statistics and status information.

NFS status

Use the following commands to display NFS statistics.

dnfs> show status.nfs.bw_savings

status.nfs.bw_savings = 76%

dnfs> nfsstat

usage: nfsstat <interval>

usage: nfsstat -h [ <hostname or ip address> ]

usage: nfsstat -l

usage: nfsstat -z

usage: nfsstat

Client statistics

To display all of the NFS statistics for a specific client, enter

dnfs> nfsstat -h client.lan.company.com

Appliance statistics

Statistics can be useful to determine if traffic is sent through the appliance as expected. To display a running tally of current operations, enter

dnfs> sysstat 1

CPU	.	ops/s	.	Net	kB/s	Disk	kB/s	BW savings/s
	tot	hit	miss	in	out	read	write
1%	0	0	0	0	0	84	132	0%
0%	0	0	0	0	0	0	0	0%
0%	0	0	0	0	0	0	0	0%

Option usage examples

A volume on an origin server can be used by many exports, as seen in the following example.

`dnfs> set config.nfs.exports\\`
`/vol/home-ro`	`filer1.lan.company.com:/vol/home ro`
`/vol/home-tcp`	`filer1.lan.company.com:/vol/home tcp`
`/vol/special`	`filer1.lan.company.com:/thunder ro,max-age=15`
/vol/hail	hail.lan.company.com/hail ro,max-age=4h
`/vol/lightening`	`lightening.lan.company.com:/ max-age=0,anon=0`
`/vol/fireball`	`fireball.lan.company.com:/ verify-sched=0 0 * * * *`
/vol/ice	`ice.lan.company.com:/ verify-sched=30 1 * * * 0`
`\\`

The following table shows the results of the preceding options.

Option	Result
`/vol/home-ro`	Exports /vol/home on filer1 read-only.
`/vol/home-tcp`	Exports /vol/home on filer1 as read/write, but upgrades all server requests to TCP.
`/vol/special`	Exports on filer1 as read-only, and the appliance serves hits on cached objects for 15 seconds before revalidating any of their attributes.
/vol/hail	Exports on hail as read-only, and the appliance serves hits on cached objects for four hours before revalidating any of their attributes.
`/vol/lightening`	Exports on lightening as trusting root on all clients, and the appliance serves hits on cached objects for 0 seconds before revalidating any of their attributes.
`/vol/fireball`	Objects are reverified on the first access after midnight daily.
/vol/ice	Objects are reverified after 1:30 a.m. on Sunday.