MetroCluster monitoring failed in Unified Manager 7.2 with Reason: An internal error has occurred during MetroCluster component refresh post re-cabling at switch ports

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 224

Visibility:: Public

Votes:: 0

Category:: oncommand-unified-manager

Specialty:: om

Last Updated:

Applies to

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

Issue

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 entry:

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

2018-11-13 00:28:06,697 ERROR [oncommand] [collection-completion-0] [c.n.d.i.m.MetroClusterRefreshCollectionCompletionListener] MetroCluster monitoring failed for MCC_CLUSTER_NAME at 00:28:06. 2018-11-13 00:28:07,646 ERROR [oncommand] [reconcile-2] [MCC_CLUSTER_NAME(incremental@00:28:05.083)] [c.n.dfm.collector.OcieJmsListener] Error during MetroCluster component monitoring : expected one element but was: <[2b:2], [2d:2]>