Hi Rhian. Just use the latest netsnmp and it should be ok. I have 200Tb xfs and all ok. After upgrade. David
Sent from my Samsung device
-------- Original message -------- From: observium-request@observium.org Date: 13/12/2015 15:18 (GMT+01:00) To: observium@observium.org Subject: observium Digest, Vol 65, Issue 49
Send observium mailing list submissions to observium@observium.org
To subscribe or unsubscribe via the World Wide Web, visit http://postman.memetic.org/cgi-bin/mailman/listinfo/observium or, via email, send a message with subject or body 'help' to observium-request@observium.org
You can reach the person managing the list at observium-owner@observium.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of observium digest..."
Today's Topics:
1. SNMP and Large FileSystems (100TB+) (Rhian Resnick) 2. Re: SNMP and Large FileSystems (100TB+) (Tom Laermans) 3. Re: SNMP and Large FileSystems (100TB+) (Rhian Resnick)
----------------------------------------------------------------------
Message: 1 Date: Sun, 13 Dec 2015 13:41:39 +0000 From: Rhian Resnick rresnick@fau.edu To: Observium Network Observation System observium@observium.org Subject: [Observium] SNMP and Large FileSystems (100TB+) Message-ID: BL2PR04MB020A904E5733C4744FA572BCBEC0@BL2PR04MB020.namprd04.prod.outlook.com
Content-Type: text/plain; charset="iso-8859-1"
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 40 HOST-RESOURCES-MIB::hrStorageIndex.40 = INTEGER: 40 HOST-RESOURCES-MIB::hrStorageType.40 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk HOST-RESOURCES-MIB::hrStorageDescr.40 = STRING: /home HOST-RESOURCES-MIB::hrStorageAllocationUnits.40 = INTEGER: 4096 Bytes HOST-RESOURCES-MIB::hrStorageSize.40 = INTEGER: 1186465536 HOST-RESOURCES-MIB::hrStorageUsed.40 = INTEGER: 1036605829 HOST-RESOURCES-MIB::hrStorageUsed.44 = INTEGER: 666446640
Some 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
Rhian Resnick
Assistant Director Middleware and HPC
Office of Information Technology
Florida Atlantic University
777 Glades Road, CM22, Rm 218
Boca Raton, FL 33431
Phone 561.297.2647
Fax 561.297.0222
[image] https://hpc.fau.edu/wp-content/uploads/2015/01/image.jpg