Network Time Protocol (NTP) is out of Sync for one server in the Cluster (Cluster of 3 servers)

Products

• CA API Gateway
• API SECURITY
• CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
• CA API Gateway Enterprise Service Manager (Layer 7)
• STARTER PACK-7
• CA Microgateway

Issue/Introduction

We are in middle of upgrading our API Gateway from 9.3CR03 to 9.4CR05

During doing the process, we noticed, NTP is out of Sync in the 3rd server in the cluster (Cluster is having 3 cluster) .

We tried below command,

[root@editedname23 init.d]# service ntpd stop
Shutting down ntpd: [ OK ]
[root@editedname23 init.d]# ntpdate 0.rhel.pool.ntp.org
5 Jan 10:48:24 ntpdate[5908]: no server suitable for synchronization found
[root@editedname23 init.d]# service ntpd start
Starting ntpd: [ OK ]

 

[root@editedname23 init.d]# date
Tue Jan 5 10:49:13 EST 2021
[root@editedname23 init.d]#

 

This server is 4hrs and 02 mins lagging of real time.

 

Please help us how to get the server in the cluster....

Environment

Release : 9.4

Component : API GATEWAY

Cause

NTP serves you chose have not been reachable from GW10

Resolution

selecte another ntp server resolved the issue.

you can check the ntpq-peers.txt file in the DCT to review the following :

Working ntpq-peers:

remote refid st t when poll reach delay offset jitter
==============================================================================
up2.com .INIT. 16 u - 1024 0 0.000 0.000 0.000
mongrel.ahem.ca .INIT. 16 u - 1024 0 0.000 0.000 0.000
smtp.irtech.ch .INIT. 16 u - 1024 0 0.000 0.000 0.000
ns3.switch.ca .INIT. 16 u - 1024 0 0.000 0.000 0.000
*LOCAL(0) .LOCL. 10 l 11 64 377 0.000 0.000 0.000

Non-working ntpq-peers:

remote refid st t when poll reach delay offset jitter
==============================================================================
time.cloudflare .INIT. 16 u - 64 0 0.000 0.000 0.000
ntp1.torix.ca .INIT. 16 u - 64 0 0.000 0.000 0.000
ntp1.ny1.ap-gp. .INIT. 16 u - 64 0 0.000 0.000 0.000
irc.gentoo.ca .INIT. 16 u - 64 0 0.000 0.000 0.000
*LOCAL(0) .LOCL. 10 l 61 64 377 0.000 0.000 0.000

If both servers have the same NTP configuration and same firewall rules, then the issue is likely to be outside of the server.

Problem It can be due your load balancers / firewalls outside of the API Gateway , need to confirm that the non-working server can still talk

to the same endpoints as the working nodes for the NTP servers they reach out to.