Skip to main content
NetApp Knowledge Base

MetroCluster IP multiple remote disk failures due to latency

Views:
29
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9
  • Broadcom BES-53248 IP switches

Issue

  • Multiple remote drives fail due to latency:

[cl01-n01: disk_latency_monitor: shm.threshold.highIOLatency:error]: Disk 0v.i1.1L99 exceeds the average IO latency threshold and will be recommended for failure.

  • ISL ports on the Broadcom switches show excessive discards.
  • The output of command show fiber-ports optical-transceiver all on the Broadcom switches shows low input power on the ISL port SFPs.
                                                 Output   Input
Port    Physical Port/  Temp  Voltage  Current   Power    Power     TX     LOS
        Lane Number     [C]   [Volt]     [mA]    [dBm]    [dBm]     Fault
------  --------------  ----  -------  -------   -------  -------   -----  ---
0/9     0/9-Lane1       35.2    3.320      6.7    -1.302   -1.941   No     No
0/10    0/10-Lane1      35.2    3.296      6.7    -1.248   -1.884   No     No
0/13    0/13-Lane1      35.3    3.329     31.1    -2.439   -4.208   No     No
0/14    0/14-Lane1      33.2    3.357     34.3    -2.342   -4.590   No     No

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.