Steve, thanks. I have a two-node network 10.103.86.6 ----- 10.49.88.6
Each ntp.conf contains a line 'tos orphan 10'. Each node had GPS but lost it. Local clocks (LCL) not configured. '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. Two things puzzle me though: 1. It looks like 10.49.88.6 is getting time reference via 10.103.86.6 from itself? Should not 10.49.88.6 show 127.0.0.1 in its remote column? And something in refid? 2. What really is a physical clock in this network? None of the nodes has local clock configured in ntp.conf, GPS clocks are down, yet both nodes remain in sync. What's the magic inside ntpd? Thanks, Jerzy. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Steve Kostecke Sent: Wednesday, October 20, 2010 12:11 PM To: [email protected] Subject: Re: [ntp:questions] orphan parent On 2010-10-20, Miernik, Jerzy (Jerzy) <[email protected]> wrote: > Is there a way to know that ntpds are working in orphan mode? ntpd advertises a ref-id of 127.0.0.1 when it has switched to orphan mode. You'll have to have access to the configuration file to see if an arbitrary ntpd is configured to use orphan mode. > Is there a way to identify which one is orphan parent? Look for the ref-id of 127.0.0.1 in 'ntpq -p'. -- Steve Kostecke <[email protected]> NTP Public Services Project - http://support.ntp.org/ _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
