NFS config |
||
| NFS License | This window configures the filer for NFS service. To reload
the current settings from the filer, click the Reload Settings button. To view the changes
that you made, click the View Changes button. After you make a change, click the Save
Changes button to save the changes to the filer. NFS LicenseThe filer requires a software license to enable NFS service. The license is installed on the filer at the factory per your order, so the initial setup of your filer does not involve entering license codes. You need to enter license codes only if any of the following conditions applies:
Network Appliance provides you with the appropriate license codes when shipping you the software upgrade kit or when giving you instructions for obtaining the software upgrade over the Internet. After you enter the license, the filer immediately starts NFS service. After you select Not Licensed from the pull-down menu, the filer immediately stops NFS service. Cluster considerationsIn a cluster, NFS must either be licensed on both filers or not licensed on both filers for takeover to occur properly. NFS EnabledStarts and stops NFS service immediately. The filer, however, does
not add the nfs on command or the nfs off command to the /etc/rc
file. If you want the setting of this field to remain in effect after the filer reboots,
remember to add the nfs on command or Cluster considerationsIn a cluster, NFS must either be enabled on both filers or not enabled on both filers for takeover to occur properly. PCNFS EnabledThe pcnfsd authentication daemon enables you to use (PC)NFS to access a filer. (PC)NFS refers to NFS client implementations for DOS, Windows, Windows NT, OS/2, and Macintosh operating systems. Using (PC)NFS, such systems can mount a directory or volume from the filer after the user provides the UNIX user name and password for authentication. Without the pcnfsd daemon running on the filer, you must set up another host to provide the authentication. The filer supports (PC)NFS version 2 except for printer support. With (PC)NFS version 2, clients can use the filer for authentication, including obtaining group IDs (GIDs) and group names through the /etc/group file or the corresponding group.byname NIS map. To use (PC)NFS to access a filer, the client system must run (PC)NFS and must be configured to mount the filer. Also, the pcnfsd daemon can run only if NFS is licensed for your filer. Cluster considerationsIn a cluster, (PC)NFS must either be enabled on both filers or not enabled on both filers for takeover to occur properly. PCNFS umaskSets the umask for (PC)NFS users. The default umask is 022, which means that users can read and write their own files, but group members and others can only read the files. WebNFS EnableWebNFS enables the filer to respond to requests for file transfers over the Web using NFS rather than HTTP made through a browser that has WebNFS client support. The headers of WebNFS requests have URLs that start with "nfs://". With WebNFS, the filer can transfer files much faster than with HTTP because WebNFS can transfer several files (including graphics files) with only one TCP connection. HTTP (in version 1.1) requires a separate connection for each file. The filer does not need an HTTP license to respond to WebNFS requests. WebNFS access does not use the mount command to enable access to a subtree, and does not consider UID/GID mapping. Requests are restricted as follows:
WebNFS Root Directory EnableYou can specify a public directory (known as the root directory) for WebNFS access. All NFS lookups are done relative to the root directory. If WebNFS is enabled on the filer, all WebNFS clients can access files and directories under the root directory. WebNFS Root DirectorySpecifies the root directory for WebNFS access. For the directory to take effect, you must select Yes for the WebNFS Root Directory Enable field. Per-client StatisticsSpecifies whether the filer collects and displays NFS statistics for each NFS client. Cluster considerationsIn a cluster, the Per-client statistics field must have the same value on both filers for takeover to occur properly. NFS over TCPSpecifies whether the filer supports NFS over TCP. Enable this option if a client has problems using NFS over UDP. NFS Version 3Specifies whether the filer supports NFS Version 3. Disable this option if a client has problems using NFS Version 3 and that client cannot be configured to use NFS Version 2. Cluster considerationsIn a cluster, the NFS Version 3 field must have the same value on both filers for takeover to occur properly. Report Maximum of 2GBLimits to 2 GB the response the filer gives to requests regarding total space, free space, or available space. This option is necessary for some NFS clients to calculate the amount of free space accurately. Without this option, a file system with more than 2 GB of free disk space might appear to be full to the client that initiates the "file system statistics" request. Cluster considerationsIn a cluster, the Report Maximum of 2GB field must have the same value on both filers for takeover to occur properly. |