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..."
- 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."
Collecting a support bundle, or directly looking at collected log "ocum-error.log", will have the following entry:
"ERROR [oncommand] [collection-completion-0] [c.n.d.i.m.MccFabricConfigDiscoveryHandler] MetroCluster monitoring failed for <MCC-CLUSTER>"
2017-11-24 14:03:14,638 ERROR [oncommand] [reconcile-0] [(incremental@14:03:05.700)] [c.n.dfm.collector.OcieJmsListener] Error during MetroCluster component monitoring : Could not execute JDBC batch update
com.netapp.dfm.ontap.outbound.zapi.OcumMonitoringFailedException: Could not execute JDBC batch update
Caused by: org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
Caused by: java.sql.BatchUpdateException: Duplicate entry '200000108670aec0' for key 'Bridge_wwn_UQ'
Caused by: java.sql.SQLIntegrityConstraintViolationException: Duplicate entry '200000108670aec0' for key 'Bridge_wwn_UQ'