Advanced Alert - Router Reboot

mkocsis

I'm tryng to setup an advanced alert to email me when a router (or switch) reboots. It is simple in the basic alerts, but I need a few of the features of the advanced.

I'm stuck on the actual simple condition.

I have...

'Last Boot' and then I go down hill fast. There isn't a 'changed' option. Only 'is equal to', 'greater', etc and then a date.

This doesn't make sense to me. Has anyone else done this?



Michael Kocsis
Data Communications
City of Tampa

kbash

I've been working on this same problem for a while. We are also using custom properties to filter notification, so the basic alert wasn’t cutting it. The only thing that I've come up with is to create a new custom property and use a SQL trigger to populate the custom property, and then the alert can be built using numeric logic. If you know some SQL and are willing to customize your database, here are the details:

1) Create a new numeric custom property for the Nodes table using the Orion Custom Property editor. I used the name "MinutesUp"
2) In Enterprise Manager, add a new trigger on the nodes table with the following text:
<----start cut---->
CREATE TRIGGER [trg_CalcMinUp] ON [dbo].[Nodes]
FOR INSERT, UPDATE
AS
DECLARE @NodeID AS int
SET @NodeID = (SELECT NODEID FROM INSERTED)
UPDATE NODES SET MINUTESUP = (SELECT SYSTEMUPTIME/60 AS MINUTESUP FROM INSERTED) WHERE NODEID = @NodeID
<----end cut---->
If you don't use the name "MinutesUp" for the custom property, be sure to change both references in the trigger.

3) Be sure to test the trigger. The easiest way is to modify the value of the SystemUpTime field in the Nodes table using enterprise manager; the MinutesUp field should immediately be calculated.
4) Build your advanced alert to fire when the Field MinutesUp is less than 5 or 10 minutes, whatever you want here. I also input conditions to trigger only when MinutesUp is not empty.

Any time a record is inserted or updated in the nodes table, this trigger will fire and populate MinutesUp with the SystemUpTime (seconds) divided by 60. The reason I am using this is because during some initial testing, I ran into problems using SystemUpTime in comparative queries due to field length. I can't remember the details, but it seemed easier to just calculate the value as minutes.

***Disclaimers: I don’t know what SW’s stance is on database customizations performed outside of their tools, but I am sure this is not a supported modification. While it is unlikely to cause any noticeable performance hit, triggers do carry some processing burden for every record update. Be sure to test the trigger thoroughly, an invalid trigger can prevent any record from being updated or inserted.