I went throught the SNMP articles in KBs here but still unable to receive any traps. here are the steps.
- Installed SNMP Trap Receiver on a local prob.
- Used default port #162
- Captured SNMP Trap OID and put full OID in the configs .
- Marked to log an event and a change trigger
Still nothing .
I am sending the same trap to another trap receiver and it works fine.
Article Comments
hmm .. that's not good ... it started working after sometime , not sure why it took a while . last change that I made was inserting full URL into SNMP trap sensor. Any ideas if PRTG is going to make SNMP management easier in the future ? is it going to support new SNMP versions (e.g. 2.0) ?
Nov, 2010 - Permalink
In the moment there are no detailed plans to change the SNMP Trap Receiver in the near future releases. Please bear in mind that, similar to the Syslog-Sensor, the Trap Receiver in PRTG is designated as a tool for very explicit and special traps/events. It's not (supposed to replace) a full dedicated Syslog/Trap-Receiver Server.
Nov, 2010 - Permalink
As of version 14.1.8, PRTG includes a completely rewritten SNMP Trap Receiver Sensor. It is able to work as a full-scale trap receiver and is designed for high-performance usage.
If you use the previous version of this sensor type, please update to the current PRTG version and add the SNMP Trap Receiver sensor anew (pause or delete the old one).
May, 2014 - Permalink
Hello,
which SNMP version is the trap? Only SNMP v1 is supported for traps in PRTG. If it is SNMP v1 and still does not work, please consider sending us a wireshark capture file with a received trap to support@paessler.com (best with a screenshot of the current settings of the SNMP Trap Receiver Sensor).
Best Regards.
Nov, 2010 - Permalink