Skip to main content
NetApp Knowledge Base

ONTAP Select Cluster Unresponsive Due to Severe Backend Disk Latency

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • ONTAP Select High Avalability cluster
  • Cluster hosted on VMware ESXi

Issue

ONTAP Select cluster becomes unavailable. Nodes and cluster management LIF are not reachable by SSH or System Manager, virtual machines (VMs) are slow or unavailable.

  • Symptoms can include:
    • Node fails to boot and panic due to latency.
    • Partner node still serves data, but with severe latency.
    • System Manager becomes unavailable when the failed node tries to come online.
  • Example EMS messages:
[kernel:device.latency.threshold:notice]: The device latency in microseconds exceeded the threshold value for device "isp18" and the associated target device "/dev/da4". The threshold is "25000", execution latency is "5555955"

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.