2 of 2 people found this helpful
The way the logic works on table pollers is that it evaluates each row of the poller table separately, so the rule you have there would alert any time 10.0.1.24 is in any table poller at all. It doesn't check the whole table for those two values as a set. You could probably get away with specifying the rowid that currently holds 10.0.2.23 and if that rowid is not 10.0.2.23 then trigger the alert. I don't know on that particular poller if the rowid would change to something else the next time the tunnel came up though, probably would want to do some experimenting to be sure of how it behaved.
Loop1 Systems: SolarWinds Training and Professional Services
Thanks for the enlightenment about table pollers logics, The multiple test I did with the alert conditions directed me to see this behavior but since I do not have much experiences with Solarwinds I though that I did not do the right thing.
I know about the RowID and did the test, unfortunately it change every time the tunnel go down/up, so this is not a possible scenario for alert.
I will have to look at some other OID's or will try to do it with the routing neighbors.
Or if anybody out there have another solution please let me know