>>>>> On Wed, 24 Aug 2011 15:30:54 +0200, Michael Schwartzkopff >>>>> <mi...@schwartzkopff.org> said:
MS> No comments on this problem? Unfortunately, many of us simply don't have the time to respond daily with free advice. I just happened to read the list (finally) today, which is the day you posted your above question. Sometimes you just need to be patient. MS> 3) Manager -> Agent MS> get-request for the OID MS> msgAuthoritativeEngineID is the one from the agent. MS> msgAuthoritativeEngineBoots is equal to the number in packet 2) MS> msgAuthoritativeEngineTime is 3437939 MS> the time differs the the time of the agent by 87965 seconds, which MS> is roughly 24,4 hours. MS> Any idea why my manager uses a different time than the one reported by the MS> Agent? Wow, no, not if it is our management stack too. It should be using a correct seconds value, except for one of a few possible possibilities: 1) the clocks are indeed off, but he manager should resync assuming not hugely off. 2) If there is an engineID conflict somewhere on the network such that two agents have the same engineID, this could happen as well. This is very very bad (TM) and needs to be fixed. After that, you probably need to point a debugger at the library. -- Wes Hardaker SPARTA, Inc. ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
