On 10 November 2010 16:42, Eckert, Doug <[email protected]> wrote:
> What do values of sysORUpTime represent?
sysORUpTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the time this conceptual
row was last instantiated."
::= { sysOREntry 4 }
> On 1 system, we’ve got values being populated:
>
> SNMPv2-MIB::sysORUpTime.1 = Timeticks: (6) 0:00:00.06
> SNMPv2-MIB::sysORUpTime.2 = Timeticks: (6) 0:00:00.06
>
>
>
> and on another we have the following:
>
> SNMPv2-MIB::sysORUpTime.1 = Timeticks: (0) 0:00:00.00
> SNMPv2-MIB::sysORUpTime.2 = Timeticks: (0) 0:00:00.00
Two possibilities spring to mind:
a) the second system is much faster than the first,
and is populating the sysORTable within the first second of operation
b) the second system does not support the sysORUpTime object
> All zeroes are causing some concern amongst our monitoring staff.
Is it just this table, or are you seeing this more widely?
The sysORTable was a nice idea that never really worked.
If that's the only thing that seems to be broken, then I wouldn't
worry too much about it.
Dave
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-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
