Sponsored Content
Operating Systems HP-UX Setting up NTP HP-UX clients from solaris NTP server Post 302625057 by vbe on Tuesday 17th of April 2012 08:20:27 AM
Old 04-17-2012
I cant guarantee but I see no reason why it should not work for NTP is a protocol...
I pick up my time from one of our main cisco routers: I asked the network guru since I knew which router I wanted the time from ( the one he uses to synchronyse all the swiches...) he finally mounted a domain NTP server ( with 4 "servers" responding...).
That is why in my example you had ntp.my-domain as preferred.. the others being unix servers which had strange behaviour from time to time...

Just give it a try, dont make things more complicated than needed! my example is all I put in ntp.conf and since I have no issues (years now...)
 

10 More Discussions You Might Find Interesting

1. Solaris

ntp server and ntp client

All, How do you set a Solaris 9 server which received ntp updates from a ntp server to broadcast them on a local subnet. I have created a /etc/inet/ntp.conf file to receive the updates from a server on network and need to make this server become like a ntp relay from the main server. Any... (1 Reply)
Discussion started by: bubba112557
1 Replies

2. AIX

Setting up NTP

Hi all I am lookig for the procedure to setup a NTP server and clients. I would like to setup a machine in my DMZ that would be a client to a external time server and all my internal systems to be clients of the machine in the DMZ. I am on AIX 5.2 and the machine that will be in the DMZ will... (2 Replies)
Discussion started by: jhansrod
2 Replies

3. HP-UX

Setting NTP for HPUX

guys have a question for HPUX really new with HPUX can you teach me how to configure NTP on HPUX here are the parameters and please give comments every commands. NTP server 10.1.1.5 (Stratum 1 server) Update interval 24hrs (please indicate the computation for 24hrs) Timezone... (1 Reply)
Discussion started by: allanigue03
1 Replies

4. AIX

NTP server with aix & wintel clients

Good morning to all, can someone advise me how to setup aix ntp server with aix & wintel clients? Secondly, I also require to enable the service to autostart on reboot, how do I configure this? Thirdly, how do I configure daily autosync between clients and server? Please advice, thanks.... (0 Replies)
Discussion started by: chongkls77
0 Replies

5. UNIX for Advanced & Expert Users

Tracking NTP Clients

I need to find out the NTP Clients which are syncing with my NTP Server in a Unix(Linux/Solaris) Machine. For eg. How many Stratum 2 Servers sync the time with my Stratum1 Server. Is there any way to track it? edit by bakunin: moving the thread to where it belongs: the technical forums. (4 Replies)
Discussion started by: hottyspidy
4 Replies

6. Linux

How often does Linux NTP server update its time with the external NTP server?

All here, thank you for listening. Now I've set up a Linux NTP server by adding a external windows NTP server in /etc/ntp.conf. Then I start the ntpd daemon. But how often does the Linux NTP server update its time with the external NTP server? I've looked up everywhere but found no information... (1 Reply)
Discussion started by: MichaelLi
1 Replies

7. Fedora

NTP Clients not sync

hi guys I have several Red Hat 5.7(7) all of them sync time with two NTP Servers based on Windows but the issue is I configure the NTP service, I start the ntp service and use ntpdate -u to set the time the first time This is what I do 1. Configure /etc/ntp.conf restrict default kod... (2 Replies)
Discussion started by: karlochacon
2 Replies

8. UNIX for Advanced & Expert Users

NTP server name and ip details on Linux/Solaris

Hi All, Where can I find all the NTP server names/ip addresses on Linux/Solaris systems. How can I grep these names/IP address from specific files from a specific OS (Linux/Solaris). I know on linux /etc/ntp.conf and /etc/ntp/ntp.conf on solaris contains these details. Whether I am right about... (4 Replies)
Discussion started by: sanzee007
4 Replies

9. Red Hat

Ntp client sync with local over ntp server

Hi, I have two ntp servers in my cluster and I want all the nodes in my cluster to sync with either of the ntp servers or just one. Unfortunately it keep rotating the sync, between my ntp server 1, ntp server 2 and local. Is there anyway I can change the sync to avoid local? # ntpq -p ... (3 Replies)
Discussion started by: pjeedu2247
3 Replies

10. Solaris

"synchronisation lost" errors for Solaris NTP server

Hi, This is Solaris 9, which is service as NTP server for many unix clients. At backend, it it synching time with three GPS clocks. From past few days, I am noticing time reset to 1 second. Is this a problem ? I was assuming that if it is a network issue or GPS clock connectivity issue, it... (14 Replies)
Discussion started by: solaris_1977
14 Replies
ntp(1)							      General Commands Manual							    ntp(1)

