GEI-100505 (Network Time Protocol NTP)

g GEI-100505
GE Industrial Systems
Network Time Protocol (NTP)
These instructions do not purport to cover all details or variations in equipment, nor to
provide for every possible contingency to be met during installation, operation, and
maintenance. If further information is desired or if particular problems arise that are not
covered sufficiently for the purchaser’s purpose, the matter should be referred to GE
Industrial Systems.
This document contains proprietary information of General Electric Company, USA and is
furnished to its customer solely to assist that customer in the installation, testing, operation,
and/or maintenance of the equipment described. This document shall not be reproduced in
whole or in part, nor shall its contents be disclosed to any third party without the written
approval of GE Industrial Systems.
Safety Symbol Legend
Indicates a procedure or condition that, if not strictly

observed, could result in damage to or destruction of
equipment or data.
Note Indicates an essential or important procedure or statement.
Section Page
Introduction..................................................................................................................2
Installation ...................................................................................................................2
Concepts ......................................................................................................................4
Configuration ...............................................................................................................5
Working With NTP....................................................................................................12
Troubleshooting .........................................................................................................29
Notes ..........................................................................................................................32
________
Ethernet is a registered trademark of Xerox Corporation.
Windows and Windows NT are registered trademarks of Microsoft Corporation.
Introduction
This document describes the Network Time Protocol (NTP) and its individual Serv-
ices. NTP is a service used to synchronize the time of a pc (Client) to another pc
(which is the time source or Master). It usually provides Client synchronization
within 25 milliseconds (ms) of the Master on local networks. NTP is set to a default
configuration at installation time, and the service is configured using the Windowsâ
Control Panel.
NTP Diagnostics is a tool used to display statistics about the NTP service running on
the local pc or on any remote pc running it (refer to the section NTP Diagnostics).
NTP Status Indicator displays a clock icon in the Windows system tray to indicate
the synchronization status of the service (refer to the section, NTP Status Indicator).
Installation
For assistance, contact: Control System Solutions installs various products for control systems as selected in
the setup program. It is recommended that you exit all Windows programs before
Industrial Systems
beginning. A dialog box prompts you for a license key, which can be found on the
General Electric Company
actual CD. You must agree to the standard Software License Agreement for these
Product Service Engineering
products.
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA Ø To install the product
Phone 1 888 GE4 SERVE
1. Place the Control System Solutions CD in the disk drive. The Setup program
(888 434 7378, United States) executes automatically, or run the program setup.exe.
+ 1 540 378.3280 (interna-
tional) 2. Follow the instructions from each screen. For more help press F1.
Fax + 1 540 387 8606 (All)
(replace + with the interna-
tional access code)
Programs
The following programs are automatically installed in the NTP subdirectory. For
more information refer to .html product documentation, also installed in %System
Drive%\Program Files\GE Control System Solutions\NTP\htmldoc.
xntpd manages the time on the Master and Client pcs.
ntpq queries local and remote NTP pcs for state variables and related time keeping
information. This program conforms to Appendix A of the NTP Version 3 Specifi-
cation RFC 1305.
xntpdc queries local and remote NTP pcs for state variables and related time keep-
ing information. This program is specific to Version 3 of NTP and does not conform
to Appendix A of the NTP Version 3 Specification RFC 1305.
ntpdate operates like the UNIX
program rdate, but is much ntpdate sets the local pc time from one or more remote pcs running NTP.
more accurate.
2 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Managing
Decide initially to install either NTP or NTP Server based on the topology. Gener-
ally, NTP Server is installed on any pc that hosts a time card and NTP is installed on
every other pc that uses Ethernet.
Note NTP Server cannot run without a time card.
In situations where both products are installed on the pc, the configuration allows
selection of the active service. The other service is automatically deactivated in or-
der to prevent both services from running at the same time.
The service that is not activated is deactivated by setting its startup to Disabled (or
Manual in the case of NTP Server) and the service is stopped if it is running. This
ensures that the selected service automatically restarts when the computer is rebooted
without running the deactivated service.
Note Setting the deactivated service startup to Disabled does not prevent a user from
manually enabling and starting the service but it serves as an indication that the
service should not be manually started.
The NTP Configuration Utility can be used to configure and test both NTP Server
and NTP. Once both configurations are tested and configured as desired, NTP Server
can be made active. If problems arise with NTP Server, the configuration utility can
be used to activate the NTP service.
Control System Solutions GEI-100505 Network Time Protocol (NTP) • 3

