"Brian Utterback" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Maarten Wiltink wrote:
[...] >> In brute fact, there aren't - there's >> only one. Backup only serves to keep the herd together if primary >> fails altogether. That's the only time anybody will listen to it. > > This isn't true. They will listen to it, all the time. And some will > sync with it. I meant sync to it, of course. [...] > So, by an large, all the leaf nodes will sync with the main server, > as planned. However, fairly often, some will sync with the backup, > due to transient errors, dropped packets, whatever. In my experience, they won't. (I have this configuration at home, with six leaf nodes. I'm not claiming proof, but it's a _lot_ of anecdotal evidence.) The backup is normally synced to the primary. So its stratum is one higher, its root dispersion is higher, it's less attractive in many respects. Perhaps the leaf nodes even recognise that one server is in the other's sync path and disqualify the latter for it. > [...] it is a good idea to configure local refclocks as Martin described. Who? Groetjes, Maarten Wiltink _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
