ntpd does not update?

A Former User

Hi all,

I have configured ntpd to stay sync in time (for CARP).

Both nodes have same DNS-servers configured and both nodes have samt ntp-servers configured:
0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org

The first one properly syncs time:

[2.4.3-RELEASE][root@rtr1.dd.de]/root: ntpq -c pe
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
+clients3.arcani 131.188.3.223    2 u    1  128  377   17.259    0.040   0.337
-25000-014.cloud 124.216.164.14   2 u   15  128  377   32.661   -1.227   0.358
-panel1.web2.clu 131.188.3.220    2 u   49  256  377   19.878    0.613   3.553
*time2.uni-konst .GPS.            1 u   52  128  377   23.037    0.197   0.130
+mx.pingless.com 5.1.80.246       3 u   34  128  377   16.901   -0.370   0.146
-atto.mcl.gg     131.188.3.222    2 u   69  128  377   19.804   -1.327   0.329

while the second does not - no change after 30minutes!

[2.4.3-RELEASE][root@rtr2.dd.de]/root: ntpq -c pe
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 0.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 1.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 2.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000
 3.de.pool.ntp.o .POOL.          16 p    -   64    0    0.000    0.000   0.000

When checking the ntpd.log on the second I see:

Jun 26 17:39:13 rtr2 ntpd[86104]: ntpd 4.2.8p11@1.3728-o Fri Mar 16 17:03:00 UTC 2018 (1): Starting
Jun 26 17:39:13 rtr2 ntpd[86104]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Jun 26 17:39:13 rtr2 ntpd[86386]: proto: precision = 0.402 usec (-21)
Jun 26 17:39:13 rtr2 ntpd[86386]: Listen normally on 0 em1 [fe80::21a:8cff:fe13:7e3a%2]:123
Jun 26 17:39:13 rtr2 ntpd[86386]: Listen normally on 1 em1 192.168.2.202:123
Jun 26 17:39:13 rtr2 ntpd[86386]: Listen normally on 2 em1 192.168.2.254:123
Jun 26 17:39:13 rtr2 ntpd[86386]: Listening on routing socket on fd #37 for interface updates
Jun 26 17:39:14 rtr2 ntpd[86386]: Soliciting pool server 129.70.132.35
Jun 26 17:39:15 rtr2 ntpd[86386]: Soliciting pool server 31.172.86.162
Jun 26 17:39:16 rtr2 ntpd[86386]: Soliciting pool server 82.165.77.22
Jun 26 17:39:17 rtr2 ntpd[86386]: Soliciting pool server 129.250.35.251
Jun 26 17:40:19 rtr2 ntpd[86386]: Soliciting pool server 51.254.155.97
Jun 26 17:40:19 rtr2 ntpd[86386]: Soliciting pool server 89.163.241.149

Doing a packet trace on both I see outgoing packets on RED interface with the same source IP!

So it appears the ntp-packets are going out with the virtual CARP-IP instead of the interface IP.

Any clue hos to solve?

A Former User

Well, not a solution but some digging showed it is ntpd sending out requests with the virtual CARP IP of the interface even when it is in backup mode and should not use this IP.

Solved here, posted in CARP forum to get a solution.

A Former User

@knebb
Final solution:
Outbound-NAT was misconfigured to always map to the VirtualIP even in backup mode.

Switched to automated outbound NAT and now working fine.