nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to add cluster datasource into AIQUM

JoaoLima91

Hello,

I'm trying to add a new cluster with version 9.14.1p8 into AIQUM running 9.14 and i'm having the error below:

I've already enabled the port 56443 and also set cloudagent to false on the server.properties file.

Note: i was able to add a cluster running version 9.14.1p5 right after i change the cloudagent to false on server.properties file. But now on i'm trying to add a new one with version 9.14.1p8 and it's not allowing me to add the cluster.

Any idea?

Thanks.

Find more posts tagged with

Active IQ Unified Manager

Accepted answers

Tas

If you still haven't resolved it, may I suggest a support call.

I had the same issue in a disconnected installation, and had to renew a certificate with help.

All comments

Sultana

Hello @JoaoLima91,

1. Check for the certificates on the cluster 9.14.1p8 are valid and not expired.

2. Check for the Event filter rules on ONTAP, Increase the maximum allowed number of event filter rules from 128 to 256. Refer-

https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/fails_to_add_ONTAP_cluster_due_to_a_breach_of_max_number_of_EMS_notification_destinations

JoaoLima91

Hello,

I've already in 256 by default.

Thanks

wareer

Maybe you can take a look at this document that might be helpful to you

https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Active_IQ_Unified_Manager_fails_to_add_OnTap_cluster_currently_monitored_by_Cloud_InSights_Workload_Security

Tas

If you still haven't resolved it, may I suggest a support call.

I had the same issue in a disconnected installation, and had to renew a certificate with help.

JoaoLima91

I've already scheduled a support call with NetApp.
Thanks all for the support.

mgmt-gateway

I am having the same problem after upgraded AIQUM to 9.14. Was there a solution provided by the support ?

JoaoLima91

Hello,

I got a call with our NetApp Support and we found out that there is a certificate within the server somewhere that was expired, and the info is not publically available. After a bunch of strange commands and hacking at the AIQUM database it is all sorted. It's evidently a feature request that they have this certificate problem fixed in newer versions.