Meinberg LANTIME M300 User manual

MANUAL
LANTIME M300 TCR
Network Time Server
19th April 2011
Meinberg Radio Clocks GmbH & Co. KG

Table of Contents
1 Impressum 1
2 Quick Start 2
3 The Modular System LANTIME 3
3.1 SupportedNetworkServices...................................... 4
3.2 AdditionalFeatures .......................................... 4
3.3 UserInterface ............................................. 4
3.4 Options ................................................ 5
3.5 Why to use a Network Time Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 IRIG receiver TCR511 6
4.1 AbstractofTimeCode ........................................ 6
4.2 DescriptionofIRIG-Codes....................................... 7
4.3 IRIGStandardFormat......................................... 8
4.4 AFNORStandardFormat....................................... 9
5 Network Time Protocol (NTP) 10
5.1 NTPTarget .............................................. 10
5.2 NTP-ClientInstallation ........................................ 10
6 Booting the Single Board Computer 12
7 Configuration User Interface 13
7.1 Introduction: Conguration LANTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.2 RootMenu............................................... 14
7.3 Menü:ReferenceTime ........................................ 16
7.3.1 Menu: Reference Clock Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.3.2 Menu:ReceiverState..................................... 16
7.3.3 MenueSetupTCR ...................................... 17
7.3.4 MenuOsetfromUTC.................................... 17
7.3.5 MenuIRIGCode ....................................... 18
7.3.6 MenuSimulationMode.................................... 18
7.3.7 Menu Initial Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
7.4 Menu:TimeService.......................................... 19
7.4.1 Menu:externalNTP ..................................... 19
7.4.2 Menu: Stratum of local clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.4.3 Menu:RestartNTP...................................... 19
7.5 Menu:TIMECODEIRIG....................................... 20
7.6 Menu:Network ............................................ 21
7.6.1 Setup Global Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.6.2 Setup Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.6.3 Setup Network Ipv4 Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.6.4 Menu: Setup Ipv6 Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
7.6.5 Menu:LinkMode....................................... 23
7.6.6 Menu: Setup Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
7.7 Menu:System............................................. 24
7.7.1 Settimezone ......................................... 24
8 The graphical user interfaces 26
9 The WEB Interface 27
9.1 Conguration:MainMenu ...................................... 27
0

9.2 Conguration:Ethernet........................................ 29
9.2.1 SYSLOGServer........................................ 29
9.3 Network interface specic conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.3.1 IPv4 addresses and DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
9.3.2 IPv6 addresses and autoconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.3.3 High Availability Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.3.4 Additional Network Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
9.4 Conguration:Notication ...................................... 33
9.4.1 Alarmevents.......................................... 33
9.4.2 E-mailmessages........................................ 34
9.4.3 WindowsPopupMessages .................................. 35
9.4.4 SNMP-TRAPmessages.................................... 35
9.4.5 VP100/NET wall mount display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.4.6 User dened Alarm scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
9.4.7 NTPClientMonitoring .................................... 35
9.4.8 Alarmmessages........................................ 36
9.5 Conguration:Security ........................................ 37
9.5.1 Password............................................ 38
9.5.2 HTTPAccessControl..................................... 38
9.5.3 SSHSecureShellLogin.................................... 38
9.5.4 Generate SSL Certicate for HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.5.5 NTPkeysandcerticates................................... 40
9.5.6 SNMPParameter ....................................... 40
9.6 Conguration:NTP.......................................... 41
9.6.1 NTPAuthentication...................................... 43
9.6.2 NTPAUTOKEY ....................................... 44
9.7 Conguration:Local.......................................... 47
9.7.1 Administrative functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.7.2 UserManagement....................................... 48
9.7.3 Administrative Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
9.7.4 SoftwareUpdate........................................ 50
9.7.5 Automatic conguration check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.7.6 Get Diagnostics Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.7.7 Webinterfacelanguage.................................... 51
9.8 Conguration:Statistics........................................ 52
9.8.1 StatisticalInformation..................................... 52
9.9 Conguration:Manual ........................................ 54
9.10Conguration:PTP.......................................... 55
9.10.1 PTPv2 - Global Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.10.2 PTP Network Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
9.10.3PTPStateFiles........................................ 58
10 The Command Line Interface 59
10.1CLIEthernet.............................................. 60
10.2CLINotication............................................ 62
10.3CLISecurity.............................................. 64
10.4CLINTPParameter.......................................... 66
10.4.1CLINTPAuthentication ................................... 67
10.5CLILocal ............................................... 67
11 SNMP Support 70
11.1CongurationoverSNMP....................................... 71
11.1.1 Examples for the usage of the SNMP conguration features . . . . . . . . . . . . . . . . 71
11.1.2 Further conguration possibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.1.3 Send special timeserver commands with SNMP . . . . . . . . . . . . . . . . . . . . . . . 72
11.1.4 Conguration of the timeserver with SNMP: Reference . . . . . . . . . . . . . . . . . . . 74
11.2SNMPTraps.............................................. 78
11.2.1SNMPTrapReference .................................... 79
12 Attachment: Technical Information 80
12.1 Skilled/Service-Personnel only: Replacing the Lithium Battery . . . . . . . . . . . . . . . . . . . 80