Concepts
Time synchronization between control system computers and devices is critical for
monitoring and troubleshooting. Messages are time-stamped by the device that gen-
erated them and collected for display and diagnostic purposes in a central location or
in multiple locations. Synchronizing time allows an event in one device to relate to
the events in the rest of the system.
NTP synchronizes time between devices and Ethernet capable devices such as Inno-
vation Series and Mark VI controllers.
Note Many non-pc-based devices actually use Simple Network Time Protocol
(SNTP). SNTP nodes can use NTP time sources in the same way NTP nodes do, but
SNTP nodes do not contain all of the diagnostic information available with NTP.
NTP Diagnostics and other monitoring programs does not work with SNTP nodes.
Differentiation
NTP relies on the stratum level advertised by each time source to determine the best
one. The stratum level is an indication of the accuracy of the time source. The more
accurate the time source the lower the stratum level. A stratum 1 time source is one
that is directly tracking UTC time (or some other time standard ) via a satellite re-
ceiver. Time sources with the same stratum level are differentiated by NTP by fac-
tors such as network delays and availability.
Synchronization
Synchronization implies that NTP is actively regulating the local pc time against a
valid time source. If a pc is unsynchronized, the pc’s time is not being regulated by
NTP. Synchronizing the remote networks to the same time standard allows correla-
tion of events between the networks.
Broadcast Mode
Broadcast mode involves one or more Master nodes broadcasting periodic time mes-
sages and the Client nodes passively listening for these broadcasts.
For more information, see the Client nodes receive broadcasts from all Master nodes broadcasting on the same
section Monitoring. subnet. Client nodes generally synchronize to the lowest stratum Master.
Unicast Mode
Unicast mode sends a directed message (poll) from each Client node to the specified
Master node. The Master node sends a reply (another directed message) to the Client
node that sent the original message. Unicast mode is more accurate than Broadcast
mode because the network delays can be precisely measured in each direction. In the
Broadcast mode, the network delay can only be approximated from the total delay
time. As the number of time samples increases and the refinements to the local clock
become smaller, the Unicast Client nodes increase the time between requests for new
time data from the Master node.
Note Unicast mode is required to reach a time source on a different subnet.

Configuration
Refer to Configuring a Master The NTP configuration utility is located under the Windowsâ Control Panel and is
or Configuring a Client. used to view or change the configuration of the NTP service. A configuration wizard
uses configuration details to update the ntp.ini file, sets the NTP service startup to
Automatic, and then restarts the NTP service after the user commits the changes.
Note: Configurations outside the scope of this utility must be maintained by hand.
Refer to the Manually Maintaining the NTP Configuration section for details.
New installations should use the control panel applet whenever possible.
For more information, refer to The utility is also used to configure NTP Server. NTP and NTP Server can be in-
the section Managing. stalled on the same pc, but only one can be active at a time. The NTP configuration
utility allows the user to select which service to configure and make active if both
are installed.
Ø To activate the NTP Configuration Utility
In Windows 3.1, go to Program
1. Click Windows Start, Settings, and Control Panel.
Manager and double-click
Control Panel.
2. Double-click .
The current configuration on the pc displays. The Configure button begins the con-
figuration sequence, and the Exit button is used to exit the program without chang-
ing the current configuration.
Note: If NTP Server is installed on the pc and NTP is not installed, the NTP Con-
figuration Utility displays the NTP Server configuration. If both NTP and NTP
Server are installed on the pc, the utility displays the configuration of the currently
active service. See the Section Managing for more information.

Default Configuration
When NTP is installed for the first time on a pc, its configuration defaults to Broad-
cast Client by the installation utility.
After installation, the configuration of the service is maintained by the NTP Configu-
ration Utility. If a configuration other than Broadcast Client is desired, the user must
run the configuration utility after the installation is complete.
Standard Vs Custom Configuration

The NTP Configuration Utility supports both a Standard and a Custom configuration
mode. Standard Configuration Mode provides the simplest configuration of NTP. In
standard configuration, one node is configured as the time Master and all other nodes
are Client nodes, with all nodes in the system configured for the same NTP Data Ac-
quisition Mode. Custom Configuration Mode provides additional configuration op-
tions and is required when multiple time Masters are used.
Note: Custom configuration mode allows specification of up to 4 time servers, while

standard mode allows only one time Master to be specified.
Configuring a Client
Configuring NTP as a Client implies that the service is only receiving time from one
or more NTP sources. It is not intended to supply time to any other pc or device. If a
Client loses communication with all other NTP time sources on the Ethernet, syn-
chronization is lost.
Configuring a Master
. Configuring NTP as a Master implies that the NTP service on the pc is able to both
supply and receive time. Since NTP Masters are assumed to supply time to other
devices, they are always configured to use their local pc clock as a valid time source.
This ensures that if all other time sources on the Ethernet are lost, the NTP Master
maintains synchronization at least with its local clock in order to continue to supply
the NTP Clients with time information. This ensures that even if a high quality time
source is not available, all of the pcs and devices still track a common time refer-
ence.
Allowing Client nodes to lose synchronization when the exter-
nal time source is lost provides an indication of abnormal
conditions that need to be addressed. Do not have Client
nodes synchronized to local time.
Note When the Master is synchronized to the local clock, it advertises itself as a low
quality time source by using a high stratum number. When the NTP Master is syn-
chronized to a high quality time source, it adjusts its stratum level according to the
stratum level of the time source against which it is synchronized. This allows the
Clients to switch to a different time source if the Master loses its source of high
quality time and another high quality NTP source is available.

