Administrator Guide

3 In the File System view, select SMB Shares.
4 In the SMB Shares panel, select an SMB share and click Edit Settings.
The Edit SMB Share Settings dialog box opens.
5 Click Advanced.
6 Select or clear the Enable branch cache checkbox.
7
Click Apply > OK.
For more information about branch cache conguration, refer to the technet article located at http://technet.microsoft.com/en-us/
library/hh848392.aspx.
Accessing an SMB Share Using UNIX or Linux
Mount the SMB share from a UNIX or Linux operating system using one of the following commands:
# mount -t smbfs -o user_name=user_name,password=password//client_vip_or_name/smb_share_name/
local_folder
# smbmount //client_vip_or_name/smb_share_name/local_folder -o user_name=user_name
Managing NFS Exports
Network File System (NFS) exports provide an eective way of sharing les across a UNIX or Linux network with authorized clients. After
creating NFS exports, NFS clients then need to mount each NFS export. The
FluidFS cluster fully supports NFS protocol version 3 and all
requirements of NFS protocol versions 4.0 and 4.1.
• Supported NFSv4 features:
– File and byte-range locking
NOTE
: Starting with FluidFS v6, if the multitenancy feature is enabled, NAS administrators can congure NFSv4 to
switch from mandatory to advisory byte-range locks at the tenant level using the CLI.
– Kerberos v5 security using an AD server
– AUTH_SYS legacy weak authentication
– UID translation using an LDAP server (UNIX or AD) or a NIS server
– UTF-8 le and directory names
• Unsupported NFSv4 features:
– Delegation of le locks to clients
– Full interoperability between NFSv3 and NFSv4 (for example, conict resolution for locks from clients using dierent protocols)
– Antivirus scanning and result caching
– LIPKEY and SPKM-3 security (not mandatory in NFSv4.1)
– Kerberos UNIX server
NFS v4 Implementation
Before implementing NFSv4, note the following, and refer to the respective documentation for your NFSv4 clients:
• User and Group identication — NFSv4 users and groups are identied by a <name>@<domain> string (rather than the traditional
UID/GID numbers). The NFSv4 server (FluidFS) and clients must be congured to use the same external Network Information Service
(NIS) or LDAP domain, which ensures consistent <UID/GID>-<name> mapping of identities. If the string does not map to a domain
object, it defaults to the nobody identity.
• Protection mode— Congure the NAS volume with UNIX security style to allow NFSv4 ACLs. NFSv4 ACLs are supported, but POSIX
ACLs are not.
• Interoperability —
FluidFS Administration
433