Re: Delay in processing get next request for host MIB tree

On 13 May 2010 05:27, A Singh <[email protected]> wrote:
>> What happens if you compare the response times of
>>
>>      snmpget ... hrMemorySize.0
>> and
>>      snmpgetnext  .... hrMemorySize
>
> Response time of both OIDs is immediate.

Hmmm.... that would tend to indicate the delay is associated with
traversing the end of the hrSystem group, rather than hrMemorySize itself.

To confirm this, please try the following queries,
and report back as to the presence or absence of a delay:

   -  snmpgetnext hrSystemMaxProcesses.0 ; snmpgetnext hrSystemMaxProcesses.0
           (i.e. run the same query twice in rapid succession - does the delay
               appear both times?)

   -  snmpgetnext hrSystem.8

   -  snmpgetnext hrStorage


You original message implies that this was a widespread problem
affecting the whole of the host group.   But above you state that
getnext on hrMemorySize is reporting back promptly.

   Which MIB object(s) are affected by this problem?
If you walk the whole of the host subtree, where do the delays appear?


Dave

------------------------------------------------------------------------------

_______________________________________________
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