Graphs stops graphing at 800 Mb and above.
Moderators: Developers, Moderators
Graphs stops graphing at 800 Mb and above.
We have a very large link coming into our building and we need to graph the overall utilization. Recently we have started going over 800mb of traffic but the cacti graph stops at 799.19 and doesn't display anything on the graph for the period we were above 800 mb. I know we went about becasue we also run MRTG which registered 860mb. I have already changed the max value in the data sources thinking that the polled value was too high so cacti threw it out but that has not helped. Any insight into this problem would be greatly appreciated. And yes we are using 64 bit counters.
Thanks
Thanks
You need to use snmpv2 and 64bit counter/graphs.
| Scripts: Monitor processes | RFC1213 MIB | DOCSIS Stats | Dell PowerEdge | Speedfan | APC UPS | DOCSIS CMTS | 3ware | Motorola Canopy |
| Guides: Windows Install | [HOWTO] Debug Windows NTFS permission problems |
| Tools: Windows All-in-one Installer |
funny...
I didn't see your post but I have the same issue.
Everyone knows v1 "wraps" not clips, and it does it at 114 meg. We're talking about a 800meg clip, so traffic is not graphing at all above 800, not wrapping as it does with a counter issue.
Thoughts??? Witness?
Everyone knows v1 "wraps" not clips, and it does it at 114 meg. We're talking about a 800meg clip, so traffic is not graphing at all above 800, not wrapping as it does with a counter issue.
Thoughts??? Witness?
-
- Cacti User
- Posts: 66
- Joined: Tue Mar 22, 2005 10:11 am
ds[traffic_in].type = "COUNTER"
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+08
ds[traffic_in].last_ds = "735415651823554"
ds[traffic_in].value = 3.1941808307e+07
ds[traffic_in].unknown_sec = 0
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+08
ds[traffic_out].last_ds = "1357359187893217"
ds[traffic_out].value = 6.0441077673e+07
ds[traffic_out].unknown_sec = 0
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+08
ds[traffic_in].last_ds = "735415651823554"
ds[traffic_in].value = 3.1941808307e+07
ds[traffic_in].unknown_sec = 0
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+08
ds[traffic_out].last_ds = "1357359187893217"
ds[traffic_out].value = 6.0441077673e+07
ds[traffic_out].unknown_sec = 0
-
- Cacti User
- Posts: 66
- Joined: Tue Mar 22, 2005 10:11 am
so...
If I change this value
ds[traffic_out].max = 1.0000000000e+08
to be
ds[traffic_out].max = 1.0000000000e+09
I won't have this issue? Is there a direct coorelation between 100000000 and 800 m/bit of traffic?
I'll change it in hope that it works tomorrow, but would love this to be the definitive answer.
If I change this value
ds[traffic_out].max = 1.0000000000e+08
to be
ds[traffic_out].max = 1.0000000000e+09
I won't have this issue? Is there a direct coorelation between 100000000 and 800 m/bit of traffic?
I'll change it in hope that it works tomorrow, but would love this to be the definitive answer.
Thanks for the reply guys....
Has the tuning worked for anyone.
Here is the info on the rrd that is causing me issues.
filename = "7606router_traffic_in_681.rrd"
rrd_version = "0003"
step = 300
last_update = 1158585901
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+08
ds[traffic_out].last_ds = "650718223173704"
ds[traffic_out].value = 7.2017697515e+07
ds[traffic_out].unknown_sec = 0
ds[traffic_in].type = "COUNTER"
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+08
ds[traffic_in].last_ds = "18805417737438"
ds[traffic_in].value = 2.1167553110e+06
ds[traffic_in].unknown_sec = 0
Has the tuning worked for anyone.
Here is the info on the rrd that is causing me issues.
filename = "7606router_traffic_in_681.rrd"
rrd_version = "0003"
step = 300
last_update = 1158585901
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+08
ds[traffic_out].last_ds = "650718223173704"
ds[traffic_out].value = 7.2017697515e+07
ds[traffic_out].unknown_sec = 0
ds[traffic_in].type = "COUNTER"
ds[traffic_in].minimal_heartbeat = 600
ds[traffic_in].min = 0.0000000000e+00
ds[traffic_in].max = 1.0000000000e+08
ds[traffic_in].last_ds = "18805417737438"
ds[traffic_in].value = 2.1167553110e+06
ds[traffic_in].unknown_sec = 0
The correct tuning command should be:
The -a specifies that you are setting the max and the actual value goes after the colon.
Also, 800 Mbps = 100 MBps = 1.0000000000e+08 bytes so that is why the values are getting lost.
Code: Select all
tune /var/www/cacti/rra/gsrgw_traffic_in_272.rrd -a traffic_out:10000000000
Also, 800 Mbps = 100 MBps = 1.0000000000e+08 bytes so that is why the values are getting lost.
Hi all,
Since I have made this change the graph is working again but I am now noticing that as we approach 900 meg the graph is not displaying it properly. For example if 100 meg is represented by two grid blocks on the graph a value of 891 only occupies one grid block which would apear to be 850mb instead of 891. Is there a tuning value that has to be changed to accomidate and display the larger values on the graph?
Thanks.
Since I have made this change the graph is working again but I am now noticing that as we approach 900 meg the graph is not displaying it properly. For example if 100 meg is represented by two grid blocks on the graph a value of 891 only occupies one grid block which would apear to be 850mb instead of 891. Is there a tuning value that has to be changed to accomidate and display the larger values on the graph?
Thanks.
- Attachments
-
- graph.png (31.41 KiB) Viewed 5565 times
Who is online
Users browsing this forum: No registered users and 2 guests