>> If I have two systems running PTP (precision time protocol) which send >> traps to a third system, should I expect that the times in the traps >> when the server sees them are fairly accurate and coordinated and >> allows me to tell which trapped event happened first? Or is the time >> in the traps SNMPd uptime or something that won't be adjusted as PTP >> updates the system clock? > > The sysUpTime value in a notification is the time that the SNMP > agent has been running. This will not be coordinated between > separate systems. (This value may also be affected by tweaks > to the system clock). > So no - this timestamp is not going to be useful in ordering events. > > You haven't said anything about the payload of these traps. > If they include timestamp varbinds provided by the PTP module, > then it's quite possible that the values will be more accurate. > But the standard SNMP trap information won't really help you here.
No doubt I could create a PTP-based trap but I was thinking of things like cold start and link up. Sounds like I don't gain anything in trap analysis by having highly-coordinated clocks. Thanks. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
