Skip to main content
NetApp Knowledge Base

OCUM fails to monitor the cluster when one of the nodes is in uneligible state

Views:
721
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Applies to

  • Active IQ Unified Manager (OCUM) 9.x
  • OnCommand Unified Manager (OCUM) 9.x

Issue

  • Cluster monitoring failed event it is displayed in the OCUM Web UI
  • The following error is present in the ocumserver.log
2020-08-12 05:57:04,193 ERROR [umadmin] [job-326] [refresh(cluster=%cluster_name%)|forceAcquisition] [com.netapp.dfm.job.JobEngine] Error executing job 929c0a0fc57e14bc:1c44b14f:173d8837f89:-7f9f task 929c0a0fc57e14bc:1c44b14f:173d8837f89:-7fa1: Errors reported on acquisition with start time 05:56:35.844: [storage-shelf-list-info; errno: 14007, reason: Node is not healthy, storage-adapter-get-adapter-info; errno: 14007, reason: Node is not healthy]
  • The following output is present in the ONTAP cli

cluster1::*> cluster show

Node                 Health  Eligibility   Epsilon

-------------------- ------- ------------  ------------

cluster1-a        true    true          true

fcluster1-b       true    true          false

fcluster1-c       false   false         false

cluster1-d        true    true          false

4 entries were displayed.

 

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.