Forum Discussion
NimbostratusNTP 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
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
luoyehelp help
Samir_Jha_52506Noctilucent
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 performanceOR
$ ntpq -ppaste the output.
- luoyeremote 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 jitter10.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
dragonflymrCirrostratus
Hi,
That relates only to older version of VE. I noticed that rather often after reboot of device ntp was failing.
showed that no set server was actually used.ntpq -npEasy fix was to just restart ntpd, like
- after that ntp was back to normal.tmsh restart sys service ntpdPiotr