TECHZEN Zenoss User Community ARCHIVE  

[Zenoss 4.2.5] No values returned for configured oids

Subject: [Zenoss 4.2.5] No values returned for configured oids
Author: [Not Specified]
Posted: 2015-01-29 11:53

Hello fellow Zenoss-ers!

I recently setup a Sensatronics EM1 Temperature Monitor and am using SNMP to poll the device for temperature data but I am getting a "No values returned for configured oids" event for the device but everything seems to be setup correctly in that the test device function is returning SNMP data from the device. See this link.

Meaning that when I setup the OID's in the Monitoring Templates section of Zenoss, I am able to use the test feature to get valid SNMP data back. It comes back as an Integer. I have also created my Graph and Thresholds to what they should be. See here. See also here.

This is not my first redeo as I have made data points before but this one I am just not understanding why it is not getting data. I can also verfy that SNMPwalk from the command line is also returning valid temperature data.

What else do you need to help diagnose this error as far as logs, etc. Is the problem because it is returning an INTEGER value help, I am at a loss here.




Subject: Hello.
Author: ValeruS
Posted: 2015-01-31 17:32

Hello.
For test can you include full oid with "0" (.0) in OID field. From the image oid terminate with .0




Subject: The Full OID's that I am
Author: [Not Specified]
Posted: 2015-02-04 09:32

The Full OID's that I am using (and appear to work in both the SNMP Walk command line and also in the Zenoss "Test" screen) are:
Temperature: 1.3.6.1.4.1.16174.1.1.3.3.3.4
Humidity: 1.3.6.1.4.1.16174.1.1.3.3.3.7




Subject: Solved Issue
Author: [Not Specified]
Posted: 2015-02-14 21:30

So that there is a record of it, the solution to the above problem was because it was returning an Integer value, apparently it has to be a different OID that returns a string value. Still don't know why but that was the solution.




< Previous
How to use pdb with zenmodeler
  Next
Error in event.log
>