On Sat, 2011-10-01 at 19:44 +0530, Vivek Nagaraj wrote: > All I did was added this line in 'snmpd.conf': "defTarget snmptrap udp > :50162" and restarted the snmpd service using: 'service snmpd > restart'. > > I used to get the first trap at the UDP port 50162. And I used to > receive trap on my client Windows machine where the trap receiver was > running at the default port 162 rather than the mentioned port. Any > setting/tweaks (you remember) to be done on the client/server?! > > The command used to send dummy trap was 'snmptrap'. The server from > which snmptrap was generated was RHEL 6.1 x64. > > Any idea why am I still not receiving traps at default port?!
Yes. > Thanks a ton for the response. You added defTarget snmptrap udp :50162 to snmpd.conf snmpd.conf is the config file for the snmp agent (snmpd). Then you use snmptrap to send a trap. Since snmptrap isn't reading snmpd.conf that explains why it didn't affect that program. To change it for all programs you should put it in snmp.conf. /MF ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
