[AGENT++] GETBULK fails with non default size

[Kerrison, Adam]

Thanks for the quick reply. Increasing the value of MAX_SNMP_PACKET does solve the problem. With debugging turned on I could see that the response size was 4587 bytes, so greater than the default MAX_PACKET_SIZE of 4096. Are they any side effects of using a larger packet size (apart of the increased memory usage)?

Is there any reason why the buffer size isn't based on the size of the incoming response? Or at least, the buffer size is increased dynamically to accommodate larger responses?

Adam

-----Original Message-----
From: agentpp-bounces at agentpp.org [mailto:agentpp-bounces at agentpp.org] On Behalf Of Jochen Katz
Sent: 12 May 2011 20:20
To: agentpp at agentpp.org
Subject: Re: [AGENT++] GETBULK fails with non default size

Hi,

> I've run into a problem where GETBULK requests fail when you use a non default size.
> 
> For example, if I request several columns from a table with a size of 12:
> $ ./snmpBulk 1.2.3.4
>     1.3.6.1.4.1.9.9.46.1.6.1.1.3.10612
>     1.3.6.1.4.1.9.9.46.1.6.1.1.4.10612
>     1.3.6.1.4.1.9.9.46.1.6.1.1.5.10612
>     1.3.6.1.4.1.9.9.46.1.6.1.1.14.10612
>     1.3.6.1.4.1.9.9.46.1.6.1.1.16.10612
>     -Cxxxxx -m12

one easy possibility: The max pdu size of the device is bigger than the
default max pdu size of snmp++ (defined in config_snmp_pp.h as 4096).

To test this, either increase the define and recompile snmp++ and
snmpBulk or first check the size of the response of the device with
tcpdump or wireshark.

Regards,
  Jochen
_______________________________________________
AGENTPP mailing list
AGENTPP at agentpp.org
http://lists.agentpp.org/mailman/listinfo/agentpp