On 6 October 2011 17:57, Vivek Nagaraj <nagaraj.vi...@gmail.com> wrote: > I am receiving SNMP traps on custom ports from RHEL 4.6 x86. Tried > installing trap receiver in one of the client servers in the same > subnet as that of the RHEL server. Outside the subnet, I couldn't see > traps on my machine though. Not clear why! > > I couldn't believe it myself. Blame UDP protocol?! Or a firewall issue > in the network?!
The two most likely causes would be routing problems, or firewall settings. A missing route would normally trigger an error from the client application. so my money would be on firewalls blocking the packet somewhere. You could try temporarily turning off 'iptables' on the receiving host (assuming this is a Linux system), and see if you can see the incoming traps then. Failing that, have a look at the configuration of any intermediate routers, to see what filtering they might be doing. Dave ------------------------------------------------------------------------------ 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
