[ntp:questions] Unable to synchronise meinberg ntp server to clients.
david at ex.djwhome.demon.invalid
Thu Sep 15 20:32:04 UTC 2011
Samuel Nyarko wrote:
> I am currently working on time synchronisation in wireless sensor
> networks. I am using meinberg ntp software but i am having some small
Meinberg do not supply the software you are using, they only supply the
installer. The software is owned by the University of Delaware.
> # your local system clock, should be used as a backup
> # (this is only useful if you need to distribute time no matter how
> good or bad it is)
> server 127.127.1.1
This is misleading. The local system clock WILL be used as a backup
(and to interpolate between polls). 127.127.1.1 should only be used if
the bit in parentheses really is true. Sometimes setting this can
prevent ntpd locking onto a real server.
> restrict 192.168.0.0
With classless routing, this could be a host, but it is unlikely.
> # Please note that you need at least four different servers to be at
> least protected against
> #peer 192.168.3.189
> #restrict 192.168.3.189 mask 255.255.255.255 nomodify notrap noquery
> server 192.168.3.100/24
What does /24 mean?
> restrict 192.168.3.100 mask 255.255.255.255 nomodify notrap noquery
> server 0.fi.pool.ntp.org minipoll 10 iburst
> server 1.fi.pool.ntp.org minpoll 10 iburst
The mistake most people make is setting minpoll too low. This is too high.
> State Remote Refid Stratum Type When Poll Reach Delay Offset Jitter
> LOCAL(1) LOCL 12 Local clock 11 64 007 0.000 0.000 0.001
> 188.8.131.52 184.108.40.206 2 Unicast server 9 64 007
> 0.779 -16.005 3.750
ntpd hasn't been up long enough, or has had a recent time step.
More information about the questions