Skip to main content
NetApp Knowledge Base

Packet loss causing slowness and latency outside of ONTAP

Last Updated:

Applies to



  • Packet loss identified by multiple duplicate acknowledgements (at least #1, #2, and #3) along with (fast) retransmissions


Packet loss causing slowness

  • Application slowness and high i/o wait times, performance issues or higher latency are observed
  • Throughput may drop to Zero then recover.
  • If the loss is severe enough, the connection may be disconnected
  • ONTAP latency is low and utilization of CPU and disk is lower than normal or expected
  • Packet loss may be increasing in ONTAP 9.5 or higher

Example: Increasing Rexmit and OOORcv columns for from netstat -anceWCT

node 1:
Proto Recv-Q Send-Q Rexmit OOORcv  0-win Local Address                                 Foreign Address   
=-=-=-=-=-=Sat Aug 13 2022, 23:16:01 -0400   BSD-NETSTAT-ANCEWCT 6 lines
tcp4       0      0 6198853 112463181      0                                                             

=-=-=-=-=-=Sat Aug 20 2022, 23:26:09 -0400   BSD-NETSTAT-ANCEWCT 6 lines                      
tcp4       0      0 1304064 57461127      0                                                            

node 2:
=-=-=-=-=-=Sat Aug 13 2022, 23:15:27 -0400   BSD-NETSTAT-ANCEWCT 6 lines                    
tcp4       0     48 5768522 3592331      0                                           

=-=-=-=-=-=Sat Aug 20 2022, 23:25:03 -0400   BSD-NETSTAT-ANCEWCT 6 lines
tcp4       0     48 1366568 11947331      0                                          
  • ifstat has 0 errors on the port of the data LIF
  • event log show has no entries indicating CRCs or other local link degradation
  • Packet loss causes TCP to perform poorly, creating up to seconds of latency from the user or application end


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.