[ntp:questions] Problem facing with Ntp client Configuration
BP00106533 at TechMahindra.com
Thu Mar 27 09:49:46 UTC 2014
I have done the required changes. I have found one problem regarding condition field in ntpq
When ever I have restarted ntpd on client and executed ntpq "as"
ind assid status conf reach auth condition last_event cnt
1 45503 9044 yes yes none reject reachable 4
Condition field shows "reject" for more then 15 to 20 minute then after it changes to "sys.peer" after then only sync happens.
I have opened the port 123 for ntp. Still it shows reject
Please let me know reason for this to fix the issue
From: Danny Mayer [mailto:mayer at ntp.org]
Sent: Tuesday, March 25, 2014 9:44 PM
To: Biswajit Panigrahi; questions at lists.ntp.org
Subject: Re: [ntp:questions] Problem facing with Ntp client Configuration
On 3/25/2014 8:35 AM, Biswajit Panigrahi wrote:
> Hi All,
> When ever I configure ntp client ,then its takes more time even if 7minute to 8 minute difference is there between client and server.
> Please provide me the configuration which will sync within less time.
> Currently ntp.drift file is empty.shall we need to modify the same?
> Current NTP Client configuration is :
> server 10.16.188.254
Add iburst to this line.
Since this is an internal server can you add any more NTP servers? One
is not a good number 3 is good and 4 is better. Never use 2.
> server 127.127.1.0
> fudge 127.127.1.0 stratum 10
Get rid of these last two lines. Unless the ntp client is serving time
elsewhere it's not needed.
> restrict 10.16.188.254 mask 255.255.255.255 nomodify notrap noquery
> restrict 127.0.0.1
> broadcastclient novolley
> broadcastdelay 0
> keys /var/ntp/keys
> logfile /var/log/ntp/ntpd.log
> driftfile /var/log/ntp/ntp.drift
> statsdir /var/log/ntp/
> statistics loopstats peerstats
> filegen loopstats file loopstats type day enable
> filegen peerstats file peerstats type day enable
> Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
Not any more. This is a public mailing list and this message is now
available through Google search.
Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
More information about the questions