NFS mount requests sent to LIFs on a specific a node time out, and the node's EMS frequently shows dns.server.timed.out:error

Last updated

Jan 29, 2025
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 93

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: nas

Last Updated:: 1/29/2025, 2:10:52 PM

Applies to

ONTAP 9
NFS
DNS

Issue

Some NFS mount requests are sent to LIF(s) hosted on a specific ONTAP node, but then the mount requests time out
Packet trace shows
- ONTAP replies to NFSv4 mount requests with NFS4ERR_DELAY
- ONTAP does not reply to NFSv3 mount requests or sends NFS3ERR_JUKEBOX
EMS logs on the symptomatic ONTAP node show that around the same date that the NFS mount time outs started happening, DNS time outs started happening frequently.
- ```
[node-1: mgwd: dns.server.timed.out:error]: DNS server 160.200.200.30 did not respond to vserver = svm1 within timeout interval.
```

check-access says that export policy rules allow the affected client host to mount NFS

::*> check-access -vserver svm1 -volume vol1  -client-ip 172.20.60.40 -authentication-method sys -protocol nfs3 -access-type read-write
  (vserver export-policy check-access)
                                Policy       Policy     Rule             Security
Path                 Policy     Owner        Owner Type Index Access     Style
-------------------- ---------- ---------    ---------- ---- ---------- ----------
/                    default    svm1_vol0    volume     1002 read       unix
/vol1                default    vol1         volume     1002 read-write unix
2 entries were displayed.