[147744] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BGP noob needs monitoring advice

daemon@ATHENA.MIT.EDU (Andree Toonk)
Tue Dec 20 14:44:47 2011

Date: Tue, 20 Dec 2011 11:43:45 -0800
From: Andree Toonk <andree+nanog@toonk.nl>
To: nanog@nanog.org
In-Reply-To: <4EF0DF04.50908@spectraaccess.com>
Reply-To: andree@toonk.nl
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Hi,

.-- My secret spy satellite informs me that at 11-12-20 11:16 AM  Bret 
Clark wrote:
> Is http://cyclops.cs.ucla.edu/ still working? I don't seem to received
> emails from them anymore when we stop announcing to one of our upstream
> providers. On the other hand http://bgpmon.net/ does send me emails when
> an announcement disappears from an upstream, although it's usually a day
> later.

Just to clarify this:
For all alert types below BGPmon.net sends out an alert within minutes:
1) prefix withdrawal (prefix disappeared)
2) new upstream
3) new prefix
4) origin AS changes
5) ASpath regex failure
6) policy violation
7) RPKI validation failure

There's one other feature, the routing-report feature, that runs only 
once a day. It's similar as the cidr report, but specific to your AS. I 
like to refer to it as a rancid for your BGP announcements.

It's basically a diff between how your routes were visible today and 
yesterday. This specific feature will also notify the user if you lost / 
gained one or more upstreams per prefix.
Also see http://bgpmon.net/blog/?p=257 for more information about that 
specific feature.

Cheers,
  Andree





home help back first fref pref prev next nref lref last post