[117376] in North American Network Operators' Group
Re: Route table prefix monitoring
daemon@ATHENA.MIT.EDU (Joel Jaeggli)
Fri Sep 11 06:54:18 2009
Date: Thu, 10 Sep 2009 04:23:21 -0700
From: Joel Jaeggli <joelja@bogus.com>
To: "Olsen, Jason" <jolsen@devry.com>
In-Reply-To: <19A6566FA5D52A44B7F7027F7E88BEE7DF65FD@OBT-W-EVS3P.dvuadmin.net>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Olsen, Jason wrote:
> Howdy all,
> What I'm left thinking is that it would have been great if we'd had a
> snapshot of our core routing table as it stood hours or even days prior
> to this event occurring, so that I could compare it with our current
> "broken" state, so the team could have seen that subnet in the core
> table and what the next hop was for the prefix. Are there any tools
> that people are using to track when/what prefixes are added/withdrawn
> from their routing tables, or to pull the routing table as a whole at
> regular intervals for storage/comparison purposes? It looks like
> there's a plugin for NAGIOS, but I'm looking for suggestions on any
> other tools (commercial, open source, home grown) that we might take a
> look at. For reference, we are running Cisco as well as Juniper kit.
Periodic table dumps, or even a log of the updates from a quagga router
inside your infrastructure could provide this information. That in a
nutshell is what routeviews and other collectors do for the dfz routing
table.
>
>
> Feel free to drop me your thoughts off-list.
>
>
>
> Thank you for any insight ahead of time,
>
>
>
> -Jason "Feren" Olsen
>
