I'm using n. 1 ntp server (XNTPD daemon on HP-UX, called FORCLIENTS,
192.168.1.240) for my clients and I'm obtaining the message
synchronization
lost about every 20 minutes.
Source time is another server (MASTER) on my lan
which updates its time
directly from Internet servers.
MASTER is OK
Below is my loopstats file:
56432 37096.090 0.0 0.854 0.01907 0.00 5
56432 37193.357 -0.000498569 0.854 0.000176280 0.00 5
56432 37356.388 -0.000635872 0.459 0.000171892 0.139789 5
56432 37581.427 -0.000141746 0.337 0.000237431 0.137653 5
56432 37587.427 0.000378025 0.346
What do you think about this NTP configuration for my company ?
I have n.1 NTP
server called 'A' (which is among private and pubblic network) and it retrieves
time from 4 time servers on Internet.
I have n.2 NTP server called 'B' and 'C'
(which are in private network) and they are used from
Unruh,
I don't happen to own David Mill's book, but I understand what you are
saying to be true. My concern is that too much data is being thrown away
when polling above 256 seconds and that allows excessive wandering of my
clock. Yes, I can cap the interval to 256, but is that the only answer?
Why are you doing this?
restrict 10.2.3.5
This is the server you want your clients to sync to, isn't it?
Regards,
Ed
-Original Message-
From: questions-bounces+edward.mischanko=arcelormittal@lists.ntp.org
[mailto:questions-
In an amazingly counter-intuitive manner, a restrict keyword with just
an IP address means that the IP address should have no restrictions. It
is therefore very common to see a line like:
restrict default ignore
Which says to ignore all packets from everywhere, and then to see a
series of
On 21/05/2013 14:31, Riccardo Castellani wrote:
n.4 srv Internet-- server A
server A -- server B
server
A -- server C
A is my internal source
B,C are cluster machine so hardware
is reliable but I don't want to present these servers directly on pubblic
network
My comments:
1)
On 2013-05-21, Mischanko, Edward T edward.mischa...@arcelormittal.com wrote:
My concern is that too much data is being thrown away when polling
above 256 seconds and that allows excessive wandering of my clock.
The clock filter algorithm processes the offset and delay samples
produced by the
Yes this is the server (192.168.1.140) which my clients will use.
I want to allow unrestricted access by 10.2.3.5 host (my private 'source
time server' ), because Server 10.2.3.5 will drive my server (192.168.1.140)
Do you think it's unnecessary option ?
NTP documents says:
1- Add the
thanks, you act before myself !
- Original Message -
From: Brian Utterback brian.utterb...@oracle.com
To: questions@lists.ntp.org
Sent: Tuesday, May 21, 2013 3:55 PM
Subject: Re: [ntp:questions] Offset is always increasing
In an amazingly counter-intuitive manner, a restrict keyword
On 2013-05-21, Mischanko, Edward T edward.mischa...@arcelormittal.com wrote:
My concern is that too much data is being thrown away when polling
above 256 seconds and that allows excessive wandering of my clock.
If too much data is being thrown away, it would be because the poll
adjust
Riccardo Castellani wrote:
server 127.127.1.1
fudge
127.127.1.1 stratum 10 # show poor quality
Remove these until you get it working, and then only re-add them if the
system is serving time to downstream systems and you really understand
why you are using them. Leaf systems never need it
12 matches
Mail list logo
