Traps get tripped - but they don't alert

Hello -

Parden if this as been reported on and discussed before - I did a quick check for this topic

But I have seen traps reported, but do get an email on the alert.

I am trying to get a better understanding of the process flow and where I should look [logs, etc...] to troubleshoot the issue.

My traps are coming from Netapp NAS, via DFM, to Solarwinds. The Alerts are setup to send via SMTP, and are active.

BTW: Would be nice to test if traps are working, the way we can test Alerts.

Regards,

Peter

Find more posts tagged with

traps

smtp_server_mail_e-mail_email_alerts

dfm

Accepted answers

All comments

rob.hock

Easy way to narrow this down to the condition or the email action would be to create another alert action to (for example) log to event log.

FormerMember

I had this issue. It turned out to be a problem in the Alert Suppression setup.

Apparently, Alert Suppression rules don't work the same as trigger conditions. I had set up a rule not to alert is the device names were "abc" or "xyz", and it turned out that rule meant to suppress the alert if a device name of "abc" or "xyz" EXISTED IN THE DATABASE. The exact same rule set up with the Trigger Conditions worked find, because when it was set up there, the name check was performed on the incoming alert, not against the entire device list.

Rob is right, best way to troubleshoot is to create a new rule, and gradually build it up to match the one that isn't working. Set up the trigger conditions one by one, and see which one is keeping the alert from firing. If it's firing ok, then start putting in the Trigger actions one by one, until you find the one that isn't doing what it's supposed to.

Also, if your trigger actions include executing an external program, try running the same program from the C:> prompt to make sure it works.

If it works from the C:> prompt but not when the alert is triggered, it might be a permissions issue.

Chris