Hi,

I cannot use PRTG to monitor the CPU usage via SNMP. I used the tester and here is the return.

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.2
3/10/2016 3:18:17 PM (1 ms) : Device: 10.68.24.152
3/10/2016 3:18:17 PM (10 ms) : SNMP V1
3/10/2016 3:18:17 PM (11 ms) : Uptime
3/10/2016 3:18:17 PM (19 ms) : SNMP Datatype: ASN_PRIMITIVE
3/10/2016 3:18:17 PM (21 ms) : -------
3/10/2016 3:18:17 PM (22 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = Could not create SNMP Session (-3000)-2011 ( 0 seconds )
3/10/2016 3:18:17 PM (24 ms) : SNMP Datatype: ASN_PRIMITIVE
3/10/2016 3:18:17 PM (25 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = Could not create SNMP Session (-3000)-2011 ( 0 seconds )
3/10/2016 3:18:17 PM (34 ms) : Done

What should I do?

Article Comments

Hi nonamehaha

Need more info. What kind of device is it?

regards Thomas


Mar, 2016 - Permalink

As Thomas already wrote, it would help to know which kind of device it is, since Could not create SNMP Session can also have a lot of reasons.

Kind regards.


Mar, 2016 - Permalink

Hi, I too am experiencing this issue. It was working a few days ago, but after windows patches on the destination server, the sensor showed paused. I checked SNMP services and it shows up.

Ran the tester... Paessler SNMP Tester 5.2.2 5/23/2016 8:10:28 AM (7 ms) : Device: OMITTED... 5/23/2016 8:10:28 AM (11 ms) : SNMP V2c 5/23/2016 8:10:28 AM (15 ms) : Uptime 5/23/2016 8:10:31 AM (2833 ms) : SNMP Datatype: ASN_PRIMITIVE 5/23/2016 8:10:31 AM (2838 ms) : ------- 5/23/2016 8:10:31 AM (2842 ms) : DISMAN-EVENT-MIB::sysUpTimeInstance = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds ) 5/23/2016 8:10:34 AM (5828 ms) : SNMP Datatype: ASN_PRIMITIVE 5/23/2016 8:10:34 AM (5834 ms) : HOST-RESOURCES-MIB::hrSystemUptime.0 = No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds ) 5/23/2016 8:10:34 AM (5840 ms) : Done

Any clue what's going on? should I reboot the probe? I had already restarted services on the Probe but that didn't work...

Thanks in Advance!


May, 2016 - Permalink

Hi cmu,

I would at least try one reboot to see if that helps, though I think the root is something else, when this occurs only with one target. Check the details of the SNMP service on the target server. It must be configured to respond to SNMP requests from other devices (should be tab "Security" inside the SNMP service). Try also restarting the SNMP service after making sure that the settings are correct.

Besides that, do you have a Ping sensor on the device and is it reaching it successfully? If that works, then maybe something in between blocks SNMP traffic. You could run a Wireshark Trace while performing a few queries with SNMP tester and then filter the traffic for port 162 and UDP to see what happens.

Kind regards.


May, 2016 - Permalink