[mrtg] Re: 8Gbps stream creates incorrect graphs- rateup problem?

[Alex Nguyen]

Hi,

I have this problem with a 2Gbps stream (an aggregation of 64bits counters 
of 2 GigE links).

With the version 2.9.7, I have the same graph without any error message.

With the lastest version of MRTG, 2.9.22, I have the same graph and
the following error message in MRTG :

line 356:              warn "ERROR: Target[$rou][$mode] '$$rcfg{target}{$rou}' evaluated to '$data' instead of a number\n";

I think, the problem is not the interval value (32bits interger), but the
last readed value is greater than what MRTG can handle.

It anyone know what is the limit of the last readed value that MRTG can
handle ? (the value that returned by the device when MRTG is polling)

Regards.

A.

On Sat, 5 Oct 2002, Chris Robb wrote:

CR> Date: Sat, 05 Oct 2002 09:09:49 -0500 (EST)
CR> From: Chris Robb <chrobb at indiana.edu>
CR> To: mrtg at list.ee.ethz.ch
CR> Subject: [mrtg] 8Gbps stream creates incorrect graphs- rateup problem?
CR> 
CR> All:
CR> 
CR> I've run into this problem before with smaller 2.5Gbps streams, but we
CR> just pushed an 8Gbps UDP stream across the country and it's really done a
CR> number on our graphs. We're running MRTG 2.9.17. The logfiles have the
CR> appropriate values in them, measured in bytes off Juniper routers. I
CR> appears that rateup is barfing on the large numbers. The generated images
CR> show a steady 4Kbps line of traffic in place of collected date. We use an
CR> external collector script to grab the data.
CR> 
CR> I've attached the top portion of our MRTG logfile, with the problematic
CR> portion at the bottom. The graphs are at:
CR> 
CR> http://loadrunner.uits.iu.edu/weathermaps/abilene/mrtg-data/WASHng-NYCMng/washng-nycmng.html
CR> 
CR> This is consistent across all the links that were measuring the data. In
CR> one case, I removed the large values, reran MRTG, and the daily graph was
CR> fixed.
CR> 
CR> I've read that the interval values in the MRTG log file are interpreted as
CR> 32-bit integers. Since we're looking at bytes, they don't come anywhere
CR> near the 4billion-byte-per-second limit.
CR> 
CR> I'm poking through the rateup code now to see if anything jumps out at me,
CR> but if anyone has any ideas, feel free to share. Thanks!
CR> 
CR> -Chris
CR> 
CR> Chris Robb
CR> Indiana University Global NOC
CR> Abilene/TransPAC Network Engineer
CR> chrobb at iu.edu  Desk: 812-855-8604 Cell: 812-325-8199
CR> 
CR> 
CR> -- Attached file removed by Listar and put at URL below --
CR> -- Type: TEXT/PLAIN
CR> -- Size: 9k (9384 bytes)
CR> -- URL : http://www.ee.ethz.ch/~slist/pantomime/wash-mrtg.log
CR> 
CR> 
CR> --
CR> Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
CR> Archive     http://www.ee.ethz.ch/~slist/mrtg
CR> FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
CR> WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi
CR> 

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi