Handling Unknown SNMP Traps
Is there a provision to handle unknown SNMP Traps.
We have to configure all the known SNMP OID's in Mango to receive traps. What I have observed is that at times we receive trap OID's which are not configured in Mango. These traps are not logged any where and they are discarded. It will be good if the unknown traps received are alerted/captured. This will help us to identify as well as configure them immediately in mango. Something like a space holder for unknown traps.
Check the log files. There should be a warning in there that starts with "Trap not handled:".
I can see the unknown traps in the logs
"/mango/apache-tomcat-6.0.20/logs/catalina.out:WARN 2009-10-08 09:31:24,070 (com.serotonin.mango.rt.dataSource.snmp.SnmpDataSourceRT.receivedTrap:236) - Trap not handled: 220.127.116.11.1.2854.2.2 = 200
/mango/apache-tomcat-6.0.20/logs/mango.log:WARN 2009-10-08 09:31:24,070 (com.serotonin.mango.rt.dataSource.snmp.SnmpDataSourceRT.receivedTrap:236) - Trap not handled: 18.104.22.168.1.2854.2.2 = 200
This justs makes me to think how can we proactively identify the unnown traps?
Should there be a log file data source to monitor specific strings?
A system event would probably be simpler.