Datum TYMSERVE 2000, Operation And Technical Manual

Page: 40 / 54

E-mail: info@datum.com Please include datumMIB
in the subject."
DESCRIPTION
"The MIB module for datum entities."
::= { private 601 }
bancomm OBJECT IDENTIFIER ::= {datumMIB 1}
timing OBJECT IDENTIFIER ::= {datumMIB 2}
austron OBJECT IDENTIFIER ::= {datumMIB 3}
fts
OBJECT IDENTIFIER ::= {datumMIB 4}
efratom OBJECT IDENTIFIER ::= {datumMIB 5}
experiment OBJECT IDENTIFIER ::= {datumMIB 99}
ntpVars OBJECT IDENTIFIER ::= {experiment 1}
ts2Vars OBJECT IDENTIFIER ::= {experiment 2}
ntpLeapIndicator OBJECT-TYPE
SYNTAX INTEGER {
nowarning(0), --No warning
insertion(1), --last minute has 61 secs
deletion(2), --last minute has 59 secs
alarm(3) --alarm, clock not sync'd
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"NTP Leap Indicator. This is a two-bit code
warning of an impending leap second to be inserted
into the NTP timescale. The bits are set before
23:59 on the day of insertion and reset after 00:00
on the following day. This causes the number of
seconds (rollover interval) in the day of insertion
to be increased or decreased by one. In the case
of primary servers the bits are set by operator
intervention, while in the case of secondary servers
the bits are set by the protocol. The two bits,
bit 0 and bit 1, respectively, are coded as follows:
===================================================
00 no warning
01 last minute has 61 seconds
10 last minute has 59 seconds
11 alarm condition(clock not synchronized)
===================================================
In all except the alarm condition(11), NTP itself
does nothing with these bits, except pass them on to
the time-conversion routines that are not part of
NTP. The alarm condition occurs when, for whatever
reason, the local clock is not synchronized, such
TYMSERVE 2000 Manual Datum Inc, Bancomm Div.
xl