Traffic Graphs are not showing the accurate usage- version 1.2.10

[Saji1980]

Hi!

I have 1G and 10G interfaces on FortiGate Firewall, Aruba switch and Dlink switch.
None of them are showing the correct graphs.

I have In/Out Bits (64-bit) graphs and snmpv2 selected in the device option.
I am taking D-Link example.

snmpwalk -OS -c mycommunity -v 2c 10.9.x.x .1.3.6.1.2.1.31.1.1.1.6.17

IF-MIB::ifHCInOctets.17 = Counter64: 2093929568340

snmpwalk -OS -c mycommunity -v 2c 10.9.x.x .1.3.6.1.2.1.31.1.1.1.10.17
IF-MIB::ifHCOutOctets.17 = Counter64: 510225986700

The tree view doesnt show traffic more thank 180M but if I run the live view and run iperf to test then I can see 500M.
See the graphs.
rrdtool info dlink-10g_traffic_in_21.rrd
filename = "dlink-10g_traffic_in_21.rrd"
rrd_version = "0003"
step = 300
last_update = 1585854901
header_size = 5216
ds[traffic_in].index = 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+10
ds[traffic_in].last_ds = "177741792737139"
ds[traffic_in].value = 5.7011157860e+06
ds[traffic_in].unknown_sec = 0
ds[traffic_out].index = 1
ds[traffic_out].type = "COUNTER"
ds[traffic_out].minimal_heartbeat = 600
ds[traffic_out].min = 0.0000000000e+00
ds[traffic_out].max = 1.0000000000e+10
ds[traffic_out].last_ds = "1868734635284088"
ds[traffic_out].value = 1.4550467552e+07
ds[traffic_out].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 600
rra[0].cur_row = 441
rra[0].pdp_per_row = 1
rra[0].xff = 5.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[0].cdp_prep[1].value = NaN
rra[0].cdp_prep[1].unknown_datapoints = 0
rra[1].cf = "AVERAGE"
rra[1].rows = 700
rra[1].cur_row = 556
rra[1].pdp_per_row = 6
rra[1].xff = 5.0000000000e-01
rra[1].cdp_prep[0].value = 1.7148943324e+07
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[1].cdp_prep[1].value = 4.5255043845e+07
rra[1].cdp_prep[1].unknown_datapoints = 0
rra[2].cf = "AVERAGE"
rra[2].rows = 775
rra[2].cur_row = 746
rra[2].pdp_per_row = 24
rra[2].xff = 5.0000000000e-01
rra[2].cdp_prep[0].value = 8.5017060609e+07
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[2].cdp_prep[1].value = 1.9207487433e+08
rra[2].cdp_prep[1].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 797
rra[3].cur_row = 518
rra[3].pdp_per_row = 288
rra[3].xff = 5.0000000000e-01
rra[3].cdp_prep[0].value = 1.6457638556e+08
rra[3].cdp_prep[0].unknown_datapoints = 202
rra[3].cdp_prep[1].value = 3.7645466428e+08
rra[3].cdp_prep[1].unknown_datapoints = 202
rra[4].cf = "MIN"
rra[4].rows = 600
rra[4].cur_row = 517
rra[4].pdp_per_row = 1
rra[4].xff = 5.0000000000e-01
rra[4].cdp_prep[0].value = NaN
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[4].cdp_prep[1].value = NaN
rra[4].cdp_prep[1].unknown_datapoints = 0
rra[5].cf = "MIN"
rra[5].rows = 700
rra[5].cur_row = 196
rra[5].pdp_per_row = 6
rra[5].xff = 5.0000000000e-01
rra[5].cdp_prep[0].value = 5.6362265495e+06
rra[5].cdp_prep[0].unknown_datapoints = 0
rra[5].cdp_prep[1].value = 1.2185822970e+07
rra[5].cdp_prep[1].unknown_datapoints = 0
rra[6].cf = "MIN"
rra[6].rows = 775
rra[6].cur_row = 471
rra[6].pdp_per_row = 24
rra[6].xff = 5.0000000000e-01
rra[6].cdp_prep[0].value = 5.6350293828e+06
rra[6].cdp_prep[0].unknown_datapoints = 0
rra[6].cdp_prep[1].value = 1.2185822970e+07
rra[6].cdp_prep[1].unknown_datapoints = 0
rra[7].cf = "MIN"
rra[7].rows = 797
rra[7].cur_row = 189
rra[7].pdp_per_row = 288
rra[7].xff = 5.0000000000e-01
rra[7].cdp_prep[0].value = 5.6350293828e+06
rra[7].cdp_prep[0].unknown_datapoints = 202
rra[7].cdp_prep[1].value = 1.2175182657e+07
rra[7].cdp_prep[1].unknown_datapoints = 202
rra[8].cf = "MAX"
rra[8].rows = 600
rra[8].cur_row = 114
rra[8].pdp_per_row = 1
rra[8].xff = 5.0000000000e-01
rra[8].cdp_prep[0].value = NaN
rra[8].cdp_prep[0].unknown_datapoints = 0
rra[8].cdp_prep[1].value = NaN
rra[8].cdp_prep[1].unknown_datapoints = 0
rra[9].cf = "MAX"
rra[9].rows = 700
rra[9].cur_row = 33
rra[9].pdp_per_row = 6
rra[9].xff = 5.0000000000e-01
rra[9].cdp_prep[0].value = 5.8108615236e+06
rra[9].cdp_prep[0].unknown_datapoints = 0
rra[9].cdp_prep[1].value = 1.8492192959e+07
rra[9].cdp_prep[1].unknown_datapoints = 0
rra[10].cf = "MAX"
rra[10].rows = 775
rra[10].cur_row = 561
rra[10].pdp_per_row = 24
rra[10].xff = 5.0000000000e-01
rra[10].cdp_prep[0].value = 5.8108615236e+06
rra[10].cdp_prep[0].unknown_datapoints = 0
rra[10].cdp_prep[1].value = 1.8492192959e+07
rra[10].cdp_prep[1].unknown_datapoints = 0
rra[11].cf = "MAX"
rra[11].rows = 797
rra[11].cur_row = 424
rra[11].pdp_per_row = 288
rra[11].xff = 5.0000000000e-01
rra[11].cdp_prep[0].value = 5.8932895888e+06
rra[11].cdp_prep[0].unknown_datapoints = 202
rra[11].cdp_prep[1].value = 2.4268517157e+07
rra[11].cdp_prep[1].unknown_datapoints = 202
rra[12].cf = "LAST"
rra[12].rows = 600
rra[12].cur_row = 207
rra[12].pdp_per_row = 1
rra[12].xff = 5.0000000000e-01
rra[12].cdp_prep[0].value = NaN
rra[12].cdp_prep[0].unknown_datapoints = 0
rra[12].cdp_prep[1].value = NaN
rra[12].cdp_prep[1].unknown_datapoints = 0
rra[13].cf = "LAST"
rra[13].rows = 700
rra[13].cur_row = 664
rra[13].pdp_per_row = 6
rra[13].xff = 5.0000000000e-01
rra[13].cdp_prep[0].value = 5.7018552509e+06
rra[13].cdp_prep[0].unknown_datapoints = 0
rra[13].cdp_prep[1].value = 1.4577027916e+07
rra[13].cdp_prep[1].unknown_datapoints = 0
rra[14].cf = "LAST"
rra[14].rows = 775
rra[14].cur_row = 411
rra[14].pdp_per_row = 24
rra[14].xff = 5.0000000000e-01
rra[14].cdp_prep[0].value = 5.7018552509e+06
rra[14].cdp_prep[0].unknown_datapoints = 0
rra[14].cdp_prep[1].value = 1.4577027916e+07
rra[14].cdp_prep[1].unknown_datapoints = 0
rra[15].cf = "LAST"
rra[15].rows = 797
rra[15].cur_row = 446
rra[15].pdp_per_row = 288
rra[15].xff = 5.0000000000e-01
rra[15].cdp_prep[0].value = 5.7018552509e+06
rra[15].cdp_prep[0].unknown_datapoints = 202
rra[15].cdp_prep[1].value = 1.4577027916e+07
rra[15].cdp_prep[1].unknown_datapoints = 202

