[ntp:questions] orphan parent

Steve Kostecke kostecke at ntp.org
Wed Oct 20 20:35:37 UTC 2010


On 2010-10-20, Miernik, Jerzy (Jerzy) <jerzy.miernik at alcatel-lucent.com> wrote:

> Each ntp.conf contains a line 'tos orphan 10'. 
> Each node had GPS but lost it. Local clocks (LCL) not configured.

Orphan Mode replaces the Undisciplined Local Clock driver (aka "LOCAL"
or "LCL").

> 'ntpg -np' in 10.103.86.6 shows this:
>
> remote           refid        st ...
> --------------------------------------
> *10.49.88.6      127.0.0.1    10 ...
>
> 'ntpg -np' in 10.49.88.6 shows this:
>
> remote           refid        st ...
> -----------------------------------------
> *10.103.86.6     10.49.88.6   10  ...
>
> So orphan parent looks to be the rightmost 10.49.88.6.
> By implication, orphan child must be 10.103.86.6.

127.0.0.1 <- 10.49.88.6 <- 10.103.86.6

> Two things puzzle me though:
>
> 1. It looks like 10.49.88.6 is getting time reference via 10.103.86.6
> from itself?

ntpd should eventually drop this loop. But I can't tell what's going on
because you truncated the peers billboard.

-- 
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/




More information about the questions mailing list