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
as when first coming up or after an extended period
when no primary reference source is available.
Parsed from file SYMM-SMI.mib
Module: SYMM-SMI
Vendor: Symmetricom
Module: SYMM-SMI
[Automatically extracted from oidview.com]
ntpSysLeap OBJECT-TYPE SYNTAX INTEGER { noWarning(0), addSecond(1), subtractSecond(2), alarm(3)} ACCESS read-only 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 as when first coming up or after an extended period when no primary reference source is available." ::= {ntpSystem 1}
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.2 | ntpSysStratum | 0 | 0 | Current NTP stratum level. This is an integer indicating the stratum of the local clock with values defined as follows: =========… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.3 | ntpSysPrecision | 0 | 0 | Current NTP precision value. This is a signed integer indicating the precision of the various clocks, in seconds to the nearest … |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.4 | ntpSysRootDelay | 0 | 0 | Total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.5 | ntpSysRootDispersion | 0 | 0 | Maximum error relative to the primary reference source at the root of the synchronization subnet, in seconds. Only positive valu… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.6 | ntpSysRefID | 0 | 0 | NTP Reference Clock Identifier. This is a 32 bit code identifying the particular reference clock. In the case of stratum 0 (uns… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.7 | ntpSysRefTime | 0 | 0 | ntpSysReftime |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.8 | ntpSysPoll | 0 | 0 | Minimum interval between transmitted messages, in seconds as a power of two. For instance, a value of six indicates a minimum in… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.9 | ntpSysPeer | 0 | 0 | Current synchronization source. In stratum > 1 this variable returns the decimal representation of the IPv4 address of its curre… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.10 | ntpSysPhase | 0 | 0 | System clock offset from the selected source. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.11 | ntpSysFreq | 0 | 0 | System clock frequency correction from ntpd. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.12 | ntpSysError | 0 | 0 | Current system error from ntpd. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.13 | ntpSysClock | 0 | 0 | Current system time from ntpd. This is usually derived from the hardware clock but could be from any other ntp source. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.14 | ntpSysSystem | 0 | 0 | Description of the current system. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.15 | ntpSysProcessor | 0 | 0 | Type of local processor. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.16 | ntpSysNotrust | 0 | 0 | Force authentication. |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.17 | ntpSysPktsReceived | 0 | 0 | This variable is a rollover counter which reflects the number of ntp packets received by the SyncServer. It is valid for all vers… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.18 | ntpSysMode | 0 | 0 | An integer indicating the NTP association mode and are coded as follows: ============================================ 0 unsp… |
| 1.3.6.1.4.1.9070.1.2.3.1.5.1.1.19 | ntpSysVersion | 0 | 0 | The version of the NTP daemon on the system. |