From: weiser <ho...@we...> - 2009-11-17 14:47:30
|
Hi, sorry that I first write now, I have had some other things which have taking all my time... <CUT> > Well, the devmon collector passes the definition in the DS line of the > message > straight through to the code that calls librrd functions to create the RRD > file, so your RRD file should have been created to use the COUNTER data > source > type for ifInOctets and ifOutOctets. You can verify which data source type > your rrd file is using for these data sets using 'rrdtool info > /path/to/rrd'. It is COUNTER there is used. > > I notice that most of the rrd collectors that ship with Xymon use the > DERIVE data type by default. Networking devices with SNMP counters should > be able to use COUNTER safely, and using COUNTER should be more accurate > (as it will get the data between the highest value seen and the counter > wrap value, which DERIVE would lose). > > You may want to experiment by changing the COUNTER in your message file to > DERIVE, and then remove / rename the existing RRD file, and see if this > prevents it in future. However, as far as I can tell, this should not make > a difference (see below), unless the bug is in rrdtool itself. I have changed in my template to DERIVE from COUNTER. And removed the rrd files. And now it work, so it looks like it is a bug in rrdtool... <CUT> > The only place I can think of where this could occur is in rrdtool itself. > > What version of rrdtool are you running? You could manually create an rrd > file > (with 'rrdcreate') and update it with values going over the counter wrap, > and see if you get the same behaviour. The version I use is: 1.2.19. Regards, Kim |