North American Network Operators Group
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Historical
Re: Backbone Monitoring Tools
- From: Ashe Canvar
- Date: Wed Mar 29 16:46:08 2006
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a/RoDyIarkHBQlmsVNV5ADI+oLB5brPngUlagF4iONrNT/XZIQd/I9GbSZ4y9bR5eFDa5E5v1H8d7xWgWFyPZEaEzGXgmGu7GN78QLNdMA8JSiVUum2PpjJyODIlJWMOnV/YZdjRSEOqjsExWkBnA0YAb0TakjFrBOKB65mQ7nk=
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.
>
>
>
|
