Missing/Incorrect information in Alerts

I have been configuring the Advanced Alerting for remote Cisco routers that have a circuit failure to send an alert to the Infrastructure Team.

The Trigger Conditions are very straight foreward as follows:

Trigger Alert when ALL of the follwoing apply:

SNMP community is equal to XXXXXX

Interface Name contains S0/0/0.16

Interface Status is equil to Down

My Trigger Actions is to send a text message to cell phones:

Serail Interface on ${NodeName} at ${Node.IP_Address} is ${Interface.Status}. This issue was identified at ${DateTime}.

Testing this alert for a specific site, then I will get the following text message:

Serial Interface on SITE-2811-MPLS at 10.X.X.X is ${Interface.Status}. This issue was identified at Friday Feb 12, 2010 12:11 PM.

This is an issue not just due to the Interface not reporting correctly but also, the address it returned is not correct, it actually resides in our data center and not at the physical location of the router. But yes another remote will report it address correctly but the Interface status is unknown and yet another remote will report its address in another country.

Has anyone else ran into this? I am trying not to pull my hair out with this one, any assistance would be wonderful!

Thanks,

Kimberly

Find more posts tagged with

advanced_alerts

advanced_alerts_configuration_and_edit

advanced_alert

${variable}_advanced_alerts

advanced_alert_manager

Accepted answers

kimberly.adams

I received this from Support on this issue:

“Test Fire Alerts” only tests the trigger / reset actions, not the trigger conditions or reset conditions themselves. Its entirely possible to have the “test” alert just send out information in an action for an interface or node that shouldn’t be triggering that alert, if you’ve selected that node or interface from the drop-down list.so what you are seeing seem to be correct its not testing again the device but simply variables within the alert

I really don't know about this as an answer, but does anyone else get the wrong information when test firing an alert or is it just me?

All comments

sedmo

The interface status information is not showing up correctly in your alert message because the table in the database is named interfaces (not interface). So, your alert message needs to say ${Interfaces.Status}.

As for the rest of your problem, how are you testing the alert?

kimberly.adams

When the remote routers were reloaded over the weekend, the alert triggered correctly with all the correct information. This issue that I stated above only happens when testing the alerts. All the Serial Interfaces in our database are setup as Interface and not Interfaces.

I go to Test Fire Alert and then select the Alert on Network Node and select a router. The biggest issue I am running into when testing is the IP address doesn't match the node the alert is triggered for. It will send me the correct node name but not the correct corrisponding IP address for the node.

macnugetz

Kimberly,

I would open a support ticket and reference this thwack thread. Not sure why you're getting the wrong IP in the alert message.

BTW, thanks sedmo for jumping on this one!

-Craig

kimberly.adams

Craig,

Thank you for responding and this one is very strange. I did open a support case on this yesterday afternoon and so far they are absolutely stumped on why the Test Fire Alert is not working and giving the wrong address but when a remote circuit fails or router is reloaded, it alerts correctly. When they come back with an answer and a solution, I will update my thread with it.

Kimberly