On Thu, 28 Jul 2011 15:30:03 -0400 Doug wrote: DM> WH> The SNMPv3 specifications say that a running manager should allow its DM> WH> notion of an agents clock values to go forward, but not backward. Thus, DM> WH> we're doing what we're supposed to do: we won't accept *older* values DM> WH> than what we have cached (but would accept newer values). So, we're DM> WH> following the specifications. DM> [...snip...] DM> Is there a way to get back this information from the net-snmp library? DM> I would like to be able to either send a trap or write out a message DM> to a log stating the problem (and the three relevant values: engineId, DM> engineBoots, and engineTime). This way, our customers could DM> pro-actively address a problem that would result in zero SNMP DM> communication.
The code you want to modify, I think, is ./snmplib/snmpusm.c:2100:usm_check_and_update_timeliness. There are already some debug messages there, so maybe just adding -Dusm to your argument list might be enough. I'm not sure how much extra noise that would generate, though. You could either make the debug token more specific (e.g. "usm:timeWindow") or change from debug messages to log messages. ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
