#Trouble communicating with Network Interfaces for NFS

1 messages · Page 1 of 1 (latest)

thorny knot
#

Greetings,

I've created a new SVM just for NFS. Configured a new LIF for it, let's say with the IP 192.168.40.54. It's on the default IPSpace, along with the SVM. I've also created a test volume to try the NFS. I added an export rule for this volume that permits the entire subnet 192.168.40.0/22 to read and write to this volume and added it to the junction path of this volume. I also edited the default rule to permit the subnet 0.0.0.0/0 to read (unix) the volumes, this is applied to the root junction path.
Unfortunately, when I try to showmount the IP of the NFS lif, I get nothing. In fact, I can't even ping the 192.168.40.54 IP, despite my test machine being in the same subnet (192.168.40.0/22), so no firewall between them.

Am I doing something wrong on the netapp side or is this just a network problem I need to solve?

Thank you immensely for your help, this server has been very helpful to me.

winter temple
#

Did you use yes GUI or cli to create this svm?

What service policy is attached to the data lif?

Is the switch properly configured?

So many questions….

thorny knot
#

Sorry for the vague problem. It was a network problem, not netapp. I did not properly configure the switch to pass the vlan that the svm was using. I've now solved and can finally see the nfs volumes.