Active IQ Unfied Manager 9.18 ONTAP 9.17.1Px

[AU-TT]

I updated my Active IQ UnifiedManager from 9.16P2 to 9.18, and everything worked fine, including cluster discovery.
Now I’ve updated a cluster to 9.17.1P6, and cluster discovery no longer works. I’ve tried everything I can think of and searched everywhere, but unfortunately haven’t found anything about this.

Does anyone know what this problem is?

Failure Reason: Monitoring refresh job ID 1f2fcec250a4451b:-58f305e3:19d967594cf:-7f98 for object 'Cluster-Name' completed unsuccessfully (Status: FAI

Translated with DeepL.com (free version)

[dawnr]

Likely what happened is that the cluster was switched from traditional or mutual TLS authentication to the cloud agent. The cloud agent requires another port be opened to work - 56443 must be open from the cluster to aiqum. If you are managing aiqum on a RHEL server, you may also need to check that port is not blocked from incoming communication, and that aiqum is able to listen for itself on ports 56072 and 56080.

AIQUM Protocol and port requirements

Unified Manager 9.14 and above unable to add or monitor a cluster with cloud agent connection error

If it's not that, you'll need to open a case so we can review the logs. There are a few issues that can affect polling, but they're not the easiest to tell apart and we don't have a single patch that covers them all.

[AU-TT]

It is an Active IQ Unified Management Appliance on the same subnet, with no firewall in between.

[chamfer]

Did you check Unable to discover existing cluster in AIQUM after changing name and cluster management IP - NetApp Knowledge Base ?

While not identical issue the solution section may assist:

• Generate a new certificate in ONTAP (self-signed/CA-signed)
• Remove the clusters in AIQUM and readd if historical data is not needed
• Remove all the certificate from ONTAP for the AIQUM before adding in case remove and readd is not possible

[AU-TT · Accepted solution]

The solution was to reset the OCUM from API to ZAPI.
https://kb.netapp.com/data-mgmt/AIQUM/AIQUM-Issues/CAIQUM-6521

[chamfer]

Hi  @AU-TT 

The KB article that you referenced advised that it has been fixed in AIQUM 9.18RC1 and all subsequent releases.  Can you advise if this was the exact problem and fix that you performed?

I ask as you advised that you updated to AIQUM 9.18.

[AU-TT]

https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Clusters_fail_collections_with_duplicate_entry_for_key_errors_in_the_logs_when_Cloud_Agent_enabled
Here is another KB article that addresses this issue