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

NTP Falseticker on ASR1k

 

Hi,

 

I recently upgraded asr1002x acting as ntp server from 3.7 to 3.16.6

Another asr1002 is also a server running 3.7

 

Before the upgrade a client used to sync with both ASR1002x without issues

After the upgrade, client syncs to both ASR1k but the newly upgraded server is set as 'falseticker' 

 

If I configure the client to only sync to the newly upgraded box running 3.16.6 it works fine, but when I add the old box back as server, the newer one is set to falseticker.

 

client#sh ntp assoc

  address         ref clock       st   when   poll reach  delay  offset   disp
*~a.b.c.e  a.b.c.f     2    969   1024   377  0.000   1.000  1.974
x~a.b.c.d  a.b.c.g     2    750   1024   377  0.000 -42.000  1.984
 * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

 

The only pointer is the rather high offset, but no sure if that is consequence or cause of the issue/upgrade

 

Has anyone encountered such an issue or can offer troubleshooting commands to understand whats going on ?

 

I see an old post from some 6 years back where it was stated that NTP code was upgraded in more recent release of IOS, making it more stringent, but since this post was back in 2011 I doubt its relevant to my case

 

 thanks

 

Mark

2 Replies 2

Isaac Smith
Level 1
Level 1

Did you ever figure this out?  We recently replaced a NTP server and i'm seeing VERY high offset and the same falseticker designation

Isaac Smith
Level 1
Level 1

Did you ever figure this out?  We recently replaced a NTP server and i'm seeing VERY high offset and the same falseticker designation