#
# File name:      TCPIP$NTP.CONF
# Product:        HP TCP/IP Services for OpenVMS
# Version:        V5.7-13
#
# © Copyright 1976, 2009 Hewlett-Packard Development Company, L.P.
#
 
#
# NTP server configuration file
#

#
# DESCRIPTION:
#
#    This file contains configuration information  for  the  NTP  server.
#    Before  starting the NTP server, you must edit this  file  and  copy
#    it to SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP.CONF.
#
#    Refer  to  the HP TCP/IP Services for OpenVMS Management  guide  for
#    instructions on editing and using this file.
#
#
# CONFIGURATION INSTRUCTIONS:
#
#    The Network Time Protocol  (NTP)  provides synchronized  timekeeping
#    among  a  set  of  distributed time servers and clients.   The local
#    OpenVMS  host  maintains an NTP configuration file,  TCPIP$NTP.CONF,
#    of participating peers.  The NTP configuration  file  is  maintained
#    in the SYS$SPECIFIC:[TCPIP$NTP] directory.
# 
#    Determine the peer hosts with which the local hosts should negotiate
#    and  synchronize.  Include at least one (but preferably three) hosts
#    that you are certain have the following characteristics:
# 
#      1. provide accurate time
#      2. synchronize to Internet Time Servers
#	  (if they are not themselves Internet Time Servers)
# 
#    The NTP configuration file is not dynamic,  and  therefore  requires
#    restarting NTP after being edited to make the changes  take  effect.
#    However, you can make runtime configuration  requests  interactively
#    using the NTPDC utility.
# 
# 
# CONFIGURATION:
# 
#    Your NTP configuration file  should  always  include  the  following
#    driftfile entry.  The driftfile is the name of the file that  stores
#    the clock drift (also known as frequency error) of the system clock.
 
driftfile SYS$SPECIFIC:[TCPIP$NTP]TCPIP$NTP.DRIFT
 
#    Samples entries follow below.  Replace them with your  own  list  of
#    hosts and identify the appropriate association mode.  If you specify
#    multiple hosts, NTP  can  choose  the  best  source  with  which  to
#    synchronize.  This also provides redundancy in case one of the hosts
#    becomes unavailable.
# 
#    Client/Server Mode
#
#    Client/Server mode indicates that the local  host  wants  to  obtain
#    time  from  the  remote server and is willing to supply time to  the
#    remote server.  Indicate Client/Server mode with a  peer  statement.
#    Identify each peer with a fully-qualified DNS host name  or  with an
#    IP address in dotted-decimal notation.
 
peer 10.1.2.3
peer ntp0.myorg.mycorp.com
peer ntp1.myorg.mycorp.com

#    Client Mode
#
#    Client mode indicates that the local host wants to obtain time  from
#    the  remote server but it is not willing  to  provide  time  to  the
#    remote server.  Indicate client  mode  with  the  server  statement.
#    Identify each server with a fully-qualified DNS host name or with an
#    IP address in dotted-decimal notation.

server 10.2.3.4
server 10.3.4.5
server ntp3.myorg.mycorp.com

#    The following commands allow interoperation of NTP with another time
#    service such as DTSS.  If enabled (by removing #), NTP will not  set
#    the system clock.
 
# server 127.127.1.0 prefer
# fudge 127.127.1.0 stratum 0
 
#    The following commands allow this node to act as a backup NTP server
#    (or as the sole NTP server on an isolated network),  using  its  own
#    system clock as  the  reference source.  If enabled (by removing #),
#    this NTP server will  become  active  only  when  all  other  normal
#    synchronization sources are unavailable.
 
# server 127.127.1.0
# fudge 127.127.1.0 stratum 8