When you open up the functions list and look at the OID function you see the following description…
Returns value of given snmp OID. Only first parameter mandatory.
First parameter - oid string,
second - cache time - default 5 seconds (5.0),
third - negative cache time - default 5 minutes (300.0),
forth - ip address (overrides context device),
fifth - snmp profile (overrides context device)
So I am curious if that default negative cache time is buggy! I am probing the cpu on my device every 30 seconds. Right after a “CPU DOWN” event if I hover on the device, SNMP clearly shows the device location, description and other SNMP information at the same time it claims that the CPU is down which is also an SNMP read…
What I am guessing here is that negative cache time is being stored for a failed read and subsequent reads of the CPU fail for both “REPROBE” and the remaining 9 CPU reads that should have worked but because negative cache time is active the probe shows as down for the duration of negative cache time. If that is the case shouldn’t negative cache time be equal to the probe interval?
Is there a problem with negative cache? See the graphic the probe is down for ~5 minutes. It seems that every “False Positive” probe that relies on an OID is always down for about 4:30…
On another note you should be able to place
[oid(“1.3.6.1.4.1.9.2.1.57.0”), 5, 300, 192.168.1.1, public] on the label of any device and show the cisco cpu in this case of the target device.
I tried various forms of this and could not get it to work as well. Such as…
[oid(“1.3.6.1.4.1.9.2.1.57.0, 5, 300, 192.168.1.1, public”)]
Is the parsing of the OID values broken?
Any time I add a new device I start getting random false positives. I have to get on the server, restart the service and force priority to real time. Then it runs great until I add another device… Please look into this.
TIA
SD