Jump to content
ccie109

NTP issue on eve-ng

Recommended Posts

Hi All,

Iam having problems getting ntp to work for some devices in my eve-ng lab

 

 

R1(ntp server)is connected as per lab topology to R2, R15, R16, R17 via management plane

R2 gets synchronzed fine but rest of the devices couldnt get synchronozed

 

R1 (ntp server)

ntp authentication-key 12 md5 030752180500 7

ntp authenticate

ntp trusted-key 12

ntp source GigabitEthernet3

ntp master 1

R1(config)#

 

R15: (ntp client)

R15(config)#do sh run | in ntp

ntp logging

ntp authentication-key 12 md5 030752180500 7

ntp authenticate

ntp trusted-key 12

ntp source Ethernet0/0

ntp server 150.1.7.231 key 12

R15(config)#

 

Working ntp client:

R2(config)#do sh ntp status

Clock is synchronized, stratum 2, reference is 150.1.7.231

nominal freq is 250.0000 Hz, actual freq is 249.9972 Hz, precision is 2**10

ntp uptime is 133700 (1/100 of seconds), resolution is 4016

reference time is E1637AD7.D7CEDB68 (18:58:31.843 PST Tue Oct 29 2019)

clock offset is 7.5000 msec, root delay is 3.00 msec

root dispersion is 19.45 msec, peer dispersion is 3.61 msec

loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000011207 s/s

system poll interval is 64, last update was 53 sec ago.

R2(config)#

 

 

Not working:

R15(config)#

R15(config)#do sh ntp status

Clock is unsynchronized, stratum 2, reference is 150.1.7.231

nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10

ntp uptime is 135400 (1/100 of seconds), resolution is 4000

reference time is E1637BCD.E41895E8 (19:02:37.891 PST Tue Oct 29 2019)

clock offset is -933.9999 msec, root delay is 0.00 msec

root dispersion is 8876.59 msec, peer dispersion is 7938.47 msec

loopfilter state is 'SPIK' (Spike), drift is 0.000000000 s/s

system poll interval is 64, last update was 64 sec ago.

R15(config)#

 

 

Ip connectivity is fine, I can ping all of the devices ntp source ip addresses.

I even see it in the debugs on R15(and other devices) that the clock has been updated

 

*Oct 30 03:10:52.891: %SYS-6-CLOCKUPDATE: System clock has been updated from 19:10:52 PST Tue Oct 29 2019 to 19:10:52 PST Tue Oct 29 2019, configured from NTP by 150.1.7.231.

R15(config)#

*Oct 30 03:10:52.891: NTP Core (NOTICE): time reset -0.934499 s

*Oct 30 03:10:52.891: NTP Core (NOTICE): trans state : 5

*Oct 30 03:10:53.892: NTP Core (INFO): 150.1.7.231 E074 84 reachable

*Oct 30 03:10:53.892: NTP Core (INFO): 150.1.7.231 F68A 8A sys_peer

*Oct 30 03:10:53.892: NTP Core (NOTICE): Spike event s

 

However " sh ntp status " still shows clock has been unsynchronized.

 

The way configured it, I copied the key from master. Shouldnt be an issue since r2 gets synchronized fine.

 

ntp authentication-key 12 md5 14141B180F0B 7

 

I even tried manually setting keys on all devices with this command

ntp authentication-key 12 md5 cisco

 

 

To me, it looks like an issue with the ios version. Since the non working routers are on on

same type of linux iol images and working one looks like a proper CSR image.

 

Any ideas/suggestions? Am i missing something?

 

Thanks,

Share this post


Link to post
Share on other sites

Hi,

 

I have same issue/output.

R2 can sync, but R15, R16, R17 not, maybe it is due to the fact that both R1 and R2 are CSRs, while other 3 not, and it is EVE-NG environment.

I found that GNS has same issues, since they are both virtual.

On lab it should be fine (or at least we can try to reboot)

Share this post


Link to post
Share on other sites

ok cool, just wanted to make sure. Thanks

wondering if anyone knows a way/hack to make it work on eve-ng/GNS

 

Hi,

 

I have same issue/output.

R2 can sync, but R15, R16, R17 not, maybe it is due to the fact that both R1 and R2 are CSRs, while other 3 not, and it is EVE-NG environment.

I found that GNS has same issues, since they are both virtual.

On lab it should be fine (or at least we can try to reboot)

Edited by ccie109

Share this post


Link to post
Share on other sites

ok cool, just wanted to make sure. Thanks

wondering if anyone knows a way/hack to make it work on eve-ng/GNS

 

no hacks I am aware of..

 

in my eve-ng I ended up running the NTP master on R17 and then making R15 and R16 sync with R17. Just so I new my certs were good.

Share this post


Link to post
Share on other sites

ntp is slow protocol for update u have to be patient on eve...+ u can put only IOL L3 Router MAY 2018 on eve and L2 may for switch on my side on all devices synchronized... CSR not need on eve... taking age too boot and take more ressources

 

Hidden Content

    Give reaction to this post to see the hidden content.

Edited by kamui

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...