Active IQ Unified Manager Discussions

Unable to add cluster datasource into AIQUM

JoaoLima91
663 Views

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:

JoaoLima91_0-1730128221257.png

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.

1 ACCEPTED SOLUTION

Tas
491 Views

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.

View solution in original post

7 REPLIES 7

Sultana
609 Views

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
589 Views

Hello,

 

I've already in 256 by default. 

 

Thanks

wareer
541 Views

Tas
492 Views

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
423 Views

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

mgmt-gateway
151 Views

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

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. 

Public