Hi Robert,
As you mentioned I will try and get debug information. With my
experiment yesterday I can see duplicate trap happening whenever
"snmp_api.c : snmp_resend_request : 5286" functions is getting called.
This is happening whenever "snmp_timeout" is happening. I don't know
when this happening. Why this snmp_timeout can happen?

Then I tried setting the sub-agents retry(agentXRetries) value to
'0(zero)' using following
API(netsnmp_ds_set_int(NETSNMP_DS_AGENT_AGENTX_RET RIES,0)), looks like
that is not changing the default retries(5). Just for experiment purpose
I changed "snmp_api.c : DEFAULT_RETRIES" to '0'. Then I didn't see
duplicate traps.

Is there any other way to change the retries in sub-agent side? What
is the impact if I change the retries to '0'?

On Thu, 2007-07-05 at 08:14 -0400, Robert Story wrote:
> [ First - *please* don't mail me directly unless you want private,
> *paid* consulting services. Keep discussions on the list, where
> others can both learn and offer advice. Thanks. ]
> On Wed, 4 Jul 2007 10:48:27 -0700 Navaneetham wrote:
> N> In some of the time our HW is generating alarms with in sort period of
> N> time.
> N> Did duplicate trap is known issue or what? Please let me know where to
> N> put a debug message to corner out this issue?
> First, you can run both the agent and the subagent with debug enabled, and
> enable the 'agentx' token. Also enable time stamps. You can do this for both
> by adding to your snmp.conf (NOT snmpd.conf):
> doDebugging 1
> debugTokens agentx,trap
> logTimestamp true
> Then run your subagent and make it send exactly 100 traps. Once the debug
> output has settled down, compress the output from both and post a link to
> somewhere we can download them from (ftp/http).

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.
Net-snmp-coders mailing list