On Mon, Oct 28, 2013 at 7:01 AM, Fulko Hew <fulko....@gmail.com> wrote:
> I was bit recently by a design limitation on the length of OCTET STRINGS
> as received and processed by AgentX.
>
> ...
> Comments?
>
I think the dual to this problem has also been reported at
https://sourceforge.net/p/net-snmp/bugs/2489/ - a SET request with a big
octet string fails to pass from master to subagent, just like the trap with
a big octet string fails to pass from subagent to master.
My thoughts:
1. Both of these expose a secondary issue (e.g., Fulko experiences that the
master agent appears to hang, Stian experiences that the subagent fails in
some way). These secondary issues deserve to be addressed.
2. The agentx transport should be able to handle these large strings,
especially since agentx runs over a stream protocol and has no control over
underlying packet sizes anyway.
Bill
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
