Ninja Precision Timing Module
Free Lifetime Technical Support
We support our products for as long as you own them with FREE technical support by phone or email and free software upgrades as they become available. No maintenance contract required.
Product Status
Introduction:
Status: New
Last Software Update: None
Latest Network Security Bulletin: None
Latest Field Service Bulletin: None
Leap Second Pending: None
Product Documents
User Manual
Installation Guide
White Papers
Datasheets
Frequently Asked Questions (FAQs)
I've had my unit for 1 year already, can I get an extended warranty?
As long as your unit is still under its current warranty then yes, you can purchase an extended warranty. Contact EndRun Sales for information.
My product is 12 years old and out-of-warranty. Can I get it repaired?
Yes - we will try. The problem may be that we no longer have parts for the old models. But, if we can still get the needed parts then we will repair your unit and charge for time and materials.
What is the EOL on my EndRun product?
At EndRun, End-of-Life (EOL) means end of the production life cycle. We continue to provide free technical support (by phone or email) for as long as you own an EndRun product. In fact, we are still providing free support for products that we shipped in 2001.
How are upgrades handled and what do they cost?
Software upgrades for all our products are freely available for download from our website at: www.endruntechnologies.com/support/software-upgrades.
I haven't upgraded my firmware for a long time. Can I upgrade straight to the latest version without installing subsequent versions first?
Current products (Sonoma, Meridian II, Tycho II, RTM3205) can be upgraded to the latest version of firmware straight from any older version. However, if you have modified either /etc/profile or /etc/rc.d/rc.M and your Linux Root File System (RFS) is prior to version 2.20 then please contact Support (support@endruntechnologies.com).
Legacy products (Tempus LX, Unison, Meridian, Tycho, RTM3204) can also be upgraded to the latest version of firmware straight from any older version. However, if your RFS is prior to version 2.60 then please read this.
Will GPS work inside?
Unlike CDMA, GPS will not work inside buildings. To receive GPS signals the antenna must have a view of the sky. The best location is on a roof-top with the antenna in view of a maximum amount of sky. However, our GPS products have the ability to operate in a single-satellite mode. This lets you avoid the trouble and expense of a rooftop installation by allowing you to mount the antenna in a window of your building with only a partial view of the sky.
How far can I install the antenna from the GPS receiver?
The standard antenna cable length is 50 feet. If you need more we offer antenna lengths up to 250 feet without a GPS preamplifier. If you need more than 250 feet of cable then a preamp is required. You can run an additional 250 feet of cable for every preamp installed and you can have up to 3 preamps. This will allow you to run a total of 1000 feet of cable. For more information click here.
Will my EndRun product be affected by the GPS week rollover event in April 2019?
All EndRun GPS-synchronized products with up-to-date firmware will not be affected by the April 7, 2019 rollover event. For more information, please refer to Field Service Bulletin 180427.
Do I set my calibration delay to positive or negative to compensate for the antenna cable?
The answer is positive because there is a delay between the antenna and the receiver.
Think about it like this: The antenna receives the time data x nanoseconds before the receiver. Therefore, the receiver is behind the antenna by x nanoseconds. By entering a positive delay, the clock will be advanced x nanoseconds to compensate.
I don't have roof-top access for a GPS antenna. What do I do?
You have two choices:
1. Mount your GPS antenna in a window. Our GPS products have the ability to operate in a single-satellite mode which allows you to mount the antenna in a window of your building with only a partial view of the sky. See this Window-Mount Installation Guide for details.
2. Purchase a CDMA-synchronized product which works very well inside buildings (assuming your area has CDMA coverage).
What is NTP Stratum?
Stratum is a term that means different things depending on the context. In the world of NTP, stratum is defined in RFC 1305. NTP uses a hierarchical structure in which Stratum 0 is the reference clock, linked via a time signal, to a reliable source of UTC. Stratum 1 is the time server with a direct link to the reference clock. Stratum 2 is a client that receives time over a network connection from a Stratum 1 clock. Stratum 3 is a client that receives time from a Stratum 2 clock. And so on, up to Stratum 15. For more details on strata in the NTP world, click here.
How accurate is NTP?
Over WANs (Wide Area Networks), up to 100 milliseconds is typical. It depends on how far away the public time server is, or more specifically, how many hops between you and the server. Within a LAN (Local Area Network) using a dedicated NTP Time Server, 0.5 to 2 milliseconds is typical. The internal accuracy of the CDMA Network Time Server is on the order of 10 microseconds. It can easily keep all clients on a LAN synchronized to typically within 0.5 to 2 milliseconds.
Where can I get NTP client software?
Client software is widely available as freeware and shareware. Setting up an NTP or SNTP client is relatively simple once you have installed the software on your workstation and communicated with the time server over the network. For a list of NTP client software click here.
How long will the NTP Server deliver Stratum 1 performance if the signal is lost?
Exclusive EndRun oscillator-control algorithms provide extended Stratum 1 holdover performance when the unit is not locked to the synchronization signal (GPS or CDMA). Typical NTP Stratum 1 holdover periods are:
24 hours - TCXO (standard)
35 days - OCXO (upgrade)
140 days - Rubidium (upgrade)
Why do I need a time server?
When two or more computers are involved, accurate time keeping is difficult, especially if they are not in the same physical location. A dedicated time server inside your network perimeter is the most accurate, reliable and secure way to ensure accurate timekeeping for all computers on your network. Accurate timekeeping is necessary to support eBusiness and other applications such as Stock Trades, Logs, B2B Transactions, File Operations, Packet Time Stamps, Software Configuration Management, Database Accuracy, Telecommunication Call Billing, etc. For a more detailed response to this question click here.
Why not use the time servers available over the Internet?
There are many public time servers available over the Internet. Access to these public time servers is free of charge. While public time servers are certainly less costly - accurate, reliable and secure time is best provided by a dedicated time server that resides under your control inside your network security perimeter. Using public time servers available over the Internet is not recommended for the following reasons:
1. Setting up your firewall to accept NTP packets (which is based on UDP/IP) introduces a security risk that many Network Administrators are not willing to take.
2. Time accuracy degrades because of indeterminate network latency, up to 100 milliseconds is typical.
Is there a command to tell me the Stratum level of my NTP Server?
Yes. For current models (Sonoma, Meridian II, Tycho II, RTM3205) use Linux command:
ntpq -c sysinfo
For legacy models use Linux command:
ntpdc -c sysinfo
How many clients can a time server handle?
For a detailed answer to this question click here.
Is support for NTS4NTP on your product roadmap?
Yes. NTS4NTP is in the draft standard level and when released we expect it will be integrated into the NTP distribution. The Time Servers are periodically upgraded with the latest distribution so when NTS4NTP is supported, then it will also be supported in our products. The standards process is lengthy so there is no telling when this capability will be in the NTP distribution.
Are the EndRun NTP Servers compliant with STIG ID: NET0813, Rule ID: SV-15326r5?
EndRun NTP Servers are compliant with STIG ID: NET0813, Rule ID: SV-15326r5, Vuln ID: V-14671. The time servers support a FIPS-approved message authentication code and NIST-approved HMAC algorithms.
How do I restart the NTP daemon without rebooting?
For our third generation units such as Sonoma, Meridian II, Tycho II, Ninja, RTM3205 and e-Series Distribution, run the command:
/etc/rc.d/rc.ntpd restart
For older models, the only way to restart the daemon is to reboot.
When I log into my unit from the CLI, a time string displays that does not match the current UTC. What is wrong?
This string:
Sonoma_D12 GPS 6010-0065-000 v 2.40 - Tue Sep 19 02:19:38 UTC 2017
which is displayed immediately after login simply means that firmware 6010-0065-000 version 2.40 was released on Tuesday September 16, 2017 at 02:19:38 UTC. It has nothing to do with current UTC.
Do I have root access to the Linux file system via the command line interface?
Yes.
Do I need to be familiar with Linux in order to use your equipment?
No. To see a list of EndRun's product commands that you can easily use, type:
help
To get help on a particular command type "help EndRun-command-name". For example:
help gpsstat
This will show you details regarding the gpsstat command.
How can the default prompt be changed?
Edit the file /etc/profile and modify the definition of PS1. After making the change, copy the file to the non-volatile area:
cp /etc/profile /boot/etc
Our security guys did a scan on the EndRun unit and found a few vulnerabilities. Is there going to be a firmware update soon to address this?
Serious vulnerabilities that cannot be mitigated with a reasonable workaround will be addressed with a new firmware update as soon as possible. For remaining vulnerabilities, please see Network Security Bulletins for mitigation steps.
Also, we recommend reading this: Best Practices to Secure Your Time Server. Taking the steps outlined in this paper will eliminate most, if not all, vulnerabilities. It was written for the Sonoma Time Servers but the same general steps apply to our other Linux-based products.
Is there a way to set a timeout for ssh sessions?
Yes. Follow these instructions:
1. Open the sshd_config file for editing.
For current models (Sonoma, Meridian II, Tycho II, RTM3205) open this file:
/etc/ssh/sshd_config
For legacy models open this file:
/etc/sshd_config
2. Uncomment and edit the lines in sshd_config with ClientAliveInterval and ClientAliveCountMax settings as follows:
ClientAliveInterval <session timeout in seconds>
ClientAliveCountMax 0
3. Don't forget to make the modified file persistent, by copying it to FLASH:
For current models (Sonoma, Meridian II, Tycho II, RTM3205):
cp -p /etc/ssh/sshd_config /boot/etc/ssh
For legacy models:
cp -p /etc/sshd_config /boot/etc/
4. Reboot the unit using this command:
reboot
I am using WinSCP to upload files for upgrading and the upgrade keeps failing. What do I do?
If you are uploading via SSH, do not use WinSCP! WinSCP does not work well with a raw flash partition. We have had great success using PuTTY's pscp utility, which is executed from the Windows command line and uses the same syntax as the Linux-based scp utility. You can download pscp from putty.org.
How can I serve time on two different networks?
You will need to configure a gateway for both the Ethernet ports. The user manual indicates that only one port can be configured with a default gateway (using the front panel or netconfig). However, with advanced routing you can configure a gateway for both ports (eth0 and eth1). You must add commands to set up static routes in the /etc/rc.d/rc.M startup script. There is an easily spotted comment in the rc.M file showing where to add the commands. For more information, read this Product Note or contact EndRun Technical Support.
Are any products manufactured by EndRun affected by the CVE-2021-44228 Apache Log4j vulnerability?
No. Products manufactured by Endrun Technologies are not affected because none of them include any version of Apache Log4j.
How are restrictions for subnet access with SSH/SNMP and telnet achieved? For example, how do I set restriction for access to 192.168.1.0/24 subnet?
For our third-generation units such as Sonoma, Meridian II, Tycho II, Ninja, RTM3205 and e-Series Distribution Chassis run the command below to invoke interactive script:
accessconfig
Then, when prompted enter a hostname, host address or range of host addresses to be given telnet/ssh/snmp access (name, IP address or IP address range, 0 to quit). You enter:
192.168.1.0/255.255.255.0
