[89655] in North American Network Operators' Group
Re: Backbone Monitoring Tools
daemon@ATHENA.MIT.EDU (Bill Nash)
Wed Mar 29 17:08:41 2006
Date: Wed, 29 Mar 2006 17:08:11 -0500 (EST)
From: Bill Nash <billn@odyssey.billn.net>
To: Ashe Canvar <acanvar@gmail.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
nanog@nanog.org
In-Reply-To: <c6f8c0e90603291344s305e73aegd35b8c0c655b8246@mail.gmail.com>
Errors-To: owner-nanog@merit.edu
Wouldn't you be better served just walking the netToMedia tables for your
devices? Parsing configs sucks. Even caching the contents of a simple
snmpwalk would save you some pain. Shovel 'em into a db and call it a day.
- billn
On Wed, 29 Mar 2006, Ashe Canvar wrote:
>
> 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.
>>
>>
>>
>
