observium says bgp neigh down, yet neigh never existed
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped.....
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email that'll give you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that works out what entity should be used.
adam. On 23/02/2015 03:30:57, John Brown john@citylinkfiber.com wrote: 38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong adama@memetic.org wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email that'll give you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that works out what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown john@citylinkfiber.com wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
If you made a definition for it, it's new alerting. If you're not running a 2 year old install, it's new alerting. :D
What did the link in the email it sent you go to? (the edit link). You might be able to work out what happened from there.
adam. On 23/02/2015 03:42:03, John Brown john@citylinkfiber.com wrote: Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email that'll give you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that works out what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 23/02/2015 02:01, Adam Armstrong wrote:
If you made a definition for it, it's new alerting. If you're not running a 2 year old install, it's new alerting. :D
What did the link in the email it sent you go to? (the edit link). You might be able to work out what happened from there.
Post says "No email generated for the alert". Though that sounds odd...
adam.
On 23/02/2015 03:42:03, John Brown john@citylinkfiber.com wrote:
Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email
that'll give
you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that
works out
what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this
address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Where did it "report" it then?
Sometimes its useful to actually explain what's happening.
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 23 February 2015 01:58:56 Tom Laermans tom.laermans@powersource.cx wrote:
On 23/02/2015 02:01, Adam Armstrong wrote:
If you made a definition for it, it's new alerting. If you're not running a 2 year old install, it's new alerting. :D
What did the link in the email it sent you go to? (the edit link). You might be able to work out what happened from there.
Post says "No email generated for the alert". Though that sounds odd...
adam.
On 23/02/2015 03:42:03, John Brown john@citylinkfiber.com wrote:
Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email
that'll give
you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that
works out
what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this
address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Reported on the main status screen right under the map, red box.
Now its gone.
What is strange is another BGP session with a similar peer IP is showing up, but is not configured on that router at all
And NO AS 2914 is not associated with this Net-32 prefix
here is output from router in LAX
cr01.lax#sh run | inc 32.1.4.24 cr01.lax#sh bgp sum | inc 2914 129.250.YYY.XXX 4 2914 45250167 296949 225255269 2 0 2w4d 521237 cr01.lax#
Note that doing a show run and searching for the neigh IP reveals no output. Ergo its not in there doing a show bgp sum and searching for AS 2914, shows only a single IPv4 session on a DIFFERENT IP (the correct one)
Thus this 32.1.4.24 isn't configured on this box
On Mon, Feb 23, 2015 at 1:12 AM, Adam Armstrong adama@memetic.org wrote:
Where did it "report" it then?
Sometimes its useful to actually explain what's happening.
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 23 February 2015 01:58:56 Tom Laermans tom.laermans@powersource.cx wrote:
On 23/02/2015 02:01, Adam Armstrong wrote:
If you made a definition for it, it's new alerting. If you're not running a 2 year old install, it's new alerting. :D
What did the link in the email it sent you go to? (the edit link). You might be able to work out what happened from there.
Post says "No email generated for the alert". Though that sounds odd...
adam.
On 23/02/2015 03:42:03, John Brown john@citylinkfiber.com wrote:
Not sure what delineates between old alerting and new alerting presently running
Observium 0.15.2.6286 (rolling)
no email generated for the alert.
On Sun, Feb 22, 2015 at 2:39 PM, Adam Armstrong wrote:
If it was the /old/ alerting, who knows, that stuff is broken.
If it's the /new/ alerting, there should be links in the email that'll give you a hint as to what it's talking about.
It's vaguely possible that there might be a bug in the code that works out what entity should be used.
adam.
On 23/02/2015 03:30:57, John Brown wrote:
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Maybe it's a NSA router ? :)
-----Message d'origine----- De : observium [mailto:observium-bounces@observium.org] De la part de John Brown Envoyé : lundi 23 février 2015 04:31 À : observium Objet : [Observium] observium says bgp neigh down, yet neigh never existed
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
No that's in the other rack ;)
On Tuesday, February 24, 2015, Mathieu POUSSIN Mathieu.POUSSIN@oxalide.com wrote:
Maybe it's a NSA router ? :)
-----Message d'origine----- De : observium [mailto:observium-bounces@observium.org javascript:;] De la part de John Brown Envoyé : lundi 23 février 2015 04:31 À : observium Objet : [Observium] observium says bgp neigh down, yet neigh never existed
38 some minutes ago, observium reported that BGP neigh 32.1.24.24 was down on our LAX router. yet this IP has never been configured on this router as anything, let alone a BGP neigh
A quick grep of rancid history for this router never shows this address.
Stumped..... _______________________________________________ observium mailing list observium@observium.org javascript:; http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org javascript:; http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (4)
-
Adam Armstrong -
John Brown -
Mathieu POUSSIN -
Tom Laermans