Measuring PoP to PoP latency--tools to use?

What tools exist that will periodically log into multiple routers and run
ping tests
to various destinations and then record the results in graphical form?

I am trying to avoid writing an expect script to do this.

I want to set up something that records semi-live data to produce
a web page similar to:

http://ipnetwork.bgtmo.ip.att.net/current_network_performance.shtml

The map portion of the graphic may be too fancy. A simple grid similar to
this
might be better:

http://www.internethealthreport.com

Any suggestions as to what tools to investigate would be greatly
appreciated.
I browsed the nanog archives as well as google...no hits so far.

Thanks,

BM

What tools exist that will periodically log into multiple routers and run
ping tests
to various destinations and then record the results in graphical form?

maybe the RTR cisco router feature for sonde-like probing ?

Response Time Reporter:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rtrenh.htm#xtocid117254

I wrote a Perl script using SNMP to collect data from
cisco RPING probes. It is storing and visualizing it later
using RRD libraries.

I am perfectly aware that ICMP echo is not really an efficient
way to measure network latency. It is rather 'IOS kernel ICMP
response' latency monitor.... I had no time to use SAA yet,
which is probably better.
   
If you are interested in my script drop me a note and I will
forward it to you.

Przemek

maybe the RTR cisco router feature for sonde-like probing ?
  
  Response Time Reporter:
  
  http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rtrenh.htm#xtocid117254
  
how many ISPs use this and [how] do they
find it helps them operationally?

it has been around for years, during which time
i have heard no actual data wrt its operational utility,
reckon that cisco would be responsive
to ISP suggestions for improvements to it

(if other router vendors have similar functionality
they should probably speak up;
we can put such features in the caida tool taxonomy)

maybe a nanog panel on provider experiences/caveats
on any of such vendor-provided functionality
is not a terrible idea.
mod all the anxiety involved in sharing such experiences

k