fkaltman
Contributor
Contributor

NFS storage won't connect over custom TCP/IP stack

I’m trying to build out a new vSphere 6 environment (DR site). All is going well except NFS storage. I have created a separate TCP/IP stack for NFS and associated the appropriate vmk port to it. I can reach the storage with the vmkping command.

vmkping ++netstack=NFS X.X.X.X –d –s 8972

When I try to mount the storage I get an error that the ESXi host could not reach the NFS server. I have double checked all settings and paths. I tried adding a static route from the ESXi host to the storage network but received an error stating that the route already existed under another stack (expected). The vmotion netstack operates without a problem and when I remove the vmk and add it back under the default TCP/IP stack, it mounts the storage successfully. Any ideas what I might be missing?

3 Replies
Nick_Andreev
Expert
Expert

What array are you connecting to? Did you allow root and read/write access to the volume you're exporting on the array side?

---
If you found my answers helpful please consider marking them as helpful or correct.
VCIX-DCV, VCIX-NV, VCAP-CMA | vExpert '16, '17, '18
Blog: http://niktips.wordpress.com | Twitter: @nick_andreev_au
0 Kudos
kpcongdon
Enthusiast
Enthusiast

Any luck figuring this out?  I'm experiencing the same issue.  I'm unable to mount my NFS storage when using a custom TCP stack, works as expected when using the default tcp/ip stack.

0 Kudos
ksimonsen
Contributor
Contributor

I just figured this out: https://kb.vmware.com/s/article/50112854

VMware Knowledge Base

It took me forever to find that KB article.