Clement, Am 15.01.2010 15:16, schrieb [email protected]: > Is it common to let the SNMP manager console modify the agent USM/VACM MIBs > through SNMP SET requests? > No, for security reasons you need to update keys regularly. This implies, that write access to (at least) USM is possible.
> If typical agents usually turn off write access to the USM/VACM MIBs, then I > might simply turn off persistence for now. > > This is independent from the above. You may, of course, also implement as clear text persitence provider. Best regards, Frank > > -----Original Message----- > From: Frank Fock [mailto:[email protected]] > Sent: Monday, January 04, 2010 2:09 PM > To: Pellerin, Clement > Cc: [email protected] > 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 > SerializableManagedObject interface > (2) a SerializableManagedObject may refuse to > load persistent data because its flag isVolatile > returns true. > > Regards, > Frank > > On 04.01.2010 16:53, [email protected] wrote: > >> I am using AgentConfigManager. I am confused between the >> configurationFactory and the persistenceProvider? Is the configuration file >> only needed for the first time the agent boots? After the agent is persisted >> once, would the persistence file override completely the configuration file? >> _______________________________________________ >> SNMP4J mailing list >> [email protected] >> http://lists.agentpp.org/mailman/listinfo/snmp4j >> > _______________________________________________ SNMP4J mailing list [email protected] http://lists.agentpp.org/mailman/listinfo/snmp4j
