NTP on Avaya Aura
Network Time Protocol and how to set it up and troubleshoot it on Avaya Aura Products
Description

This article will show you how to trouble the Network Time protocol service on Linux Servers.

This article applies to several Avaya products as well as any other server we happen to work with.

Requirements

This article assumes you have access to a Linux server to follow along with.

Configuration files

In Linux the following files control how the NTP service operates. Viewing these files will show you all of the startup operations that will be passed to the NTP daemon on a Linux server.

/etc/ntp.conf
/etc/sysconfig/ntpd


Example ntp.conf file

driftfile /var/lib/ntp/ntp.drift
restrict default ignore
server ntp.tmpw.net iburst
restrict ntp.tmpw.net mask 255.255.255.255 nomodify notrap noquery
restrict 127.0.0.1
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10


Here we can see that we have our server set to pull time from server ntp.tmpw.net this means that our Linux server is going to pull its network time from ntp.tmpw.net. We would want to ping this server to make sure it is in fact reachable.

NTP reachability

The network time protocol uses TCP and UDP ports 123 from Linux. This means that in our example our server will try sending a packet to ntp.tmpw.net with a destination port of UDP 123 most likely. So any firewalls in between our server and the time server need to allow port 123 to be open.

NTP Commands

To view the current date and time on the linux server, type the command: date

user@host> date

Fri Aug 28 13:30:43 EDT 2020


To view the list of NTP servers and which server is being used, type the command:

/usr/sbin/ntpq -p

NOTE: The asterisk indicates the NTP server that is being utilized. If the asterisk is next to the line that says LOCAL, the NTP servers are not being used and most likely are not able to be reached from the linux server.

dadmin@localhost> /usr/sbin/ntpq -p

remote refid st t when poll reach delay offset jitter

==============================================================================

AMA-vDC02.actme .LOCL. 1 u 960 1024 377 0.205 -2736.7 20.455

*AMA-pDC04.actme 50.205.57.38 3 u 197 1024 377 0.340 0.101 0.045

LOCAL(0) .LOCL. 10 l 23h 64 0 0.000 0.000 0.000


To view the NTP servers configured to use, type the command: grep server /etc/ntp.conf

dadmin@localhost> grep server /etc/ntp.conf

server 172.19.30.11 prefer iburst

server 172.19.40.12 iburst

server 127.127.1.0 # local clock


To determine if the NTP server configured is synchronized or not, type the command: ntpdate -q x.x.x.x (IP address of the NTP server)

NOTE: In this example the NTP server is not synchronized with Communication Manager

dadmin@localhost> ntpdate -q 10.0.1.14

server 10.0.1.14, stratum 0, offset 0.000000, delay 0.00000

28 Aug 13:55:13 ntpdate[21736]: no server suitable for synchronization found


NOTE: In this example the NTP server IS synchonized to pull the correct time.

dadmin@localhost> ntpdate -q 172.19.30.11

server 172.19.30.11, stratum 1, offset -2.743310, delay 0.04146

28 Aug 13:58:46 ntpdate[22972]: step time server 172.19.30.11 offset -2.743310 sec
Was this article helpful?
Cancel
Thank you!