We are trying to attach Our IT Watchdog temperature sensors.

They can communicate with Snmp, over the network. It ha a V1 Trap and V2C Notify feature. It appears as if they are able to send the data out, but we can't find a way for PTRG to accept the data.

Here is the product. http://www.itwatchdogs.com/temperature-humidity-climate-monitor-watchdog-15poe-p72.html Here is the manual for the sensors. http://www.itwatchdogs.com/DataSheets/WatchDog-15_User_Manual_(rev_A1.02).pdf

Article Comments

Dear bishop,

I have some questions. Which version of PRTG are you using? The newest version offers a good SNMP trap sensor: https://www.paessler.com/manuals/prtg/snmp_trap_receiver_sensor.htm


Mar, 2014 - Permalink

We are usingPRTG Network Monitor 14.1.8.1371


Mar, 2014 - Permalink

In this case, please use the SNMP trap sensor as linked in the previous reply (https://www.paessler.com/manuals/prtg/snmp_trap_receiver_sensor.htm)

According to the documentation of your Watchdog device, a tool delivered with that device is able to send test traps.

If the test fails, please take screenshots and contact us.


Mar, 2014 - Permalink

Hi Support,

We are also considering using Watchdog 15 in our environment and we run version 14.1.8.2113.

Has there been additional information on the issue jbishop was experiencing with regards to getting their watchdog 15 configured with PRTG for snmp traps?

Thanks for the update.

Nate


Jun, 2014 - Permalink

Dear Nate

"14.1.8.2113" is no existing PRTG version. Can you double-check which PRTG you are using?

In addition, please allow me to ask you to clarify your issue. What exactly do you want to know?


Jun, 2014 - Permalink

Hi Arne, sorry I had the wrong version. We have 14.2.10.2113 installed.

We want to know if you know if the prior poster on this thread (jbishop) was able to successfully use watchdog 15 with PRTG.

We were hoping to know that as part of our consideration to purchase watchdog 15 vs others like Poseidon and Jacarta.

Thanks

Nate


Jun, 2014 - Permalink

Is there an update for this? I cannot get the PRTG to pull data from my Watchdog 15P or from my Black Box ServSensorJR. The error is -2003. I have used the MIB importer to get the right OID from the watchdog but it won't pull data.

If I am supposed to use the trap receiver, how can I set it up to display just the temp and humidity results that I want. Currently I only see the traps per hour and drops etc which is of zero use.

PRTG Network Monitor 15.1.13.1382+

Thanks Simon


Mar, 2015 - Permalink

Dear Skay

The exported oidlib files are XML structures. It contains the OID in plaintext. Please contact the manufacturer of the device about the OID you need to monitor temperature and humidity and check if these OIDs are part of the oidlib file.

If you cannot find those OIDs, please either ask the manufacturer to get the complete MIB library, or use the PRTG SNMP Custom Sensor to manually add the OID to your monitoring.


Mar, 2015 - Permalink

I have the OIDs. I have several custom sensors set up that work just fine. I have a hard time imagining that both the Black box unit and the Watchdog units are at fault. I have the complete MIB files and have even imported them into PRTG to try and get this to work with no success. I have seen replies about previous versions of the watchdog product working with PRTG but nobody seems to be able to get this device to work.

I have the right OID. It's just not pulling into PRTG. What next?


Mar, 2015 - Permalink

Dear Skay

Please use the SNMP Tester to read an OID outside of PRTG. Are you getting a result, or an error message (which one?)


Mar, 2015 - Permalink

Same error -2003.


Mar, 2015 - Permalink

Dear Simon

Error -2003 means SNMP Timeout. Please increase the timeout value and check if you can query the device.


Mar, 2015 - Permalink

I finally found the resolution. The Black Box device will only use SNMP1 so I have to convert the custom sensor to use snmp1 and use the OID I found in the paessler snmp tester. For the Watchdog it can use snmpv2 but you have to run the tester in v2 to get the right OID there also. Both devices are now reporting as they should.


Apr, 2015 - Permalink