Skip to main content
NetApp Knowledge Base

MetroCluster monitoring failed in ActiveIQ Unified Manager with Reason: An internal error has occurred during MetroCluster component refresh due to hex values to the "Reason for Last Reboot" field

Views:
1,151
Visibility:
Public
Votes:
3
Category:
oncommand-unified-manager
Specialty:
om
Last Updated:

    

Applies to

  • Active IQ Unified Manager 9.6+
  • Oncommand Unified Manager 6.x/7.x/9.x
  • Metrocluster

Issue

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

MetroCluster monitoring failed in ActiveIQ Unified Manager

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

MetroCluster monitoring failed in ActiveIQ Unified Manager

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 <MetroCluster-CLUSTER>"

ERROR [oncommand] [reconcile-1] [affhosmc.chkd.net(incremental@13:58:23.999)] [c.n.dfm.collector.OcieJmsListener] Error during MetroCluster component monitoring : com.ctc.wstx.exc.WstxIOException: Invalid UTF-8 middle byte 0xb (at char #34185, byte #31999)

ocumserver.log
ERROR [oncommand] [reconcile-2] [QSCPS040(incremental@00:22:34.950)] [c.n.dfm.collector.OcieJmsListener] Error during MetroCluster component monitoring : MetroCluster component monitoring failed. Zapi execution failed XML processing error during ZAPI call storage-bridge-get-iter to QSCPS040: Invalid UTF-8 middle byte 0xb (at char #34126, byte #31999)
com.netapp.dfm.ontap.outbound.zapi.OcumMonitoringFailedException: MetroCluster component monitoring failed. Zapi execution failed XML processing error during ZAPI call storage-bridge-get-iter to <metrocluster name>: Invalid UTF-8 middle byte 0xb (at char #34126, byte #31999)

 

 

This will show up in autosupports or output for the 'Reason for last reboot' for the bridge in the storage-bridge-view.

Critical Hardware Error Detected0xED 0x
or
Critical Software Error Detected0xED 0xB 

You can log into AIQ and pull up the cluster by name,serial or system id.

  1. Click on AutoSupport on the left side of the page
  2. Select the node from the drop down.
  3. Click on a weekly autosupport.
  4. Check the storage-bridge-view.xml
  5. Review the 'Reason for last reboot' to confirm.

 

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.