Traffic graphs in bytes instead of bits

[adfire]

I created new graphs using build in templates for interface traffic - by default it is bits/second. Graphs are created but they show values in bytes/second ! For sure, triple checked.
What is quite interesting - on bits/second graphs when I chose realtime graph - traffic is in bits/second, not in bytes/second as on 'base' graph.
I chose 64-bit counters - the same. I chose bytes/second - values are approximitly 10-times lower than real traffic.


What is going on ? I really don't understand.
Cacti ver. 1.1

Thanks in advance for any help.

[Rno]

I have to agree with you

For my understanding if you look into Data Queries -> SNMP - Interface Statistics
In/Out Bits Interface - Traffic (bits/sec) 13
In/Out Bits with 95th Percentile Interface - Traffic (bits/sec, 95th Percentile) 20
In/Out Bits with Total Bandwidth Interface - Traffic (bits/sec, Total Bandwidth) 21
In/Out Bytes Interface - Traffic (bytes/sec) 16
In/Out Bytes (64-bit Counters) Interface - Traffic (bytes/sec) 9
In/Out Bytes with Total Bandwidth Interface - Traffic (bytes/sec, Total Bandwidth) 22
In/Out Errors/Discarded Packets Interface - Errors/Discards 2
In/Out Non-Unicast Packets Interface - Non-Unicast Packets 3
In/Out Unicast Packets Interface - Unicast Packets 4

The 64 bit counter display in bytes !?
I re-create my on template to correct this

[darkng]

Hi,

I have the same problem with the new version of Cacti.

For example on the graphs i see this values below. But when i do a realtime graph then i see it 10times bigger than that.

[Cramin]

Standard SNMP - Interface Statistics

Code: Select all

In/Out Bits 	Interface - Traffic (bits/sec) 	10 	
In/Out Bits (64-bit Counters) 	Interface - Traffic (bits/sec) 	2 	
In/Out Bits (64-bit Counters) with 95th Percentile 	Interface - Traffic (bits/sec, 95th Percentile) 	7 	
In/Out Bits (64-bit Counters) with Total Bandwidth 	Interface - Traffic (bits/sec, Total Bandwidth) 	3 	
In/Out Bits with 95th Percentile 	Interface - Traffic (bits/sec, 95th Percentile) 	13 	
In/Out Bits with Total Bandwidth 	Interface - Traffic (bits/sec, Total Bandwidth) 	14 	
In/Out Bytes 	Interface - Traffic (bytes/sec) 	12 	
In/Out Bytes (64-bit Counters) 	Interface - Traffic (bytes/sec) 	9 	
In/Out Bytes (64-bit Counters) with Total Bandwidth 	Interface - Traffic (bytes/sec, Total Bandwidth) 	15 	
In/Out Bytes with Total Bandwidth 	Interface - Traffic (bytes/sec, Total Bandwidth) 	6 	
In/Out Errors/Discarded Packets 	Interface - Errors/Discards 	8 	
In/Out Non-Unicast Packets 	Interface - Non-Unicast Packets 	1 	
In/Out Unicast Packets 	Interface - Unicast Packets 	4 	
Interface - Broadcast Packets (Legacy) 	Interface - Broadcast Packets (Legacy) 	11 	
Interface - Multicast Packets (Legacy) 	Interface - Multicast Packets (Legacy) 	5 	

How do you create graphs?

[Rno]

That's not the standard one, it's your creation!!
And the second one is suppose to be the 64bits counter, in bits mode!!

To create a graph take another Interface traffic graph template, it would be the easiest way

[Cramin]

That's not the standard one, it's your creation!!

No it's not!
Cacti 1.1.2

[zetoo]

Teach me how to populate graph ..

My Cacti graph template wont populating again after upgrade to 1.0.x

[Rno]

That's not the standard one, it's your creation!!

No it's not!
Cacti 1.1.2

Whoo cool I have 1.1.0
sorry about that !!

[adfire]

In my case, graphs are created by default, without any changes, anywhere.

On a device: data query - interface statistics, then create graphs for this device - by default bits/second.

Devices are different - switches, routers, servers, NAS... everywhere the same.

So what should I do, how to create graphs to show traffic in bits/second ?

[Rno]

Not sure the default is 64bits counters

That's why we may need other graph

[adfire]

No, the default is not 64 bit counters.

What other graph we may need ? Rno, I truly don't understand you since the beggining of that topic.

[Cramin]

I use Traffic and Errors/Discards.

[Osiris]

Keep in mind folks, it's not the id, it's the hash that is important.