Skip to main content
NetApp Knowledge Base

AIQUM acquisition fails via REST when FIPS is enabled on ONTAP cluster

  1. Last updated
  2. Save as PDF
Views:
41
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • Active IQ Unified Manager 9.14 and later (AIQUM)
  • All OS platform
  • REST type acquisition
  • ONTAP 9.x with FIPS enabled

Issue

  • Cluster acquisition fails in AIQUM when the Cloud Agent (REST-based acquisition) is enabled and FIPS mode is enabled on the ONTAP cluster
  • All of the following symptoms are observed while other clusters without FIPS enabled acquire normally:
    • Acquisition attempts consistently time out after approximately 10 minutes
    • AIQUM logs show: Timed out waiting for cluster, recommend increasing timeout value
    • apache_error.log shows HTTP 404 errors for REST API calls to the affected cluster
    • No TCP connection is established to the cluster management LIF, even when network connectivity is confirmed (same subnet, no firewall blocking)
    • enable.cloudagent=true is set in server.properties

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.