NAME
ntp - query a clock running a Network Time Protocol daemon, either ntpd or xntpd SYNOPSIS
/usr/bin/ntp [-v] [-s] [-f] host1 | IPaddress1 ... OPTIONS
Specifies verbose output. The output shows the full contents of the received NTP packets, plus the calculated offset and delay. Sets local clock to remote time. This only happens if the offset between the local and remote time is less than 1000 seconds. The local clock is not reset if the remote host is unsynchronized. If you specify more than one host name on the command line, ntp queries each host in order, waiting for each host to answer or time- out before querying the next host. The local clock is set to the time of the first remote host that responds. Forces setting local clock regardless of offset. The -f option must be used with -s option. The local clock is not reset if the remote host is unsyn- chronized. DESCRIPTION
The ntp command may be retired in a future release; use the ntpdate(8) command instead. The ntp command is used to determine the offset between the local clock and a remote clock. It can also be used to set the local host's time to a remote host's time. The ntp command sends an NTP packet to the NTP daemon running on each of the remote hosts specified on the command line. The remote hosts must be running either the ntpd daemon or xntpd daemon. When the NTP daemon on the remote host receives the NTP packet, it fills in the fields (as specified in RFC 1129), and sends the packet back. The ntp command then formats and prints the results on the standard output. Note You can specify hosts by either host name or Internet address. The hosts that you specify must either exist in the /etc/hosts file, or in the master hosts database, if the database is being served to your system by BIND or Network Information Service (NIS). The default output shows the roundtrip delay of the NTP packet in seconds, the estimated offset between the local time and remote time in seconds, and the date in ctime format. See the ctime(3) reference page for more information. The -s and -f options can be used to reset the time of the local clock. RESTRICTIONS
Using the -s and -f options require that you be logged on as superuser. ERRORS
The following error messages can be returned by NTP: May indicate that the NTP daemon is not running on the remote host. The NTP command cannot resolve the specified host name in the /etc/hosts file. Check that the host exists in the /etc/hosts file, or that it exists in the master hosts database, if the database is being served to your system by BIND or NIS. EXAMPLES
In the following examples, some output text lines may be broken. The line end are marked with the backslash symbol () and the following line is indented. Such text may appear as a single line on your terminal. The following is the default output to an ntp query about a remote host with an internet address of 555.5.55.5: # /usr/bin/ntp 555.5.55.5 555.5.55.5: delay:1.845207 offset:-0.358460 Mon Aug 20 08:05:44 1991 The following is the verbose output to an ntp query about the same remote host: # /usr/bin/ntp -v 555.5.55.5 Packet from: [555.5.55.5] Leap 0, version 1, mode Server, poll 6, precision -10 stratum 1 (WWVB) Synch Distance is 0000.1999 0.099991 Synch Dispersion is 0000.0000 0.000000 Reference Timestamp is a7bea6c3.88b40000 Tue Aug 20 14:06:43 1991 Originate Timestamp is a7bea6d7.d7e6e652 Tue Aug 20 14:07:03 1991 Receive Timestamp is a7bea6d7.cf1a0000 Tue Aug 20 14:07:03 1991 Transmit Timestamp is a7bea6d8.0ccc0000 Tue Aug 20 14:07:04 1991 Input Timestamp is a7bea6d8.1a77e5ea Tue Aug 20 14:07:04 1991 555.5.55.5: delay:0.019028 offset:-0.043890 Tue Aug 20 14:07:04 1991 The fields are interpreted as follows: The address of the remote host from which this NTP packet was received. The leap second indicator. Non-zero if there is to be a leap second inserted in the NTP timescale. The bits are set before 23:59 on the day of insertion and reset after 00:00 on the following day. The NTP protocol version. The NTP mode can be Server, Client, Symmetric Pas- sive, Symmetric Active, or Broadcast. See RFC 1129 for more information on NTP modes. The desired poll rate of the peer in seconds as a power of 2. For example, if poll is equal to 6, that means that the poll rate is one message exchanged every 2**6 seconds. The precision of the remote host's clock in seconds as a power of 2. For example, if precision is equal to -10, that means that the pre- cision is 2**-10. The NTP daemon sets this automatically. The stratum of the clock in the NTP hierarchy, along with the source of the clock. The source is either the name of a reference standard (such as WWVB or GOES), or the Internet address of the clock that this clock references. The values reported are used internally by the NTP daemon. The values reported are used internally by the NTP daemon. The next five timestamps are given as NTP fixed-point values, in both hexadecimal and ctime. The timestamps are set either by this NTP process, or by the remote host you are querying. These timestamps are used by the local host to calculate delay and offset for this query. This specifies the last time the remote host clock was adjusted. (remote time) This specifies when the NTP request was transmitted by the local host to the remote host. (local time) This specifies when the NTP request was received at the remote host. (remote time) This specifies when the NTP response was transmitted by the remote host. (remote time) This specifies when the NTP response was received by the local host. (local time) This field summarizes the results of the query, giving the host name or inter- net address of the responding clock specified in the command line, the round-trip delay in seconds, and the offset between the two clocks in seconds (assuming symmetric round-trip times). SEE ALSO
ctime(3), ntp.conf(4), ntpdate(8), xntpd(8), xntpdc(8), ntpq(8) Internet time synchronization: The Network Time Protocol (RFC 1129) Network Administration ntp(1)
All times are GMT -4. The time now is 11:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy