cannot create NFS Datastore

[sri_asr]

# esxcfg-nas -a -o 199.200.192.104 -s /vol/vmtst_01 test

Connecting to NAS volume: test

Unable to connect to NAS volume test: NFS Error: Unable to Mount filesystem: I/O error

# rpcinfo -p 199.200.192.104

program vers proto port

100003 3 tcp 2049 nfs

100003 2 tcp 2049 nfs

100003 3 udp 2049 nfs

100003 2 udp 2049 nfs

# vmkping 199.200.192.104

PING 199.200.192.104 (199.200.192.104): 56 data bytes

64 bytes from 199.200.192.104: icmp_seq=0 ttl=254 time=0.290 ms

64 bytes from 199.200.192.104: icmp_seq=1 ttl=254 time=0.324 ms

How do I debug or obtain VMkernel logs to get more info about the cause of this error

[patrickds]

have you configured the firewall on your ESX to allow NFS traffic?

[sri_asr]

Yes it is enabled

# service --status-all | grep nfs

Enabled services: nfsClient CIMSLP ntpClient nisClient VCB CIMHttpsServer sshClient vpxHeartbeats LicenseClient sshServer

ACCEPT udp -- anywhere anywhere udp dpt:nfs

ACCEPT tcp -- anywhere anywhere tcp dpt:nfs

My understanding is that the NFSdaemon is not necessary, just the nfsclient is needed to talk to a NAS filer.

# service nfs status

rpc.mountd is stopped

nfsd is stopped

[dtux101]

Did you present the share with appropriate permissions for both the COS and vmkernel IPs on the filer?

[langadi]

Do you see any error in vmkernel log file ?

# pwd

/var/log

# cat vmkernel| grep NFS

Nov 13 16:44:08 esxnode1 vmkernel: 0:23:49:45.983 cpu5:1072)WARNING: NFS: 960: Connect failed for client 0xb6139f8 sock 184679448: No route to host

Nov 13 16:44:15 esxnode1 vmkernel: 0:23:49:52.984 cpu5:1072)WARNING: NFS: 960: Connect failed for client 0xb6139f8 sock 184679448: No route to host

Nov 13 16:44:22 esxnode1 vmkernel: 0:23:49:59.985 cpu5:1072)WARNING: NFS: 960: Connect failed for client 0xb6139f8 sock 184679448: No route to host

Please upload.

-langadi

[Karunakar]

Please do a vmkping to the nfs server, and also are you able to mount the nfs share from cos.

this will isolate where the issue exactly is.

-karunakar

[Texiwill]

Hello,

Please note that you do not need to enable nfsClient within the esxcfg-firewall command for an NFS datastore to work. This is not necessarily unless you want to mount nfs to the COS only.

vmkernel show no route to host, so can you vmkping the NFS server, which you can. So it is either a badly configured NFS Server or a firewall issue outside ESX. THere are no firewalls on vmkernel ports.

Also, look at the logs on your NFS server for any errors. Remember the NFS server must speak NFS v3 over TCP and you must set 'no_root_squash' on the mount points.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

[sri_asr]

Can't still connect to the NFS Datastore, it says "Unable to connect to NAS volume NFS: NFS Error: Unable to Mount filesystem: I/O error"

I have allowed the VMkernel IPs to have root access on the filer and I can do vmkping to the filer

VMKernel logs show the below:

Nov 13 10:33:28 csesxt01 vmkernel: 0:00:32:57.759 cpu2:1037)WARNING: NFS: 931: MOUNT RPC failed with RPC status 9 (RPC program version mismatch) trying to mo

unt Server (199.200.192.104) Path (/vol/vmtst_01)

#

1. The filer has NFS ver 2 and Ver 3 enabled on it and on both UDP and TCP so should I assume that ESX will attempt to talk only on NFS ver3?

2. Where do we set the 'no_root_squash'. Is it on the NetApp filer ?

Please let me know if how to do additional debugging to get more info?

[kjb007]

Check the qtree security for the volume you want to enable on the filer.

-KjB