Windows NFS & ESX?

[Grax]

Ok I was reading here: http://www.vmware.com/community/thread.jspa?messageID=643734&#643734

It's talking about setting up and NFS share on a windows 2003 r2 box. I've installed NFS and configured the share as he's stated.

However when I go into ESX Virtual Infrastructure Client and try to add the store, I get and error: "Error during the configuration of the host: Please make sure you have configured network for VMkernel".

Any ideas what is wrong? Or even better, how to fix it?

Thanks,

Andrew

[MayurPatel · Accepted solution]

Before you can attach the NFS share to the ESX3 host that you have configured on your Win2K3 you have to configure the VMKernel Networking which will allow you to connect to the NFS share.

The network services provided by the VMkernel (iSCSI, NFS, and VMotion) use a TCP/IP stack in the VMkernel.

Refer to http://www.vmware.com/pdf/vi3_301_201_server_config.pdf page 34 on how to configure the NFS VMKernel network switch.

[nitinsahi]

Hi Grax,

You need to configure VMkernel port as communicating with NAS you need VMkernel port in your Virtual switch.

You will need to provide the IP address and Gateway to the port as well.and then try to configure NFS share.

Thanks

Nitin

[nitinsahi]

Choose ESX Server ---> Configuration ---> Network ---> Add Networking ---> Out of 3 option choose VM Kernel -

---

> provide the IP Address ---> and hit finish after providing the vSwitch.

[Grax]

Ok I tried this and I was able to "mount" the store within VMware Virtual Infrastructure Client.

When I ssh into the ESX box, and goto /vmfs/volumes/, I can not do anything, create dir, see the directory, etc. I get "permission denied".

From within VI Client, when I browse the database, it doesn't show anything that I have in the directory.

Also when creating the NFS store, I have to use the IP address of the machine, it will not resolve the machine name. Any idea?

Any help would be appreciated.

Thanks,

Andrew

[Texiwill]

Hello,

Look at the NFS logs on the W2K3 host. Most likely you have a NFS Server configuration issue. At the very least you have permission problems on that server.

Best regards,

Edward

[Grax]

Where are the NFS logs stored? I looked in the event viewer and didn't see anything.

I checked the permission on the share amd gave everyone read/modify access. The NFS share is setup to allow root access and read/write access.

Andrew

[nitinsahi]

By default logs are stored in /opt/cassatt/log. This log will give you the clue to go ahead.

[MayurPatel]

Please give points for helpful answers

[Grax]

When I get a correct Answer I will. Thank very much, too bad I can't give negative points or you'd get some.

Andrew

[Grax]

Ok I have a /opt directory but there's nothing in it.

Any suggestions?

Andrew

[dsanders]

Are the ports enabled on the firewall?

In VC select the ESX host -> Configuration -> Security Profile -> Make sure NFS Client is checked.

[Texiwill]

Hello,

NFS client does not need to be open from the SC in order to use a vmkernel device.

The logs I mentioned should be on the NFS server. That depends entirely on what NFS server you are using on W2K3 and should be documented with the NFS server.

Are you trying to use SFU? Which NFS Server?

Generally if you see the NFS share under /vmfs/volumes then the vmkernel was able to mount the share successfully. However, if you can not write to the share, then it is a permission problem on the NFS Server and not the ESX server.

Best regards,

Edward

[Grax]

Ok the problem was a permissions setting on the W2K3 share.

I wasn't able to get it to work without giving "Anonynous Logon" the access it needed; this is under the security tab of the folder properties. This is different than giving anonymous access under the NFS tab of the folder properties.

Thanks for those who helped.

Andrew

[acmcnick]

We use NFS for VM's extensively, however not hosted on a Windows Machine. Anyway... You shouldn't need to allow anonymous ID on the share, you just need to make sure that is has a Full Access account on the share that maps to Root. ESX want to connect with root only. You will also need to map the NFS share to the ESX host with R/W and Root Permissions. Anonymous ID will work, we have one such share, but of course then any Linux style machine or NFS client can connect to it and since NFS doesn't lock the VMDK files for use that could be a security risk in the wrong environment. As far as the name resolution, make sure you set the DNS and Gateway setting properly for that Kernel connection, and always use FQDN where ever possible.

[Flan5ter]

'anonymous logon' needed to be added to the security tab of the directory being shared out on the Windows 2k3 box. Thank you Grax for sussing this out, I spent ages trying to work out what was missing.

Thanks

Flan5ter