cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2214
Views
0
Helpful
0
Replies

ntp drift not saved

Hello everybody!

I'm trying to configure ntp server on ASR1002f (

asr1000rp1-advipservicesk9.03.09.01.S.153-2.S1.bin)

, but i get a lot of annoying log messages like this:

Jul 30 20:14:56.180 MSK: %NTP : Drift Value NTPv4_Drift=0.E68F not saved in persistent data, will be stored before reload

Jul 30 21:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.EB94 not saved in persistent data, will be stored before reload

Jul 30 22:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.EBA9 not saved in persistent data, will be stored before reload

Jul 30 23:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.F3EF not saved in persistent data, will be stored before reload

Jul 31 00:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.F53E not saved in persistent data, will be stored before reload

Jul 31 01:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.F5C4 not saved in persistent data, will be stored before reload

Jul 31 02:14:56.180 MSK: %NTP : Drift Value NTPv4_Drift=0.FAC5 not saved in persistent data, will be stored before reload

Jul 31 03:14:56.180 MSK: %NTP : Drift Value NTPv4_Drift=0.FAD9 not saved in persistent data, will be stored before reload

Jul 31 04:14:56.180 MSK: %NTP : Drift Value NTPv4_Drift=0.FAE5 not saved in persistent data, will be stored before reload

Jul 31 05:14:56.179 MSK: %NTP : Drift Value NTPv4_Drift=0.FAF1 not saved in persistent data, will be stored before reload

Could someone clarify what does this mean and how to stop this?

If I turn on ntp logging I get periodic ntp messages like so:

.Jul 26 15:52:40.790 MSK: NTP Core (INFO): 0.0.0.0 C618 08 no_sys_peer

.Jul 26 15:52:40.790 MSK: NTP Core (INFO): 0.0.0.0 C61C 0C clock_step

.Jul 26 15:52:41.789 MSK: NTP Core (INFO): 192.168.10.225 962A 8A sys_peer

.Jul 26 15:52:41.789 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 26 15:52:42.201 MSK: NTP Core (INFO): 0.0.0.0 C62C 0C clock_step

Jul 26 15:52:42.201 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 26 15:53:37.792 MSK: NTP Core (INFO): IP1 962A 8A sys_peer

.Jul 26 15:53:37.792 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 26 16:04:51.791 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 26 16:04:51.791 MSK: NTP Core (INFO): IP2 962A 8A sys_peer

.Jul 26 16:04:51.791 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 26 16:07:05.791 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 26 16:07:05.791 MSK: NTP Core (INFO): IP3 962A 8A sys_peer

.Jul 26 16:07:05.791 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 27 12:29:47.789 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 27 12:29:47.789 MSK: NTP Core (INFO): IP2 961A 8A sys_peer

.Jul 27 12:29:47.789 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 27 14:38:23.792 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 27 14:38:23.792 MSK: NTP Core (INFO): IP1 961A 8A sys_peer

.Jul 27 14:38:23.792 MSK: NTP Core (NOTICE): Clock is synchronized.

Jul 27 15:41:33.790 MSK: NTP Core (NOTICE): Clock synchronization lost.

.Jul 27 15:41:33.790 MSK: NTP Core (INFO): IP3 961A 8A sys_peer

.Jul 27 15:41:33.790 MSK: NTP Core (NOTICE): Clock is synchronized.

0 Replies 0