ONTAP Discussions
ONTAP Discussions
I have configured an ontap 9.11.1 with NFS, when creating the volume and presenting it, it always gives me a permissions error. I have configured the following per cli
vserver nfs modify -vserver vserver_name -v3 enabled
vserver nfs modify -vserver vserver_name -v4.0 enabled
vserver nfs modify -vserver vserver_name -v4.1 enabled
vserver nfs modify -vserver vserver_name -tcp enabled
vserver nfs modify -vserver vserver_name -udp enabled
vserver nfs modify -vserver vserver_name -mount-rootonly disabled
vserver nfs modify -vserver vserver_name -nfs-rootonly disabled
vserver nfs modify -vserver vserver_name -showmount enabled
vserver export-policy create -policyname all_nfs -vserver nfs
vserver export-policy rule create -policyname all_nfs -clientmatch 0.0.0.0/0 -rorule any -rwrule any -superuser any -protocol nfs,nsf3,nfs4
vserver export-policy rule show -vserver nfs -policyname all_nfs
volume modify -volume Testing -vserver nfs -policy all_nfs
I need to be able to mount the volume, but the strangest thing is that a volume \! as the picture shows and check and is the nfs_root SVM
Thanks for your help
Solved! See The Solution
Check this:
When using Windows NFS in Data ONTAP the following option should be set:
::> nfs server modify -vserver vservername -showmount enabled
::> nfs server modify -vserver vservername -v3-ms-dos-client enabled
::> nfs server modify -vserver vservername -enable-ejukebox false
::> nfs server modify -vserver vservername -v3-connection-drop disable
Mount failure with "Network Error - 53" on Native Windows NFS clients
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/Mount_failure_with_Network_Error_53_on_Native_Windows_NFS_clients
Window nfs is pretty much the worst nfs client there is. There are Few extra steps to perform in order to make it work with Microsoft. It doesn’t support anything higher than version 3. I don’t have the link handy but search the Netapp site for windows nfs
Check this:
When using Windows NFS in Data ONTAP the following option should be set:
::> nfs server modify -vserver vservername -showmount enabled
::> nfs server modify -vserver vservername -v3-ms-dos-client enabled
::> nfs server modify -vserver vservername -enable-ejukebox false
::> nfs server modify -vserver vservername -v3-connection-drop disable
Mount failure with "Network Error - 53" on Native Windows NFS clients
https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/Mount_failure_with_Network_Error_53_on_Native_Windows_NFS_clients
One common error is forgetting about the export permissions on your root volume (probably vserver_name_root). If you're trying to mount a junction path /Testing, make sure that / is also exported to your clients.