Skip to main content
NetApp Knowledge Base

Clusters in Failed State in AIQUM due to OCIE Service Failure

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

Applies to

Active IQ Unified Manager (AIQUM) 9.16 (Linux)

Issue

Clusters monitored in Active IQ Unified Manager (AIQUM) show as “failed” and are not being polled successfully. The last refreshed time for the clusters was significantly out of date, indicating a prolonged disruption.

Relevant log output:

From au.log and ocumserver.log:

Error0_Message=Failed to send Baseline request to cluster!Error0_Type=BAD_ZAPI_RESPONSE2026-04-1312:36:33,093 ERROR [ForceAcqListener] c.o.s.a.f.m.ServiceManager(ServiceManager.java:501) - DataSourceEventsManager reported a fatal error: Failed to communicate with server. Acquisition unit is shutting down2026-04-1312:36:33,093 ERROR [ForceAcqListener] c.o.s.a.f.m.ServiceManager(ServiceManager.java:480) - DataSourceEventsManager reported an error: Failed to listen to acquisition events! java.net.ConnectException: Connection refused (Connection refused)2026-04-0200:00:07,605 WARN [oncommand][reconciliation-0][c.n.d.c.ClusterStatusListener] Acquisition Failed for cluster: 192.168.3.239 message: Failed to send Baseline request to cluster!

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.