Forum Discussion

luoye's avatar
luoye
Icon for Nimbostratus rankNimbostratus
Jun 07, 2017

NTP failed

Hi,all:

I have a ntp server 10.24.20.20 and 10.21.45.45 which work normal。But F5 can't communicate with them correctly. I find an abnormal command output as the following：

ntpq> as
ind assID status conf reach auth condition last_event cnt

1 32732 8000 yes yes none reject 2 32733 8000 yes yes none reject ntpq> rv 32732 assID=32732 status=8000 unreach, conf, no events, srcadr=10.21.45.45, srcport=123, dstadr=127.1.1.1, dstport=123, leap=11,

ntpq> rv 32733 assID=32733 status=8000 unreach, conf, no events, srcadr=10.24.20.20, srcport=123, dstadr=127.1.1.1, dstport=123, leap=11,

In the command line，dstadr should be F5' self-ip。

And in the packet,I see F5 uses tmm0 to request while tmm4 to accept the response

application delivery
BIG-IP

4 Replies

Sort By
  • Samir_Jha_52506's avatar
    Samir_Jha_52506
    Icon for Noctilucent rankNoctilucent
    Jun 09, 2017

    Was it working earlier or it is new setup? Are you able trace NTP server from F5 device. Type the following command to check status.

        $ ntpstat   --> Status of NTP server
    $ ntpq -pn  --> ntpd operations and determine performance

    OR

        $ ntpq -p

    paste the output.

    • luoye's avatar
      luoye
      Icon for Nimbostratus rankNimbostratus
      Jun 13, 2017
      remote refid st t when poll reach delay offset jitter

      10.21.45.45 .INIT. 16 u - 64 0 0.000 0.000 0.000 10.24.20.20 .INIT. 16 u - 64 0 0.000 0.000 0.000 [root@SHDC-PR1-LTM5200-03:Standby:Changes Pending] config [root@SHDC-PR1-LTM5200-03:Standby:Changes Pending] config ntpq -p

       

      remote refid st t when poll reach delay offset jitter

      10.21.45.45 .INIT. 16 u - 64 0 0.000 0.000 0.000 10.24.20.20 .INIT. 16 u - 64 0 0.000 0.000 0.000

       

  • dragonflymr's avatar
    dragonflymr
    Icon for Cirrostratus rankCirrostratus
    Jun 09, 2017

    Hi,

    That relates only to older version of VE. I noticed that rather often after reboot of device ntp was failing.

    ntpq -np
    showed that no set server was actually used.

    Easy fix was to just restart ntpd, like 

    tmsh restart sys service ntpd
    - after that ntp was back to normal.

    Piotr