Reference Guide

ntp master <stratum>
To configure the switch as NTP Server use the ntp master<stratum> command. stratum number identifies the NTP
Server's hierarchy.
The following example shows configuring an NTP server.
R6_E300(conf)#1w6d23h : NTP: xmit packet to 192.168.1.1:
leap 0, mode 3, version 3, stratum 2, ppoll 1024
rtdel 0219 (8.193970), rtdsp AF928 (10973.266602), refid C0A80101 (192.168.1.1)
ref CD7F4F63.6BE8F000 (14:51:15.421 UTC Thu Apr 2 2009)
org CD7F4F63.68000000 (14:51:15.406 UTC Thu Apr 2 2009)
rec CD7F4F63.6BE8F000 (14:51:15.421 UTC Thu Apr 2 2009)
xmt CD7F5368.D0535000 (15:8:24.813 UTC Thu Apr 2 2009)
1w6d23h : NTP: rcv packet from 192.168.1.1
leap 0, mode 4, version 3, stratum 1, ppoll 1024
rtdel 0000 (0.000000), rtdsp AF587 (10959.090820), refid 4C4F434C (76.79.67.76)
ref CD7E14FD.43F7CED9 (16:29:49.265 UTC Wed Apr 1 2009)
org CD7F5368.D0535000 (15:8:24.813 UTC Thu Apr 2 2009)
rec CD7F5368.D0000000 (15:8:24.812 UTC Thu Apr 2 2009)
xmt CD7F5368.D0000000 (15:8:24.812 UTC Thu Apr 2 2009)
inp CD7F5368.D1974000 (15:8:24.818 UTC Thu Apr 2 2009)
rtdel-root delay
rtdsp - round trip dispersion
refid - reference id
org -
rec - (last?) receive timestamp
xmt - transmit timestamp
mode - 3 client, 4 server
stratum - 1 primary reference clock, 2 secondary reference clock (via NTP)
version - NTP version 3
leap -
NOTE:
● Leap Indicator (sys.leap, peer.leap, pkt.leap) — This is a two-bit code warning of an impending leap second
to be inserted in the NTP time scale. 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:
● Poll Interval — integer indicating the minimum interval between transmitted messages, in seconds as a power of two.
For instance, a value of six indicates a minimum interval of 64 seconds.
● Precision — integer indicating the precision of the various clocks, in seconds to the nearest power of two. The value
must be rounded to the next larger power of two; for instance, a 50 Hz (20 ms) or 60 Hz (16.67ms) power-frequency
clock is assigned the value -5 (31.25 ms), while a 1000 Hz (1 ms) crystal-controlled clock is assigned the value -9 (1.95
ms).
● Root Delay (sys.rootdelay, peer.rootdelay, pkt.rootdelay) — a signed fixed-point number indicating the
total round-trip delay to the primary reference source at the root of the synchronization subnet, in seconds. This
variable can take on both positive and negative values, depending on clock precision and skew.
● Root Dispersion (sys.rootdispersion, peer.rootdispersion, pkt.rootdispersion) — a signed fixed-
point number indicating the maximum error relative to the primary reference source at the root of the synchronization
subnet, in seconds. Only positive values greater than zero are possible.
● Reference Clock Identifier (sys.refid, peer.refid, pkt.refid) — This is a 32-bit code identifying the
particular reference clock. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-
octet, left-justified, zero-padded ASCII string, for example: in the case of stratum 2 and greater (secondary reference)
this is the four-octet internet address of the peer selected for synchronization.
● Reference Timestamp (sys.reftime, peer.reftime, pkt.reftime) — This is the local time, in timestamp
format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
● Originate Timestamp: The departure time on the server of its last NTP message. If the server becomes
unreachable, the value is set to zero.
System Time and Date
747