On Thu, Sep 29, 2011 at 10:20 AM, <ali.br...@selex-comms.com> wrote:
> Fulko,
>
> I also tried to send my trap (oid 1.3.6.1.4.1.2257.11.1.1.0.0.9) without
> any additional var-binds as an SNMPv1 trap and it worked. The problem seems
> to be sending it as an SNMPv2 trap, SNMPv1 is OK.
>
> As for the sysUpTime, each time I run the command the timeticks value has
> incremented by the correct amount. However it is not being reset when my
> Master-Agent is stopped and started. It's as if it's taking the sysUpTIme
> from somewhere else!
>
You are right. I never looked at it that closely before.
It seems that the value is based on the up time of the OS, and not the up
time
of the master agent. (I'm not about to reboot my machine to prove it, or to
dive into the source code to find out.)
Technically thats against the specification of sysUpTime that says:
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."
Perhaps you should file a bug report.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
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