GE Master Time Server
An NTP Server node has been created on the GE Intranet to provide a reliable time
source for hosts running NTP on the GE plant network. The host, named GRUMPY,
broadcasts NTP packets every 64 seconds on the 165.156.xxx.xxx subnet (Broadcast
mode). GRUMPY can also be polled directly (Unicast mode) at address
165.156.1.14. The NTP configuration utility looks for this node when it runs in Stan-
dard Configuration mode and incorporates it into the configuration by default if it is
found. The configuration utility facilitates the use of this time source while a requi-
sition is being configured in Salem without the need to reconfigure NTP when the
requisition ships to the customer site. Refer to the configuration and topology exam-
ples in the following sections for further information.
Node Setup
Ø To configure the pc as a Broadcast Time Master
Select Master
or Client.
Select the
operating
mode.
Select Next. The Synchronization dialog box displays.

If Specify Time Master(s) is chosen, the Network Time Protocol (NTP) dia-
log box displays.
Primary Time Master always defaults to the GE Master

timeserver GRUMPY if it can be contacted on the network.
The optional Secondary Time Master specifies a time source

that exists at the customer site.
Click Next. The stratum slider bar indicates the level of accuracy.
The default value of 13 can be used if only one time master will
be configured for the system. If multiple time masters are
configured, adjust the stratum level so that each master has a
unique stratum level. The master with the lowest stratum level
will be used by the client nodes as long as it is available on the
network. If the lowest stratum master is lost, the master with the
next highest stratum level will be used, and so on.
Configuration is complete. The configuration is displayed in a final dialog box.

Special Configuration
NTP is configured by entries in the ntp.ini file. Modifying the ntp.ini file directly, or
upgrading from an older version of the NTP product can create mismatches between
the configuration specified in the ntp.ini file and the configuration parameters main-
tained by the utility in the registry.
Note Use the configuration utility to prevent mismatch errors.
Ø To check for proper operation

3. From Programs, select the Administrative Tools program group/folder.
Double-click .
4. Click the Event Viewer icon. The Event Viewer–Application displays.
5. From the Log menu, select Application. The Application Log displays.
Log Menu
Source Column
4. Under the Source column, double-click the latest NTP entry. The Event De-
tail dialog box displays.

Multiple entries can be written The text message in Event Detail indicates this pc is synchronized to the Master.
before synchronization occurs.
If there is a time difference of more than a minute between the Client and the Master
node, a delay can occur before time synchronization is achieved. This delay can be
minimized by stopping the NTP from the Service program and setting the Client time
to the current value of the Master node.
If the time difference between the Master and the Client nodes is greater than 2000
seconds, the NTP automatically shuts down before achieving synchronization. The
NTP sends the message time error is way too large (set clock manually) to the Event
Viewer. If the NTP service shuts down because of a large time error, set the Client
time to the current value of the Master node.

Ø To set the local time to the same value as the Master node
w From the MS-DOSâ command prompt on the Client pc, type the command
ntpdate <Master> (<Master> is the current Master pc). The NTP service
must be stopped on this pc before running this command.

Working With NTP
Startup Option
The NTP consists of a Service (xntpd.exe) and supporting programs used for de-
bugging and support.
When setup is complete, the file ntp.ini is created in the Windowsâ system direc-
tory. This text file contains the configuration settings for proper operation. Type set
systemroot at a command promptt to display the directory.
The Service program manages all NT services including NTP. The startup for each
service can be selected as automatic, manual, or disabled. The default for NTP
startup is set at automatic.
Ø To activate the Service dialog box
1. Click Windows Start, Settings, and Control Panel.
2. Double-click Services. The Services dialog box displays.
3. Click on Network Time Protocol.
4. Click Stop to shut down the service and Start to start it again.

