Is there setting, which can be applied on NTP servers or individual clients and tell it, do not sync with bad ones, because sudden 19 years drop doesn't make sense. Why it couldn't not have synced with good GPS device and picked date from bad ones ? There was one good, out of 3.
time-serv1 # cat /etc/inet/ntp.conf server 192.168.xx.xx server 172.28.42.xx server 172.28.34.yy driftfile /var/ntp/ntp.drift statsdir /var/ntp/ntpstats/ filegen peerstats file peerstats type day enable filegen loopstats file loopstats type day enable filegen clockstats file clockstats type day enable time-serv1 # time-serv1 # ntpq -p remote refid st t when poll reach delay offset disp ============================================================================== *gps-clock3. .GPS. 1 u 715 1024 377 3.52 1.718 2.14 +172.28.42.xx .GPS. 1 u 697 1024 377 44.37 -0.865 1.16 +172.28.34.yy .GPS. 1 u 820 1024 377 70.02 0.865 1.01 time-serv1 #
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.