PSINet/Cogent Latency

Tue Jul 23 05:09:25 UTC 2002

Call me crazy -- but what's wrong with setting up RRDtool with a
heartbeat time of 30 seconds, and putting in cron:
* * * * * rrdscript.sh ; sleep 30s ; rrdscript.sh

Wouldn't work just as well?

I haven't tried it -- so perhaps this is too taxing (probably you would
only run this on a few interfaces anyway)...

The last time I tested such a thing was on an uplink doing ~200 mgs and
deviation was about +/- 5mbs per second

--Phil

-----Original Message-----
From: owner-nanog at merit.edu [mailto:owner-nanog at merit.edu] On Behalf Of
Doug Clements
Sent: Tuesday, July 23, 2002 12:59 AM
To: Richard A Steenbergen
Cc: nanog at merit.edu
Subject: Re: PSINet/Cogent Latency

----- Original Message -----
From: "Richard A Steenbergen" <ras at e-gerbil.net>
Subject: Re: PSINet/Cogent Latency
> Personally I would like to see the data collection done on the router 
> itself where it is simple to collect data very frequently, then pushed

> out. This is particularly important when you are doing things like 
> billing 95th percentile, where a loss of connectivity between the 
> polling machine and the device is a loss of billing information.

Redbacks can actually do this with what they call Bulkstats. Collects
data on specified interfaces and ftp uploads the data file every so
specified often. Pretty slick.

Course, this isn't very helpful with Redback's extensive core router
lineup, but still.

--Doug