bowulf
Enthusiast
Enthusiast

ESXCFG-NAS problem in 3.5

Jump to solution

I am trying to connect to our default NFS store that all our 3.0.2 hosts are connected. I have enabled the firewall for nfsClient and verified network connectivity to the NFS Server. I however get the following error:

  1. esxcfg-nas -a GlobalStorage -o 172.20.1.87 -s gs Error performing operation: SysinfoException: Node (<null>) ; Status(bad00c2)= Module not found; Message= Unable to Get Instance List

Is it a problem on the NFS Server or within the ESX host? I have tried allowing all outgoing firewall communication with no success either.

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

Try "vmkload_mod nfsclient"

Looks like somehow the nfs module isn't loaded.

Also the standard syntax for esxcfg-nas add is:

esxcfg-nas -a -o <host> -s <share> <name>

View solution in original post

0 Kudos
5 Replies
ssahadev2
Enthusiast
Enthusiast

Is vmkernel port created for NFS network?

what is the output of vmkping 172.20.1.87

0 Kudos
bowulf
Enthusiast
Enthusiast

Yes, the vmkernel is created and is within the same subnet. The default gateway was inserted, and vmkping did respond from the nfshost.

vmkping 172.20.1.87

PING 172.20.1.87 (172.20.1.87): 56 data bytes

64 bytes from 172.20.1.87: icmp_seq=0 ttl=128 time=0.457 ms

64 bytes from 172.20.1.87: icmp_seq=1 ttl=128 time=0.197 ms

0 Kudos
ssahadev2
Enthusiast
Enthusiast

What happens when VI client is used for adding NFS Datastore?

0 Kudos
admin
Immortal
Immortal

Try "vmkload_mod nfsclient"

Looks like somehow the nfs module isn't loaded.

Also the standard syntax for esxcfg-nas add is:

esxcfg-nas -a -o <host> -s <share> <name>

View solution in original post

0 Kudos
bowulf
Enthusiast
Enthusiast

What happens when VI client is used for adding NFS Datastore?

I have a problem with my LUN presentation that the Microsoft Cluster RDM exposed for Physical-Virtual clusters prevents adding any new storage via the GUI. The CLI is the only way it works with the default settings. VMware is aware of the issue (timeout setting too low), and will eventually solve the issue.

>> Try "vmkload_mod nfsclient"

It did solve my issue. The attachment to the NFS NAS worked after doing it. I checked out my other 3 VI3.5 boxes, and each of them failed in the same manner. After installing the nfsclient on each host, it worked.

0 Kudos