Cannot set HP-UX Server as time sync Server

[Ian Dennison_1]

Am trying to get an HP-UX 11.11 Server set up as the NTP Server while our time server appliance gets a new satellite dish.

Have followed instructions from various postings here and the server refuses to recognise itself as a time source.

Does anyone know of any bugs in NTP at this level? Here is the "ntpdate" command (Server bc02n0v0 is IP Address 53.202.170.94) and the tail of the /etc/ntp.conf file.

bc02n0v0> ntpdate -d bc02n0v0
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
server 53.202.170.94, port 123
stratum 16, precision -16, leap 11, trust 000
refid [0.0.0.0], delay 0.02571, dispersion 0.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 6:28:16.000
originate timestamp: c94df8e9.1006c000 Tue, Jan 9 2007 11:20:09.062
transmit timestamp: c94df8e9.10015000 Tue, Jan 9 2007 11:20:09.062
filter delay: 0.02591 0.02573 0.02571 0.02571
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000062 0.000006 0.000003 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.02571, dispersion 0.00000
offset 0.000003

9 Jan 11:20:09 ntpdate[4346]: no server suitable for synchronization found

/etc/ntp.conf
==============
server bc02n0v0.dcsit.net version 3 prefer
broadcast 53.202.69.191 version 3
broadcastclient yes
broadcast 53.202.145.255 version 3
bc02n0v0>

[Peter Godron]

Hi,
your reference time seems to be way off.
What does "ntpdate -bd bc02n0v0" report ?

[Wouter Jagers · Accepted solution]

Synchronizing with yourself ? That requires a small config change.

From http://docs.hp.com/en/B2355-90774/ch04s02.html :

Local Synchronization Clock (pseudo clock)

A system with this type of clock uses the local system clock as a time source. The address used to configure this clock is 127.127.1.u, where u is a value between 0 and 15 and specifies the stratum level at which the clock runs. When you synchronize the local host to this clock, the local host operates at one stratum level higher than the local clock. You can use this type of clock in an isolated synchronization subnet, which does not have access to a stratum-1 time server.

Cheers
Wout

[Ian Dennison_1]

Peter,

Here is the results of the command. I have added 127.127.1.1 to the ntp.conf file which has made no difference.

Share and Enjoy! Ian

bc02n0v0> ntpdate -bd bc02n0v0.dcsit.net
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
receive(53.202.170.94)
transmit(53.202.170.94)
server 53.202.170.94, port 123
stratum 16, precision -17, leap 11, trust 000
refid [0.0.0.0], delay 0.02568, dispersion 0.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 6:28:16.000
originate timestamp: c94e0408.b6e37000 Tue, Jan 9 2007 12:07:36.714
transmit timestamp: c94e0408.b6de5000 Tue, Jan 9 2007 12:07:36.714
filter delay: 0.02591 0.02570 0.02568 0.02568
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000063 0.000005 0.000002 0.000002
0.000000 0.000000 0.000000 0.000000
delay 0.02568, dispersion 0.00000
offset 0.000002

9 Jan 12:07:36 ntpdate[10736]: no server suitable for synchronization found
bc02n0v0>

[Wouter Jagers]

I suppose you also restarted xntpd :-)

I remember 'ntpq -p' to be a useful command as well, showing info about the server's peers. I'd say that one's output as well..

[Wouter Jagers]

I suppose you also restarted xntpd :-)

I remember 'ntpq -p' to be a useful command as well, showing info about the server's peers. I'd say check that one's output as well..

[Ian Dennison_1]

Yep, restarted xntpd

bc02n0v0> ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 3 l 5 64 377 0.00 0.000 10.01
53.202.69.191 0.0.0.0 16 - - 64 0 0.00 0.000 16000.0
53.202.145.255 0.0.0.0 16 - - 64 0 0.00 0.000 16000.0
bc02n0v0>

[Ian Dennison_1]

For some reason, the SAN Switches I am trying to synchronise against this server are now picking up the synch. I think the principle of "it works, so I won't mess with it" applies here.

Thanks to all for their assistance. Share and Enjoy! Ian

[Wouter Jagers]

I remember that waiting a few minutes after restarting xntpd is a good idea, it might be just that.

Glad to see it's working !
Sorry about the double post (HP, upgrade these boxes ;-)), and thanks for helping me get my very first hat !

Cheers

[Ian Dennison_1]

Issue closed, thanks all and congrats to Wouter on his first hat.

Share and Enjoy! Ian