Hello, we appreciate your contact.
When you say that the Read Device Uptime from the tester works pretty good, which is the exact output of test in the SNMP Tester?
In addition to the Read Device Uptime test, kindly perform a Walk test using the following OID:
The result should be similar to this:
----------------------- New Test -----------------------
Paessler SNMP Tester 5.2
06:12:33 (2 ms) : Device: %yourdeviceaddr%
06:12:33 (4 ms) : SNMP V2c
06:12:33 (6 ms) : Walk 1.3.6.1.2.1.25.3.3.1.2
06:12:33 (9 ms) : 1.3.6.1.2.1.25.3.3.1.2.4 = "8" [ASN_INTEGER]
06:12:33 (11 ms) : 1.3.6.1.2.1.25.3.3.1.2.5 = "8" [ASN_INTEGER]
06:12:33 (14 ms) : 1.3.6.1.2.1.25.3.3.1.2.6 = "4" [ASN_INTEGER]
06:12:33 (17 ms) : 1.3.6.1.2.1.25.3.3.1.2.7 = "3" [ASN_INTEGER]
That displays the CPU utilization for each core, if that test fails, it means that the device isn't replying the values correctly/at all.
In some linux SNMP implementations you must manually configure the SNMP Agent after installation. This means to edit /etc/snmp/snmpd.conf and configure which hosts are allowed to query which OID's and which communities. It could be that the agent is restricting the queries to the CPU OID's, even with SNMP enabled and the uptime counters working.
Otherwise, please double check that the device's SNMP Credentials within PRTG match the settings that you're using within the tester.
Add comment