>>>>> On Wed, 28 Apr 2010 23:27:21 -0700 (PDT), surya prakash >>>>> <[email protected]> said:
sp> This causes the client (snmpclient) to resend the packet (with one sp> varbind less) and which in turn cause 'no such instance object' for sp> the next 20 set of SNMPget packet request. This is a very common situation. The agent is functionally trying to act as a "proxy" of sorts between two other cases. Eventually one of a few things may happen: 1) the agent gives up waiting for the agentx client 2) the application gives up waiting for the agent as a whole and resends You combine those things and all sorts of chaos happens. The best thing to do is increase the timeout for the client and possibly increase the timeout for agentx to get around these conditions under heavy load. If you stop and think through it, both #1 and #2 have to be dealt with by the application "in charge". -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
