Hi Scott, The seems to be an issue with the NET-SNMP agent not SNMP4J.
Best regards, Frank On 22.03.2010 17:20, Mackay, Scott wrote: > Hi, I am checking out how SNMP4J returns results when the results are too > large for a single response. > I have a normal loop of send, check for a null response then check for the > response error status. For testing, I am using a net-snmp daemon which calls > a small shell script, dumping the single line contents of a file. > I request 6 different OIDs (each dump the same content). I see it work happy > when the data is under 10000 bytes (pdu size limit of 65535 I think?). When > I push it to 12000 per message, instead of getting a response with a > SNMPConstants.SNMP_ERROR_TOO_BIG, the ResponseEvent.getResponse() is null (so > I cannot check the getResponse.getErrorStatus()). When you ask for 1+ OIDs > and the results are too big for the response, is there a different way to see > if the results are too large? > > -Scott > _______________________________________________ > SNMP4J mailing list > [email protected] > http://lists.agentpp.org/mailman/listinfo/snmp4j -- AGENT++ http://www.agentpp.com http://www.snmp4j.com http://www.mibexplorer.com http://www.mibdesigner.com _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
