[21982] in North American Network Operators' Group

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

Re: aggregation tool wanted

daemon@ATHENA.MIT.EDU (Cengiz Alaettinoglu)
Mon Nov 30 19:31:43 1998

From: Cengiz Alaettinoglu <cengiz@ISI.EDU>
Date: Mon, 30 Nov 1998 15:59:55 -0800 (PST)
To: Randy Bush <randy@psg.com>
Cc: nanog@merit.edu
In-Reply-To: <m0zjrDV-0008G4C@rip.psg.com>
Reply-to: cengiz@ISI.EDU


Randy Bush (randy@psg.com) on November 28:
> i have a perl script which takes in the form
> 
>     133.10.0.0
>     133.11.0.0
>     155.162.0.0/15
>     155.164.0.0/14
> 
> and tells me that i can aggregate the first two into a /15.
> 
> unfortunately, the actual data as paths can differ
> 
>     133.10.0.0       2914 2907
>     133.11.0.0       2914 2907 2501
>     155.162.0.0/15   2914
>     155.164.0.0/14   2914
> 
> so, what i would like is a tool which takes something like the latter syntax
> and tells me what the origin ass could aggregate.  i.e. i am specifically
> not inclined to proxy aggregation at this point.
> 
> Maybe CIDRadvisor does this, but I have been unable to make it do so.

CIDRadvisor requires aut-num's to be populated to figure out differing 
as paths. Given the state of aut-num's in IRR, it is not a very useful 
tool.

One could use as paths from a BGP route table dump. But that is only
an estimate, as two routes flap the as paths may diverge differently.

> 
> randy


Cengiz

-- 
Cengiz Alaettinoglu           Information Sciences Institute
http://www.isi.edu/~cengiz    University of Southern California

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