[SNMP4J] Accessing v3 servers who are ahead in time and UsmTimeTable
c v
caenews at gmail.com
Sun Feb 1 01:47:59 CET 2009
Thanks for your quick response. If you are saying growing differences ...
the way i implemented can also be a potential issue ... i have multiple
components in same jvm trying to send/receive snmp requests (new snmp
instance for each component) to same server at random times and they
can conflict too .... as usm model is implemented as a singleton can there
be a possible conflicts in times and misbehaviour that i'm seeing ?
if that is the case ... can you suggest any implementation to work around
this?
On Sat, Jan 31, 2009 at 2:08 PM, Jochen Katz <katz at agentpp.com> wrote:
> Hello,
>
> > When trying to access servers service snmp v3 which are in time ahead
> > (8-10 hrs) than the sender. I received a bunch of the following messages.
> >
> > "CheckTime: received message outside time window (non authorative)"
>
> for SNMPv3 it is no problem, if manager and agent have different times.
> But you have a problem if the times on manager and agent are growing at
> different speeds and the difference increases by 150 seconds during
> runtime of agent and manager.
>
> If you cannot keep the host times in sync or at a stable difference,
> your only workaround would be to regularly remove the time information
> from the USM time table. But you then lose part of the SNMPv3 security.
>
> Regards,
> Jochen
> _______________________________________________
> SNMP4J mailing list
> SNMP4J at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/snmp4j
>
More information about the SNMP4J
mailing list