Ø To change the Startup Type for the service
1. From the Services dialog box, click on the service you want to edit.
Automatic starts the NTP when 2. Click . The Service dialog box displays
the pc is started.
Manual allows the user to turn
on NTP on the Control Panel.
Disabled turns off the NTP.
The NTP does not run until the
Startup Type is changed.
3. Click Automatic, Manual, or Disabled.
4. Click OK. The new Startup Type displays in the Services dialog box.
Monitoring
For more information, refer to The NTP product includes an NTP Status Monitor utility that maintains an icon in
the section Diagnostics. the Windows System Tray. The icon provides a constant indication of the NTP syn-
chronization status of the pc. Refer to the NTP Status Monitor section for a detailed
description. Detailed statistics about the NTP service on the local pc or a remote pc
can be displayed using the NTP Diagnostic utility
NTP Server
Refer to the NTP Server docu- NTP Server is a separate product closely related to the NTP product that only re-
mentation (GEI-100507) for ceives its time from an internal time card. The time card can be configured to re-
information on installing and ceive time signals from a satellite or GPS time source, or the pc time card can use its
configuring NTP Server. internal low drift clock as a time source. If a satellite-based time source is not avail-
able, NTP can be configured as a time Master using either the internal pc clock or
another NTP time source on one pc, and the remaining pcs can be configured as time
Clients.
Note: The ability to act as both a time Master and a time Client is sometimes re-
ferred to as Peer operation.

Diagnostics
The Diagnostics utility monitors the status of the NTP Service on any specified com-
puter on the network. The application periodically polls the service and displays data
about the NTP Service. Diagnostics provides a Windows interface to the ntpq utility
and is installed with the NTP product installation as part of GE Control Systems
Solutions.
Ø To start NTP Diagnostics
w From the GE Control Systems Solutions program group, select NTP Di-
agnostic.
– Or – in Windows NT 4.0 and later:
Select NTP Status Indicator and right-click the icon located on the right
side of the taskbar. From the pop-up menu, click Create a new NTP Diag-
nostics window.
– Or – double-click on the icon .
The NTP Diagnostics application starts and the NTP Diagnostics window dis-
plays. Multiple NTP diagnostic windows can be open at once.
Ø To exit NTP Diagnostics
w For the NTP Diagnostics window, select the File menu and Exit.
– Or – click in the top right of the window.

Note The font used by NTP Diagnostics is automatically selected based on the
active video modeand cannot be changed by the user.
Configuration
The NTP host name is the only configurable item for this application. The default
host name is localhost, which displays data for the NTP service running on the local
computer.
Ø To display data on a remote computer
1. From the Configure menu, select Set Host.
2. Enter the name or IP address of the remote computer.

Operation
When NTP Diagnostics starts or when the user selects a new host, the application in-
dicates that it is waiting for a reply from the specified host:
The application displays data. It periodically (about every 5 to 10 seconds) updates

the data as it is received from the specified host as follows:
• Data that corresponds to the node that the computer is synchronized to displays
against a green background.
• Data that corresponds to any potential time source displays against a yellow
background.
• All other data displays against a white background.
The data fields are defined as follows:

remote is the name or IP address of each remote time source. The asterisk charac-
ter (*) indicates the current Master node, which indicates that synchronization with
this node has occurred. The plus character (+) indicates that the host is a potential
time source.
refid indicates the current source of synchronization for the remote time source.
st indicates the stratum level of the remote time source. The stratum level is a decla-
ration of the quality of the time source. Lower stratum numbers indicate a more ac-
curate time source.

t indicates the data gathering method used, such as u = Unicast, b = broadcast.
when is the time in seconds since the last broadcast from the time source (Broadcast
mode) or since the time source was polled by the Client (Unicast mode).
poll is the broadcast period of the time source or the polling rate of the Client node
(defined in the ntp.ini file by the minpoll parameter (2^minpoll)).
reach is an octal number representing the responsiveness of the time source.
delay is the communication delay between the time source and the local node in
milliseconds.
offset is the time difference between the time source and the local node in millisec-
onds.
disp (dispersion) is a measure of how well the local time is tracking the remote time
source. Smaller numbers indicate better tracking accuracy.
Status Indicator
The NTP Status Indicator displays the synchronization status of the NTP service
The icon displays in the through a clock icon. The icon has associated tool tips. The tool tips enumerate the
lower right of the Windows machine’s synchronization status, including the name or IP address of the node to
taskbar which the local machine is synchronized.
Note The NTP Status Indicator is not compatible with versions of Windows NT
prior to 4.0.
Operation
Ø To start the NTP Status Indicator
w From the GE Control Systems Solutions program group, select NTP
Status Indicator
– Or – from the MSDOS prompt, change to the directory where NTP is in-
stalled (usually C:\Program Files\GE Control System Solutions\NTP) and enter the
command ntpdiag -s.
The NTP Status Indicator starts. An icon displays in the lower right of the
Windows taskbar. Refer to the section Operation for icon status definitions.
The NTP Status Indicator queries the NTP service running on the local computer
approximately every 15 seconds and updates the clock icon in the Windows taskbar.
The icon graphically displays the NTP synchronization status of the computer.
Note Hold the cursor over the clock icon to generate a tool tip that enumerates the
synchronization status of the machine and the name or IP address of the node to
which the local machine is synchronized.

