Skip to main content
NetApp Knowledge Base

Cluster monitoring doesn't work in OCUM after applying firewall rule in ONTAP

  1. Last updated
  2. Save as PDF
Views:
564
Visibility:
Public
Votes:
0
Category:
oncommand-unified-manager
Specialty:
om
Last Updated:

Applies to

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

Issue

  • Monitoring failed for a specific cluster in OCUM
  • The following error will be present in the ocumserver.log file

2020-07-27 12:13:05,080 ERROR [admin] [job-327] [refresh(cluster=clustername)|forceAcquisition] [com.netapp.dfm.job.JobEngine] Error executing job 4f93c562a2fc8c90:5f9303c:173774a6c44:-4d3a task 4f93c562a2fc8c90:5f9303c:173774a6c44:-4d3c: Errors reported on acquisition with start time 12:13:04.798: [[Device name IP or FQDN]: Failed to connect to the cluster.]
java.lang.RuntimeException: Errors reported on acquisition with start time 12:13:04.798: [[Device name 172.27.37.102]: Failed to connect to the cluster.]

Note: Unified Manager: What are the notable log files and their respective locations

 

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.