Skip to main content
NetApp Knowledge Base

Long CPs reported on MetroCluster IP nodes

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

Applies to

  • MetroCluster IP
  • ONTAP 9
  • Layer-2 Intermediate network

Issue

  • Clients report latency on applications
  • Long CPs are logged
Example:

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

  • The long CPs have a long P2A_FLUSH phase

Example:

 2026-01-03T00:30:27Z ...    [2:0]   CRUISE_6:  CP toolong:  aggr1 [9591880] CP_P2_FLUSH          129675ms

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.