Skip to main content
NetApp Stage KB

MetroCluster monitoring failed in Unified Manager 7.2 with Reason: An internal error has occurred during MetroCluster component refresh due to a failed poll with null exception

Last Updated:

Applies to

OnCommand Unified Manager (OCUM) 7.2 only
Any MetroCluster (MCC) version interoperable with OCUM 7.2


  • In "Configuration" menu, "Cluster Data Sources" tab, MCC clusters will have this message in Description column: "Monitoring failed..."

User-added image

  • Event created with title "Event: Cluster Monitoring Failed" and Trigger Condition: "Monitoring failed for cluster <MCC-CLUSTER>. Reason: An internal error has occurred during MetroCluster component refresh. Contact technical support."

User-added image

Collecting a support bundle, or directly looking at collected log "ocum-error.log", will have the following entries: 

"ERROR [oncommand] [collection-completion-0] [c.n.d.i.m.MccFabricConfigDiscoveryHandler] MetroCluster monitoring failed for <MCC-CLUSTER>"

ERROR [oncommand] [reconcile-0] [(baseline@13:16:25.716)] [c.n.dfm.collector.OcieJmsListener] Error during MetroCluster component monitoring : null
com.netapp.dfm.ontap.outbound.zapi.OcumMonitoringFailedException: null

Caused by: java.lang.NullPointerException: null



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.
Case Citation