North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Graphing Peering

  • From: Kevin
  • Date: Thu Jan 20 00:07:04 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=EsjcyICK8bf+5q5Y4yjRI69euY6s8ZWwft0Fo4dEOfuK+z2YASQRQpRNRP0dErOW7JOXMSPe6HSQPF1+S8czqYvwxRPP/HDX7sxEFUGqU+VgrhVk66rO36+ta1xRux2v7ORWujzkTOuD9I9QWBF9BY0FJfWGQHPc47oKdb7Hk/k=
On Wed, 19 Jan 2005 14:37:54 -0800, andrew matthews <[email protected]> wrote:
> no i mean graph bgp sessions...
> 
> it's a single interface, and i want to graph every bgp session so i
> can see how much traffic i'm doing between each peer.

If you are looking to graph statistics about the BGP peering sessions,
(rather than graphing transit router bytes in/out as suggested elsewhere),
you might take a look at the sample-config for the Cricket graphing tool,
specifically ~cricket/cricket-1.0.4/sample-config/routing

Unfortunately this graphs counts of BGP peering messages, not bytes.

Cricket can track BGP route announcements,  including graphing counts
(rates) of peer updates in/out along along with total BGP messages,
for each peering session.  You could use Cricket itself to view the data,
extract the collected data from 'rrdtool', or just look at the sources to
get an idea of the requisite Cisco OIDs to use in another tool entirely.

More information on Cricket is available from http://cricket.sourceforge.net/


Kevin