Re: SNMP4J configuration and persistence
Correct me if I'm wrong, but AgentConfigManager.configure() reads the configuration file using
MOServerPersistence.loadData() which means the configuration file is exactly equivalent to
read-only persistence in the current implementation.
I'm trying to decide how users will configure the agent USM and VACM. The cheaper the better as long as it is
The configuration file is human-readable so it fits the bill. Unfortunately, the persistence format is
binary which makes it hard to predict the combined configuration.
Is it common to let the SNMP manager console modify the agent USM/VACM MIBs through SNMP SET requests?
If typical agents usually turn off write access to the USM/VACM MIBs, then I might simply turn off
persistence for now.
From: Frank Fock [mailto:fock@...]
Sent: Monday, January 04, 2010 2:09 PM
To: Pellerin, Clement
Subject: Re: [SNMP4J] SNMP4J configuration and persistence
The configurationFactory is also needed if persistent MIB data
is available, because
(1) not all ManagedObjects may implement the
(2) a SerializableManagedObject may refuse to
load persistent data because its flag isVolatile