Meinberg LANTIME M300and PZF NTP Time Server User’s Manual M300
User Manual: Meinberg LANTIME M300andPZF NTP Time Server User’s Manual Troubleshoot Meinberg LANTIME M300andPZF NTP Time Server |
Open the PDF directly: View PDF 
.
Page Count: 122
| Download | |
| Open PDF In Browser | View PDF |
MANUAL
LANTIME M300 PZF
DCF77 NTP Server
17th February 2014
Meinberg Radio Clocks GmbH & Co. KG
Table of Contents
1 Impressum
1
2 Quick Start
2
3 Network Timeserver with DCF77 synchronized time base
3
4 The
4.1
4.2
4.3
4.4
4.5
Modular System LANTIME
Supported Network Services . . . . .
Additional Features . . . . . . . . .
User Interface . . . . . . . . . . . .
Input and Output Options . . . . . .
Why to use a Network Time Server?
.
.
.
.
.
4
5
5
5
6
6
5 Network Time Protocol (NTP)
5.1 NTP Target . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 NTP-Client Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
7
7
6 General information PZF
6.1 Features of PZF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7 DCF77 Antenna
11
7.1 Assembly of the Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
8 Booting the PZF receiver
12
9 Booting the Single Board Computer
13
10 Configuration User Interface
10.1 Introduction: Con guration LANTIME
10.2 Root Menu . . . . . . . . . . . . . . .
10.3 Menü: Reference Time . . . . . . . .
10.3.1 Info PZF . . . . . . . . . . . .
10.3.2 PZF Status and Version . . . .
10.3.3 Correlation and Field . . . . .
10.3.4 Setup PZF . . . . . . . . . . .
10.3.5 Transmitter Distance . . . . .
10.3.6 Ignore Lock (Simulation Mode)
10.3.7 Initial Time . . . . . . . . . .
10.3.8 Serial Outputs . . . . . . . . .
10.4 Menu: Time Service . . . . . . . . . .
10.4.1 Menu: external NTP . . . . .
10.4.2 Menu: Stratum of local clock .
10.4.3 Menu: Restart NTP . . . . . .
10.5 Menu: Network . . . . . . . . . . . .
10.5.1 Setup Global Con guration . .
10.5.2 Setup Network Interfaces . . .
10.5.3 Setup Network Ipv4 Parameter
10.5.4 Menu: Setup Ipv6 Parameter .
10.5.5 Menu: Link Mode . . . . . . .
10.5.6 Menu: Setup Network Services
10.6 Menu: System . . . . . . . . . . . . .
10.6.1 Set time zone . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
14
14
15
17
18
18
18
19
19
19
19
20
21
21
21
21
22
22
23
23
24
24
24
25
25
11 The WEB Interface
27
11.1 Con guration: Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
0
11.2 Con guration: Ethernet . . . . . . . . . . .
11.2.1 SYSLOG Server . . . . . . . . . . .
11.3 Network interface speci c con guration . .
11.3.1 IPv4 addresses and DHCP . . . . .
11.3.2 IPv6 addresses and autoconf . . . .
11.3.3 High Availability Bonding . . . . . .
11.3.4 Additional Network Con guration .
11.4 Con guration: Noti cation . . . . . . . . .
11.4.1 Alarm Events . . . . . . . . . . . .
11.4.2 E-mail messages . . . . . . . . . . .
11.4.3 Windows Popup Messages . . . . .
11.4.4 SNMP-TRAP messages . . . . . . .
11.4.5 VP100/NET wall mount display . .
11.4.6 User de ned Alarm scripts . . . . .
11.4.7 NTP Client Monitoring . . . . . . .
11.4.8 Alarm messages . . . . . . . . . . .
11.5 Con guration: Security . . . . . . . . . . .
11.5.1 Password . . . . . . . . . . . . . . .
11.5.2 HTTP Access Control . . . . . . . .
11.5.3 SSH Secure Shell Login . . . . . . .
11.5.4 Generate SSL Certi cate for HTTPS
11.5.5 NTP keys and certi cates . . . . . .
11.5.6 SNMP Parameter . . . . . . . . . .
11.6 Con guration: NTP . . . . . . . . . . . . .
11.6.1 NTP Authentication . . . . . . . . .
11.6.2 NTP AUTOKEY . . . . . . . . . .
11.7 Con guration: Local . . . . . . . . . . . . .
11.7.1 Administrative functions . . . . . .
11.7.2 User Management . . . . . . . . . .
11.7.3 Administrative Information . . . . .
11.7.4 Software Update . . . . . . . . . . .
11.7.5 Automatic con guration check . . .
11.7.6 Get Diagnostics Information . . . .
11.7.7 Receiver Information . . . . . . . .
11.7.8 Web interface language . . . . . . .
11.8 Con guration: Statistics . . . . . . . . . . .
11.8.1 Statistical Information . . . . . . . .
11.9 Con guration: Manual . . . . . . . . . . .
11.10Con guration: PTP . . . . . . . . . . . . .
11.10.1 PTPv2 - Global Con guration . . .
11.10.2 Option: PTP Client Monitoring . . .
11.10.3 PTP Network Con guration . . . .
11.10.4 PTP State Files . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
29
30
31
31
31
32
33
34
35
36
36
36
36
36
37
37
38
39
39
39
41
42
42
43
45
46
49
50
50
51
53
54
54
55
55
56
57
58
59
60
61
63
64
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
65
66
68
70
72
73
73
13 SNMP Support
13.1 Con guration over SNMP . . . . . . . . . . . . . . . . . . . . . . .
13.1.1 Examples for the usage of the SNMP con guration features
13.1.2 Further con guration possibilities . . . . . . . . . . . . . . .
13.1.3 Send special timeserver commands with SNMP . . . . . . .
13.1.4 Con guration of the timeserver with SNMP: Reference . . .
13.2 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13.2.1 SNMP Trap Reference . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
76
77
78
79
79
81
86
86
12 The
12.1
12.2
12.3
12.4
Command Line Interface
CLI Ethernet . . . . . . . . . . .
CLI Noti cation . . . . . . . . .
CLI Security . . . . . . . . . . .
CLI NTP Parameter . . . . . . .
12.4.1 CLI NTP Authentication
12.5 CLI Local . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Page 0
14 Attachment: Technical Information
14.1 Skilled/Service-Personnel only: Replacing the Lithium Battery
14.2 Technical Speci cations M600/300 Multipac . . . . . . . . . .
14.3 Safety instructions for building-in equipment . . . . . . . . . .
14.3.1 CE-Label . . . . . . . . . . . . . . . . . . . . . . . . .
14.4 Rear Panel Connectors . . . . . . . . . . . . . . . . . . . . .
14.5 Pin Assignment: Serial Connectors . . . . . . . . . . . . . . .
14.5.1 Serial Time String . . . . . . . . . . . . . . . . . . . .
14.5.2 TERMINAL (Console) . . . . . . . . . . . . . . . . . .
14.6 Error Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.6.1 Technical Speci cation . . . . . . . . . . . . . . . . .
14.7 Technical speci cations PZF600 . . . . . . . . . . . . . . . .
14.8 Technical Speci cations LAN CPU . . . . . . . . . . . . . . .
14.9 Time Strings . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.9.1 Format of the Meinberg Standard Time String . . . . .
14.9.2 Format of the Uni Erlangen String (NTP) . . . . . . .
14.9.3 Format of the ATIS standard Time String . . . . . . .
14.9.4 Format of the SYSPLEX-1 Time String . . . . . . . .
14.9.5 Format of the SAT Time String . . . . . . . . . . . .
14.9.6 Format of the ABB SPA Time String . . . . . . . . .
14.9.7 Format of the Computime Time String . . . . . . . . .
14.9.8 Format of the NMEA 0183 String (RMC) . . . . . . .
14.10Manual VP100/NET Display con guration . . . . . . . . . . .
14.11Global Con guration File . . . . . . . . . . . . . . . . . . . .
14.12Global Option File . . . . . . . . . . . . . . . . . . . . . . . .
14.13Third party software . . . . . . . . . . . . . . . . . . . . . . .
14.13.1 Operating System GNU/Linux . . . . . . . . . . . . .
14.13.2 Samba . . . . . . . . . . . . . . . . . . . . . . . . . .
14.13.3 Network Time Protocol Version 4 (NTP) . . . . . . .
14.13.4 mini_httpd . . . . . . . . . . . . . . . . . . . . . . .
14.13.5 GNU General Public License (GPL) . . . . . . . . . . .
14.14USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14.14.1 Menu Backup Con guration to USB Stick . . . . . . .
14.14.2 Menu Write Diagnostic File to USB Stick . . . . . . .
14.14.3 Keypad locking . . . . . . . . . . . . . . . . . . . . .
14.14.4 Menu Restore Con guration . . . . . . . . . . . . . .
14.15Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . .
0
Date: 17th February 2014
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
87
87
88
89
89
90
90
90
90
91
91
92
93
94
94
95
97
98
99
100
101
102
103
105
107
108
108
108
109
110
111
115
115
115
116
116
117
LANTIME M300 PZF
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:
info@meinberg.de
Date:
2014-02-11
LANTIME M300 PZF
Date: 17th February 2014
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:.
Starting up
.......
please wait...
Main Menu will be displayed with some important status informations after booting has nished:
PZF: NORMAL OPERATION
NTP: not sync
Fri, 11.05.2009
UTC 09:12:11
PZF: NORMAL OPERATION
NTP: not sync
Fri, 11.05.2009
UTC 09:12:11
If the DCF77 PZF receiver remains asynchronous (Ref.Time LED is still red after 3 minutes) the Field and the
Correlation (at least 60, optimum 99) are to check (press buttons "↓, OK, OK, ↓, OK" from main menu). The
antenna has to be installed with the longer side to direction of Frankfurt in Germany.
PZF STATE:
CORR.: 90
FIELD: 94
State:fine
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:
Global Cfg.
-> Interfaces <-
Services
Select "Interfaces" and then press 3 times the OK button to change to the IPv4 con guration page to enter the
IP address, netmask and the default gateway:
SETUP:
Ipv4
Ipv4 LAN Parameter ETH0
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 Session.
Default user: root
Default password: timeserver
2
Date: 17th February 2014
LANTIME M300 PZF
Page 3
3 Network Timeserver with DCF77 synchronized
time base
(Local Area Network Timeserver) provides a high precision time base to a TCP/IP network (Stratum1-Server). The NTP (Network Time Protocol) is used to synchronize all NTP clients with the reference. The
several LANTIME variants dier from each other by the time reference. A GPS receiver, a DCF77 receiver or an
IRIG time code receiver can be integrated as an internal reference as well as a combination of these references
(hybrid system). External references are also possible. LANTIME M300 / PZF (equivalent to LANTIME/PZF)
is a set of equipment composed of a DCF77 controlled clock, a single-board computer with integrated network
board and a power supply, all installed in a metal 19" modular chassis and ready to operate. A simpli ed
LINUX operating system is installed on the single-board computers ash disk. Eight push buttons and a 2 x 40
character LC display can be used to con gure and monitor the time server. After the network connection has
been established the time server can also be con gured and monitored remotely from a workstation via TELNET
or FTP. An integrated HTTP server enables access to the LANTIME by using an ordinary WEB browser.
LANTIME
LANTIME M300 PZF
Date: 17th February 2014
3
Page 4
4 The Modular System LANTIME
4 The Modular System LANTIME
LANTIME time server is a set of equipment composed of a reference clock (e.g.: satellite controlled clock GPS,
correlation receiver PZF or time code reader 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 accessible via connectors in the rear panel of the case. Details of the components are
described below.
2
1
PZF: NORMAL OPERATION
NTP: Offset
PPS:
-4µs
Mon , dd.mm.yyyy
UTC 12: 00 : 00
6
4
5
F1
OK
Ref. Time
Time Service
Terminal
F2
ESC
Network
Alarm
USB
ENGLISH
1.
LC-Display, 2 x 40 characters
2.
Function buttons: 4-way navigation; F1, F2, OK, ESC
3.
Status LEDs: Ref. Time, Time Service, Network, Alarm
4.
Terminal / VT100, 38400 Baud, 8N1, 9pin. D-SUB male
5.
USB connector
7
3
LANTIME M300
DEUTSCH
1.
LC-Display, 2 x 40 Zeichen
2.
Funktionstasten: 4 Wege Navigation; F1, F2; OK, ESC
3.
Status LEDs: Ref. Time, Time Service, Network, Alarm
4.
Terminal / VT100, 38400 Baud, 8N1, 9pol. D-SUB Stecker
5.
USB Anschluss
5
4
3
Error
TxD 0
CO NO NC
COM 0
2
1
PPS Out
ETH1
O
ETH0
100M 10M
10MHz Out
ENGLISH
1.
Power supply connector
2.
Serial Port COM 0, 9pin. D-SUB, female
3.
Serial Port TxD 0, 9pin. D-SUB, female
4.
Error relay output, 3pin. DFK
5.
PZF Antenna, BNC
6.
PPS / 10MHz output, BNC
7.
Network connectors ETH0 - ETH1, 10/100 Mbit RJ45
PZF
Antenna
I
100-240V AC
50/60Hz
DEUTSCH
1.
Spannungsversorgung
2.
Serielle Schnittstelle COM 0, 9pol. D-SUB Buchse
3.
Serielle Schnittstelle TxD 0, 9pol. D-SUB Buchse
4.
Störmelderelaisausgang, 3pol. DFK
5.
PZF Antenne, BNC
6.
PPS / 10MHz Ausgang, BNC
7.
Netzwerk Anschlüsse ETH0 - ETH1, 10/100MBit RJ45
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 LANTIME. 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.
4
Date: 17th February 2014
LANTIME M300 PZF
4.1 Supported Network Services
Page 5
4.1 Supported Network Services
The following network services are provided via RJ45 10/100Base-T Ethernet (Auto sensing):
-
NTP
NTP
NTP
NTP
NTP
Simple
TIME
SNMP
-
DHCP Client
NFS
TELNET
FTP
HTTP
HTTPS with Openssl2
SSH2 Secure Shell Login
Alarm messages via e-mail
- IPv6
v2, v3, v4
broadcast mode
multicast
symmetric keys
Autokey
Network Time Protocol (SNTP)
v1,2,3 with extended SNMP-Agent and SNMP-Traps
for NTP and reference clock status
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)
4.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
• 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
4.3 User Interface
• Terminal connection via serial interface, status LED
• Web browser interface with graphical statistic of the one-day cycle osets
• 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 dierent computers
• Con gurable e-mail noti cation
• Simulation of a synchronous radio clock in order to operate without antenna
LANTIME M300 PZF
Date: 17th February 2014
5
Page 6
4 The Modular System LANTIME
4.4 Input and Output 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
4.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 transmission 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 aect 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.
6
Date: 17th February 2014
LANTIME M300 PZF
Page 7
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 implementation 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 dierent 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 hierarchy 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, satelliet 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 dierent UNIX systems. Many UNIX systems have an NTP client preinstalled. 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.ntp.org
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 dierent ways. Either the system time can be set once by using the tool "ntpdate 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.
LANTIME M300 PZF
Date: 17th February 2014
7
Page 8
5 Network Time Protocol (NTP)
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:
remote
refid
st
t
when poll reach delay offset
ji�er
=======================================================================
LOCAL(0)
LOCAL(0) 3
l
36
64
3
0.00 0.000
7885
lan�me
.GPS.
0
l
36
64
1
0.00 60.1
15875
with the following meaning:
-
remote:
re d:
st:
when:
poll:
reach:
delay:
oset:
-
jitter:
list of all valid time servers (ntp.conf)
reference number
actual stratum value (hierarchy level)
last request (seconds)
period of requesting the time server (seconds)
octal notation of the successful requests, shifted left
delay of the network transmission (milliseconds)
dierence between system time and reference time
(milliseconds)
variance of the osets (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 diers 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").
8
Date: 17th February 2014
LANTIME M300 PZF
Page 9
6 General information PZF
The German long wave transmitter DCF77 started continuous operation in 1970. The introduction of time codes
in 1973 build the basic for developing modern radio remote clocks.
The carrier frequency of 77.5 kHz is amplitude modulated with time marks each second. The BCD-coding
of the time telegram is done by shifting the amplitude to 25% for a period of 0.1s for a logical '0' and for 0.2s
for a logical '1'. The receiver reconstructs the time frame by demodulating this DCF-signal. Because the AMsignal is normally superimposed by interfering signals, ltering of the received signal is required. The resulting
bandwidth-limiting causes a skew of the demodulated time marks which is in the range of 10 ms. Variations of
the trigger level of the demodulator make the accuracy of the time marks worse by additional +/-3 ms. Because
this precision is not su cient for lots of applications, the PTB (Physical and Technical Institute of Germany)
began to spread time information by using the correlation technique.
The DCF-transmitter is modulated with a pseudo-random phase noise in addition to the AM. The pseudo-random
sequence (PZF) contains 512 bits which are transmitted by phase modulation between the AM-time marks. The
bit sequence is build of the same number of logical '0' and logical '1' to get a symmetrical PZF to keep the
average phase of the carrier constant. The length of one bit is 120 DCF-clocks, corresponding to 1,55 ms. The
carrier of 77.5 kHz is modulated with a phase deviation of +/-10◦ per bit. The bit sequence is transmitted each
second, it starts 200ms after the beginning of an AM second mark and ends shortly before the next one.
Compared to an AM DCF77-receiver, the input lter of a correlation receiver can be dimensioned wide-bandwidth.
The incoming signal is correlated with a reconstructed receiver-PZF. This correlation analysis allows the generation
of time marks which have a skew of only some microseconds. In addition, the interference immunity is increased
by this method because interference signals are suppressed by averaging the incoming signal. By sending the
original or the complemented bit sequence, the BCD-coded time information is transmitted.
The absolute accuracy of the generated time frame depends on the quality of the receiver and the distance
to the transmitter, but also on the conditions of transmission. Therefore the absolute precision of the time frame
is better in summer and at day than in winter and at night. The reason for this phenomenon is a dierence in
the portion of the sky wave which superimposes the ground wave. To check the accuracy of the time frame, the
comparison of two systems with compensated propagation delay is meaningful.
LANTIME M300 PZF
Date: 17th February 2014
9
Page 10
6 General information PZF
6.1 Features of PZF
The PZF is a high precision receiveer module for the DCF77-signal build in euro card size (100 mm x 160 mm).
The micro controller of the system correlates its receiver-PZF with the incoming pseudorandom sequence and
decodes the time information of the DCF-telegram simultaneously. The controller handles input and output functions of the PZF600 and synchronizes the internal real-time clock.
By evaluating the pseudorandom phase noise, the PZF is able to generate time frames with thousand times
the accuracy of standard AM-time code receivers. The precise regulation of the main oscillator (TCXO, OCXO
optional for higher accuracy) of the radio clock is possible therefore. So, the PZF can be used as a standard
frequency generator besides the application as a time code receiver. Six xed and one settable TTL-level standard
frequencies are available at the rear VG-connector. The synthesizer frequency exists as an open drain output and
a sine wave signal also.
The PZF delivers TTL-low and TTL-high active pulses per minute and per second further. To distribute information concerning date, time and status, two independent serial interfaces (RS232) are used which are con gurable
in a setup menu.
Like mentioned before, the PZF includes a battery-backed real-time clock which runs crystal-precise if the main
power supply fails.
Important system parameters are stored in a battery-backed (RAM of the RTC) or non-volatile (EEPROM)
memory.
If an update of system software becomes necessary, the new rmware can be loaded via serial interface (COM0)
without removing the PZF600 for inserting a new EPROM.
10
Date: 17th February 2014
LANTIME M300 PZF
Page 11
7 DCF77 Antenna
The PZF Radio Clock operates with a ferrite antenna which is damped to match the bandwidth needed for the
correlation reception. The IP-Code is: IP56
7.1 Assembly of the Antenna
The antenna has to be mounted as exactly as possible. Turning it out of the main receive direction will result in
less accurate time frames. The antenna must be placed in longitudinal direction to the DCF-transmitter (Frankfurt). The nearness to microcomputers should be avoided and the antenna should be installed with a minimum
distance of 30 cm to all metal objects, if possible. A distance of several meters to TV- or computer monitors
must be kept.
After switching the PZF to the menu 'PZF STATE', the adjustment of the antenna can be executed. The
displayed value is proportional to the received eld strength. The best method of mounting the antenna is to look
for the minimum eld strength and turn the antenna by 90◦ to maximum then. A high eld strength on its own
is no guarantee for good conditions of reception, because interfering signals within the bandwidth of the receiver
also have an eect on the displayed value.
The maximum interference immunity can be found by looking at the autocorrelation coe cient (in percent)
in the menu 'PZF-STATE'. The displayed value should be close to 99 % for best reception.
LANTIME M300 PZF
Date: 17th February 2014
11
Page 12
8 Booting the PZF receiver
8 Booting the PZF receiver
If both, the antenna and the power supply, have been connected the system is ready to operate. About 10 seconds
after power-up the receiver's TCXO has warmed up and operates with the required accuracy.
Press navigation keys "↓. OK, OK, ↓, OK" from main menu to check the eld and correlation values. The
correlation "State" starts in "row" mode. If a good correlation has been found the receiver check 20 times this
new correlation: this State is called "check" and the correlation value counts from 1 to 20. If the correlation is
stell good the State changes to " ne" mode.
12
PZF STATE:
CORR.: 18
FIELD: 0
State:row
PZF STATE:
CORR.: 1
FIELD: 94
State:check
PZF STATE:
CORR.: 90
FIELD: 94
State:fine
Date: 17th February 2014
LANTIME M300 PZF
Page 13
9 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:
Starting up
.......
please wait...
After starting up the LINUX system the network function is initiated and the program for communication with
the PZF600 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 DCF77 PZF receiver). Until synchronisation is nished the following message is displayed:
PZF: NORMAL OPERATION
NTP: not sync
Fri, 15.12.2005
UTC 09:12:11
For the synchronisation of the NTPD with the PZF it is necessary that the DCF77 PZF receiver is synchronous
with the DCF77 time ("Ref.Time" LED is green). In this case the following message is monitored on the display.
PZF: NORMAL OPERATION
NTP: Offset PPS: 1ms
Fri, 15.12.2005
UTC 09:14:16
The second line shows the user that the NTPD is synchronized with the PZF with an oset of -1 ms. 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 oset. The NTPD tries to keep the oset below +-128 ms; if the oset becomes too large the
system time is set with the DCF77-time. Typically values for the oset are +-5 ms after the NTPD has already
synchronized.
LANTIME M300 PZF
Date: 17th February 2014
13
Page 14
10 Con guration User Interface
10 Configuration User Interface
10.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 root@198.168.10.10 // 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
14
Date: 17th February 2014
LANTIME M300 PZF
10.2 Root Menu
Page 15
10.2 Root Menu
The root menu is shown when the receiver has completed initialization after power-up. 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. After the start-up, the Lantime is not synchronized and
the text "NOT SYNC" is displayed. If the text "NORMAL OPERATION" appears, the system is already synchronized. If the antenna is disconnected or not working properly, the text "NOT AVAILABLE" is displayed instead.
PZF: NORMAL OPERATION
NTP: not sync
Mon, 28.08.2006
UTC 14:33:10
F1
OK
F2
ESC
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. The multicolor LEDs will
re ect the current state of the device:
Ref. Time
Time Service
Network
Alarm
Ref. Time
green:
red:
the reference clock (e.g. integrated PZF600) produce valid time.
the reference clock produce no valid time (e.g. not synchronized)
Time Service
green:
red:
Network
green:
red:
Alarm
o:
ret:
NTP has been synchronized to reference clock.
NTP is not synchronous to reference clock or sync to local clock
all watched network ports has been link up detected
at least one of the watched network ports (look at Setup Device
Parameter / Check Network Linkup) is not connected
no error at moment
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 PZFXXX M3x VX.xx 2.6.12
SN:030100000000
NTP: 4.2.0
The following main menus will be displayed when pressing the UP and DOWN arrow buttons:
LANTIME M300 PZF
Date: 17th February 2014
15
Page 16
10 Con guration User Interface
PZF: NORMAL OPERATION
NTP: Offest PPS: 1ms
-> Reference Time
Time Service
OK
16
<-
Setup Serial Out
Network
System
<-
->
Network
System
-> Global Cfg.
Interfaces
Reference Time
Time Service
OK
Network
System
-> external NTP Setup PZF
Info PZF
Reference Time
-> Time Service
OK
Thu, 20.07.2006
UTC 14:02:01
->
<-
<-
Network
System
->Set Time Zone Reference Time
Time Service
OK
<-
Network
System
-> Info PZF
Setup PZF
<-
Setup Serial Out
->
OK
Info PZF
-> Setup PZF
Setup Serial Out
<->Transmitter Dist.
Initial Time
Setup Serial Out <-
->Setup COM 0 Info PZF
Setup PZF
<-
Setup Serial Out
->
OK
Status & Version
Correlation & Field
<-
10.3.2 PZF Status and Version
Reference Clock PZF511
State: SYNC
PZF511 v2.06 S/N:001510000000 TCXO HQ
This rst menu will monitor the current state (sync or not sync). The next line will re ect the rmware version,
the serial number of the internal GPS and the type of the integrated oscillator.
10.3.3 Correlation and Field
PZF STATE:
CORR.: 18
FIELD: 0
State:row
PZF STATE:
CORR.: 1
FIELD: 94
State:check
PZF STATE:
CORR.: 90
FIELD: 94
State:fine
This message State:row indicates that the pseudo-random sequence is read into the internal RAM for one second
and the system tries to achieve a coarse synchronization. This procedure starts after power-up or worse reception
for more than ten seconds.
If the coarse synchronization was successful, the receiver enters the state of ne-correlation. The system tries to
lock the received PZF as exact as possible to generate a precise time frame. The display shows the correlation
coe cient at the end of each second, which can be in the range of 52 % to 99 %. A high value for the coe cient
should be achieved by choosing a suitable position for the antenna.
The essential part of the tracking is completed ve seconds after the appearance of 'CORR:xx%' and the generation of pulses per minute and per second starts. Tracking steps of three microseconds are possible each second
until the internal real time clock is synchronized (two minutes max.). Afterwards, corrections of the time frame
are executed per minute only.
The Field parameter will display the digitized value of the eld strength in this menu. There is a logarithmic relation between this value and the eld strength. This menu is useful for mounting the antenna
18
Date: 17th February 2014
LANTIME M300 PZF
10.3 Menü: Reference Time
Page 19
10.3.4 Setup PZF
Info PZF
-> Setup PZF <-
Setup Serial Out
-> Transmitter Dist. Setup COM 0 Time Service
<-
Network
System
-> external NTP
Network
System
-> Global Cfg.
Interfaces
OK
<-
<-
Services
->Hostname Interfaces
Namesrv.
Syslog
Services
<-> Ipv4 Parameter
Ipv6 Parameter
OK
Global Cfg.
Interfaces
->
<-
Link Mode
Services <-
>SSH:on < TELN:on
FTP:on
SNMP:off
OK
Netw.LED
IPv6:on
HTTP:on
HTTPS:on
NETB:off
In this submenu the network con guration parameters related to the network interfaces can be changed. The
submenus can be selected with the arrow keys and the OK button:
As soon as an IP address is con gured, additional network con guration can be done via network connection
with TELNET, SSH or the WEB interface. Ask your network administrator for network speci c parameters.
Every change of the network parameters will restart the NTP. All network speci c parameters will be saved on the
ash disk (/mnt/ ash/con g/global_con guration) and will be reloaded after reboot. It is highly recommended
not to edit this le manually but to con gure the parameters via the several con guration interfaces (HTTP, CLI
or SNMP). If this le is not present, an empty le will be created. See Appendix for the default settings of this
le.
10.5.1 Setup Global Configuration
Interfaces
-> Global Cfg. <-
OK
Services
->Hostname Interfaces
Services
<-> Ipv4 Parameter
Ipv6 Parameter
OK
<-
Link Mode
When con gured an IP address once additionally network con guration can be done via network connection with
TELNET, SSH or the WEB interface. Ask your network administrator for network speci c parameters. Every
change of the network parameters will restart the NTP. All network speci c parameters will be saved on the ash
disk (/mnt/ ash/con g/global_con guration) and will be reloaded after reboot.
10.5.3 Setup Network Ipv4 Parameter
->
ETH0
ETH1
OK
<-
Def.Gateway
>DHCP: disabled< ADDR: 192.168.10.2
NETMASK: 255.255.255.0
There is a separate con guration submenu for every physical network interface. If there is no DHCP client mode
activated a static IP address for each interface can be entered. IPv4 addresses are built of 32 bits which are
grouped in four octets, each containing 8 bits. You can specify an IP address in this mask by entering four
decimal numbers, separated by a point . .
Example: 192.168.10.2
Additionally you can specify the IPv4 netmask and your default gateway address.
Please contact your network administrator, who can provide you with the settings suitable for your speci c network.
If there is a DHCP (Dynamic Host Con guration Protocol) server available in your network, the LANTIME system
can obtain its IPv4 settings automatically from this server. If you want to use this feature (again, you should
ask your network administrator whether this is applicable in your network), you can change the DHCP Client
parameter to ENABLED. Using DHCP is the default factory setting.
If the DHCP client has been activated, the automatically obtained parameters are shown in the appropriate
elds (IPv4 address, netmask, gateway).
LANTIME M300 PZF
Date: 17th February 2014
23
Page 24
10 Con guration User Interface
10.5.4 Menu: Setup Ipv6 Parameter
Ipv4 Parameter
-> Ipv6 Parameter
Link Mode
<-
-> Link Local
Services <-
>SSH:on < TELN:on
FTP:on
SNMP:off
IPv6:on
HTTP:on
HTTPS:on
NETB:off
The possible network protocols and access methods can be con gured. After pressing the OK button you can
enable/disable SSH, TELNET, SNMP, FTP, IPV6, HTTP, HTTPS and NETBIOS by using the UP/DOWN Keys
and navigate through the list with the LEFT/RIGHT keys. After you saved your settings with the OK button,
all these subsystems are stopped and eventually restarted (only if they are enabled, of course).
24
Date: 17th February 2014
LANTIME M300 PZF
10.6 Menu: System
Page 25
10.6 Menu: System
Reference Time
Time Service
OK
->
Network
System
->Set Time ZoneSetup Outputs)
This menu lets the user enter the names of the local time zone with daylight saving disabled and enabled,
together with the zones time osets from UTC. The left part of the display shows the zone and oset if daylight
saving is o whereas the right part shows name and oset if daylight saving is on. These parameters are used to
convert UTC to local time, e.g. MEZ = UTC + 1h and MESZ = UTC + 2h for central Europe. The range of
date daylight saving comes in eect can be entered using the next two topics of the setup menu.
DAYLIGHT SAVING OFF:
DAYLIGHT SAVING ON :
|MEZ |
|MESZ |
+01:00h
+02:00h
These two topics let the user enter the range of date for daylight saving to be in eect. Concerning parameter
input both topics are handled identically, so they are described together in this chapter. Beginning and ending
of daylight saving may either be de ned by exact dates for a single year or using an algorithm which allows the
receiver to re-compute the eective dates year by year. The gures below show how to enter parameters in both
cases. If the number of the year is displayed as wildcards (*), a day-of-week must be speci ed. Then, starting
from the con gured date, daylight saving changes the rst day which matches the con gured day-of-week. In the
gure below March 25, 1996 is a Saturday, so the next Sunday is March 31, 1996.
All changeover rules for the daylight saving like "the rst/the second/the second to last/the last Sunday/Monday etc. in the x-th month," can be described by the used format " rst speci ed day-of-week after a de ned date".
If the number of the year is not displayed as wildcards the complete date exactly determines the day daylight
saving has to change (March 31, 1996 in the gures below), so the day-of-week does not need to be speci ed
and therefore is displayed as wildcards.
DAYLIGHT SAV ON
Day of Week: Sun
LANTIME M300 PZF
Date: 25.03.****
Time:
02:00:00
Date: 17th February 2014
25
Page 26
10 Con guration User Interface
DAYLIGHT SAV ON
Day of Week: ***
DAYLIGHT SAV OFF
Day of Week: Sun
DAYLIGHT SAV OFF
Day of Week: Sun
Date: 31.03.1996
Time:
02:00:00
Date: 25.10.****
Time:
03:00:00
Date: 25.03.1996
Time:
03:00:00
If no changeover in daylight saving is wanted, identical dates and times must be entered in both of the sub menus.
In addition identical osets for DAYLIGHT SAV ON/OFF should be con gured in the sub menu TIMEZONE.
After this a restart should be done.
26
Date: 17th February 2014
LANTIME M300 PZF
Page 27
11 The WEB Interface
Connect to the web interface by entering the IP of your LANTIME into the address eld of your web browser:
If you want to use an encrypted connection, replace the http:// with https:// in the above address. You may
be prompted to accept the SSL certi cate of your LANTIME the rst time you are connecting to the system via
HTTPS. In both HTTP and HTTPS mode, you will see the following login screen:
On this start page you see a short status display, which corresponds with the LC display on the front panel of the
LANTIME unit. The upper line shows the operation mode of the receiver.
In the upper right corner of the LC display the time and time zone can be found, below that you will nd
the date and day of the week. On the second line the systems reports the NTP status. During the initial synchronisation process a NTP: not sync indicates that the NTP system is not synchronised with the receiver, this can
also appear if the receiver looses synchronisation and the NTP switches back to its LOCAL CLOCK time source.
The receiver is connected to the LANTIME system internally by using a serial connection and additionally by
using the second pulse. There are therefore 2 references used by NTPD, the receiver (GPS, PZF,...) and PPS
time source. You will nd the two time sources in the status information of the NTPD. After the NTP is synchronised, the display shows NTP: Oset GPS [PZF,MSF,WWV,TCR]: x or NTP: Oset PPS: x where x is
the actual oset to the receiver or PPS time source.
This page will be reloaded every 30 seconds in order to re ect the current status of the unit. Please bear
this in mind when you try to login and enter your password. If you do not press ENTER or the Login button
within 30 seconds, the user and password eld is cleared and you have to start over again.
Login rst installation:
Default User: root
Default Password: timeserver
LANTIME M300 PZF
Date: 17th February 2014
27
Page 28
11 The WEB Interface
11.1 Configuration: Main Menu
After entering the right password, the main menu page shows up. This page contains an overview of the most
important con guration and status parameters for the system.
The start page gives a short overview of the most important con guration parameters and the runtime statistics
of the unit. In the upper left corner you can read which LANTIME model and which version of the LANTIME
software you are using. This LANTIME software version is a head version number describing the base system
and important subsystems. Below the version you will nd the actual hostname and domain of your LANTIME
unit, the IPv4 and IPv6 network address of the rst network interface and on the right side the serial number, the
uptime of the system (time since last boot) and the noti cation status.
In the second section the actual status of the GPS reference clock and the NTP subsystem is shown, additional information about the GPS receiver are also found here. This includes the number of satellites in view and
the number of good satellites in view.
The third section shows the last messages of the system, with a timestamp added. The newest messages are on
top of the list. This is the content of the le /var/log/messages, which is created after every start of the system
(and is lost after a power o or reboot).
By using the buttons in the lower part of the screen, you can reach a number of con guration pages, which
are described below.
28
Date: 17th February 2014
LANTIME M300 PZF
11.2 Con guration: Ethernet
Page 29
11.2 Configuration: Ethernet
In the network con guration all parameters related to the network interfaces can be changed. In the rst section
you can change the hostname and domain name. You can also specify two nameserver and two SYSLOG server.
In the nameserver and syslog server elds you may enter an IPv4 or IPv6 address (the syslog servers can be
speci ed as a hostname, too).
LANTIME M300 PZF
Date: 17th February 2014
29
Page 30
11 The WEB Interface
11.2.1 SYSLOG Server
All information written to the LANTIME SYSLOG (/var/log/messages) can be forwarded to one or two remote
SYSLOG servers. The SYSLOG daemon of this remote SYSLOG needs to be con gured to allow remote systems
to create entries. A Linux SYSLOD can be told to do so by using the command syslogd r when starting the
daemon.
If you enter nothing in the SYSLOG server elds or specify 0.0.0.0 as the SYSLOG servers addresses, the remote SYSLOG service is not used on your LANTIME.
Please be aware of the fact that all SYSLOG entries of the timeserver are stored in /var/log/messages and
will be deleted when you power o or reboot the timeserver. A daily CRON job is checking for the size of the
LANTIME SYSLOG and deletes it automatically, if the log size is exceeding a certain limit.
By specifying one or two remote SYSLOG servers, you can preserve the SYSLOG information even when you
need to reboot or switch o the LANTIME.
In the second section the possible network protocols and access methods can be con gured. You can enable/disable TELNET, FTP, SSH, HTTP, HTTPS, SNMP and NETBIOS by checking/unchecking the appropriate check
boxes. After you saved your settings with the Save button, all these subsystems are stopped and eventually
restarted (only if they are enabled, of course).
The third section allows you to select the IP protocol version 6. In this version the IPv4 protocol is mandatory and cannot be disabled, but as a workaround a standalone IPv6 mode can be achieved by entering an IPv4
address 0.0.0.0 and disabling the DHCP client option for every network interface of your LANTIME. By doing
so, you ensure that the timeserver cannot be reached with IPv4. Please note that TELNET, FTP and NETBIOS
cannot be used over IPv6 in this version. It is no problem to use IPv4 and IPv6 in a mixed mode environment on
your LANTIME.
30
Date: 17th February 2014
LANTIME M300 PZF
11.3 Network interface speci c con guration
Page 31
11.3 Network interface specific configuration
The interface speci c parameters can be found in the Interface section. If your LANTIME is equipped with only
one network interface, you will nd only one sub section (Interface 0). Otherwise you see a sub section for each
installed Ethernet port.
Here, the parameters for the network port can be changed. In the upper section of the page you can enter
the IPv4 parameters, the lower part gives you access to the IPv6 parameters of the interface.
11.3.1 IPv4 addresses and DHCP
IPv4 addresses are built of 32 bits, which are grouped in four octets, each containing 8 bits. You can specify an
IP address in this mask by entering four decimal numbers, separated by a point ..
Example: 192.168.10.2
Additionally you can specify the IPv4 netmask and your default gateway address. Please contact your network administrator, who can provide you with the settings suitable for your speci c network.
If there is a DHCP (Dynamic Host Con guration Protocol) server available in your network, the LANTIME
system can obtain its IPv4 settings automatically from this server. If you want to use this feature (again, you
should ask your network administrator whether this is applicable in your network), you can change the DHCP
Client parameter to ENABLED. In order to activate the DHCP client functionality, you can also enter the IP
address 000.000.000.000 in the LCD menu by using the front panel buttons of the LANTIME. Using DHCP is
the default factory setting.
The MAC address of your timeserver can be read in the LCD menu by pressing the NEXT button on the front
panel twice. This value is often needed by the network administrator when setting up the DHCP parameters for
your LANTIME at the DHCP server.
If the DHCP client has been activated, the automatically obtained parameters are shown in the appropriate
elds (IPv4 address, netmask, gateway).
11.3.2 IPv6 addresses and autoconf
You can specify up to three IPv6 addresses for your LANTIME timeserver. Additionally you can switch o the IPv6
autoconf feature. IPv6 addresses are 128 bits in length and written as a chain of 16bit numbers in hexadecimal
notation, separated with colons. A sequence of zeros can be substituted with :: once.
Examples:
"::"
"::1"
is the address, which simply consists of zeros
is the address, which only consists of zeros and a 1
as the last bit. This is the so-called host local address
of IPv6 and is the equivalent to 127.0.0.1 in the IPv4 world
"fe80::0211:22FF:FE33:4455" is a typical so-called link local
address, because it uses the fe80 pre x.
In URLs the colon interferes with the port section, therefore
IPv6-IP-addresses are written in brackets in an URL.
("http://[1080::8:800:200C:417A]:80/" ;
the last :80 simply sets the port to 80, the default http port)
If you enabled the IPv6 protocol, the LANTIME always gets a link local address in the format fe80:: . . . .,
which is based upon the MAC address of the interface. If a IPv6 router advertiser is available in your network and
if you enabled the IPv6 autoconf feature, your LANTIME will be set up with up to three link global addresses
automatically.
LANTIME M300 PZF
Date: 17th February 2014
31
Page 32
11 The WEB Interface
The last parameter in this sub section is Netlink mode. This controls the port speed and duplex mode of
the selected Ethernet port. Under normal circumstances, you should leave the default setting (autosensing)
untouched, until your network administrator tells you to change it.
11.3.3 High Availability Bonding
The standard moniker for this technology is IEEE 802.3ad, although it is known by the common names of trunking,
port trunking, teaming and link aggregation. The conventional use of bonding under Linux is an implementation
of this link aggregation.
Only one link is used at any given time. At least two physical Ethernet ports must be linked to one bonding group to activate this feature. The rst Ethernet Port in one bonding group provides the IP-Address and the
net mask of this new virtual device. The implementation of the LANTIME Bonding feature will not replace the
MAC address of the active ethernet port. Depending on the LINK state of the ETH-port the IP address of the
rst port in the bonding group will be set to the next ethernet port. All services will be restarted automatically.
32
Date: 17th February 2014
LANTIME M300 PZF
11.3 Network interface speci c con guration
Page 33
11.3.4 Additional Network Configuration
You can con gure additional network parameter like special network routes or alias de nitions. For this you will
edit a script le which will be activated every time after the network con guration will run.
Also the Samba Con guration from /etc/samba/smb.conf can be edited:
LANTIME M300 PZF
Date: 17th February 2014
33
Page 34
11 The WEB Interface
11.4 Configuration: Notification
34
Date: 17th February 2014
LANTIME M300 PZF
11.4 Con guration: Noti cation
Page 35
11.4.1 Alarm Events
On this page you can set up dierent noti cation types for a number of events. This is an important feature
because of the nature of a timeserver: running unobserved in the background. If an error or problem occurs, the
timeserver is able to notify an administrator by using a number of dierent noti cation types.
The LANTIME timeserver oers dierent ways of informing the administrator or a responsible person about
nine dierent events: EMAIL sends an e-mail message to a speci ed e-mail account, SNMP-TRAP sends a
SNMP trap to one or two SNMP trap receivers, WINDOWS POPUP MESSAGE sends a winpopup message to
one or two dierent computers. DISPLAY shows the alarm message on a wall mount display model VP100/NET,
which is an optional accessory you can obtain for your LANTIME. You also can use user de ned scripts and the
error relay out (see appendix).
Attention: mbgLtTrapNormalOperation
clears everything! It is a master
trap to show that the LANTIME is
running in full state!
Trapname
Cleared By
NTPStopped
NTPNotSync or
NTP Sync
NTPNotSync
NTPSync
ReceiverNotResponding
ReceiverNotSync or
ReceiverSync
ReceiverNotSync
ReceiverSync
AntennaFaulty
AntennaReconnect
SecondaryRecNotSync
SecondaryRecSync
PowerSupplyFailure
PowerSupplyUp
NetworkDown
NetworkUp
SecondaryRecNotResp
RecNotSync or
RecSync
The following traps are noti cations that do not have a "clearing" trap:
• mbgLtTrapCon gChanged
• mbgLtTrapLeapSecondAnnounced
• mbgLtTrapServerBoot
Every event can use a combination of those four noti cation types, of course you can disable noti cation for an
event (by just disabling all noti cation types for this event). The con guration of the four noti cation types can
be changed in the upper section of the page, you can control which noti cation is used for which event in the
lower part of the page.
LANTIME M300 PZF
Date: 17th February 2014
35
Page 36
11 The WEB Interface
11.4.2 E-mail messages
You can specify the e-mail address which is used as the senders address of the noti cation e-mail (From: address),
the e-mail address of the receiver (To: address) and a SMTP smarthost, that is a mail server forwarding your
mail to the receiver's mail server. If your LANTIME system is connected to the internet, it can deliver those
e-mails itself by directly connecting to the receivers mail server. Additional e-mail addresses can be speci ed via
the CC-recipients button.
These settings cannot be altered with the LC display buttons of the front panel. Please note the following:
• The host name and domain name should be known to the SMTP smarthost
• A valid nameserver entry is needed
• The domain part of the From: address has to be valid
11.4.3 Windows Popup Messages
Most Microsoft Windows operating systems provide you with a local noti cation tool. You can send messages via
the special Windows protocol in your local network. It is not necessary to enable the NETBIOS protocol of the
LANTIME in order to use this noti cation. On the Windows client side it is necessary to activate the Microsoft
Client for Windows in the network con guration.
You can enter the Windows computer name of up to two Windows PCs in the appropriate elds. Every message
contains a time stamp and a plain text message:
11.4.4 SNMP-TRAP messages
Up to two SNMP trap receiver hosts can be con gured in this subsection, you may use IPv4 or IPv6 addresses
or specify a hostname. Additionally you have to enter a valid SNMP community string for your trap receiving
community. These can be unrelated to the SNMP community strings used for status monitoring and con guration
access (see SNMP con guration on the Security page).
11.4.5 VP100/NET wall mount display
The VP100/NET wall display is an optional accessory for the LANTIME timeserver, it has an own integrated
Ethernet port (10/100 Mbit) and a SNTP client. The time for the display can be received from any NTP server
using the SNTP protocol (like your LANTIME), additionally the display is capable of showing text messages,
which are sent by using a special utility. The LANTIME can send an alarm message to one or two VP100/NET
displays over the network, whenever an event occurs for which you selected the display noti cation type. If this
happens, a scrolling alarm message is shown three times on the display.
Just enter the display's IP address and its serial number (this is used for authorisation), which can be found
by pressing the SET button on the back of the display four times. The serial number consists of 8 characters,
representing four bytes in hexadecimal notation.
If you want to use the display for other purposes, you can send text messages to it by using our command
line tool send2display, which can be found on the LANTIME. This allows you to use the display by CRON jobs
or your own shell scripts etc. If you run the tool without parameters, a short usage screen is shown, explaining
all parameters it may understand. See appendix for a printout of this usage screen.
11.4.6 User defined Alarm scripts
You can de ne your own alarm script for every event by using the Edit user de ned noti cation script. This
script will be called automatically if one of the selected events occurs.
36
Date: 17th February 2014
LANTIME M300 PZF
11.4 Con guration: Noti cation
Page 37
This user alarm script will be stored on the Flash-Disk at /mnt/ ash/user_de ned_noti cation. This script
will be called with index and the alarm message as text. The index value of the test message is 0.
11.4.7 NTP Client Monitoring
You can monitor a group of NTP clients and supervise the time oset, the NTP stratum value and if the client
is reachable or not. With the button edit client list you can edit the list of clients to monitor. You can add the
TCP/IP address or the hostname of the client:
You can monitor the current states of the con gured clients:
11.4.8 Alarm messages
You can change the alarm message text for every event by using the "Edit Messages" button, the messages are
stored in a le /mnt/ ash/noti cation_messages on the ash disk of your timeserver.
LANTIME M300 PZF
Date: 17th February 2014
37
Page 38
11 The WEB Interface
11.5 Configuration: Security
38
Date: 17th February 2014
LANTIME M300 PZF
11.5 Con guration: Security
Page 39
11.5.1 Password
On the Security page you can manage all security relevant parameters for your timeserver. In the rst section
Login the administration password can be changed, which is used for SSH, TELNET, FTP, HTTP and HTTPS
access. The password is stored encrypted on the internal ash disk and can only be reset to the default value
timeserver by a factory reset, changing all settings back to the factory defaults. Please refer to the LCD
con guration section in this manual.
11.5.2 HTTP Access Control
With this function you can restrict the access to the web interface and allow only a few hosts to login. Only the
hosts you entered in the list are able to login to the HTTP/HTTPS server of your LANTIME.
If a non-allowed host tries to login, the following message appears:
11.5.3 SSH Secure Shell Login
The SSH provides you with a secure shell access to your timeserver. The connection is encrypted, so no readable
passwords are transmitted over your network. The actual LANTIME version supports SSH1 and SSH2 over IPv4
and IPv6. In order to use this feature, you have to enable the SSHD subsystem and a security key has to be
generated on the timeserver by using the Generate SSH key button. Afterwards, a SSH client can connect to
the timeserver and opens a secure shell:
ssh root @ 192.168.16.111
The rst time you connect to a SSH server with an unknown certi cate, you have to accept the certi cate,
afterwards you are prompted for your password (which is con gured in the rst section of this page).
Default Password:
timeserver
If you generate a new SSH key, you can copy and paste it into your SSH client con guration afterwards in
LANTIME M300 PZF
Date: 17th February 2014
39
Page 40
11 The WEB Interface
order to allow you to login without being prompted for a password. We strongly recommend to use SSH for shell
access, TELNET is a very insecure protocol (transmitting passwords in plain text over your network).
If you enabled SSH, your LANTIME automatically is able to use secure le transfer with SCP or SFTP protocol. The usage of FTP as a le transfer protocol is as insecure as using TELNET for shell access.
40
Date: 17th February 2014
LANTIME M300 PZF
11.5 Con guration: Security
Page 41
11.5.4 Generate SSL Certificate for HTTPS
HTTPS is the standard for encrypted transmission of data between web browser and web server. It relies on X.509
certi cates and asymmetric crypto procedures. The timeserver uses these certi cates to authenticate itself to the
client (web browser). The rst time a web browser connects to the HTTPS web server of your LANTIME, you
are asked to accept the certi cate of the web server. To make sure that you are talking to your known timeserver,
check the certi cate and accept it, if it matches the one stored on the LANTIME. All further connections are
comparing the certi cate with this one, which is saved in your web browser con guration. Afterwards you are
prompted to verify the certi cate only when it changed.
By using the button "Generate SSL certi cate for HTTP" you can create a new certi cate. Please enter your
organisation, name, mail address and the location in the upcoming form and press Generate SSL certi cate to
nally generate it.
After the successful generation of the certi cate, it is shown to you:
It is also possible to upload your own HTTPS certi cation. If you upload a non valid certi cation HTTPS will
not work.
LANTIME M300 PZF
Date: 17th February 2014
41
Page 42
11 The WEB Interface
11.5.5 NTP keys and certificates
The fourth and fth section of the Security page allow you to create the needed crypto keys and certi cates for
secure NTP operation (please see NTP authentication below).
The function Generate new NTP public key is creating a new self-signed certi cate for the timeserver, which is
automatically marked as trusted.
Important note: This certi cate is depending on the hostname of your LANTIME, it is mandatory to re-create
the certi cate after changing the hostname. The certi cates are build with the internal command ntp-keygen
-T (ntp-keygen is part of the installed NTP suite). Your LANTIME is using the /etc/ntp/ directory for storing
its private and public keys (this is called the keysdir). Please refer to the chapter NTP Autokey for further
information (below).
The two options Show NTP MD5 key and Edit NTP MD5 keys allow you to manage the symmetric keys
used by NTP. More about that can be found in the chapter about symmetric keys (below).
11.5.6 SNMP Parameter
In the last Section all parameters for SNMP can be con gured. More information you can nd later in this manual.
42
Date: 17th February 2014
LANTIME M300 PZF
11.6 Con guration: NTP
Page 43
11.6 Configuration: NTP
The NTP con guration page is used to set up the additional NTP parameters needed for a more speci c con guration of the NTP subsystem.
The default con guration of the timeserver consists of a local clock, which represents the hardware clock of
your LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference
after the GPS clock lost its synchronisation. The stratum level of this local clock is set to 12, this ensures that
clients recognise the switchover to the local clock and are able to eventually take further actions. The local clock
can be disabled if the timeserver should not answer any more when the reference clock is out of order.
Because the reference clock is internally connected to the LANTIME system by using a serial connection, the
accuracy using this way of synchronisation is around 1 ms. The high accuracy of the LANTIME timeserver (around
10 microseconds) is available by using the ATOM driver of the NTP subsystem, which is directly interpreting the
PPS (pulse per second) of the GPS reference clock. The default con guration looks like this:
# *** lantime ***
# NTP.CONF for GPS167 with UNI ERLANGEN
server 127.127.1.0
fudge 127.127.1.0 stratum 12
# local clock
# local stratum
server 127.127.8.0 mode 135 prefer
fudge 127.127.8.0 time1 0.0042
server 127.127.22.0
fudge 127.127.22.0 ag3 1
enable stats
#
#
#
#
LANTIME M300 PZF
GPS167 UNI Erlangen PPS
relative to PPS
ATOM (PPS)
enable PPS API
Date: 17th February 2014
43
Page 44
11 The WEB Interface
statsdir /var/log/
statistics loopstats
drift le /etc/ntp.drift
# Edit /mnt/ ash/ntpconf.add to add additional NTP parameters
By using the NTP con guration page, a number of additional parameters can be added to this default ntp.conf.
In the upper section up to ve external NTP servers can be set up to provide a high grade of redundancy for
the internal reference clock. For each of these external NTP servers the AUTOKEY or symmetric key feature of
NTP can be used to ensure the authentic of these time sources. The Prefer ag can be set for each external
server. The internal refclock has set this ag by default. The Prefer ag is usefull if one of the refclocks are
not available or out of sync.
The eld Stratum of local clock is used to change the stratum level of the local clock (see above), default
is 12.
The Local trusted key eld holds a list of all trusted symmetric keys (comma or space separated), which
have to be accepted by the NTPD of your LANTIME.
If you want to use your LANTIME timeserver to send NTP broadcast packets to your network, you have to
enter a valid broadcast address in NTP broadcast address. If you want to use IPv6 multicast mode, you have to
enter a valid IPv6 multicast address in this eld. Please note that NTP Version 4, which is used by the LANTIME
timeserver, only permits authenticated broadcast mode. Therefore you have to set up the AUTOKEY feature or
a symmetric key if you use a NTPv4 client and want to broadcast / multicast your time. A sample con guration
of the NTP client for broadcast with symmetric keys looks like:
broadcastclient yes
broadcastdelay 0.05
keys /etc/ntp/keys
trustedkey 6 15
requestkey 15
controlkey 15
# depends on your network
In the next section you can enable the AUTOKEY feature for your LANTIME timeserver and the PPS mode
(which is enabled in default settings), see above for a description.
The NTP Trusttime will specify the time how long the NTP will trust the reference time if this is not synchronized (free running). This time will be set in seconds or minutes or hours. The value 0 will be select the
default value for the speci c reference clock. The default values are:
LANTIME/GPS:
LANTIME/PZF:
LANTIME/RDT:
LANTIME/NDT:
96 h
0,5 h
0,5 h
96 h
After each restart and after any change of con guration a new /etc/ntp.conf le is generated by the LANTIME
software. Any changes you made to this le are lost. In order to use your custom ntp.conf (your LANTIME is
using a standard version of the NTP software suite, therefore all con guration parameters of the NTP software
are fully supported), you have to edit the le /mnt/ ash/ntpconf.add, which is automatically appended to the
/etc/ntp.conf le generated at boot time or when reloading con guration after a change. You can edit this le
by using the button Edit additional NTP parameter.
44
Date: 17th February 2014
LANTIME M300 PZF
11.6 Con guration: NTP
Page 45
By choosing Show current NTP con guration, you can review the actual state of the /etc/ntp.conf le. The
le cannot be changed on this page, see above for a description why editing this le is not reasonable.
11.6.1 NTP Authentication
NTP version 2 and version 3 support an authentication method using symmetric keys. If a packet is sent by the
NTPD while using this authentication mode, every packet is provided with a 32 bit key ID and a cryptographic
64/128 bit checksum of the packet. This checksum is built with MD5 or DES, both algorithms oer a su cient
protection against manipulation of data.
Please note that the distribution of DES in the United States of America and Canada is subject to restrictions, while MD5 is not aected by that. With any of these algorithms the receiving NTP clients validate the
checksum. Both parties (server and client) need to have the same crypto key with the same key ID.
In the authentication mode a party is marked untrusted and not suitable for synchronisation, whenever unauthorised packets or authorised packets with a wrong key are used. Please note that a server may recognise a lot of
keys but uses only a few of them. This allows a timeserver to serve a client, who is demanding an authenticated
time information, without trusting the client.
Some additional parameters are used to specify the key IDs used for validating the authentic of each partner. The con guration le /etc/ntp.conf of a server using this authentication mode may look like this:
# peer con guration for 128.100.100.7
# (expected to operate at stratum 2)
# fully authenticated this time
peer 128.100.49.105 key 22 # suzuki.ccie.utoronto.ca
peer 128.8.10.1 key 4
# umd1.umd.edu
peer 192.35.82.50 key 6
# lilben.tn.cornell.edu
keys /mnt/ ash/ntp.keys
trustedkey 1 2 14 15
requestkey 15
LANTIME M300 PZF
# path for key le
# de ne trusted keys
# key (mode 6) for accessing server variables
Date: 17th February 2014
45
Page 46
11 The WEB Interface
controlkey 15
# key (mode 7) for accessing server variables
The keys parameter indicates the location of the le, in which all symmetric keys are stored. The trustedkey
line identi es all key IDs, which have to be considered trusted or uncompromised. All other keys de ned in the
key le are considered compromised. This allows to re-use already owned keys by just adding their respective key
ID to the trustedkey parameter. If a key needs to be switched o, it can be removed from this line without
actually removing it from the system. This ensures an easy way to re-activate it later without actually transferring
the key again.
The line requestkey 15 declares the key ID for mode-6 control messages (as described in RFC-1305), which
are used by the ntpq utility for example. The controlkey parameter is specifying the key used for mode-7 private
control messages, for example used by the ntpdc utility. These keys protect the ntpd variables against unauthorised modi cation.
The ntp.keys le mentioned above holds a list of all keys and their respective ID known by the server. This
le should not be world-readable (only root should be able to look into this) and it may look like this:
# ntp keys le (ntp.keys)
1
2
14
15
N 29233E0461ECD6AE
M RIrop8KPPvQvYotM
M sundial
A sundial
10
10
10
A SeCReT
N d3e54352e5548080
S a7cb86a4cba80101
#
#
#
#
#
des key in NTP format
md5 key as an ASCII random string
md5 key as an ASCII string
des key as an ASCII string
the following 3 keys are identical
The rst column holds the key ID (used in the ntp.conf le), the second column de nes the format of the key,
which is following in column three. There are four dierent key formats:
means DES key with up to eight 7-bit ASCII characters, where each character is standing for a key
octet (this is used by Unix passwords, too).
•
A
•
S
is a DES key written in hexadecimal notation, where the lowest bit (LSB) of each octet is used as the
odd parity bit.
• If the key format is speci ed as N , it also consists of a hexadecimal string, but in NTP standard format
by using the highest bit (HSB) of each octet used as the odd parity bit.
• A key de ned as
M
is a MD5 key with up to 31 ASCII characters.
• The LANTIME supports MD5 authentication only.
• Please be aware of the following restrictions: No #, t (tab), n (newline) and 0 (null) are allowed
in a DES or MD5 ASCII key. The key ID 0 is reserved for special purposes and should not appear in the
keys le.
11.6.2 NTP AUTOKEY
NTP Version 4 supports symmetric keys and additionally provides the so-called AUTOKEY feature. The authentic
of received time at the NTP clients is su ciently ensured by the symmetric key technique. In order to achieve a
higher security, e.g. against so-called replay attacks, it is important to change the used crypto keys from time to
time.
In networks with a lot of clients, this can lead to a logistic problem, because the server key has to be changed
on every single client. To help the administrator to reduce this work (or even eliminate it completely), the NTP
developers invented the AUTOKEY feature, which works with a combination of group keys and public keys. All
NTP clients are able to verify the authentic of the time they received from the NTP servers of their own AUTOKEY group by using this AUTOKEY technique.
The AUTOKEY features works by creating so-called secure groups, in which NTP servers and clients are combined. There are three dierent kinds of members in such a group:
46
Date: 17th February 2014
LANTIME M300 PZF
11.6 Con guration: NTP
Page 47
a) Trusted Host
One or more trusted NTP servers. In order to become a trusted server, a NTP server must own a self-signed
certi cate marked as trusted. It is good practice to operate the trusted hosts of a secure group at the lowest
stratum level (of this group).
b) Host
One ore more NTP servers, which do not own a trusted certi cate, but only a self-signed certi cate without
this trusted mark.
c) Client
One ore more NTP client systems, which in contrast to the above mentioned servers do not provide accurate time
to other systems in the secure group. They only receive time.
All members of this group (trusted hosts, hosts and clients) have to have the same group key. This group
key is generated by a so-called trusted authority (TA) and has to be deployed manually to all members of the
group by secure means (e.g. with the UNIX SCP command). The role of a TA can be ful lled by one of the
trusted hosts of the group, but an external TA can be used, too.
The used public keys can be periodically re-created (there are menu functions for this available in the web
interface and also in the CLI setup program, see Generate new NTP public key in section NTP Autokey of the
Security Management page) and then distributed automatically to all members of the secure group. The group
key remains unchanged, therefore the manual update process for crypto keys for the secure group is eliminated.
A LANTIME can be a trusted authority / trusted host combination and also a non-trusted host in such a secure
group.
To con gure the LANTIME as a TA / trusted host, enable the AUTOKEY feature and initialise the group
key via the HTTPS web interface (Generate groupkey) or CLI setup program. In order to create such a group
key, a crypto password has to be used in order to encrypt / decrypt the certi cate. This crypto password is
shared between all group members and can be entered in the web interface and CLI setup program, too. After
generating the group key, you have to distribute it to all members of your secure group (and setup these systems
to use AUTOKEY, too). In the ntp.conf le of all group members you have to add the following lines (or change
them, if they are already included):
crypto pw cryptosecret
keysdir /etc/ntp/
In the above example cryptosecret is the crypto password, that has been used to create the group key and the
public key. Please note that the crypto password is included as a plain text password in the ntp.conf, therefore
this le should not be world-readable (only root should have read access to it).
On the clients, the server entries must be altered to enable the AUTOKEY feature for the connections to the
NTP servers of the group. This looks like:
server time.meinberg.de autokey version 4
server time2.meinberg.de
You nd the server time.meinberg.de which is using the AUTOKEY feature, while time2.meinberg.de is used
without any authentic checks.
If you want to setup the LANTIME server as a trusted host, but need to use a dierent trusted authority,
please create your own group key with this TA and include it with the web interface of your LANTIME (on page
Security Management see section NTP autokey , function Upload groupkey).
If you want to setup the LANTIME as a non-trusted NTP server, you have to upload the group key of your
secure group ( Security Management / NTP autokey / Upload groupkey) and create your own, self-signed
certi cate (without marking it as trusted). Because every certi cate which is creating by using the web interface
and/or CLI setup is marked trusted, you have to execute the tool ntp-keygen manually on your LANTIME by
LANTIME M300 PZF
Date: 17th February 2014
47
Page 48
11 The WEB Interface
using shell access (via SSH).
LantimeGpsV4:/etc/ntp # ntp-keygen -q cryptosecret
Here, too, cryptosecret is the crypto password used in the ntp.conf entry. Then you have to copy the new
ntpkeys to the ash disk with:
cp /etc/ntp/ntpkey_* /mnt/ ash/con g/ntp/uploaded_groupkeys
A detailed description about ntp-keygen can be found on the NTP website (http://www.ntp.org).
Example:
This autokey group is formed by one Stratum-1-server (B), two Stratum-2-servers (D and E) and a number of
clients (in the diagram there are 4 clients shown, c1 c4). B is the trusted host, he holds the group key and a
self-signed certi cate marked as trusted.
D and E are NTP servers, which are non-trusted hosts of the group, they hold the group key and a self-signed
certi cate which lacks the trusted mark. The clients also hold the group key and a self-signed certi cate. In
order to distribute new public keys to the whole group, the administrator only has to generate a new t key,
which will be distributed automatically to the two hosts D and E. Because these two servers can now present a
unbroken chain of certi cates to a trusted host, they can be considered trusted by the clients as well.
More about the technical background and detailed processes of the AUTOKEY technique can be found at the
o cial NTP website (http://www.ntp.org).
48
Date: 17th February 2014
LANTIME M300 PZF
11.7 Con guration: Local
Page 49
11.7 Configuration: Local
LANTIME M300 PZF
Date: 17th February 2014
49
Page 50
11 The WEB Interface
11.7.1 Administrative functions
In the rst section there are several functions which may be used by the administrator. The button Reboot LANTIME is restarting the system, the built-in reference clock is not aected by this, only the included computer
system is rebooted, which may take up to 30 seconds.
With Manual con guration you are able to change the main con guration by editing the con guration le
by hand. After editing, press the Save le button to preserve your changes, afterwards you are asked if your
changes should be activated by reloading the con guration (this results in reloading several subsystems like NTPD,
HTTPD etc.).
The function Send test noti cation is generating a test alarm message and sends it using all con gured notify
possibilities (e-mail, WMail, SNMP-Traps, wall mount display).
You can use the function Save NTP drift le to copy the le /etc/ntp.drift to the internal ash disc of your
LANTIME. NTP is using this le to have the parameters for compensation of the incorrectness of the system
clock available directly after a restart. This results in a faster synchronisation process of the NTPD subsystem
after a system restart. You should use this function only, if the NTPD has been synchronized to the internal
reference clock for more than one day. This is done here at Meinberg directly before shipping the LANTIME unit
to our customers, so you do not need to use this function during normal operation. It may be applicable after a
software update.
The function Reset to factory defaults is setting all con guration parameters back to default values. The
regular le /mnt/ ash/global_con guration will be replaced with the le /mnt/ ash/factory.conf, but rst a
copy of the con guration is saved under /mnt/ ash/global_con guration.old for backup reasons. The default
password timeserver is replacing the actual password, too. After using this function, all certi cates should be
recreated because of the change of the unit's hostname.
Please be aware of the fact that the default con guration is not activated instantly. If you want to avoid setting up
the IP address of your unit by locally con guring it on site with the buttons of the front panel (meaning physical
presence of someone directly at the location of the LANTIME), you have to con gure the network parameters
of your LANTIME immediately after using the reset to factory defaults button. So, please proceed directly to
the Ethernet page and check/change the IP address and the possible access subsystems (HTTP for example) of
the LANTIME. The rst usage of Save settings will load the con guration from ash into memory and activate it.
The point Download SNMP MIB les can be used to download all Meinberg speci c SNMP MIB les to
your workstation. They can be distributed to all SNMP management clients afterwards.
11.7.2 User Management
For administration dierent users can be set up. 3 group memberships can be assigned to each user: the SuperUser has all properties for administration. The group membership Administrator can change all parameters via
50
Date: 17th February 2014
LANTIME M300 PZF
11.7 Con guration: Local
Page 51
the command line interface (CLI) con guartion tool and the WEB interface. The group Administrator cannot
use any Linux command in a Telnet, SSH or Terminal session. If the Administrator will login, the setup program
will be started directly. After termination of the Setup program this user will be logout automatically. The group
membership Info has the same properties like the Administrator but cannot change any parameter.
The menu User Management allows you to set up dierent users with a password and the group membership. To change the properties of an user you have to delete the old user and set up a new one. The user root
cannot be deleted and has always the membership of Super-User. The password of the user root can be set on
the security page.
11.7.3 Administrative Information
The button List all messages displays the SYSLOG of the LANTIME completely. In this log all subsystems
create their entries, even the OS (upper case) kernel. The SYSLOG le /var/log/messages is only stored in
the system's ram disk, therefore it is lost after a power o or restart. If you con gured an external SYSLOG
server, all LANTIME syslog entries will be duplicated on this remote system and can be saved permanently this way.
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
15
15
15
15
15
15
15
15
15
15
13:35:17
13:35:17
13:35:17
13:35:17
13:35:17
13:38:36
13:38:36
13:45:36
14:01:11
14:01:17
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
ntpd[12948]:
ntpd[12948]:
ntpd[12948]:
ntpd[12948]:
ntpd[12948]:
lantime[417]:
lantime[417]:
proftpd[14061]:
login[15711]:
login[15711]:
ntpd 4.2.0@1.1161-r Fri Mar 5 15:58:48 CET 2004 (3)
signal_no_reset: signal 13 had ags 4000000
precision = 3.000 usec
kernel time sync status 2040
frequency initialized 45.212 PPM from /etc/ntp.drift
NTP sync to GPS
NTP restart
connect from 172.16.3.2 (172.16.3.2)
invalid password for `root' on `ttyp1' from `172.16.3.45'
root login on `ttyp1' from `172.16.3.45'
With List detailed version information a number of version numbers (including LANTIME software, operating
system and NTPD) are shown in a textbox.
LANTIME M300 PZF
Date: 17th February 2014
51
Page 52
11 The WEB Interface
The function List LANTIME Options shows the hardware options installed in your LANTIME.
Using the button List detailed GPS information gives you the possibility to check detailed GPS status information. The rst parameter indicates the time and date of the last update of the shown parameters. Next
you nd the GPS receiver status and the NTP status, followed by the GPS position data. The position uses
the Latitude / Longitude / Altitude format. Latitude and Longitude are shown in degrees, minutes and seconds,
Altitude is shown in meters above WGS84 ellipsoid.
The satellite section shows the numbers of satellites in view and the number of usable satellites (good SV).
Additionally, the selected set of the four used satellites can be read.
The accuracy of the calculated receiver position and time deviation is dependent on the constellation of the
four selected satellites. Using the position of the receiver and the satellites, a number of values can be calculated,
which allow a rating of the selected constellation. These values are called Dilutions of Precision (DOP).
PDOP is the abbreviation for Position Dilution of Precision, TDOP means Time Dilution of Precision and
GDOP stands for General Dilution of Precision. Lower values are indicating better accuracy.
The next section Satellite Info shows information about all the satellites, which are in view momentarily. The
satellite ID, elevation, Azimuth and distance to the receiver reveal the position of the satellite in the sky. The
Doppler shows whether the satellite is ascending (positive values) or descending (negative value).
52
Date: 17th February 2014
LANTIME M300 PZF
11.7 Con guration: Local
Page 53
11.7.4 Software Update
If you need to update the software of your LANTIME, you need a special le from Meinberg, which can be
uploaded to the LANTIME by rst choosing the le on your local computer with the Browse button and then
press Start rmware update.
The chosen le will be uploaded to the LANTIME, afterwards you are prompted to con rm the start of the
update process. The scope of the update only depends on the chosen le.
LANTIME M300 PZF
Date: 17th February 2014
53
Page 54
11 The WEB Interface
11.7.5 Automatic configuration check
All parameters of the LANTIME can be checked for plausibility and all con gured servers (e.g. SYSLOG servers,
nameservers) are tested for reachability. All red coloured values should be reviewed by the administrator. Because
all con gured hostnames / IP addresses of the servers are processed during the reachabilitytests, the whole check
process may take a while.
11.7.6 Get Diagnostics Information
The diagnostics information is a set of con guration parameters and les stored in a packed text le. With the
help of these informations the technical support from Meinberg can reproduce the current state of your LANTIME.
It takes some time to collect all information from the LANTIME. Do not press the button again while this process
is running - some web browsers will cancel the job if you press the button twice. After that you can download
the packed le con g.zip to your local computer. If you have any questions or problems with your LANTIME
please send this le con g.zip as an attachment of an e-mail to Meinberg support and describe your problem.
54
Date: 17th February 2014
LANTIME M300 PZF
11.7 Con guration: Local
Page 55
11.7.7 Receiver Information
Here you can indicate all important and relevant information about the used receiver / radio clock.
The example shows the menu with a GPS receiver and MGR module. With the button "List detailed GPS information" you can open a text eld with all relevant receiver information. A LANTIME server with GPS receiver
and MGR module can be adjust to its operational mode (appropriate environment) - computing the position to
the expecting speed.
11.7.8 Web interface language
With the selector box Web interface language you can change the displayed language of the WEB interface.
LANTIME M300 PZF
Date: 17th February 2014
55
Page 56
11 The WEB Interface
11.8 Configuration: Statistics
56
Date: 17th February 2014
LANTIME M300 PZF
11.8 Con guration: Statistics
Page 57
11.8.1 Statistical Information
In the rst section a graphical diagram shows the running synchronisation process. NTP is storing this statistical
information in so-called loopstats les, which are used here to draw the curves. The red line is describing
the oset between the internal reference clock (GPS) and the system clock. The blue line shows the frequency
errors of the system time (in PPM, parts per million). In the upper right corner of the diagram you will nd the
measurement range of the red and blue curve. The last 24 hours are shown initially, but you are able to select the
last 10 days (or fewer days, depending on the system uptime) or switch to a merge loopstats diagram, which
shows all available days in one diagram (with a maximum of 10 days). All time data is using UTC.
The next sections shows version information for a number of subsystems, including the OS kernel version, NTPD
version and the GPS rmware revision of the internal reference clock. Additionally, the MAC address of the rst
Ethernet interface can be found here. The Mem free value is indicating the free memory available to the system,
the Disk free value is related to the ram disk of the LANTIME. Both system memory and ram disk have a total
capacity of 32 MB (each). The Uptime parameter displays the time since the last boot process of the unit.
In the next section all NTP clients accessing the NTP server are listed. This list is maintained internally by
NTPD, clients who did not access the NTPD for a longer period are automatically removed. This section can
grow very long in large networks. There are no further information found about the parameters code, avglen and
rst. The name resolution of the IP address in the rst colume will take too much time; so its disabled.
After that a list of all actually refclocks of the internal NTP server will be shown.
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)
- oset:
dierence between system time and reference time (milliseconds)
- jitter:
variance of the osets (milliseconds)
The last section will show some NTP speci c informations about the refclock.
LANTIME M300 PZF
Date: 17th February 2014
57
Page 58
11 The WEB Interface
11.9 Configuration: Manual
This page gives you access to the documents stored on your LANTIME, especially the manuals and your own
notes. The two lists include lename, language, le type, date and size of the documents/notes.
The LANTIME documents can be downloaded from here in order to read / print them on your workstation.
The customer notes are a way of storing small pieces of information on your LANTIME, for example if you want to
keep track of con guration changes and want to comment them, you can create a note called con g_changes
and show or edit it from here. If you want to get rid of one of your notes, you are able to delete it by choosing
the appropriate button.
If you want to add a note (you can maintain more than one note on your LANTIME), after choosing the
button add note you have to enter a lename (without a directory path, all notes are stored in a xed directory
on the ash disk of your LANTIME) and the language of your note rst. After you con rmed these parameters
with Add document, you are able to edit the text of your new note.
58
Date: 17th February 2014
LANTIME M300 PZF
11.10 Con guration: PTP
Page 59
11.10 Configuration: PTP
In the PTP section, all parameters of the PTP subsystem can be con gured. The current state can be monitored
as well. When operating in SLAVE mode (as with MRS devices), a graphical representation of the oset and the
path delay to the grandmaster will be shown:
-
In the PTP V2 Management menu section you can view the current PTP state by displaying
the "ptp2_state_0" le (see 11.10.4).
-
All con guration parameters of the PTP unit can be viewed and changed by editing the
"ptp2_global_conf_0" le (see 11.10.1).
-
The IP address and VLAN con guration can be edited by altering the "ptp2_network_con g_0"
le (see 11.10.3).
- If more than one PTP unit is built into the system, then the con guration for each port can
be edited separately and will be listed on this page. A detailed description of the parameters
can be found in chapter 11.10.1 (Global PTP Parameters).
LANTIME M300 PZF
Date: 17th February 2014
59
Page 60
11 The WEB Interface
11.10.1 PTPv2 - Global Configuration
Parameter
Value
Description
PTP
PTP
PTP
PTP
[0,1]
[NUM,0:255]
[NUM,1,3]
[NUM,0:1]
PTP packet length as in PTPv1 standard (0=default)
A domain is logical group of PTP devices
1=UDP/IPv4 (L3), 3=IEEE 802.3 (L2)
0=ARB, 1=PTP (default)
PTP priority1
PTP priority2
[NUM:0:255]
[NUM:0:255]
Priority1 as used in Best Master Clock Algorithm
Priority2 as used in Best Master Clock Algorithm
PTP
PTP
PTP
PTP
[2x ]:0
[2x ]:1
[2x ]:3
[NUM]:60
used in MC Master or UC Slave mode
used in MC Master or UC Slave mode
used in MC Master or UC Slave mode
Requested duration until timeout/renewal
PTP Mode
[NUM]
0=Multicast (MC), 1=Unicast (UC)
PTP is slave
[BOOL]
1=Slave only, 0=Grandmaster only
PTP Delay Mechanism
[0,1]
0=End-to-End, 1=Peer-to-Peer
V1 Hardware Compatibility
Domain Number
Network Protocol
Timescale
Sync Interval
Announce Interval
DelayRequest Interval
Unicast interval duration [s]
PTP Unicast clockid of master
[ASCII,50]
PTP Unicast IP address of master
[IP]
Feature Presets
[NUM]
1=Power Pro le Preset, 2=Telecom Pro le Preset
Power Pro le Grandmaster ID
Power Pro le Network Inaccuracy
[NUM,3:254]:0
[NUM]:0
ID of Grandmaster, 3 - 254 (Power Pro le only)
accumulated time inaccuracy in worst
network path in ns (Power Pro le only)
User de ned Fix Oset positive
User de ned Fix Oset [ns]
[BOOL]
[NUM]
1=Positive PTP Phase shift to RefTime
Phase shift to RefTime (0..1000000 ns)
HQ Filter active
HQ Filter estimated accuracy [ns]
PDSC active
[BOOL]:0
[NUM]:5000
[BOOL]:0
Slave: Optimized lter for high load/jitter
estimated accuracy of HQ Filter,maximum jitter in network
Path Delay Step Compensation (Filter on)
(see also chapter ??)
PTP Announce Receipt Timeout
[2x ]:3
60
Unicast: Master Clock ID
(default: FF:FF:FF:FF:FF:FF:FF:FF as wildcard)
Unicast: IP address of Grandmaster
(e.g. 172.29.9.236)
only used with Mulicast Master mode
Date: 17th February 2014
LANTIME M300 PZF
11.10 Con guration: PTP
Page 61
11.10.2 Option: PTP Client Monitoring
From Lantime Firmware Version 5.34m onwards
The PTP Client-Monitor can be con gured via Front Panel Time
Service -> PTP IEEE1588 -> Setup PTP0
IEEE1588 V2 -> PTP Settings -> PTP Parameters -> PTP Client Management (for con guration see
the chapter on User Interfaces) and via Web Interface. In the Front-Panel maximum seven nodes (PTP Clients)
can be displayed. Therefore, for a complete overview the usage of the Web Interface is advised.
By selecting the ptpmmm_0.log button more than 100 PTP nodes can be listed. The list of PTP nodes with
their current status information has the following form:
# PTP Client Management: found 6 PTP nodes
#
#
UUID
State-Txt
-Val Offset
Pathdelay
Alias
#----------------------------------------------------------------------EC4670FFFE0024CC SLAVE
9
-0.000000015
0.000010420
alias_0
EC4670FFFE002435 MASTER
6
0.000000000
0.000000000
0050C2FFFEB717EA SLAVE
9
0.000000146
0.000020675
alias_2
0050C2FFFED287DE SLAVE
9
0.000000107
0.000020859
alias_3
EC4670FFFE000801 PASSIVE
7
0.000000000
0.000000000
Prior to one or more PTP nodes monitoring, a list of the PTP clients needs to be generated. The list can
be displayed and edited via Web Interface with the ptp2_client_management_list_of_uuids_0 button.
Each line corresponds to one of the PTP node being monitored. The line format correlates to the nodes
status-info in ptpmmm_0.log (see above). Therewith it is possible to copy the line with a desired PTP node
from the status-info with "Copy" and "Paste" it to the PTP client list.
#
UUID
0050C2FFFED287DE
LANTIME M300 PZF
State text
Slave
val
9
offset
0.000000500
Date: 17th February 2014
pathdelay
0.000025000
Alias
alias_name
61
Page 62
11 The WEB Interface
The rst value is a so-called PTP UUID, which consists mainly of the MAC address and a xed "FFFE" middle
part as follows: XX XX XX FF FE XX XX XX
Both next values correspond to PTP status as a text and a value. The following status values are possible:
SLAVE
9
MASTER
6
PASSIV
7
If the PTP status is equal to SLAVE, the maximal oset and the maximal pathdelay to a PTP Master can be
added additionally as limit threshold values. For each PTP node the following conditions are also being checked:
1.
2.
3.
4.
Accessibility
PTP Status
If PTP Status = SLAVE: exceeding a given maximal absolute oset value (related to the PTP Master).
If PTP Status = SLAVE: exceeding a given maximal pathdelay value (related to the PTP Master).
The current status conditions are forwarded to the Noti cation Triggers respectively via "PTP State changed"
noti cation. All noti cations are triggered only once until the state changes in the following way:
1.
2.
3.
4.
A node is again accessible.
PTP Status has changed again.
Oset value is below a given threshold again.
Pathdelay is below a given threshold again.
Menu Noti cation
62
Date: 17th February 2014
LANTIME M300 PZF
11.10 Con guration: PTP
Page 63
11.10.3 PTP Network Configuration
All network con gurations of the selected PTP interface can be done with this menu:
Content of the PTP Network Con guration File:
Parameter
Value
Description
TCPIP address
NETMASK
Default Gateway
[IP]:192.168.100.10
[IP]:255.255.255.0
[IP]:192.168.100.1
IP address of PTP port
Netmask of PTP port
Gateway
DHCP CLIENT
VLan enabled
VLan ID
VLan Priority
[BOOL]:0
[BOOL]:0
[NUM]:
[NUM]:
1=Activate DHCP client
Enable Virtual LAN interface (IEEE 802.1Q)
VLAN ID for virtual interface
VLAN priority for virtual interface
PTP IP TTL
[NUM]:
Multicast IP Packet Time To Live (TTL default:5)
Hostname
[ASCII,50]:PTPv2
Hostname for PTP port
Domainname
[ASCII,50]:
Domainname for PTP port
Nameserver 1
[ASCII,50]:
Nameserver 2
[ASCII,50]:
LANTIME M300 PZF
Date: 17th February 2014
63
Page 64
11 The WEB Interface
11.10.4 PTP State Files
In diesem Menü werden alle Statusinformationen der gewählten TSU angezeigt:
PTP Mode
Domain number
Network Protocol
PTP DelayMech
Current Port State
:
:
:
:
:
Clock class
:
Clock accuracy
Clock variance
Grandmaster MAC
Number of clients
Number of masters
PTP Port Link up
IPv4 address
Netmask
Gateway
Local Mac Address
PTP seconds
PTP timescale
PTP time source
PTP UTC Oset
PTP Leapsecond
TSU Time
SYS Time
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
64
[MASTER,SLAVE]
[0...3]
[UDP IPv4 Layer3,IEEE 802.3 Layer 2]
[E2E,P2P]
[INITIALIZING,LISTENING,UNCALIBRATED,MASTER,
UnicastMASTER,SLAVE,UnicastSLAVE]
[6=RefClock Sync,7=RefClock Holdover,
52=RefClock unsynchronized,255=Slave only]
33 (according to enumeration list in standard)
13565 [,65535=unknown]
00:60:6E:7C:27:2C
0 (not used yet)
0 (not used yet)
1
172.29.4.10
255.255.255.0
172.29.4.1
00:60:6E:7C:27:2C
1299849447 [raw PTP seconds]
PTP (TAI) [,ARB]
GPS [NTP,PTP,Internal Oszillator, unknown]
34
0 [Announcement active]
TAI:11.03.11 13:17:27.652680;
UTC:11.03.11 13:16:53.655558;
Date: 17th February 2014
LANTIME M300 PZF
Page 65
12 The Command Line Interface
The command line interface (CLI) can be used within a TELNET or SSH session. After login, just enter setup
to start the CLI setup tool.
The start page gives a short overview of the most important con guration parameters and the runtime statistics
of the unit. In the upper left corner you can read which LANTIME type and version of the LANTIME software you
are using. This LANTIME software version is a head version number describing the base system and important
subsystem. Below the version you will nd the actual hostname and domain of your LANTIME unit, the IPv4
and IPv6 network address of the rst network interface and on the right side the serial number, the uptime of the
system (time since last boot) and the noti cation status is reported.
In the second section the actual status of the GPS reference clock and the NTP subsystem is shown, additional information about the GPS receiver can also be found here. This includes the number of satellites in view
and the number of good satellites in view.
The third section shows the last messages of the system, each with a timestamp added. The newest messages are placed at the top of the list. This re ects the content of the le /var/log/messages, which is created
after every start of the system (and is lost after a power o or reboot, see Syslog server to learn how to save
the entries of your SYSLOG).
By using the buttons in the lower part of the screen, you can reach a number of con guration pages, that
are described below.
LANTIME M300 PZF
Date: 17th February 2014
65
Page 66
12 The Command Line Interface
12.1 CLI Ethernet
In the network con guration all parameters related to the network interfaces can be changed. In the rst section
you can change the hostname and domain name. You can also specify two nameservers and two SYSLOG servers.
In the nameserver and SYSLOG server elds you may enter an IPv4 or IPv6 address (the SYSLOG servers can be
speci ed as a hostname, too).
All information which is written to the LANTIME SYSLOG (/var/log/messages) can be forwarded to one or
two remote SYSLOG servers. The SYSLOG daemon of this remote SYSLOG needs to be con gured to allow
remote systems to create entries. A Linux SYSLOGD can be told to do so by using the command syslogd r
for starting the daemon.
If you enter nothing in the SYSLOG server elds or specify 0.0.0.0 as the SYSLOG server's addresses, the
remote SYSLOG service is not started on your LANTIME.
Please be aware of the fact that all SYSLOG entries of the timeserver are stored in /var/log/messages and
will be deleted when you power o or reboot the timeserver. A daily CRON job is checking for the size of the
LANTIME SYSLOG and deletes them automatically, if their size is exceeding a limit.
By specifying one or two remote SYSLOG servers, you can preserve the SYSLOG information even when you
have to reboot or switch o the LANTIME.
In the second section the possible network protocols and access methods can be con gured. You can enable/disable TELNET, FTP, SSH, HTTP, HTTPS, SNMP and NETBIOS by checking/unchecking the appropriate check
box. After you saved your settings with the Save button, all of these subsystems are stopped and restarted (if
they are enabled).
The third section allows you to select the IP protocol 6. In this version the IPv4 protocol is mandatory and
cannot be disabled, but a standalone IPv6 mode can be reached by entering an IPv4 address 0.0.0.0 and disabling the DHCP client option for every network interface of your LANTIME. By doing so, you ensure that the
timeserver cannot be reached with IPv4. Please note that TELNET, FTP and NETBIOS cannot be used over
IPv6 in this version. IPv4 and IPv6 can be used together on one LANTIME.
To manage the interface speci c parameters, you can enter the Ethernet Con guration Line page by using one of
the ETHERNET buttons. If your LANTIME is equipped with only one network interface, you will nd only one
button (ETHERNET 0). Otherwise you see one button for each installed Ethernet port.
66
Date: 17th February 2014
LANTIME M300 PZF
12.1 CLI Ethernet
Page 67
Here, the parameters for the network port can be changed. In the upper section of the page you can enter
the IPv4 parameters, the lower part gives you access to the IPv6 parameters of the interface.
IPv4 addresses are built of 32 bits, which are grouped in four octets, each containing 8 bits. You can specify an
IP address in this mask by entering four decimal numbers, separated by a point ..
Example: 192.168.10.2
Additionally you can specify the IPv4 Netmask and your default gateway address.
Please contact your network administrator, who will provide you with the settings suitable for your speci c network.
If you are running a DHCP (Dynamic Host Con guration Protocol) server in your network, the LANTIME system
can obtain its IPv4 settings automatically from this server. If you want to use this feature (you should also ask your
network administrator if this is applicable in your network), you can change the DHCP Client parameter to ENABLED. In order to activate the DHCP client functionality, you can also enter the IP address 000.000.000.000
in the LCD menu by using the front panel buttons of the LANTIME. This is the default setting.
The MAC address of your timeserver can be read in the LCD menu by pressing the NEXT button on the front
panel twice. This value is often used by the network administrator when setting up the DHCP parameters for
your LANTIME at the DHCP server.
If the DHCP client has been activated, the automatically obtained parameters are shown in the appropriate
elds (IPv4 address, netmask, gateway).
You can specify up to three IPv6 addresses for your LANTIME timeserver. Additionally you can switch o
the IPv6 AUTOCONF feature. IPv6 addresses are 128 bits in length and written as a chain of 16 bit numbers in
hexadecimal notation, separated with colons. A sequence of zeros can be substituted with :: once.
Examples:
"::"
"::1"
is the address, which simply consists of zeros
is the address, which only consists of zeros and a 1 as the last bit.
This is the so-called host local address of IPv6 and is the equivalent
to 127.0.0.1 in the IPv4 world
"fe80::0211:22FF:FE33:4455" is a typical so-called link local address, because it
uses the fe80 pre x.
In URLs the colon interferes with the port section, therefore IPv6-IP-addresses are written
in brackets in an URL: "http://[1080::8:800:200C:417A]:80/";
the last :80 simply sets the port to 80, the default http port)
If you enabled the IPv6 protocol, the LANTIME always gets a link local address in the format fe80:: . . . ., which
is based upon the MAC address of the interface. If a IPv6 router advertiser is available in your network and if
you enabled the IPv6 AUTOCONF feature, your LANTIME will be set up with up to three link global addresses
automatically.
The next parameter in this sub section is Netlink mode. This controls the port speed and duplex mode of
LANTIME M300 PZF
Date: 17th February 2014
67
Page 68
12 The Command Line Interface
the selected Ethernet port. Under normal circumstances, you should leave the default setting (autosensing)
untouched, until your network administrator tells you to change it.
The standard moniker for this technology is IEEE 802.3ad, although it is known by the common names of
trunking, port trunking, teaming and link aggregation. The conventional use of bonding under Linux is an implementation of this link aggregation. Only one link is used at any given time. At least two physical Ethernet
ports must be linked to one bonding group to activate this feature. The rst Ethernet Port in one bonding group
provides the IP-Address and the net mask of this new virtual device. The implementation of the LANTIME
Bonding feature will not replace the MAC address of the active ethernet port. Depending on the LINK state of
the ETH-port the IP address of the rst port in the bonding group will be set to the next ethernet port. All
services will be restarted automatically.
At this menu point it is possible to add each Ethernet port to a bonding group. At least two physical Ethernet ports must be linked to one bonding group to activate this feature. The rst Ethernet Port in one bonding
group provides the IP Address and the net mask of this new virtual device.
12.2 CLI Notification
Alarm events
On this page you can set up dierent noti cation types for a number of events. This is an important feature
because of the nature of a timeserver: running in the background. If an error or problem occurs, the timeserver
is able to notify an administrator by using a number of dierent noti cation types.
The LANTIME timeserver oers four dierent ways of informing the administrator or a responsible person about
nine dierent events: EMAIL send an e-mail message to a speci ed e-mail account, SNMP-TRAP sends a SNMP
trap to one or two SNMP trap receivers, WINDOWS POPUP MESSAGE sends a Winpopup message to one or
two dierent computers and DISPLAY shows the alarm message on a wall mount display model VP100/NET,
that is an optional accessory you can obtain from us.
"NTP not sync"
NTP is not synchronised to a reference time source
"NTP stopped"
NTP has been stopped (mostly when very large time osets occur)
"Server boot"
System has been restarted
"Receiver not responding"
No contact to the internal GPS receiver
"Receiver not sync"
Internal GPS clock is not synchronised to GPS time
"Antenna faulty"
GPS antenna disconnected
"Antenna reconnect"
GPS antenna reconnected
"Con g changed"
Con guration was changed by a user
Leap second announced
A leap second has been announced
Every event can use a combination of those four noti cation types, of course you can disable noti cation for
events by disabling all noti cation types. The con guration of the four noti cation types can be changed in
the upper section of the page, you can control which noti cation is used for which event by using the button
noti cation conditions in the lower part of the page.
68
Date: 17th February 2014
LANTIME M300 PZF
12.2 CLI Noti cation
Page 69
E-mail messages
You can specify the e-mail address which is used as the senders address of the noti cation e-mail (From: address),
the e-mail address of the receiver (To: address) and a SMTP smarthost, that is a mail server who is forwarding
your mail to the receiver. If your LANTIME system is connected to the internet, it can deliver those e-mails itself.
Additional e-mail recipients can be con gured with the button CC recipients. These settings cannot be altered
with the LC display buttons of the front panel.
Please note the following:
• The LANTIME hostname and domain name should be known to the SMTP smarthost
• A valid nameserver entry is needed
• The domain part of the From: address has to be valid
Windows Popup Messages
Most Microsoft Windows operating systems provide you
with a local noti cation tool.
You can send messages via the special Windows protocol in your local network. It is not necessary to enable
the NETBIOS protocol of the LANTIME in order to use
this noti cation. On the Windows client side it is necessary to activate the Microsoft Client for Windows
in the network con guration.
You can enter the Windows computer name of up to
two Windows PCs in the appropriate elds. Every message contains a time stamp and a plain text message:
SNMP-TRAP messages
Up to two SNMP trap receiver hosts can be con gured in this subsection, you may use IPv4 or IPv6 addresses
or specify a hostname. Additionally you have to enter a valid SNMP community string for your trap receiving
community. These are mostly independent from the SNMP community strings used for status monitoring and
con guration (see SNMP con guration on the Security page).
VP100/NET wall mount display
The VP100/NET wall display is an optional accessory for the LANTIME timeserver, it has an own integrated
Ethernet port (10/100 Mbit) and a SNTP client. The time of the display can be received from any NTP server
using the SNTP protocol, additionally the display is able to show text messages, which are sent by using special
software. The LANTIME can send an alarm message to one or two VP100/NET displays over the network,
whenever an event occurs, for which you selected the display noti cation type. An alarm message is shown three
times as a scrolling message.
Just enter the display's IP address and its serial number (this is used for authorization), which can be found
by pressing the red SET button on the back of the display four times. The serial number consists of 8 characters,
representing four bytes in hexadecimal notation.
LANTIME M300 PZF
Date: 17th February 2014
69
Page 70
12 The Command Line Interface
If you want to use the display for other purposes, you can send text messages to it by using our command
line tool send2display, which can be found on the LANTIME. This allows you to use the display by CRON jobs
or your own shell scripts etc. If you run the tool without parameters, a short usage screen is shown, explaining
all parameters it may understand. See appendix for a printout of this usage screen.
NTP Client Monitoring
You can monitor a group of NTP clients and supervise the time oset, the NTP stratum value and if the client
is reachable or not. With the button edit client list you can edit the list of clients to monitor. You can add the
TCP/IP address or the hostname of the client:
You can monitor the current states of the con gured clients:
12.3 CLI Security
On the Security page you can manage all security relevant parameters for your timeserver. In the rst section
Login the administration password can be changed, which is used for SSH, TELNET, FTP, HTTP and HTTPS
access.
The password is stored encrypted on the internal ash disk and can only be reset to the default value timeserver
by a factory reset, changing all settings back to the factory defaults. Please refer to the LCD con guration
70
Date: 17th February 2014
LANTIME M300 PZF
12.3 CLI Security
Page 71
section in this manual.
SSH Secure Shell Login
The SSH provides you with a secure shell access to your timeserver. The connection is encrypted, so no readable
passwords are transmitted over your network. The actual LANTIME version supports SSH1 and SSH2 over IPv4
and IPv6. In order to use this feature, you have to enable the SSHD subsystem and a security key has to be
generated on the timeserver by using the Generate SSH key button. Afterwards, a SSH client can connect to
the timeserver and opens a secure shell:
ssh root @ 192.168.16.111
The rst time you connect to a SSH server with an unknown certi cate, you have to accept the certi cate,
afterwards you are prompted for your password (which is con gured in the rst section of this page).
If you generate a new SSH key, you can copy and paste it into your SSH client con guration afterwards in order to
allow you to login without being prompted for a password. We strongly recommend to use SSH for shell access,
TELNET is a very insecure protocol (transmitting passwords in plain text over your network).
If you enabled SSH, your LANTIME automatically is able to use secure le transfer with SCP or SFTP protocol. The usage of FTP as a le transfer protocol is as insecure as using TELNET for shell access.
Generate SSL Certi cate for HTTPS
HTTPS is the standard for encrypted transmission of data between web browser and web server. It relies on X.509
certi cates and asymmetric crypto procedures. The timeserver uses these certi cates to authenticate itself to the
client (web browser). The rst time a web browser connects to the HTTPS web server of your LANTIME, you
are asked to accept the certi cate of the web server. To make sure that you are talking to your known timeserver,
check the certi cate and accept it, if it matches the one stored on the LANTIME. All further connections are
comparing the certi cate with this one, which is saved in your web browser con guration. Afterwards you are
prompted to verify the certi cate only when it changed.
By using the button Generate SSL certi cate for HTTP" you can create a new certi cate. Please enter your
organisation, name, mail address and the location in the upcoming form and press Generate SSL certi cate to
nally generate it.
NTP keys and certi cates
The fourth and fth section of the Security page allow you to create the needed crypto keys and certi cates for
secure NTP operation (please see NTP authentication below).
The function Generate new NTP public key is creating a new self-signed certi cate for the timeserver, which is
automatically marked as trusted.
Important note: This certi cate is depending on the hostname of your LANTIME, it is mandatory to recreate the certi cate after changing the hostname. The certi cates are build with the internal command ntp-keygen
-T (ntp-keygen is part of the installed NTP suite). Your LANTIME is using the /etc/ntp/ directory for storing
its private and public keys (this is called the keysdir). Please refer to the chapter NTP Autokey for further
information (below).
The two options Show NTP MD5 key and Edit NTP MD5 keys allow you to manage the symmetric keys
used by NTP. More about that can be found in the chapter about symmetric keys (below).
LANTIME M300 PZF
Date: 17th February 2014
71
Page 72
12 The Command Line Interface
12.4 CLI NTP Parameter
The NTP con guration page is used to set up the additional NTP parameters needed for a more speci c con guration of the NTP subsystem.
The default con guration of the timeserver consists of a local clock, which represents the hardware clock of
your LANTIME system and the GPS reference clock. The local clock is only chosen as the NTP time reference
after the GPS clock lost its synchronisation. The stratum level of this local clock is set to 12, this ensures that
clients recognise the switchover to the local clock and are able to eventually take further actions. The local clock
can be disabled.
Because the GPS reference clock is internally connected to the LANTIME system by using a serial connection, the accuracy using this way of synchronisation is around 1 ms. The high accuracy of the LANTIME
timeserver (around 10 microseconds) is available by using the ATOM driver of the NTP subsystem, which is directly interpreting the PPS (pulse per second) of the GPS reference clock. The default con guration looks like this:
# *** lantime ***
# NTP.CONF for GPS167 with UNI ERLANGEN
server
fudge
server
fudge
server
fudge
127.127.1.0
127.127.1.0 stratum 12
127.127.8.0 mode 135 prefer
127.127.8.0 time1 0.0042
127.127.22.0
127.127.22.0 ag3 1
#
#
#
#
#
#
local clock
local stratum
GPS167 UNI Erlangen PPS
relative to PPS
ATOM (PPS)
enable PPS API
enable stats
statsdir /var/log/
statistics loopstats
drift le /etc/ntp.drift
# Edit /mnt/ ash/ntpconf.add to add additional NTP parameters
72
Date: 17th February 2014
LANTIME M300 PZF
12.5 CLI Local
Page 73
12.4.1 CLI NTP Authentication
Please see the corresponding chapter in the web interface description.
12.5 CLI Local
Administrative functions
In the rst section there are several functions which may be used by the administrator. The button Reboot LANTIME is restarting the system, the built-in reference clock is not aected by this, only the included computer
system is rebooted, which may take up to 30 seconds.
With Manual con guration you are able to change the main con guration by editing the con guration le
by hand. After editing, press the Save le button to preserve your changes, afterwards you are asked if your
changes should be activated by reloading the con guration (this results in reloading several subsystems like NTPD,
HTTPD etc.).
The function Send test noti cation is generating a test alarm message and sends it using all con gured notify
possibilities (e-mail, WMail, SNMP-Traps, wall mount display).
You can use the function Save NTP drift le to copy the le /etc/ntp.drift to the internal ash disc of your
LANTIME. NTP is using this le to have the parameters for compensation of the incorrectness of the system
clock available directly after a restart. This results in a faster synchronisation process of the NTPD subsystem
after a system restart. You should use this function only, if the NTPD has been synchronized to the internal
reference clock for more than one day. This is done here at Meinberg directly before shipping the LANTIME unit
to our customers, so you do not need to use this function during normal operation. It may be applicable after a
software update.
The function Reset to factory defaults is setting all con guration parameters back to default values. The
regular le /mnt/ ash/global_con guration will be replaced with the le /mnt/ ash/factory.conf, but rst a
copy of the con guration is saved under /mnt/ ash/global_con guration.old for backup reasons. The default
password timeserver is replacing the actual password, too. After using this function, all certi cates should be
recreated because of the change of the unit's hostname.
Please be aware of the fact that the default con guration is not activated instantly. If you want to avoid setting up
the IP address of your unit by locally con guring it on site with the buttons of the front panel (meaning physical
presence of someone directly at the location of the LANTIME), you have to con gure the network parameters
of your LANTIME immediately after using the reset to factory defaults button. So, please proceed directly to
the Ethernet page and check/change the IP address and the possible access subsystems (HTTP for example) of
the LANTIME. The rst usage of Save settings will load the con guration from ash into memory and activate it.
User Management
For administration dierent users can be set up. 3 group memberships can be assigned to each user: the SuperUser has all properties for administration. The group membership Administrator can change all parameters via
the command line interface (CLI) con guartion tool and the WEB interface. The group Administrator cannot
use any Linux command in a Telnet, SSH or Terminal session. If the Administrator will login, the setup program
LANTIME M300 PZF
Date: 17th February 2014
73
Page 74
12 The Command Line Interface
will be started directly. After termination of the Setup program this user will be logout automatically. The group
membership Info has the same properties like the Administrator but cannot change any parameter.
The menu User Management allows you to set up dierent users with a password and the group membership.
To change the properties of an user you have to delete the old user and set up a new one. The user root cannot
be deleted and has always the membership of Super-User. The password of the user root can be set on the
security page.
Administrative information
The button List all messages displays the SYSLOG of the LANTIME completely. In this log all subsystems
create their entries, even the OS kernel. The SYSLOG le /var/log/messages is only stored in the system's ram
disk, therefore it is lost after a power o or restart. If you con gured an external SYSLOG server, all LANTIME
SYSLOG entries will be duplicated on this remote system and can be saved permanently this way.
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
15
15
15
15
15
15
15
15
15
15
13:35:17
13:35:17
13:35:17
13:35:17
13:35:17
13:38:36
13:38:36
13:45:36
14:01:11
14:01:17
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
LanGpsV4
ntpd[12948]: ntpd 4.2.0@1.1161-r Fri Mar 5 15:58:48 CET 2004 (3)
ntpd[12948]: signal_no_reset: signal 13 had ags 4000000
ntpd[12948]: precision = 3.000 usec
ntpd[12948]: kernel time sync status 2040
ntpd[12948]: frequency initialized 45.212 PPM from /etc/ntp.drift
lantime[417]: NTP sync to GPS
lantime[417]: NTP restart
proftpd[14061]: connect from 172.16.3.2 (172.16.3.2)
login[15711]: invalid password for `root' on `ttyp1' from `172.16.3.45'
login[15711]: root login on `ttyp1' from `172.16.3.45'
With List detailed version information a number of version numbers (including LANTIME software, operating
system and NTPD) are shown in a textbox.
The function List LANTIME Options shows the hardware options installed in your LANTIME.
Using the button List detailed GPS information gives you the possibility to check detailed GPS status information. The rst parameter indicates the time and date of the last update of the shown parameters. Next
you nd the GPS receiver status and the NTP status, followed by the GPS position data. The position uses
the Latitude / Longitude / Altitude format. Latitude and Longitude are shown in degrees, minutes and seconds,
Altitude is shown in meters above WGS84 ellipsoid.
The satellite section shows the numbers of satellites in view and the number of usable satellites (good SV).
Additionally, the selected set of the four used satellites can be read.
The accuracy of the calculated receiver position and time deviation is dependent on the constellation of the
four selected satellites. Using the position of the receiver and the satellites, a number of values can be calculated,
which allow a rating of the selected constellation. These values are called Dilutions of Precision (DOP).
PDOP is the abbreviation for Position Dilution of Precision, TDOP means Time Dilution of Precision and
GDOP stands for General Dilution of Precision. Lower values are indicating better accuracy.
The next section Satellite Info shows information about all the satellites, which are in view momentarily. The
satellite ID, elevation, Azimuth and distance to the receiver reveal the position of the satellite in the sky. The
74
Date: 17th February 2014
LANTIME M300 PZF
12.5 CLI Local
Page 75
Doppler shows whether the satellite is ascending (positive values) or descending (negative value).
Software Update
If you need to update the software of your LANTIME, you need a special le update.tgz from Meinberg, which
has to be uploaded to the LANTIME by using ftp, SCP or SFTP to the root dir (/update.tgz), after the le
transfer is complete, press Start rmware update.
Afterwards you are prompted to con rm the start of the update process. The scope of the update only depends on the chosen le.
LANTIME M300 PZF
Date: 17th February 2014
75
Page 76
13 SNMP Support
13 SNMP Support
The Simple Network Management Protocol (SNMP) has been created to achieve a standard for the management
of dierent networks and the components of networks. SNMP is operating on the application layer and uses
dierent transport protocols (like TCP/IP and UDP), so it is network hardware independent.
The SNMP design consists of two types of parties, the agent and the manager. SNMP is a client-server architecture, where the agent represents the server and the manager represents the client.
The LANTIME has an integrated SNMP agent, who is designed especially to handle SNMP requests for LANTIME
speci c status information (including status variables for the internal reference clock). The LANTIME SNMP
agent is also capable of handling SET requests in order to manage the LANTIME con guration via SNMP, if your
SNMP management software is also supporting this feature.
The elements (objects / variables) are organised in data structures called Management Information Base (MIB).
The LANTIME includes the standard NET-SNMP MIB and is based on SNMPv1 (RFC 1155, 1157), SNMPv2
(RFC 1901-1908) and SNMPv3.
The following SNMP version is installed on the timeserver:
Net-SNMP Version:
Network transport support:
SNMPv3 Security Modules:
Agent MIB code:
Authentication support:
Encryption support:
5.0.8
Callback Unix TCP UDP TCPIPv6 UDPIPv6
usm
mibII, ucd_snmp, snmpv3mibs,
noti cation, target, agent_mibs, agentx
agent_mibs, utilities, meinberg, mibII/ipv6
MD5 SHA1
DES
By using the special Meinberg SNMP-agent all important status variables can be read with SNMP conformant
client software. Where applicable, a variable is implemented as string and numeric value, for example allowing
SNMP client software to use the information for drawing diagrams or monitor threshold levels.
When using the NET-SNMP suite, you can read all status information your LANTIME oers via SNMP by
using the snmpwalk command:
snmpwalk v2c c public timeserver enterprises.5597
...mbgLtNtp.mbgLtNtpCurrentState.0 = 1 : no good refclock (->local)
...mbgLtNtp.mbgLtNtpCurrentStateVal.0 = 1
...mbgLtNtp.mbgLtNtpStratum.0 = 12
...mbgLtNtp.mbgLtNtpActiveRefclockId.0 = 1
...mbgLtNtp.mbgLtNtpActiveRefclockName.0 = LOCAL(0)
...mbgLtNtp.mbgLtNtpActiveRefclockOset.0 = 0.000 ms
...mbgLtNtp.mbgLtNtpActiveRefclockOsetVal.0 = 0
...mbgLtNtp.mbgLtNtpNumberOfRefclocks.0 = 3
...mbgLtNtp.mbgLtNtpAuthKeyId.0 = 0
...mbgLtNtp.mbgLtNtpVersion.0 = 4.2.0@1.1161-r Fri Mar 5 15:58:56 CET 2004 (3)
...mbgLtRefclock.mbgLtRefClockType.0 = Clock Type: GPS167 1HE
...mbgLtRefclock.mbgLtRefClockTypeVal.0 = 1
...mbgLtRefclock.mbgLtRefClockMode.0 = Clock Mode: Normal Operation
...mbgLtRefclock.mbgLtRefClockModeVal.0 = 1
76
Date: 17th February 2014
LANTIME M300 PZF
13.1 Con guration over SNMP
Page 77
...mbgLtRefclock.mbgLtRefGpsState.0 = GPS State: sync
...mbgLtRefclock.mbgLtRefGpsStateVal.0 = 1
...mbgLtRefclock.mbgLtRefGpsPosition.0 = GPS Position: 51.9834◦ 9.2259◦ 181m
...mbgLtRefclock.mbgLtRefGpsSatellites.0 = GPS Satellites: 06/06
...mbgLtRefclock.mbgLtRefGpsSatellitesGood.0 = 6
...mbgLtRefclock.mbgLtRefGpsSatellitesInView.0 = 6
...mbgLtRefclock.mbgLtRefPzfState.0 = PZF State: N/A
...mbgLtRefclock.mbgLtRefPzfStateVal.0 = 0
...mbgLtRefclock.mbgLtRefPzfKorrelation.0 = 0
...mbgLtRefclock.mbgLtRefPzfField.0 = 0
Please note that you only see the object names (like mbgLtRefclock.mbgLtRefPzfField) if you installed the
Meinberg MIB les on your client workstation rst (please see the web interface or CLI setup tool chapters to
nd out how to do this).
By using the standard MIB, no NTP get requests are allowed. Only the standard system and network parameters can be accessed (e.g. using the NET-SNMP command snmpget).
Only by using the Meinberg MIB the change of con guration parameters is possible (the command snmpset is
used to alter a variable, for example).
13.1 Configuration over SNMP
The LANTIME timeserver can be con gured via several user interfaces. Besides the possibility to setup its parameters with the web interface (HTTP and/or HTTPS) and the direct shell access via Telnet or SSH, a SNMP
based con guration interface is available.
In order to use the SNMP con guration features of the timeserver, you need to ful l the following requirements (the system has to be reachable over the network, of course):
a)
b)
c)
SNMP has to be activated in the timeservers setup by setting up a RWCOMMUNITY
In the SNMP con guration the read-write-access needs to be activated
The timeserver-speci c MIB les must be present on the clients,
they have to be included in the SNMP setup of the client software
a) and b) can be achieved by using the web interface or the shell access, please see the appropriate chapters in
this manual. The mentioned MIB les can be found directly on the timeserver located at /usr/local/share/snmp/mibs. All les with names starting with MBG-SNMP- have to be copied onto the SNMP clients by using
the timeservers ftp access (for example). You may also use the web interface, on the page "Local - LANTIME
Services" (V5) or "System - Services and Functions" (V6) you will nd a button "Download MIB les. You will
get a tar-archive if you are using the download button, which you have to unpack rst.
Afterwards, copy all MIB les to the MIB directory on your client(s) and con gure your SNMP client software to use them.
LANTIME M300 PZF
Date: 17th February 2014
77
Page 78
13 SNMP Support
13.1.1 Examples for the usage of the SNMP configuration features
The following examples are using the software net-snmp, a SNMP open source project. You will nd detailed
information at www.net-snmp.org!
To browse the con guration branch of the timeserver-MIB, you could use the following command on a UNIX
system with net-snmp SNMP tools installed:
root@testhost:/# snmpwalk -v 2c -c public timeserver.meinberg.de mbgLtCfg
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: LantimeSNMPTest
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgDomainname.0 = STRING: py.meinberg.de
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgNameserver1.0 = STRING: 172.16.3.1
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgNameserver2.0 = STRING:
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver1.0 = STRING:
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgSyslogserver2.0 = STRING:
[ ... ]
To alter a parameter, with net-snmp you would use the snmpset command:
root@testhost:/# snmpset -v 2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCfghostname.0 string helloworld
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: helloworld
root@testhost:/#
Please note that your SNMP request has to be sent with a su cient timeout (in the above snmpset example
this was achieved by using the -t 10 option, choosing a timeout of 10 seconds), because after each parameter
change, the timeserver reloads its con guration, which takes a few seconds. The request is acknowledged by the
SNMP agent afterwards.
To change a group of parameters without reloading the con guration after each parameter, you have to send all
parameter changes in one single request. You can do this with the net-snmp snmpset command by speci ying
multiple parameters in one command line:
root@testhost:/# snmpset -v 2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCfghostname.0 string helloworld mbgLtCfgDomainname.0 string
internal.meinberg.de
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfghostname.0 = STRING: helloworld
MBG-SNMP-LANTIME-CFG-MIB::mbgLtCfgDomainname.0 = STRING: internal.meinberg.de
root@testhost:/#
The available SNMP variables are described in detail in the SNMP con guration reference part of this manual.
Additionally, it is recommended to also read the mentioned MIB les.
78
Date: 17th February 2014
LANTIME M300 PZF
13.1 Con guration over SNMP
Page 79
13.1.2 Further configuration possibilities
Because the timeserver uses a standard version of the net-snmp SNMP daemon (with extended features covering
the timeserver-speci c functions), all con guration parameters of the SNMPD can be used. The con guration
le of the SNMP daemon is located at /usr/local/share/snmp after boot time, the lename is snmpd.conf.
During the boot sequence, this le is created dynamically by using a template le and appending the SNMP
parameters stored in the timeserver setup.
If you need to customize the con guration of the timeservers SNMPD (for setting up detailed access control
rights for example), you may edit /mnt/ ash/packages/snmp/etc/snmpd_conf.default (which is the mentioned template le). Please note that some lines are appended to this le (as described above), before it is used
as /usr/local/share/snmp/snmpd.conf by the snmpd process.
13.1.3 Send special timeserver commands with SNMP
The timeserver is capable of receiving special commands by SNMP in order to reboot the unit or reload its
con guration after you manually changed it. A special SNMP variable is reserved for this (mbgLtCmdExecute)
and has to be set to a special integer value for each command. The following commands are available:
Reboot(1)
Setting the mbgLtCmdExecute variable to value 1 will reboot the timeserver after a short waiting period of approximately 3-5 seconds.
FirmwareUpdate(2)
This command installs a previously uploaded (with FTP for example) rmware version.
ReloadCon g(3)
The parameters of the timeserver con guration (stored in
/mnt/ ash/global_con guration) are re-read and afterwards a number of subsystems (e.g. NTPD, HTTPD/HTTPSD,
SMBD) will be restarted in order to use those eventually changed settings. Please note that the SNMPD will not
be restarted by this command (you have to use reboot instead or restart it manually by killing the process and
starting it again in the shell).
GenerateSSHKey(4)
A new SSH key will be generated.
GenerateHTTPSKey(5)
A new HTTPS key will be generated.
ResetFactoryDefaults(6)
The con guration of the timeserver is reset to factory defaults, afterwards an automatic ReloadCon g is executed
in order to use these default settings.
GenerateNewNTPAutokeyCert(7)
A new key is generated, it can be used with the NTP AUTOKEY feature.
SendTestNoti cation(8)
A test message is sent by using all noti cation methods the timeserver has a con guration for (e.g. mail, winpopup, SYSLOG etc.).
A few examples:
(we are again using the snmpset command which comes with the net-snmp tools).
root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCmdExecute.0 int 1
MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: Reboot(1)
root@testhost:/#
LANTIME M300 PZF
Date: 17th February 2014
79
Page 80
13 SNMP Support
The command shown above is forcing the timeserver to reboot. Instead of using the integer value, you may also
enter the command name, as it is de ned in the MIB le MBG-SNMP-LANTIME-CMD.txt (and in the command
list above).
If you want the timeserver to reload it's con guration le (which you previously uploaded via FTP probably),
you would enter this command:
root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCmdExecute.0 int ReloadCon g
MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: ReloadCon g(3)
root@testhost:/#
Please pay attention to the options -r 0 (meaning no retries) and -t 10 (meaning timeout of 10 secs) in
the above examples. These options avoid multiple executions of the desired command, additionally they give your
snmpset command enough time to wait for an acknowledgement from the timeservers snmp agent.
80
Date: 17th February 2014
LANTIME M300 PZF
13.1 Con guration over SNMP
Page 81
13.1.4 Configuration of the timeserver with SNMP: Reference
The MIB of the timeserver includes the following parts:
SNMP Object
Name
Description
enterprises.5597
mbgSNMP
Root node of the Meinberg-MIB
mbgSNMP.3
MbgLANTIME
Root node of the LANTIME MIB
mbgLANTIME.1
mbgLtNtp
LANTIME NTP status variables
mbgLANTIME.2
mbgLtRefclock
LANTIME reference time source status variables
mbgLANTIME.3
mbgLtTraps
LANTIME SNMP traps
mbgLANTIME.4
mbgLtCfg
LANTIME con guration variables
mbgLANTIME.5
mbgLtCmd
LANTIME control commands
Further detailed information can be found in the Meinberg MIB les.
Reference of LANTIME SNMP con guration variables:
SNMP branch
Variable
Data type
Description
mbgLtCfgNetwork
mbgLtCfghostname
string
The hostname of the timeserver
mbgLtCfgDomainname
string
The Domainname of the timeserver
mbgLtCfgNameserver1
string
(IPv4
or
IP-address of rst nameserver
or
IP-address of second nameserver
IPv6-address)
mbgLtCfgNameserver2
string
(IPv4
IPv6-address)
mbgLtCfgSyslogserver1
string
(IPv4
IPv6-address
or
IP-address or hostname of rst syslog-
or
server
or
IP-address or hostname of second syslog-
or
server
hostname)
mbgLtCfgSyslogserver2
string
(IPv4
IPv6-address
hostname)
mbgLtCfgTelnetAccess
integer (0 = disabled,
1
=
Telnet access activated?
en-
abled)
mbgLtCfgFTPAccess
integer (0 = disabled,
1
=
FTP-access activated?
en-
abled)
mbgLtCfgHTTPAccess
integer (0 = disabled,
1
=
Webinterface activated?
en-
abled)
mbgLtCfgHTTPSAccess
integer (0 = disabled,
1
=
Encrypted webinterface activated?
en-
abled)
mbgLtCfgSNMPAccess
integer (0 = disabled,
1
=
SNMP-daemon activated?
en-
abled)
LANTIME M300 PZF
Date: 17th February 2014
81
Page 82
SNMP branch
13 SNMP Support
Variable
Data type
mbgLtCfgSambaAccess
integer (0 = disabled,
1
Description
=
LANManager-access activated?
en-
abled)
mbgLtCfgIPv6Access
integer (0 = disabled,
1
=
IPv6-protocol enabled?
en-
abled)
mbgLtCfgSSHAccess
integer (0 = disabled,
1
=
SSH-access activated?
en-
abled)
mbgLtCfgNTP
mbgLtCfgNtpServer1IP
string
(IPv4
IPv6-address
or
First external NTP-server
or
hostname)
mbgLtCfgNtpServer1KEY
integer
Link to the key which should be used for
the rst NTP-server
mbgLtCfgNtpServer2IP
string
(IPv4
IPv6-address
or
Second external NTP-server
or
hostname)
mbgLtCfgNtpServer2KEY
integer
Link to the key which should be used for
the second NTP-server
mbgLtCfgNtpServer3IP
string
(IPv4
IPv6-address
or
Third external NTP-server
or
hostname)
mbgLtCfgNtpServer3KEY
integer
Link to the key which should be used for
the third NTP-server
mbgLtCfgStratumLocal
integer(0..15)
Stratum-value
Clock
of
the
internal
system
clock of the timeserver
mbgLtCfgNTPTrustedKey
integer
Link to the key which should be used for
the internal reference time source
mbgLtCfgNTPBroadcastIP
string
(IPv4
or
IPv6-address)
mbgLtCfgNTPBroadcast
IP-address,
which has to be used for
NTP-broadcasts (or multicasts)
integer
Link to the key which should be used for
Key
outgoing NTP-broadcasts
mbgLtCfgNTPBroadcast
integer (0 = dis-
Autokey
abled,
1
=
Use autokey for NTP broadcasts?
en-
abled)
mbgLtCfgAutokeyFeature
integer (0 = disabled,
1
=
Use autokey feature of the NTP server?
en-
abled)
82
Date: 17th February 2014
LANTIME M300 PZF
13.1 Con guration over SNMP
SNMP branch
Page 83
Variable
Data type
mbgLtCfgAtomPPS
integer (0 = disabled,
1
Description
=
en-
(Liste
von
Atom PPS (pulse per second) activated?
abled)
mbgLtCfgEMail
mbgLtCfgEMailTo
string
EMail-addressn)
One or more (semicolon separated) email
address(es). which should receive warnings and alarm noti cations from the
timeserver
mbgLtCfgEMailFrom
string
(EMail-
address)
mbgLtCfgEMailSmarthost
string
The EMail-address which is used as the
senders address for email notifcations
(IPv4
IPv6-address
or
The SMTP-host, which is used for send-
or
ing mails
or
First host, which receives noti cations
or
sent as SMTP-traps
hostname)
mbgLtCfgSNMP
mbgLtCfgSNMPTrapRecei
string
ver1
IPv6-address
(IPv4
hostname)
mbgLtCfgSNMPTrapRecei
string
The SNMP community used when send-
ver1Community
ing SNMP-Traps to the rst host
mbgLtCfgSNMPTrapRecei
string
ver2
IPv6-address
(IPv4
or
Second host, which receives noti cations
or
sent as SMTP-traps
hostname)
mbgLtCfgSNMPTrapRecei
string
ver2Community
The SNMP community used when sending SNMP-Traps to the second host
mbgLtCfgSNMPRO
string
Community
The SNMP community, which has readonly access and therefore can be used to
only monitor status variables or con guration values (SNMP V2c)
mbgLtCfgSNMPRW
string
Community
The SNMP community, which has readwrite access and there for can be used
to monitor status variables and get/set
con guration values (SNMP V2c)
mbgLtCfgSNMPContact
string
Contact information (e.g. name of a contact person) of the timeserver
mbgLtCfgSNMPLocation
string
Location (e.g. building/room number) of
the timeserver
mbgLtCfgWinpopup
mbgLtCfgWMailAddress1
string
First receiver of noti cations sent as windows popup messages
mbgLtCfgWMailAddress2
string
Second receiver of noti cations sent as
windows popup messages
LANTIME M300 PZF
Date: 17th February 2014
83
Page 84
13 SNMP Support
SNMP branch
Variable
mbgLtCfgWalldisplay
mbgLtCfgVP100Display1IP string
Data type
(IPv4
IPv6-address
mbgLtCfgVP100Display
Description
or
hostname or IP-address of the rst wall-
or
mount display used for showing noti ca-
hostname)
tions
string (Hexstring)
The serial number of the rst wall mount
1SN
display
used
for
showing
noti cations
(can be found in the setup menu of the
display)
mbgLtCfgVP100Display
string
2IP
IPv6-address
mbgLtCfgVP100Display
(IPv4
or
hostname or IP-address of the second
or
wall mount display used for showing no-
hostname)
ti cations
string (Hexstring)
The serial number of the rst wall mount
2SN
display
used
for
showing
noti cations
(can be found in the setup menu of the
display)
mbgLtCfgNotify
mbgLtCfgNotifyNTPNot
string(combination)
Sync
Exactly one, none or a combination of
the following noti cation types:
email = sending an email
wmail = sending a winpopup-message
snmp = sending a SNMP-trap,
disp = showing on wall mount display,
syslog = sending a syslog-entry
for the event NTP not synchronized
mbgLtCfgNotifyNTP
string
Stopped
tion)
mbgLtCfgNotifyServer
string
Boot
tion)
mbgLtCfgNotifyRefclock
string
NotResponding
tion)
mbgLtCfgNotifyRefclock
string
NotSync
tion)
mbgLtCfgNotifyAntenna
string
Faulty
tion)
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event NTP Daemon stopped
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event Timeserver reboot
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event Refclock not ready
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event Refclock not synchron
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event GPS antenna not connected
or dammaged
mbgLtCfgNotifyAntenna
string
Reconnect
tion)
mbgLtCfgNotifyCon g
string
Changed
tion)
mbgLtCfgNotifyLeapSecond string
Announced
84
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event GPS antenna reconnected
(combina-
(see
mbgLtCfgNotifyNTPNotSync)
for
the event Con guration changed
(combina-
tion)
Date: 17th February 2014
(see
mbgLtCfgNotifyNTPNotSync)
for
the event Leap second announced
LANTIME M300 PZF
13.1 Con guration over SNMP
Page 85
SNMP branch
Variable
Data type
mbgLtCfgEthernet
mbgLtCfgEthernetIf0IPv4
string
Description
IP
address)
the timeserver
mbgLtCfgEthernetIf0IPv4
string (IPv4 Netz-
IPv4-netmask of rst network interface of
Netmask
maske)
the timeserver
mbgLtCfgEthernetIf0IPv4
string
Gateway
address)
(IPv4
(IPv4
IP-
IP-
IPv4-address of rst network interface of
IPv4-address of the default gateway of
the timeservers rst network interface
mbgLtCfgEthernetIf0DHCP integer (0 = dis-
Con gure the rst network interface of
Client
abled,
=
en-
the timeserver with DHCP?
(IPv6
IP-
First IPv6-IP-address of the timeservers
1
abled)
mbgLtCfgEthernetIf0IPv6
string
IP1
address)
mbgLtCfgEthernetIf0IPv6
string
IP2
address)
mbgLtCfgEthernetIf0IPv6
string
IP3
address)
mbgLtCfgEthernetIf0IPv6
integer (0 = dis-
Activate autoconf for the IPv6 - con g-
Autoconf
abled,
uration of the timeservers rst network
mbgLtCfgEthernetIf0
rst network interface
(IPv6
Second
IPv6-IP-address
of
the
time-
servers rst network interface
(IPv6
1
IP-
IP-
Third IPv6-IP-address of the timeservers
rst network interface
=
en-
abled)
interface?
integer (0..4)
Con guration of the network-speed and
NetlinkMode
duplex settings of the timeservers rst
network interface
0 = autosensing,
1 = 10Mbit/s half duplex,
2= 10Mbit/s full duplex,
3=100Mbit/s half duplex,
4=100Mbit/s full duplex
For all additional Ethernet interfaces of the timeserver, If0 only has to be replaced with Ifx, where x is
substituted by the number of the desired Ethernet interface. Example: The IPv4-address of the timeservers third
Ethernet interface can be set with mbgLtCfgEthernetIf2IPv4IP!
LANTIME M300 PZF
Date: 17th February 2014
85
Page 86
13 SNMP Support
13.2 SNMP Traps
If con gured, the LANTIME is sending SNMP traps, which can be received by up to 2 SNMP management systems. These traps can be received by using the NET-SNMP suite tool snmptrapd, you can start it on a UNIX
system with snmptrapd p (-p is for output to stdout, -s would use the syslog for output). The corresponding
MIB les can be found on the LANTIME at /usr/local/share/snmp/mibs/ , all Meinberg speci c MIB les are
named MBG-SNMP. . . . . These MIB les can be downloaded by using the web interface (see Local page,
Download MIB les button), after unpacking the archive le you can import the MIB les into your management
system.
The following SNMP-traps are available:
"NTP not sync"
NTP not synchronised to refclock
"NTP stopped"
NTP stopped
"Server boot"
System has rebooted
"Receiver not responding"
no answer from GPS
"Receiver not sync"
GPS receiver not synchronised
"Antenna faulty"
GPS antenna not connected
"Antenna reconnect"
GPS antenna reconnected
"Con g changed"
System parameter changed by user
Leap second announced
Leap second announced
See the Noti cation page at the web interface and Command Line Interface description to learn how to con gure
the SNMP trap receivers.
13.2.1 SNMP Trap Reference
All traps can be found under the mbgLtTraps section in the Meinberg MIB. A special trap exists for every noti cation event the timeserver knows. Please note that the traps are only sent if you con gured the noti cation type
SNMP trap for the event, otherwise no trap is generated. All traps have a string parameter included, which
contains the plain text event message for the appropriate event (you are able to change the default text messages,
see web interface and/or CLI setup section to nd out how to do this).
Here is a list of all traps the timeserver knows:
Whenever the NTP daemon (ntpd) looses sync, it will generate this trap and send it to the con gured SNMP trap receivers.
•
mbgLtTrapNTPNotSync (mbgLtTraps.1):
•
mbgLtTrapNTPStopped (mbgLtTraps.2):
or because of an error condition.
This trap is sent when the NTP daemon stopped, manually
After nishing the boot process, this trap is generated.
•
mbgLtTrapServerBoot (mbgLtTraps.3):
•
mbgLtTrapReceiverNotResponding (mbgLtTraps.4):
timeserver is not responding.
•
mbgLtTrapReceiverNotSync (mbgLtTraps.5):
ceivers will receive this trap.
This trap will be sent whenever the timeserver recognises a
broken connection to the antenna of the receiver.
mbgLtTrapAntennaFaulty (mbgLtTraps.6):
•
mbgLtTrapAntennaReconnect (mbgLtTraps.7):
established, this trap is sent.
mbgLtTrapCon gChanged (mbgLtTraps 8):
this trap.
•
•
After the connection to the antenna has been re-
After reloading its con guration, the timeserver generates
mbgLtTrapLeapSecondAnnounced (mbgLtTraps 9):
GPS receiver, this trap will be sent.
86
If the internal receiver looses sync, the SNMP trap re-
•
•
Trap to be sent when the internal receiver of the
If a leap second has been announced by the internal
This trap is sent whenever you are requesting a test
noti cation; it is only used for testing the connection between the timeserver and your SNMP trap receivers.
mbgLtTrapTestNoti cation (mbgLtTraps 99):
Date: 17th February 2014
LANTIME M300 PZF
Page 87
14 Attachment: Technical Information
14.1 Skilled/Service-Personnel only: Replacing the Lithium Battery
The life time of the lithium battery on the board is at least 10 years. If the need arises to replace the battery, the
following should be noted:
ATTENTION!
There is a Danger of explosion if the lithium battery is
replaced incorrectly. Only identical batteries or batteries recommended by the manufacturer must be used for
replacement.
The waste battery has to be disposed as proposed
by the manufacturer of the battery.
CE marking
This device follows the provisions
of the directives 93/68/EEC
LANTIME M300 PZF
Date: 17th February 2014
87
Page 88
14 Attachment: Technical Information
14.2 Technical Specifications M600/300 Multipac
HOUSING:
Metal desktop case, Schro 282T
Front panel: 1U/84HP (43 mm high / 442 mm wide)
LC-DISPLAY:
M300: 2 x 40 character, LC-Display
M600: 256 x 64 Dots, vacuum uorescent graphic display (VFD)
with backlight and function keys for menu control
POWER
SUPPLY:
100-240 VAC
Available DC variants:
! 100 - 240
!
12
!
24
!
48
VDC
VDC
VDC
VDC
INPUT FUSE:
Electronic
PROTECTION
RATING:
IP20
POWER
CONSUMPTION:
28W
PHYSICAL
DIMENSIONS:
-
+
442 mm wide x 43 mm high x 288 mm deep
(498 mm wide with mounting bracket, 85mm high as XL/2U model)
AMBIENT
TEMPERATURE:
0 ... 50 ◦ C
HUMIDITY:
85 % max.
88
DC Input
Date: 17th February 2014
LANTIME M300 PZF
14.3 Safety instructions for building-in equipment
Page 89
14.3 Safety instructions for building-in equipment
This building-in equipment has been designed and tested in accordance with the requirements of Standard
IEC60950-1 "Safety of Information Technology Equipment, including Electrical Business Equipment".
During installation of the building-in equipment in an end application (i.e. rack) additional requirements in
accordance with Standard IEC60950-1 have to be taken into account.
• The building-in equipment is a class 1 - equipment and must be connected to an earthed outlet
(TN Power System).
• The building-in equipment has been evaluated for use in o ce environment (pollution degree 2) and may be
only used in this environment. For use in rooms with a higher pollution degree more stringent requirements
are applicable.
• The building-in equipment may not be opened.
• Protection against re must be assured in the end application.
• The ventilation opening may not be covered.
• The equipment/building-in equipment was evaluated for use in a maximum ambient temperature of 40◦ C.
• For safe operation the building-in equipment must be protected by max 16 A fuse in the power installation
system.
• Disconnection of the equipment from mains is done by pulling the mains plug.
14.3.1 CE-Label
Low voltage directive:
2006/95/EC EN 60950-1
EMV-directive:
89/336EEC EN50081-1
Safety of Information Technology Equipment,
including Electrical Business Equipment
Electromagnetic compatibility.
Electromagnetic compatibility (EMC).
Generic emission standard.
Part 1: Residential, commercial and light industry
EN50082-2
Electromagnetic compatibility (EMC).
Generic immunity standard.
Part 2: Industrial environment
LANTIME M300 PZF
Date: 17th February 2014
89
Page 90
14 Attachment: Technical Information
14.4 Rear Panel Connectors
Name
Type
Signal
Cable
Network
RJ-45
Ethernet
shielded data line
PPS, 10 MHz
BNC
TTL
shielded koaxial line
COM 0 , COM 1
9pin. D-SUB
RS-232
shielded data line
Error
3pin. DFK
Relais
screw terminal
PZF
Antenna
BNC
77,5kHz
shielded koaxial line
power supply
power cord receptable
power supply cord
14.5 Pin Assignment: Serial Connectors
14.5.1 Serial Time String
1
TxD0_OUT
RxD0_IN
GND -
5
1
6
TxD1_OUT
RxD1_IN
9
GND -
COM0
5
6
9
COM1
The 9pin female connectors can be connected to a PC with a direct cable.
14.5.2 TERMINAL (Console)
To connect a serial terminal use 9 pin SUBD RS232 connector in the front panel. Via the serial terminal connection it is possible to con gure parameters with the command line interface. You have to use a NULL-MODEM
cable connecting to your PC or Laptop computer. You can use e.g. the standard Hyperterminal program shipped
with your Windows operating system. Con gure your terminal program with 38400 Baud, 8 Databits, no parity
and 1 Stopbit. The terminal emulation have to set to VT100. After connecting to the timeserver there will be
displayed the login message (press RETURN for rst connection; default user: root password: timeserver).
DSR_IN RTS_OUTCTS_INRI_IN-
6
9
1
5
-DCD_IN
-RXD_IN
-TXD_OUT
-DTR_OUT
-GND
TERM
90
Date: 17th February 2014
LANTIME M300 PZF
14.6 Error Relay
Page 91
14.6 Error Relay
On the back panel of the device you can nd a DFK connector labeled Error. This relay output is connected
to the TTL TIME_SYNC output of the reference clock (GPS, PZF, TCR, ...). If the internal reference clock
has been synchronized by its source (GPS, DCF77 or IRIG) the relay will switch to mode NO . In case of bad
antenna signal or the device has been switched o the relay falls back to mode NC.
Additionally the relay can be switched by one of the noti cation conditions. In the noti cation condition table via WEB or CLI interface you can select the relay out. The priority is on the TIME SYNC ERROR signal of
the receiver (refclock not sync). Relay state which will be set via noti cation conditions will be reseted by any
access via the WEB or CLI interface (if no TIME SYNC ERROR is active).
14.6.1 Technical Specification
SWITCHING VOLTAGE max.:
125 VDC
150 VAC
1A
SWITCHING CURRENT max.:
SWITCHING LOAD max.:
SWITCHING-CURRENT
UL/CSA:
RESPONSE TIME:
DC
AC
30 W
60 VA
0.46A
0.46A
1A
150V AC
65V DC
30V DC
ca.2ms
Error
Normal Operation: CO - NO connected
Error:
CO - NC connected
CO NO NC
Error
VCC
LANTIME M300 PZF
Date: 17th February 2014
91
Page 92
14 Attachment: Technical Information
14.7 Technical specifications PZF600
RECEIVER:
CONTROL OF
RECEPTION:
BATTERYBACKUP:
INTERFACES:
PULSE
OUTPUTS:
ACCURACY
OF PULSES:
PROPAGATION TIME
COMPENSATION:
STANDARD
FREQUENCIES:
Two seperate receiver channels for signal conversion and best
aquisition and tracking of the DCF77 signal.
Reception via external ferrite antenna AW02.
The DCF-signal is checked for minimum eld strength by microprocessor.
The result is indicated by LED. In addition, the value of the digitized eld
strength is displayed in menu 'FIELD'.
In case of power failure an internal realtime clock runs crystal-precise.
Important parameters are stored in the system-RAM.
Life time of lithium battery: 10 years minimum
Option: capacitance-backup for about 150 hours
Four independant asynchronous serial ports (internal RS232)
Active-high and active-low pulses per minute and per second, TTL-level,
pulse duration 200 ms
Time delay of two systems with a maximum distance of 50 km:
typ. 20µs, max. 50µs
Time shifting of successive pulses: max. 1.5µs
The signal delay is compensated if the distance of the receiver to the transmitter
is given.
10 MHz are synchronized to DCF by a digital PLL.
Accuracy in synchronized state: +/- 5·10-9 (short term stability)
Accuracy in unsynchronized state: 1·10-8 for one hour
77.5 kHz, 155 kHz und 310 kHz derived from receiver-PLL
Accuracy in synchronous state: +/- 5·10-7 (short term stability)
TERMINAL
CONNECTION:
BOARD
DIMENSIONS:
Blade-connector strip VG64, DIN 41612
Sub-miniatur coaxial HF-connector (SMB internal)
Eurocard size 100 mm x 160 mm, Epoxy 1,5 mm
Front panel 12TE (61 mm)
ANTENNA:
Ferrite antenna in plastic housing
HUMIDITY:
Relativ humidity 85 % max.
TEMPERATURE
RANGE:
0◦ - 60
POWER
SUPPLY:
+ 5 V, approx. 230 mA
92
◦
Celsius
Date: 17th February 2014
LANTIME M300 PZF
14.8 Technical Speci cations LAN CPU
Page 93
14.8 Technical Specifications LAN CPU
PROCESSOR:
AMD GeodeTM LX 800 (500 MHz, 128 KB L2 cache, 3.6 W)
MAIN MEMORY:
onboard 256 MByte
CACHE-MEMORY:
16 KB 2nd Level Cache
FLASHDISK:
1 GB
NETWORK
CONNECTOR:
10/100 MBIT with RJ45-Jack
SERIAl INTERFACE:
Four serial RS232-Ports 16550 compatible to FIFO
- RS232 9-pol. DSUB-male connector
- three RS232 male connector according to DIN 41612,
type C 96 ( only TxD, RxD, DCD)
PARALLEL
INTERFACE :
One LPT-Port male connector type C 96
VGA-CONNECTION:
10-pol pin contact strip
KEYBOARD
CONNECTION:
10-pol pin contact strip
STATE LEDs:
POWER
REQUIREMENTS:
- power supply
- 'Connect', 'Activity' and 'Speed' of the network connection
5 V +- 5 %, @ 1 A
FRONTPANEL:
LANTIME in 3U modular case
3U / 4 TE (128 mm high x 20,3 mm wide)
CONNECTOR:
According to DIN 41612, type C 96, rows a+b+c (male)
DSUB-plug (9-pol) RJ45-jack, USB Port
AMBIENT
TEMPERATURE:
0 ... 50 ◦ C
HUMIDITY:
85 % max.
LANTIME M300 PZF
Date: 17th February 2014
93
Page 94
14 Attachment: Technical Information
14.9 Time Strings
14.9.1 Format of the Meinberg Standard Time String
The Meinberg Standard Time String is a sequence of 32 ASCII characters starting with the STX (start-of-text)
character and ending with the ETX (end-of-text) character. The format is:
D:
dd.mm.yy;T:w;U:hh.mm.ss;uvxy
The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as de ned below:
dd.mm.yy
Start-Of-Text, ASCII Code 02h
sending with one bit occuracy at change of second
the current date:
dd
day of month
(01..31)
mm
month
(01..12)
yy
year of
the century (00..99)
w
the day of
the week
hh.mm.ss
the current
hh
mm
ss
uv
(1..7, 1 = Monday)
time:
hours
minutes
seconds
(00..23)
(00..59)
(00..59, or 60 while leap second)
clock status characters (depending on clock type):
u:
`#'
``
Clock has not synchronized after reset
(space, 20h)
Clock has synchronized after reset
v:
`*'
``
Clock currently runs on XTAL
(space, 20h)
Clock is syncronized with transmitter
x
time zone indicator:
`U'
``
y
anouncement of discontinuity of time, enabled during last hour before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
`A'
announcement of leap second insertion
``
(space, 20h) nothing announced
94
UTC
MEZ
`S'
Universal Time Coordinated, formerly GMT
European Standard Time, daylight saving disabled
MESZ European Summertime, daylight saving enabled
End-Of-Text, ASCII Code 03h
Date: 17th February 2014
LANTIME M300 PZF
14.9 Time Strings
Page 95
14.9.2 Format of the Uni Erlangen String (NTP)
The time string Uni Erlangen (NTP) of a GPS clock is a sequence of 66 ASCII characters starting with the STX
(start-of-text) character and ending with the ETX (end-of-text) character. The format is:
tt.mm.jj; w; hh:mm:ss; voo:oo; acdfg i;bbb.bbbbn lll.lllle hhhhm
The letters printed in italics are replaced by ASCII numbers whereas the other characters are part
of the time string. The groups of characters as de ned below:
Start-Of-Text, ASCII Code 02h
sending with one bit occuracy at change of second
dd.mm.yy
the current date:
dd
day of month
mm
month
yy
year of
the century
w
the day of
the week
(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday)
hh.mm.ss
the current time:
hh
hours
mm
minutes
ss
seconds
v
sign of the oset of local timezone related to UTC
oo:oo
oset of local timezone related to UTC in hours and minutes
ac
clock status characters:
a:
`#'
clock has not synchronized after reset
``
(space, 20h) clock has synchronized after reset
c:
``
(00..23)
(00..59)
(00..59, or 60 while leap second)
`*'
GPS receiver has not checked its position
(space, 20h) GPS receiver has determined its position
d
time zone indicator:
`S'
MESZ
``
MEZ
f
anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
``
(space, 20h) nothing announced
g
anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
`A'
announcement of leap second insertion
``
(space, 20h) nothing announced
i
leap second insertion
`L'
leap second is actually inserted
(active only in 60th sec.)
``
(space, 20h) no leap second is inserted
European Summertime, daylight saving enabled
European Standard Time, daylight saving disabled
The following information regarding the receiver position is set to zero
because receiver does not support this.
bbb.bbbb
latitude of receiver position in degrees
leading signs are replaced by a space character (20h)
LANTIME M300 PZF
Date: 17th February 2014
95
Page 96
14 Attachment: Technical Information
n
latitude, the following characters are possible:
`N'
north of equator
`S'
south d. equator
lll.llll
longitude of receiver position in degrees
leading signs are replaced by a space character (20h)
e
longitude, the following characters are possible:
`E'
east of Greenwich
`W'
west of Greenwich
hhhh
altitude above WGS84 ellipsoid in meters
leading signs are replaced by a space character (20h)
96
End-Of-Text, ASCII Code 03h
Date: 17th February 2014
LANTIME M300 PZF
14.9 Time Strings
Page 97
14.9.3 Format of the ATIS standard Time String
The ATIS standard Time String is a sequence of 23 ASCII characters terminated by a CR (Carriage Return)
character. The format is:
yymmddhhmmsswcc
The letters printed in italics are replaced by ASCII numbers whereas the other characters are part of the time
string. The groups of characters as de ned below:
Address of the receiver
code 7Fh
Originator of message
ASCII '0'
code 30h
Telegram number
ASCII '0'
code 30h
Command code
ASCII 'S' for SET
code 53h
Command code
ASCII 'A' for ALL
code 41h
Time status
ASCII 'C' for valid time
code 43h
yymmdd
the current date:
yy year of the century
mm month
dd day of month
(00..99)
(01..12)
(01..31)
hh:mm:ss
the current time:
hh hours
mm minutes
ss seconds
(00..23)
(00..59)
(00..59, or 60 while leap second)
w
the day of the week
(1..7, 1 = 31h = Monday)
cc
checksum in hex, built from all characters
including GID, ABS, TSQ, CC, ST, ...
Carriage Return, ASCII code 0Dh
(The standard interface con guration for this string type is 2400 baud, 7E1)
LANTIME M300 PZF
Date: 17th February 2014
97
Page 98
14 Attachment: Technical Information
14.9.4 Format of the SYSPLEX-1 Time String
The SYSPLEX1 time string is a sequence of 16 ASCII characters starting with the SOH (Start of Header) ASCII
controll character and ending with the LF (line feed, ASCII Code 0Ah) character. The format is:
ddd:hh:mm:ssq
The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as de ned below:
Start of Header (ASCII control character)
sending with one bit accuracy at change of second
ddd
day of year
hh:mm:ss
the current time:
hh
hours
mm
minutes
ss
seconds
q
Quality
indicator
(001..366)
(00..23)
(00..59)
(00..59, or 60 while leap second)
(space) Time Sync (GPS lock)
(?) no Time Sync (GPS fail)
Carriage-return (ASCII code 0Dh)
Line-Feed (ASCII code 0Ah)
98
Date: 17th February 2014
LANTIME M300 PZF
14.9 Time Strings
Page 99
14.9.5 Format of the SAT Time String
The SAT Time String is a sequence of 29 ASCII characters starting with the STX (start-of-text) character and
ending with the ETX (end-of-text) character. The format is:
dd.mm.yy/w/hh:mm:ssxxxxuv
The letters printed in italics are replaced by ASCII numbers whereas the other characters
are part of the time string. The groups of characters as de ned below:
Start-Of-Text, ASCII Code 02h
sending with one bit accuracy at change of second
dd.mm.yy
the current date:
dd
day of month
mm
month
yy
year of the century
w
the day of the week
(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday)
hh:mm:ss
the current time:
hh
hours
mm
minutes
ss
seconds
(00..23)
(00..59)
(00..59, or 60 while leap second)
xxxx
time zone indicator:
`UTC`
Universal Time Coordinated, formerly GMT
`CET`
European Standard Time, daylight saving disabled
`CEST'
European Summertime, daylight saving enabled
u
clock status characters:
`#'
clock has not synchronized after reset
``
(space, 20h) clock has synchronized after reset
v
anouncement of discontinuity of time, enabled during last hour
before discontinuity comes in eect:
` !'
announcement of start or end of daylight saving time
``
(space, 20h) nothing announced
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
End-Of-Text, ASCII Code 03h
LANTIME M300 PZF
Date: 17th February 2014
99
Page 100
14 Attachment: Technical Information
14.9.6 Format of the ABB SPA Time String
The ABB SPA Time String is a sequence of 32 ASCII characters starting with the characters
ending with the (Carriage Return) character. The format is:
">900WD"
and
yy-mm-tt_hh.mm;ss.f:cc
>900WD:
The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as de ned below:
yy-mm-tt
the current date:
yy
year of the century
mm
month
dd
day of month
_
(00..99)
(01..12)
(01..31)
Space (ASCII code 20h)
hh.mm;ss.f the current time:
hh
hours
mm
minutes
ss
seconds
f
milliseconds
(00..23)
(00..59)
(00..59, or 60 while leap second)
(000..999)
cc
Check sum. EXCLUSIVE-OR result of the previous characters,
displayed as a HEX byte (2 ASCII characters 0..9 or A..F)
Carriage Return, ASCII Code 0Dh
100
Date: 17th February 2014
LANTIME M300 PZF
14.9 Time Strings
Page 101
14.9.7 Format of the Computime Time String
The Computime time string is a sequence of 24 ASCII characters starting with the T character and ending with
the LF (line feed, ASCII Code 0Ah) character. The format is:
T:
yy:mm:dd:ww:hh:mm:ss
The letters printed in italics are replaced by ASCII numbers whereas the other
characters are part of the time string. The groups of characters as de ned below:
T
Start character
sending with one bit accuracy at change of second
yy:mm:dd
the current date:
yy
year of the century
mm
month
dd
day of month
ww
the day of the week
(00..99)
(01..12)
(01..31)
(01..07, 01 = monday)
hh:mm:ss
the current time:
hh
hours
mm
minutes
ss
seconds
(00..23)
(00..59)
(00..59, or 60 while leap second)
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
LANTIME M300 PZF
Date: 17th February 2014
101
Page 102
14 Attachment: Technical Information
14.9.8 Format of the NMEA 0183 String (RMC)
The NMEA String is a sequence of 65 ASCII characters starting with the `$GPRMC' character and ending with
the characters CR (carriage return) and LF (line-feed). The format is:
hhmmss.ss,A,bbbb.bb,n,lllll.ll,e,0.0,0.0,ddmmyy,0.0,a*hh
$GPRMC,
The letters printed in italics are replaced by ASCII numbers or letters where as the
other characters are part of the time string. The groups of characters as de ned below:
$
Start character, ASCII Code 24h
sending with one bit occuracy at change of second
hhmmss.ss
the current time:
hh
hours
mm
minutes
ss
seconds
ss
fractions
of seconds
A
Status
(00..23)
(00..59)
(00..59, or 60 while leap second)
(1/10 ; 1/100)
(A = time data valid)
(V = time data not valid)
The following information regarding the receiver position is set to zero
because receiver does not support this.
bbbb.bb
latitude of receiver position in degrees
leading signs are replaced by a space character (20h)
n
latitude, the following characters are possible:
`N'
north of equator
`S'
south d. equator
lllll.ll
longitude of receiver position in degrees
leading signs are replaced by a space character (20h)
e
longitude, the following characters are possible:
`E'
east of Greenwich
`W'
west of Greenwich
ddmmyy
the current date:
dd
day of month
mm
month
yy
year of
the century
(01..31)
(01..12)
(00..99)
a
magnetic variation
hh
checksum (EXOR over all characters except `$' and `*')
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
102
Date: 17th February 2014
LANTIME M300 PZF
14.10 Manual VP100/NET Display con guration
Page 103
14.10 Manual VP100/NET Display configuration
send2display Version 0.1
usage: send2display -h hostname -s serialnumber [options]
Valid options are:
-h,
-s,
-c,
-b,
-a,
-m,
-e,
-q,
-v,
-?,
host H
Uses H as the hostname of the display unit
serialnumber S Uses S as the serialnumber of the display (e.g. 03A00C7F)
clear M
Clear message M (0-31)
beep
Beeper sound while showing the message
clearall
Clear all messages of the display
message M
Create/change message M (0-31, default = 0)
executions E
Sets number of consecutive executions to E (1-9, default = 1)
quiet
Quiet mode (no program output to stdout/stderr)
verbose
Verbose mode (output of debugging info on stdout)
help
Show help message
De ning messages
a)
Static or ashing text:
You can de ne a maximum of 9 lines for a message.
Start with -(x) "text", where (x) represents the line number.
-1,
line1 "text"
Set text for line 1
-2,
line2 "text"
Set text for line 2
...
You can set the duration and mode for each line separately. Speci y the following
options directly after the text-de nition of a line:
-f,
-d,
b)
no ash
duration X
Change line mode to static (default is ashing)
Set the duration of the line to x seconds (default is 3 seconds)
Scrolling text:
You can de ne a maximum of 241 characters per scrolling message. If you want the message
to "softly" end, simply add some spaces to the end of your text (attention: text and
spaces must be no more than 241 chars in length).
-t,
scrolltext "text"
Set scrolltext
If you want the message (any type) to appear periodically, you can set the time interval with:
-D,
-H,
-M,
periodday D
periodhour H
periodminute M
Display message every D days
Display message every H hours
Display message every M minutes
(You can combine these options. Default is: message is displayed only once)
Possible error codes: 1=parameter error, 2=no ACK from display, 3=network error
Examples:
send2display -h 172.16.3.251 -s 0a03007f -m1 -e2 -1"Hello World" -d5 -2"what a nice day" -d3
(shows two lines of text (2 times), 1st line is shown for 5 seconds and 2nd line for 3 seconds)
send2display -h 172.16.3.251 -s 0a03007f -m1 -e1 -1"Oops" -H2 -M30
(shows one line of text every 2 hours and 30 minutes, a sound (beep)
can be heared while the message is displayed)
send2display -h 172.16.3.251 -s 0a03007f -c1
LANTIME M300 PZF
Date: 17th February 2014
103
Page 104
14 Attachment: Technical Information
(deletes the message 1, so no more beeps every 2:30 hrs ...)
send2display -h 172.16.3.251 -s 0a03007f -t"Hello world..." -e3
(shows a scrolling message with soft end, repeating it 3 times
104
Date: 17th February 2014
LANTIME M300 PZF
14.11 Global Con guration File
Page 105
14.11 Global Configuration File
This le contains all global parameters of the LANTIME. You can nd this le on the write protected ash disk
at /mnt/ ash/global_con guration:
##
# Con guration File #
##
# Con guration File Section
Con guration File Version Number:
Con guration File Last Change:
4.17
# Network Parameter Section
Hostname
Domainname
Default IPv4 Gateway
Default IPv6 Gateway
Nameserver 1
Nameserver 2
Syslogserver 1
Syslogserver 2
Telnet Port active
FTP Port active
SSH active
HTTP active
HTTPS active
SNMP active
SAMBA active
IPv6 active
[ASCII,50]
[ASCII,50]
[IP]
[IP]
[IP]
[IP]
[ASCII,50]
[ASCII,50]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
# NTP Section
External NTP Server 1 IP
External NTP Server 1 KEY
External NTP Server 1 AUTOKEY
External NTP Server 2 IP
External NTP Server 2 KEY
External NTP Server 2 AUTOKEY
External NTP Server 3 IP [ASCII,50]
External NTP Server 3 KEY
External NTP Server 3 AUTOKEY
NTP Stratum Local Clock
NTP Trusted Key
NTP AUTOKEY feature active
NTP ATOM PPS active
NTP Broadcast TCPIP
NTP Broadcast KEY
NTP Broadcast AUTOKEY
NTP Trust Time
[ASCII,50]
[NUM]
[BOOL]
[ASCII,50]
[NUM]
[BOOL]
:
[NUM]
[BOOL]
[NUM,0..15]
[NUM]
[BOOL]
[BOOL]
[IP]
[NUM]
[BOOL]
[NUM]
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
# EMail Section
EMail To Address
EMail From Address
EMail Smarthost
[ASCII,50]
[ASCII,50]
[ASCII,50]
:
:
:
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
:
:
:
:
# SNMP Section
SNMP Trap Receiver
SNMP Trap Receiver
SNMP Trap Receiver
SNMP Trap Receiver
LANTIME M300 PZF
Address 1
Community 1
Address 2
Community 2
LanGpsV4
py.meinberg.de
1
1
1
1
1
1
0
1
12
0
1
0
0
0
Date: 17th February 2014
105
Page 106
SNMP
SNMP
SNMP
SNMP
SNMP
106
14 Attachment: Technical Information
V3 User Name
Read Community String
Write Community String
Contact String
Location String
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
:
:
:
:
:
# Windows Messages Section
WMail Address 1
WMail Address 2
[ASCII,50]
[ASCII,50]
:
:
# VP100 Display Section
VP100 Display Address 1
VP100 Display Sernum 1
VP100 Display Address 2
VP100 Display Sernum 2
[ASCII,50]
[ASCII,50]
[ASCII,50]
[ASCII,50]
:
:
:
:
# Noti cation Section
Noti cation on NTP_not_sync
Noti cation on NTP_stopped
Noti cation on Server_boot
Noti cation on Refclock_not_respon.
Noti cation on Refclock_not_sync
Noti cation on Antenna_faulty
Noti cation on Antenna_reconnect
Noti cation on Con g_changed
Noti cation on Leap second announ.
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
:
:
:
:
:
:
:
:
:
# Ethernet Parameter Section
ETH0 IPv4 TCPIP address
ETH0 IPv4 NETMASK
ETH0 DHCP CLIENT
ETH0 IPv6 TCPIP address 1
ETH0 IPv6 TCPIP address 2
ETH0 IPv6 TCPIP address 3
ETH0 IPv6 Autoconf
ETH0 Net Link Mode
ETH0 Bonding Group
[IP]
[IP]
[BOOL]
[IP]
[IP]
[IP]
[BOOL]
[NUM,0:4]
[NUM,0:4]
:
:
:
:
:
:
:
:
:
root
public
Meinberg
Germany
0
0
1
1
Date: 17th February 2014
LANTIME M300 PZF
14.12 Global Option File
Page 107
14.12 Global Option File
This le contains all global options for special hardware con guration of the LANTIME. Do not modify this le.
You can nd this le on the write protected ash disk at /mnt/ ash/global_options:
#GLOBAL OPTIONS
NUMBER ETHERNET INTERFACES
SYSTEM LAYOUT
SYSTEM ADV LAYOUT
SYSTEM LANGUAGE
SYSTEM PARAMETER
SYSTEM DESIGN
LANTIME M300 PZF
:
:
:
:
:
:
1
0
0
0
server
0
Date: 17th February 2014
107
Page 108
14 Attachment: Technical Information
14.13 Third party software
The LANTIME network timeserver is running a number of software products created and/or maintained by open
source projects. A lot of people contributed to this and we explicitly want to thank everyone involved for her/his
great work.
The used open source software comes with its own license which we want to mention below. If one of the
licenses for a third party software product is violated, we will as soon as possible apply any changes needed in
order to conform with the corresponding license after we acknowledged about that violation.
If a license for one of the software products states that we have to provide you with a copy of the source
code or other material, we will gladly send it to you on data media via normal post or by e-mail upon request.
Alternatively we can provide you with a link to a download location in the internet, allowing you to download the
most actual version. Please note that we have to charge you for any incurred expenses if you choose to receive
the source code on data media.
14.13.1 Operating System GNU/Linux
The distribution of the GNU/Linux operating system is covered by the GNU General Public License (GPL), which
we included below.
More information about GNU/Linux can be found on the GNU website
www.gnu.org
and on the website of GNU/Linux
www.linux.org
14.13.2 Samba
The Samba software suite is a collection of programs, which implement the Server Message Block (SMB) protocol
for UNIX systems. By using Samba your Lantime is capable of sending Windows popup messages and serves
request for network time by clients using the NET TIME command.
The distribution of Samba is covered like GNU/Linux by the GNU General Public License, see below.
The website of the Samba project (or a mirror) can be reached at
www.samba.org
108
Date: 17th February 2014
LANTIME M300 PZF
14.13 Third party software
Page 109
14.13.3 Network Time Protocol Version 4 (NTP)
The NTP project, lead by David L. Mills, can be reached in the internet at www.ntp.org. There you will nd
a wealthy collection of documentation and information covering all aspects of the application of NTP for time
synchronization purposes. The distribution and usage of the NTP software is allowed, as long as the following
notice is included in our documentation:
*************************************************************************
*
*
* Copyright (c) David L. Mills 1992-2004
*
*
*
* Permission to use, copy, modify, and distribute this software
*
* and its documentation for any purpose and without fee is hereby
*
* granted, provided that the above copyright notice appears in all
*
* copies and that both the copyright notice and this permission
*
* notice appear in supporting documentation, and that the name
*
* University of Delaware not be used in advertising or publicity
*
* pertaining to distribution of the software without speci c,
*
* written prior permission. The University of Delaware makes no
*
* representations about the suitability this software for any
*
* purpose. It is provided "as is" without express or implied
*
* warranty.
*
*
*
*************************************************************************
LANTIME M300 PZF
Date: 17th February 2014
109
Page 110
14 Attachment: Technical Information
14.13.4 mini httpd
For our web based con guration tool (HTTP and HTTPS) we use mini_httpd from ACME Labs. The distribution
and usage of this program is free provided as long as the following notice appears in the documentation:
Copyright c 2000 by Jef Poskanzer (jef@acme.com). All rights reserved.
Redistribution and use in source and binary forms, with or without
modi cation, are permitted provided that the following conditions
are met:
1.
Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2.
Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS AS IS AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Find out more regarding mini_httpd at the ACME Labs homepage:
www.acme.com
110
Date: 17th February 2014
LANTIME M300 PZF
14.13 Third party software
Page 111
14.13.5 GNU General Public License (GPL)
Version 2, June 1991 - Copyright (C) 1989, 1991
Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not
allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast,
the GNU General Public License is intended to guarantee your freedom to share and change free softwareto
make sure the software is free for all its users. This General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to using it. (Some other Free Software
Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your
programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service
if you wish), that you receive source code or can get it if you want it, that you can change the software or use
pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask
you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies
of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And
you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) oer you this license which gives
you legal permission to copy, distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there
is no warranty for this free software. If the software is modi ed by someone else and passed on, we want its
recipients to know that what they have is not the original, so that any problems introduced by others will not
re ect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that
redistributors of a free program will individually obtain patent licenses, in eect making the program proprietary.
To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modi cation follow.
GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING,
DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder
saying it may be distributed under the terms of this General Public License. The "Program", below, refers to
any such program or work, and a "work based on the Program" means either the Program or any derivative work
under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with
modi cations and/or translated into another language. (Hereinafter, translation is included without limitation in
the term "modi cation".) Each licensee is addressed as "you".
Activities other than copying, distribution and modi cation are not covered by this License; they are outside
its scope. The act of running the Program is not restricted, and the output from the Program is covered only if
its contents constitute a work based on the Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium,
LANTIME M300 PZF
Date: 17th February 2014
111
Page 112
14 Attachment: Technical Information
provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and
give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option oer warranty
protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on
the Program, and copy and distribute such modi cations or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
a) You must cause the modi ed les to carry prominent notices stating that you changed the les and the
date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived
from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms
of this License.
c) If the modi ed program normally reads commands interactively when run, you must cause it, when started
running for such interactive use in the most ordinary way, to print or display an announcement including an
appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty)
and that users may redistribute the program under these conditions, and telling the user how to view a copy of
this License. (Exception: if the Program itself is interactive but does not normally print such an announcement,
your work based on the Program is not required to print an announcement.)
These requirements apply to the modi ed work as a whole. If identi able sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then
this License, and its terms, do not apply to those sections when you distribute them as separate works. But when
you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the
whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and
thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather,
the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work
based on the Program) on a volume of a storage or distribution medium does not bring the other work under the
scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed
under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written oer, valid for at least three years, to give any third party, for a charge no
more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily
used for software interchange; or,
c) Accompany it with the information you received as to the oer to distribute corresponding source code.
(This alternative is allowed only for noncommercial distribution and only if you received the program in object
code or executable form with such an oer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modi cations to it. For an
executable work, complete source code means all the source code for all modules it contains, plus any associated
interface de nition les, plus the scripts used to control compilation and installation of the executable. However,
as a special exception, the source code distributed need not include anything that is normally distributed (in either
source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which
the executable runs, unless that component itself accompanies the executable.
112
Date: 17th February 2014
LANTIME M300 PZF
14.13 Third party software
Page 113
If distribution of executable or object code is made by oering access to copy from a designated place, then
oering equivalent access to copy the source code from the same place counts as distribution of the source code,
even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this
License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you
under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants
you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law
if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on
the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying,
distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically
receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and
conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not
limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that
contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations,
then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit
royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance
of the section is intended to apply and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or
to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free
software distribution system, which is implemented by public license practices. Many people have made generous
contributions to the wide range of software distributed through that system in reliance on consistent application
of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this
License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit
geographical distribution limitation excluding those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this
License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from
time to time. Such new versions will be similar in spirit to the present version, but may dier in detail to address
new problems or concerns.
Each version is given a distinguishing version number. If the Program speci es a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either
of that version or of any later version published by the Free Software Foundation. If the Program does not specify
a version number of this License, you may choose any version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions
are dierent, write to the author to ask for permission. For software which is copyrighted by the Free Software
Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the
sharing and reuse of software generally.
LANTIME M300 PZF
Date: 17th February 2014
113
Page 114
14 Attachment: Technical Information
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE
PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED
IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.
SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
114
Date: 17th February 2014
LANTIME M300 PZF
14.14 USB Stick
Page 115
14.14 USB Stick
Most LANTIME M-Series products come with a USB interface for connectiong a USB storage device, e.g. a USB
stick. This USB stick can be used for dierent tasks in combination with the LANTIME:
Transfer con guration parameters
between dierent LANTIMEs
Keypad locking for secure using
the keypad of the LCD
Transfer of log les
Install Software Updates
Upload and download secure certi cates
(SSL, SSH) and passwords
When connecting the USB stick the LC Display will after a few seconds signal that the USB stick has been
detected and allows you to enter the USB menu with the OK button.
USB Memory Stick Main Menu
USB Stick Menu (OK to confirm)
Backup
Config.
USB↓ Stick
The desired menu function can be chosen
by usingto
↑ and
keys and it will be activated with the OK button.
You can leave this menu with removing the USB storage or with the "ESC" button.
USB Stick Menu (OK to confirm)
Write Diagn. File to USB Stick
USB Stick Menu (OK to confirm)
14.14.1 Menu Backup Configuration
to USB Stick
Lock Front Panel
In this submenu you can copy the con guration le from your LANTIME to the USB storage device.Now you can
USB Stick
to confirm).
nd this con guration on your USB storage
deviceMenu
under(OK
/Lantime/Con g/
Memory
Stick Main Menu
UnlockUSB
Front
Panel
USB Stick Menu (OK to confirm)
USB
Memory
Stick
Main
Menu
USB
Stick
Menu
(OK
to confirm)
Restore
Config.
and
REBOOT
Backup Config. to USB Stick
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Backup
Config.
USB
Stick
14.14.2 Menu Write Diagnostic
File File
totoUSB
Stick
Write Diagn.
to USB
Stick
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Write
Diagn.
File
to
USB
Stick
Lock Front Panel
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Lock Front
Panel
Unlock
Front
Panel
This submenu is an easy way to get the contents of the LANTIMEs diagnostic les. After you push the OK
button, the system will copy a le archive to your USB device: /ltdiag.tgz
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Unlock
Panel
RestoreFront
Config.
and REBOOT
USB Stick Menu (OK to confirm)
Restore Config. and REBOOT
LANTIME M300 PZF
Date: 17th February 2014
115
Page 116
14 Attachment: Technical Information
14.14.3 Keypad locking
USBfunction
Memorybuttons
StickofMain
Menu
The USB stick can be used for locking the
the LANTIME
LC Display. Activating this feature
the user cannot use the buttons without connecting the USB stick to the LANTIME. The access authorisation has
been realized with a password le on the USB stick /Lantime/keypad_lock. This password le will be compared
Menu to
(OK
to confirm)
with /mnt/ ash/con g/keypad_lockUSB
. So Stick
it is possible
manage
dierent LANTIME with one USB stick.
Backup Config. to USB Stick
The keypad locking will be activated with a submenu from the USB stick:
USB
Memory
Stick
Menu
USB
Stick
Menu
(OK Main
to confirm)
Write Diagn. File to USB Stick
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Backup
Config.
to USB Stick
Lock
Front
Panel
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Write Diagn.
File
to USB Stick
Unlock
Front
Panel
When activating this submenu the le /mnt/ ash/con g/keypad_lock will be copied to the internal ash. When
de-activating the keypad locking this le will be removed from the internal ash.
USB
USB Stick
Stick Menu
Menu (OK
(OK to
to confirm)
confirm)
Lock
Front
Panel and REBOOT
Restore
Config.
USB Stick Menu (OK to confirm)
Unlock Front Panel
USB Stick Menu (OK to confirm)
Restore Config. and REBOOT
NOTE:
Make sure, that you never loose the "Keypad_Lock" le or the USB storage device! If you have problems, please
contact Meinberg Radio clocks: Mail an info@meinberg.de .
14.14.4 Menu Restore Configuration
This command is for restoring the LANTIME con guration. The Timeserver restarts after this procedure.
OK
USB Stick Menu (OK to confirm)
Restore Config. and REBOOT
...
rebooting System...
Please remove the USB storage device when the display shows "rebooting system..."
116
Date: 17th February 2014
LANTIME M300 PZF
14.15 Reference
Page 117
14.15 Reference
[Mills88]
Mills, D. L., "Network Time Protocol (Version 1) - speci cation and implementation",
DARPA Networking Group Report RFC-1059, University of Delaware, July 1988
[Mills89]
Mills, D. L., "Network Time Protocol (Version 2) - speci cation and implementation",
DARPA Networking Group Report RFC-1119, University of Delaware, September 1989
[Mills90]
Mills, D. L., "Network Time Protocol (Version 3) - speci cation, implementation and analysis",
Electrical Engineering Department Report 90-6-1, University of Delaware, June 1989
Kardel, Frank, "Gesetzliche Zeit in Rechnernetzen", Funkuhren, Zeitsignale und Normalfrequenzen,
Hrsg. W. Hilberg, Verlag Sprache und Technik, Groÿ-Bieberau 1993
Kardel, Frank, "Verteilte Zeiten", ix Multiuser-Multitasking-Magazin, Heft 2/93,
Verlag Heinz Heise, Hannover 1993
LANTIME M300 PZF
Date: 17th February 2014
117
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.4 Linearized : No Page Count : 122 Page Mode : UseOutlines Author : Title : Subject : Creator : LaTeX with hyperref package Producer : pdfTeX-1.40.10 Create Date : 2014:02:17 12:07:48+01:00 Modify Date : 2014:02:17 12:07:48+01:00 Trapped : False PTEX Fullbanner : This is pdfTeX, Version 3.1415926-1.40.10-2.2 (TeX Live 2009/Debian) kpathsea version 5.0.0EXIF Metadata provided by EXIF.tools