Re: subagent - how long can it take to respond to a get request?

"Dave Shield" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
On 31/08/06, Nikanth K <[email protected]> wrote:
> > So can I take around 30 secs to respond? Will that be acceptable?
>> If I do that will SNMP walk work without any glitches?

30 seconds is a little bit long.
A typical management application would probably give up before then.

If you can control the client side, it should be possible to increase
the timeout value
to compensate.  But if other people will be querying your system,
that's not really a scalable solution.


> If that is a get next request, can I make them come back again with the same
> OID so that I will move on once the data is ready?

That's how the Net-SNMP client tools work, yes.
They'll make the request, and if they don't receive an answer within a
reasonable time, they'll try again.  Only when a certain number of
retries have timed out will they report failure.
Try   "snmpgetnext -d ....." to see this happening.

But a typical setup is something like 3 retries with a 5s timeout.
So a 30s processing overhead wouldn't respond in time.



Q:  Is this a single value that you're trying to retrieve, or a set of
related values?
(e.g. a table).  If multiple, is the 30s processing a one-off
overhead, or incurred for each individual value?

Dave

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.