VMware Cloud Community
josegerez
Contributor
Contributor

Can't browse Windows NFS Datastore trouhg Virtual Center

Hi,

We have an W2K + SFU 3.5 for serving a NFS Datastore contaning templates & ISOs for our VMware infrastructure. I think our config is correct because we can browse the DS if we connect directly to ESX servers (via VI Client or Web Access), but if we try to browse the DS after connecting to Virtual Center (via VC Client or Web Access) we can't see anything. There are no errors, only a blank DS.

Any ideas?

Thans in advance,

Jose

Reply
0 Kudos
12 Replies
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose,

Have you copied /etc/passwd and /etc/group files onto the the SFU Server?

Most of this erros with SFU Server are about permisions .

rgds,

J.

El blog de la Virtualizacion en Español

josemariagonzalez.es

Reply
0 Kudos
josegerez
Contributor
Contributor

Yes, I do. Actually I can browse the DS if I connect (using VI Client or web access) directly to ESX server. The problem only appears connecting to VC.

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose,

That´s kind of wired alright.

Can you map the NFS datastore within VC and attached VC & SFU Server logs to see what´s going on when mapping the NFS LUN?

Rgds,

J.

-


El Blog de Virtualizacion en Español

Reply
0 Kudos
josegerez
Contributor
Contributor

Yes, these are. But there are no useful info about the nfs DS.

I've attached only the latest lines of each file

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose,

Apologies for the delay in getting back to you on this.

Attached below is a nfssvr.log extract of my environment.

I get "mount, read, create, write" access from the ESX servers to the NFS LUN something that I have seen different from your log. Could it be something doggy going on with your WSU server?

rgds,

J.

-


El Blog de Virtualizacion en Español

http://josemariagonzalez.es

Microsoft Server For NFS Activity Log

-


DATE TIME TASK RESULT ADDRESS DESCRIPTION...

-


07-14-2007 22:43:23 MOUNT SUCCESS 192.168.147.132 C:\ESX

07-14-2007 22:54:14 MOUNT SUCCESS 192.168.147.133 C:\ESX

07-14-2007 22:59:06 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:06 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:23 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:24 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\.lck-01a5a10000000000

07-14-2007 22:59:24 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\.lck-01a5a10000000000

07-14-2007 22:59:24 DELETE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:24 DELETE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\.lck-01a5a10000000000

07-14-2007 22:59:25 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:25 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:25 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmxf

07-14-2007 22:59:25 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmxf

07-14-2007 22:59:25 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:25 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:26 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmsd

07-14-2007 22:59:26 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:26 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:26 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:26 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmxf

07-14-2007 22:59:27 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:27 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:27 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:27 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:27 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:27 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmxf

07-14-2007 22:59:27 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:28 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:28 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:29 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:29 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:29 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:29 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:43 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:43 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:43 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:43 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:43 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:43 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\vmware.log

07-14-2007 22:59:43 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\vmware.log

07-14-2007 22:59:44 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:44 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:44 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:44 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:45 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1-33fd624d.vswp

07-14-2007 22:59:45 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:45 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:46 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:46 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:46 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\.lck-0c5e370000000000

07-14-2007 22:59:46 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\.lck-0c5e370000000000

07-14-2007 22:59:46 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:46 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.vmx

07-14-2007 22:59:47 CREATE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.nvram

07-14-2007 22:59:47 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\.lck-0c5e370000000000

07-14-2007 22:59:49 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 22:59:50 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1.vmdk

07-14-2007 23:00:02 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\.lck-0c5e370000000000

07-14-2007 23:00:08 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\w3k_demo1.nvram

07-14-2007 23:00:10 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\w3k_demo1\vmware.log

07-14-2007 23:00:23 WRITE SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\.lck-0c5e370000000000

07-14-2007 23:00:56 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1-flat.vmdk

