Hi,
When I restart snmpd, I notice that the agent would come up and send a cold
start trap using its own uptime in the trap PDU, probably 1 sec. In my system,
there is also a monitoring process that sending a trap every time any process
in the system restart. For this, the uptime is the system uptime because we use
snmptrap.
The question here is if it's OK to have two traps from the same system with
different timestamp/uptime? Would it cause any confusion for the trap receiver?
If we have to use one uptime for the trap PDU, which one is correct?
Thanks,
Phong
________________________________
From: Nguyen Dinh Phong <ndph...@yahoo.com>
To: "net-snmp-coders@lists.sourceforge.net"
<net-snmp-coders@lists.sourceforge.net>
Sent: Thursday, November 3, 2011 10:19 AM
Subject: snmptrap uptime
Hi,
The uptime for traps such as coldstart or node down, ... generated by the
snmpd is the time the agent last initialized. However, for the snmptrap
utility, if we do not pass the uptime parameter, the traps were sent with the
uptime computed by get_uptime(), i.e. the system uptime. Do we have the reason
behind this? Shouldn't the default uptime for the snmptrap utility should also
be the agent uptime?
Thanks,
Phong
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