Page 0
12.2 Technical Specications M600/300 Multipac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
12.3 Safety instructions for building-in equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.3.1CE-Label............................................ 81
12.4RearPanelConnectors ........................................ 82
12.5TERMINAL(Console)......................................... 83
12.6ErrorRelay............................................... 84
12.6.1 Technical Specication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
12.7 Technical Specications TCR511 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
12.8SignalDescriptionTCR5xx ...................................... 86
12.9 Rear Connector Pin Assignments TCR511 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
12.10Technical Specications LAN CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
12.10.1Rear Connector Pin Assignments LAN CPU . . . . . . . . . . . . . . . . . . . . . . . . . 89
12.10.2VGA, Keyboard Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . 89
12.11TimeStrings.............................................. 90
12.11.1Format of the Meinberg Standard Time String . . . . . . . . . . . . . . . . . . . . . . . . 90
12.11.2Format of the Meinberg Capture String . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
12.11.3Format of the SAT Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
12.11.4Format of the Uni Erlangen String (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . 93
12.11.5Format of the NMEA 0183 String (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . 95
12.11.6Format of the NMEA 0183 String (GGA) . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.11.7Format of the ABB SPA Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
12.11.8Format of the Computime Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
12.11.9Format of the RACAL standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . 99
12.11.10Format of the SYSPLEX-1 Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
12.12Manual VP100/NET Display conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
12.13GlobalCongurationFile .......................................102
12.14GlobalOptionFile...........................................104
12.15Thirdpartysoftware..........................................104
12.15.1Operating System GNU/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.15.2Samba.............................................104
12.15.3Network Time Protocol Version 4 (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . 104
12.15.4mini_httpd ..........................................105
12.15.5GNU General Public License (GPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
12.16USBStick ...............................................110
12.16.1Menu Backup Conguration to USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . 110
12.16.2Menu Write Diagnostic File to USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . 110
12.16.3Keypadlocking ........................................110
12.16.4Menu Restore Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
12.17Reference ...............................................112
0 Date: 19th April 2011 LANTIME M300 TCR

Page 1
1 Impressum
Meinberg Radio Clocks GmbH & Co. KG
Lange Wand 9, 31812 Bad Pyrmont - Germany
Phone: + 49 (0) 52 81 / 93 09 - 0
Fax: + 49 (0) 52 81 / 93 09 - 30
Internet: http://www.meinberg.de
Mail: [e-mail]
Date: 2010-06-23
LANTIME M300 TCR Date: 19th April 2011 1

Page 2 2 Quick Start
2 Quick Start
When booting the system the following message will be displayed while dots will be counted up in the lower line:.
MEINBERG TIMESERVER please wait...
.......
Main Menu will be displayed with some important status informations after booting has nished:
TCR: no data available Wed, 18.05.2009
NTP: Not Sync UTC 10:03:30
TCR: NORMAL OPERATION Wed, 18.05.2009
NTP: Not Sync UTC 10:03:30
If the TCR receiver remains asynchronous (Ref.Time LED is still red after 1 minute) the selected IRIG code and
the cable (Input Impedance) are to check. Press buttons " ↓, ok, ↓, ok, ↓, ok " from main menu to enter SETUP
TCR PARAMETERS. Then press OK to display the current selected IRIG-CODE:
SETUP: TCR PARAMETERS
IRIG Code: B122/B123
For rst time installation enter TCP/IP address, netmask and default gateway. To get an overview of the current
conguration press F2 from main menu. Press F2 again to enter SETUP conguration page. Please ask your
administrator for proper TCP/IP conguration:
OK
-> Ipv4 Parameter <- Link Mode
Ipv6 Parameter
Global Cfg. Services
-> Interfaces <-
Then press 3 times the OK button to change to IPV4 ETH0 conguration page to enter the IP address, netmask
and the default gateway:
SETUP: Ipv4 LAN Parameter ETH0
Ipv4 ADDRESS: 192.168.10.200
After this all further settings can be done via network interface, either by using a WEB browser or a Telnet/SSH
Session.
Default user: root
Default password: timeserver
2 Date: 19th April 2011 LANTIME M300 TCR

Page 3
3 The Modular System LANTIME
M300 is a set of equipment composed of a reference clock (e.g.: GPS satellite controlled clock or a Time Code
Receiver TCR), a single-board computer SBC LX800 500 MHz with integrated network card, and a power supply
unit, all installed in a metal desktop case and ready to operate. The interfaces provided by LANTIME are acces-
sible via connectors in the rear panel of the case. Details of the components are described below.
OK
ESC
Time Service
Ref. Time
Network
Alarm
Terminal
USB
5
9
1
6
GPS: NORMAL OPERATION
NTP: Offset PPS: -4µs UTC 12: 00 : 00
Mon , dd.mm.yyyy
F1
F2 LANTIME M300
LANTIME M300
ENGLISH
1. LC Display
2. Function buttons: 4-way navigation
Button; F1, F2, OK, ESC
3. Status LEDs: Ref. Time, Time Service,
Network, Alarm
4. Terminal port, RS232 Time String output
5. USB connector
6. 19” Mounting Rack
DEUTSCH
1. LC - Display
2. Funktionstasten: 4 - Richtungen;
F1, F2, OK, ESC
3. Status LEDs: Ref. Time, Time Service,
Network, Alarm
4. Terminal port, RS232 Zeitstring Ausgang
5. USB Anschluss
6. Haltewinkel für 19” Rackmontage
1 2 3 4 5 6
Error
mod.
CO NO NC
100M 10M 100M 10M
ETH0 ETH2
ETH1 ETH3
PPS Out
10MHz Out
6 5 4 3 2 1
DEUTSCH
. Error: Störmelderelais Ausgang
3. IRIG Eingang - moduliert, DCLS
4. Sekunden Impuls Ausgang, 10MHz Ausgang (TTL)
5. LNE Optional
6. Netzwerk Anschlüsse ETH0, ETH1, 10/100 Mbit Rj45
1. Stromversorgungseingang
2
ENGLISH
. Error relay output3
3. IRIG Input (modulated, DC Level Shift)
4. Pulse Per Second (PPS) output, 10MHz (TTL) output
5. Option: LNE - additional network interfaces
6. Network interfaces ETH0, ETH1, 10/100 Mbit Rj45
1. Power Supply (AC/DC)
2
Time Code in
DCLS
The implemented NTPD distributes the reference time from the receiver cyclic in the network. Information on
the NTPD is monitored on the LC display or can be inquired via the network.
The installation of LANTIME is very easy for the system/network administrator. The network address, the
netmask and the default gateway have to be congured from the front panel of M300. The network address or
the equivalent name of LANTIME has to be shown to all NTP clients in the TCP/IP network.
As well as NTP the Linux system also supports a number of further network protocols: HTTP(S), FTP, SSH and
Telnet. Because of this remote conguration or status requests can come from any WEB browser. This access via
the network can be deactivated. Changes in the receiver status, errors or other important events are logged either
on the local Linux system or on an external SYSLOG-Server. In addition messages can be sent to a data center
via SNMP traps or automatically generated e-mails where they can be recorded. Furthermore all alarm messages
can be displayed by the large display VP100/20/NET that is accessed via network connection. In order to avoid
a service interruption several LANTIME NTP servers can be installed in the same network to obtain redundancy.
LANTIME M300 TCR Date: 19th April 2011 3

Page 4 3 The Modular System LANTIME
3.1 Supported Network Services
The following network services are provided via RJ45 10/100Base-T Ethernet (Auto sensing):
- NTP v2, v3, v4
- NTP broadcast mode
- NTP multicast
- NTP symmetric keys
- NTP Autokey
- Simple Network Time Protocol (SNTP)
- TIME
- SNMP v1,2,3 with extended SNMP-Agent and SNMP-Traps
for NTP and reference clock status
- DHCP Client
- NFS
- TELNET
- FTP
- HTTP
- HTTPS with Openssl2
- SSH2 Secure Shell Login
- Alarm messages via e-mail
- IPv6 3 global IPv6 addresses congurable
Autoconf Feature to be disabled
supported network services: NTP, HTTP, HTTPS, SNMP, SSH
- Windows net time via NETBIOS
- Winpopup (Window Mail)
3.2 Additional Features
• external NTP timeserver
• free conguration of NTP: thereby MD5 authentication and access control via address & mask restriction
• extended menu guidance for conguration and monitoring via Telnet, SSH or serial terminal interface
• optional up to 3 RJ45/10/100 MBit Ethernet interfaces
• extended HTTP statistic support with long-term graphic and access statistic to NTP
• alarm messages can be displayed on external large display VP100/20/NET
• USB memory stick slot for extended functionality: software update, transfer of secure certicates, log les
and congurations, keypad locking
3.3 User Interface
• Terminal connection via serial interface, status LED
• Web browser interface with graphical statistic of the one-day cycle osets
• Telnet or Secure Shell Login for password protected operation of the Linux operating system
• FTP access for updating the operating system and downloading log les
• Simple Network Management Protocol for automatically SNMP-Traps in case of alarm
• SYSLOG messages can be passed to dierent computers
• Congurable e-mail notication
• Simulation of a synchronous radio clock in order to operate without antenna
4 Date: 19th April 2011 LANTIME M300 TCR

3.4 Options Page 5
3.4 Options
• Additional Ethernet RJ45 connectors available (eight in 3U housing, four in 1U housing and eight additional
connectors in HS - XL railmount housing)
• Frequency and pulse outputs via BNC connectors (e.g. 10 MHz, 2.048 MHz, PPS)
• Higher free running accuracy with optional oscillators (OCXO)
• IRIG-B outputs
• ANZ14NET or VP100/20/NET as display connected via network
3.5 Why to use a Network Time Server?
In principle it is possible to synchronize your computers with time servers on the internet. However, a lot of our
customers rely on their own time server in their network environment for security and/or maintainability reasons.
• Particularly in the case of our LANTIME you or a responsible person can be notied by mail or SNMP trap
if there is a malfunction in your time synchronization.
• The clients on the network do not depend on an active internet connection.
• The clients on the network do not depend on the availability of an external time server.
• A test of other freely available time servers reported that many NTP servers distributed a signicantly
wrong time, although they were classied as stratum-1 time servers. This is the responsibility of the server's
administrators.
• If an internet connection is working properly then NTP can determine and account for the packet transmis-
sion delays quite reliable. However, if the internet connection is at its capacity limit, time synchronization
can be signicantly degraded due to high dispersion in packet transmission delays. Reasons for this may be
hacker attacks, which must not address your own network, or new viruses causing a huge ood of emails,
like it has already happened in the past.
In the United States the U.S. Naval Observatory (USNO) has a similar function to spread the legal time as the
PTB in Germany, and also operates publicly available NTP servers for a long time. Those NTP servers are more
and more constrained by "bad" clients, which makes the future of the public service questionable. There are
already precautions to limit the aect of such clients. Dave Mills, the originator of NTP, cooperates with the
USNO and has already adverted this in the NTP news group.
The topics outlined above should provide some arguments to install an own time server, if an accurate time
is a requirement for the reliable operation of a local network.
LANTIME M300 TCR Date: 19th April 2011 5

Page 6 4 IRIG receiver TCR511
4 IRIG receiver TCR511
The Board TCR511 was designed for the decoding of unmodulated and modulated IRIG- and AFNOR-Timecodes.
Modulated codes transport the time information by modulating a sinusoidal carrier signals amplitude whereas un-
modulated signals employ a pulse width modulated DC signal.
The receivers automatic gain control allows the reception of signals within a range from abt. 600mVpp up
to 8Vpp. The potential free input can be jumper selectable terminated in either 50 Ohm, 600 Ohm or 5 kOhm.
Modulated codes are applied to the board via an on board SMB connector.
4.1 Abstract of Time Code
The transmission of coded timing signals began to take on widespread importance in the early 1950s. Especially
the US missile and space programs were the forces behind the development of these time codes, which were used
for the correlation of data. The denition of time code formats was completely arbitrary and left to the individual
ideas of each design engineer. Hundreds of dierent time codes were formed, some of which were standardized
by the "Inter Range Instrumentation Group" (IRIG) in the early 60s.
Except these "IRIG Time Codes", other formats like NASA36, XR3 or 2137 are still in use. The board TCR
however generates the IRIG-B, AFNOR NFS 87-500 code as well as IEEE1344 code which is an IRIG coded
extended by information for time zone, leap second and date. Other formats may be available on request.
6 Date: 19th April 2011 LANTIME M300 TCR

4.2 Description of IRIG-Codes Page 7
4.2 Description of IRIG-Codes
The specication of individual IRIG time code formats is dened in IRIG Standard 200-04. They are described by
an alphabetical character followed by a three-digit number sequence. The following identication is taken from
the IRIG Standard 200-98 (only the codes relevant to TCR5xx are listed):
character bit rate designation A 1000 pps
B 100 pps
1st digit form designation 0 DC Level Shift width coded
1 sine wave carrier amplitude modulated
2nd digit carrier resolution 0 no carrier (DC Level Shift)
1 100 Hz, 10 msec resolution
2 1 kHz, 1 msec resolution
3 10 kHz, 100 µ sec resolution
3rd digit coded expressions 0 BCD, CF, SBS
1 BCD, CF
2 BCD
3 BCD, SBS

BCD: time of year, BCD-coded
CF: Control-Functions (user dened)
SBS: seconds of day since midnight (binary)
LANTIME M300 TCR Date: 19th April 2011 7

Page 8 4 IRIG receiver TCR511
4.3 IRIG Standard Format
8 Date: 19th April 2011 LANTIME M300 TCR

4.4 AFNOR Standard Format Page 9
4.4 AFNOR Standard Format
LANTIME M300 TCR Date: 19th April 2011 9

Page 10 5 Network Time Protocol (NTP)
5 Network Time Protocol (NTP)
NTP is a common method for the synchronization of hardware clocks in local and global networks. The basic
concept, version 1 [Mills88], was published in 1988 as RFC (Request For Comments). Experiences acquired from
its practical use on the Internet was followed by version 2 [Mills89]. The NTP software package is an implemen-
tation of the actual version 3 [Mills90], based on the specication RFC-1305 from 1990 (directory doc/NOTES).
Permission to use, copy, modify and distribute this software for any purpose and without fee is hereby granted
(read File COPYRIGHT).
NTP operates in a way that is basically dierent from that of most other timing protocols. NTP does not
synchronize all connected clocks; instead it forms a hierarchy of timeservers and clients. Each level in this hier-
archy is called a stratum, and Stratum 1 is the highest level. Timeservers at this level synchronize themselves
by means of a reference time source such as a radio controlled clock, GPS receiver, or modem time distribution.
Stratum 1 Servers distribute their time to several clients in the network which are called Stratum 2.
Highly precise synchronization is feasible because of the several time references. Every computer synchronizes
itself with up to three valued time sources. NTP enables the comparison of the hardware times and the adjustment
of the internal clock. A time precision of 128 ms, and often better than 1 ms, is possible.
5.1 NTP Target
The NTP software package was tested on dierent UNIX systems. Many UNIX systems have an NTP client pre-
installed. Only some basic congurations need to be done (/etc/ntp.conf). NTP clients as freeware or shareware
are also available for most other operating systems like Windows 7/Vista/XP/NT/2000/98/95/3x, OS2 or MAC.
The following WEB site is recommended to get the latest version of NTP:
http://www.eecis.udel.edu/ ntp/
You can nd more information on our web page at: http://www.meinberg.de/english/sw/ntp.htm
5.2 NTP-Client Installation
The following example shows the installation of a NTP client under UNIX. First make sure that there is no NTP
installed on your computer because many UNIX operating systems include NTP already.
The shipped source code of the NTP daemon has to be compiled on the target system. Using the enclosed
script le congures the compilation of the NTP daemon and all tools.
congure
All necessary information from the system will be collected and the corresponding make les will be generated in
the subdirectories.
After that the NTP daemon and all needed utilities will be generated. Therefore type:
make
While compiling the NTP daemon several warnings may appear. These warnings are mostly unimportant. In case
of problems during the compilation read the system dependent notes in the subdirectory `html'.
Afterwards the generated programs and tools have to be moved in the corresponding directories. Therefore type:
make install
The time adjustment can occur in dierent ways. Either the system time can be set once by using the tool "ntp-
date lantime" or the NTPD daemon is started. In the rst case it is recommended to set the time automatically
with "cron" or once when booting the system. The second case is described below.
10 Date: 19th April 2011 LANTIME M300 TCR

5.2 NTP-Client Installation Page 11
First a le named /etc/ntp.conf has to be generated with an editor. Adapting the le to Meinberg LANTIME it
should contain the following:
# Example for /etc/ntp.conf for Meinberg LANTIME
server 127.127.1.0 # local clock
server 172.16.3.35 # TCPIP address of LANTIME
# optional: Driftle
# driftle /etc/ntp.drift
# optional: activate all messages in syslogle
# logcong =all
The NTP daemon is started with 'ntpd' or, using 'rc.local', while booting the system. Status messages during
operation are saved in /var/adm/messages and /var/adm/syslog (corresponding to the syslog conguration).
e.g.: tail /var/log/messages
Shows the last lines from the le messages . The status messages can also be redirected in a log le by using the
following option:
ntpd -llogle
The command 'ntpq' in the directory ntpq requests the actual status of the NTP daemon (see also doc/ntpq.8).
e.g.: ntpq/ntpq
An interpreter appears; Type "?" for a list of all available commands. The command 'peer' is used to list all
active reference clocks:
         

         
         
with the following meaning:
- remote: list of all valid time servers (ntp.conf)
- red: reference number
- st: actual stratum value (hierarchy level)
- when: last request (seconds)
- poll: period of requesting the time server (seconds)
- reach: octal notation of the successful requests, shifted left
- delay: delay of the network transmission (milliseconds)
- oset: dierence between system time and reference time
(milliseconds)
- jitter: variance of the osets (milliseconds)
Repeatedly 'peer' commands lets the user observe the accuracy of the NTP daemon. Every 64 seconds (value
of -poll) a new time string is red in from the radio clock. The NTP daemon needs approx. 3...5 minutes for
initialisation. This is indicated by a wildcard (*) on the left side of the remote name.
The NTP daemon terminates itself if the system time diers from the UTC time by more than 1024 seconds.
This often happens when the time zone is not correctly set (see also system manual "zic" or "man zic").
LANTIME M300 TCR Date: 19th April 2011 11

Page 12 6 Booting the Single Board Computer
6 Booting the Single Board Computer
The LINUX operating system is loaded from a packed le on the ash disk of the single board computer to a
RAM disk. All les of the ash disk are stored in the RAM disk after booting. Because of that it is guaranteed
that the le system is in a dened condition after restart. This boot process takes approx. two minutes. During
this time the following message appears on the display:
MEINBERG TIMESERVER please wait...
.......
After starting up the LINUX system the network function is initiated and the program for communication with
the TCR510 and the NTPD (NTP daemon) is started. After that NTPD starts synchronisation with the reference
clocks (usual the hardware clock of the single board computer and the TCR). Until synchronisation is nished the
following message is displayed:
TCR: NORMAL OPERATION Wed, 18.11.****
NTP: Not Sync MEZ 10:04:10
For the synchronization of the NTPD with the GPS it is necessary that the GPS receiver is synchronous with the
GPS time. In this case the following message is monitored on the display:
TCR: NORMAL OPERATION Wed, 18.11.****
NTP: Offset TCR: 1ms MEZ 10:04:10
The second line shows the user that the NTPD is synchronized with the GPS with an oset of -50us. Because
of the internal time of the NTP which is adjusted by a software PLL (phase locked loop) it takes a certain time
to optimise this oset. The NTPD tries to keep the oset below +-128 ms; if the oset becomes too large the
system time is set with the GPS time. Typically values for the oset are +-5 ms after the NTPD has already
synchronized.
12 Date: 19th April 2011 LANTIME M300 TCR

Page 13
7 Configuration User Interface
7.1 Introduction: Configuration LANTIME
There are several ways to congure the LANTIME parameters:
Command Line Interface (CLI) via TELNET
Command Line Interface via SSH
Command Line Interface via serial terminal in front panel
(38400/8N1/VT100)
HTTP Interface
Secure HTTP Interface (HTTPS)
Front panel LCD/VFD Interface
SNMP Management
In order to be able to congure the time server via the web interface or a telnet/SSH connection, an IP address
has to be assigned via the front panel keys and LC/VF display (for automatic assignment possibilities please refer
to: DHCP IPv4 or AUTOCONF IPv6). LANTIME variants without a display can be congured using the serial
terminal interface (labeled Term or Terminal) The termin program should be set to 38400Baud / 8N1  VT100
emulation. Once the IPv4 address, net mask and IPv4 GATEWAY have been set up or the network interface has
been automatically congured with DHCP/Autoconf, further conguration changes can be done via a network
connection:
To set up a TELNET connection the following commands are entered:
telnet 198.168.10.10 // LANTIME IP address
user: root
password: timeserver
With setup the conguration program is started.
To set up a SSH connection the following commands are entered:
ssh ro[email protected] // LANTIME IP address
password: timeserver
With setup the conguration program is started.
To set up a HTTP connection the following address is to enter in a web browser:
http://198.168.10.10 // LANTIME IP address
password: timeserver
To set up a Secure HTTP (HTTPS) connection the following address is entered in a web browser:
https://198.168.10.10 // LANTIME IP address
password: timeserver
LANTIME M300 TCR Date: 19th April 2011 13

Page 14 7 Conguration User Interface
7.2 Root Menu
The root menu is shown when the receiver has completed initialisation after powerup. With the four arrow buttons
and the buttons OK, "ESC", "F1" and "F2" the navigation and setting of parameters can be managed. Main
menu can be reached by pressing "ESC" some times. The main menu reect some of the main parameters of
the time server. First line displays the status of the Reference Clock. The text "NORMAL OPERATION" might
be replaced by "no data available", "not locked" or "telegram error". If the Time Code signal is disconnected or
not working properly, the text "no data available" is displayed instead.
TCR: NORMAL OPERATION Mon, 28.08.2006
NTP: not sync UTC 14:33:10
OK
ESC
F1
F2
Current time and date of the timeserver with the name
of the time zone (NTP uses UTC time zone) will be
monitored on the right side. If the "IGNORE LOCK"
option is enabled "Simulation Mode" will be shown.
Time Service
Ref. Time
Network
Alarm
Ref. Time
green: the reference clock (e.g. integrated TCR511) produce valid time.
red: the reference clock produce no valid time (e.g. not synchronized)
Time Service
green: NTP has been synchronized to reference clock.
red: NTP is not synchronous to reference clock or sync to local clock
Network
green: all watched network ports has been link up detected
red: at least one of the watched network ports (look at Setup Device
Parameter / Check Network Linkup) is not connected
Alarm
o: no error at moment
ret: general error  more information will be shown on display.
When pressing the "OK" button from main menu the version of the LANTIME software, the NTP and the LINUX
kernel version will be displayed.
TYP:ELX800 TCR511 M3x V5.26 2.6.12
SN:030100000000 NTP: 4.2.0
The following main menus will be displayed when pressing the "UP" and "DOWN" arrow buttons:
14 Date: 19th April 2011 LANTIME M300 TCR

7.2 Root Menu Page 15
TCR: NORMAL OPERATION Thu, 20.07.2006
NTP: Offest PPS: 1ms UTC 14:02:01
-> Reference Time <- Network
Time Service System
-> Info TCR <-
Setup TCR
OK
Reference Time Network
-> Time Service <- System
-> external NTP <- Restart NTP
Local Stratum
OK
Reference Time -> Network <-
Time Service System
-> Global Cfg. <- Services
Interfaces
OK
Reference Time Network
Time Service -> System <-
->Set Time Zone<- Restart NTP
Reboot Server Factory Defaults
OK
LANTIME M300 TCR Date: 19th April 2011 15