Menu Commands
The NTP Status Indicator menu commands:
• Close the application
• Start the application automatically whenever the computer is logged on
• Create NTP Diagnostic window(s) to display NTP data
• Access online Help
Ø To operate the menu command
w Click on the icon with the right mouse button. The following pop-up menu
displays:
This command toggles Click this command to

the auto start. A close the window. The
checkmark indicates icon disappears and the
that the command is on. application must be
reopened.
Click here for online
Help. Click here to create a
new window and view
specific NTP data.

Icon Status
When the NTP Status Indicator starts, the clock icon displays in the Windows task-
bar (right side). The icon status reflects the synchronization:
Icon Status Color of clock face
Not running white with red X
Waiting for feedback from the NTP serv- white

ice (displays when application starts)
NTP service is not synchronized red
NTP service is not synchronized, but yellow

has located at least one potential time
source
NTP service is synchronized green
The NTP Status Indicator dis- The NTP Status Indicator icon is animated to indicate that the application is ac-
plays a clock icon is designed tively receiving data from the NTP service. Every time the NTP service returns data
like a clock. This icon only to the application, the minute hand of the clock icon moves one position. The hour
conveys its relation to system hand of the clock icon always remains at the horizontal (3 o'clock) position.
time. It is not intended to re-
flect the actual system time.
Note Only one instance of the NTP Status Indicator can run on the computer. Do
not attempt to start the application when another instance of the application is al-
ready running.

Sample Topologies
The following sample topologies are provided to illustrate some of the configuration
options available using the NTP Configuration utility.
Single Broadcast Master With Broadcast Clients (Standard)

The following diagram illustrates the system topology where a single node is config-
ured as a Broadcast Master and the Client nodes are all configured for Broadcast Cli-
ent operation using the Standard configuration option. The Broadcast Master listens
for any broadcasts from other time sources. If it is on the GE Salem network it can
receive broadcasts from Grumpy, or if it is at the end site it receives broadcasts from
any time sources broadcasting on the Ethernet (on the same subnet). The Broadcast
Master synchronizes to one of these external time sources if they exist, otherwise it
synchronizes to its local clock and broadcasts that time on the Ethernet. The Client
nodes also receive all broadcasts on the Ethernet (on the same subnet). They syn-
chronize to an external time source, if available, as it has a lower stratum level than
the Broadcast Master. If there are no external time sources, or communication with
them is lost, the Clients receives broadcasts only from the Broadcast Master and they
synchronize to it.
Grumpy or
Site Master
(Broadcast
Master)
Broadcast
Master
Broadcast Broadcast Broadcast Broadcast

Client Client Client Client
Note: Broadcast mode can be problematic if there are many time sources broad-
casting on the same subnet, especially if those sources have similar stratum levels.
The broadcast Clients individually selects the best time source based on stratum level
and other factors such as network delays. With many similar broadcast sources avail-
able, the Clients might not synchronize to the same time source. It is possible they
continue to hunt for a better time source, causing them to periodically drop synchro-
nization from one time source and synchronize to a different one. Consider using
Unicast mode instead of broadcast mode for these types of situations.

Single Unicast Master With Unicast Clients (Standard)
ured as a Unicast Master and the Client nodes are all configured for Unicast Client
operation using the Standard configuration option. The Unicast server node named
Grumpy is the GE Salem Master Time Server and configured as the Primary Master
time source for the Unicast Master node. The Site Master is a time source at the site
and is specified as the Secondary Master time source for the Unicast Master node.
The Primary and Secondary Masters are optional. If they are not specified the Uni-
cast Master synchronizes to its internal clock only. If the Primary and Secondary
Masters are specified, the Unicast Master synchronizes to Grumpy while the system
is being staged at GE Salem. It synchronizes to the site Master after the system is in-
stalled at the site. The Unicast Client nodes request time from only the Unicast Mas-
ter node, regardless of other time sources on the Ethernet.
Note The Unicast Master node can be reconfigured to use an additional time source
at the site instead of Grumpy when the system is installed at the site.
Grumpy Site Master
Unicast Master
Unicast Unicast Unicast Unicast


Single Unicast Master Using NTP Server With Unicast
Clients (Standard)
ured as a Broadcast Master using NTP Server and the Client nodes are all configured
for Broadcaset Client operation using the Standard configuration option.
Satellite
Time
Source
Unicast Master
(NTP Server)

(NTP) (NTP) (NTP) (NTP)
Single Broadcast Master using NTP Server With Broadcast

Clients (Standard)
ured as a Unicast Master using NTP Server and the Client nodes are all configured
for Unicast Client operation using the Standard configuration option.
Satellite
Time
Source
Broadcast
Master
(NTP Server)


Multiple Broadcast Masters With Broadcast Clients
(Custom)
The following diagram illustrates the system topology where multiple nodes are con-
figured as Broadcast Masters using the Custom configuration option in order to as-
sign a unique stratum level to each. The Client nodes are all configured for Broadcast
Client operation using the Standard configuration option. The Broadcast Masters
listen for any broadcasts from other time sources. If they are on the GE Salem net-
work, they can receive broadcasts from Grumpy, or if they are at the end site they re-
ceive broadcasts from any time sources broadcasting on the Ethernet (on the same
subnet). The Broadcast Masters synchronize to one of these external time sources if
they exist, otherwise they synchronize to their local clocks and broadcast that time
on the Ethernet. The Client nodes also receive all broadcasts on the Ethernet (on the
same subnet). If there is an external time source they synchronize to it, since it has a
lower stratum level than the Broadcast Master. If there are no external time sources,
or communication with them is lost, the Clients receive broadcasts only from the
Broadcast Masters and they synchronize to the Master with the lowest stratum. The
Broadcast Masters listen to each other’s broadcasts, so the highest stratum master(s)
synchronize to the lowest stratum Master. If the lowest stratum Master is lost, the
next highest stratum Master is used.
Grumpy or
Site Master(s)
Broadcast Broadcast Broadcast

Master Master Master
(Stratum = 14) (Stratum = 13) (Stratum = 12)

Note: Broadcast mode can be problematic if there are many time sources broad-
casting on the same subnet, especially if those sources have similar stratum levels.
The broadcast Clients individually select the best time source based on stratum level
and other factors such as network delays. With many similar broadcast sources avail-
able, the Clients might not synchronize to the same time source. It is possible they
continue to hunt for a better time source, causing them to periodically drop synchro-
nization from one time source and synchronize to a different one. Consider using
Unicast mode instead of broadcast mode for these types of situations.

Triple Redundant Unicast Masters (Custom)
The following diagram illustrates the system topology where three nodes are config-
ured as Unicast Masters and the Client nodes are all configured for Unicast Client
operation. The Master nodes must be configured using the Custom configuration op-
tion to allow adjustment of the stratum levels. The Client nodes must be configured
using the Custom configuration option to allow specification of multiple Master time
sources. In the configuration, the Unicast Master nodes can be configured to syn-
chronize to one or multiple time sources at the site. The higher stratum Masters also
poll the lower stratum Masters. The Client nodes periodically poll each Master node
and synchronize to the best one based on the Master node’s stratum level. If the Uni-
cast Masters are synchronized to a quality time source at the site, their stratum level
reflects the stratum level of the source to which they are synchronized. If there are no
time sources available at the site or communication with the available time sources is
lost, the Master nodes assume the stratum level for which they have been configured.
In this case, the Client nodes synchronize to the Master with the lowest stratum level,
and the higher stratum Masters synchronize to the lowest stratum Master. If the low-
est stratum Master becomes unavailable, the Clients use the next lowest one.
Unicast Master
(NTP)
Unicast Master (stratum = 12)
(NTP)
(stratum = 13)
Unicast Master
(NTP)
(stratum = 14)


Master Polling On A Different Subnet (Custom)
The following diagram illustrates a system where there are no time sources broad-
casting on the local subnet. The Master node is configured as a Broadcast and Uni-
cast Master using the Custom configuration option to poll a time source (or multiple
sources) on a different subnet and broadcast the time to the Clients on the local sub-
net.
Note Unicast mode is the only way to receive time from sources on remote subnets
because broadcast messages are not repeated by routers to other subnets.
Grumpy or
Site Master(s)
Subnet Boundary
Broadcast and
Unicast Master


Sample .ini files
ntp.ini file can be edited with The ntp.ini file is a text file that provides the startup parameters for the Network
any text editor, such as Win- Time Protocol service. This file is created by the setup program during installation,
dows NT® Notepad. and is modified by the configuration utility under the Windowsâ Control Panel.
Changes to the ntp.ini file do not become effective until the NTP service is stopped
and restarted. The setup utility and the configuration utility automatically stop and
restart the NTP service when changes are made. Changes made directly to the ntp.ini
file require the user to manually stop and restart the service or reboot the machine
before the changes take effect.
This document is automatically
installed in the NTP directory. Note Normally it is not necessary to edit the ntp.ini file. Changes should only
be made using the NTP configuration utility under the Windowsâ Control Panel.
However, if the Service is not operating properly, consult the full product documen-
tation in the directory \Program Files\GE Control System Solutions
\Ntp\htmldoc. Refer to the readme.txt file to view the HTML Help files.
The following is an example of an ntp.ini file for a Broadcast Master node:

#
# Created by Version 2.0 of the NTP Control Panel Application 14:16:17
# 10/25/2000
#
# Provides the NTP Service its startup parameters and
# list of startup files.
#
# Refer to the HTML documentation ( in the C:\Program Files\GE Control System
# Solutions\NTP\htmldoc directory)
# for complete details on the options supported.
# See readme.txt in the htmldoc directory for setting up the html files.
#
#
# -----Time Master Server entries -----------
#
server 127.127.1.0 prefer minpoll 4 # Use this pc as time Master server
fudge 127.127.1.0 stratum 12 # Use local clock on server as time source
disable auth
broadcast 255.255.255.255 minpoll 4
broadcastClient
#
#
driftfile C:\PROGRA~1\GECONT~1\NTP\ntp.drift # path for drift file
#
# --- Remove comment to activate debug files in stats dir ----
# statsdir C:\PROGRA~1\GECONT~1\NTP\stats\ # directory for statistics files
# statistics loopstats peerstats

The following is an example of an ntp.ini file for a Unicast Master node synchro-
nized to the server Grumpy with NS01 as a secondary time source:
#
# 10/25/2000
#
#
#
#
# -----Time Master Server entries -----------
#
server 127.127.1.0 prefer minpoll 4 # Use this pc as time Master server
fudge 127.127.1.0 stratum 12 # Use local clock on server as time source
disable auth
#
# Comment out the following 'server' line(s) to remove the remote time source(s).
server GRUMPY
server NS01
#
#
#
The following is an example of an ntp.ini file for a Broadcast Client node:
#
# 10/25/2000
#
#
#
#
# -------- Client entry --------------------
#
disable auth
broadcastClient
#
#
#

The following is an example of an ntp.ini file for a Unicast Client node:
#
# 10/25/2000
#
#
#
#
# -------- Client entry --------------------
#
disable auth
server GRUMPY
#
#
#

Troubleshooting
Configuration Mismatch
The NTP Configuration Utility maintains the NTP configuration information in the
registry and writes the ntp.ini file according to these entries. When the utility is
started, the specified registry entries are verified. If a mismatch is found, the utility
presents the following dialog box:
For more information, see the Selecting Next causes the utility to create a backup of the original ntp.ini file
section Manually Maintaining (named ntp_backup.ini) and allows the utility to continue with the configuration
the NTP Configuration. process. The current configuration defined by the utility in the registry is displayed
to the user and the user can modify the configuration or exit without making
changes. If the user accepts the changes at the end of the configuration sequence the
ntp.ini file is rewritten. The user should compare the new ntp.ini file with
ntp_backup.ini if there are any configuration details from the original configuration
that need to be saved. The configuration utility should be used to implement any
missing functionality. Functionality that was added by hand that is outside the scope
of the configuration utility must either be abandoned or manually supported outside
of the configuration utility
Re-Installing Over An Existing Version

The upgrade detects the existing ntp.ini file and makes no changes to the registry
settings or the existing ntp.ini file.
Upgrading the NTP product from an old version can create some configuration man-
agement issues. Early versions of the NTP product incorporated the configuration
activity into the installation step. Dialogs similar to the configuration utility were
presented during installation time and the results were saved in the registry and used
to create the ntp.ini file.

For more information, refer to Changing the configuration after installation required either re-installing the NTP
the section Configuration Mis- product or modifying the ntp.ini file by hand. If the NTP product was always con-
match. figured by re-installing it, the registry entries matches the .ini file and mismatches
between the registry and .ini file should not exist. If the ntp.ini file has been config-
ured by modifying the ntp.ini file directly, the installation does not overwrite the
current ntp.ini file or the registry settings, but the NTP Configuration Utility should
be used to establish control of the configuration. The configuration reports the mis-
match when it runs and saves a copy of the ntp.ini file to ntp_backup.ini. This
backup file should be used as the basis for configuring NTP with the configuration
tool.
It is not recommended to leave the ntp.ini and registry set-

tings in a mismatched state. The configuration should either
be recreated using the configuration utility or the configura-
tion should be maintained outside of the configuration utility
as described in the Manually Maintaining the NTP Configura-
tion section.
Uninstalling The Old Version, Then Re-Installing A

New Version
For more information, refer to If an old version of NTP is uninstalled before a new version is installed, the existing
the section Manually Main- ntp.ini file is removed as part of the uninstall and the original configuration is lost. If
taining the NTP Configuration. you want to save the configuration, save the ntp.ini file with a different name before
uninstalling. Use this file as the basis for recreating the configuration using the con-
figuration utility. The file can be saved as ntp.conf and the configuration maintained
manually.
NTP.ini File Path And The Broadcast Mask

The configuration specified in an old ntp.ini file matches the registry settings main-
tained by the configuration utility, but the path information stored in the ntp.ini file
reflects an obsolete path. If the .ini file matches the registry but the path specified in
the .ini file does not match the current product installation directory, the NTP Con-
figuration Utility saves the ntp.ini file to ntp_backup.ini and overwrites the ntp.ini
file so that the paths specified in the .ini file correctly match the installed product. No
action is required by the user in this situation. The configuration utility presents the
following message:

The situation can arise where NTP has been configured as a Broadcast Master and
the ntp.ini file was created by an old version of the product installation. The default
broadcast mask used in older versions has been changed in later versions of the
product. If the broadcast mask corresponds to an old version of the product, the
ntp.ini file is copied to ntp_backup.ini and the file is overwritten. No action should
be required by the user in this situation. The following message displays:
Manually Maintaining the NTP Configuration

The NTP Configuration Utility provides a mechanism for maintaining the configura-
tion outside of the configuration utility in order to support configurations beyond the
scope of the configuration utility. The NTP service looks first for the existence of an
ntp.conf file, and if that file is not found it looks for the ntp.ini file. The configura-
tion utility issues a warning to the user and terminates if the ntp.conf file is found in
the winnt directory. The configuration utility does not attempt to alter the ntp.conf
file. The ntp.conf file is also not considered part of the NTP product files, so it is not
deleted when the NTP product is uninstalled. Creating the ntp.conf file is the only
way to specify a configuration that is beyond the scope of the configuration utility
and guarantee that the configuration is persistent between product installations.
The drift file and statsdir paths specified in the ntp.conf file
must be manually updated to reflect the product installation
directory if it changes between product versions.

Notes
g
GE Industrial Systems
Issue date: 2001-02-14 General Electric Company
 2001 by General Electric Company, USA.
All rights reserved.
1501 Roanoke Blvd.
32 • Network Time Protocol (NTP) Salem, VA 24153-6492 USA Control System Solutions GEI-100505

GEI-100505 (Network Time Protocol NTP)

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GEI-100505 (Network Time Protocol NTP)

Caricato da

Copyright:

Formati disponibili

g GEI-100505

Network Time Protocol (NTP)

Indicates a procedure or condition that, if not strictly

Note Indicates an essential or important procedure or statement.

2 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Note NTP Server cannot run without a time card.

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 3

Note Unicast mode is required to reach a time source on a different subnet.

4 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 5

Standard Vs Custom Configuration

Note: Custom configuration mode allows specification of up to 4 time servers, while

6 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Select Next. The Synchronization dialog box displays.

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 7

Primary Time Master always defaults to the GE Master

The optional Secondary Time Master specifies a time source

Configuration is complete. The configuration is displayed in a final dialog box.

8 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Note Use the configuration utility to prevent mismatch errors.

Ø To check for proper operation

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 9

10 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 11

1. Click Windows Start, Settings, and Control Panel.

2. Double-click Services. The Services dialog box displays.

3. Click on Network Time Protocol.

12 • Network Time Protocol (NTP) Control System Solutions GEI-100505

3. Click Automatic, Manual, or Disabled.

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 13

– Or – in Windows NT 4.0 and later:

– Or – double-click on the icon .

– Or – click in the top right of the window.

14 • Network Time Protocol (NTP) Control System Solutions GEI-100505

2. Enter the name or IP address of the remote computer.

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 15

The application displays data. It periodically (about every 5 to 10 seconds) updates

• All other data displays against a white background.

The data fields are defined as follows:

16 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 17

• Start the application automatically whenever the computer is logged on

• Create NTP Diagnostic window(s) to display NTP data

• Access online Help

Ø To operate the menu command

This command toggles Click this command to

18 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Waiting for feedback from the NTP serv- white

NTP service is not synchronized red

NTP service is not synchronized, but yellow

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 19

Single Broadcast Master With Broadcast Clients (Standard)

Broadcast Broadcast Broadcast Broadcast

20 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Grumpy Site Master

Unicast Unicast Unicast Unicast

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 21

Unicast Unicast Unicast Unicast

Single Broadcast Master using NTP Server With Broadcast

Broadcast Broadcast Broadcast Broadcast

22 • Network Time Protocol (NTP) Control System Solutions GEI-100505

Broadcast Broadcast Broadcast

Broadcast Broadcast Broadcast Broadcast

Control System Solutions GEI-100505 Network Time Protocol (NTP) • 23