I added a SNMP library to monitor the input, output and other parameters for a device. The problem is when I added the sensors, PRTG displays only one channel which is "response time" regardless of the sensor I create (I tried three sensors with the same result).
I checked the MIB file with the device vendor and they inform me no problem with it, and below is wireshark capture for the snmp request/response which clarify that the device is responding properly to the PRTG server with the actual value for each sensor. but the prtg show only one channel "response time" which is weird.
please advise about the reason and what is the solution to this problem.
Simple Network Management Protocol
version: v2c (1)
community: public
data: get-response (2)
get-response
request-id: 20101384
error-status: noError (0)
error-index: 0
variable-bindings: 1 item
1.3.6.1.4.1.18210.2.4.5.2.0: 322e30
Object Name: 1.3.6.1.4.1.18210.2.4.5.2.0 (iso.3.6.1.4.1.18210.2.4.5.2.0)
Value (OctetString): 322e30 (=> 2.0)
Simple Network Management Protocol
version: v2c (1)
community: public
data: get-response (2)
get-response
request-id: 20101417
error-status: noError (0)
error-index: 0
variable-bindings: 1 item
1.3.6.1.4.1.18210.2.4.3.2.0: 34352e34
Object Name: 1.3.6.1.4.1.18210.2.4.3.2.0 (iso.3.6.1.4.1.18210.2.4.3.2.0)
Value (OctetString): 34352e34 (=> 45.4)
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Well, basic strings - like test or Version 1.2.4 or integer/float values. Unsupported means that PRTG can't make anything of the values (i.e. can't interpret them), hence it's omitting them.
Jan, 2017 - Permalink
The values are stored as octet strings from what it looks like:
Unfortunately, PRTG does not support octet and hex string evaluation. That's why it's not working.
Jan, 2017 - Permalink