cancel
Showing results for 
Search instead for 
Did you mean: 

ntp

 
A.G.M. Velthof
Valued Contributor

ntp

Hello to all,

 

I want to do the following:

 

We have a closed network with no internet connection.

On 1 HPUX server 11.31 I want to configure ntp to act as ntpserver, using his local time.

 

The other server will have to point to this server to retrieve the time.

 

The ntp.conf of my timeserver is:

server 127.127.1.0

fudge  127.127.1.1 stratum 10

driftfile /etc/ntp.drift

 

I did a xntpd stop and start

 

On another server (redhat) I added my timeserver to the list NTP servers, but get the error:

"host not reachable or not configured as timeserver."

 

What am I doing wrong?

 

Best regards,  Alfons Velthof

 

3 REPLIES 3
Ken Grabowski
Respected Contributor

Re: ntp

Your server address ending in a zero would normally represent a network and not a host server. Is that the actual IP address assigned to the HP-UX host acting as an NTP server?

Patrick Wallek
Honored Contributor

Re: ntp

The 'server 127.127.1.0' line tells NTP to use the local clock as its time source.

 

When you are setting up your NTP client, I assume you are using the real IP address of your NTP server.

 

Can you ping the IP address of the NTP server?  Is there any firewall between your NTP client and server that may be blocking access to UDP port 123?

 

 

Matti_Kurkela
Honored Contributor

Re: ntp

The IP address on the "fudge" line should match the IP address on the "server" line.

 

The purpose of the "fudge" line here is to adjust the stratum value of the local clock driver. The local clock is NTP driver #1, instance #0, hence the "IP address" 127.127.1.0. Since you aren't using driver #1, instance #1 (127.127.1.1) for anything in your configuration, adjusting its stratum value would make no sense at all.

 

After starting xntpd, wait a few minutes. One xntpd default polling cycle takes a bit more than a minute, and xntpd will always monitor any clock source for several cycles before synchronizing to it. This is true even when you're using the local clock driver: xntpd does not treat it any different from an actual time server, although it obviously is always in perfect agreement with the system clock. Once the synchronization is complete, the "ntpq -p" output should include an asterisk (*) in the first column of the listing, to indicate the timesource xntpd has synchronized to.

 

Xntpd will start providing time information to clients only after the synchronization is complete.

MK