08-09-2013 02:19 PM
I have several snmptrap monitors setup in SiteScope 11.22 and I keep getting the summarry message of:
(SNMP No Such Object)
Please see attched screen shot.
Any information on how to resolve this issue?
Any seen this in SiteScope?
08-12-2013 02:29 AM
May you can attach the RUNMONITOR.LOG so that we can check it for more detailed information about this error?
08-12-2013 12:48 PM
08-13-2013 01:19 AM
I checked the RUNMONITOR.LOG, and found the SNMP is timing out. You may want to increase the timeout for the SNMP monitor.
2013-08-10 20:20:25,238 [Monitor Scheduler] (AtomicMonitor.java:1836) ERROR - skipped #2, monitor still running: SiteScope/200699775/12:( seans3-admin seans3-admin.alteoncbt.com ), starting the monitor update...
2013-08-10 21:20:25,256 [seans3-admin(200699775/12) ] (SNMPMonitor.java:447) ERROR - time out after retries
Also, please upload the ERROR.LOG so that i can check it as well.
08-14-2013 03:31 AM
the logs contains data in DEBUG mode, it is not very useful for me, and it does not contains information about the SNMP issue.
Please disable debugging on the Sitescope logs. Hopefully normal ERROR log level will show us more.
08-14-2013 05:18 AM
just a quick question, this error (SNMP No Such Object) is after configure the monitor or the monitor was working fine and suddently start to appears this error?
I would like to check the snmpmonitor.log, please can you upload it?
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution."
08-19-2013 10:29 AM
It occurs after configured monitors and alerts for monitors.
I ahve attached the snmptrap.log for review. There is no snmpmonitor.log found.
08-19-2013 10:39 AM
I ahve attached the latest RunMonitor.log without DEBUG turned on.
Please let me know what you find or thoughts.
08-19-2013 10:41 AM
08-20-2013 07:44 AM
As suggested, I advise you to increase the timeout for the SNMP monitor. the timeout error still exists in Runmonitor.log:
(SNMPMonitor.java:447) ERROR - time out after retries
If after increasing the timeout, the problem still persists, then i would log a support case here.