Skip to main content
NetApp Knowledge Base

High Read Latency and aborts in the network for LUNs on AFF System

Last Updated:

Applies to

  • ONTAP 9.3 & above.
  • AFF System
  • Environments serving any SAN protocol (iSCSI / FCP / FCoE / NVMEoF)


  • Higher average latency may be observed for a specific LUN/Volume
    • Poor read latency will be reported by user/Application.
    • Potential aborts and timeouts may be seen in host logs.
    • Write latency, however, should not be affected
  • The latency breakdown from AIQUM or QOS shows all the delay from Delay-Center:Network.
cluster::> qos statistics volume latency show
Workload            ID    Latency    Network    Cluster       Data       Disk        QoS      NVRAM      Cloud
--------------- ------ ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
-total-              -     8.88ms     4.82ms     1.00us  1032.00us     4.02ms        0ms     2.00us        0ms
vm_lun_home1-..   4169   137.73ms   112.91ms     1.00us    22.93ms     1.89ms        0ms        0ms        0ms




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.
Scan to view the article on your device