Hi all,
Recently I made some modifications in the code of NTP just to log the r=
equests that arrive on the server. In this logs I put date, time, IP addres=
s of client and server, dootdispersion and rootdelay of the client (taken f=
rom the 'pkt' variable).
All that works fine, but I want to know why of the discrepancy in the v=
alues of rootdispersion. Take a look on the logs:
---------
date; time; rootdispersion(ms); rootdelay(ms); client; server;
11/08/2004; 16:56:01; 216.461; 0.229; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:03; 216.492; 0.229; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:05; 216.522; 0.229; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:07; 216.553; 0.229; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:09; 958.069; 0.244; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:11; 958.099; 0.244; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:13; 207.321; 0.244; 128.0.0.213; 128.0.0.216;
11/08/2004; 16:56:15; 207.352; 0.244; 128.0.0.213; 128.0.0.216;
---------
The proximity for the requests is because of the iburst. I just don=
=B4t understand why at 16:56:07 the dispersion if 216.553ms and at 16:56:09=
this value jumps to 958.069ms, going back to 207.321ms at 16:56:13. Is tha=
t normal?
Thanks for any help,
V=EDtor
|
|
0
|
|
|
|
Reply
|
Windows
|
8/11/2004 5:15:00 PM |
|
Vitor,
Variations like this are not unusual. The root values are summed on the
path to the primary server and can change when a server along the path
switches to a different server or if a packet is lost, etc.
Dave
V�tor Claudino dos Santos wrote:
> Hi all,
>
> Recently I made some modifications in the code of NTP just to log the requests that arrive on the server. In this logs I put date, time, IP address of client and server, dootdispersion and rootdelay of the client (taken from the 'pkt' variable).
> All that works fine, but I want to know why of the discrepancy in the values of rootdispersion. Take a look on the logs:
> ---------
> date; time; rootdispersion(ms); rootdelay(ms); client; server;
>
> 11/08/2004; 16:56:01; 216.461; 0.229; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:03; 216.492; 0.229; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:05; 216.522; 0.229; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:07; 216.553; 0.229; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:09; 958.069; 0.244; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:11; 958.099; 0.244; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:13; 207.321; 0.244; 128.0.0.213; 128.0.0.216;
> 11/08/2004; 16:56:15; 207.352; 0.244; 128.0.0.213; 128.0.0.216;
> ---------
>
> The proximity for the requests is because of the iburst. I just don�t understand why at 16:56:07 the dispersion if 216.553ms and at 16:56:09 this value jumps to 958.069ms, going back to 207.321ms at 16:56:13. Is that normal?
> Thanks for any help,
>
> V�tor
|
|
0
|
|
|
|
Reply
|
David
|
8/15/2004 4:51:53 PM
|
|
|
1 Replies
300 Views
(page loaded in 0.049 seconds)
Similiar Articles: get current drift value - comp.protocols.time.ntp... xxx.xxx.xxx assID=3D0 status=3D06f4 leap_none, sync_ntp, 15 events, event_peer/ strat_chg, system=3D"SunOS", leap=3D00, stratum=3D2, rootdelay=3D0.600, rootdispersion ... High jitter with GPS Clock - comp.protocols.time.ntp... server 127.0.0.1, port 123 stratum 2, precision -16, leap 00 refid 127.127.29.0 delay 0.00111, dispersion 0.00000 offset 0.000442 rootdelay 0.00000, rootdispersion 0 ... Solairs 8 xntpd client oscillates - comp.protocols.time.ntp ...... 146.59 > > ntpq> readvar > status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg > system="SunOS", leap=00, stratum=3, rootdelay=52.40, > rootdispersion=1161 ... Spurious positive leap second announcement? - comp.protocols.time ...... 2.0b@1.1436-mbg-o Dec 22 12:23:10 (UTC+01:00) 2005 (1)", processor="unknown", system="WINDOWS/NT", leap=00, stratum=2, precision=-23, rootdelay=1.335, rootdispersion=36 ... Single best NTP status indicator of clock accuracy? - comp ...... 1585-o Fri Jun 15 10:17:41 UTC 2007 (1)", > processor="i486", system="Linux/2.6.21-tinytgb5-pc", leap=00, > stratum=1, > precision=-16, rootdelay=0.000, rootdispersion=0 ... NTP Stratum 16? - comp.protocols.time.ntp... ntpd 4.1.1b@1.829 Fri Sep 26 21:41:19 EST 2003 (1)", processor="i686", system="Linux2.4.20-xfs-r3", leap=11, stratum=16, precision=-17, rootdelay=0.000, rootdispersion=9 ... Leap second bug? - comp.protocols.time.ntp... 2.4p0@1.1472 Fri Mar 16 10:45:43 UTC 2007 (1)", >> processor="i686", system="Linux/2.6.22.1-rt9", leap=00, stratum=3, >> precision=-20, rootdelay=30.293, rootdispersion ... basic questions about the leapsecond - comp.protocols.time.ntp ...... ntpd 4.2.0-a Sun May 8 06:01:21 UTC 2005 (1)", >processor="i386", system="FreeBSD/5.4-RELEASE", leap=00, stratum=1, >precision=-17, rootdelay=0.000, rootdispersion=2.125 ... Apple Mac mini instabiliy - comp.protocols.time.ntp... ntpd 4.2.0@1.1161-r Fri Jan 13 11:36:23 PST 2006 (1)", processor="i386", system="Darwin/8.8.1", leap=00, stratum=3, precision=-20, rootdelay=37.959, rootdispersion=70.441 ... ntpd on embedded risc - comp.protocols.time.ntp... ntpd 4.1.1@1.786 Tue Sep 11 19:14:27 CDT 2007 (1)", processor="armv4tl", system="Linux2.6.9-uc0", leap=00, stratum=1, precision=-7, rootdelay=0.000, rootdispersion=32.592 ... Windows NTP Time Client: 3.4.4 Packet ProcedureTest 8 requires that the header contains reasonable values for the pkt.rootdelay and pkt.rootdispersion fields. test6 <-- ( roman pkt.leap != 11 2 and /* test 6 */ Network Time Protocol (Version 3) Specification, Implementation ...Test 8 requires that the header contains <169>reasonable<170> values for the pkt.rootdelay and pkt.rootdispersion fields 7/29/2012 8:03:29 PM
|