NTP Statistics Menu
the added time offset parameter appeared to be incorrect. This can occur if an
becomes unsynchronized and generates false timestamp information.
undefinable. This is usually caused by packet corruption.
information was incomplete.
or information. This is usually caused by packet corruption.
Display the Current Leap Second State
If necessary,
correct for errors in time information. These modifications are called leap seconds. To display
leap second information for the switch, enter the
screen similar to the following is displayed:
Field Descriptions
The following section describes the fields displayed using the
. The current status of the leap second monitor. There are four possible codes:
. The number of leap seconds that occurred during the current day.
. The number of leap seconds that will occur in the current month.
. The number of leap bits set within the last hour.
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.
the most current leap interrupt is finished.
Page 12-30
. The number of
NTP
. The number of packets received where the version number of
. The number of packets received that
. The number of
NTP
adds or subtracts a second from the timestamps sent out on the network to
NTP
No warning.
Last minute has 61 seconds.
Last minute has 59 seconds.
Alarm condition (clock not synchronized)
. A leap interrupt occurs when the
. The time, in standard date notation, of the next leap interrupt after
. The number of times a leap second has been added or subtracted.
. A scheduled leap second insertion more than a month away.
timestamps received that the switch disallowed because
rejected because the packet
NTP
packets received that contained an unreadable request
command at the system prompt. A
NTP
entity
NTP
was
NTP
command.
algorithm examines the topol-
Need help?
Do you have a question about the Omni Switch/Router and is the answer not in the manual?