On Tue, Aug 09, 2005 at 01:50:21PM -0400, Robert Story wrote:
> On Tue, 9 Aug 2005 06:44:24 +0100 (BST) saifulla wrote:
> SMA> As per the SNMP standard, the MAX OID length should
> SMA> not be > 128 bytes.
> SMA>
> SMA> We have found that SNMP agents(Commercial, open
> SMA> software) take care of this differently.
> SMA>
> SMA> Question is : What is the correct behaviour:
> SMA>
> SMA> 1. Does agent must Return Error(ASN Parse Error) for
> SMA> any GET/SET/NEXT request with OID > 128?
>
> My reading of the specs is that an ObjectName with more than 128
> subidentifiers is not valid. Thus a parse error is the correct, and the packet
> should be dropped.
>
> Any tool/library that sends such a packet is broken.
>
That's nice in theory, but in the real world there are devices which
use oids of length greater than 128. One could consider those devices broken,
but that doesn't help much when you need to poll them.
We've hit this problem before and needed to set MAX_OID_LENGTH higher,
but I don't recollect the details of what the exact behavior is when this
happens.
Austin
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
