Ok. I am sorry. Not working in the sense, if I provide custom ports other than 162, I am not receiving any traps at those custom ports.
I am not seeing any error message after the execution of the command mentioned by you. My server administrator says that the backward compatibility needs to be maintained with older server OS too. I am kind of stuck. I tried and tried and tried but could not receive traps at the ports other than 162. 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 >> Works well and traps are received in port no 30617 in RHEL 5.X upwards 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 >> Not receiving traps in port no 30617 in RHEL 4.X (tried with RHEL 4.7 x86 >> and x64) <and I am not seeing traps even in port no 162; quite dangerous I >> think> <Problem at sending or receiving side?! Any tweaks to be made at the sender or receiver?> snmptrap -v 1 -m ALL -c public 135.36.115.62:162 .1.3.6.1.6.3 169.254.1.1 6 1 20071105 >> Works well and traps are received in port no 162 in RHEL 4.X Was there a known issue earlier with SNMP rectified at a later stage? Thanks a ton guys! ------------------------------------------------------------------------------ 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
