Attached are screen shots of all the alerts that LibreNMS says are down, but are really up, the alerts i have configured, and the config of the BGP down alert.
Something changed with with the LibreNMS update that happened Thursday Night (1/18/18) into Friday Morning (1/19/18) USA East Coast Time.
Hello @mvoity,
It is probably connected to bgp-peers refactor by @murrant.
I tested it but probably missed something or some incompatibility
with your device.
Try to collect:
./discover.php -h affected-device -m bgp-peers -d
./poller.php -h affected-device -m bgp-peers -d
and check output for problems.
@mvoity Hm if no visible signs try to save output into file, then revert bgp-peers update commit and collect again, after that diff outputs to see differences. Usually last part of discover with sql inserts is most readable for comparison.
@mvoity Ah i forgot that discover.php for Cisco only show peer list, status changes tracked with poller.php where shown all peer stats and its safis stats. Output seems fine, try to grep it for neighbor which status you expect parsed wrong and track all its occurancies.
@zombah, Again, thanks for your response, It’s all the ipv4 Neighbors on this router that LibreNMS sees as down, in reality they are up. The ipv6 neighbors are not reporting down.
Something clearly changed in the LibreNMS code Thursday Night (1/18/18) into Friday Morning (1/19/18) because prior to Friday Morning, LibreNMS saw the device as everything was a-ok with BGP.
Can you post the poller debug output? ./poller.php -m bgp-peers -d -h HOSTNAME
Also, if you are willing to donate some test data, we can try to make sure this doesn’t happen again. ./scripts/collect-snmp-data.php -m bgp-peers -h HOSTNAME
@mvoity I see alot “No Such Instance currently exists at this OID” in your log and result empty arrays with peers cbgp data, so problem somehow connected to polling stats from devices. @murrant it seems @mvoity posted discover and poller data in one paste, just scroll to the bottom
@murrant Thank you again for your reply, I will give that a shot. Do you know what repo i might find it from easily or is this something i need to do from scratch?
Moving to NET-SNMP 5.7 is going to be more difficult then expected.
Like i said in previous post, Something clearly changed in the LibreNMS code Thursday Night (1/18/18) into Friday Morning (1/19/18) because prior to Friday Morning, LibreNMS saw the device as everything was a-ok with BGP.
How can I get someone to look into this deeper and what kind of debugs or data do you need to fix this?