Connecting ActiveIQ Unified Manager to ONTAP cluster

SVHO · ‎2024-08-23

We recently placed in production a FAS 8300 (9.14.1P6). We had a FAS2650 for seven years. We built a Windows 2019 with ActiveIQ Unified Manager 9.14. When we first tried to add the ONTAP to the Unified Manager, it told us the self signed cert has already been expired. We followed the instructions below

https://kb.netapp.com/on-prem/ontap/DM/System_Manager/SM-KBs/How_to_renew_an_ONTAP_selfsigned_certificate_via_System_Manager

Under the client/server certificates tab, we renewed the self signed cert for the expired SVM self signed cert in which we got a new self signed cert with a new name. Then we deleted the original self signed cert (SVM). Then we did the same and renewed the cert for the cluster but we didn't remove the expired self signed cert (cluster).

We went through the process again to add the ONTAP cluster but it would just hang forever with the spinning circle.

We have a few questions as a result of this process.

1) The renewal of the certs does not affect users access on CIFS shares?

2) How do we fix the issue described above (trying to add ONTAP onto ActiveIQ Unified Manager).

SVHO

SVHO · ‎2024-08-23

We added more memory and CPU for this Windows machine and re-attempted to add ONTAP to the cluster and got this:

Unable to add cluster datasource. This can occur if the clocks on the systems are not synchronized and the Active IQ Unified Manager HTTPS certificate start date is later than the date on the cluster, or if the cluster has reached the maximum number of EMS notification destinations.