Hi,
In this instance, 32.1.4.24 is the configured peer IP as reported by the router. Wether not the router is reporting this correctly is something you probably want to discuss with cisco :)
The MIB defines the index of this table as being the bgpPeerRemoteAddr. The other address you see is the bgpPeerIdentifier, the Router ID.
bgpPeerEntry OBJECT-TYPE SYNTAX BgpPeerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry containing information about the connection with a BGP peer." INDEX { bgpPeerRemoteAddr } As always, the informaiton we report is only as good as the informaiton returned by the device. Thanks, adam.
On 26/02/2015 16:11:05, John Brown john@citylinkfiber.com wrote: Hi Ron,
Thought of that, so I did a traceroute to that IP. Figured it should be very close to me and go thru one of my peers. It didn't Its not even a netblock that is advertised to me. Yes, I know the BGP router-id is just a 32 bit number. Sometimes people use loopback at the router-id, etc.
What is also strange is that Observium said 32.1.24.24 was down earlier in the week. Then it says its up, now it doesn't list it when I click on the Routing / BGP drop down.
Also other real sessions are not listed. Like my session with L-Root DNS. ASN 20144. Its in the Router, but not in the poller output Its in the SNMP walk for remote ASN.
Here is a snipped output on looking at remote ASN
SNMPv2-SMI::mib-2.15.3.1.9.32.1.4.24 = INTEGER: 2914 SNMPv2-SMI::mib-2.15.3.1.9.32.1.5.4 = INTEGER: 38861 SNMPv2-SMI::mib-2.15.3.1.9.32.1.24.24 = INTEGER: 7850 SNMPv2-SMI::mib-2.15.3.1.9.129.250.197.173 = INTEGER: 2914
So the strange 32.1.4.24 as remote ASN is 2914 and then 129.250.197.173 also has remote ASN 2914. The 129 is the correct peer, and according to NTT their router-id would not be 32.1.4.24
On Thu, Feb 26, 2015 at 8:39 AM, Ron Marosko, Jr. wrote:
Just a cursory glance at this through my phone, so I may be missing something...
Bgp router-id is not always the same as the bgp neighbor id. Given the counts I appear to see, is it possible that this 32.x.x.x address your seeing is the bgp router-id of your upstream neighbor, which is why you don't see it in your configuration as a bgp neighbor?
Just a thought... I'll be able to review this further once I get on my laptop.
...Ron
Sent from my Verizon Wireless 4G LTE DROID
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium