Page 1
User Manual Quad Port NTP Time Server NTP-800 For Brandywine Communications and Time & Frequency Solutions Part Number: 040600202 900600201 Rev. A April, 2024...
Page 2
Revision History REVISION DATE COMMENTS ECO NUMBER 2024/04/09 For NTP800 S/W V2.2 ECO13028...
Page 3
Safety Warnings WARNING: The lightning flash with an arrowhead inside of an equilateral triangle is intended to alert the user to the presence of uninsulated “dangerous voltage” within the product’s enclosure. The “dangerous voltage” may be of sufficient magnitude to con- stitute a risk of electrical shock to people.
Chapter 1 System Overview Introduction to the NTP800 Multi-port Time Server This manual shows you how to install, configure and operate your NTP800 to provide a Network Time Protocol (PTP) time server for your network. Once up and running the NTP800 will provide accurate time synchronization for your computer clients to within nanoseconds on a Local Area Network (LAN) and tens of microseconds over a Wide Area Network (WAN).
1.2. SYSTEM OVERVIEW CHAPTER 1. OVERVIEW NTP800 System Overview The NTP800 time server is a Stratum 1 NTP time server that can synchronise from up to three external reference sources: Global Navigation Satellite Systems (GNSS)—such as the Global Positioning System (GPS)—Inter Range Instrument Group (IRIG) Time Code and serial time of day with Pulse Per Second (PPS).
Page 15
CHAPTER 1. OVERVIEW 1.2. SYSTEM OVERVIEW Figure 1.1: NTP800 Block Diagram 3 of 107 900600201 Rev. A...
1.3. SPECIFICATIONS CHAPTER 1. OVERVIEW Specification (Basic Unit) 1.3.1 Reference Inputs 1.3.1.1 Commercial GNSS • GNSS, Active or Long Distance Antenna • 1 PPS with Serial Time of Day • IRIG B, AC or DC • NTP Client • 10 MHz 1.3.1.2 Outputs •...
1.3. SPECIFICATIONS CHAPTER 1. OVERVIEW 1.3.1.6 Physical (Stand Alone Unit) Size 19-inch rack mounting 1U high 200 mm deep Weight 4 5 kg Power Dual redundant option, hot swappable AC Power 90 V to 264 V AC 50-60 Hz Load 20 W (typical), subject to oscillator. Connection via 3 pin IEC plug DC Power 18 V to 36 V DC...
CHAPTER 1. OVERVIEW 1.3. SPECIFICATIONS 1.3.1.9 Frequency Stability Table 1.1 below shows the frequency stability of the various oscillator options for the NTP800. Table 1.1: Oscillator Frequency Stability Holdover accuracy at Stability constant temperature Oscillator Performance while disciplined Averaging Time per C after loss of reference.
Chapter 2 Quick Start Guide Remove the NTP800 from the shipping carton shown in Figure 2.1 below. The fol- lowing items should be included in the shipment: • 1 NTP800 • 2 Power supply cables • 1 CD-ROM containing User Manual and Utility Software Figure 2.1: NTP800 Quick Setup Guide 9 of 107 900600201 Rev.
Chapter 3 Installation Site Preparation 3.1.1 Antenna To prepare the site for the NTP800 installation, a suitable antenna location has to be found. The antenna is a sealed unit. It should be located outside where there is good sky- coverage (e.g. on a roof) and away from high frequency electrical interference sources. It is highly recommended to use the mounting points provided and not to make any additional holes for mounting since may compromise the IP65 rating of the antenna.
3.1. SITE PREPARATION CHAPTER 3. INSTALLATION 3.1.1.1 Power The NTP800 requires between 90 V to 240 VAC @ 50/60 Hz for power. Power Con- sumption is 30 W. 3.1.1.2 Network The NTP800 has four RJ45/SFP network connections. If an SFP module is fitted for a port, the associated RJ45 port is disabled.
Page 25
CHAPTER 3. INSTALLATION 3.1. SITE PREPARATION 3.1.1.4 Power Insert the power cord of the NTP800 into an electrical socket to apply power to the unit. If dual redundant power is required, connect both power supplies to independent power sources 3.1.1.5 Antenna Connect the antenna to the BNC connector J17 labelled “GPS Antenna”...
Chapter 4 Setup Power on the NTP800 by switching the rear Power Supply Module to the upwards “On” position. To view the IP address depress the reset button on the rear of the unit for a maximum of 5 seconds and release. The 4 IP addresses are then rolled across the front panel display shown in Figure 4.1 for 10s each in sequence, expressed in the standard dot decimal format, with the left most digit indicating the port number 1 to 4.
4.1. ACCESSING THE NTP800 CHAPTER 4. SETUP Accessing the NTP800 NOTE The NTP800’s factory settings have no default username and password for the system. Ensure you configure appropriate security settings for your environment after setting it up. Once the NTP800 is powered on and connected to the network, open up a web browser on a device connected to the same network as the NTP800 and type the IP Address of the NTP800 into the address bar to access the web page user interface (Web UI) shown in Figure 4.2 below.
CHAPTER 4. SETUP 4.1. ACCESSING THE NTP800 Table 4.1: Status Web Page Field Description Firmware Displays the name of the NTP800’s firmware. Runtime The length of time that the NTP800 has been powered on. Version Displays the current version of the NTP800’s firmware.
4.2. NETWORK CONFIGURATION CHAPTER 4. SETUP Network Configuration Web Page Use the [NETWORK] button on the right to select the network configuration page shown in Figure 4.3 below. This provides configuration for all the network settings, IP addresses, SNMP and service selection for the network ports. Figure 4.3: Network Setting Web Page Configure each port as required.
CHAPTER 4. SETUP 4.3. SOURCES AND NTP Sources and NTP Configuration Use the [CONFIGURE NTP] buttons to open the Time Source Settings Configura- tion page shown in Figure 4.4 below to configure the unit references and NTP service. The timesources and priority boxes allow for selection and ordering of timesources for synchronization.
4.3. SOURCES AND NTP CHAPTER 4. SETUP Figure 4.5: NTP Configuration Web Page, continued When using peer to peer mode, add the IP addresses for the NTP peers, along with their associated polling interval range values. For the NTP standard, this range value should be from 64s.
Chapter 5 Connections Figure 5.1: Rear Panel Drawing Figure 5.1 above shows the rear of the NTP800. The following sections of this chapter detail the signal formats that the NTP800 is capable of receiving or sending. 21 of 107 900600201 Rev. A...
5.1. INPUT SIGNAL CONNECTIONS CHAPTER 5. CONNECTIONS Input Signal Connections 5.1.1 GNSS Antenna Connections (GNSS Version) 5.1.1.1 Standard GPS Antenna for NTP800 P/N 040002XX The antenna is connected to the BNC port marked J17 GPS Antenna on the rear of the NTP800. The antenna connector is a BNC Socket (50 Ω) and its connections are: Centre Pin : GPS Signal 1 6 GHz (&...
CHAPTER 5. CONNECTIONS 5.1. INPUT SIGNAL CONNECTIONS 5.1.2 IRIG B Time Code Input The IRIG B time code input is connected to BNC connector J15. The pin connections are as follows: Centre Pin : Time Code Input Shield : Time Code Return This is internally configured for either Modulated (IRIG B12X) or IRIG DCLS (IRIG B00X).
5.1. INPUT SIGNAL CONNECTIONS CHAPTER 5. CONNECTIONS 5.1.4 1PPS Input This 1 PPS input is used to provide the on-time mark for the time of day. Time of day message will follow the PPS to which it is associated. The 1 PPS input is connected to BNC connector J13.
CHAPTER 5. CONNECTIONS 5.2. OUTPUT CONNECTIONS Output Connections 5.2.1 1PPS Output NOTE If enabled, the 1 PPS output will be available from initial power on. It should be noted, however, that the 1 PPS will not be within the quoted accuracy specifications until the NTP800 has synchronized. Upon synchronization of the NTP800 to the selected reference, the 1 PPS will be accurate to the quoted specifications.
5.2. OUTPUT CONNECTIONS CHAPTER 5. CONNECTIONS 5.2.2 IRIG Time Code Output NOTE The available options for IRIG-B output type are dependent upon the factory settings, as configured for customer requirements. The NTP800 generates IRIG B serial time code in either carrier modulated (AC) or Unmodulated (DCLS) format by means of the IRIG Output radio button, on the [CONFIGURE OUTPUTS] webpage.
CHAPTER 5. CONNECTIONS 5.2. OUTPUT CONNECTIONS 5.2.3 Time of Day Output Port J10 provides time of day output through an RJ45 connection with the pinout shown in Table 5.3. RS422 is available from pins 1 & 2, and RS232 from pins 3 & 4. Table 5.3: J10 Pin Connections Signal RS422 TX +...
5.2. OUTPUT CONNECTIONS CHAPTER 5. CONNECTIONS 5.2.3.1 NMEA0183 Message format GPZDA The NMEA0183 message format provides UTC day, month, and year, and local time zone offset. Table 5.4 below shows a more detailed breakdown of the ZDA message format. An example of the ZDA message string is: $GPZDA,172809.456,12,07,1996,00,00 45 Table 5.4: ZDA Message Fields Field...
CHAPTER 5. CONNECTIONS 5.2. OUTPUT CONNECTIONS 5.2.3.2 TFS Message1 Table 5.5 below shows the fields for the TFS Message1 output from the NTP800. Table 5.5: TFS Message1 Fields Field Meaning BCD centiseconds BCD seconds BCD minutes BCD hours BCD Day of Week (00 = Sunday) BCD Day of Month BCD Month BCD Year...
5.3. NETWORK PORTS CHAPTER 5. CONNECTIONS Network Ports Four independent Ethernet ports are available for interfacing to your network(s) and can use either the standard Ethernet RJ45 connections or and SFP module. If an SFP module is fitted the associated RJ45 connection port is disabled. The unit is also configured and monitored via a web GUI through a network connection.
CHAPTER 5. CONNECTIONS 5.4. POWER CONNECTION Power Connection The AC power connector is suitable for 90 V to 240 V AC at 50/60 Hz. Use Table 5.6 below to find the power cord appropriate to the country of use. A locking cord is available for applications where the power cord must remain securely attached when the power cord may experience tension –...
5.5. DEFAULT SETTING / IP BUTTON CHAPTER 5. CONNECTIONS Default Setting / IP Address Button Pressing this button for less than 5 seconds and releasing it causes the unit to display its four IP address in sequence for 10 seconds each. The 4 IP addresses are then given for 10s each in sequence, expressed in dot-decimal notation.
Chapter 6 Web Configuration The main configuration method is via the web interface. There are five main pages, two for status information and three for configuration. Access to any of these is via the navigation bar shown in Figure 6.1. Figure 6.1: NTP800 Navigation Menu The three pages that configure the unit are: •...
Page 46
CHAPTER 6. WEB CONFIGURATION The NTP800 is delivered with all the web security disabled so access to the unit for the first time does not require login details. It is highly rec- ommended that these are set on first use to avoid unauthorised access. NOTE All security credentials are case sensitive.
CHAPTER 6. WEB CONFIGURATION 6.1. SYSTEM SECURITY System Security System security is managed using the System Setup Screen, shown in Figure 6.2. NTP800 offers user-defined security configuration for the following areas: 1. Login credentials 2. Simple Network Management Protocol (SNMP) 3.
6.1. SYSTEM SECURITY CHAPTER 6. WEB CONFIGURATION 6.1.1 Login Credentials NOTE Do not lose the details of the user name and password. If they are lost then the unit will have to be restarted and the factory defaults restored. Use the fields shown in Figure 6.3 below to set a username and password, and to control access to the NTP800.
CHAPTER 6. WEB CONFIGURATION 6.1. SYSTEM SECURITY 6.1.2 Remote Configuration Access NOTE It is important that discrepancies are avoided between the subnet mask and IP address; for example if 192.168.101.1 had been entered with a subnet mask of 255.255.255.0 then all access would be denied as there are no addresses that can meet this configuration.
6.1. SYSTEM SECURITY CHAPTER 6. WEB CONFIGURATION 6.1.3 SNMP v3 Credentials Use the section of the webpage shown in Figure 6.4 below to configure SNMP V3 with the authentication and privacy keys. Figure 6.4: SNMP v3 Credentials Input Area Enter the desired keys and click on [Submit]. 6.1.4 NTP Aunthentication The section of the webpage shown in Figure 6.5 below allows the three following...
Page 51
CHAPTER 6. WEB CONFIGURATION 6.1. SYSTEM SECURITY keys and the authentication type. This file is uploaded in its entirety. It is up to the user to manage this file and maintain appropriate secure copies. Once uploaded the file cannot be directly accessed in any way. If a change to it is required it must be done to the file externally and reloaded.
6.2. NETWORK CONFIGURATION CHAPTER 6. WEB CONFIGURATION Network Configuration This page, shown in Figure 6.6, allows the configuration of each of the Ethernet ports. Select the port to configure from the drop down list box. The current settings for that port will be shown. Figure 6.6: Network Settings Screen The following settings in Table 6.1 on the next page are port specific: Speed, Duplex...
CHAPTER 6. WEB CONFIGURATION 6.2. NETWORK CONFIGURATION Table 6.1: Port Specific Network Settings Description Setting Permit port to acquire its address via Dynamic Host Con- DHCP (IP4 IP6) figuration Protocol (DHCP). This will be shown on the status page. This can only be applied to one port of the unit.
6.2. NETWORK CONFIGURATION CHAPTER 6. WEB CONFIGURATION Table 6.2: Port Non-specific Network Settings Description Setting Comma separated list of DNS server IP addresses. DNS server list (IPv4 IPv6) These are effective on the ports that have SNMP access SNMP enabled. parameters The NTP800 will send traps when a trap address is set.
6.3. CONFIGURE CHAPTER 6. WEB CONFIGURATION Configure This page sets up the NTP service and input and output sources. The NTP800 has three possible external reference sources, GNSS, IRIG and Time of Day (with PPS). The use of these sources can be either as manual selection or under the TimeWall™arbitrator.
CHAPTER 6. WEB CONFIGURATION 6.3. CONFIGURE The default priority order is GNSS, IRIG and Time of Day. Without any available reference time, an external 10 MHz will be used to maintain the timescale established from the last available reference source. 6.3.1.1 STATS This is used for diagnostic purposes and should normally not be enabled.
6.3. CONFIGURE CHAPTER 6. WEB CONFIGURATION The tracked satellites on status page will show the satellites used in each constella- tion. 6.3.1.4 Signal Mask A signal level value below which satellites ignored for timing, this is an integer between 0 and 55. The default value is 35, reduce this if there are problems with GNSS synchronization.
CHAPTER 6. WEB CONFIGURATION 6.3. CONFIGURE 6.3.1.8 IRIG year For IRIG formats that do not contain a year, enter the current year. This will be provided by other reference sources if they are available. 6.3.1.9 AC/DCLS Set to agree with the configuration of the unit for the IRIG input; either AC IRIG or DCLS.
6.3. CONFIGURE CHAPTER 6. WEB CONFIGURATION 6.3.1.12 Time of Day Select the serial port parameters from the list, either RS232 or RS422. Select the message protocol to be expected either GPZDA standard NMEA message or TFS message 4, defined in Appendix D on page 101. 6.3.1.13 Local time Check this box if the time in the reference source message is in local time and not...
CHAPTER 6. WEB CONFIGURATION 6.3. CONFIGURE 6.3.1.15 Mulitcast (or Broadcast) Address The NTP800 can be used as a broadcast NTP server. A broadcast address or mul- ticast address can be specified in the multicast address box along with the poll interval.
6.3. CONFIGURE CHAPTER 6. WEB CONFIGURATION 6.3.2 Outputs Table 6.3 below shows the various output configuration options. Table 6.3: Output Configuration Options Output Description Enable/disable PPS output Select the required IRIG output format. DCLS or AC IRIG IRIG output is dependent on the hardware jumper con- format figuration.
CHAPTER 6. WEB CONFIGURATION 6.4. STATUS Status The status of the NTP800 is shown across two status pages. 6.4.1 Status Selecting [STATUS] will bring up the NTP800 Network Time Server status screen, shown in Figure 6.9 shows the current running state of the NTP800. The top section shows the system state including how long it has been running and the currently loaded date and time.
Page 64
6.4. STATUS CHAPTER 6. WEB CONFIGURATION Where multi-constellation mode has been selected then the satellites tracked from each constellation are identified. PTP slave status provides an indication of the NTP800 operational state, with regard to the PTP network clock hierarchy. The NTP status indicates the current NTP service synchronization source and the stratum level.
CHAPTER 6. WEB CONFIGURATION 6.5. EVENTS Events Figure 6.10 below shows the Event Log Screen. Figure 6.10: Event Log Screen The following lists all the events and their causes that can appear in the event log. They will cause an SNMP v1 trap to be sent to SNMP enabled ports. Global Positioning System (GPS) events are also shown on the front panel of the NTP800, and these events will be shown in the relevant status field on the web status page.
6.5. EVENTS CHAPTER 6. WEB CONFIGURATION 6.5.1 System Events Table 6.4 below shows the possible System Events for the NTP800. Table 6.4: System Events Event Description System startup. Initialization of event log. Not visible after first 800 events. Manual restart Remote reboot has been applied.
CHAPTER 6. WEB CONFIGURATION 6.5. EVENTS some intermediate messages will occur as the number of satellites tracked increases. In most cases, if any state other than normal is seen persistently then the likelihood is that there is an issue with the GPS reception either due to antenna placement, operation or cable length.
6.6. REMOTE RESTART CHAPTER 6. WEB CONFIGURATION Remote Restart There is a mechanism to remotely reboot the NTP800. From the SYSTEM webpage notice the small ‘ ’ on the top left side of the webpage as shown in Figure 6.11 below. Figure 6.11: Detail View of Remote Restart Option Selecting the [reboot now] button will cause the unit to do a complete restart.
CHAPTER 6. WEB CONFIGURATION 6.6. REMOTE RESTART Figure 6.12: Remote Restart Complete Clicking the link shown in Figure 6.12 above will take you back to the status webpage. 57 of 107 900600201 Rev. A...
Chapter 7 Working with the Clock Management System The status of the NTP800 will be shown on the status tab for the particular time server. There are five sources of possible alarm states. These relate to the status elements NTP overall state, GPS system state and the ETHx ifOperState for each port.
CHAPTER 7. CLOCK MANAGEMENT SYSTEM Table 7.1: NTP States (Continued) Description NTP State NTP Peer to Peer Disabled for GPS NTP800. For peer to peer peer NTP800 indicates that NTP service has no peers to synchronize to and will therefore cause an alarm.
Chapter 8 Maintenance Preventive Maintenance The NTP800 does not require scheduled preventative maintenance during normal operation. 61 of 107 900600201 Rev. A...
8.2. UPLOADING NEW FIRMWARE CHAPTER 8. MAINTENANCE Uploading New Firmware to the NTP800 See Chapter 11 on page 71, “Updating Firmware and FPGA” for the instructions on how to do this. 62 of 107 900600201 Rev. A...
Chapter 9 Frequently Asked Questions Table 9.1 below and on page 65 is a list of commonly asked questions by our cus- tomers. If the question that you wished to be answered is not in the list please contact us. Contact details are found at the end of this manual under Chapter A. Table 9.1: Frequently Asked Questions Can the NTP800 act as a stratum one server? Yes, Once the NTP800 has synchronized to a traceable GPS or Off-Air...
CHAPTER 9. FREQUENTLY ASKED QUESTIONS Table 9.1: Frequently Asked Questions (Continued) What packet types will the NTP800 respond to? ARP requests - to find Ethernet addresses given the TCP/IP address. ICMP echo requests - to allow ‘pings’ of the NTP server. UDP connections to port 123 –...
Page 77
CHAPTER 9. FREQUENTLY ASKED QUESTIONS Table 9.1: Frequently Asked Questions (Continued) How many Clients may I connect to one NTP800 Time Server? The NTP800 can handle up to 512 packets per second, which equates to a theoretical 512 x 64 (32,000+) clients assuming standard NTP operation.
Chapter 10 Troubleshooting The NTP800 is capable of alarm and status reporting. These alarms are listed in Table 10.1 on page 69 together with likely causes, and potential solutions. 67 of 107 900600201 Rev. A...
10.1. STATUS LED MEANINGS CHAPTER 10. TROUBLESHOOTING 10.1 Status LED Meanings POWER LED on PSUs STATUS – On TIME VALID Unit has obtained time from a time source since power on and holdover has not expired Flashing = Unit time invalid but advancing with 10 MHz input = Unit has not obtained time from a time source since power on GNSS = GNSS receiver PPS and time data both present...
CHAPTER 10. TROUBLESHOOTING 10.2. TROUBLESHOOTING GUIDE 10.2 Faults/Troubleshooting Guide Table 10.1: Faults/Troubleshooting Guide Cause Solution Fault The NTP800 does The NTP800 does Unsure that the NTP800 is respond not have power connected to power (on both the network and no power supplies if necessary), lamps illumi-...
Chapter 11 Updating Firmware and FPGA The file for system update and a checksum will be supplied by Brandywine. At this point it is possible to set up an ftp-server onto which the update file is placed, and retrieve from, or secure copy (scp) the provided file to the unit under Brandywine’s instruction.
CHAPTER 11. UPDATING FIRMWARE AND FPGA Figure 11.1: Firmware Update Click ‘Update Firmware’ and wait, for up to 4 minutes. DO NOT TURN THE POWER OFF DURING THIS TIME. An outline of the actions that have taken place is given at the end of the process. 72 of 107 900600201 Rev.
Appendix A Support Information All Brandywine Communications and Time & Frequency Solutions products come with a three-year warranty. If the unit is still exhibiting problems not covered by the above troubleshooting guide, contact us for technical support at support@brandywinecomm.com or call us at +1 (714) 755-1050.
Appendix B Understanding the Network Time Protocol Why use the Network Time Protocol Accurate Time has always been an important issue, especially in today’s world where computer systems are required to precisely time stamp events and occurrences. How- ever, computers are notorious for poor time keeping because they use a basic watch crystal as their internal timebase.
Page 88
B.2. UNDERSTANDING NTP APPENDIX B. NETWORK TIME PROTOCOL Understanding NTP The client computer obtains the NTP protocol by requesting a NTP packet from the NTP Server. The Software that requests the packet handles reception, maintenance and distribution of the time on the computers where it is installed. All Time & Frequency Solutions NTP Time Servers are supplied, with client software as standard for a range of operating systems &...
Page 89
APPENDIX B. NETWORK TIME PROTOCOL B.3. NTP HIERARCHY NTP Hierarchical Structure NTP supports a hierarchical structure as shown in Figure B.2 to ensure the avail- ability of time, allowing the user to monitor their position in the hierarchy and thus the quality of the time service available.
Page 91
Appendix C SNMP MIB Format Brandywine Communications Common MIB File --*********************************************************************-- -- BRANDYWINE COMMUNICATIONS Inc -- COMMON MIB 928600001 -- Standard MIB objects in all products. --*********************************************************************-- BRANDYWINECOMM-COMMON-MIB DEFINITIONS ::= BEGIN IMPORTS enterprises, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE FROM SNMPv2-SMI; brandywineComm MODULE-IDENTITY LAST-UPDATED "201910210000Z"...
Page 92
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT ORGANIZATION "Brandywine Communications Inc" CONTACT-INFO "support@www.brandywinecomm.com" DESCRIPTION "All objects common to Brandywine Communications products" -- Revision History REVISION "201905250000Z" DESCRIPTION "Initial release" REVISION "201910020000Z" DESCRIPTION "v1.0 Add class/project definitions" REVISION "201910210000Z"...
Page 93
APPENDIX C. SNMP MIB FORMAT C.1. BRANDYWINE COMMON MIB ntp80 (8), ptp80 (9), ptp8 (10), timeacc001 (11), ntp800 (6002), catu (6033) MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates type of unit and hence its functionality" ::= {inventory 1} partNo OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..16))
Page 94
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT SYNTAX OCTET STRING (SIZE(0..14)) MAX-ACCESS read-only STATUS current DESCRIPTION "Programmable logic (FPGA, EPLD) part number" ::= {inventory 6} phwversion OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "Programmable logic (FPGA, EPLD) version number"...
Page 95
APPENDIX C. SNMP MIB FORMAT C.1. BRANDYWINE COMMON MIB timestamp OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "time as number of secs since 1 January 1970" ::={syslogEntry 1} resolver OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "fraction of seconds, in microseconds"...
Page 96
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT function OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..31)) MAX-ACCESS read-only STATUS current DESCRIPTION "Function within module causing event" ::={syslogEntry 6} description OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..128)) MAX-ACCESS read-only STATUS current DESCRIPTION "Description of event"...
Page 97
APPENDIX C. SNMP MIB FORMAT C.1. BRANDYWINE COMMON MIB ::= {systemstatus 4} restart OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS current DESCRIPTION "Remote reset. Set to 1 to cause reset." ::= {systemstatus 7} clock OBJECT IDENTIFIER ::= {common 3} frequency OBJECT-TYPE...
Page 98
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT freqoffset OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "clock offset in ppb" ::= {clock 5} stability OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "clock stability in ppb" ::= {clock 6}...
Page 99
APPENDIX C. SNMP MIB FORMAT C.1. BRANDYWINE COMMON MIB 0x04 loaded last frame (LLF) 0x08 loaded since reset (LSR) 0x10 LSR in the last VALIDSECONDS 0x20 Synchronised since reset. 0x40 Manual time entry 0x80 Leap second pending Note not all flags are implemented in all clocks. LLF & LSR are always implemented.
Page 100
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT phase INTEGER sourcetype OBJECT-TYPE SYNTAX INTEGER noClockSource (0), gps (1), timecode (2), msf (3), dcf (4), wwvb (5), ntp (6), ptp (7), havequick (8), irig (9) MAX-ACCESS read-only STATUS current DESCRIPTION "type of synchronization source"...
Page 101
APPENDIX C. SNMP MIB FORMAT C.1. BRANDYWINE COMMON MIB MAX-ACCESS read-only STATUS current DESCRIPTION "Current time expressed as number of seconds since 1/1/1970" ::= {sourcelistEntry 4} phase OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "last phase error measurement ns"...
Page 102
C.1. BRANDYWINE COMMON MIB APPENDIX C. SNMP MIB FORMAT 90 of 107 900600201 Rev. A...
Page 103
APPENDIX C. SNMP MIB FORMAT C.2. TFS COMMON MIB Time & Frequency Solutions Common MIB File --*********************************************************************-- -- TFS Enterprise MIB -- v8.00 Additional clock objects. -- v7.00 Rationalisation of TFS mibs for all products. Initial common MIB for all products. --*********************************************************************-- TFS DEFINITIONS ::= BEGIN IMPORTS...
Page 104
C.2. TFS COMMON MIB APPENDIX C. SNMP MIB FORMAT ptp80 (9), ptp8 (10), timeacc001 (11) ACCESS read-only STATUS mandatory DESCRIPTION "Indicates type of unit and hence its functionality" ::= {common 1} modelNo OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..16)) ACCESS read-only STATUS mandatory DESCRIPTION "Model number"...
Page 105
APPENDIX C. SNMP MIB FORMAT C.2. TFS COMMON MIB lastevent OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Last event ID" ::= {systemstatus 2} trapmask OBJECT-TYPE SYNTAX INTEGER (0..63) ACCESS read-write STATUS mandatory DESCRIPTION "This is a bit-mask representing the severity levels that cause a trap.
Page 106
C.2. TFS COMMON MIB APPENDIX C. SNMP MIB FORMAT SyslogEntry ::= SEQUENCE { timestamp INTEGER, resolver INTEGER, eventid INTEGER, severity INTEGER, module OCTET STRING (SIZE(0..31)), function OCTET STRING (SIZE(0..31)), description OCTET STRING (SIZE(0..128)) timestamp OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "time as number of secs since 1 January 1970"...
Page 107
APPENDIX C. SNMP MIB FORMAT C.2. TFS COMMON MIB DESCRIPTION "Event type" ::={syslogEntry 4} module OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..31)) ACCESS read-only STATUS mandatory DESCRIPTION "Module causing event" ::={syslogEntry 5} function OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..31)) ACCESS read-only STATUS mandatory DESCRIPTION "Function within modules causing event"...
Page 108
C.2. TFS COMMON MIB APPENDIX C. SNMP MIB FORMAT ::= {clock 2} jitter OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "clock jitter in ns" ::= {clock 3} dispersion OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "clock dispersion, averaged error, in ns" ::= {clock 4} freqoffset OBJECT-TYPE SYNTAX INTEGER...
Page 109
APPENDIX C. SNMP MIB FORMAT C.2. TFS COMMON MIB DESCRIPTION "Oscillator type description" ::= {clock 8} clockState OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Clock status bit flags: 0x01 valid pps 0x02 valid data 0x04 loaded last frame (LLF) 0x08 loaded since reset (LSR) 0x10 LSR in the last VALIDSECONDS 0x20 Synchronised since reset.
Page 110
C.2. TFS COMMON MIB APPENDIX C. SNMP MIB FORMAT ACCESS read-only STATUS mandatory DESCRIPTION "Last lock time expressed as number of seconds since 1/1/1970" ::= {source 2} currenttime OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Current time expressed as number of seconds since 1/1/1970" ::= {source 3} modules OBJECT IDENTIFIER ::= {tfs 8} alerts OBJECT IDENTIFIER ::= {tfs 99}...
Page 111
APPENDIX C. SNMP MIB FORMAT C.2. TFS COMMON MIB DESCRIPTION "System log event trap" ::= 8 99 of 107 900600201 Rev. A...
Page 113
Appendix D TFS Message4 Format Definition Each message is 22 bytes long and the format is defined in Table D.1 below. Table D.1: TFS Message4 Format Definition Byte Definition ASCII ‘T’ ASCII TENS OF HOURS ASCII UNITS OF HOURS ASCII ‘:’ ASCII TENS OF MINUTES ASCII UNITS OF MINUTES ASCII ‘:’...
APPENDIX D. TFS MESSAGE4 FORMAT DEFINITION Table D.1: TFS Message4 Format Definition (Continued) Byte Definition ASCII UNITS OF YEAR ASCII DAY OF WEEK(‘0’ = SUN) HEX Checksum: Longitudinal Redundancy Check bytes 1-20 (XOR data) HEX Status ASCII Carriage Return STATUS: 0000abcd (a-d = 0 or 1) when 1, a = Time loaded since reset, b = Time loaded last minute, c = Leap year, d = Daylight Saving time 102 of 107 900600201 Rev.
Page 115
Front Panel Drawing Figure D.1 below shows the front panel of the NTP800 Figure D.1: Front Panel Drawing 103 of 107 900600201 Rev. A...
Page 117
Rear Panel Drawing Figure D.2 below shows the rear panel of the NTP800 Figure D.2: Rear Panel Drawing 105 of 107 900600201 Rev. A...
Page 119
Parts List 107 of 107 900600201 Rev. A...
Need help?
Do you have a question about the NTP-800 and is the answer not in the manual?
Questions and answers