I even tried tune option which I found but it didnt help.
rrdtool tune dlink-10g_traffic_in_21.rrd -a traffic_out:10000000000
rrdtool tune dlink-10g_traffic_in_21.rrd -a traffic_in:10000000000

Anyone can help with this issue?

Thanks

[Saji1980]

Anyone who can give some tip?

[netniV]

There are a few things to check, such as:

• The returned value is not exceeding the data source defined maximum value
• You don't have other devices timing out thus preventing the poller from making it to the remaining sources
• You have actually got a value being returned from the data source
• etc.

[TheWitness]

In the just released 1.2.11, you can modify the Traffic Data Template and change the MAX value to |query_ifSpeed|, after that, you should run the Data Debugger and find the RRDfiles that have an incorrect MAX value. Though note that some VIP's and bonded interfaces report an incorrect ifSpeed or ifHighSpeed.

[Saji1980]

Thanks. Is it possible to do that in 1.2.10?
1.2.11 is still not available via yum on Centos7.

[Saji1980]

Why its becoming to much issue with simple graphs .
It used to be very easy before.

[Osiris]

I think what happened was that somehow the packages lost a setting that calculated the max speed if the interfaces setting somehow. We have to republish the working package. Someone needs to research it.

[Saji1980]

Is the new package is available without any issue or you can please mention the best stable release?

[Saji1980]

Hi!

Can anyone please help in this. Now I have 1.2.11 and still the graphs can only go to 100MB. Where I have to add this ifspeed value. Please help.
thanks

[Saji1980]

are you referring to this?