Cacti

Has there been any further development on this? Nope, as Gandalf pointed out, and as I had suspected this isn't a problem with cacti. Rather it's a limitation of the old/standard snmpd MIB for reporting disk space which at the time probably didn't expect to ever see disks above 2 or 4 TB. I haven't...

Changing the MIB file does not help. The problem lies with the snmp agent on the target system Are you aware of a solution or work around? Is there an alternate MIB that can be used which supports larger values? Is there something that I can change in the snmpd client source such that recompiling i...

Editing the file UCD-SNMP-MIB.txt on the cacti server and replacing "Integer32" with "Counter64" for the "dskUsed" field(s) results in: UCD-SNMP-MIB::dskUsed.4 = Wrong Type (should be Counter64): INTEGER: -2147483648 I tried using Counter64 because it appears to be defi...

So on the Linux and BSD systems I've found these files: /usr/share/snmp/mibs/UCD-SNMP-MIB.txt or /usr/local/share/snmp/mibs/UCD-SNMP-MIB.txt and /usr/share/snmp/mibs/HOST-RESOURCES-MIB.txt or /usr/local/share/snmp/mibs/HOST-RESOURCES-MIB.txt Which contain lines such as DskEntry ::= SEQUENCE { ... ds...

I'm running Cacti Version 0.8.7b with SNMPv2 on and against a variety of platforms including Linux (Ubuntu & Debian), FreeBSD, and Windows (2000, XP, Vista). The problem I'm encountering is with disks larger than 2TB or 4TB. I believe that the problem is due to the 16 bit values that are returne...