Skip to main content
NetApp Knowledge Base

MetroCluster high write latency due to ISL cabling distance mismatch

  1. Last updated
    Apr 18, 2024
  2. Save as PDF
Views:
123
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:
4/18/2024, 2:27:08 PM

Applies to

  • Fabric MetroCluster
  • ONTAP 9

Issue

Many mlm.excessive.TPlatency alerts are shown in the EMS log, similar to this: 
Mon Jan 01 01:00:00 XX [Cluster-01: slifc_intrd: mlm.excessive.TPlatency:notice]: Average latency of XXXXus on target portXXXXXXXXXXXXXXXX, has exceeded 250000us.

 

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.