Skip to main content
NetApp Knowledge Base

Scheduled Metrocluster check run fails due to API call

  1. Last updated
  2. Save as PDF
Views:
6
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • Metrocluster
  • Metrocluster API calls
  • MetroCluster Check Job Schedule

Issue

  • The default setup is to have one site of the MetroCluster run the periodic check at 15 minutes after the hour and the second site at 47 minutes after the hour.
  • If another Metrocluster operation is already in progress, the scheduled Metrocluster check will fail like below:
mcc.check.failed: The MetroCluster (tm) check job has failed to complete all checks for the system in cluster <cluster>.
  • Metrocluster operation history does not show the failed Metrocluster check.
  • No other Metrocluster operations show up in the history at the time of the failure.

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.