[89652] in North American Network Operators' Group
Re: Backbone Monitoring Tools
daemon@ATHENA.MIT.EDU (Ashe Canvar)
Wed Mar 29 16:45:15 2006
Date: Wed, 29 Mar 2006 13:44:43 -0800
From: "Ashe Canvar" <acanvar@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: nanog@nanog.org
In-Reply-To: <200603291848.k2TImXcX018593@turing-police.cc.vt.edu>
Errors-To: owner-nanog@merit.edu
Well, True. But the idea is to have a full mesh of 'n' sensors each
doing 'tests' to the remaining n-1 sensors. Finding asymmetric routes
should be trivial as I plan to feed it my router configs from rancid,
for detecting interfaces that belong to the same router. ( Of course,
this can't be extended to the Internet in genral. )
From all the replies I have received, I don't think anything open
source fits the bill.
Going to the mines to write my own. Good bye cruel world...
On 3/29/06, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> On Tue, 28 Mar 2006 16:07:27 PST, Ashe Canvar said:
>
> > 2. actively detect routing changes / failover to redundant paths
> > using traceroutes
> > i.e. alert if SFO->CHG->NYC changes to SFO->LXE->HOU->NYC
> > ( link state protocols suck as far as testing backup paths go)
>
> Two words: "Asymmetric routes". Just be aware of the implications.
>
>
>
