Incorrect graphs with traffic over 600 mbps

[from]

Hi All,
I have problem with graphs of traffic over 600mbps. As I understand counter (ifInOctets) just reachs its max limit and starts from zero.
I know, it is possible to configure cacti to poll all interfaces more frequently than one min period (lets say 5 secs or 10 secs), but I have a lot ot tests for 10/100 interfaces so my PC will die doing all tests every 5-10 sec.

Is there any other solution?

[sauron]

Realistically, I'd say you probably need a 64-bit counter. If you don't have this in the device you could fake one up with a couple of scripts. I'd have on which runs in the background, and wakes up often enough that your counter doesn't overflow between polls. This would then write a 64-bit value to a file somewhere. You can then have a data input method which calls a script that simple reads the value from the file. It's a bit crude, but it would work.

[gandalf]

Hi All,
I have problem with graphs of traffic over 600mbps. As I understand counter (ifInOctets) just reachs its max limit and starts from zero.
I know, it is possible to configure cacti to poll all interfaces more frequently than one min period (lets say 5 secs or 10 secs), but I have a lot ot tests for 10/100 interfaces so my PC will die doing all tests every 5-10 sec.

Is there any other solution?

600 mbps is an odd boundary. Are you polling every 60sec? Then, the comment above is correct: use 64 bit counters
Reinhard

[from]

Hmmmm, Thanks!
looks like I have missed option how to say Cactus to use 64bit counters for my ciscos
In fact I have supposed Cactus is wise enough to determine which counters to use automaticaly.

[BSOD2600]

In fact I have supposed Cactus is wise enough to determine which counters to use automaticaly.

The same could be said for the users -- supposing they are wise enough to use the proper SNMP version


Glad you got it working.

[gandalf]

Hmmmm, Thanks!
looks like I have missed option how to say Cactus to use 64bit counters for my ciscos
In fact I have supposed Cactus is wise enough to determine which counters to use automaticaly.

There is far too much weirdness around with that kind of "sophisticated counters" as to rely on them "automatically". Or did you ever happen to come around with a bunch of MIB files (lets say 10-15) of _any_ vendor that will be parsed _without_ errors? This may sound stupid, but it reflects my private knowledge
Reinhard