I want to monitor my JVM details and there fore i am using native SNMP interface. I try to follow instruction which appear in your knowledge base.

https://helpdesk.paessler.com/en/support/solutions/articles/59728-how-can-i-monitor-jvms-with-prtg

I download the MIB file and convert it to OID library using MIB importer.Then i copy the library to snmplibs folder and try to create a SNMP library sensor. In that process i am getting this error "No such object (SNMP error # 222)"

i downloaded your snmp tester tool and select "Read device uptime" and run test but results became as "NO response" for all snmp versions.when i give the created oidlib path to the "scan OIDLIB" option under "select request type" it gave me this result, "No OIDs found"

I am using windows XP operating system. What should i do to overcome these difficulties?Any help will be great.


Article Comments

Dear thiwankabsharp

I am sorry, Windows XP is no longer supported. You still can try to use the SNMP Tester to perform a Walk over 1.3.6.1 to see if you can read any OID, but we no longer offer any PRTG support for the Windows XP platform.


Jul, 2016 - Permalink

Thanks for the reply. i switched to the windows 10 did the same thing as above. This time "Read device uptime" worked fine. But when i give the created oidlib path to the "scan OIDLIB" option under "select request type" it gave me the sameresult, "No OIDs found" and same error "No such object (SNMP error # 222)" came when i tried to create the snmp library sensor.

I walk over 1.3.6.1 but result came as NO Response. What should i do?


Jul, 2016 - Permalink

Dear thiwankabsharp

Please try to manually read this OID: 1.3.6.1.2.1.1.3.0

Are you getting a result?


Jul, 2016 - Permalink

i am new to this. So manually reading means without using the snmp tester?


Jul, 2016 - Permalink

Dear thiwankabsharp

I mean to use the SNMP Tester. There is an option to read an OID. Please enter that OID and try to read it.


Jul, 2016 - Permalink

I did that and results cam like this.

Paessler SNMP Tester 5.2.3 Computername: DESKTOP-4OHEF27 Interface: (192.168.8.100) 7/7/2016 9:59:08 PM (1 ms) : Device: 192.168.8.100 7/7/2016 9:59:08 PM (2 ms) : SNMP V2c 7/7/2016 9:59:08 PM (2 ms) : Custom OID 1.3.6.1.2.1.1.3.0 7/7/2016 9:59:08 PM (4 ms) : SNMP Datatype: ASN_TIMETICKS 7/7/2016 9:59:08 PM (5 ms) : ------- 7/7/2016 9:59:08 PM (6 ms) : Value: 26173070 7/7/2016 9:59:08 PM (7 ms) : Done

what should i do?


Jul, 2016 - Permalink

Dear thiwankabsharp

This shows, that the uptime is readable. "Read device uptime" via the SNMP tester should work as well. Please check if that is possible, and/or check in PRTG if you entered wrong credentials. Please also check the device address in the PRTG device object on which you attached the sensor to.


Jul, 2016 - Permalink

yes device uptime is working fine. but when i give a custom oid like 1.3.6.1.4.1.42.2.145.3.163.1.1.3.2.0 it give a result like this

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: DESKTOP-4OHEF27 Interface: (192.168.8.100)
7/11/2016 12:38:08 AM (2 ms) : Device: 192.168.8.167
7/11/2016 12:38:08 AM (2 ms) : SNMP V2c
7/11/2016 12:38:08 AM (3 ms) : Custom OID 1.3.6.1.4.1.42.2.145.3.163.1.1.3.2.0
7/11/2016 12:38:08 AM (4 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
7/11/2016 12:38:08 AM (5 ms) : -------
7/11/2016 12:38:08 AM (6 ms) : Value: No such object (SNMP error # 222)
7/11/2016 12:38:08 AM (7 ms) : Done

Jul, 2016 - Permalink

Dear thiwankabsharp

Please check if you enabled the SNMP agent of the JVM.


Jul, 2016 - Permalink

i follow this link http://docs.oracle.com/javase/7/docs/technotes/guides/management/snmp.html

in that, they have given path like this JRE_HOME/lib/management/snmp.acl.template

in that path is "JRE_HOME" refers to C:\Program Files\Java\jre7 ? (this path is my JRE_HOME path variable)

or does it refer to C:\Program Files\Java\jdk1.7.0_79\jre ? can anyone help?


Jul, 2016 - Permalink

That's for the linux version. They describe the Windows based installation here as well.


Jul, 2016 - Permalink