[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20031009: rainbow clock is off (cont.)
- Subject: 20031009: rainbow clock is off (cont.)
- Date: Thu, 09 Oct 2003 11:28:47 -0600
>From: Eirh-Yu Hsie <address@hidden>
>Organization: Aeronomy Laboratory/NOAA
>Keywords: 200309291535.h8TFZhk1020058 IDD ntpd ntpdate clock
Hi Hsie,
re: setting the clock on rainbow (and other CIRES machines)
>My original configuration is that one machine (cirrus) synchronizes to
>NIST machine, and all others are multicast clinets. I just find out
>that there are at 8 multicat NTP server signal in out net. So my
>clients are sync to different servers. I already change my
>configuration. All of them now are pointing explicitly to my local
>server (cirrus) by adding a server line. Hope this will increase the
>accuracy.
Excellent. A quick look at the IDS|DDPLUS latency plots for rainbow:
http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?IDS|DDPLUS+rainbow.al.noaa.gov
indicates that your change has had a positive effect. Monitoring the
latencies over an extended period of time will tell us if this fixed
the problem for good.
>rainbow:[44]# /usr/sbin/ntpdc
>ntpdc> peers
> remote local st poll reach delay offset disp
>=======================================================================
>*LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.00093
>=cirrus 5.0.0.0 16 128 0 0.00000 0.000000 0.00000
>ntpdc> sysinfo
>system peer: LOCAL(0)
>system peer mode: client
>leap indicator: 00
>stratum: 11
>precision: -17
>root distance: 0.00000 s
>root dispersion: 0.01181 s
>reference ID: [127.127.1.0]
>reference time: c33012f2.a8abd5dc Thu, Oct 9 2003 11:01:38.658
>system flags: auth monitor ntp kernel stats
>jitter: 0.000000 s
>stability: 0.000 ppm
>broadcastdelay: 0.007996 s
>authdelay: 0.000000 s
>ntpdc>
Looks much better than before. Thanks for the quick action!
Cheers,
Tom