跳转到主内容

为什么在运行"运行状况子系统显示"时、某些子系统中未列出所有节点?

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core<a>2009-167098</a>
Last Updated:

适用场景

  • ONTAP 9
  • FAS/AFF 系统

问题解答

  • 某些HM (运行状况监控器)子系统正在集群中的所有节点上运行。
  • 其他HM子系统仅在一个节点上运行。 
  • 这是因为存在节点级HM进程和集群级HM进程。
  • 集群级别的HM子系统仅在一个节点上运行(必要时、可能会移至另一个节点)。  节点级HM进程在集群中的每个节点上运行。
  • 因此、这是预期行为。

追加信息

  • 集群级别的HM子系统示例:
     

Cluster::> health subsystem show
Subsystem: FHM-Switch
Health: ok
Initialization State: initialized
Number of Outstanding Alerts: 0
Number of Suppressed Alerts: 0
Node: cluster-02
Subsystem Refresh Interval: 1h

Subsystem: FHM-Bridge
Health: ok
Initialization State: initialized
Number of Outstanding Alerts: 0
Number of Suppressed Alerts: 0
Node: cluster-02
Subsystem Refresh Interval: 1h

  • 节点级HM子系统示例:

Subsystem: MetroCluster_Node
Health: ok
Initialization State: initialized
Number of Outstanding Alerts: 0
Number of Suppressed Alerts: 0
Node: cluster-01, cluster-02, cluster-03,
cluster-04, cluster-05, cluster-06,
cluster-09, cluster-10
Subsystem Refresh Interval: 15m, 15m, 15m, 15m, 15m, 15m, 15m, 15m

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.
  • 这篇文章对您有帮助吗?