Template:FAQ:Applications 07

Assuming that the agent hasn't crashed completely, the most likely explanation is that it's simply overloaded, and is taking longer to respond than the querying tool is waiting. Since the agent handles each request in turn, without regard to earlier activity, and most tools will retry a request when it times out, the list of outstanding requests can grow longer and longer.

To determine whether this is the cause, try leaving the agent undisturbed for a while, and then probe it using a single 'snmpget' or 'snmpgetnext' request, specifying a longer timeout (e.g. '-t 120'). This should give the agent time to handle the request first time round, and avoids overloading it with duplicate requests.

This is not a full solution, of course, but at least it should allow you to isolate the offending portion of the tree. The developers may then be able to offer a more long-term solution.