topic Re: configuring NTP in Operating System - HP-UX

configuring NTP

kunjuttan — Thu, 23 Dec 2010 13:06:36 GMT

Hi all,

I want to setup an NTP server.Please help me doing the same.
My os is HP-UX11.31

Re: configuring NTP

James R. Ferguson — Thu, 23 Dec 2010 14:07:53 GMT

Hi:

See chapter-4 here:

http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c02215026/c02215026.pdf

You should configure at least three (3) time sources for the best, most accurate timekeeping. The NTP "pool" is a wonderful source sink:

http://www.pool.ntp.org/en/

Regards!

...JRF...

Re: configuring NTP

Hakki Aydin Ucar — Thu, 23 Dec 2010 15:51:19 GMT

one word;
xntdp daemon must be Up and Running :
# ps -ef | grep /usr/sbin/xntpd

Re: configuring NTP

Tim Nelson — Thu, 23 Dec 2010 19:02:08 GMT

man xntpd

but for a simplified list

edit /etc/ntp./conf
server

edit /etc/rc.config/netdaemons
export XNTPD=1

/sbin/init.d/xntpd start

Re: configuring NTP

Ismail Azad — Fri, 24 Dec 2010 05:01:04 GMT

Hi,

If you are new to NTP configuration as the pharoah said, it's the simplified list. However, some typo errors:-

edit /etc/ntp.conf
edit /etc/rc.config.d/netdaemons
:)

Regards
Ismail Azad

Re: configuring NTP

Don Mallory — Fri, 24 Dec 2010 14:40:17 GMT

NTP will not serve up time until the time source has been stable for a couple of minutes. So, be patient. You may find that you've configured it, started it, and the clients can't connect (ntpq: lpeers, lassociations, pstatus... all bad..)

The best thing you can do is go get a coffee. By the time you come back, it will likely be working.

Sometimes it's worthwhile to restrict the client / server config..

restrict default ignore
restrict 192.168.1.81 mask 255.255.255.255 nomodify notrap noquery
restrict 192.168.1.84 mask 255.255.255.255 nomodify notrap noquery

This would definitely limit any NTP allowed responses to the ntp servers 192.168.1.81 and .84.

For servers, go the other way and limit connections to only your hosts:

restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

Also, using the NTP pools is a great idea, as it localises your NTP sources, and also doesn't overload the tier 1 sources, but it has the limitation of not working through a firewall unless you are willing to open udp/123 to your clients/NTP server. Better to have a couple of internal sources that you trust and have them go out to a tier 2 or tier 1 source in a firewalled fashion (preferably from your DMZ.. then get the time from the hosts in your DMZ from internal). Routers also do this well...

Best regards,
Don