[51348] in North American Network Operators' Group
RE: Measuring BGP routes
daemon@ATHENA.MIT.EDU (Frank Scalzo)
Fri Aug 23 15:51:09 2002
Date: Fri, 23 Aug 2002 15:49:02 -0400
From: "Frank Scalzo" <frank.scalzo@amerinex.net>
To: "Jeff S Wheeler" <jsw@five-elements.com>, <nanog@merit.edu>
Errors-To: owner-nanog-outgoing@merit.edu
Depends on how much info you want. There is obviously more info in the
network then outside. If you want to look at things in a confederated
environment like how many routes are coming from each confederation, you
need to be in the network. Same thing if you want to do any analysis on
any attribute that doesn't cross an EBGP border. I think ideally it is
preferable to be outside the network so you're not taxing a live box,
but sometimes if you want the purest picture there is a reason to get it
from in the network.
Whether the box is in or out of the network the basic premise is still
the same, get the table out, and parse away.
-----Original Message-----
From: Jeff S Wheeler [mailto:jsw@five-elements.com]=20
Sent: Friday, August 23, 2002 3:34 PM
To: nanog@merit.edu
Subject: RE: Measuring BGP routes
On Fri, 2002-08-23 at 15:05, Frank Scalzo wrote:
*edited for length*
> Most of the tools I have seen have basically done a show ip bgp
> collected the whole table and parsed it. I know I wrote a tool like
that
Is there any reason this is preferable to establishing an eBGP multihop
session with the box and receiving the information by that means?
--
Jeff S Wheeler <jsw@five-elements.com>
