Preprocessing steps order of Interface discovery "ifInOctets"

[rockaut]

Heja,

I have a maybe silly question but I just can't wrap my head around this. My network guys are complaining that the values presented in the graphs are wrong compared to PRTG/Cisco Tools.

I checked that the SNMP values I get are correct so I just found some older forum posts and also some other sites where the preprocessing steps are described as:
- multiply with 8
- changes per second
Sounds resonable as its "1.3.6.1.2.1.2.2.1.10.{#SNMPINDEX}" which is ifInOctets.

But then I check my templates and also the official ones where the two steps are actually swapped:
- changes per second
- multiply with 8

As I see it this shouldn't be a problem and especially not THE problem that the values/graphs displayed are wrong?

What do you guys have? Any ideas?

[isaqueprofeta]

The order of preprocessing doesn't really matter here. The Delta from "changes per second" vs multiply per 8 will have the same effect.

Oh man... you need to compare the PRTG/Cisco Tools OID with Zabbix OID. A clear example here is that you write about ifInOctets 1.3.6.1.2.1.2.2.1.10 (which are 32Bits counters and have a lot of errors in "high speed" interfaces)... but Zabbix uses ifHCInOctets 1.3.6.1.2.1.31.1.1.1.6 (which are 64Bits counters), if that's the case it's rather funny because Zabbix is right, and PRTG/Cisco Tools are outdated.