07-14-2007 23:00:56 READ SUCCESS 192.168.147.133 \DosDevices\C:\ESX\W3k_demo1_1\W3k_demo1-flat.vmdk

Reply
0 Kudos
josegerez
Contributor
Contributor

I also get these events (see below), but only if the access directly to ESX server. If we connect to VC, there are no events (as you can see in previous posts).

I think there might be a permissions problem but I don't understand why. I believe that VC uses the root user of each ESX servr to access the nfs D, so if it works connecting to ESX server directl, why it didn't connecting to VC?

-


DATE TIME TASK RESULT ADDRESS DESCRIPTION...

-


10-03-2008 10:35:44 MOUNT SUCCESS 172.17.7.179 D:\Tecnico\Plantillas VMware ESX

10-03-2008 10:36:12 MOUNT SUCCESS 172.17.7.178 D:\Tecnico\Plantillas VMware ESX

10-03-2008 10:36:41 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\Win2003R2-x64-ENT-ENG-512MB-20GB.vmx

10-03-2008 10:36:41 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\Win2003R2-x64-ENT-ENG-512MB-20GB.vmdk

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\Win2003R2-x64-ENT-ENG-512MB-20GB.nvram

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\Win2003R2-x64-ENT-ENG-512MB-20GB.nvra

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware.log

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware.lo

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware.lo

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-2.log

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-2.lo

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-1.log

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-1.lo

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-1.lo

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-3.log

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-3.lo

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-3.lo

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-4.log

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-4.lo

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-4.lo

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\vmware-4.lo

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\.lck-0362610600000000

10-03-2008 10:36:42 WRITE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\.lck-036261060000000

10-03-2008 10:36:42 DELETE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\Win2003R2-x64-ENT-ENG-512MB-20GB.vmdk

10-03-2008 10:36:42 DELETE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\.lck-0362610600000000

10-03-2008 10:36:42 CREATE SUCCESS 172.17.7.179 \DosDevices\D:\Tecnico\Plantillas VMware ESX\Win2003R2-x64-ENT-ENG-512MB-20GB\.vmBigFileTest0

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose,

I think you answered yourself ;). There must be a permission problem.

Have you done your user mappings within WSU ? See snapshot attached

You have to map your VC windows user administrator with the user root

I hope that fix your problem

rgds,

J.

-


El Blog de Virtualizacion en Español

http://josemariagonzalez.es

Reply
0 Kudos
josegerez
Contributor
Contributor

Yes, I do. As I said, it's working if I connect directly to ESX as root (view attached images).

So, what user is VC using to browse the ESX? I thought it was root, but if connecting to ESX server using root it works, VC must use anoter account.

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose

As far as I know, VirtualCenter access NFS datastores using the user ID (uid) and group ID (gid) for

root.

Do you have your VC & WUS services on the same server?

rgds,

J.

-


El Blog de Virtualizacion en Español

http://josemariagonzalez.es

Reply
0 Kudos
josegerez
Contributor
Contributor

> As far as I know, VirtualCenter access NFS datastores using the user ID (uid) and group ID (gid) for

> root.

I also thought that.

> Do you have your VC & WUS services on the same server?

No. VC is running virtual on our cluster and WUS is on a physical server. The ISOs DS what I'm trying to access via NFS is also being shared via CIFS to the Windows world

Reply
0 Kudos
jose_maria_gonz
Virtuoso
Virtuoso

Hi Jose

Sorry that I cannot help you further with this. It appears to me that you could have a config problem with Windows Services for Unix.

I have similar environment as yours and it is working fine. The only problem I found wih mine at the begging was SFU. if you don´t get the user mapping right you would get access issues like I did.

But once I got the user mapping right it worked like a charm.

Please can I suggest you have a look at the following URL just to make sure you have installed SFU in the right way?

Good luck.

-


El Blog de Virtualizacion en Español

josegerez
Contributor
Contributor

OK, thanks for your assistance, José Mª.

Muchas gracias.

Reply
0 Kudos