Skip to main content
NetApp Knowledge Base

MetroCluster IP performance issues

  1. Last updated
  2. Save as PDF
Views:
141
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9
  • Cisco Switches

Issue

  • A latency increase is observed on a MetroCluster IP
  • Clients encounter performance issues
  • Congestion is reported on the MetroCluster IP back-end network:

Example:

Mon Aug 21 14:19:30 +0200 [ClusterA-01: mccip_mirror_congestion_mgr_p: mcc.network.congestion:notice]: Network congestion detected. Action taken: Increased ic_timeout to 2000 msec.

  • CPs exceed the threshold, causing a cp too long:
Example:

Mon Aug 21 15:29:17 +0200 [ClusterA-01: wafl_exempt13: wafl.cp.toolong:error]: Aggregate aggr0 experienced a long CP.

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.