How can I ignore Idle (Admin) BGP neighbors in Alerts?

Problem: Until I find time to go through all my gear and delete unused peering sessions,  I'd like to make Solarwinds ignore BGP neighbors with the following state: Idle (Admin)

You'll see this if you do a sh ip bgp sum and you have an admin down BGP peer.

Currently I only have the first gray child condition, Routing Neighbors Protocol Orion Status is equal to Down.  The 3 gray child conditions listed under the AND statement are ones that I was considering tinkering with if it will accomplish the task.

I was thinking that all I need to do is tell the Alerts to IGNORE Idle (Admin) bgp states this would solve my problem for now.  It doesn't look like there is a way to do this.  Can anyone give a suggestion (besides delete the bgp peers bc yeah yeah it's on my list)?

pastedImage_1.png

Here are some other options to choose from:

pastedImage_0.png

Parents Reply Children
  • Not really, at least not in all cases.  I have this situation going on right now due to a cut fiber somewhere.  The BGP down alerts that have fired originate from a different router, but cross a couple of routers to get to the end point.  The physical link is broken somewhere between, not at the point the BGP failed.  It also isn't very dynamic if things change, which they do.  There would be a lot of manual maintenance.  Dependencies don't look at the routing protocols either, so I can't build a protocol dependency on an interface.

    I might be able to attach custom properties to an interface, but what about the route itself.  Really, it would be best if SolarWinds just incorporated the Admin Down status to reference in the alert.  They mark admin down interfaces, we need that on routes, especially idle backup routes.  I need this feature for both BGP and OSPF in our very large network.