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_manual_setup(7)					 Miscellaneous Information Manual				       ntp_manual_setup(7)

NAME
ntp_manual_setup - Describes how to manually set up the Network Time Protocol (NTP) DESCRIPTION
Setting up the Network Time Protocol (NTP) manually includes selecting your most accurate time source and then configuring the following: Local NTP servers NTP clients You can also choose to set your system time with the rdate command, which is explained in the Setting Network Time with rdate section in this reference page. Setting Up a Local NTP Server What you must do to configure a local NTP server depends on your time source. If your time source is Internet NTP servers, see the Time Source - Internet NTP Servers section in this reference page. If your time source is a local reference clock, see the Time Source - Local Reference Clock section in this reference page. Time Source - Internet NTP Servers Use the following procedure to set up your local NTP servers if your time source is Internet NTP servers: Select three Internet primary or secondary servers for each local NTP server. Selecting a different set of Internet servers for each local server is recommended. Secondary servers are usually as reliable and accurate as primary servers. See the Network Administration manual for information on obtaining a list of Internet servers. Decide which options to the xntpd daemon you want to run. You can chose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will log only the initialization message and error messages to syslog. Edit the /etc/ntp.conf file. You must add a peer entry to the /etc/ntp.conf file for each Internet server. Each Internet server must either have an entry in the local /etc/hosts file or the hosts file distributed by BIND or NIS. The following /etc/ntp.conf file is for a local NTP server that is synchronizing its time with the fictitious Internet time servers host1, host2, and host3. The version 1 after host3 indicates that host3 is running the ntpd daemon instead of the xntpd daemon. (Servers running Tru64 UNIX run the xntpd daemon.) The line driftfile /etc/ntp.drift indicates the location of the drift file on this system. # # XNTPD Configuration File (template for NTP V3) # # # Specify a filename for the driftfile created by xntpd. # /etc/ntp.drift is the default. # driftfile /etc/ntp.drift # # # # # Specify several NTP servers and/or peers (See the xntpd # documentation for recommendations on selecting servers and peers). # NOTE: Be sure to specify the version number of the server/peer: # # peer host1 version 2 # xntpd V2 # server host2 version 1 # ntpd V1 # server host3 version 3 # xntpd V3 # # For further information on configu- ration options, see the xntpd # documentation. If you have a local accurate clock (radio clock, # etcetera), you will need to spec- ify further configuration options. # #Server and peer configuration peer host1 version 3 peer host2 version 3 peer host3 version 1 Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following series of commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host1 # /usr/sbin/rcmgr set XNTP_SERV2 host2 # /usr/sbin/rcmgr set XNTP_SERV3 host3 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host1, host2, and host3 with the names of the Internet pri- mary or secondary servers that you selected in step 1. Replace options with the options you selected in step 2. You must enclose the options in quotation marks (" "). Start the xntpd daemon with the following command: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command with the -p option: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Time Source - Local Reference Clock Use the following procedure to set up your local NTP servers if your time source is a local reference clock: Choose one of your local NTP servers to be the local reference clock. The other two local NTP servers can be set up as NTP clients that use the local reference clock and each other as peers. For example, if host4, host5, and host6 are the local NTP servers and host4 is the local reference clock, then you should set them up as follows: Set up host5 as an NTP client that specifies host4 and host6 as its local NTP servers Set up host6 as an NTP client that specifies host4 and host5 as its local NTP servers Complete steps 3 through 6 only if you are setting up the local reference clock. Decide which options to the xntpd daemon you want to run. You can choose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will log only the initialization message and error messages to syslog. Edit the /etc/ntp.conf file and add the following entry: # peer 127.127.1.1 This entry allows the local reference clock to run at stratum 3. For more information about local refer- ence clocks, see the ntp.conf(4) reference page. Note that when using a local reference clock, you should never use stratum 1, since the clock may provide very inaccurate time. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following series of commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host4 # /usr/sbin/rcmgr set XNTP_SERV2 host5 # /usr/sbin/rcmgr set XNTP_SERV3 host6 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host4, host5, and host6 with the names of the hosts that you selected to be servers in step 1. Replace options with the options you selected in step 2. You must enclose the options in quota- tion marks (" "). Start the xntpd daemon with the following command: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Setting Up NTP Clients Use the following procedure to set up an NTP client: Decide which options to the xntpd daemon you want to run. You can choose the -g option, the -l option, or both: The -g option allows the xntpd daemon to correct time differences of more than 1000 seconds between your system and that of your system's NTP servers that occur after the xntpd daemon is started. Initial time differences are corrected before the xntpd daemon is started by the ntpdate command which is run at boot time by the /sbin/init.d/settime script. If your system is sensitive to security threats, do not use the -g option. Normally, NTP logs an ini- tialization message, error messages, status messages, and several other informative messages to syslog. The -l option specifies that NTP will only log the initialization message and error messages to syslog. For each client, add a server entry to the /etc/ntp.conf file for each local NTP server. The following /etc/ntp.conf file is for an NTP client that is synchronizing its time with the local NTP servers host4, host5, and host6. The line driftfile /etc/ntp.drift indicates the location of the drift file on this system. # # XNTPD Configuration File (template for NTP V3) # # # Specify a filename for the driftfile created by xntpd. # /etc/ntp.drift is the default. # driftfile /etc/ntp.drift . . . server host4 version 3 server host5 version 3 server host6 version 3 Remember that each local NTP server that you specify must have an entry in either the client's /etc/hosts file or in a BIND or NIS hosts database that is searched by your system. Edit the /etc/rc.config file by using the /usr/sbin/rcmgr command. The syntax for the /usr/sbin/rcmgr command is as follows: /usr/sbin/rcmgr set variable value To edit the /etc/rc.config file and add the required information, enter the following commands: # /usr/sbin/rcmgr set XNTPD_CONF YES # /usr/sbin/rcmgr set XNTP_SERV1 host4 # /usr/sbin/rcmgr set XNTP_SERV2 host5 # /usr/sbin/rcmgr set XNTP_SERV3 host6 # /usr/sbin/rcmgr set XNTPD_OPTS "options" Replace host4, host5, and host6 with the names of three local NTP servers for your network. Replace options with the options you selected in step 1. You must enclose the options in quotation marks (" "). Enter the following command to start the xntpd daemon: # /sbin/init.d/xntpd start Verify that NTP is working by using the ntpq command with the -p option: # /usr/bin/ntpq -p For information on monitoring the xntpd daemon and using the ntpq command, see the ntpq(8) reference page. Setting Network Time with rdate For your system to use the rdate command to set its time to the average network time when it starts, you must add an entry for rdate to the /etc/rc.config file. If your network uses the Network Time Protocol (NTP) time service you might still want to put the rdate entry in the /etc/rc.config file; if NTP hosts are unreachable, the system's time will still be set. If NTP hosts are reachable, the ntpdate command, which runs after the rdate command, will set the time to NTP time before starting the xntpd daemon. You must use the rcmgr command to edit the /etc/rc.config file. Enter the following command to add an entry for the rdate command to the /etc/rc.config file: # /usr/sbin/rcmgr set RDATE_CONF YES RELATED INFORMATION
Commands: ntp(1), timedsetup(8), xntpdc(8).. Daemons: timed(8), xntpd(8). Routines: ctime(3). Files: ntp.conf(4). Introduction: ntp_intro(7). Network Administration delim off ntp_manual_setup(7)
All times are GMT -4. The time now is 06:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy