Greetings Thwack Community Friends!
It's been a while since I've written a post seeking assistance because almost everything I've wanted to find, I've already found. That being said, I'm having issues with one of my Universal Device Pollers and the Advanced Alert Bound to it. I'll try to explain the situation as best I can and then attach the export of the UnDP and the Alert Definition in case that will help.
| Universal Device Poller Definition | |
| OID Polled (Numberical) | 1.3.6.1.2.1.15.3.1.2 |
| OID Polled (Long) | iso.org.dod.internet.mgmt.mib-2.bgp.bgpPeerTable.bgpPeerEntry.bgpPeerState |
| Get Type | GetSubTree / Get Table |
| Label Type | Same Table |
| Label Detail | 1.3.6.1.2.1.15.3.1.7 |
| Label Detail "Name" | iso.org.dod.internet.mgmt.mib-2.bgp.bgpPeerTable.bgpPeerEntry.bgpPeerRemoteAddr |
This returns (on some routers) two entries based on two BGP neighbors. We currently only have one or two remote site routers setup this way, but it is the way in which we are going in the future.
Right now, we're only interested in alerting on a BGP down (defined to us as any result that is not equal to 6 [established]) on routers which are part of our MPLS cloud. All of our internal neighbors would start with a private IP scheme. For the sake of discussion, let's say that the internal scheme is the 10.0.0.0/8 IP network.
My alert is defined like this:
| Trigger Condition | |
| Property Type: | Custom Node Poller |
| Trigger Alert when all of the following apply | |
| Poller Name is equal to bgpPeerState | |
| Numerical Status is not equal to 6 | |
| Reset Condition | |
| When trigger actions are no longer true | |
| Alert Suppression | |
| Suppress Alert when all of the following apply | |
| Row ID starts with 10. | |
I think this will work as I guess, but I'd really appreciate any insight anyone can give. Right now we're showing no alerts, but the only time we show an alert is when one of our WAN providers has an issue. Obviously, I'd like to not have to wait on that or cause that.
Lastly, I'd love to be able to "fix" the variables that are available for the alerting text itself. Right now it's pretty basic. It's just:
On Trigger Subject: [ALERT] BGP Down on ${Node.Caption} (${Node.IP_Address})
On Trigger Body: BGP Status on ${Node.Caption} (${Node.IP_Address}) is not-established for neighbor ${CustomPollerStatus.RowID}.
On Reset Subject: [RESET] BGP Down on ${Node.Caption} (${Node.IP_Address})
On Reset Body: BGP Status on ${Node.Caption} (${Node.IP_Address}) is established for neighbor ${CustomPollerStatus.RowID}.
Lastly, I'd like to change the the headers on the rows in the UnDP element on my node detail pages. Having the Remote IP of the peer would be great, but it's only really "useful" if that's what it's called. This also applies with the bgpPeerState itself which shows as the numerical value even though the UnDP "knows" what each number 1-6 means.
Above you can see the private address of 10.28.x.x that is showing a state of "3" which should have the alert suppressed. The second (216.149.x.x) is at 6 and will not trigger the alert.
Summary
OK - this has gone way far afield, but it's basically me trying to figure out how to work with multiple elements returned from a UnDP request.
Any help would be greatly appreciated.
