Skip to main content
NetApp Knowledge Base

NFS access denies though the new added export-policy rule includes the client IP

  1. Last updated
  2. Save as PDF
Views:
321
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • NFS

Issue

  • Specific nfs client fails to mount nfs volume through the new added expot-policy rule includes the corresponding client IP
  • The new added export-policy rule looks without any problems

Example:

vserver  policyname ruleindex protocol clientmatch  rorule rwrule superuser
-------- ---------- --------- -------- ------------ ------ ------ ---------
svm1     test123    1         nfs      192.168.90.73 any    any    any
svm1     test123    2         nfs      192.168.90.77  any  any    any
 
  • Error messages of "exports.hostname.notFound" can be observed in event log:
Example:
 
Tue Dec 20 14:57:34 +0800 [node1: mgwd: exports.hostname.notFound:info]: Hostname "192.168.90.77 " does not have a forward mapping for its corresponding IPv4 address in the configured name servers when evaluating the export-policy rule at index "2" in policy-id "30064771179" for Vserver "svm1".

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.