NFS mount 10.0.0.48:/ISOimages/ failed: Unable to connect to NFS server.

[scerazy]

ESX5i installed from scratch (updated or not, no difference)

Does not allow to add the Server 2008 R2 NFS R/O share

I have another ESX5i (installed in the same way, as well as ESX4.1), which connect to the SAME NFS share just fine (which means that it is NOT the shhare issue, but rather this very ESX

All physical hardware for each ESX are exactly the same

Anybody has any idea?

Call "HostDatastoreSystem.CreateNasDatastore" for object "datastoreSystem-4300" on vCenter Server "VC5" failed.
NFS mount 10.0.0.48:/ISOimages/ failed: Unable to connect to NFS server.

Thanks

Seb

[vmroyale]

Hello.

Is your networking the same on this host as it is on the hosts that work?

Is the upstream physical networking configured correctly?

Can you vmkping 10.0.0.48 from the ESXi Shell?

Good Luck!

Good Luck!

[scerazy]

Yes, yes, and yes. 2 out of 3 hosts have no problem, one does

sebuis

[vmroyale]

Did you account for this new host in the NFS server config? How is the NFS exports configured?

[scerazy]

Same as I always done with server 2003 & now 2008 R2

Windows config does not care about new host

Seb

[scerazy]

So I have an idea why it is wrong, but have no idea how to fix it

On working server gateway is assigned to vmk1 (VMkernel) interface

On non-working server gateway is assigned to vmk0 (management) interface

How to make vmk1 on server 10.0.0.52 (as per attached)

Thanks

Seb

edit:

Had to swap the IP addresses between Management Network & VMkernel network (this way the routing is "attached" to VMkernel & NFS mount worked as it should)

No idea where & why it got in the muddle in first place

edit2:

Had to redo this ESXi host (used console restore config option)

After that the same issue appeared. But this time it took 2 hours of moving IPs, changing network names in VC, as well as setting management network at console. EVENTUALLY IT "CAUGHT" and the routing stayed on VMkernel network

PURE MADNESS