[ntp:questions] NTP Peer Keeps Swapping on Start-up

SteveW qsw000 at email.mot.com
Tue Oct 5 16:46:36 UTC 2010

On Oct 5, 10:05 am, Martin Burnicki <martin.burni... at meinberg.de>
> Steve Kostecke wrote:
> > On 2010-10-04, Rob <nom... at example.com> wrote:
> >> SteveW <qsw... at email.mot.com> wrote:
> >>> I am seeing a case where one board in my system keeps switching its
> >>> peer back and forth between its local clock and a remote ntp server
> >>> for about 40 minutes when it first comes up.  Eventually, it correctly
> >>> starts using the remote ntp server.
> >> It is advisable to just remove this "local clock" from your config.
> > Because the Undisciplined Local Clock (127.127.1.x) is not a "backup
> > time source" for a leaf-node (i.e. a pure client ntpd).
> But what is the basic difference if this node works as a server for other
> clients, or not?
> If other clients *would* use this NTP node as server the local clock *would*
> make sense, but ntpd's switching between local clock and remote server
> would *not* make sense, either.
> @SteveW:
> BTW, about which version of ntpd are we talking?
> Martin
> --
> Martin Burnicki
> Meinberg Funkuhren
> Bad Pyrmont
> Germany

Version of ntp is 4.2.6p1.  Recently upgraded from 4.2.0 where I had
not observed this behavior with same configuration.

More information about the questions mailing list