[SNMP4J] EngineID problem

[Mark Gorokhov]

BTW, it's plain SNMPv2/public.

I did not dive into persistent storage details 
but these are exact steps to reproduce the problem.

It's possible that there is a bug in my code. It's not clear why
removing snmp4j persistency storage and restarting the application fixes
the problem. This means (for me) that persistency storage knows
something about old EngineID and prevents work with new one.

-mg

-----Original Message-----
From: Frank Fock [mailto:fock at agentpp.com] 
Sent: Tuesday, October 09, 2007 3:32 PM
To: Mark Gorokhov
Cc: SNMP4J at agentpp.org
Subject: Re: [SNMP4J] EngineID problem

Hi Mark,

Are you really sure that the engine ID is

(a) stored in persistent storage by the agent
(b) it is modified while restoring the persistent storage?

That the MIB browser times out after an engine ID
change is normal and wanted.

Best regards,
Frank

Mark Gorokhov wrote:
> Steps to reproduce the problem:
> 1. Start application with SNMP4J agent with EngineID
> "00:00:00:00:00:00:00:00:02"
> 2. MIB browser displays managed objects from the application.
> 3. Close the application (not kill!) This will create SNMP4J
persistency
> storage.
> 4. Start the same application with modified EngineID
> "00:00:00:00:00:00:00:00:03"
> PROBLEM: MIB browser timeouts to display managed objects from the
> application.
> 
> The problem is fixed after persistency storage is deleted.
> 
> How to load SNMP4J persistency storage and not to break EngineID?
> 
> -mg
> 
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j

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