NTP server - problem

RouterOS General
1

Hi
I have run NTP server version 6..47.6 on x86.
my config:
system ntp server print
enabled: yes
broadcast: no
multicast: no
manycast: no

client config:
/system ntp client print
enabled: yes
primary-ntp: 10.10.99.103
secondary-ntp: 10.1.1.11
server-dns-names:
mode: unicast
poll-interval: 16s
active-server: 10.1.1.11
last-bad-packet-from: 10.10.99.103
last-bad-packet-before: 26s210ms
last-bad-packet-reason: server-not-synchronized

My client not synchronized with server. In log i see:
17:55:03 ntp,debug,packet sending to 10.10.99.103 NTP packet (48 bytes)
17:55:03 ntp,debug,packet VN=4
17:55:03 ntp,debug,packet Mode=3 (Client)
17:55:03 ntp,debug,packet TransmitTimestamp=e33c45f7e5c853c1
17:55:03 ntp,debug Wait for 16 seconds before sending next message
17:55:03 ntp,debug,packet ignoring received NTP packet (48 bytes)
17:55:03 ntp,debug,packet LI=3
17:55:03 ntp,debug,packet VN=4
17:55:03 ntp,debug,packet Mode=4 (Server)
17:55:03 ntp,debug,packet Stratum=0 (KoD)
17:55:03 ntp,debug,packet Poll=3
17:55:03 ntp,debug,packet Precision=-21
17:55:03 ntp,debug,packet RootDelay=0
17:55:03 ntp,debug,packet RootDispersion=0
17:55:03 ntp,debug,packet ReferenceID=INIT
17:55:03 ntp,debug,packet OriginateTimestamp=e33c45f7e5c853c1
17:55:03 ntp,debug,packet ReceiveTimestamp=e33c46047ba6f7d4
17:55:03 ntp,debug,packet TransmitTimestamp=e33c46047bb5930d

what is wrong?

2

any idea?

3

The status of client says it:

last-bad-packet-from: 10.10.99.103
last-bad-packet-before: 26s210ms
last-bad-packet-reason: > server-not-synchronized

So how exactly is NTP server configured? It should be configured as a client at the same time so that it gets precise time from somewhere.

BTW, if you’re running CHR variant: having bare-metal host synchronized doesn’t make VM’s timing precise, there’s a plethora of problems with synchronizing VM to host OS through hypervisor API, some virtualization platforms are less bad than others (and none is great). Guest OS (in your case CHR) needs its own external synchronization to be sure that its “wall clock” is precise.
If you’re running ROS x86, then properly running NTP client is even more important.

4

It is it. I set ntp client in my ntp server (x86) and now work fine. Thanks for good idea and help:)