I have NPM 11.5.2 and I want to setup some alerting so when a peer or connection to our ISP goes down I want to get an email alert stating which node is having the issues and what connection it lost. I am new to SW and still trying to get this whole alerting thing down so any help would be great to get me started on this.
Also, is there a away to create a report that can show all my neighbors and then i can have it posted on one of my summary screens?
There's a canned report in the alert tool: "Alert me when a neighbor goes down", which by default writes an entry in the SW log. You just need to add an additional action to that alert to send an email to you, and make sure you have the "BGP neighbors" and EIGRP neighbors" resources selected under "Routing" via List Resources for your routers.
A while ago I have bumped into a problem with default alert. When route has been deleted it would not account for this check and would alert anyways neither there is a way to exclude deleted routes within the alert in standard (non-sql) way. Hence the following line in code:
NPM_RoutingNeighbor_V.IsDeleted <> 1 --Exclude deleted routes
Maybe I just haven't found it yet ...
Here's what the default alert shows for me in the logic, you could delete the "Is Deleted" field if you didn't want it to fire on that? Our network guys wanted to be alerted in both cases so I kept that in:
ah, ok, yes.... my memory... I have mixed it up with Hardware alert, whereby it was not possible to filter out deleted sensors. May well be the case now with latest NPM. Ye, if you can get away without SQL - I would prefer more native setup obviously.
This is how I do it (sql based): Know Your Routing Neighbours
This report will highlight routing issues in a resource/report way. I keep it handy on may dashboard.
I also use exact same SQL script to fire off alerts as well. Just simply select "Routing Neighbour" as your object in alert trigger and SQL Statement as your filter construction. Then remove entire SELECT section and paste remaining SQL query into filter.
This is what I found a few years ago. And I'm still using the syslog solution as there's nothing as quick as it available.
And I just look for BGP-5-ADJCHANGE messages and forward them to the network team. Everything else in the Alert/Filter Rules section in Syslog Viewer is set to default (other than the email option).
I've accomplished the desired results by alerting off Syslog information. When a BGP or EIGRP neighbor relationship is lost, that shows up in the syslog. The router or L3 switch is configured to forward that syslog info to Orion NPM. I built a Syslog action in NPM that looks for BGP or EIGRP in the message and forwards it to my team. It's pretty easy and intuitive to do.
The online manual and the on-server manual have great instructions for how to accomplish this. All it takes is a bit of reading and you'll be working with Alerts just the way you want.
Thank cjfranca.. I know how to create node down alerts but I need to know when a bgp peer does down. I hope i am making sense at all. I think there is more to it than just node up/down.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.