Oh Cisco they are being reported as 23456. On Juniper it sounds like they're being reported as a wrapped counter, which is pretty typical Juniper type of failure.
I have nothing with 4-byte ASNs and I don't touch Juniper kit, so I don't really know.
You can probably work it out yourself by walking the relevant OIDs and/or looking at the poller debug output.
adam.
------ Original Message ------ From: "bt" geemales@gmail.com To: observium@observium.org Sent: 11/14/2014 12:48:34 AM Subject: [Observium] Junos 4-byte ASN support
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