Page 1 of 2
Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 1:11 am
by progressive.nagiosXI
Hi Team,
We are not able to monitor Memory usage of servers haveing memory size greater then 2 TB,
can you please help in this we have a lot of production servers with more then 2 TB memory and Space.
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 8:18 am
by progressive.nagiosXI
check_snmp_storage_wizard.pl is used
showing wrong CRITICAL %
Physical memory: 185%used(3723200MB/2010848MB) (>80%) : CRITICAL
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 9:10 am
by mcapra
If net-snmp is your only option, it looks like you may be out of luck:
https://sourceforge.net/p/net-snmp/mail ... /35978443/
Nobody will ever change the type of an existing OID as it would break compatibility.
The maximum amount you can represent with a signed 32-bit integer is about 1.98TiB.
Maybe just add 2^32 in the meantime:
Might be worth looking into
NCPA to get more accurate measurements.
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 9:35 am
by lmiltchev
This is a known issue. As mcapra suggested - it might be worth giving NCPA a try.
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 11:21 am
by progressive.nagiosXI
Nobody will ever change the type of an existing OID as it would break compatibility.
The maximum amount you can represent with a signed 32-bit integer is about 1.98TiB.
Maybe just add 2^32 in the meantime:
i want to know where can i add 2^32 in which file?
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 11:29 am
by progressive.nagiosXI
which file to add to the data you have given now? (2^32)
Re: Unable to monitor memory size grater then 2 TB
Posted: Mon Oct 15, 2018 11:55 am
by tgriep
There is an updated plugin that may work for for you. It has some changes added to it to take account for systems that are larger that 2TB.
# Fix for filesystems larger 2 TB. More than 2 TB will cause an error because
# as defined in the RFC hrStorageSize is a 32 bit integer. So filesystems
# larger 2 TB report a negative value because the first bit will be interpreted
# as an algebraic sign. (0 = +, all others will be -). You simply have to add
# 2 to the power of 32 (4294967296) and it is fixed.
Here is the link to the updated plugin.
https://github.com/dnsmichi/manubulon-s ... storage.pl
Give it a try and post back the results.
Re: Unable to monitor memory size grater then 2 TB
Posted: Wed Oct 17, 2018 3:24 pm
by progressive.nagiosXI
Tried this pluging but the results is same. Can you please confirm do we need to edit this updated plugin or its already edited
Re: Unable to monitor memory size grater then 2 TB
Posted: Wed Oct 17, 2018 3:36 pm
by tgriep
The link to the plugin is already updated so if you overwrote the existing plugin with the new one, that should be enough.
Re: Unable to monitor memory size grater then 2 TB
Posted: Tue Oct 30, 2018 12:25 pm
by progressive.nagiosXI
No Success team,
Is there any way we can do this.