Adding an NFS export

Navigate to Home > File Services > NFS Exports to display the NFS Exports page.

Click add to display the Add Export page.

The following table describes the fields on the page:

Field/Item	Description
EVS/File System	Currently selected file system, to which the NFS Export will link.
Cluster Namespace	Currently selected cluster namespace, to which the NFS Export will link.
change / browse (depending on Web browser)	Enables the user to select a different file system or (on a cluster) a different cluster namespace.
Export Name	Name of the export.
Path / CNS Path	Path to the source directory for the export. To locate a source directory for the export, click the browse/change button.
Path Options	Determines the path options: Create path if it does not exist to create the path entered in the Path field (filesystems only). Allow this export to overlap other exports if nested NFS exports are allowed. Note: If the file system is mounted read-only, for example it is an object replication target, it is not possible to create a new directory. Select a path to an existing directory.
Show snapshots	Determines how to show snapshots: Show and Allow Access, to display and allow access to snapshots. Hide and Allow Access, to hide snapshots, but still allow access to the hidden snapshots. Hide and Disable Access, to hide and disallow access to snapshots.
Local Read Cache (file systems only)	Allows caching of files or cross file system links from the file system to which this export points: Cache all files. Allows caching of files and cross file system links in the file system of the export. Cross file system links are local links that point to a data file in a remote file system. The remote file system may be on a remote server or storage device. Cache cross-file system links. Allows only cross file system links to be cached Do not cache files. Do not allow read caching of files and cross file system links. Local read caching is not supported for NFSv4 clients.
Transfer to Object Replication Target (file systems only)	When a file system is recovered from a snapshot, one of the final steps is to import the NFS exports found in the snapshot representing the selected version of the file system. Only those NFS exports marked as transferable will be imported. Enable: NFS exports will be transferred to recovered file systems. Disable: NFS exports will not be transferred to recovered file systems. Use FS default: When the target file system is brought online, NFS exports will be transferred if Transfer Access Points During Object Replication option is enabled for the file system.
Access Configuration	IP addresses, host names, or the NIS netgroups of the clients who are allowed to access the NFS export (up to 5957 characters). If the system has been set up to work with a name server, you can enter the NIS netgroup to which the clients belong, or the client’s computer name rather than its IP address (not case sensitive). You can also specify the required flavors of NFS security in a colon-separated list using the option (sec=<list>). The supported flavors are: none - Connect as a null user sys - The traditional security flavor used by NFS, users are not authenticated by the server krb5 - Kerberos authentication krb5i - Kerberos authentication with per-messaging integrity krb5p - Kerberos authentication with per-message privacy For example: 10.1..(sec=sys:krb5:krb5i) See the mount-point-access-configuration man page for further information.

To add an export to a new EVS or file system, click change next to that line and make a selection from the Select a File System page.

Enter the Export Name through which clients will access the export.

Type the path to the directory being exported or click browse... to locate an existing directory.

Set Path Options as follows:

To create the path automatically when it does not already exist, fill the Create path if it does not exist check box.
Note: Automatically created directories will be owned by the root user and group (UID:0 / GID:0) and will be accessible to all users (that is, the permissions are set to rwxrwxrwx). It is recommended that such directories be created via CIFS or NFS, or that such directories are given the desired permissions explicitly after being created by this option.
To allow this export path to overlap other exports, fill the Allow this export path to overlap other exports check box.
This option is useful if you expect to set up future, nested exports. For example, suppose you export the root directory of a volume and make it available to managerial staff only. By selecting this option, you can later export subdirectories of the root directory and make each of them available to different groups of users.

If snapshots are present, make them visible to clients by selecting from the list:

Show and Allow Access, to display and allow access to snapshots.
Hide and Allow Access, to hide snapshots, but still allow access to the hidden snapshots.
Hide and Disable Access, to hide and disallow access to snapshots.

In order for this change to become effective on NFS clients, all NFS clients should unmount and then remount the export, or the administrator must run ʹ touch . ʹ from within the root directory of the export.

Select the Local Read Cache setting. To allow caching of files or cross file system links from the file system to which this export points, select one of the following:

Cache all files. Allows caching of files and cross file system links in the file system of the export. Cross file system links are local links that point to a data file in a remote file system. The remote file system may be on a remote server or storage device.
Cache cross-file system links. Allows only cross file system links to be cached.

Local read caching is not supported for NFSv4 clients.

Choose the Transfer to Object Replication Target option.

When a file system is recovered from a snapshot, one of the final steps is to import the NFS exports found in the snapshot representing the selected version of the file system. Only those NFS exports marked as transferable will be imported.

Use the list to specify one of the following:

Enable: NFS exports will be transferred to recovered file systems.
Disable: NFS exports will not be transferred to recovered file systems.
Use FS default: When the target file system is brought online, NFS exports will be transferred if Transfer Access Points During Object Replication option is enabled for the file system.

In the Access Configuration field, type the IP addresses, host names, or the NIS netgroups of the clients who are allowed to access the NFS export (up to 5,957 characters). If the system has been set up to work with a name server, you can enter the NIS netgroup to which the clients belong, or the client’s computer name rather than its IP address (not case sensitive). You can also specify the flavor of NFS security using the option (sec=<mode>). The table outlines what to type in this field.

What to Type	Means
Blank or *	All clients can access the export.
Specific address or name. Examples: 192.0.2.0, client.dept.example.com	Only clients with the specified names or addresses can access the export.
A range of addresses using Classless Inter-Domain Routing (CIDR) notation. Example: 192.0.2.0/24	Clients with addresses within the range can access the export.
Partial address or name using wildcards. Examples: *192.0.., .example.com**	Clients with matching names or addresses can access the export.

Click OK.