[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3656
  • Last Modified:

vmware esxi 5.5 connection to NFS

Hi!

I have trouble connectiong esxi 5.5 host (part of vsphere - essential) to NFS hosted on a fedora 20 linux host

I opened the firewall on esxi for correct subnet
I can vmkping the host from esxi
nc -z connection succeeds


vmk log from esxi:

2014-01-31T07:18:57.471Z cpu47:34081)NFS: 157: Command: (mount) Server: (yyy) IP: (x.x.x.89) Path: (/home/first-backup/kt-vcenter) Label: (backup-datastore-onClone) Options: (None)

2014-01-31T07:18:57.471Z cpu47:34081)StorageApdHandler: 698: APD Handle 32aa8fb2-26b1028f Created with lock[StorageApd0x41124f]

2014-01-31T07:18:57.482Z cpu47:34081)NFS: 1236: NFS FSINFO failed with NFS status 70 (Stale file handle) on Server (yyy) Path (/home/first-backup/kt-vcenter)

2014-01-31T07:18:57.482Z cpu47:34081)StorageApdHandler: 745: Freeing APD Handle [32aa8fb2-26b1028f]

2014-01-31T07:18:57.482Z cpu47:34081)StorageApdHandler: 808: APD Handle freed!
2014-01-31T07:18:57.482Z cpu47:34081)NFS: 218: NFS mount yyyy:/home/first-backup/kt-vcenter status: Unable to query remote mount point's attributes


the /etc/exports file on the server yyyy includes the line
/home/first-backup/kt-vcenter QQQQ (rw,sync,no_subtree_check)


QQQQ is ip of the esxi host (the hostname of the esxi is not yet in the dns). I can ping the ip of the esxi from fedora server

What else can I check?
(the esxi host is a the moment the only host in vsphere).


Thanks for help,
0
DamjanDemsar
Asked:
DamjanDemsar
  • 10
  • 6
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Do you have a VMKernel port group?

What version of NFS is supported on your Linux box?

only v3.0 is supported by VMware vSphere.
0
 
DamjanDemsarAuthor Commented:
vmkernel port group - probably not how do I set it up?

If I see correctly the linux box supports NFS v3.0 and v4.0
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
Cyber Threats to Small Businesses (Part 2)

The evolving cybersecurity landscape presents SMBs with a host of new threats to their clients, their data, and their bottom line. In part 2 of this blog series, learn three quick processes Webroot’s CISO, Gary Hayslip, recommends to help small businesses beat modern threats.

 
DamjanDemsarAuthor Commented:
Hmm,

I created the vmkernel port group, tried again, same error
Then I thought, that it be a problem with IPs, since the vmkernel port group has a new ip... I tried to allow that vmkernel port group ip on linux server nfs settings, but now I got an error that mount request was denied.

original error is Unable to query remote mount point's attributes

I also tried adding no_root_squash permission in linux NFS settings, and it does not help
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
mount request denied.

do you have the IP Address added to the export.
0
 
DamjanDemsarAuthor Commented:
yes, that happend when I chaned the IP in the /etc/exports from esxi host IP to the vmkernel port group IP... do I need them both in the export file?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You need the IP Address which is talking NFS, which is the VMKernel Portgroup.
0
 
DamjanDemsarAuthor Commented:
I added permissions for both IPs and still the Unable to query remote point's permissions error is reported. The mount request denied is reported only when I use the vmkernel port group IP only.

if I check the linux server log I get:
Jan 31 12:24:36 YYYY rpc.mountd[13386]: authenticated mount request from QQQQ:746 for /home/first-backup/kt-vcenter (/home/first-backup/kt-vcenter)

QQQQ is the managemnt network IP from esxi
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
make sure the IP addresses can be resolved to names.

add to local host table on linux machine if needed.

also check the /var/log/vmkernel.log on ESXi.
0
 
DamjanDemsarAuthor Commented:
Hmmmm...

If I understand correctly the log from linux server, esxi tries to connect and is correctly authenticated

how to resolve the vmkernel IP   - the same name as the esxi host ip (management network IP)? - there was no place to put another name in esxi for vkernel port group ip

the unable to query mount point's attributes error is from vmkernel.log and it is always the same as in my original post

the first error is
2014-01-31T11:45:15.185Z cpu24:34081)NFS: 1236: NFS FSINFO failed with NFS status 70 (Stale file handle) on Server (YYYY) Path (/home/first-backup/kt-vcenter)
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
on the linux server in the hosts file

xxx.xxx.xxx.xxx management IP Host name of server
xxx.xxx.xxx.xxx IP Address of VMKernel and another name
0
 
DamjanDemsarAuthor Commented:
Sure... done

no effect.


and the hostname for vmkernel ip could not helo, since the esxi does not know it.
0
 
Paul SolovyovskyCommented:
have you enabled no_root_squash?  Essentially allow root access for read/write without authentication?

What type of hardware is the NFS mount on?
0
 
DamjanDemsarAuthor Commented:
Yes I tried it with and without no_root_squash.
The server itself is an older linux server (I do not need performance, since this will be a datastore for backups), but the data itself is on a fibrechannel connected infortrend enclosure.

The server has already NFS connections to other linux servers (as a NFS server, not client).
0
 
DamjanDemsarAuthor Commented:
Hmm... still not working

NFS server logs say that esxi is trying to connect using Management network IP, not VMkernel IP.

VMkernel has empty routing table...

is it possible to convince esxi to use the VMkernel?
0
 
DamjanDemsarAuthor Commented:
the problem was with the nfs server (even if it worked for other servers, it did not work for esxi. Update and reboot helped)
0
 
DamjanDemsarAuthor Commented:
The question was pointed in the wrong direction... I thought the problem was the NFS client - that is VMware esxi, but the problem resolved itself after a scheduled update and reboot of NFS server (even if it worked ok with other non VMware NFS clients)
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 10
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now