NTP Sync Issue on Avaya CM

[makemetrend]

● ntpdate.service - Set time via NTP
Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-02-12 01:09:05 PST; 12s ago
Main PID: 10103 (code=exited, status=1/FAILURE)

/usr/sbin/ntpdate -d -q 10.0.110.79
12 Feb 01:16:14 ntpdate[10693]: ntpdate 4.2.6p5@1.2349-o Mon Oct 9 16:33:12 UTC 2017 (1)
Looking for host 10.0.110.79 and service ntp
host found : mvprd-ntp01.makatimed.local
transmit(10.0.110.79)
receive(10.0.110.79)
transmit(10.0.110.79)
receive(10.0.110.79)
transmit(10.0.110.79)
receive(10.0.110.79)
transmit(10.0.110.79)
receive(10.0.110.79)
10.0.110.79: Server dropped: Server has gone too long without sync
server 10.0.110.79, port 123
stratum 3, precision -24, leap 00, trust 000
refid [10.0.110.79], delay 0.02574, dispersion 0.00000
transmitted 4, in filter 4
reference time: e3b8dfae.34263cc3 Mon, Jan 25 2021 14:11:58.203
originate timestamp: e3cf747e.db880b22 Thu, Feb 11 2021 17:16:46.857
transmit timestamp: e3cfe4e4.230649fd Fri, Feb 12 2021 1:16:20.136
filter delay: 0.02576 0.02576 0.02574 0.02576
0.00000 0.00000 0.00000 0.00000
filter offset: -28773.2 -28773.2 -28773.2 -28773.2
0.000000 0.000000 0.000000 0.000000
delay 0.02574, dispersion 0.00000
offset -28773.279370

12 Feb 01:16:20 ntpdate[10693]: no server suitable for synchronization found


We cant define the NTP on Avaya CM upon checking the logs we saw this.

 

[AvayaTier3]

CM software version and hardware platform?

For each server:
cat /etc/ntp/drift



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[LoPath]

May be worth testing to ensure your NTP server is behaving. Here's an app that should do the job:

https://www.galsys.co.uk/categories/ntp-server-checker.html

Example from testing my NTP server:

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4 & V6, OpenScape Xpressions V7, OpenScape Contact Center V8, OpenScape Voice V9

 

[kyle555]

ntpq -p

 

[makemetrend]

Upon checking on wireshark the reference timestap is out of date.

But the client is saying that their NTP is working fine even if I told them the reference timestamp is out of date.