Skip to main content
NetApp Knowledge Base

Partial functionality with Active IQ Unified Manager monitoring on a specific cluster

  1. Last updated
    Jun 6, 2025
  2. Save as PDF
Views:
3,853
Visibility:
Public
Votes:
1
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:
6/6/2025, 7:03:59 AM

Applies to

  • Active IQ Unified Manager (AIQUM) 9.12 and later
  • ONTAP 9

Issue

  • Cluster appears to gather most inventory info, but acquisition shows Failed in Cluster Setup in AIQUM
  • Performance data is not collected, resulting in a gap in the performance graphs
  • Attempts of restoring files from AIQUM fails with "Connection error to storage system <cluster name>:Error writing to server"
  • ONTAP audit log gives Message (null) on HTTP from the AIQUM address
  • In the sample.log under root within an acquisition recording or the ocumserver.log. Error: 
    WARN [oncommand] [reconciliation-0] [c.n.d.c.ClusterStatusListener] Acquisition Failed for cluster : <ip address> message : Cannot store non-PrivateKeys
  • The cluster cannot be removed, throwing no error in the UI, and if attempted using um cli, it throws: ERROR: Cannot store non-PrivateKeys
  • /opt/netapp/essentials/jboss/server/onaro/cert/aiqum_mtls_<cluster_name/IP>.keystore will not exist for the affected cluster if this is the issue being experienced
  • ocumserver.log:

INFO  [admin] [default task-1485] [c.n.o.r.c.s.i.v.ClusterConnectionService] Unable to fetch the mututal TLS certificate for alias aiqum-mtls-<NODE_MANAGEMENT_IP>...

ERROR [oncommand] [reconciliation-2] [syd-nas2-cl.gnm.int(incremental@00:00:46.349)] [c.n.dfm.collector.OcieJmsListener] Inventory change listener error
com.netapp.autozapi.client.ApiProtocolException: Connection error to Storage System <cluster_name>: PKIX path validation failed: java.security.cert.CertPathValidatorException: Path does not chain with any of the trust anchors
    at deployment.dfm-app.war//com.netapp.autozapi.client.ZapiInvocation.invoke(ZapiInvocation.java:146)
    at deployment.dfm-app.war//com.netapp.autozapi.client.XmlZapiInvocation.invoke(XmlZapiInvocation.java:40)

  • Cluster Operation State shows "Failed" and below event generated in AIQUM server -

The cluster <Cluster_Name> is not reachable. The cluster cannot be reached.  Ensure there is network connectivity to the cluster and the API has not timed out. the following settings must also be configured correctly for the cluster hostname or cluster-management IP address, protocol, and port.

 

 

 

 

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.