Problems accurately graphing gigabit interfaces

[TheWitness]

Gandalf,

I guess I should release scanner It would make this very much easier.

TheWitness

[rock]

Is there an ETA? I really want to avoid going through almost 600 interfaces and changing them manually

Thanks, Rock

Gandalf,

I guess I should release scanner It would make this very much easier.

TheWitness

[TheWitness]

It would be easier to write a simple script to do it. Scanner is a beast of a plugin.

TheWitness

[ARC1450]

Maybe someone can help me understand why 64-bit counters are needed for 1Gb interfaces as I'm not really understanding.

2 to the power of 32 is 4 billion, so why don't some people get the proper graphs with 32 bit counters?

That said, I have 32 bit counters on all my Gb interfaces and regularly see traffic spikes over 200Mb.

[Howie]

Maybe someone can help me understand why 64-bit counters are needed for 1Gb interfaces as I'm not really understanding.

2 to the power of 32 is 4 billion, so why don't some people get the proper graphs with 32 bit counters?

That said, I have 32 bit counters on all my Gb interfaces and regularly see traffic spikes over 200Mb.

Traffic is calculated by looking at the difference between the traffic counters now, and last time you looked. The counter wraps around when it gets to 2^32. So if you come back after five minutes, and the counter is lower than it was before (and the uptime hasn't gotten lower too), you can only assume that it has wrapped around. If it has wrapped around twice, you have no way to tell.

The counters will wrap around fully after 4GB is transferred (2^32 bytes), so you can't tell if more than that is transferred.

In 5 minutes, 4GB transferred works out to be about 114Mbit/sec.

By using 64-bit counters, the bytes-to-wrap is much much larger. Alternatively, you can get a bit more headroom by polling more often (but still not 1Gbit/sec).

[ARC1450]

Ahh!

So the reason I'm not seeing much issue is because I'm polling once a minute then, eh?

[Howie]

Ahh!

So the reason I'm not seeing much issue is because I'm polling once a minute then, eh?

Yep - that would do it Your limit should be somewhere around 550Mbit/sec.

[ARC1450]

Ahhh, thanks dude!

I appreciate the clarification.

[kendirangu]

1) You will need to adjust your Max Value in the Data Templates for Interfaces.
2) You will need to utilize SNMP v2/v3
3) You need to select one of the 64bit counter graphs in Cacti. When creating graphs, you will see them on the drop down.

TheWitness

Where do i find the 64bit counter graphs ? I'm using 0.8.7b are the graph templates labelled 64bits ? I have been using the typical Interface - Traffic (bits/sec) template.

[TheWitness]

Where do i find the 64bit counter graphs?

Create Graphs

I'm using 0.8.7b are the graph templates labelled 64bits ?

Not unless you alter the template

TheWitness

[Howie]

You could follow along the fun with
How can I tell if a graph is using 64-bit counters? too... it's not that simple to find the graphs that need fixing

[TheWitness]

[ronnyg]

Hi all. Just installed Cacti 0.8.8b and got some difficulties with gigabit ports on ProCurve 1800 (1810) switches and Server NICs. As people said above, graph only goes up to 114Mbit.
SNMP version is 2.0
Graph Template is default Interface - Traffic (bits/sec) 64bit Counters
Data Template is default Interface - Traffic with Max Value set to U

ProCurve 1810 even doesnt show any datas in graphs while 1800 showing the same 114Mbit

P.S. Plugin Realtime shows correct values!!! I think its because of different poller used or smth...

Please, help me to resolve this issue.