Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
NFS, CIFS, FC and iSCSI are separately licensed
If you do not have the license enabled, you will not be able to enable
the protocol on the SVM
NetApp NAS Implementation
NFS and CIFS are configured on a per SVM basis
NFS and CIFS are configured independently of each other
They can both be enabled on the same SVM
Each SVM appears as a separate storage system to clients
NFS Versions
NFS was invented by Sun Microsystems and is the standard NAS
protocol for Unix and Linux clients. It can also be accessed by VMware
ESXi, Windows and Mac clients
NFSv1: was only used for internal testing by Sun
NFS Versions
NFSv2: was standardized in 1989. It is a stateless protocol that supports only
32‐bit files with a maximum file size of 2 GB. Not supported on NetApp
NFSv3: was standardized in 1995. It is a stateless protocol with performance
improvements over NFSv2 and supports TCP and 64‐bit files. Files can be up
to 16 TB on NetApp Data ONTAP. Supports local UID and GID to authenticate
users and Kerberos. It retains widespread support and is enabled by default
on NetApp Data ONTAP systems
NFS Version Features
NFSv4: was standardized in 2003. Stateful protocol with same file size
capability as NFSv3. Has security enhancements including Windows
style ACLs, and end to end security. Disabled by default on NetApp
NFSv4.1: Stateful protocol that extends NFSv4 by adding sessions,
directory delegations, and Parallel NFS (pNFS) to provide scalability and
performance improvements on clustered storage systems. NFSv4.1 has
no dependencies on NFSv4 and is considered a separate protocol.
Disabled by default on NetApp
NFS Referrals
Referrals are supported in NFS v4 and v4.1
If a node receives an NFS request for data on a volume on another node, it
will refer the client to use a LIF on the node which hosts the volume
The client will now use a local path, avoiding extra traffic over the cluster
interconnect
Support for NFS referrals is not uniformly available on all NFSv4 clients. If the
feature is enabled and a client that does not support it receives a referral
from the server, the client cannot access the volume and experiences
failures. Do not enable referrals unless all your clients support it
NFS Referral Commands
pNFS can also direct a client to use a LIF on the local node that houses
the volume
If an administrator moves the volume to another node, pNFS will
redirect the client with no need to remount
With NFS Referrals, if the volume moves the client is not updated until
it unmounts and remounts the file system
NFS Referrals and pNFS are mutually exclusive
pNFS Commands
pNFS is enabled by default if NFSv4.1 is enabled
NFS v4 and v4.1 support Windows style NFS ACLs in addition to
standard UNIX permissions
ACLs are disabled by default
If you use local UNIX accounts (file) then the SVM trusts the end host
to authenticate the client
If the client matches an export policy rule and sends a UID which has
permissions in the SVM then they can access the directories and files
This is obviously a security risk
LDAP with Kerberos authentication is preferred
Kerberos is configured at the LIF level
NFS Configuration Steps
Enable the NFS protocol license on the SVM
Create an NFS server on the SVM
Configure export policies on the SVM
Configure the NFS server with the appropriate security and other
settings depending on the network and storage environment.