Skip to main content
NetApp Knowledge Base

How to troubleshoot NFS APD issues on VMware ESXi

Last Updated:

Applies to

  • ONTAP 9
  • VMware ESXi


  • An all paths down (APD) timer is started when there has been a 5 second period with no communcation on any given TCP stream
  • After 140 seconds of being in this state, the connection is considered lost and an APD timeout is reached
    • Possible errors seen in VMware logs include, but not limited to:

YYYY-MM-DD T00:26:51.504Z: [APDCorrelator] xxxxxxxxxxxxxus: [] Device or filesystem with identifier [xxxxxxxx-xxxxxxxx] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.

NFSLock: 608: Stop accessing fd 0x410011446d28  3
NFS: 133: Lost connection to the server mount point /vol/datastore, mounted as xxxxxxxxx-xxxxxxxx-0000-000000000000 (“datastore”)

StorageApdHandler: 248: APD Timer started for ident [xxxxxxxx-xxxxxxxx]
StorageApdHandler: 846: APD Start for ident [xxxxxxxx-xxxxxxxx]!
StorageApdHandler: 277: APD Timer killed for ident [xxxxxxxx-xxxxxxxx]
StorageApdHandler: 902: APD Exit


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.