Unable to query NTP server "x" with address x.x.x.x within 5 seconds

Applies to

Issue

• When adding an NTP server:

Cluster::*> cluster time-service ntp server create time.mydomain.com

Error: command failed: Unable to query NTP server "time.mydomain.com" with address 10.1.25.1 within 5 seconds.

• NTP server is pingable from all mgmt lifs:

Cluster::*> net int show -role *mgmt*

  (network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
Cluster
            cluster_mgmt up/up    10.1.81.90/24      node01 e0M  true
            node01_mgmt up/up 10.1.81.91/24 node01 e0M true
            node02_mgmt up/up 10.1.81.92/24 node02 e0M true
3 entries were displayed.

• Example ping using the cluster mgmt lif:

Cluster::*> network ping -vserver Cluster -lif cluster_mgmt -destination 10.1.25.1
10.1.25.1 is alive

• Multiple default routes in Admin vserver with the same metric:

Cluster::*> network route show -vserver Cluster

Vserver             Destination     Gateway         Metric
------------------- --------------- --------------- ------
Cluster
                    0.0.0.0/0       10.1.81.254     20
                    0.0.0.0/0       172.22.2.254    20
2 entries were displayed.

• From systemshell can see correct gateway is used:

Cluster::*> systemshell -node node01 -c sudo route get 10.1.25.1
  (system node systemshell)
   route to: ntp_server1.x.x

destination: default

       mask: default

    gateway: 10.1.81.254

        fib: 0

  interface: e0M

        ifa: node01.mgmt.x.x

      flags: <UP,GATEWAY,DONE,STATIC>

 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire

       0         0         0         0      1500        65         0

 

• Node can reach the NTP server, with the 'ntpdate' command from the systemshell:

::*> systemshell -node node01 -c ntpdate -d -q 10.1.25.1
  (system node systemshell)
26 Oct 20:20:48 ntpdate[24829]: ntpdate 4.2.8p14@1.3728-o Wed Jun 10 12:28:59 UTC 2020 (1)

Looking for host 10.1.25.1 and service ntp

10.1.25.1 reversed to ntp_server1.x.x

host found : ntp_server1.x.x

transmit(10.1.25.1)

receive(10.1.25.1)

transmit(10.1.25.1)

receive(10.1.25.1)

transmit(10.1.25.1)

receive(10.1.25.1)

transmit(10.1.25.1)

receive(10.1.25.1)

server 10.1.25.1, port 123

stratum 2, precision -25, leap 00, trust 000

refid [152.45.7.44], root delay 0.001450, root dispersion 0.000870

reference time:      e704136a.1d1c1bd9  Wed, Oct 26 2022 20:13:30.113

originate timestamp: e7041526.c80d59dd  Wed, Oct 26 2022 20:20:54.781

transmit timestamp:  e7041526.771ffef0  Wed, Oct 26 2022 20:20:54.465

filter delay:  0.02617    0.02612    0.02609    0.02605   

               ----       ----       ----       ----      

filter offset: +0.315928  +0.315880  +0.315877  +0.315872 

               ----       ----       ----       ----      

delay 0.02605, dispersion 0.00000, offset +0.315872

26 Oct 20:20:54 ntpdate[24829]: adjust time server 10.1.25.1 offset +0.315872 sec

 

• And 'ntpq' command shows the nodes syncing with Cluster lifs.

Cluster::*> systemshell -node node02 -c sudo ntpq -pn
  (system node systemshell)
     remote           refid      st t when poll reach   delay   offset  jitter

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

*169.254.55.71   127.0.0.1       12 u  619 1024  377    0.097   -0.035   0.079

Cluster::*> systemshell -node node01 -c sudo ntpq -pn
  (system node systemshell)
     remote           refid      st t when poll reach   delay   offset  jitter

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

*169.254.55.71   127.0.0.1       12 u  628 1024  377    0.097   -0.035   0.079