Suppressing an alert.... | NetApp | Page 1

modern eagle Oct 29, 2024, 12:06 PM

#

We have a cluster that uses a pair of unsupported cluster switches, so we get an alert from the system... At first we just deleted the alerts in the web gui, but they just keep comming back... We then tried it from the command line like: "system health alert modify -node * -alert-id UnsupportedSwitch_Alert -suppress true", but that also only works for a few hours, and the alert returns again...
We have of cause also disabled monitoring via "system switch ethernet...." and it shows as "Is monitored: false"... So are we missing something here? Isn't it possible to suppress the alerts? This is not a critical system... we have full monitoring on the Nexus switch ports and on the node cluster ports, and we have no errors besides the alerts about the unsupported switch... which is getting annoying 😉

outer forge Oct 29, 2024, 1:47 PM

#

I think you can just system switch ethernet delete it

modern eagle Oct 29, 2024, 3:56 PM

#

outer forge I think you can just `system switch ethernet delete` it

it autodiscovers the switches via SNMP... and CDP... so i would have to disable this possibility on the specific ports then..?

outer forge Oct 29, 2024, 4:37 PM

#

I think it remembers the switch and that you deleted it, and won't re-add it. But there have been many changes to the health monitoring in the past releases so that might have changed

dense karma Oct 29, 2024, 4:53 PM

#

for the cluster switches, try:
system switch ethernet modify {-type cluster} -is-monitoring-enabled-admin false

#

or maybe you have to run individually against each cluster switch.

outer forge Oct 29, 2024, 5:09 PM

#

yeah that's what I thought at first but since they said it is showing up with "Is monitored: false" that it was alerady disabled?

modern eagle Oct 29, 2024, 7:03 PM

#

OK, after I deleted them (a few hours ago) the alerts has not returned (yet) and only one of the cluster switches has been discovered.. but the status is "Is Monitored: false" and it states the reason is "SNMP Invalid settings" which is most likely the community name not matching the default... but it was able to find the Nexus IOS version etc... so for now I think I will let it be and cross my fingers 😉 To be honnest, I think I already tried the "-is-monitoring-enabled-admin false".. which didn't make a difference... but I will keep you updated... 🙂

dense karma Oct 29, 2024, 8:40 PM

#

What about grabbing the snmp line from the official Cisco rcf and applying that? Maybe it will help? If not, just undo the command

#Suppressing an alert....