On Mon, Oct 03, 2011 at 08:44:50AM +0530, Vivek Nagaraj wrote: > Response to your previous mail: > > 1) Could not find 'snmp.conf'
You have to create it yourself. > 2) And options you have mentioned to be used with 'snmptrap' command > is not working > [root@localhost snmp]# snmptrap -v 1 -m ALL -c public 135.36.115.62 > .1.3.6.1.6.3 169.254.1.1 6 1 20071105 udp:169.254.1.1:30617 > udp:169.254.1.1:30617: Missing type/value for variable That last udp:169... parameter does not make sense. You probably meant snmptrap -v 1 -m ALL -c public 135.36.115.62:30617 .1.3.6.1.6.3 169.254.1.1 6 1 20071105 /Niels -- Niels Baggesen - @home - Århus - Denmark - n...@users.sourceforge.net The purpose of computing is insight, not numbers --- R W Hamming ------------------------------------------------------------------------------ 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
