topic Re: Network Time Clock Issue in Operating System - HP-UX

Network Time Clock Issue

Laurie A. Krumrey — Tue, 15 Jan 2002 16:13:00 GMT

HI All,

My Host HP Server SPOT goes to ORION to get the
time. And then all my other boxes go to
SPOT.

Well all my servers are off by 5 minutes (not
good) and ORION has the correct time and
SPOT does not:

/etc/ntp.conf at the end of this file I have:

server 123.127.1.1
fudge 123.127.1.1 stratum
server 173.28.10.70 prefer (ORION)

When I do a #ntpq -p on SPOT I get this:

remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 10 l 11 64 377 0.00 0.000 10.01
orion.iftc.net 0.0.0.0 16 - - 1024 0 0.00 0.000 16

I think it goes to the LOCAL clock on SPOT
first ??? How do I set up my ntp. conf
file to always to to ORION first and then
SPOT local clock if ORION is down?

Actually if ORION is down all my servers
could just use their local clock. ORION
hardly ever goes down and it's hooked up
to an ATOMIC clock.

Laurie

Re: Network Time Clock Issue

Justo Exposito — Tue, 15 Jan 2002 16:19:33 GMT

Hi,

You must put something like this:
server ntp_serv1 version 3 prefer
authenticate no
server ntp_serv2 version 3
peer hp2 version 3
peer hp3 version 3
peer hp4 version 3

Regards,

Justo.

Re: Network Time Clock Issue

Darrell Allen — Tue, 15 Jan 2002 16:39:16 GMT

Hi Laurie,

It looks like ntp on SPOT can't communicate with the ntp server on ORION. Notice 16 is the stratum listed for orion.iftc.net (3rd field). Stratum 16 basically means you are communicating. Is there a firewall blocking ntp? Does nslookup orion.iftc.net return the correct IP address?

For what it's worth, my ntp.conf looks like:
server cs_ntp version 3 prefer
server boston_ntp version 3
broadcastclient no
driftfile /etc/ntp.drift

Darrell

Re: Network Time Clock Issue

Bill Hassell — Tue, 15 Jan 2002 20:32:22 GMT

To add to the test for ORION:

ntpq -p orion

and it should reply with the time sources used inside the orion box. If it does not respond, orion is not functioning as an NTP server or is not reachable. Reachable is defined as the ntp port is allowed to propagate through the network to your node, that the IP address associated with orion is correctly interpreted on your local node and that orion can be at least ping'ed from your local node.

Re: Network Time Clock Issue

Darrell Allen — Tue, 15 Jan 2002 20:35:26 GMT

Oops! BIG typo in my reply. Should be:

Stratum 16 basically means you are NOT communicating.

Sorry for the typo.

Darrell