After you have successfully tested NFS client access, you can perform additional NFS configuration or add SAN access. When protocol access is complete, you should protect the root volume of storage virtual machine (SVM). There are express guides, comprehensive guides, and technical reports to help you achieve these goals.
You can further configure NFS access using the following comprehensive guides and technical reports:
Describes how to configure and manage file access using NFS.
Serves as an NFSv3 and NFSv4 operational guide, and provides an overview of the ONTAP operating system with a focus on NFSv4.
Explains how to configure ONTAP for use with UNIX-based Kerberos version 5 (krb5) servers for NFS storage authentication and Windows Server Active Directory (AD) as the KDC and Lightweight Directory Access Protocol (LDAP) identity provider.
Describes the best practices that should be followed while implementing NFSv4 components on AIX, Linux, or Solaris clients attached to systems running ONTAP.
You can further configure networking features and name services using the following comprehensive guides and technical reports:
Describes how to configure and manage ONTAP networking.
Describes the implementation of ONTAP network configurations, and provides common network deployment scenarios and best practice recommendations.
Explains how to configure LDAP, NIS, DNS, and local file configuration for authentication purposes.
If you want to provide or modify SAN access to the new SVM, you can use any of the FC or iSCSI configuration express guides, which are available for multiple host operating systems.
After configuring protocols on the SVM, you should ensure that its root volume is protected:
Describes how to create a load-sharing mirror to protect the SVM root volume, which is a NetApp best practice for NAS-enabled SVMs. Also describes how to quickly recover from volume failures or losses by promoting the SVM root volume from a load-sharing mirror.