Problems with graph when traff is more than 114 mbit.

_k4 · Post by **_k4** » Fri Feb 13, 2009 12:40 am

When traff is more than 114 mbit graph value is going to 0 and graph have only values of difference between real traph count and 114 mbit. See the attachment.

How can I solve this problem?
Thanks.

Post by **browniebraun** » Fri Feb 13, 2009 2:04 am

For interfaces like this one you've to choose a graph type which supports 64 Bit counters.

Best regards
-Andreas-

_k4 · Post by **_k4** » Mon Feb 16, 2009 12:34 am

Is this a template? I meat 64bit graph..
I have only this:

Post by **gandalf** » Tue Feb 17, 2009 1:32 pm

When "Create Graphs for this Host" is selected, please find the table related to "Interface - Traffic". The dropdown underneath this table includes all Graphs avaibale for that SNMP Data Query, including a 64bit Traffic Graph
Reinhard

_k4 · Post by **_k4** » Thu Feb 26, 2009 4:51 am

I created 64 bit graph, but it's empty

On screenshot there are 2 graphs: upper - In/Out BITS (64 bit), another - default In/Out BITS

Is this known problem or it is something special with summit x450 switch?

_k4 · Post by **_k4** » Thu Feb 26, 2009 5:22 am

mm... strange... 64 bit counter solved problem with GGSN (JunOS), but problem with summit's and NetScreen's (ISG-2000) graphs is steel present.

Jacket · Post by **Jacket** » Thu Feb 26, 2009 5:28 am

It seems that your devices doesn't support 64bit counters. I have the same problem here, and the only solution is to switch to 1 minute polling interval. That will give you about 400Mbps speeds, and then the counters will flip again...
It's fine for me because my 1gb equipment without 64bit counters rarely exceeds 300Mbps.

Sadly switching from 5 minute to 1 minute polling interval isn't painless... You will have to recreate all graphs, and i my case i had about 13 000 graphs, so i made a script to recreate them. Unfortunately my script is exclusive to my case, because i have a repository with the switches, and have used it to repopulate all my hosts in cacti.

Post by **TheWitness** » Fri Feb 27, 2009 5:35 pm

You should also check the max values in your RRDfiles. One thing that happens from time to time is that a user starts doing the 64bit counters, but the Max value of the RRDfile zero's out the data in the RRDfile anyway.

If this is the case, you can use RRDtool to increase the maximum value in the RRDfile.

TheWitness

_k4 · Post by **_k4** » Mon Mar 02, 2009 5:31 am

TheWitness wrote: If this is the case, you can use RRDtool to increase the maximum value in the RRDfile.

TheWitness

ok, I increased max value in rrdfile of this graph using rrdtool from cli:

root@radius-rnd1 # /usr/local/rrdtool-1.2.19/bin/rrdtool tune cisco_72064.rrd -a traffic_in:10000000000.0000
root@radius-rnd1 # /usr/local/rrdtool-1.2.19/bin/rrdtool tune cisco_72064.rrd -a traffic_out:10000000000.0000
root@radius-rnd1 # /usr/local/rrdtool-1.2.19/bin/rrdtool tune cisco_72064.rrd
DS[traffic_in] typ: COUNTER hbt: 600 min: 0.0000 max: 10000000000.0000
DS[traffic_out] typ: COUNTER hbt: 600 min: 0.0000 max: 10000000000.0000

I think it have the same effect when I change max value from cacti.

finally, I have no result. Graph is steel clear. What was wrong?
Thx.

Cacti

Problems with graph when traff is more than 114 mbit.

Problems with graph when traff is more than 114 mbit.

Who is online