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

Hi Dave,

Thanks for your reply. Please forgive me for replying late to your questions.

On Fri, Apr 23, 2010 at 9:26 PM, Dave Shield <[email protected]> wrote:
> On 20 April 2010 10:38, A Singh <[email protected]> wrote:
>> When I issue getnext command, it takes around 6 sec to process a
>> request for OIDs under host MIB; for example:
>> % snmpgetnext -v2c -cpublic -t30 10.0.6.103
>> HOST-RESOURCES-MIB::hrSystemMaxProcesses.0
>> ..
>> ..
>> HOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 897832 KBytes
>> but snmpget returns without delay:
>> % snmpget -v2c -cpublic -t30 10.0.6.103 HOST-RESOURCES-MIB::hrMemorySize.0
>> HOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 897832 KBytes
>
>
> GET is inherently a simpler (and faster) request than GETNEXT.
> But 6s seems excessive.
>
> What happens if you compare the response times of
>
>      snmpget ... hrMemorySize.0
> and
>      snmpgetnext  .... hrMemorySize

Response time of both OIDs is immediate.
>
> Is anything being logged by the agent?

I'm running the agent with OPTIONS="-Lsd -p /var/run/snmpd.pid -a" and
logs don't show any error message/warning when I execute getnext on
HOST-RESOURCES-MIB::hrSystemMaxProcesses.0, but still delay in getting
response is > 6 sec.
>
> 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