RE: sysORUpTime?

Thanks so much for the reply.

>> 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 }
>

I did find this description in the MIB.  

>
>>  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
>

Very possible as the 'offending' system is a 10-core Power770 LPAR and the 'reference' system is a 2-core Power6 LPAR.  

But, how would the speed of populating sysORTable affect the value of sysUpTime?  If I'm reading the description above correctly, it takes the value of sysUpTime and sets the next(?) instance of sysORUpTime.

>  b)  the second system does not support the sysORUpTime object
>

Quite possible, and I must apologize for this.  The 'offending' system is using net-snmp 5.5.0.0 whereas the 'reference' system is running net-snmp 5.4.1.2.  Was sysORUpTime support perhaps deprecated in 5.5.x?


>
>> 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.
>

There are other sysOR* OIDs (sysORID, sysORDescr, etc), and others, that are populated.  

>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

BEGIN:VCARD
VERSION:2.1
X-MS-SIGNATURE:YES
N;LANGUAGE=en-us:Eckert;Douglas;F
FN:Douglas F Eckert
ORG:Dow Jones & Company;Global Business & Technology Services 
TITLE:Technical Architect
TEL;WORK;VOICE:(609) 520-4993
X-MS-OL-DEFAULT-POSTAL-ADDRESS:2
EMAIL;PREF;INTERNET:[email protected]
X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards" ver="1.0" layout="text" bgcolor="ffffff"><fld xmlns="" prop="name" align="left" dir="ltr" style="b" color="000000" size="11"/><fld xmlns="" prop="title" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="dept" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="email" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="telwork" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card>
REV:20100120T190324Z
END:VCARD