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.
if an NMS timeout and retires(repeats the request), it might actually get the response for the first request when it can actually think it is getting for the nth repeat request it just made :)
How does the Master agent react to repeat requests ? Does it identify it. If it does, does it ignore the responses for the earlier requests. Does it ignore the later requests/responses etc.
------------------------------------------------------------------------- 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-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
