shep@lcs.mit.edu (Tim Shepard) (02/25/91)
While curiously poking around, I just noticed this and thought that
maybe I should pass it along.
It looks to me like wwvb.isi.edu is 15 minutes behind, and from its
listing of its peers, it looks like it has taken some machines with it
into the past.
-Tim
allspice<29>% date
Sun Feb 24 13:08:10 EST 1991
allspice<30>% ntpq -n -c lpeers allspice
remote refid st when poll reach delay offset disp
==========================================================================
18.52.0.88 132.249.16.1 2 900 1024 376 56.7 -6.57 1.6
+128.8.10.1 .WWVB. 1 81 1024 377 120.5 -13.97 3.5
*128.4.0.1 .ATOM. 1 29 64 377 115.8 -4.91 7.3
128.100.63.2 128.4.0.1 2 604 1024 377 172.7 6.13 10.4
130.43.2.2 .WWV. 1 345 1024 377 216.5 -1.89 5.6
18.26.0.0 0.0.0.0 16 never 64 0 0.0 0.00 64000
+128.118.46.3 .WWV. 1 649 1024 377 122.5 6.38 2.7
+132.249.16.1 .WWVB. 1 901 1024 357 187.0 -4.43 5.0
18.26.0.95 18.72.0.3 2 923 1024 377 34.2 9.96 1.0
+129.116.3.3 .WWV. 1 518 1024 377 146.2 -1.78 11.2
allspice<31>% ntpq -n -c lpeers 18.52.0.88
remote refid st when poll reach delay offset disp
==========================================================================
+18.72.0.3 .WWV. 1 741 1024 377 59.0 17.89 4.1
+128.8.10.1 .WWVB. 1 753 1024 377 112.5 -1.71 5.4
.128.9.2.129 .WWVB. 1 33 256 377 299.9 -967955 7.6
*132.249.16.1 .WWVB. 1 14 64 377 192.6 -3.12 1.2
192.5.105.2 128.4.0.1 2 92d 1024 0 244.5 -4.29 64000
128.174.5.50 132.249.16.1 2 598 1024 377 132.5 1.59 44.8
134.174.51.3 128.4.0.1 2 92 1024 376 81.5 0.82 63.5
.18.26.0.115 128.4.0.1 2 875 1024 377 57.5 6.16 1.8
allspice<32>% ntp -v 128.9.2.129
Packet from: [128.9.2.129]
Leap 0, version 1, mode Server, poll 6, precision -10 stratum 1 (WWVB)
Synch Distance is 0000.0000 0.000000
Synch Dispersion is 0000.02d0 0.010986
Reference Timestamp is ab727bc1.fb640000 Sun Feb 24 12:52:01 1991
Originate Timestamp is ab727fa3.93154002 Sun Feb 24 13:08:35 1991
Receive Timestamp is ab727bdb.c3d70000 Sun Feb 24 12:52:27 1991
Transmit Timestamp is ab727bdb.d7ce0000 Sun Feb 24 12:52:27 1991
Input Timestamp is ab727fa3.f3af8593 Sun Feb 24 13:08:35 1991
128.9.2.129: delay:0.299366 offset:-967.959227 Sun Feb 24 12:52:27 1991
allspice<33>% host 128.9.2.129
wwvb.isi.edu 128.9.2.129
allspice<34>% ntp -v 128.9.2.129
Packet from: [128.9.2.129]
Leap 0, version 1, mode Server, poll 6, precision -10 stratum 1 (WWVB)
Synch Distance is 0000.0000 0.000000
Synch Dispersion is 0000.02d0 0.010986
Reference Timestamp is ab727c45.a1060000 Sun Feb 24 12:54:13 1991
Originate Timestamp is ab728025.f1ab191c Sun Feb 24 13:10:45 1991
Receive Timestamp is ab727c5e.19160000 Sun Feb 24 12:54:38 1991
Transmit Timestamp is ab727c5e.2c8b0000 Sun Feb 24 12:54:38 1991
Input Timestamp is ab728026.892d7731 Sun Feb 24 13:10:46 1991
128.9.2.129: delay:0.515829 offset:-968.103940 Sun Feb 24 12:54:38 1991
allspice<35>% ntpq -n -c lpeers 128.9.2.129
remote refid st when poll reach delay offset disp
==========================================================================
.128.4.0.5 .WWVB. 1 1819 1024 377 159.0 841012 7938.0
.128.5.192.1 .GOES. 1 1605 1024 376 231.0 -9.00 19.0
.128.8.10.1 .WWVB. 1 1860 1024 337 179.0 841016 7939.0
.192.43.244.9 .WWVB. 1 1794 1024 376 136.0 518009 7938.0
130.126.174.40 0.0.0.0 0 never 64 0 0.0 0.00 16000
.132.249.16.1 .WWVB. 1 1320 1024 377 35.0 968009 7940.0
.16.1.0.4 .GOES. 1 1515 1024 377 155.0 968027 7938.0
128.171.90.5 192.52.195.10 2 972 64 0 168.0 968014 3.0
192.35.82.50 128.4.0.6 2 1050 1024 0 168.0 122006 3951.0
134.173.4.23 132.249.16.1 2 982 64 0 70.0 968027 12.0
128.252.135.4 192.35.82.50 3 1245 1024 0 191.0 841009 139.0
128.165.156.1 128.9.2.129 2 996 64 0 56.0 2.00 254.0
130.221.192.44 128.9.2.129 2 977 64 0 21.0 -62.00 3939.0
128.32.132.1 130.43.2.2 2 1188 1024 0 93.0 968022 7945.0
128.99.0.77 132.249.16.1 2 1057 512 0 194.0 968003 7883.0
192.52.70.2 132.249.16.1 2 1025 64 0 75.0 968000 4.0
128.110.4.28 128.4.0.5 2 1243 1024 0 119.0 841012 80.0
129.193.72.51 129.193.72.26 3 1201 64 0 23.0 968019 1.0
128.227.116.18 128.227.128.12 3 1185 1024 0 178.0 968019 7945.0
129.237.116.220 128.9.2.129 2 1016 64 0 271.0 124396 970.0
131.91.128.3 128.8.10.1 2 1075 64 0 237.0 967990 5633.0
128.165.148.17 128.102.16.10 2 1301 1024 0 52.0 968016 7945.0
129.101.120.8 128.9.2.129 2 1009 64 0 160.0 -146679 253.0
144.86.1.1 192.52.195.10 2 1092 512 0 84.0 968010 7816.0
131.252.21.99 128.9.2.129 2 993 64 0 119.0 4.00 3753.0
.128.4.0.6 .WWV. 1 1716 1024 277 479.0 605032 7967.0
131.215.139.240 130.43.2.2 2 1022 64 0 25.0 968013 9.0
128.18.4.100 128.18.4.81 2 1303 1024 0 69.0 841012 4013.0
128.250.35.37 192.43.244.9 2 1250 1024 0 658.0 841016 4015.0
128.171.7.2 128.4.0.5 2 1004 512 0 135.0 968013 7692.0
130.62.14.10 128.102.16.10 2 1005 64 0 76.0 968019 475.0
129.18.1.2 132.249.16.1 2 1300 1024 0 71.0 841000 76.0
131.215.65.1 128.102.16.10 2 1001 512 0 30.0 968010 3942.0
128.99.0.32 132.249.16.1 2 1196 1024 0 190.0 967869 7945.0
131.179.128.3 128.8.10.1 2 1257 1024 0 41.0 968007 7945.0
192.55.214.1 128.9.2.129 2 972 64 0 175.0 -16.00 3316.0
137.186.128.12 18.72.0.3 2 1131 512 0 233.0 967980 15.0
130.221.192.46 132.249.16.1 2 1023 64 0 20.0 968018 2.0
128.32.139.1 130.43.2.2 2 1139 1024 0 77.0 968018 7945.0
134.173.4.32 132.249.16.1 2 1028 64 0 59.0 967888 9.0
129.216.202.50 129.216.200.44 5 1101 64 0 201.0 967812 3.0
128.95.174.5 130.43.2.2 2 1206 1024 0 76.0 841018 1018.0
128.149.67.213 128.9.2.129 2 48h 64 0 53.0 -394.00 241.0
128.194.3.112 192.52.195.10 2 1030 64 0 139.0 968006 9.0
129.65.17.1 129.65.17.15 3 979 64 0 -24.0 967941 84.0
129.78.8.50 128.8.10.1 2 1061 512 0 715.0 968006 2.0
130.150.102.20 130.43.2.2 2 1273 1024 0 66.0 841112 1014.0
129.140.6.1 132.249.16.1 2 1035 512 0 41.0 968002 5941.0
129.127.40.4 129.127.40.3 3 1027 512 0 699.0 841012 412.0
140.145.254.253 130.43.2.2 2 986 64 0 86.0 967907 259.0
130.70.48.2 128.9.2.129 2 25h 64 0 186.0 -75.00 17.0
128.101.224.1 128.9.2.129 2 984 64 0 158.0 10.00 127.0
128.95.175.3 132.249.16.1 2 992 512 0 73.0 841004 202.0
146.5.2.10 128.4.0.1 2 1131 512 0 397.0 841011 2266.0
130.217.64.3 128.102.16.10 2 1010 64 0 737.0 968045 6.0
130.224.1.11 132.249.16.1 2 1071 512 0 61.0 967997 6950.0
129.193.109.17 192.43.244.9 2 1031 64 0 31.0 968298 25.0
128.102.19.96 128.9.2.129 2 1009 64 0 320.0 937576 390.0
139.121.19.1 132.249.16.1 2 1806 64 0 32.0 841000 10.0
128.102.19.3 128.102.19.62 3 1049 256 0 64.0 966851 7.0
128.146.8.60 192.43.244.9 2 1200 1024 0 174.0 841016 4015.0
128.101.232.1 128.9.2.129 2 982 64 0 147.0 -26.00 1065.0
134.48.1.31 128.8.10.1 2 1078 256 0 208.0 968008 64.0
129.65.17.15 128.9.2.129 2 989 64 0 146.0 127027 6008.0
131.252.20.12 128.9.2.129 2 1023 64 0 101.0 8.00 763.0
129.216.200.51 128.9.2.129 2 1027 64 0 200.0 -25.00 880.0
128.146.18.50 128.146.8.98 3 1218 1024 0 166.0 841005 521.0
128.200.16.12 128.102.16.10 2 1271 1024 0 49.0 841011 4013.0
128.175.1.1 128.4.0.20 3 970 512 0 179.0 968019 7442.0
131.232.10.8 128.9.2.129 2 973 64 0 484.0 -7.00 7505.0
131.179.128.2 132.249.16.1 2 1326 1024 0 34.0 841003 143.0
132.204.22.50 128.8.10.1 2 1267 1024 0 257.0 841030 86.0
128.149.21.6 192.43.244.9 2 987 64 0 51.0 968020 9.0
131.236.1.2 .LOCL. 1 1230 1024 0 724.0 841005 1020.0
130.150.108.90 132.249.16.1 2 1319 1024 0 56.0 841005 4014.0
131.106.1.22 192.43.244.9 2 1243 1024 0 150.0 968014 7945.0
15.255.160.64 16.1.0.4 2 982 128 0 180.0 841004 4896.0
128.170.2.8 .. 0 1027 1024 0 41.0 126922 2703.0
128.54.16.1 132.249.16.1 2 1047 256 0 40.0 841008 452.0
130.70.40.21 128.8.10.1 2 25h 1024 0 178.0 1.00 21.0
129.66.20.2 128.8.10.1 2 1074 64 0 178.0 968032 3754.0
128.4.0.2 .DCN. 0 1012 64 0 182.0 12.00 8.0
128.8.10.30 128.8.10.1 2 977 64 0 163.0 968012 7.0
192.35.82.200 128.4.0.1 2 1001 512 0 163.0 968011 7824.0
192.41.211.41 192.43.244.9 2 1098 64 0 177.0 968017 190.0
192.41.211.40 192.43.244.9 2 1153 512 0 191.0 968028 5947.0
128.59.64.60 132.249.16.1 2 1132 512 0 166.0 968002 7.0
128.119.47.21 128.8.10.1 2 1017 512 0 269.0 967953 15.0
***Remote host didn't return peer.srcadr for association 256
allspice<36>%Mills@udel.edu (02/25/91)
Tim, On closer inspection at wwvb.isi.edu earlier today I found the Spectracom clock wandering 25 minutes slow, but ticking correct format and quality indicator. As of now (2129Z 24 Feb) it has returned to truetick. This is the first time I have seen this kind of wobble. All previous wobbles known to me have involved onboard clock silicon failures such as stuck hot and cold bits and microprocessor hiccups. What worries me is that the wwvb hardware has recently been gutted and replaced with the innards of the new Spectracom Netclock/II, which they just announced. I sure hope this particular wobble is not species-specific, since I would like to upgrade four of the other Spectracom 8170 clocks now used at other primary servers. The new clock, as well as the upgrade, now decode the year and leap information, which would be a Good Thing and also simplify my life in the first moments of every New Year. As Tim noted, several secondary sites got warped along with the wwvb server itself. Some ten out of about 120 chimers at wwvb warped tick in this way. This shouldn't happen with strategically configured peers as recommended in the pub/ntp/ntpinfo file on louie.udel.edu and in many messages sent to this list and published in various RFCs and other documents. In addition, I can say that a version-3 server has considerably more resistance to falsetickers than the previous versions now indigent to the present Unix daemons. In reviewing the statistics collected by a version-3 fuzzball near here during a five-day interval including the wwvb warp, I found the mean error 0.768 ms, standard deviation 1.782 ms and max error +4.922 -2.579 referenced to its other stratum-1 peers, including wwvb. However, during this interval 4 of the 9 configured peers became warped for at least long enough to get noticed. I suspect some of these warps were due to reboots and zoon, but it also reveals that the wwvb warp was gloriously ignored. Dave
Mills@udel.edu (02/25/91)
Tim, A closer look at wwvb reveals that it was wildly wobbling to and fro in frequency where the rate of change in frequency varied up to 1000 ppm in an hour(!) I strongly suspect the radio simply lost signal, which is not an uncommon event with these things, whereupon the radio tracking loop went nuts. All timecode receivers have the problem of what to do when the signal dies, which is common in WWV/H receivers like PSTI/Traconex and Heath and to a lesser degree in WWVB receivers, but most receivers (Heath excepted) can hold the fort to maybe a few ppm over the loss interval. I have keenly observed the Traconex receiver, which commonly warps a few milliseconds near sunup and sundown, the Spectracom 8170 and the True-Time GOES receivers, which don't warp, but can wander a few milliseconds over a day under signal- loss conditions. However, the wwvb behavior, assuming it was caused by signals fading into the muck no silicon is broken in the circuitry, is clearly beyond any reasonable nominals. I will take this issue up with Spectracom. Dave