![](https://secure.gravatar.com/avatar/3bbbd945c333b8013d0dfa23058f65b9.jpg?s=120&d=mm&r=g)
Hi,
please send me debug poller/discovery output: ./discovery.php -d -m bgp-peers -h <junos> ./poller.php -d -m bgp-peers -h <junos>
On Fri, Nov 14, 2014 at 9:48 AM, bt geemales@gmail.com wrote:
Hello,
I tried digging through the mailing archives but jet lag from my recent trip is stymieing my efforts in finding relevant threads.
I'm running 0.14.11.5945 and notice that 4-byte ASN is still not supported. We use 4-byte ASN for the greater range as we eventually plan to run eBGP down to our servers.
On Junos devices -- anything from MX, QFX to SRX -- I notice that ASNs show as a negative integer (example "-94967243"). On our Cisco's, they show up as our favorite 23456.
The main question is: Are the negative integers a limitation of the Junos MIB? On those individual devices I do not have a "tab=routing/proto=bgp/", the BGP sessions do not show up at all under the general "routing -> BGP All Sessions" tab, and consequently we're missing a large chunk of our network and we don't have any BGP alerts (though I have all the above with Cisco Nexus gear).
Are there any workarounds or plans to support 4-byte ASN in Observium, specifically with Junos equipment?
Thank you!
bt
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium