Subscribe
Accepted Solution

vSphere ESXi 5.5 to Clustered Data Ontap 8.3 SVM unable to connect NFS server

It is tempting easy to create new SVM in Clustered Data Ontap, hence I am quickly trying to test datastores for vSphere 5.5 under cDOT 8.3RC1.

 

This is what I got so far:

 a SVM "bgs_nfs_vmw2" created by the wizard of the built-in System Manager

a volume "bgs_nfs_vmw2_ds1_snp3" created by the wizard "Provision Storage for VMware"

an export-policy, created by the wizard

and a LIF

 

The NFS is enabled and running:

bgsstg2::vserver nfs> show
Vserver: bgs_nfs_vmw2

        General Access:  true
                    v3:  enabled
                  v4.0:  enabled
                   4.1:  disabled
                   UDP:  enabled
                   TCP:  enabled
  Default Windows User:  -
 Default Windows Group:  -

 

bgsstg2::> vserver nfs status
The NFS server is running on Vserver "bgs_nfs_vmw2".

 

The network is there:

bgsstg2: network interface show
bgs_nfs_vmw2
            bgs_nfs_vmw2_v053_n1
                         up/up    10.0.53.61/24      bgsstg2-n1    e0c-53  true

 

The export-policy matches to the ESXi-host 10.0.53.23 and is attached to the volume "bgs_nfs_vmw2_ds1_snp3":

bgsstg2::vserver export-policy> rule show

bgs_nfs_vmw2 bgs_nfs_vmw2_ds1_snp3_policy 1 nfs 10.0.53.23 sys

 

Now on the ESXi:
~ # ping 10.0.53.61 (the SVM)
PING 10.0.53.61 (10.0.53.61): 56 data bytes
64 bytes from 10.0.53.61: icmp_seq=0 ttl=255 time=0.252 ms
64 bytes from 10.0.53.61: icmp_seq=1 ttl=255 time=0.218 ms

I'm also able to netcat:
~ # nc 10.0.53.61 111 < /dev/null; echo $?
0 -> meaning: service answer on port 111

but still:
~ # esxcfg-nas -a -o 10.0.53.61 -s /bgs_nfs_vmw2_ds1_snp3 bgs_nfs_vmw2_ds1_snp3
 
returns: unable to connect to NFS server
 
Seems a part of the puzzle is missing - but which? Any ideas?
 
thx

Re: vSphere ESXi 5.5 to Clustered Data Ontap 8.3 SVM unable to connect NFS server

after hours of reading and testing I finally set up another NFS-SVM by commandline - with this SVM it worked, so I compared the two...

it looks like the System Manager wizard took the entries for the DNS servers and created with those also a NIS record - deleting the NIS entry - and now my clients can connect to the SVM "bgs_nfs_vmw2"