Clustered Data ONTAP 8.3
This guide intends to provide a set of troubleshooting procedures to assist one with identifying the cause of an NFS mount hang or access denied response.
This guide uses troubleshooting features added in clustered Data ONTAP 8.3.1 and thus intended only for clustered Data ONTAP 8.3.1 and later use.
It is recommended that all command-line input and resulting console output be recorded in a text file for later review. Providing this in a technical support case notes may significantly improve time to resolution.
Throughout this guide, commands with diagnostic and advances privilege levels are used. Exercise all with due caution when running these commands as erroneous inputs might have unexpected consequences.
Common Causes of Access Denied or Hang
There are many causes of NFS mounts that fail with access denied or continually re-attempt and appear to hang. The following list describes the most common causes that have been observed. The following section will provide troubleshooting strategies that will enable you to quickly identify and remediate the cause of the issue.
- Export rule does not exist for the client's IP or hostname
- Mount attempts prior to provisioning the name services including netgroup or DNS entries results in negative entry in access cache
- DNS resolution of client IP to name does not match netgroup or the hostname specified in the export rule
- Missing or incorrect DNS search domains
- DNS, NIS or LDAP server timeouts
- Missing DNS PTR record
- Hostname specified in export rules is not fully qualified and end with a dot (.), also known as a rooted name
- DNS, NIS or LDAP servers are unreachable due to network connectivity – firewall policies or route configurations
- Lack of
netgroup.byhostmaps in NIS or LDAP
- Netgroups with hostnames that will not resolve in DNS
- Netgroup hostname case sensitivity for local files and some remote services including NIS and LDAP
- NFSv4 mounts or NFSv3 auth=null require user mapping only if there is an NTFS volume in the path