Meinberg LANTIME M600/MRS/PTP User manual

Category
Networking
Type
User manual
MANUAL
LANTIME Firmware 6.18
Configuration+Management Manual
9th May 2016
Meinberg Radio Clocks GmbH & Co. KG
Table of Contents
1 Imprint 1
2 Safety instructions for building-in equipment 2
2.1 Skilled/Service-Personnel only: Replacing the Lithium Battery . . . . . . . . . . . . . . . . . . . . 3
2.2 CE-Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3 LANTIME: Quick Installation 4
4 LANTIME System Description 6
4.1 Network Configuration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 Input and Output Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.5 Network Time Protocol (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.5.1 NTP Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4.6 SNMP Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.6.1 Configuration over SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.6.2 SNMP Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.7 Third party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.7.1 Operating System GNU/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.7.2 Samba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.7.3 Network Time Protocol Version 4 (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.7.4 lighttpd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.7.5 GNU General Public License (GPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
5 Option: Precision Time Protocol (PTP) / IEEE1588 28
5.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
5.2 Functionality in Master Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.3 Functionality in Slave Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.4 PTPv2 IEEE 1588-2008 Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4.1 General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4.2 Network Layer 2 or Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.4.3 Multicast or Unicast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4.4 Two-Step or One-Step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4.5 End-To-End (E2E) or Peer-To-Peer (P2P) Delay Measurements . . . . . . . . . . . . . . 34
5.4.6 Mode Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
5.4.7 Message Rate Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4.8 ANNOUNCE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5.4.9 SYNC/FOLLOWUP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.10 (P)DELAY_REQUEST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.11 HQ Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6 LANTIME CPU 38
6.1 LANTIME CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
6.2 Technical Specifications LAN CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
7 LANTIME Diagnostic File 40
7.1 Download via Web GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
7.2 Download Diag-File via USB Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.3 Download via Command Line Interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
7.4 Content / most important Files in a Diagnostic Archive . . . . . . . . . . . . . . . . . . . . . . . . . 42
0
8 LANTIME Reference Clocks 45
8.1 GPS Satellite Controlled Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.1.1 GPS Clock Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
8.1.2 Technical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
8.1.3 Mounting the GPS Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
8.2 GPS/GLONASS satellite controlled clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.2.1 GLN Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8.2.2 Technical Specifications <b></b> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
8.2.3 40dB GPS-L1/GLONASS-L1/GALILEO-E1 Timing Antenna with Integrated Lightning
Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
8.2.4 RV-76G GPS/GLONASS Antenne for mobile Applications . . . . . . . . . . . . . . . . . . 56
8.3 GPS satellite controlled clock with MRS option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.3.1 MRS functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.4 General information PZF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.4.1 Features of PZF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.4.2 Technical specifications PZF600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.4.3 DCF77 Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.5 IRIG/AFNOR Time Code Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
8.5.1 Technical Specifications TCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.5.2 Description of IRIG-Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
8.5.3 Time Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
8.6 MSF Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.6.1 Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.6.2 DUT Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
8.6.3 Time and Date Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.6.4 Other Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
8.6.5 Features of MSF Radio Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
8.6.6 Technical specifications AM5xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
8.7 General information about WWVB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
8.7.1 Code Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
8.8 Time Zone and Daylight Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
8.9 Booting the Meinberg Receivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
8.10 Oscillator specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
9 Configuration User Interface 82
9.1 Introduction: Configuration LANTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
9.2 TERMINAL (Console) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
9.3 LANTIME Display Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
9.3.1 Description of the graphical menu: VF-Display . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.4 Root Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
9.5 Menu: Reference Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
9.5.1 Optional Menu Switch Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
9.5.2 Menu Option Setup MRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.5.3 Menu: Info Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
9.5.4 Receiver Status and Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
9.5.5 Menu: Setup Meinberg Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
9.5.6 Menu: Output Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9.5.7 Menu: Serial Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9.5.8 Setup Output Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9.5.9 Menu: Setup Time Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
9.5.10 Option: Setup Progr. Pulses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
9.5.11 Option: Synthesizer Frequency Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
9.6 Menu: Time Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.6.1 Menu NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
9.6.2 Option: Menu PTPv2 - IEEE 1588-2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
9.6.3 Optional Menu: 2nd Receivere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
9.7 Menu: Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.7.1 Menu: Setup Network Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.7.2 Menu: Setup IPv4 LAN Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9.7.3 Menu: Setup IPv6 Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.7.4 Menu: Link Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
9.7.5 Menu: Global Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
9.7.6 Menu: Network Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
9.8 Menu: System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
9.8.1 Menu: Set Time Zone of Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
9.8.2 Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
9.8.3 Menu System Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
9.8.4 Option: Fan Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
10 The graphical user interfaces 139
11 The WEB Interface 140
11.1 Configuration: Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
11.2 Configuration: Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.2.1 Network interface specific configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11.2.2 IPv4 addresses and DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
11.2.3 IPv6 addresses and autoconf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
11.2.4 High Availability Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
11.3 Configuration: Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.3.1 SYSLOG Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
11.3.2 E-mail messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.3.3 Windows Messenger Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
11.3.4 SNMP-TRAP messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.3.5 VP100/NET wall mount display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
11.3.6 User defined Alarm scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
11.3.7 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
11.3.8 Alarm events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
11.4 Configuration: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.4.1 HTTP Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.4.2 Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.4.3 SSH Secure Shell Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
11.4.4 Generate SSL Certificate for HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
11.4.5 SNMP Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
11.4.6 SHS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
11.5 Configuration: NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.5.1 General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
11.5.2 External NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
11.5.3 NTP Local Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
11.5.4 NTP Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
11.5.5 Show NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
11.5.6 NTP Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
11.5.7 NTP Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
11.5.8 NTP Autokey Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
11.5.9 NTP Leap Second Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
11.6 Configuration: PTP V2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
11.6.1 PTP Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.6.2 PTP Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
11.7 FDM - Frequency Deviation Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
11.7.1 FDM - Current State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
11.7.2 FDM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
11.7.3 Manual FDM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
11.8 Configuration: System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
11.8.1 Common Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
11.8.2 Web interface language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
11.8.3 Services and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
11.8.4 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
11.8.5 System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
11.8.6 Show System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
11.8.7 Firmware/Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.8.8 Download Diagnostic File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
11.8.9 Configuration and Firmware Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
11.8.10 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
11.8.11 Option: Fan Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
11.9 Configuration: Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
11.9.1 Statistical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
11.10Configuration: Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
11.10.1 MRS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
11.10.2 IRIG Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
11.10.3 Serial Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
11.10.4 Synthesiser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
11.10.5 Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
11.10.6 Enable Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
11.10.7 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
11.10.8 Receiver Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
11.11I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.11.1 Configuration: Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
11.11.2 Configuration: Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.12NTP Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
11.13Configuration: Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
12 Time Strings 227
12.1 Format of the Meinberg Standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
12.2 Format of the Meinberg GPS Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
12.3 Format of the Meinberg Capture String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
12.4 Format of the Uni Erlangen String (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
12.5 Format of the NMEA 0183 String (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
12.6 Format of the NMEA 0183 String (GGA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
12.7 Format of the NMEA 0183 Telegram (GLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
12.8 Format of the NMEA 0183 String (ZDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
12.9 Format of the ATIS standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
12.10Format of the SAT Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
12.11Format of the SPA Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
12.12Format of the ION Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
12.13Format of the RACAL standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
12.14Format of the Computime Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
12.15Format of the SYSPLEX-1 Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
13 USB Stick 244
13.1 Menu Backup Configuration to USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
13.2 Menu Write Diagnostic File to USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
13.3 Keypad locking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
13.4 Menu Restore Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
14 List of Literature 246
Date: 9th May 2016 LANTIME Firmware 6.18
1 Imprint
1 Imprint
Meinberg Funkuhren 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
Date: 2015-06-22
LANTIME Firmware 6.18 Date: 9th May 2016 1
2 Safety instructions for building-in equipment
This building-in equipment has been designed and
tested in accordance with the requirements of Stan-
dard 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.
LANTIME Railmount
NOTE: First attach the case to protective earth - be-
fore you connect the LANTIME OS6 Firmware with
the power line.
General Safety instructions
The building-in equipment has been evaluated for use in office 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 equipment/building-in equipment was evaluated for use in a maximum ambient temperature of 40
C.
The building-in equipment may not be opened.
Protection against fire must be assured in the end application.
The ventilation opening may not be covered.
For AC Supply 100-240VAC
The building-in equipment is a class 1 - equipment and must be connected to an earthed outlet
(TN Power System).
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 at the outlet. Don’t use the
connector at the module for disconnection from mains.
For DC Supply 100-240VDC
The device can be disconnected outside the unit in accordance with the regulations as in EN 60950 (e.g.
through primary side line protection).
Assembling and disassembling of the power connector is only allowed if the device is disconnected from
power supply (e.g. trough primary side line protection).
All feed lines are sufficiently protected and dimensioned.
Fuse: T3A
Connector Diameter: 1mm
2
- 2,5mm
2
/ 17AWG - 13AWG
2 Date: 9th May 2016 LANTIME Firmware 6.18
2 Safety instructions for building-in equipment
2.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 bat-
tery 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.
2.2 CE-Label
Low voltage directive: 2006/95/EC EN 60950-1
Safety of Information Technology Equipment,
including Electrical Business Equipment
Electromagnetic compatibility.
EMV-directive: 89/336EEC EN50081-1
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 Firmware 6.18 Date: 9th May 2016 3
3 LANTIME: Quick Installation
When booting the system the following messages will be displayed while dots will be counted up in the lower
line. After then Main Menu will be displayed with some important status informations after booting has finished.
Starting up
please wait ...
..........
NORMAL OPERATION
NTP: Offs. 2ms
Wed, dd.mm.yyyy
UTC 12:00:00
Sv Constellation
SV in view: 10
Good Svs : 9
Sel:01 21 16 22
GPS, MRS, GLN
PZF State
CORR. : 97
State : fine
Field : 105
PZF
Ref. State
State : sync
Field : 95
MSF, WWVB,
JJY ...
TCR PARAMETERS
Set IRIG Code:
B006/B007 (DC)
TCR
Refclk n.a.
NTP:not sync.
Wed, dd.mm.yyyy
UTC 12:00:00
GPS/GLONASS: If the satellite receiver remains asynchronous (Ref. Time LED is still red after 12 minutes)
the number of satellites in view and the good satellites are to check. The antenna has to be installed without
any obstructions to the sky. If the receiver has not synchronized (Ref. Time LED is still red after 12 minutes),
check the receiver status in the submenu Reference Time.
PZF: If the 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. The antenna has to be installed with the longer side to
direction of Frankfurt in Germany.
WWVB, MSF: If the long wave receiver remains asynchronous (Ref. Time LED is still red after 3 minutes) the
field value has to be checked. The antenna has to be installed so that the longer side points to the location of
the transmitter (WWVB in Fort Collins - Colorado, MSF in Anthorn - England).
TCR: If the time code receiver remains asynchronous (Ref. Time LED is still red after 1 minute) the se-
lected IRIG code and the cable (Input Impedance) are to check within the Reference Time submenu.
RDT: The time server will wait for the external time source after booting the system. Possible time sources are
external NTP server or serial RS232 time string on rear panel COM0 (Meinberg Standard Telegram 9600/7E2
or 9600/8N1 or Uni-Erlangen time string with 19200/8N1 or NMEA time string with 4800/8N1). With the NTP
Parameter submenu you can adjust several external NTP server.
4 Date: 9th May 2016 LANTIME Firmware 6.18
3 LANTIME: Quick Installation
For first time installation enter TCP/IP address, netmask and default gateway. To get an overview of the current
configuration press F2 from main menu. Press F2 again to enter SETUP configuration page. Please ask your
administrator for propper TCP/IP configuration:
->Interfaces<-
Global Cfg.
Services
Use Up and Down
to select Port:
lan0:0 #1
>172.100.000.001
>IPv4 Parameter<
IPv6 Parameter
Link Mode
> LAN Address <
LAN Netmask
Def. Gateway
Set LAN Address
IPv4 lan0:0
DHCP:[]enabled
172.100.000.001
OK OK
OK
OK
Select "Interfaces" and then press the OK button. Now you can select the appropriate network interface (eg.
lan0:0 is the first physical interface of your time server). Press the OK button and you can modify the network
parameters of the selected interface (IPv4, IPv6, Link Mode). Use the arrow keys to change the IP address, the
netmask and, if necessary, the default gateway.
NOTE: These settings are related to the first Ethernet connection (LAN0). 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
LANTIME Firmware 6.18 Date: 9th May 2016 5
4 LANTIME System Description
A LANTIME is a multi-purpose time and frequency synchronization solution with a flexible approach to support
a large number of synchronization requirements in different applications and network environments. The system
combines a powerful CPU with dedicated hardware like reference clocks or I/O modules, creating a powerful
network appliance that supports almost all commonly used time and frequency synchronization protocols and
signals.
The basic installation of a LANTIME Server is a very easy and straightforward process. After installing
the hardware, the network address, the netmask and the default gateway have to be configured to be able to
access the web GUI. If everything is set up correctl,y as soon as the device is reachable over the network, it
can start serving time via NTP and/or PTP.
In addition to the time sync protocols NTP and PTP, the LANTIME system supports a number of additional net-
work protocols primarily used for remote management of the system: HTTP(S), FTP, SSH and Telnet. Remote
configuration, status checks and other maintenance procedures like fimrware updates or configuration backups
can be controlled from any WEB browser. For security reasons, every protocol can be enabled or disabled for
each configured IP address, allowing to reduce potential attack vectors and effectively control access to the
device.
Status changes, alarms or other important events are logged in local log files and additionally can be forwarded
to external SYSLOG servers. A number of notification protocols are supported to integrate the LANTIME system
into already existing IT monitoring solutions. For example, SNMP traps or automatically generated e-mails
are two potential options for notifying IT administrators about important events.
Installing multiple LANTIME devices in one network is a way to create redundancy for important network
time synchronization services.
6 Date: 9th May 2016 LANTIME Firmware 6.18
4 LANTIME System Description
4.1 Network Configuration Concept
The LANTIME system supports a wide range of different network environments due to its flexible and powerful
network configuration concept. A separation between physical and logical ("virtual") interface configurations
covers almost all possible requirements for datacenters, telecommunication backhaul networks and industrial
network environments.
Each LANTIME server has at least one physical ethernet interface which is provided by the CPU module
(lan0). Additional network interfaces can be provided by network expansion cards (LNE or TSU cards) or on
backplanes (depending on model). These additional physical interfaces can be used to provide synchronization
services to multiple physical network segments, to separate management and synchronization networks or to
combine multiple ethernet interfaces to form redundant connections ("bonding"). The 6th generation of LANTIME
firmware (LTOS6) can manage up to 99 physical network interfaces as a theoretical maxmium.
Configuration of IPv4 and IPv6 addresses is done based on logical interface configurations. Each logical
interface is assigned to one physical ethernet port and can be configured to use one IEEE 802.1q VLAN ID. The
current firmware version supports up to 99 logical interfaces per server and all of those could be theoretically
assigned to a single physical port.
The network ports of TSU modules (for PTP and Hardware-NTP) are not providing this logical interface
functionality and are limited, at least in the current firmware version, to one IPv4/IPv6 address and one VLAN
ID per physical interface. Redundancy and connectivity to multiple network segments and VLANs can be
achieved by adding multiple TSU cards in a system.
For each logical interface the available netwokr services for synchronization (NTP, TIME, ..) and manage-
ment (HTTP, HTTPS, SSH, SNMP, TELNET, ...) can be enabled/disabled individually. This allows to only
provide synchronization on one IP address and remote access the unit for management tasks over a different IP
address.
4.2 Additional Features
external NTP timeserver
free configuration of NTP: thereby MD5 authentication and access control via address & mask restriction
extended menu guidance for configuration 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 certificates, log files
and configurations, keypad locking
4.3 User Interface
Terminal connection via serial interface, status LED
Web browser interface with graphical statistic of the one-day cycle offsets
Telnet or Secure Shell Login for password protected operation of the Linux operating system
FTP access for updating the operating system and downloading log files
Simple Network Management Protocol for automatically SNMP-Traps in case of alarm
SYSLOG messages can be passed to different computers
Configurable e-mail notification
Simulation of a synchronous radio clock in order to operate without antenna
LANTIME Firmware 6.18 Date: 9th May 2016 7
4.4 Input and Output Options
Additional Ethernet RJ45 connectors available (eight in 3U housing, four in 1U housing and eight addi-
tional 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
8 Date: 9th May 2016 LANTIME Firmware 6.18
4 LANTIME System Description
4.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 i s an
implementation of the actual version 3 [Mills90], based on the specification 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 different 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 i s the highest level. Timeservers at this level synchronize them-
selves 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 synchro-
nizes 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.
4.5.1 NTP Clients
The NTP software package was tested on different UNIX systems. Almost all UNIX-like systems come with a
pre-installed NTP client software. In order to use the LANTIME as an NTP server, it is required to add its
IP address to the client configuration. NTP client software are available for most other operating systems like
Microsoft Windows or MAC OS.
The following WEB site is recommended to get the latest version of NTP:
http://www.ntp.org
You can find more information on our web page at: https://www.meinbergglobal.com/english/sw/ntp.htm
LANTIME Firmware 6.18 Date: 9th May 2016 9
4.6 SNMP Support
The Simple Network Management Protocol (SNMP) has been created to achieve a standard for the manage-
ment of different networks and the components of networks. SNMP is operating on the application layer and
uses different 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 specific status information (including status variables for the internal reference clock). The LAN-
TIME SNMP agent is also capable of handling SET requests in order to manage the LANTIME configuration
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: 5.0.8
Network transport support: Callback Unix TCP UDP TCPIPv6 UDPIPv6
SNMPv3 Security Modules:usm
Agent MIB code: mibII, ucd_snmp, snmpv3mibs,
notification, target, agent_mibs, agentx
agent_mibs, utilities, meinberg, mibII/ipv6
Authentication support: MD5 SHA1
Encryption support: 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 offers 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.mbgLtNtpActiveRefclockOffset.0 = 0.000 ms
...mbgLtNtp.mbgLtNtpActiveRefclockOffsetVal.0 = 0
...mbgLtNtp.mbgLtNtpNumberOfRefclocks.0 = 3
...mbgLtNtp.mbgLtNtpAuthKeyId.0 = 0
...mbgLtNtp.mbgLtNtpVersion.0 = [email protected] 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
...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
10 Date: 9th May 2016 LANTIME Firmware 6.18
4 LANTIME System Description
...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 files on your client workstation first (please see the web interface or CLI setup tool chapters to
find out how to do this).
By using the standard MIB, no NTP get requests are allowed. Only the standard system and network param-
eters can be accessed (e.g. using the NET-SNMP command “snmpget”).
Only by using the Meinberg MIB the change of configuration parameters is possible (the command “snmpset
is used to alter a variable, for example).
4.6.1 Configuration over SNMP
The LANTIME timeserver can be configured 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 configuration interface is available.
In order to use the SNMP configuration features of the timeserver, you need to fulfil the following requirements
(the system has to be reachable over the network, of course):
a) SNMP has to be activated in the timeservers setup by setting up a RWCOMMUNITY
b) In the SNMP configuration the read-write-access needs to be activated
c) The timeserver-specific MIB files 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 files can be found directly on the timeserver located at /usr/local/share/sn-
mp/mibs. All files 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 find a button "Download MIB files“. You will
get a tar-archive if you are using the download button, which you have to unpack first.
Afterwards, copy all MIB files to the MIB directory on your client(s) and configure your SNMP client software
to use them.
LANTIME Firmware 6.18 Date: 9th May 2016 11
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 find detailed
information at www.net-snmp.org!
To browse the configuration 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 sufficient 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 configuration, which takes a few seconds. The request is acknowledged by
the SNMP agent afterwards.
To change a group of parameters without reloading the configuration 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 specifiying
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 configuration reference“ part of this
manual. Additionally, it is recommended to also read the mentioned MIB files.
12 Date: 9th May 2016 LANTIME Firmware 6.18
4 LANTIME System Description
Further configuration possibilities
Because the timeserver uses a standard version of the net-snmp SNMP daemon (with extended features covering
the timeserver-specific functions), all configuration parameters of the SNMPD can be used. The configuration
file of the SNMP daemon is located at /usr/local/share/snmp after boot time, the filename is snmpd.conf.
During the boot sequence, this file is created dynamically by using a template file and appending the SNMP
parameters stored in the timeserver setup.
If you need to customize the configuration of the timeservers SNMPD (for setting up detailed access control
rights for example), you may edit /mnt/flash/packages/snmp/etc/snmpd_conf.default (which is the mentioned
template file). Please note that some lines are appended to this file (as described above), before it is used as
/usr/local/share/snmp/snmpd.conf by the snmpd process.
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
configuration 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) firmware version.
ReloadConfig(3)
The parameters of the timeserver configuration (stored in
/mnt/flash/global_configuration) 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 configuration of the timeserver is reset to factory defaults, afterwards an automatic ReloadConfig 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.
SendTestNotification(8)
A test message is sent by using all notification methods the timeserver has a configuration for (e.g. mail, win-
popup, 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 Firmware 6.18 Date: 9th May 2016 13
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 defined in the MIB file MBG-SNMP-LANTIME-CMD.txt (and in the
command list above).
If you want the timeserver to reload its configuration file (which you previously uploaded via FTP proba-
bly), you would enter this command:
root@testhost:/# snmpset -v2c -r 0 -t 10 -c rwsecret timeserver.meinberg.de
mbgLtCmdExecute.0 int ReloadConfig
MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: ReloadConfig(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.
14 Date: 9th May 2016 LANTIME Firmware 6.18
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150
  • Page 151 151
  • Page 152 152
  • Page 153 153
  • Page 154 154
  • Page 155 155
  • Page 156 156
  • Page 157 157
  • Page 158 158
  • Page 159 159
  • Page 160 160
  • Page 161 161
  • Page 162 162
  • Page 163 163
  • Page 164 164
  • Page 165 165
  • Page 166 166
  • Page 167 167
  • Page 168 168
  • Page 169 169
  • Page 170 170
  • Page 171 171
  • Page 172 172
  • Page 173 173
  • Page 174 174
  • Page 175 175
  • Page 176 176
  • Page 177 177
  • Page 178 178
  • Page 179 179
  • Page 180 180
  • Page 181 181
  • Page 182 182
  • Page 183 183
  • Page 184 184
  • Page 185 185
  • Page 186 186
  • Page 187 187
  • Page 188 188
  • Page 189 189
  • Page 190 190
  • Page 191 191
  • Page 192 192
  • Page 193 193
  • Page 194 194
  • Page 195 195
  • Page 196 196
  • Page 197 197
  • Page 198 198
  • Page 199 199
  • Page 200 200
  • Page 201 201
  • Page 202 202
  • Page 203 203
  • Page 204 204
  • Page 205 205
  • Page 206 206
  • Page 207 207
  • Page 208 208
  • Page 209 209
  • Page 210 210
  • Page 211 211
  • Page 212 212
  • Page 213 213
  • Page 214 214
  • Page 215 215
  • Page 216 216
  • Page 217 217
  • Page 218 218
  • Page 219 219
  • Page 220 220
  • Page 221 221
  • Page 222 222
  • Page 223 223
  • Page 224 224
  • Page 225 225
  • Page 226 226
  • Page 227 227
  • Page 228 228
  • Page 229 229
  • Page 230 230
  • Page 231 231
  • Page 232 232
  • Page 233 233
  • Page 234 234
  • Page 235 235
  • Page 236 236
  • Page 237 237
  • Page 238 238
  • Page 239 239
  • Page 240 240
  • Page 241 241
  • Page 242 242
  • Page 243 243
  • Page 244 244
  • Page 245 245
  • Page 246 246
  • Page 247 247
  • Page 248 248
  • Page 249 249
  • Page 250 250
  • Page 251 251
  • Page 252 252

Meinberg LANTIME M600/MRS/PTP User manual

Category
Networking
Type
User manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI