uptimes and timestamps

[[e-mail]]

The objects chasSlotLastChange and chasEntityTimeStamp are based on sysUpTime.
The problem is that sysUpTime is defined as the time since the "network
management portion" of the system was last re-initialized.  There are
devices (e.g. repeaters) that can operate without the presence of
a management entity.  Also, the hardware portion of a device may be
reset independently of the management portion.

We have been using a object called "chassisUpTime" in our agents for awhile,
indicating the time power has been applied to the chassis.  Objects such as
a chassisSlotTimeStamp are relative to the chassisUpTime.  This prevents
the situation in which a hardware uptime (or timestamp) has to be reset 
when sysUpTime is reset.

So I'm proposing this additional object:

          chasUpTime   OBJECT-TYPE
              SYNTAX    TimeTicks
              ACCESS    read-only
              STATUS    mandatory
              DESCRIPTION
                      "The time (in hundredths of a second) that
                      power has been applied to the chassis."
              ::= { chassis 5 }


I realize that many vendors have been using sysUpTime in this way (I believe
incorrectly). I would also propose that chasSlotLastChange and possibly
chasEntityTimeStamp be relative to chasUpTime, not sysUpTime.


--andy;
[e-mail]