NTP admin needs to either fix the NTP resource or try a new NTP server until criteria is validated
Some basics on NTP:
[admin@aawg ~]$ ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp1.company. 192.168.110.100 2 u 41 64 377 26.181 4200.95 1.485
The ntpstat command will show if basic criteria met, synchronized. If unsynchronized then something is not healthy with the ntp resource. The ntpq -p command will show but if there is no * next to the remote name then the resource is not trusted for some reason. The likely reason is high root dispersion.
[admin@aawg ~]$ ntpq -nc ass
ind assid status conf reach auth condition last_event cnt
===========================================================
1 28029 9024 yes yes none reject reachable 2
[admin@aawg ~]$ ntpq
ntpq> rv 28029
associd=28029 status=9024 conf, reach, sel_reject, 2 events, reachable,
srcadr=ntp1.company.domain, srcport=123, dstadr=172.16.24.33,
dstport=123, leap=00, stratum=2, precision=-23, rootdelay=41.397,
rootdisp=10243.896, refid=192.168.110.100,
reftime=deb177e7.966eb265 Thu, May 24 2018 12:41:59.587,
rec=deb17a6e.cd5dbf44 Thu, May 24 2018 12:52:46.802, reach=037,
unreach=0, hmode=3, pmode=4, hpoll=6, ppoll=6, headway=313,
flash=400 peer_dist, keyid=0, offset=1.268, delay=25.702,
dispersion=0.925, jitter=0.764, xleave=0.083,
filtdelay= 25.70 25.76 25.70 26.08 25.97 25.96 25.67 26.14,
filtoffset= 1.27 1.00 0.76 0.62 0.44 0.40 0.22 0.38,
filtdisp= 0.00 1.02 2.01 3.03 3.89 3.92 3.95 3.98
Above shows the root dispersion is 10243.896 ms, this is too high. In basic terms the root dispersion is the longest amount of time the client and server have been out of communication at any one point during the span of the connection. If the root dispersion is too high then the client will REJECT it as a valid source.
There is also a way to get ntpd startup to essentially ignore the high root dispersion. Here's an example that corrected this problem on an AMM server:
sudo /bin/systemctl stop ntpd
sudo ntpd -gq
sudo /bin/systemctl start ntpd
The -gq flags are useful if customer is using a Windows time server
If customer does not have a good NTP server in internal network, they can try to use a global NTP server address, for example : 88.147.254.230, we have validated this global ntp server address in one of customer's system already.
Add the NTP server below in /etc/ntp.conf in AAWG server.
server 88.147.254.230 iburst maxpoll 10
restrict 88.147.254.230 mask 255.255.255.255 nomodify notrap noquery
