跳转到主内容

ActiveIQ Unified Manager 中的 MetroCluster 监控失败,原因:由于 " 上次重新启动的原因 " 字段具有十六进制值,因此在 MetroCluster 组件刷新期间发生内部错误

Views:
20
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager<a>MetroCluster</a><a>统一管理器</a><a>1005364</a>
Specialty:
om
Last Updated:

    

状态信息

适用场景

  • Active IQ Unified Manager 9.6及更高版本
  • OnCommand统一管理器6.x/7.x/9.x
  • MetroCluster

问题描述

  • "Configuration"(配置)菜单 的"Cluster Data Sources (集群数据源)选项卡中、MetroCluster集群的问题描述列将显示以下消息:"monitoring failed.."(监控失败..)

ActiveIQ Unified Manager中的MetroCluster监控失败

  • 已创建标题为"事件:集群监控失败"且触发条件为"集群<MetroCluster-CLUSTER>监控失败"的事件。原因:MetroCluster组件刷新期间发生内部错误。请联系技术支持。"

ActiveIQ Unified Manager中的MetroCluster监控失败

收集支持包或直接查看收集的日志ocum-error.log''将具有以下条目:

"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)

 

 

此消息将显示在autost-bridge视图中、并显示此网桥的"上次重新启动原因"。

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

您可以 [1] 按名称、串行或系统ID登录到AIQ并提取集群。

  1. 单击页面左侧的AutoSupport
  2. 从下拉列表中选择节点。
  3. 单击每周AutoSupport。
  4. 查看storage-bridge-view.xml
  5. 查看"上次重新启动的原因"进行确认。

 

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.