The ICMP response usually indicates that nothing is listening to the port (in this case 162). I am guessing that snmptrapd only sends traps and does not listen for incoming traps or you need to configure snmptrapd to listen for incoming traps. Either way, the traps are arriving, but there is nothing on your server to process them. There is probably documentation on the website or in the source files on how to achieve what you want.
Robert Wilcox --- [EMAIL PROTECTED] wrote: > > I did a TCPDUMP and found tht the traps do reach the > server from the router > ...bit of relief !!! :-))) > > But the server sends back a icmp request to the > router and reports that the > udp port is unreachable ... > > Here's the output of TCPDUMP > > 11:23:36.745041 172.25.63.23.55549 > > inatpuxpms01.snmptrap: > C=permitadp Trap(36) E:cisco.1.110 > 172.25.63.23 linkDown > 501199095 .iso.org.dod=[|snmp] > > 172.25.63.23 --> router > inatpuxpms01 -> server > > and then the error in the next line > > 11:23:36.745049 inatpuxpms01 > 172.25.63.23: icmp: > inatpuxpms01 udp port > snmptrap unreachable [tos 0xc0] > > Iam sort of confused y this error comes .... When i > do the same in other > server ( which receives traps successfully )) the > 2nd line is not there.. > > is tht anything to do with snmpconf ??? shud we > change any default options > ??? > > Thanks in advance > > > regards , > rajasekaran C > > > > > > Robert Story > > <[EMAIL PROTECTED] > > com> > To > > [EMAIL PROTECTED] > 02/15/2005 11:26 > cc > PM > [EMAIL PROTECTED] > et, > [EMAIL PROTECTED] > > Subject > Please respond to Re: Help > wanted Regarding SNMPTRAP > [EMAIL PROTECTED] (URGENT) > > ists.sourceforge. > > net > > > > > > > > > > > > > > On Tue, 15 Feb 2005 07:51:29 -0500 > [EMAIL PROTECTED] wrote: > CRC> > My router sents traps on link-down status to > A linux box . In the > CRC> > routerside its sending the packets perfectly > to server . > CRC> > CRC> Have you configured your trap sinks correctly? > > Trapsinks are for the agent (snmpd) sending traps. > He's talking about > receiving > traps (snmptrapd) from another box... > > The first thing I'd check is if snmptrapd is > receiving the packets. Run it > iin the foreground with packet dumping on: > > snmptrapd -f -Le -d > > Then generate the traps and see if the incoming > packet is printed. If not, > then > I'm guessing that you have a firewall running which > is blocking the > packets. > You need to open up UDP port 162 to receive traps. > > -- > Robert Story; NET-SNMP Junkie > Support: <http://www.net-snmp.org/> > <irc://irc.freenode.net/#net-snmp> > Archive: < > http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> > > You are lost in a twisty maze of little standards, > all different. > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Net-snmp-coders mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
