> -----Original Message----- > From: dave.shi...@googlemail.com > [mailto:dave.shi...@googlemail.com] On Behalf Of Dave Shield > Sent: Thursday, March 24, 2011 1:44 PM > To: Lewis Adam-VNQM87 > Cc: net-snmp-coders@lists.sourceforge.net > Subject: Re: Trap retries > > On 24 March 2011 13:20, Lewis Adam-VNQM87 > <vnq...@motorolasolutions.com> wrote: > > that's what I thought and yet ... that's what we're seeing. > > It may be something lower down in our protocol stack. > > The other thought that springs to mind is if the 'send' fails > (because the interface is already down). Maybe that then > schedules a retransmission? > > You could test this by increasing the timeout and/or retry > count, and see whether this affects the length of "short downtime" > that still results in a stale trap being received. > What are you suggesting that schedules the retransmission? The net-snmp code detecting the trap send fail or the lower level protocol stack detecting the udp pdu send fail?
Adam. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
