#Cannot add 9.16.1P1 clusters to AIQUM 9.16

1 messages · Page 1 of 1 (latest)

primal tinsel
light kayak
#

have you tried restarting AIQUM after the change? I know it's not explicitly mentioned in the KB article but sometimes that helps

exotic herald
#

Yes, most likely support case needed.
AIQUM had (and still has) many issues with mTLS and REST based connection to clusters (especially when they are on newer ONTAP versions). All the cases I know they switch it back to ZAPI in AIQUM (while ONTAP tells you that ZAPI might become deprecated in some near-/distance-future). I don't know why it's so hard to fix.

acoustic stag
#

Any errors in the ocumserver.log, server_mega.log or au.log?

primal tinsel
south galleon
#

I've been going through this the last few weeks. AIQUM and REST is more than a bit of a PITA

primal tinsel
#

did you end up getting this working ? Our case is still ongoing

south galleon
#

well, I did get the mTLS certs updated and the new tcp ports opened in the firewall (would be nice if the vmware "appliance" included tcpdump) and added a new cluster, but my existing clusters just stopped collecting data and that I haven't yet fixed

#

I'm about to disable the "cloud" option in server.preferences and let the cards fall where they may

south galleon
#

My Harvest setup doesn't seem to suffer the same problems, but it uses mostly zapi calls, so that could be part of the issue. The REST subsystem in ONTap seems to have a few performance issues yet, but my boxes are a bit overloaded as well until I get new hardware up and running, so there's that as well.

south galleon
#

Basically, the only way I've gotten things to work now with the clusters that stopped working after years of mostly ok monitoring is to disable the REST polling (my assumption) by changing the enable.cloudagent=true to "false" in /opt/netapp/essentials/conf/server.properties ('sudo vi' in diag login shell) .

stoic aspen
#

clearing the database and restarting worked for me.