Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

Active IQ Unified Manager Discussions

Just getting started, could use some input


I'm new to netapp and azure so please, bear with me. I follow these instructions to get NetApp in my Azure cloud. I created a volume share using the oncommand cloud manager. However, when I try to mount it, I get these errors. I also followed NetApps guide but I clearly missed something when it comes to permissions. 


mount.nfs: timeout set for Tue Apr  3 01:09:30 2018

mount.nfs: trying text-based options 'rsize=1048576,wsize=1048576,hard,intr,timeo=600,retrans=2,vers=4,addr=,clientaddr='

mount.nfs: mount(2): Protocol not supported

mount.nfs: trying text-based options 'rsize=1048576,wsize=1048576,hard,intr,timeo=600,retrans=2,addr='

mount.nfs: prog 100003, trying vers=3, prot=6

mount.nfs: trying prog 100003 vers 3 prot TCP port 2049

mount.nfs: prog 100005, trying vers=3, prot=17

mount.nfs: trying prog 100005 vers 3 prot UDP port 635

mount.nfs: mount(2): Permission denied

mount.nfs: access denied by server while mounting


nfs-commons are on the client, I don't know where on the nfs server I would make changes. The command line for the netapp nfs server is foriegn to me. NFS ports are opened. 

I also ran on the client


showmount -e
Export list for
/myfileshare (everyone)
/ (everyone)


Any and all help is appreaciated. 





can you tell which mount command you are using on your (I suppose Linux) client?

It's probably something like 

# mount <-o <options> /<mount point> 

where mount point is an empty directory on your linux box.


The error message "Protocol not supported" indicates that the Mount Protocol version that you are using on the client 



is not enabled in ONTAP. I've attached a screenshot that shows that for me on my demo system, version 3 is enabled while version 4 and version 4.1 is disabled. 

If you want to use NFS version 4 (as shown in your mount options) , then this version needs to be enabled in ONTAP as well.


I hope this makes sense.





Hi! I am also facing similar issue, for the vserver I see the version 4 of nfs is enabled on my end though.

any other suggestion if still user is not able to mount the volume?


I solved the issue by setting security-style to unix

vol modify -vserver <vserver> -volume <volume> -security-style unix

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner