[ntp:questions] NTP not syncing to configured servers

Chandra Kanth kckanth21 at gmail.com
Wed May 13 16:00:58 UTC 2015


Also you can see that the reach is 377 to both of the servers. So reach is
not a problem and not firewall issue etc.
It is something to do with the algorithm. Why ntp has rejected the servers?
Based on what values?
Is it offset, jitter, etc?

Thanks
Chandrakanth

On Wed, May 13, 2015 at 9:28 PM, Chandra Kanth <kckanth21 at gmail.com> wrote:

> Hi Graves, Yu,
>
> First of all thanks for response. Let me clarify, this is private lab
> setup, no public ntp servers.
> The idea is to setup private ntp subnet, where the time on servers such as
> .198 and .204 should be propagated to other clients.
>
> Think as .198 and .204 as private ntp servers which is configured as lower
> stratum server. (i.e. /etc/ntp.conf contains stratum 5). So these servers
> does not get a reference clock from any other lower stratum i.e. stratum 4.
> It simply provides system time from its own local clock.
>
> The client here which .196 is running at higher stratum i.e. 10.
>
> So I'm was hoping the client (.196) should sync to any one of the server
> since at least their stratum is lower.
>
> I hope the question is clear.
>
> Regards
> Chandrakanth
>
>
> On Wed, May 13, 2015 at 7:42 PM, Dallas Graves <dallasg79 at gmail.com>
> wrote:
>
>> To expound upon Yu’s comment.  If you don’t have access to the firewall,
>> a good check would be to conduct a test against each of your targeted NTP
>> servers with the “ntpdate -d” command, which is the debug switch and will
>> let you know if you can or cannot reach the intended systems.
>>
>> -Dallas
>>
>>
>> > On May 13, 2015, at 8:54 AM, Wang, Yu <ywang10 at fsu.edu> wrote:
>> >
>> > Do your ntp servers have public IP addresses configured or do you do
>> NAT for the two ntp servers? 10.126.142.198 and 10.126.142.204 are private
>> addresses and won't be routed over the Internet.
>> > The second place to check is firewall. Make sure it opens to upd/123
>> between your ntp servers and outside ntp servers.
>> >
>> > Yu
>> > Core Networking, FSU
>> >
>> >
>> > -----Original Message-----
>> > From: questions [mailto:questions-bounces+ywang10=fsu.edu at lists.ntp.org]
>> On Behalf Of Chandrakanth K
>> > Sent: Wednesday, May 13, 2015 7:52 AM
>> > To: questions at lists.ntp.org
>> > Subject: [ntp:questions] NTP not syncing to configured servers
>> >
>> > Hi,
>> >
>> > I am seeing ntp not syncing to external configured servers. We tried
>> both 4.2.4 and 4.2.6 versions.
>> > The following is the configuration,
>> >
>> > We use two servers 10.126.142.198 and 10.126.142.204 in our Lab.
>> > They are statically configured as running @ stratum level 5 and
>> providing the clock from its own local clock.
>> >
>> > Even though the servers does not have a valid reference time and
>> provides time from its own clock, according to me still we need to be able
>> to sync to it since it is running at better stratum.
>> > Please clarify.
>> >
>> > Logs:
>> > -------------------------
>> >
>> > bash-4.2$ ntpq -np -c assoc
>> >     remote           refid      st t when poll reach   delay   offset
>> jitter
>> >
>> ==============================================================================
>> > *127.127.1.0     .LOCL.          10 l   19   64  377    0.000    0.000
>>  0.001
>> > 10.126.142.198      LOCAL(0)         6 u    7   16  377    0.172
>> 859.844   0.501
>> > 10.126.142.204      LOCAL(0)         6 u   15   16  377    0.227
>> 1057.22   0.240
>> >
>> > ind assID status  conf reach auth condition  last_event cnt
>> ===========================================================
>> >  1 26554  9614   yes   yes  none  sys.peer   reachable  1
>> >  2 26555  9014   yes   yes  none    reject   reachable  1
>> >  3 26556  9014   yes   yes  none    reject   reachable  1
>> >
>> > Logs: 10.126.142.198
>> > -----------------------------------
>> > bash-4.2$ ntpq -np -c assoc
>> >     remote           refid      st t when poll reach   delay   offset
>> jitter
>> >
>> ==============================================================================
>> > *127.127.1.0     .LOCL.           5 l   10   64  377    0.000    0.000
>>  0.000
>> >
>> > ind assid status  conf reach auth condition  last_event cnt
>> ===========================================================
>> >  1 48508  965a   yes   yes  none  sys.peer    sys_peer  5
>> >
>> >
>> > Logs: 10.126.142.204
>> > -----------------------------------
>> >
>> > bash-4.2$ ntpq -np -c assoc
>> >     remote           refid      st t when poll reach   delay   offset
>> jitter
>> >
>> ==============================================================================
>> > *127.127.1.0     .LOCL.           5 l   13   64  377    0.000    0.000
>>  0.000
>> >
>> > ind assid status  conf reach auth condition  last_event cnt
>> ===========================================================
>> >  1 32737  963a   yes   yes  none  sys.peer    sys_peer  3
>> >
>> >
>> > Regards
>> > Chandrakanth
>> > _______________________________________________
>> > questions mailing list
>> > questions at lists.ntp.org
>> > http://lists.ntp.org/listinfo/questions
>> > _______________________________________________
>> > questions mailing list
>> > questions at lists.ntp.org
>> > http://lists.ntp.org/listinfo/questions
>>
>> _______________________________________________
>> questions mailing list
>> questions at lists.ntp.org
>> http://lists.ntp.org/listinfo/questions
>>
>
>


More information about the questions mailing list