Skip to main content
NetApp Knowledge Base

High latency from cluster interconnect caused by faulty SFPs

Views:
110
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:

Applies to

ONTAP 9

Issue

  • Users reported high latency on NetApp volume. 
  • Qos stats report latency from Cluster interconnect.

cluster1::> qos statistics volume latency show -iterations 100
Workload        ID      Latency     Network    Cluster    Data      Disk     QoS       NVRAM   
--------------- ------ --------    --------   --------   --------  -------- -------- ----------
-total-                2320.45ms   109.00us   2320.02ms  327.00us  32.00us    0ms        0ms       
vdisk_vol1      111    2214.05ms   135.00us   2213.22ms  603.00us  89.00us    0ms        0ms      
vol2            1234   2701.12ms   238.00us   2700.56ms  191.00us  133.00us   0ms        0ms  

  • Depending on the type of SFP failure, this may not always trigger an EMS event
  • The EMS log may report the following error:

Mon Nov 21 08:31:41 +0900 [ST-BNC-5708N2: vifmgr: callhome.clus.net.degraded:alert]: Call home for CLUSTER NETWORK DEGRADED: Large MTU Packet Loss - Ping failures detected between cluster-02_clus2 ( xxx.xxx.xx.xx ) on Node2 and cluster-01_clus2 ( xxx.xxx.xxx.xxx ) on Node1

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.
  • Was this article helpful?