I shall provide you some of my findings now. Please correct me if I am wrong.
1) I 'DID' receive the trap message on my trap receiver (another server in the network) on port no 162 if mentioned hostname:portno 2) I 'DID NOT' receive the trap message on my trap receiver (another server in the network) on port no other than 162 if mentioned hostname:portno in the following cmd: >> snmptrap -v 1 -m ALL -c public \ 135.36.115.62:<port no> .1.3.6.1.6.3169.254.1.1 127.128.129.130 6 1 20071105 3) Since you say that the 'defTarget' was introduced in netSNMP v5.4 (I have netSNMP v5.1 pre-installed with the RHEL 4.6 OS) or later, I shall not touch configuration files. Lets leave that for the moment. 4) I am not seeing any snmp errors in '/var/log/message' either. If you know a place where the SNMP logs are generated, can you please let me know the same? ------------------------------------------------------------------------------ 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
