Unable to configure NTP on HP 1910 / a5500 / 1920 etc

[Dunky]

What do you get from a "dis ntp status", should be....

[SWITCH-00]dis ntp status
Clock status: synchronized
Clock stratum: 4
Reference clock ID: 192.168.100.1
Nominal frequency: 100.0000 Hz
Actual frequency: 100.0000 Hz
Clock precision: 2^18
Clock offset: 29.8469 ms
Root delay: 7.23 ms
Root dispersion: 53.85 ms
Peer dispersion: 0.00 ms
Reference time: 11:01:46.692 UTC Apr 11 2017(DC97361A.B14A3C64)
[SWITCH-00]

If you are synchronizing to an external server, then ensure that you are allowing this out through the firewall.

[n3mmr]

No I get "unsynchronized."

There seems to be something missing, something to tell the ntp client to start.

Following another answer here, I tried "ntp-service enable" but that was rejected by the cli.

[n3mmr]

So, consider my question to be: What do you tell system-view in a _cmdline-mode cli over telnet, in order to make the ntp client to start?

[n3mmr]

in my recent-FW V1910, loggin in over telnet, enabling _cmdline-mode and entering system-view, the command "ntp-service enable" is rejected.

[Dunky]

What reference clock are you trying to get NTP from?

Please share the output of "dis ntp trace" as below...

[SWITCH-00]dis ntp trace
server 127.0.0.1,stratum 4, offset 0.037021, synch distance 0.04550
server 192.168.100.1,stratum 3, offset 0.041750, synch distance 0.00319
server 94.125.132.7,stratum 2, offset 0.029039, synch distance 0.03711
server 195.66.241.2,stratum 1, offset 0.029389, synch distance 0.00037
refid PPS
[SWITCH-00]

Also please share the output from a "dis ntp sess verbose" ...

[SWITCH-00]dis ntp sess verbose
clock source: 192.168.100.1
clock stratum: 3
clock status: configured, master, sane, valid
reference clock ID: 94.125.132.7
local mode: client, local poll: 10
peer mode: server, peer poll: 10
offset: 37.0210 ms,delay: 9.27 ms, disper: 14.84 ms
root delay: 6.39 ms, root disper: 0.00 ms
reach: 255, sync dist: 0.038, sync state: 4
precision: 2^29, version: 3, peer interface: wildcard
reftime: 11:56:10.057 UTC Apr 11 2017(DC9742DA.0EA24FFF)
orgtime: 12:27:11.242 UTC Apr 11 2017(DC974A1F.3E0AC7FF)
rcvtime: 12:27:11.209 UTC Apr 11 2017(DC974A1F.35C0767D)
xmttime: 12:27:11.200 UTC Apr 11 2017(DC974A1F.3360AE96)
filter delay : 0.01 0.00 0.00 0.00 0.00 0.00 0.00 0.00
filter offset: 0.04 0.03 0.04 0.03 0.03 0.03 0.04 0.04
filter disper: 0.00 0.11 0.09 0.08 0.06 0.05 0.03 0.02

Total associations : 1
[SWITCH-00]

[n3mmr]

I found it. It was entirely unrelated to the ntp-service command.

I had somehow lost the wildcard 0.0.0.0 static route, but once I put that back in, ntp started nicely.

Using the two commands you showed.

[Dunky]

Thats great news, glad you got it sorted.

I couldnt figure out why it wasnt working unless for some reason you couldnt see the ip address of the ntp reference clock :)