[snmp] slow snmp v3 discovery timeout
Gejo.Thayil at aricent.com
Gejo.Thayil at aricent.com
Tue Jan 30 10:53:50 GMT 2007
>In working with snmpv3 contexts, I've found that sending a Pdu request to
an
>agent is not there takes a long time to return ~19 seconds. When I looked
>into the code, it looks as though the v3 context is using a
UsmDiscoveryBean
>to discover the v3 engineid and other parameters if that agent has never
>been contacted.
well in my case i was working with Westhawk Stack version 4_13, i have
switched off
the authentication and privacy flags in the context. also while
initialising the context
call TimeWindow.setSnmpEngineId(host, port, engineId), this will stop the
discovery of engineId everytime before sending a packet
> The bean class uses the default timeout when sending the Pdu
>request for discovery. However, I had set a different retry_array on the
>original Pdu that is causing the discovery to be sent in the first place.
It
>would make sense for the stack to use this retry array when sending the
>discovery Pdu as well. Or at a minimum provide a way to change the
default
>retry array for v3 discovery. Perhaps there is another way to do this
that
>won't take so long that I am missing.. suggestions welcome.
>Josh
why dont you add the same retry array before v3 Discovery, i.e in
UsmDiscoveryBean.java
when you are creating an instance of DiscoveryPdu, just call method
pdu.setRetryInterval(retry_array)
and set the retries required there.
Regards
Gejo Joseph
Flextronics Software Systems
18/1, Outer Ring Road
Panathur Post, Bangalore
"I would love to change the world, but no one would give me the source
code"
*********************** Aricent-Unclassified ***********************
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of
the individual to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this email including damage from virus."
More information about the snmp
mailing list