Sponsored Content
Operating Systems Solaris How to configure NTP in Solaris/Windows/Linux environment...??? Post 302105981 by Tornado on Monday 5th of February 2007 09:04:06 PM
Old 02-05-2007
Why use windows as your networks ntp server ?
Why not setup you Solaris system(smc01) as the ntp server and sync all your servers off it ?

Not sure about Veritas Cluster, But with Sun Cluster, there is ntp.cluster template file you use for ntp and we use ntp.conf.cluster , not ntp.conf

In the ntp.conf.cluster you setup your nodes as peers to sync off each other using the private interconnects and set the ntp server to your time server on your network.

This is what we use on our Sun Cluster:
Code:
server my.ntp.server
#
# One of the "peers" should be "preferred" over the others.
#
peer clusternode1-priv prefer
peer clusternode2-priv

#
# Drift file (optional)
#
driftfile /var/ntp/ntp.drift

#
# Stats (optional)
#
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable

Code:
# ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
*my.ntp.server yarrina.connect  3 u   74 1024  377     1.13   -0.392    1.94
 clusternode1-pr 0.0.0.0         16 -    - 1024    0     0.00    0.000 16000.0
+clusternode2-pr my.ntp.server  4 u  298 1024  376     0.43   -0.270   16.14
#

my.ntp.server is a Stratum 3 server, it syncs its time from our Internet providers Stratum 2 servers. Its ntp.conf looks like this:
Code:
server ntp.mel.connect.com.au
server ntp.syd.connect.com.au

broadcast 224.0.1.1 ttl 4
broadcastdelay  0.5

driftfile /etc/inet/ntp.drift

Code:
# ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
 NTP.MCAST.NET   0.0.0.0         16 -    -   64    0     0.00    0.000 16000.0
*yarrina.connect ntp.sydney.nmi.  2 u   49  128  377     3.02    0.429    0.44
+warrane.connect ntp.melbourne.n  2 u   68  128  377    19.01    0.851    0.66
#

Strata NTP servers are arranged in a hierarchy of levels, called strata. A stratum-1 server is more accurate than a stratum-2 server. There are 15 strata, but only first three are usually used.

Stratum 1 is the highest hierarchical level and those servers are directly attached to highly accurate reference sources such as atomic clocks. This is backbone of NTP and regular servers should not interface with backbone directly, but using NTP servers on lower stratums.

Stratum 2 servers tend to operate out of academic institutions and large corporations. Those can be used by "regular" Internet-connected servers but any sizable organization usually has its own "local" NTP server(s) that interfaces with Stratum 2 servers.

Below Stratum 2 you will find local NTP server that most organizations on the Internet now have. Most organization use free xntp daemon, but some prefer using appliances. Appliances often provide alternative synchronization case of lost internet connectivity using GPS.
Tornado
 

10 More Discussions You Might Find Interesting

1. Linux

How to configure linux to receive snmp traps from a windows server?

Can anybody please tell me how to configure linux to receive snmp traps from a windows server? I am not able to receieve snmp traps on unix machines specifically linux and solaris. I have tried starting snmptrapd service on linux but it didn't work. Is there anything special that I have to do on... (2 Replies)
Discussion started by: iamtulipin
2 Replies

2. UNIX for Dummies Questions & Answers

configuring NTP in Solaris/Windows/Linux environment.

configuring NTP in Solaris/Windows/Linux environment. Can anybody please explain the below table to monitor NTP daemon status This contains many columns like remote,refid,st....various values corresponding to those columns If possible provide me any link to study about... (1 Reply)
Discussion started by: sgand
1 Replies

3. UNIX for Advanced & Expert Users

configuring NTP in Solaris/Windows/Linux environment.

Can anybody please explain the below table to monitor NTP daemon status This contains many columns like remote,refid,st....various values corresponding to those columns If possible provide me any link to study about these quantities clearly. It is very much required for my project please... (3 Replies)
Discussion started by: sgand
3 Replies

4. Solaris

Cannot configure NTP client

Hi, I am trying to configure NTP client on my Solaris server, but I am getting error like: Jan 13 10:53:33 SPOTS ntpdate: no server suitable for synchronization foundMy ntp.conf file: bash-3.00# pwd /etc/inet bash-3.00# bash-3.00# bash-3.00# cat ntp.conf # ident "@(#)ntp.client... (5 Replies)
Discussion started by: nypreH
5 Replies

5. AIX

Configure one host against two ntp servers for redundancy

Dears all is it possible to have two NTP servers in one host ? how i can configure them . please advice (5 Replies)
Discussion started by: thecobra151
5 Replies

6. UNIX for Dummies Questions & Answers

Samba setup in virtual server environment Windows/ Linux

I have a home network set up that consists of a few windows clients and 3 centos, and 1 suse client. These are all virtual machines, VMware Workstation. One centos vm is set to be the Samba server. Do I need Samba set up on the other Linux clients?I have no problem seeing the windows clients... (0 Replies)
Discussion started by: ktb231
0 Replies

7. HP-UX

Setting up NTP HP-UX clients from solaris NTP server

Hi I wonder if its possible to setup NTP clients running HP-UX o.s. from a solaris 10 NTP server? FR (3 Replies)
Discussion started by: fretagi
3 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. Linux

Configure ntp server and Linux in oel 5.9

i want to configure machine1 as ntp server. this machine has oel 5.9 64 bit installed and this machine is not connected to internet neither there is any ntp server. there is another machine2 and i want to configure that as ntp client. plz do tell me that what lines do i add in /etc/ntp.conf... (0 Replies)
Discussion started by: rehantayyab82
0 Replies

10. Ubuntu

Install and configure ntp rpm on Ubuntu 13.10 version

Hello, I am new to ubuntu Server OS and so trying to setup and ntp service on couple of servers. I see ntp rpm is not installed. # dpkg --get-selections | grep -v deinstall | grep ntp ntpdate install # so I tried to installed ntp rpm using... (5 Replies)
Discussion started by: bobby320
5 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 06:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy