Good morning,
We recently noticed that SNMP is having difficulty handling large file sysystem. We have a 120TB XFS system that is reporting on 4.4TB and alerting because SNMP is reporting the wrong values.
snmpwalk -mALL -v2c -{COM} {HOST} hrStorageTable | grep 40HOST-RESOURCES-MIB::hrStorageIndex.40 = INTEGER: 40HOST-RESOURCES-MIB::hrStorageType.40 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDiskHOST-RESOURCES-MIB::hrStorageDescr.40 = STRING: /homeHOST-RESOURCES-MIB::hrStorageAllocationUnits.40 = INTEGER: 4096 Bytes
HOST-RESOURCES-MIB::hrStorageSize.40 = INTEGER: 1186465536HOST-RESOURCES-MIB::hrStorageUsed.40 = INTEGER: 1036605829HOST-RESOURCES-MIB::hrStorageUsed.44 = INTEGER: 666446640Some forums have indicated this can be resolved by upgrading to 64 bit integers but I am not an SNMP expert.
Has anyone seen this behavior and if so how do we work around it? In the HPC world this is a small name space so I worry about monitoring storage on our Lustre FS.
Thanks
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium