By default, the maximum version supported is version 3, meaning that the server supports versions 2 and 3 by default. To change the maximum supported version to NFSv4, use the CLI command nfs-max-supported-version. By setting the maximum supported version to 4, you allow the storage server to support NFS versions 2, 3, and 4.
NFS statistics for the server are available for activity since the previous reboot, or since the point when the statistics were last reset.
Statistics for NFS requests received by the server are broken down by NFS version and procedure, and are shown (in 10-second time slices) on the NFS Statistics page (refer to the Server and Cluster Administration Guide for more information). The statistics can also be sampled and viewed on-demand using the nfs-stats CLI command.
The storage server (or cluster) stores metadata about the files, directories, migration paths, CIFS shares, NFS exports, user names, group names, log entries, mount points and so on for the virtual servers, file systems, and namespaces served by the server/cluster.
When interacting with another network device, the metadata transmitted to or received by the storage server/cluster must use a character encoding supported by the other network device. Typically, clients/devices using the SMB/SMB2 protocol (Windows) encode data in the UCS-2 character encoding, and clients/devices that use the NFS protocol encode data in the UTF-8 character encoding.
When using the FTP protocol to communicate with clients/devices, the storage server/cluster supports the UTF-8 character encoding for user names, passwords, and file/directory names.
NFS and NIS unicode support
Character sets supported by the NAS server to communicate with NFS clients and NIS servers include:
|Communicating with||Character encodings supported||Default character encoding|
|NFSv2 and NFSv3 clients||Latin-1, UTF-8, EUC-KR, EUC-JP, and EUC-CN||Latin-1|
|NIS servers||Latin-1 and UTF-8||Latin-1|
You can specify the character encoding to be used when communicating with NFS clients and/or NIS servers using the protocol-character-set command.
The NFS character set controls:
- File, directory, and export names to/from NFSv2 and NFSv3 clients.
- Symlinks to/from NFS clients.
The NIS character set controls:
- NIS user and group names.
- LDAP user and group names.
Character set encoding may not be set for:
- Namespace links.
- Namespace directories.
- Communication with NFSv4 clients.
When multi-tenancy is not enabled, the configured character encoding applies on a cluster-wide basis (all clients communicate with the server using the same encoding). When multi-tenancy is enabled, the character encoding is configured on a per-EVS basis, allowing the use of multiple character sets on the same NAS server/cluster.
To correctly display the characters during communication between the client and the NAS server, both the program used by the the client to communicate with the NAS server and the NAS server itself must be configured with the same character encoding and locale.
Changing the character set
By default, the storage server/cluster uses the ISO 8859-1 (Latin-1) character set when communicating with NFS clients and/or NIS servers. When NIS servers and NFS clients use different character sets, the administrator must specify which character set the NFS clients are using, and which character set the NIS servers are using. The protocol-character-set command allows an administrator to specify the character set to be used when communicating with NFS clients and/or NIS servers.
Refer to the Command Line Reference for more information on the protocol-character-set command.
Enabling and disabling file services
You can enable and disable the required file services for the system in the NAS Manager.
Navigate to Enable File Services page.to display the
The following table describes the fields on this page:
Select the check box for each service you want to enable. apply Click to apply the selections.
Select or deselect one or more services.
- With the exception of FTP, all of these services require a valid license.
- If ReadCache is selected or deselected, a reboot may be required. If so, follow the on-screen instructions to restart the server.