Alcatel Carrier Internetworking Solutions Omni Switch/Router - Manual (Page 308)

NTP Statistics Menu
Page 12-30
bad offset on input . The number of NTP timestamps received that the switch disallowed because
the added time offset parameter appeared to be incorrect. This can occur if an NTP entity
becomes unsynchronized and generates false timestamp information.
bad version packets . The number of packets received where the version number of NTP was
undefinable. This is usually caused by packet corruption.
data in pkt too short . The number of packets received that NTP rejected because the packet
information was incomplete.
unknown op codes . The number of NTP packets received that contained an unreadable request
or information. This is usually caused by packet corruption.
Display the Current Leap Second State
If necessary, NTP adds or subtracts a second from the timestamps sent out on the network to
correct for errors in time information. These modifications are called leap seconds. To display
leap second information for the switch, enter the
ntpleap command at the system prompt. A
screen similar to the following is displayed:
sys.leap: 11 (clock out of sync)
leap.indicator: 00 (leap controlled by lower stratum)
leap.warning: 00 (leap controlled by lower stratum)
leap.bits: 00 (no leap second scheduled)
time to next leap interrupt: 1 s
date of next leap interrupt: Tue, Jul 6 1999 12:38:45
calls to leap process: 0
leap more than month away: 0
leap less than month away: 0
leap less than day away: 0
leap in less than 2 hours: 0
leap happened: 0
Field Descriptions
The following section describes the fields displayed using the ntpleap command.
sys.leap . The current status of the leap second monitor. There are four possible codes:
00 No warning.
01 Last minute has 61 seconds.
10 Last minute has 59 seconds.
11 Alarm condition (clock not synchronized)
leap.indicator . The number of leap seconds that occurred during the current day.
leap.warning . The number of leap seconds that will occur in the current month.
leap.bits . The number of leap bits set within the last hour.
time to next leap interrupt . A leap interrupt occurs when the NTP algorithm examines the topol-
ogy of the network and determines if a leap second is needed (it may or may not be neces-
sary at the time of the interrupt). This counter displays seconds until the next interrupt.
date of next leap interrupt . The time, in standard date notation, of the next leap interrupt after
the most current leap interrupt is finished.
calls to leap process . The number of times a leap second has been added or subtracted.
leap more than month away . A scheduled leap second insertion more than a month away.