Closed stefangweichinger closed 2 years ago
Hi.
These normally happens when the system did not use the OID for memory as expected. What kind of device is your client 10.0.0.134? You should get more details just by adding the -v argument.
Greetings, Steffen
Unfortunately "-v" doesnt give anything, see my example. I will try to check the OIDs etc
The device is a HSM appliance of a rather young company, the implementation of SNMP is still quite raw.
I find these in snmpwalk:
.iso.3.6.1.2.1.25.2.3.1.3.1 = STRING: "Physical memory"
.iso.3.6.1.2.1.25.2.3.1.3.3 = STRING: "Virtual memory"
.iso.3.6.1.2.1.25.2.3.1.3.6 = STRING: "Memory buffers"
.iso.3.6.1.2.1.25.2.3.1.3.7 = STRING: "Cached memory"
.iso.3.6.1.2.1.25.2.3.1.3.8 = STRING: "Shared memory"
.iso.3.6.1.2.1.25.2.3.1.3.10 = STRING: "Swap space"
Would that help me to patch the script maybe? I assume I would have to look up the values as well, still learning ...
I solved it by using /usr/lib/nagios/plugins/check_snmp_storage.pl
instead: the appliance has the RAM-related values there.
thanks
Expected Behavior
Get correct memory values reported.
Current Behavior
I try this:
Possible Solution
Maybe the implemented OIDs don't match the ones requested by the script?
Steps to Reproduce (for bugs)
Your Environment
check_snmp_int.pl -V
): 2.1.0perl -v
): v5.32.1icinga2 --version
): icinga2 r2.12.3-1