NTP Not working

[tchup]

hello,
I try to configure ntp on OS6360 but the sync never happens...

Code: Select all

OS6360 # show configuration snapshot ntp
! NTP:
ntp server clock1.ovcirrus.com iburst
ntp server clock0.ovcirrus.com iburst
ntp client admin-state enable

OS6360 # show ntp server client-list
Total: 0
IP Address                                    Ver   Key
---------------------------------------------+---+-------+

OS6360 # show ntp client server-list
Legends: + active peer, - passive peer, * current system peer,
         ^ broadcast server
Mode IP Address                                                             Ver   Key    St    When      Poll     Reach    Delay         Offset          Disp
----+----------------------------------------------------------------------+---+-------+----+---------+---------+-------+----------+-----------------+----------

OS6360 # show ntp client
Current time:                   Sun, Jul 24 2020 13:10:22.872 (CEST),
Last NTP update:                -,
Server reference:               INIT,
Client mode:                    enabled,
Broadcast client mode:          disabled,
Broadcast delay (microseconds): 4000,
VRF Name:                       default

OS6360 # show ntp server status
Host name          = clock1.ovcirrus.com,
iBurst             = yes,
Status             = not configured,

Host name          = clock0.ovcirrus.com,
iBurst             = yes,
Status             = not configured,

OS6360 # ip service ntp admin-state enable

OS6360 # show ip service

  Name                   Port   Status
----------------------+-------+---------
  ftp                      21   enabled
  ssh                      22   enabled
  telnet                   23   enabled
  http                     80   enabled
  ntp                     123   enabled
  snmp                    161   enabled
  radius                 3799   enabled

OS6360 # ntp key load
ERROR: Unable to open keys file

OS6360 # ping clock0.ovcirrus.com
PING 0.ovcirrus.pool.ntp.org (91.224.149.41) 56(84) bytes of data.
64 bytes from eva.aplu.fr (91.224.149.41): icmp_seq=1 ttl=61 time=21.5 ms
64 bytes from eva.aplu.fr (91.224.149.41): icmp_seq=2 ttl=61 time=17.1 ms
64 bytes from eva.aplu.fr (91.224.149.41): icmp_seq=3 ttl=61 time=17.0 ms
64 bytes from eva.aplu.fr (91.224.149.41): icmp_seq=4 ttl=61 time=16.9 ms

--- 0.ovcirrus.pool.ntp.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 16.995/18.168/21.529/1.945 ms

Thanks for your help !

[Gleylancer]

Why is eva.aplu.fr responding to your pings?

clock0.ovcirrus.com = 3.64.117.201
clock1.ovcirrus.com = 141.95.116.43
clock2.ovcirrus.com = 164.68.116.11

DNS issue? Packets being intercepted?

[tchup]

Servers change all the time...

Code: Select all

OS6360 # ping clock0.ovcirrus.com
PING 0.ovcirrus.pool.ntp.org (51.195.117.133) 56(84) bytes of data.
64 bytes from ntp6.kashra-server.com (51.195.117.133): icmp_seq=1 ttl=49 time=20.5 ms
64 bytes from ntp6.kashra-server.com (51.195.117.133): icmp_seq=2 ttl=49 time=16.5 ms
--- 0.ovcirrus.pool.ntp.org ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5003ms
rtt min/avg/max/mdev = 16.316/17.210/20.532/1.509 ms

OS6360 # ping clock0.ovcirrus.com
PING 0.ovcirrus.pool.ntp.org (95.81.173.74) 56(84) bytes of data.
64 bytes from ntp-2.arkena.net (95.81.173.74): icmp_seq=1 ttl=58 time=10.3 ms
64 bytes from ntp-2.arkena.net (95.81.173.74): icmp_seq=2 ttl=58 time=6.24 ms
--- 0.ovcirrus.pool.ntp.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 6.208/7.097/10.377/1.644 ms

I logged the traffic on the firewall: DNS requests ok, ping ok, but never an NTP request!

as if the client NTP service does not work with DNS... yet "clock0.ovcirrus.com" is part of the factory configuration

[tchup]

it works with:

Code: Select all

ntp server 3.64.117.201
ntp client admin-state enable

I would just like to understand why it does not work with the FQDN...

[blasterxi]

Hi, I believe you need to enable ip domain-lookup and add a name-server into it, then you would be able to ping from the switch via FQDN.