On 22 October 2010 14:45, Doug Manley <[email protected]> wrote:
> To address this, we see two possible solutions:
> 1. Force every agent on the planet to support proper RequestIDs.
> 2. Add an option to net-snmp to wrap request IDs on the 31-bit boundary.
>
> I don't think that option #1 is viable, and my company needs to have
> this "solved" in some manner fairly shortly.
$ man snmp.conf
16bitIDs yes
restricts requestIDs, etc to 16-bit values.
The SNMP specifications define these ID fields as
32-bit quantities, and the Net-SNMP library typically
initialises them to random values for security. However
certain (broken) agents cannot handle ID values greater
than 2^16 - this option allows interoperability with such agents.
> I also don't think that we should force net-snmp to perform poorly
> because some manufacturers can't count past 31 bits. I think that an
> *option*, however, either to net-snmp itself or to a particular
> session would address the problem.
We agree.
Which is why this particular option was introduced in 2003 :-)
Dave
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
