1848731 Members
2295 Online
104036 Solutions
New Discussion

Re: XNTPD

 
Junior C.
Frequent Advisor

XNTPD

All,

What option/script, etc to used with xntpd not to accept time from NT time server if time is greater than 60 min on HP server.

Thanks in advance.

Junior
6 REPLIES 6
James R. Ferguson
Acclaimed Contributor

Re: XNTPD

Hi:

The 'xntpd' daemon will reject incoming time packets if the difference in the server's time and its source is 1000 seconds or greater.

If, after about 320 seconds, no suitable time source can be found, the daemon will simply die.

I don't think either setting is configurable.

Regards!

...JRF...
Sanjay_6
Honored Contributor

Re: XNTPD

Hi Junior,

The xntpd will not sync the time if the ntp server and client time difference is nore than 1000 seconds

60 minutes = 60 * 60sec = 3600 seconds

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90685/B2355-90685_top.html&con=/hpux/onlinedocs/B2355-90685/00/00/66-con.html&toc=/hpux/onlinedocs/B2355-90685/00/00/66-toc.html&searchterms=ntp&queryid=20020109-085638

Look at the section "Time Difference Greater than 1000 seconds"

Hope this helps.

Regds
Junior C.
Frequent Advisor

Re: XNTPD

James/Sanjay

I had this problem over the weekend. HP server did accept
wrong time from NT server.

1) NT server date/time was
Aug, 17 2021

2) HP server accetp above time

3) All other HP/SUN servers gets time from above HP(2) server.

You can see the domino effect.

Bill Hassell
Honored Contributor

Re: XNTPD

If you configure the netdaemons script in /etc/rc.config.d to start NTP services with a source:

export XNTPD=1
export NTPDATE_SERVER=ntp-cup.external.hp.com

then rebooting your HP-UX system will instantly sync it with the NTP server. If the box is that far out of sync, you don't want to make a single change all at one time, which is why a reboot is the best.

Make sure that the time you are seeing on HP-UX is really off by an hour by doing this:

echo $TZ
date

If the $TZ value matches your timezone and the date is an hour out of sync, then you can should reboot.

Also, verify that the NT box is actually working as an NTP server with:

ntpq -p nt_box.domain.com

It should respond with the time sources used by the NT box.


Bill Hassell, sysadmin
Steve Labar
Valued Contributor

Re: XNTPD

the only way to sync an ntp client to an ntp server if the time divergence is to great is to do an ntpdate -b before starting xntpd. You could create your own startup script to run before running xntpd or run ntpdate manually then xntpd manually.

Good Luck.
Steve
Sanjay_6
Honored Contributor

Re: XNTPD

Hi Junior,

Seems like the problem was on the NT side. We has a similar problem, but was identified as a hardware problem on the NTP server side. My idea is that if the change is abrupt the clients would not have updated the new time, but if the change is gradual, it might have sync'ed the clients too. What does your syslog on hp side say around the time when this transition took place.

Hope this helps.

Regds