#Onprem AIQ setup...

1 messages · Page 1 of 1 (latest)

winged tusk
#

Hi there... One of my customers would like me to setup AIQ for their setup... and it works "fairly well"... other than a few issues which I will try to describe in the hope that others have found soltions to this...

  1. We have a lot of events about anti ransomware and learning etc.. which is annoying because this is all NFS datastores with VMs on it.. so it does not make any sense enabling this... so is there a "global" way that you can tell AIQ to stop bugging us about ransomware related issues?
  2. The customer are running Veeam backups, which triggeres the "VeeamAUX" clones which AIQ picks up on and creates an event complaining that the volumes is offline... not all the time, but often... can you create a "filter" of volumes that AIQ should just ignore?
  3. We have an old cluster that has been turned off and decommisioned, yet we cannot delete it from the list of clusters... it says deleting... forever... we tried reboot etc. yet we are stuck with the cluster (we have now created a support case)
small tapir
#

Regarding #1:
I wouldn't recommend it but Global events can be disabled by Storage Management - Event Setup - Disable.
There you can disable the Critical severity event "Ransomware activities detected".

winter valley
#

You can set an exclude filter for an alarm to exclude resources.

#

Deleting the old cluster will require support assistance as it will require database manipulation. The recommended practice is to remove the cluster prior to offlining it. Unified Manager will attempt to remove records from it as part of the deletion process. It is unable to do so on systems that are no longer online.

winged tusk
#

Yeah we had a quick session to delete the old cluster... I guess I could have done this myself, but apparently NetApp would like to help out.. and I guess this will all be fixed in a future release...

#

I will investigate the filter of alarm... some of this stuff is "kinda" hidden in the menus 😉

winter valley
#

We always prefer to be careful when performing DB manipulation.

For the filter

You could do something like