[ntp:questions] Excessive NTP configuration of a stratum 2 server

shoppa at trailing-edge.com shoppa at trailing-edge.com
Wed Jan 17 16:35:54 UTC 2007


Eric wrote:
> For the group's amusement, below are the results of an NTPQ "peer" command to a
> us.pool.ntp.org server (located in Florida).  It also claimed an offset of -0.220 and
> a root dispersion of 39ms.
>
>      remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> -192.53.103.103  .PTB.            1 u  400 1024  377  130.298   -1.174   0.244
> -ntp1.twc.weathe .CDMA.           1 u  168 1024  377  129.244   -5.943  14.381
>  ip-207-145-113- .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> -time-b.timefreq .ACTS.           1 u  399 1024  377   49.234    0.721   0.116
> -time-c.timefreq .ACTS.           1 u  369 1024  377   48.755    0.100   0.156
> -clock.tl.fukuok .GPS.            1 u  353 1024  377  223.609    6.273   0.047
> -ntps1-0.cs.tu-b .PPS.            1 u  411 1024  377  125.724    2.846   9.080
>  ip-207-145-113- .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> -ntp0.nl.uu.net  .GPS.            1 u  384 1024  377  124.976   -0.923   1.086
> +clock.xmission. .GPS.            1 u  251 1024  377   59.315   -0.155   0.126
> -clepsydra.dec.c .GPS.            1 u  360 1024  377   90.972    6.350   0.139
> -murgon.csse.uni .GPS.            1 u  346 1024  377  256.885    5.216   0.202
>  node-217.machin .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> -usno.pa-x.dec.c .USNO.           1 u  360 1024  377   91.458    6.422   0.186
> -ntp-sop.inria.f woon.curie.fr    2 u  216 1024  377  132.026   -5.562   0.576
> -clock.nc.fukuok .GPS.            1 u  211 1024  377  225.222    6.180   0.244
>  adsl-65-43-21-9 .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> -clock.via.net   .GPS.            1 u  355 1024  377   89.641    5.174   0.084
> -timekeeper.isi. .GPS.            1 u  421 1024  371   94.798   11.324  12.381
> -tick.exit.com   .GPS.            1 u  382 1024  377  114.721    6.601   0.264
> -ptbtime2.ptb.de .PTB.            1 u  383 1024  377  129.350    0.275   0.202
>  24.130.207.189  .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> -time-b.nist.gov .ACTS.           1 u  166 1024  377   29.409   -0.272   0.067
> -nist1-dc.witime .ACTS.           1 u  186 1024  377   28.626    5.308   0.161
> -time1.stupi.se  .PPS.            1 u  169 1024  377  121.422   -0.981   0.049
> -ntp-nasa.arc.na .GPS.            1 u  388 1024  367  107.347   -0.587   0.185
> -tick.gbpsw.com  .GPS.            1 u  182 1024  377   52.197   -8.503   1.352
>  193.63.105.18   .INIT.          16 u    - 1024    0    0.000    0.000 4000.00
> +tick.ucla.edu   .PSC.            1 u  664 1024  377   65.326   -0.184   0.068
> -otc1.psu.edu    .WWV.            1 u  277 1024  377   52.915  -18.965   1.203
> -ntp1.sp.se      .PPS.            1 u  210 1024  377  126.697    0.022   0.401
> *navobs1.oar.net .USNO.           1 u  696 1024  377   46.624   -0.167   0.113
> +navobs1.mit.edu .PSC.            1 u  432 1024  377   39.301   -0.088   0.370
> +216.106.191.253 navobs1.oar.net  2 u  650 1024  377    0.643   -0.113  47.992
> -prov1.voip.mia1 clock.xmission.  2 u  659 1024  377    0.360    0.119   0.090

I will agree with "excessive"! But one thing I've noted in other
similar excessive configurations, is that ntpd starts really being
really aggressive with declaring falsetickers. Of course it can afford
to be, it only needs a few to survive the selection process.

Tim.




More information about the questions mailing list