Unable to monitor memory size grater then 2 TB
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Unable to monitor memory size grater then 2 TB
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.
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.
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Re: Unable to monitor memory size grater then 2 TB
check_snmp_storage_wizard.pl is used
showing wrong CRITICAL %
Physical memory: 185%used(3723200MB/2010848MB) (>80%) : CRITICAL
showing wrong CRITICAL %
Physical memory: 185%used(3723200MB/2010848MB) (>80%) : CRITICAL
Re: Unable to monitor memory size grater then 2 TB
If net-snmp is your only option, it looks like you may be out of luck:
https://sourceforge.net/p/net-snmp/mail ... /35978443/
https://sourceforge.net/p/net-snmp/mail ... /35978443/
Might be worth looking into NCPA to get more accurate measurements.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:
Former Nagios employee
https://www.mcapra.com/
https://www.mcapra.com/
Re: Unable to monitor memory size grater then 2 TB
This is a known issue. As mcapra suggested - it might be worth giving NCPA a try.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Re: Unable to monitor memory size grater then 2 TB
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?
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?
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Re: Unable to monitor memory size grater then 2 TB
which file to add to the data you have given now? (2^32)
Re: Unable to monitor memory size grater then 2 TB
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.
https://github.com/dnsmichi/manubulon-s ... storage.pl
Give it a try and post back the results.
Here is the link to the updated plugin.# 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.
https://github.com/dnsmichi/manubulon-s ... storage.pl
Give it a try and post back the results.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Re: Unable to monitor memory size grater then 2 TB
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
The link to the plugin is already updated so if you overwrote the existing plugin with the new one, that should be enough.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
progressive.nagiosXI
- Posts: 277
- Joined: Mon Jul 31, 2017 5:54 am
Re: Unable to monitor memory size grater then 2 TB
No Success team,
Is there any way we can do this.
Is there any way we can do this.