Sync source pointing to LOCAL(0) instead of NTP server

Server operators
1

I have configured the management NTP server and the ip address is 172.30.148.40.

I configure the NTP server and Peer details in NE#1 after that Configure NTP peer details in NE#2.

Initially in NE1 it’s pointing NTP server as sync source. After deleting the NTP peer in NE#1 the LOCAL(0)

updated as sync source instead of NTP server. Please share if you have input.

root@NE# run show ntp associations detail
remote refid st t when poll reach delay offset jitter

192.168.127.255 .BCST. 16 B - 64 0 0.000 +0.000 0.031
*172.30.148.40 .LOCL. 1 u 4 16 37 0.404 +2.148 1.154
LOCAL(0) .LOCL. 10 l 83 64 2 0.000 +0.000 0.031
172.30.88.156 .STEP. 16 s - 16 0 0.000 +0.000 0.000

After deleting the NTP peer in NE#1, the LOCAL(0) become sync source instead of NTP server

root@NE# ntpq -p
remote refid st t when poll reach delay offset jitter

192.168.127.255 .BCST. 16 B - 64 0 0.000 +0.000 0.002
172.30.148.40 .INIT. 16 u - 1024 0 0.000 +0.000 0.000
*LOCAL(0) .LOCL. 10 l 15 64 377 0.000 +0.000 0.002
[root@RCP194 log]#

This is ntp.conf file.

[root@NE# ~]# cat /config/etc/ntp.conf
broadcast 192.168.127.255
interface listen all
interface ignore fe80::/10
server 172.30.148.40 key 12 version 3 prefer minpoll 4 maxpoll 14
server 127.127.1.0
fudge 127.127.1.0 stratum 10
keys /etc/ntp/keys
trustedkey 12
tinker panic 1000
[root@NE# ~]#

2

I don’t get it, you are synching local-clocks?

What’s the point of that? As local-clocks are not accurate at all.

Normally you use other sources like GPS, PPS, DCF or simply online NTP-servers to make sure you have the correct time.

Local clocks are known to tick false.