Options - Option E06 Network Time Protocol (NTP) / Precision Time Protocol (PTP) Server Copper/Copper
Provides GNSS-synchronized, stratum level 1 Network Time Protocol or Precision Time Protocol - PTP (IEEE 1588) on two 10/100BT connectors. Available on Model 1201B/C.
The Network Time Protocol / Precision Time Protocol Server option allows an Arbiter Systems®, Inc. GNSS Synchronized Clock to act as a time server over an Ethernet network using the Network Time Protocol (NTP) and the Precision Time Protocol (PTP). Operating as a primary server (NTP stratum 1 or PTP Grandmaster), time is distributed to connected systems, such as workstations, PCs, servers, routers, relays and other IEDs via the two 10/100 BT Ethernet interfaces. The Network Time Protocol Server understands NTP version 2, version 3 and version 4 frames while optionally supporting authentication via DES and MD5 cryptographic checksums as defined in RFCs 5905. Typical accuracy for NTP is one millisecond on a LAN to a few tens of milliseconds on a WAN as compared to UTC (Coordinated Universal Time); accuracy varies depending upon network traffic. The Precision Time Protocol Server supports the IEEE 1588-2008 protocol and functions as a grandmaster clock. PTP accuracy is better than 1 microsecond.
The Option E06 was designed with flexibility and security in mind allowing customized configurations while maintaining NERC CIP compatibility. Dual 10/100 Mb/s, independently configurable Ethernet ports give simultaneously access to both the NTP and PTP servers. Providing both NTP and PTP support allows for future upgrade paths for networks that currently lack PTP hardware support. Configuration is simplified using the web interface or the SSH console. The two 10/100BT Ethernet ports are standard electrical RJ-45 connectors.
NTP Principles of Operation
Synchronizing a client to a network server consists of several packet exchanges where each exchange is a pair of request and reply. The client stores its local time into the packet being sent. The server receives the packet and then stores its own estimate of the current time into the packet and returns the updated packet. The client receives the updated packet and will once more log its own receipt time to estimate the travelling time of the packet.
These time differences are used to estimate the time it took for the packet to be transmitted from the server to the client. That round-trip time is taken into account when estimating the current time. The shorter the round-trip time, the more accurate the estimate of the current time.
It takes several packet exchanges before the client accepts the server time is correct. Only when the replies from the server satisfy the conditions defined in the protocol specification, is the server considered valid. Time cannot be synchronized from a server that is considered invalid by the protocol. Multistage filters are used to estimate the quality of the time samples. Usually it takes about five minutes (five good samples) until an NTP client is synchronized to a server.
The quality estimate of a client, obtained using multistage filtering, usually improves over time. If the client has a more accurate estimate than a server, such a server may be considered invalid after some time.
PTP Principles of Operation
PTP was developed to provide very precise time coordination of LAN connected devices using hardware assisted synchronization. Similar to NTP, PTP uses a master clock to provide a time reference for one or more slave clocks or clients. PTP clients use a best master clock algorithm to determine the best clock to synchronize with. The master clock sends out a synch message every 2 seconds (default setting) and then sends out a follow up message with the exact time the original sync message was sent. The slave clock sends a delay request message to the master clock noting the time it was sent in order to measure and eliminate packet delays. The master clock then replies with the time stamp the delay message was received. The slave clock then computes the master clock time compensated for delays and finalizes synchronization.
NTP: Better than one hundred microseconds, depending on network load and clock accuracy
PTP: Better than one microsecond with hardware assist
Link (green 10 Mb/s, yellow 100 Mb/s)
Web (HTTP or HTTPS) and SSH
IP Number (DHCP or Static)
UDP Broadcast parameters
Two Ethernet (Ver 2.0/IEEE 802.3)
Two - 10/100BT standard RJ-45.
NTP, SNTP, PTP (IEEE 1588TM-2008)
ICMP, SNMP, TCP, SSH, SCP, SSL
HTTP, HTTPS, DHCP