Alert not triggering. Can't work out why.

Hi supermop2000 so you need to make your alert an Interface Alert, it should look something similar to this:

You could also add an extra trigger condition for the Operational or Administrative State, but as you are being specific about the interface I don't think you should need that.

Cheers

Thanks - I did notice that just after I posted. I changed the 'alert on' to "Interface" and reset the trigger conditions exactly as my original post.

If the node IP is X and the interface name is Y and the interface status is DOWN then trigger.

It's still not triggering

Alerts are not muted on node are they?

A good way to validate an alert is to remove some of it's uniqueness.

If you change the Scope to 'All Objects' and goto the Summary tab, in the bottom right corner you should see a small screen that tells you how many devices will trigger this alert if you submit. If you click on the LIST and see if your interface is in that list?

I used Interface - Full Name to get the specific interface rather than relying on two filters for Node and Interface, maybe try the same thing. It will show as NODE - Interface which means you can select the right interface.

For troubleshooting purposes, could try 'contains' vs 'is' for interface.

Hi supermop,

This alert is already created OOTB. It is turned off by default, as from our experience users get inundated with alerts for down interfaces when they first do a discovery. There is a slider to turn these alerts on/off....go to alerts - manage alerts and search for interface. http://oriondemo.solarwinds.com/Orion/Alerts/Default.aspx

They are not, no.

I have now tried the trigger condition like this but no effect still:

We've got a load of other alerts that seem to be working fine. I also found an "interface down" template now, but it looks identical to what I've set up, minus the node selection.

Cheers.

We're only wanting it to alert on a single interface on a specific node, so this alert is not really suitable.

Thanks - configured as suggested:

Still doesn't trigger

Logically, my original trigger should have worked, but then I dont know what manner of database lookup shenanigans is going on under the hood!