[SNMP4J] SNMP Manager re-installation no longer authenticating

[Frank Fock]

Yes, that is true. SNMP4J caches engine IDs,
boot counters, and engine times non-persistently.


On 18.01.2010 21:26, Clement_Pellerin at ibi.com wrote:
> I stand corrected. The SNMPv3 spec uses "less-than" comparisons which assumes the boot count is indeed a monotonically increasing number.
>
> On the other hand, reverting the boot count or letting it roll over has the same effect on the communication partners. The partners need to redo time synchronization.
>
> I would expect the cached authoritativeEngineBoots are not persisted, so a simple reboot of SNMP4J would cause time synchronization again and fix the problem. Is this true?
>
>
> -----Original Message-----
> From: snmp4j-bounces at agentpp.org [mailto:snmp4j-bounces at agentpp.org] On Behalf Of Frank Fock
> Sent: Monday, January 18, 2010 2:04 PM
> To: snmp4j at agentpp.org
> Subject: Re: [SNMP4J] SNMP Manager re-installation no longer authenticating
>
>
> The engineBoots counter needs to monotonically increasing.
> There is no time limit. The roll-over is handled
> differently.
>
> On 18.01.2010 18:17, Clement_Pellerin at ibi.com wrote:
>> I don't think the boot count needs to be monotonically increasing. I believe the boot count only needs to be unique within the time window (maybe 2 minutes). Eventually any boot count will roll over and the application needs to handle that case. Are you sure it is related to the boot count?
>>
>> Error 1414 is:  "SNMPv3: USM: Address error"
>>
>>
>> -----Original Message-----
>> From: snmp4j-bounces at agentpp.org [mailto:snmp4j-bounces at agentpp.org] On Behalf Of Aidan Diffey
>> Sent: Monday, January 18, 2010 10:31 AM
>> To: snmp4j at agentpp.org
>> Subject: [SNMP4J] SNMP Manager re-installation no longer authenticating
>>
>> Hello.
>>
>> I have an SNMP device which is connected to a manager (A J2EE application).
>> They are both talking to each other using SNMP V3.  I have re-installed the
>> manager which involved reloading a database.
>> This has reset the engine boot count on the manager from 21 back to 1. Since
>> then, I am receiving a -1414 error from SNMP4J.
>>
>> Is there something in SNMP4J that requires the engine boots to be
>> incremented in order for authentication to take place?
>>
>> How would I get the devices talking again after rebuilding the manager
>> database?
>>
>> Kind Regards
>> _______________________________________________
>> SNMP4J mailing list
>> SNMP4J at agentpp.org
>> http://lists.agentpp.org/mailman/listinfo/snmp4j
>> _______________________________________________
>> SNMP4J mailing list
>> SNMP4J at agentpp.org
>> http://lists.agentpp.org/mailman/listinfo/snmp4j
>

-- 
AGENT++
http://www.agentpp.com
http://www.snmp4j.com
http://www.mibexplorer.com
http://www.mibdesigner.com