On Tue, 2011-10-04 at 12:03 +0530, Vivek Nagaraj wrote: > I have added my agent address to the snmpd.conf file. Or else I would > have not received the trap at port no 162.
Read my lips. snmptrap *DOES NOT OPEN* snmpd.conf! You can write anything you like in that file and it won't affect the operation of snmptrap. I posit that if you perform the following command: snmptrap -v 1 -m ALL -c public \ 135.36.115.62:162 .1.3.6.1.6.3169.254.1.1 127.128.129.130 6 1 20071105 you won't receive anything on the target machine either. Also, please try these commands in a console and not from within your program as they normally logs to standard output/error as they are intended to be interactive. There are flags to redirect the logs to other places. These are also described in the manual. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
