> From: net-snmp-users-bounces@lists.sourceforge.net
> [mailto:net-snmp-users-bounces@lists.sourceforge.net] On
> Behalf Of Dave Shield
> Sent: Tuesday, April 29, 2008 6:56 AM

> > 2008/4/28 JAW-Woei MAA :
> > In our knowledge, timeout means the period of responsive
> > time after we set
> > the packet out.
> > In reality, when we work it within the net-snmp, it
> > wouldn't need the
> > responsive time if it can find host.

> I'm sorry - that still doesn't make much sense.

I believe the OP is confusing "timeout" and "interval"[1]. SNMP uses a timeout strategy, which translates[2] to "give up after X seconds have elapsed from the start of query, but end as soon as an answer is received." This sets a *minimimum* rate of traversal. An interval mechanism would be "do not start the next query until at least X seconds have elapsed since the last query was started"[3], which sets a *maximum* rate of traversal.

The snmpwalk command does not have interval control.



[1] Dave, you can stop reading here. ;-)

[2] This is only one of many interpretations, but the one most useful here.

[3] For cheap and/or bandwidth-paranoid implementations, "...since the last query completed".

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
Net-snmp-users mailing list
Please see the following page to unsubscribe or change other options: