NFS Storage and comms setup issue

[spi200]

All

Having problems connecting to an NFS store on three new ESX servers I have built. I get an error that the NFS can not be found.
We have a good SAN\NAS guy and he has done plenty of these in the past, but not with me - so I suspect I have a comms issue of some sort and not sure how to fault find it issue.
I am unable to pink the "Filer" where the NFS is located and they are on the same subnet. Here is what I have...

Vmnic0 Console at 192.168.57.99 connected at 100 Meg
Vmnic1 VMKernel at 192.168.66.50 connected at Gig
Vmnic5 NFS at 10.2.130.200 connected at gig

NFS Filer at 10.2.130.240

Using vmkping, I can ping my inteface 10.2.130.200 from the console, but can ping nothing else on that segment.
Ifconfig shows the inferface which are present, but show nothing bound to any nic other than vmnic0 (console) - not sure if this is right or not.
The comms guys says he can see my mac address on vmnic5, but can not tell much more and could not ping that interface from his router.

I am not familiar with any other tools other than above so please step out any suggestion so I can follow thru and provide more information.
I might resort to putting a laptop on the gig link and ensure its a good link - but that's next week.

Thanks

Dave

 

[Provogeek]

have you checked the firewall config?

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt SPOOOOON!!!!!
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[spi200]

Provogeek

I checked the firewall settings on hte ESX server against another server and looked fine, however the other servers and 3.02 and this new server is 3.5 so there may be slight differences in the setup.

Keep em comming



Dave

 

[Provogeek]

Run esxcfg-firewall -q nfsClient and tell me what you get back.


I have a feeling though that your issue is default gateway as you can only set one default gateway for VMKernel, and it more than likely is set to the 192.168 subnet, not the 10 subnet your NFS share is on.

Open your VI client, go tothe server in question, click on the Configuration tab, select DNS and Routing in the Software box. From there you will see the default gateways for Service Console and VMkernal. Click Properties in the upper right hand corner to edit this.

BTW, is this NFS share for the purpose of storing VM's? or are you trying to get a VM access to an NFS share?

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt SPOOOOON!!!!!
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[spi200]

Hi

Trying to create a store to store the VM's - this is just a development bed and there is no need to fibre. NFS has worked well for us in the past.
I have played around with the default gateways and pretty sure its OK.
Plugged a laptop into the patched cable this morning and got a connection at a gigabit but could ping nothing on the segment. Comms could see my Mac address on the switch and could see no errors but could not ping me from the switch.
They can not see a problem, so are going to put their own laptop on in a day or so. I was told today its a new switch, so I suspect its a config issue on their side.


Thanks Dave

 

[spi200]

Provogeek


I run that command and it returns

Service nfsClient is enabled.

Comms tested with there laptop and it appears to be fine from there side, still can not ping from my ESX servers to anything else on the segment.

Back to drawing board....



Dave

 

[spi200]

All

Thanks for the help, I have found the issue after much pain.

In the network settings there is an option to select a VLan Id (Optional) - I was putting an entry in there as per our standard Vlan names we use - seems like it did not like it as the moment I took it off I was able to ping and was able to setup my NFS storage. I had three servers that I was having issues with in one cluster and they are all good now.
I guess if you select a Vlan ID and comms are not using Vlan tagging then you can run into troubles.


Thanks Again

Dave