[ntp:questions] NTP - orphan mode with SAME stratum ("tos orphan 6") FAIL to sync.
sheikdawoodrajali at gmail.com
sheikdawoodrajali at gmail.com
Wed Apr 8 03:58:33 UTC 2009
On Apr 6, 7:05 pm, Steve Kostecke <koste... at ntp.org> wrote:
> On 2009-04-06, sheikdawoodraj... at gmail.com <sheikdawoodraj... at gmail.com> wrote:
> [snip: a 27 line block of text]
> > Yes, that's what I'm experimenting now.
> What are you experimenting with?
> > I beleive the Orphan Broadcast Mesh will work when none of the
> > systems configured with external time servers at all.
> Why don't you test it? I have.
> > I saw it working time-sync'ed after adding shim value "tos mindist
> > 0.010" for correctness interval.
> I've conducted extensive testing with Orphan Mode and never had to add
> a tos mindist command.
> > I beleive the "time island" concept will work fine
> The nodes will all be chasing whichever clock is chosen as the master.
> > and time-sync will happen regardless of ANY time set in ALL the nodes
> > running NTP service.
> Why would you be changing the clock on systems which are running ntpd?
> > Is there any restrictions in time difference on a time island (30
> > minutes or less)??
> Restrictions in the time island between what things?
> > Here is the "ntp.conf" file on ALL the systems (7 nos):
> > ------------------------------------------------------------------
> > driftfile "C:\Program Files\NTP\etc\ntpd.drift"
> > keys "C:\Program Files\NTP\etc\ntpd.keys"
> > trustedkey 1
> > # Any clock offset will be accepted
> > tinker panic 0
> > #shim added to the correctness interval
> > tos mindist 0.010
> > # We participate as orphans to auto-find a Time Server
> > tos orphan 6
> > # Default restrict all
> > restrict default ignore
> > # Allow local host for utilities like ntpq
> > restrict 127.0.0.0 mask 255.0.0.0
> > # Allow communication over primary
> > restrict <primary IP> mask 255.240.0.0 nomodify notrap
> > # Allow communication over secondary
> > restrict <secondary IP> mask 255.240.0.0 nomodify notrap
> > broadcastclient
> > broadcast xx.yy.255.255 key 1
> > broadcast xx.zz.255.255 key 1
> What is the purpose of broadcasting on two different addresses?
> Steve Kostecke <koste... at ntp.org>
> NTP Public Services Project -http://support.ntp.org/- Hide quoted text -
> - Show quoted text -
Regarding the "Broadcast" address, the nodes configure their two
network cards using the network id of xx.0.0.0 with a netmask of
255.240.0.0 so the correct network brodcast addresses are xx.yy.
255.255 on the primary network and xx.zz.255.255 on the secondary
The primary and secondary network are configured according to an
algorithm that encodes physical and logical configuration information
into the ip address. Every interface uses the 255.240.0.0 netmask
when configured with a Class A network id. The primary and secondary
networks are not routed.
Is broadcasting to more than one address will create any problem's in
And I do noticed "bind() fd 248, family 2, port 123, addr
22.214.171.124, in_classd=0 flags=0x8 fails: Can't assign requested
error when I maintian the broadcast configuration in the below order.
But I did not see any error eventlog when the broadcast order is
broadcast xx.yy.zz.255 key 1
More information about the questions