Le Thu, May 26, 2016 at 01:05:06PM +0300, Mike Stupalov a écrit:
Confirmed here too, issue has disappear. Peers have been reimported by IP address, and all is working nicely ™
I spoke a bit too fast, I still have the 14m41s edge.pa2 edge.pa2.domain.tld Bgp-peers: 1 updated, 58 unchanged. on one Juniper.
Here seems as really updated peer: SQL[UPDATE `bgpPeers` set `bgpPeerIdentifier` ='37.77.34.0',`bgpPeerLocalAddr` ='37.77.92.45' WHERE `device_id` = '9' AND `bgpPeerRemoteAddr` = '37.77.92.44']
Updated: bgpPeerIdentifier and bgpPeerLocalAddr
Seems strange, it is not updated every few minutes ;)
1m 9s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged. 26m 40s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged. 2h 22m 26s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged. 2h 47m 16s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged. 6h 24m 57s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged. 12h 22m 58s edge.pa2 edge.pa2.dom.tld Bgp-peers: 1 updated, 58 unchanged.
Hrm, but I see something strange in SNMP output for BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerRemoteAddr
.1.3.6.1.4.1.2636.5.1.1.2.1.1.1.11.0.1.37.77.34.45.1.37.77.34.44 = "","
please attach additionally poller debug for these device: ./poller.php -d -m bgp-peers -h <device>
I just redid discovery + poller:
/srv/www/observium/discovery.php -d -m bgp-peers -h edge.pa2.dom.tld >/tmp/discovery-pa2-7889-3.txt /srv/www/observium/poller.php -d -m bgp-peers -h edge.pa2.dom.tld >/tmp/poller-pa2-7889-3.txt
Files enclosed.
Arnaud.