Snmpget probe triggers alarme when the actual values are below the threshold configuration. NsMemoryUsage is now '9.28', (>= 80.00)"s
search cancel

Snmpget probe triggers alarme when the actual values are below the threshold configuration. NsMemoryUsage is now '9.28', (>= 80.00)"s

book

Article ID: 8889

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

  • The snmpget probe is generating an alarm that should not exist.
  • "The SNMP OID 'enterprises.netScaler.masRoot.deviceGroup.netscalerTable.netscalerEntry.nsNsMemoryUsage"' for device 1.1.1.1 is now '9.99' (Threshold: >= 80.00)."
  • As you can see, the threshold (80.00) is greater than the polled value (9.99).

 

Environment

  • Any snmpget probe version

Cause

  • The polled value is an OctetString and the threshold value is an integer.

Resolution

Get the Mib and check the OID to see if is a OctetString as below:

1.3.6.1.4.1.5951.7.3.2.1.35.1.4.172.28.172.18.1.4.172.28.172.12, OctetString

You cannot do a numeric comparison on a string value.

OctetString can be compared as "=" or "!=" but you cannot compare with numbers like ">=" or "<="

Additional Information

https://users.cs.cf.ac.uk/Dave.Marshall/PERL/node37.html