Hi Robert, Please find attached file which contains output of sub-agent and master-agent. Log which has the time stamp is from sub-agent. Log without time stamp is from master-agent. I done this to differentiate logs which are comes from master/sub-agent.
In this output you can see trap#0 is getting the response at after trap#9. By the way I enabled sess_select also in logging. On Fri, 2007-07-06 at 17:07 -0400, Robert Story wrote: > On Thu, 5 Jul 2007 10:56:02 -0700 Navaneetham wrote: > N> As you mentioned I will try and get debug information. With my > N> experiment yesterday I can see duplicate trap happening whenever > N> "snmp_api.c : snmp_resend_request : 5286" functions is getting called. > N> This is happening whenever "snmp_timeout" is happening. I don't know > N> when this happening. Why this snmp_timeout can happen? > > It shouldn't happen unless the pdu is expecting a response.. a trap2sink > should not expect a response. > > N> Just for experiment purpose > N> I changed "snmp_api.c : DEFAULT_RETRIES" to '0'. Then I didn't see > N> duplicate traps. > > You changed that and rebuilt snmpd? or just the sub-agent? I done the modification and complied snmplib, which gives libnetsnmp*. I copied into standard location. Sub-agent and snmpd both are picking up changes library.
dupTrapInfo.tar
Description: Unix tar archive
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
