Unable to add NFS share to the ESX host

[writehaseeb]

Hi,

I am running ESX 4.0 with vcenter server as VM. All is working fine. I have now attached a Seagate NAS 220 storage to the network.

The NAS is sitting on the same network as the ESX service console VLAN10 (I hope this is where it had to be).

I have enabled NFS service in the NAS server and the two default folders have NFS capabilities enable as well.

Now when I try to add the folder as NFS share to one of the ESX host it gives me an error:

Error during the configuration of the host: NFS error: Unbale to Mount filesystem: The mount

request was denied by the NFS server. Check that the export exists and that the client is permitted to

mount it.

Amy idea guys???

[AndreTheGiant]

Seems a problem on the NFS server.

Check if there are some ACLs, or if there is a specific configuration to enable no_root_squash option.

Andre

[writehaseeb]

I fixed the allowed IP range in the NAS, now the vcenter says that the server do not support NFS ver 3 over TCP.

I think my NAS do not support NFS ver 3 over TCP and I also checked the VMware hardware compatibility guide and it does not list

the seagate NAS as the certified HW. I will probably return this one and will get the Cisco NSS 322 4T one.

Thanks for your support.

[AndreTheGiant]

Also most of Buffalo and Iomega NAS are compatible.

I do not need your model, but in some case there are the sources of the OS (if is Linux based).

For example, for most WD NAS is possible compile the module with the right support.

But I do not suggest WD NAS cause are quite slower for this kind of purpose.

Andre

[anonim1]

I'm getting the same error with both a WD ShareSpace and a WD My Book World Edition II device. How can I go about compiling the needed modules to enable NFS Mount version 3 over TCP? Many thanks..

[DSTAVERT]

When you setup the WD NFS share, make sure that it is using what amounts to anonymous read and write access --NO authentication required. These types of devices usually have a Public folder that doesn't require any authentication. Try using the Public folder as the NFS share to present to ESXi. If that works use the permission settings for the Public folder to match your NFS share for ESXi.

Make sure that the spelling and capitalization of the share name is the same as displayed in the share setup on the NAS.

[writehaseeb]

Also make sure the storage is compatiable with the version of ESX/ESXi you are using. The Vendor I mean...else it wont work.

[writehaseeb]

Check here for Vendor compatability...

http://www.vmware.com/resources/compatibility/search.php?action=search&deviceCategory=san&productId=1&advancedORbasic=advanced&maxDisplayRows=50&key=&datePosted=-1&partnerId[]=-1&arrayTypeId[]=3&isSVA=0&rorre=0

[anonim1]

Thanks for the replies.. I was hoping for a response from AndreTheGiant, who stated "for most WD NAS is possible compile the module with the right support". I know my configuration is right, there are no issues with authentication or share names. I have root SSH access to the storage devices and wanted to know if it would be possible to upgrade the NFS mount version of the services.. AndreTheGiant made it sound like this was doable..

[DSTAVERT]

The source code for this type of device based on Linux or bsd will be available from the manufacturers website. You might need to create a I would be very surprised if the current version on your WD device needed to be replaced. Most of these devices only use NFS version 3 over TCP

Make sure you have the latest WD firmware. From the WD forums "make sure the NFS service is turned on. It is off by default"

You can try either of these while logged in to the WD device via SSH

rpcinfo -p | grep nfs

or

nfsstat -o all -234

If these utilities are available they will return some results showning the NFS version currently running. If they are available but don't support the options use the utility with the --help option.

[anonim1]

Both of the devices have the latest firmware. Neither of those utilities are available (running under root).. any other ideas to determine the NFS version?

[DSTAVERT]

Use

ps -ef | grep nfs

to verify nfs is running. It may also reveal any startup options. See if you can find how the NFS service is launched/configured.

On this device ?? /etc/inet.d

If you can locate the configuration file in /etc you may be able to find and modify the startup options.

Ask on the WD forums. Someone must have an answer.

[admin]

If you are trying to add the NFS share as a datastore you need to create a VMKernel port group. You cannot use Service Console port group to mount a NFS datastore. You can either mount the NFS datastore using UI or through the command

esxcfg-nas -a -o 'hostname' -s 'nfs_share' 'nfs_datastore_name'

Let me know if this helps.

~Sudhish

[anonim1]

Thanks, I've already created the VMKernel port. I'm really thinking my device does not support NFS mount version 3 over TCP. When I attempt to connect to the target from ESX (via GUI or shell), the following events are logged in /var/log/vmkernel:

NFS: 149: Command: (mount) Server:  (192.168.xxx.yyy) IP: (192.168.xxx.yyy) Path: (/nfs/myshare) Label:  (datastore-nas) Options: (None)
WARNING: NFS: 918: Server (192.168.xxx.yyy) does not support Mount Program (100005) Version (3) Protocol (TCP)
NFS: 171: NFS mount 192.168.xxx.yyy:/nfs/myshare status: The NFS server does not support MOUNT version 3 over TCP

[emashaal00]

Hey all I had the pleasure of add a WD ShareSpace drive to a customers esx environment. I ran into the same issues everyone else seems to. So I will give you my experience.

1. SSH to your esx host and tail your vmkernel tail -f /var/log/vmkernel
   
2. Create a vmkernel port with IP address and all
   
3. Make sure in the security profile of the esx host you allow nfs
   
4. Go to the GUI of the WD ShareSpace and allow use of SSH
   
5. Create a NFS share that you want to access
   
6. SSH to the WD ShareSpace
   
7. VI to /etc/exports and edit the entry for your share to show no_root_squash
   
8. From the SSH console of the WD ShareSpace tail -f /var/messages
   
9. On the WD ShareSpace allow IP addresses to NFS MAKE SURE THAT YOU ALLOW THE IP ADDRESS OF THE VMKERNEL not that of the host
   

now that you have both /var/log/vmkernel and /var/messages open you will be able to see why the error messages are comming up

im my case I put an allow (WD GUI allowed NFS address) on my esx host ip address while the one i needed was the vmkernel ip address

once this was done I created a new nfs datastore and added it successfully

one thing i noticed and have not resolved is that if I reboot the WD ShareSpace it removed the changes made to "no_root_squash" so everytime I reboot the WD I have to edit the /etc/exports with no_root_squash

Anyway the magic in troubleshooting this was in tailing the logs on both ESX and WD....

There is hope for WD ShareSpace!!!!!!