Skip to main content
NetApp Knowledge Base

High Cluster Interconnect Latency due to unstable link

Views:
210
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
CORE
Last Updated:

Applies to

  • FAS & AFF systems
  • ONTAP 9

Issue

  • Increased cluster interconnect latency

Example: qos statistics volume latency show show Cluster latency

cluster1::> qos statistics volume latency show -iterations 100
Workload        ID      Latency  Network  Cluster   Data     Disk     QoS       NVRAM      Cloud
--------------- ------ -------- -------- -------- -------- -------- -------- ---------- ----------
-total-                110.35ms    0ms   110.02ms 327.00us      0ms      0ms        0ms        0ms
vs1vol0         111    167.82ms    0ms   167.22ms 603.00us      0ms      0ms        0ms        0ms
vol1            1234   117.76ms    0ms   117.56ms 191.00us      0ms      0ms        0ms        0ms
  • Multiple CSM mismatch errors seen in EMS logs

Example:

[NODE1: server_common_RPC: csm.mismatchRemoteDevice:error]: CSM connection between source LIF 1001 and destination address 198.168.0.1 might not be optimal for session XXXXXXXXXXXXXXXX. The source is currently connected to InterfaceName(xxxxxxxxxxx) remote device and the destination is currently connected to - remote device.

 

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.