I have created Node alerts in SW that triggers when a "Node" goes down. I've set these up for Router_Function "primary", "back-up", and "only". All of them work great! Here is one of those alerts "Back-up router DOWN". This alert will e-mail me when a site's back-up router has been down for 5 minutes and it is restored after 10 minutes of uptime.
Trigger Conditions - Node Status is equal to Down and Router_Function (defined in custom properties) is equal to back-up (defined in custom properties). Reset alert if Node Status is equal to Up.
Trigger Actions - Send an e-mail to me. Message: The ${Router_Function} network connection which provides network redundancy for ${Node.City}, ${Region} is ${Status}. Network communications at the site are not being impacted at this time. The Bio-Rad IT Network Group is already aware of this issue and is currently working to resolve it. For any questions, please contact the Global IT Service Desk at 510-741-XXXX.
Thank you,
Corporate IT Network Management & Monitoring Group
The second part of this project is to do the same thing for the "primary WAN link" and "back-up link" since if these interfaces are down, I wanted to be alerted as well because it means network performance issues. I know they are interfaces and has to be set up as an interface alert. I've manually defined every Primary WAN Link and Back-up Link as an Interface_Type in custom properties. I've also defined the Interface_City and Region for each of these interfaces as well. I can get the alert to work but when I test the trigger on the back-up link interface of my Linz router in Austria, the message is received for the interface of my Olso router in Northern Europe. I can't figure out why when I'm testing on a router that has been defined as being in a certain city and region, it's being sent as one from a different city and region. Help!
