CME-4331 ISR - wrong Time (21 minutes ahead)!

[Imma]

Hello all,

I have a strange situation. The CME time was showing properly but just two days ago it changed. It is showing 21 minutes ahead.

clock timezone Albania 1 0
clock summer-time TIMESAVE recurring last Sun Mar 2:00 last Sun Oct 3:00

!

voice register global
mode cme
source-address 172.30.30.1 port 5060
timezone 28
time-format 24

date-format D/M/Y
dst start Mar day 31 time 02:00
dst stop Oct day 27 time 03:00
network-locale U1
ntp-server 172.30.30.1 mode directedbroadcast
auto-register

Any idea?

Thank you in advanced,

denisa

[Jonathan Unger]

Hi Dena,

Can you check the NTP sync on the router and current date/time to see if the router is out of sync?

The following commands should help:

1. show ntp status
2. show ntp associations
3. show clock

[Imma]

Hi Jonathan, 

Thank you for your reply.

After I changed manually the time of the router, it seems everything is OK. The router time is correct and the phone's time is synchronised with the router's time.

#show clock
08:49:54.485 TIMESAVE Tue Jul 16 2019

#show ntp associations

address ref clock st when poll reach delay offset disp
*~127.127.1.1 .LOCL. 7 12 16 377 0.000 0.000 1.204
~23.23.86.44 .INIT. 16 - 1024 0 0.000 0.000 15937.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

#show ntp status
Clock is synchronized, stratum 8, reference is 127.127.1.1
nominal freq is 250.0000 Hz, actual freq is 249.8776 Hz, precision is 2**10
ntp uptime is 179133700 (1/100 of seconds), resolution is 4016
reference time is E0D7F22C.676C8C60 (08:50:20.404 TIMESAVE Tue Jul 16 2019)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 2.37 msec, peer dispersion is 1.20 msec
loopfilter state is 'CTRL' (Normal Controlled Loop), drift is 0.000489467 s/s
system poll interval is 16, last update was 13 sec ago.

The question is if the problem would be repeated again?

Thank you again,

Denisa

[Jonathan Unger]

Hi Denisa,

It looks like your router may not be synchronizing with an external NTP server correctly. Can you try configuring a different NTP time source than the one indicated in red below (23.23.86.44)?The entry you see in the list for 127.127.1.1 is actually just a local reference indicating the router is using its local hardware clock. The hardware clock can drift over time which is why an NTP source is preferred.

#show ntp associations

address ref clock st when poll reach delay offset disp
*~127.127.1.1 .LOCL. 7 12 16 377 0.000 0.000 1.204
~23.23.86.44 .INIT. 16 - 1024 0 0.000 0.000 15937.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured

Here is an example of how you can use to configure a new NTP server:

ntp server 1.1.1.1 source GigabitEthernet 1/1

Be sure to specify the correct source interface if the router has more than one interface, otherwise you could end up with reachability issues.

Hope this helps!

[Imma]

Jonathan Hi,

Thank you for your help. I see. I did configured an ntp server of 0.europe.pool.ntp.org:

nslookup 0.europe.pool.ntp.org
Server: UnKnown
Address: 192.168.2.7

Non-authoritative answer:
Name: 0.europe.pool.ntp.org
Addresses: 185.123.84.51
85.254.217.2
95.216.101.162
92.62.34.78

I configured the first server as ntp server. I can ping it. But it is not synchronized yet. This router should behave as a client and as a ntp server for the phones.

#show ntp associations

address ref clock st when poll reach delay offset disp
*~127.127.1.1 .LOCL. 7 12 16 377 0.000 0.000 1.204
~185.123.84.51 .INIT. 16 - 512 0 0.000 0.000 15937.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
#ping 185.123.84.51
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 185.123.84.51, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 62/62/63 ms

ntp master
ntp server 185.123.84.51 source GigabitEthernet0/0/0.1004

Kind Regards,

Denisa

[Jonathan Unger · Accepted solution]

Hi Denisa,

Can you try sourcing your ping from the same interface that you have configured NTP to use and seeing if the ping still goes through?

ping 185.123.84.51 source GigabitEthernet0/0/0.1004

Additionally, I am fairly sure that the ntp pool is meant to use DNS, as they can change the servers over time, be aware that the server you configured now may not be available at some point. If this is an issue you could google for some NTP servers near you which have static IP addresses.

[Imma]

Amazing! Thank you Jonathan.

The source address GigabitEthernet0/0/0.1004 was not the right interface to reach the ntp server. 

Once I changed it with the right one, it was synchronised immediately. I used 0.europe.pool.ntp.org and it was synchronised to one server 194.58.205.20.

Kind Regards,

Denisa

[Jonathan Unger]

Hi Denisa,

Thanks for taking the time to come back and note that your issue was solved!

Glad it worked out.

- J