On Wed, May 7, 2008 at 11:39 PM, Eugene Smiley <[EMAIL PROTECTED]> wrote: > You need more commonality between the two servers configs. Currently, your > only > commonality is a server that has a high delay (aka network-wise distant from > you). At least put time.nist.gov in both configs and note the difference.
For what it's worth, I would recommend against time.nist.gov unless you have some sort of regulatory requirement that it be used. It is under very heavy load, as are the other NIST and USNO servers. All of those show very jittery time from my network vantage point, undoubtedly due to network traffic. I recall a recall reading that USNO handles >5 Mb/s of NTP traffic, and that was many years ago. It may be much worse than that now. Also the typical "rules of engagement" are that you never use a stratum-1 unless you are a stratum-2 server that is in turn serving time to many clients. In your situation, if you really have only these two machines, I would add use this configuration on blue: server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org server 3.pool.ntp.org And this configuration on red: server blue iburst prefer server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org This ensures that red syncs to blue, but uses the NTP pool as a sanity check on its time. If blue really goes crazy and is marked as a false-ticker, red will choose one of the pool servers as its source. -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
