Meinberg LANTIME M300 Manual
The Meinberg LANTIME M300 is a network time server that provides precise time synchronization to your TCP/IP network. It's powered by a GPS receiver, offering high accuracy timekeeping. The LANTIME M300 is easy to install and configure, coming with both physical buttons and a web interface for remote management. You can also monitor the device's status and configure alarms for potential issues.
Advertisement
Advertisement
MANUAL
LANTIME M300/GPS
NTP Server
29th July 2014
Meinberg Radio Clocks GmbH & Co. KG
Table of Contents
3 Network Timeserver with GPS synchronized time base
1
4
5
5
5
6
6
7
7
7
6 GPS satellite controlled clock
9
9
11
14
2
3
9 Booting the Single Board Computer
15
10 Configuration User Interface
16
10.3.3 Set GPS Receiver Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
0
10.5.1 SETUP POUT X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
10.5.9 PPS, PPM, PPH Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
11 The graphical user interfaces
39
40
12.3.4 Additional Network Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
12.4.3 Windows Popup Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.4 SNMP-TRAP messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.4.5 VP100/NET wall mount display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
12.5.4 Generate SSL Certicate for HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
12.6.2 NTP AUTOKEY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
12.10.3 PTP Network Conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
78
89
14.1.1 Examples for the usage of the SNMP conguration features . . . . . . . . . . . . . . . . 91
14.1.3 Send special timeserver commands with SNMP . . . . . . . . . . . . . . . . . . . . . . . 92
14.1.4 Conguration of the timeserver with SNMP: Reference . . . . . . . . . . . . . . . . . . . 94
15 Attachment: Technical Information
100
15.9.5 Assignment of CF Segment in IEEE1344 Code . . . . . . . . . . . . . . . . . . . . . . . . 114
Page 0
15.10.6 Format of the NMEA 0183 String (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . 123
15.10.7 Format of the NMEA 0183 String (GGA) . . . . . . . . . . . . . . . . . . . . . . . . . . 124
15.10.8 Format of the NMEA 0183 String (ZDA) . . . . . . . . . . . . . . . . . . . . . . . . . . 125
15.15.1 Menu Backup Conguration to USB Stick . . . . . . . . . . . . . . . . . . . . . . . . . . 140
144
0 Date: 29th July 2014 LANTIME M300/GPS
1 Impressum
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
Mail: [email protected]
Date: 2014-06-12
Page 1
LANTIME M300/GPS Date: 29th July 2014 1
Page 2 2 Quick Start
2
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:
GPS: NORMAL OPERATION Mon, 28.08.2011
NTP: Offs. PPS: -50us UTC 14:33:10
If the GPS receiver remains asynchronous (Refclock LED is still red after 12 minutes) the number of satellites in view and the good satellites are to check (press bottons ↓ , ok, ↓ , ok, → , ok from main menu). The antenna has to be installed without any obstructions to the sky.
SATELLITE CONSTELLATION
In view: 8 Good: 7 Sel: 05 22 17 09
For rst time installation enter TCP/IP address, netmask and default gateway. To get an overview of the current conguration press F2 from main menu. Press F2 again to enter SETUP conguration page. Please ask your administrator for propper TCP/IP conguration:
Global Cfg. Services
-> Interfaces <-
Select "Interfaces" and then press 3 times the OK button to change to IPV4 ETH0 conguration page to enter the IP address, netmask and the default gateway:
SETUP: Ipv4 LAN Parameter ETH0
Ipv4 ADDRESS: 192.168.10.200
NOTE: These settings are related to the rst Ethernet connection (ETH0).
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
Date: 29th July 2014 LANTIME M300/GPS
Page 3
3 Network Timeserver with GPS synchronized time base
The LANTIME (Local Area Network Time Server) provides a high precision time base to a TCP/IP network
(Stratum-1-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 and output conguration. A GPS or combined GPS/GLONASS receiver, a long wave receiver (like DCF77, MSF or WWVB) 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.
The LANTIME system is a set of equipment composed of a internal receiver, a single-board computer and a power supply, all installed in a metal 19 inch modular chassis and ready to operate. A simplied LINUX operating system is installed on the single-board computers ash disk. Eight push buttons and a display can be used to congure and monitor the time server.
After the network connection has been established the time server can also be congured and monitored remotely from a workstation via TELNET or FTP. An integrated web server enables access to the LANTIME by using an ordinary web browser.
LANTIME M300/GPS Date: 29th July 2014 3
4
Page 4 4 The Modular System LANTIME
4 The Modular System LANTIME
The system LANTIME is a set of equipment, composed of a reference clock (e.g.: GPS/GLONASS satellite controlled clock, DCF77 radio clock or IRIG/AFNOR time code reader), 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.
1 2 3 4 5 6
GPS: NORMAL OPERATION
NTP: Offset PPS: -4µs
Mon , dd.mm.yyyy
UTC 12: 00 : 00
F1
F2
OK
ESC
Ref. Time
Time Service
Network
Alarm
Terminal
USB
ENGLISH
1.
LC Display
2. Function buttons: 4-way navigation
Button; F1, F2, OK, ESC
3. Status LEDs: Ref. Time, Time Service,
Network, Alarm
4. Terminal port, RS232 Time String output
5. USB connector
6. 19” Mounting Rack
DEUTSCH
1.
LC - Display
2. Funktionstasten:
3. Status LEDs:
4 - Richtungen;
F1, F2, OK, ESC
Ref. Time, Time Service,
Network, Alarm
4. Terminal port, RS232 Zeitstring Ausgang
5. USB Anschluss
6. Haltewinkel für 19” Rackmontage
8 7 6 5 4 3 2 1
PPS Out
ETH1
ETH0
ETH3
ETH2
10MHz Out
100M 10M 100M 10M
ENGLISH
1. Power Supply (AC/DC)
2.
RS232 Output: serial interface, time telegram
3. Error relay output
4. GPS antenna
5. Pulse Per Second (PPS) output , 10MHz (TTL) output
6. for additional outputs (e.g. IRIG time code)
7. Option: LNE - additional network interfaces
8. Network interfaces ETH0, ETH1, 10/100 Mbit Rj45
COM1
Error
GPS
Antenna CO NO NC COM 0
DEUTSCH
1. Stromversorgungseingang
2.
RS232 Ausgang: serielle Schnittstellen, Zeittelegramme
3. Error: Störmelderelais Ausgang
4. GPS Antenne
5. Sekunden Impuls Ausgang, 10MHz Ausgang (TTL)
6. für weitere BNC Ausgänge
7. LNE Optional
8. Netzwerk Anschlüsse ETH0, ETH1, 10/100 Mbit Rj45
The implemented NTPD distributes the reference time from the used 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 congured 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 conguration 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.
Date: 29th July 2014 LANTIME M300/GPS
4.1 Supported Network Services
4.1 Supported Network Services
The following network services are provided via RJ45 10/100Base-T Ethernet (Auto sensing):
- NTP v2, v3, v4
- NTP broadcast mode
- NTP multicast
- NTP symmetric keys
- NTP Autokey
- Simple Network Time Protocol (SNTP)
- TIME
- SNMP v1,2,3 with extended SNMP-Agent and SNMP-Traps for NTP and reference clock status
- DHCP Client
- NFS
- TELNET
- FTP
- HTTP
- HTTPS with Openssl2
- SSH2 Secure Shell Login
- Alarm messages via e-mail
- IPv6 3 global IPv6 addresses congurable
Autoconf Feature to be disabled supported network services: NTP, HTTP, HTTPS, SNMP, SSH
- Windows net time via NETBIOS
- Winpopup (Window Mail)
Page 5
4.2 Additional Features
• external NTP timeserver
• free conguration of NTP: thereby MD5 authentication and access control via address & mask restriction
• extended menu guidance for conguration 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 certicates, log les and congurations, 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
• Congurable e-mail notication
• Simulation of a synchronous radio clock in order to operate without antenna
LANTIME M300/GPS Date: 29th July 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 notied 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 signicantly wrong time, although they were classied 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 signicantly 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: 29th July 2014 LANTIME M300/GPS
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 specication 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 congurations 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 congures the compilation of the NTP daemon and all tools.
congure
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/GPS Date: 29th July 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
server 172.16.3.35
# optional: Driftle
# local clock
# TCPIP address of LANTIME
# driftle /etc/ntp.drift
# optional: activate all messages in syslogle
# logcong =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 conguration).
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 -llogle
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 lan�me .GPS. 0 l l
36
36
64
64
3
1
0.00
0.00
0.000
60.1
7885
15875
with the following meaning:
remote:
red:
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: 29th July 2014 LANTIME M300/GPS
Page 9
6 GPS satellite controlled clock
A Meinberg GPS170 satellite controlled radio clock is used as a reference time base. The GPS170 satellite receiver clock provides extremely precise time. The clock has been developed for applications where conventional radio controlled clocks can not meet the growing demand for precision time. The advantage of the GPS clock is that it can provide highly precise time worldwide, 24 hours a day using the Global Positioning System.
The Global Positioning System (GPS) is a satellite-based radio-positioning, navigation, and time-transfer system. It was installed by the United States Department of Defense and provides two levels of accuracy: The
Standard Positioning Service (SPS) and the Precise Positioning Service (PPS). SPS has been made available to the general public, but the PPS is encrypted and only available for authorized (military) users.
GPS accurately measures the propagation time of signals transmitted from satellites to the user's receiver. A nominal constellation of 24 satellites together with 3 active spares, in six orbital planes at 20,000 km altitude provides a minimum of four satellites in view 24 hours a day at every point on the globe. Four satellites need to be received simultaneously to determine both the receiver position (x, y, z) and the receiver clock oset from
GPS system time. All the satellites are monitored by ground control stations which determine the exact orbit parameters and clock osets of the satellites' onboard atomic clocks. These parameters are uploaded to the satellites and become part of a navigation message, which is retransmitted by the satellites and passed on to the user's receiver.
The high precision orbit parameters of the satellites are called ephemeris parameters, and a reduced precision subset of the ephemeris parameters is called a satellite's almanac. While ephemeris parameters must be evaluated to compute the receiver's position and clock oset, almanac parameters are used to check which satellites are in view from a given receiver position at a given time. Each satellite transmits its own set of ephemeris parameters and almanac parameters of all existing satellites.
6.1 GPS Clock Features
The GPS clock module is a 100 mm x 160 mm microprocessor board, and is connected to the antenna/converter unit by a 50 ohm coaxial cable (refer to "Mounting the Antenna"). DC power to fed to the antenna/downconverter via the antenna cable. An optional antenna splitter is available to operate up to four receivers from a single antenna.
The navigation message coming in from the satellites is decoded by the GPS clcoks microprocessor in order to track the GPS system time with an accuracy of better than 500 ns (or 250 nsec OCXO). Compensation of the RF signal's propagation delay is done by automatic determination of the receiver's position on the globe. A correction value computed from the satellites' navigation messages increases the accuracy of the board's TCXO or OCXO to 10 -9 and automatically compensates for the oscillators aging. The last recent value is restored from the battery buered memory at power-up.
LANTIME M300/GPS Date: 29th July 2014 9
Page 10 6 GPS satellite controlled clock
6.2 Time Zone and Daylight Saving
GPS system time diers from the universal time scale (UTC) by the number of leap seconds which have been inserted into the UTC time scale since GPS was initiated in 1980. The current number of leap seconds is part of the navigation message supplied by the satellites, so the internal real time of the GPS170 is based on UTC time scale. Conversion to local time and annual daylight saving time can be done by the receiver's microprocessor if the corresponding parameters are set up by the user.
10 Date: 29th July 2014 LANTIME M300/GPS
Page 11
7 Mounting the GPS Antenna
The GPS satellites are not stationary, but circle round the globe with a period of about 12 hours. They can only be received if no building is in the line-of-sight from the antenna to the satellite, so the antenna/downconverter unit must be installed in a location that has as clear a view of the sky as possible. The best reception is achieved when the antenna has a free view of 8 ◦ angular elevation above the horizon. If this is not possible, the antenna should be installed with the clearest free view to the equator, because the satellite orbits are located between
◦ latitudes 55 ◦ North and 55 South. If this is not possible, you may experience diculty receiving the four satellites necessary to complete the receiver's position solution.
The antenna/converter unit can be mounted on a wall, or on a pole up to 60 mm in diameter. A 45 cm plastic tube, two wall-mount brackets, and clamps for pole mounting are included with every GPS170. A standard
RG58 coaxial cable should be used to connect the antenna/downconverter unit to the receiver. The maximum length of cable between antenna and receiver depends on the attenuation factor of the coaxial cable.
Up to four GPS170 receivers can be run with one antenna/downconverter unit by using an optional antenna splitter. The total length of an antenna line from antenna to receiver must not be longer than the max. length shown in the table below. The position of the splitter in the antenna line does not matter.
High voltage protectors must be installed directly after reaching the indoors. The optional delivered protection kit is not for outdoor usage.
7.1 Example:
Type of cable diameter Ø Attenuation at 100MHz max lenght.
[mm] [dB]/100m [m]
RG58/CU 5mm 17 300
(1)
RG213 10.5mm
7 700
(1)
(1)This specications are made for antenna/converter units produced after January, 2005
The values are typically ones; the exact ones are to nd out from the data sheet of the used cable
LANTIME M300/GPS Date: 29th July 2014 11
Page 12 7 Mounting the GPS Antenna
7.2 Antenna Assembly with Surge Voltage Protection
Optional a surge voltage protector for coaxial lines is available. The shield has to be connected to earth as short as possible by using the included mounting bracket. Normally you connect the antenna converter directly with the antenna cable to the system.
12 Date: 29th July 2014 LANTIME M300/GPS
7.3 Antenna Short-Circuit
7.3 Antenna Short-Circuit
(optional for displayed systems)
In case of an antenna line short-circuit the following message appears in the display:
Page 13
ANTENNA
SHORT-CIRCUIT
DISCONNECT POWER
! ! !
If this message appears the clock has to be disconnected from the mains and the defect eliminated. After that the clock can be powered-up again. The antenna supply voltage must be 15V
DC
.
LANTIME M300/GPS Date: 29th July 2014 13
Page 14 8 Booting the GPS170 receiver
8 Booting the GPS170 receiver
If both the antenna and the power supply have been connected, the system is ready to operate. About 2 minutes after power-up the receiver's oscillator has warmed up and operates with the required accuracy. If the receiver nds valid almanac and ephemeris data in its battery buered memory and the receiver's position has not changed signicantly since its last operation, the receiver can determine which satellites are presently in view. Only a single satellite must be received to synchronize and generate output pulses, so synchronization can be achieved within one minute after power-up.
If the receiver position has changed by more than one hundred kilometers since last operation, the satellites' real elevation and Doppler might not match those values expected by the receiver, and this will force the receiver to start scanning for satellites. This mode is called Warm Boot because the receiver can obtain ID numbers of existing satellites from the valid almanac. When the receiver has found four satellites in view it can update its new position and switch to Normal Operation. If the almanac has been lost (because the battery has been disconnected) the receiver has to scan for a satellite and read in the current almanac. This mode is called Cold
Boot. It takes 12 minutes until the new almanac is complete and the system switches to Warm Boot mode, scanning for other satellites.
14 Date: 29th July 2014 LANTIME M300/GPS
Page 15
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 dened 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 GPS and the NTPD (NTP daemon) is started. After that NTPD starts synchronization with the reference clocks (usual the hardware clock of the single board computer and the GPS receiver). Until synchronization is nished the following message is displayed:
GPS: NORMAL OPERATION Mon, 28.08.2006
NTP: sync to local UTC 14:33:10
GPS: NORMAL OPERATION Mon, 28.08.2006
NTP: not sync UTC 14:33:10
For the synchronization of the NTPD with the GPS it is necessary that the GPS receiver is synchronous with the
GPS time. In this case the following message is monitored on the display:
GPS: NORMAL OPERATION Mon, 28.08.2011
NTP: Offs. PPS: -50us UTC 14:33:10
The second line shows the user that the NTPD is synchronized with the GPS with an oset of -50us. Because of the internal time of the NTP which is adjusted by a software PLL (phase locked loop) it takes a certain time to optimise this oset. The NTPD tries to keep the oset below +-128 ms; if the oset becomes too large the system time is set with the GPS time. Typically values for the oset are +-5 ms after the NTPD has already synchronized.
LANTIME M300/GPS Date: 29th July 2014 15
Page 16 10 Conguration User Interface
10 Configuration User Interface
10.1 Introduction: Configuration LANTIME
There are several ways to congure 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 congure 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 congured 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 congured with DHCP/Autoconf, further conguration 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 conguration program is started.
To set up a SSH connection the following commands are entered: ssh [email protected] // LANTIME IP address password: timeserver
With setup the conguration 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
16 Date: 29th July 2014 LANTIME M300/GPS
10.2 Root Menu Page 17
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 reect 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.
GPS: NORMAL OPERATION Mon, xx.xx.xxxx
NTP: Offs. GPS: 3us CET 12:00:00
F1
F2
OK
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 reect the current state of the device:
Ref. Time
Time Service
Network
Alarm
Ref. Time green: red: the reference clock (e.g. integrated GPS170) produce valid time.
the reference clock produce no valid time (e.g. not synchronized)
Time Service green: red:
NTP has been synchronized to reference clock.
NTP is not synchronous to reference clock or sync to local clock
Network green: red: 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
Alarm o: ret: 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 GPS170 M3x V6.xx x.x.xx
SN:030100000000 NTP: 4.2.6
The following main menus will be displayed when pressing the UP and DOWN arrow buttons:
LANTIME M300/GPS Date: 29th July 2014 17
Page 18 10 Conguration User Interface
GPS: NORMAL OPERATION Thu, XX.XX.XXXX
NTP: Offs. GPS: 2us CET 14:00:00
F
1
-> Reference Time <- Network
Time Service System
OK
-> Setup GPS <- Setup Outputs
Info GPS
Reference Time Network
-> Time Service <- System
OK
-> external NTP <- Restart NTP
Local Stratum
Reference Time -> Network <-
Time Service System
OK
-> G lobal Cfg.
<- Services
Interfaces
Reference Time Network
Time Service -> System <-
OK
->Set Time Zone<- Restart Menu
Factory Defaults
18 Date: 29th July 2014 LANTIME M300/GPS
10.3 Menu: Reference Time Page 19
10.3 Menu: Reference Time
The Reference Clock menu and all its sub menus will manage all status information and parameters of the reference clock.
-> Reference Time <- Network
Time Service System
OK
-> Setup GPS <- Setup Outputs
Info GPS
OK
-> Setup GPS Receiver Parameters <-
Init GPS Receiver
Setup GPS Setup Outputs
-> Info GPS <-
OK
->GPS Status <- GPS Satellites
GPS Position GPS Version
Setup GPS -> Setup Outputs <-
Info GPS
OK
->Output Options<- Serial Outputs
IRIG Output Pulses Outputs
OK
-> Enable Outputs <-
Setup Output Time Zone
To enter the following sub menus press the OK or right arrow button.
10.3.1 Setup GPS Receiver Parameters
-> Setup GPS Receiver Parameters <-
Init GPS Receiver
OK
-> Setup GPS Antenna Length <-
Setup GPS Simulation Mode
10.3.2 Set Antenna Cable Length
This menu asks the user to enter the length of the antenna cable. The received time frame is delayed by approx.
5ns per meter antenna cable. The receiver is able to compensate this delay if the exact cable length is given. The default value is 20m. The maximum value that can be entered is 500 m (only with low loss cable).
Set Antenna Cable Length
of GPS receiver: 020m
LANTIME M300/GPS Date: 29th July 2014 19
Page 20 10 Conguration User Interface
10.3.3 Set GPS Receiver Simulation Mode
Enabling this menu lets the user run the LANTIME without antenna. Normally the NTPD loses synchronization with the GPS when the antenna is disconnected or the GPS did not receive enough satellites (red Ref.Time LED is turned on). When Simulation Mode is enabled the status information from the GPS is xed to SYNC. So it is possible to set the NTPD with any other time entered by the SETUP INITIAL TIME menu. Usually this menu should be disabled. If this option is enabled an "*" will be shown behind the time string in the root menu.
Set GPS Receiver Simulation Mode
disabled
10.3.4 Init GPS Receiver
Setup GPS Receiver Parameters
-> Init GPS Receiver <-
OK
->GPS Cold Boot<- Init GPS Position
GPS Warm Boot Init GPS Time
10.3.5 Initiate Cold Boot of GPS Receiver
This menu lets the user initialize all GPS data's, e.g. all saved satellite data will be cleared. The user has to acknowledge this menu again before the initialization starts. The system starts operating in the COLD BOOT mode and seeks for a satellite to read its actual parameters.
Initiate COLD BOOT of GPS receiver
Press F2 to confirm
10.3.6 Initiate Warm Boot of GPS Receiver
This menu lets the user force the receiver into the Boot Mode. This may be necessary when the satellite data in the memory are too old or the receiver position has changed by some hundred kilometers since last operation.
Synchronization time may be reduced signicantly. If there is valid satellite data in the memory the system starts in the WARM BOOT mode, otherwise the system changes into COLD BOOT to read new data.
Initiate WARM Boot of GPS receiver
Press F2 to confirm
20 Date: 29th July 2014 LANTIME M300/GPS
10.3 Menu: Reference Time Page 21
10.3.7 Init GPS Position
When the receiver is primarily installed at a new location far away from the last position saved in the receiver's memory the satellites in view and their Doppler will dier so much from those expected due to the wrong position that GPS has to scan for satellites in Warm Boot mode. Making the new approximately known position available to the receiver can avoid Warm Boot and speed up installation.
Set Initial Position
LAT:51°58'57" LON:9 °13'32" ALT:186 m
10.3.8 Init GPS Time
If the receiver's on-board real time clock keeps a wrong time the receiver is unable to compute the satellites correct elevation angles and Doppler. This sub menu enables the user to change the receiver's system time for initialization. After the receiver has locked, its real time clock will be adjusted using the information from the satellites.
Set Initial Time
MESZ 14:26:00 29.08.2006
When the antenna is disconnected it is possible to set the LANTIME with any time. Note that the NTP will not synchronize to a GPS losing its reception or if the deviation to the system time is larger than 1024 seconds. In this case the menu Simulation Mode has to be active. After setting the clock manually the system time will be set and the NTP will be restarted.
10.3.9 Info GPS
Setup GPS Setup Outputs
-> Info GPS <-
OK
->GPS Status <- GPS Satellites
GPS Position GPS Version
10.3.10 GPS Status
Reference Clock GPS State: SYNC
OSC: TCXO warmed up:*
This rst menu will monitor the current state (sync or not sync). The next line will reect the type of the integrated oscillator.
LANTIME M300/GPS Date: 29th July 2014 21
Page 22 10 Conguration User Interface
10.3.11 GPS Receiver Position
This menu shows the current receiver position. The OK key lets the user select one of three formats. The default format is geographic latitude, longitude and altitude over the WGS84 ellipsoid with latitude and longitude displayed in degrees, minutes and seconds and the altitude displayed in meters. The next format is also geographic, with latitude and longitude displayed in degrees with fractions of degrees. The third format displays the receiver position in earth centered, earth xed coordinates (ECEF coordinates). The rst two formats are shown below:
GPS RECEIVER POSITION
LAT: 51.1234 LON:10.2111 ALT: 120m
10.3.12 GPS Satellite Constallation
The SV constellation menu gives an overview of the current satellites (SVs) in view. The display shows the number of satellites with an elevation of 5 ◦ or more (In view), the number of satellites that can be used for navigation
(Good) and the selected set of satellites which are used to update the receiver position (Sel).
SATELLITE CONSTELLATION
In view: 8 Good: 7 Sel: 05 22 17 09
10.3.13 GPS Version
GPS1xx v1.19 S/N: 029010002200
OSC: TCXO EPLD: 002E10CB
The rst line will reect the version of the GPS clock, the second line shows the type of the integrated oscillator and the EPLD (Erasable Programmable Logic Device) identication.
22 Date: 29th July 2014 LANTIME M300/GPS
10.3 Menu: Reference Time
10.3.14 Setup GPS Outputs
Setup GPS -> Setup Outputs <-
Info GPS
OK
->Output Options<- Serial Outputs
IRIG Output Pulse Outputs
Page 23
10.3.15 GPS Enable Outputs
This menu lets the user congure at which time after power up the serial ports, pulse outputs, and frequency synthesizer output are to be enabled. Outputs which are shown to be enabled always will be enabled immediately after power-up. Outputs which are shown to be enabled if sync will be enabled after the receiver has decoded the signals from the satellites and has checked or corrected its on-board clock. The default setting for all outputs is if sync.
-> Enable Outputs <-
Setup Output Time Zone
OK
Serial: always Pulses: always
Synth: always
LANTIME M300/GPS Date: 29th July 2014 23
Page 24 10 Conguration User Interface
10.3.16 Serial Outputs
This menu lets the user congure the baud rate and the framing of the serial RS232 port to one of the following values:
Baudrate:
Dataformat:
300 to 19200
7E2, 8N1, 8E1, 8O1
->Setup COM 0 <-
Setup COM 1
COM provides a time string once per second, once per minute or on request. If the on request is activated you have to send the character ? to get the timestring.
Defaultsettings COM0: Speed Framing Mode Signal Type
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
19200 baud 8N1 per second Meinberg Standard
COM0: 19200 8N1 Mode:per second
String Type: Meinberg Standard
This topic is used to select one of several dierent types of serial time strings or the capture string for each serial port.
The following time strings can be selected. All time strings are described in the appendix at the end of this documentation.
• Standard Meinberg-Telegram
• ION
• NMEA-Telegram (ZDA)
• NMEA-Telegram (RMC GGA)
• NMEA-Telegram (GGA)
• Meinberg GPS
• RACAL-Telegram
• SPA-Telegram
• Meinberg Capture
• Sysplex1-Telegram
• Computime-Telegram
• UNI-Erlangen-Telegram
• NMEA-Telegram (RMC)
• SAT-Telegram
24 Date: 29th July 2014 LANTIME M300/GPS
10.3 Menu: Reference Time Page 25
10.3.17 Setup Time Zone of Serial Outputs
The time zone of the GPS receiver can be set up. These parameters will aect the serial output lines and the time code (IRIG) outputs. The internal time zone of the timeserver and the time of NTP will always be UTC.
The time monitored in the main menu will be the time of the NTP.
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: |MEZ | +01:00h
DAYLIGHT SAVING ON : |MESZ | +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 dened 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 specied. Then, starting from the congured date, daylight saving changes the rst day which matches the congured 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 specied day-of-week after a dened 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 specied and therefore is displayed as wildcards.
DAYLIGHT SAVING ON Date: 25.03.****
Day of Week: Sun Time: 2:00:00
DAYLIGHT SAVING ON Date: 31.03.1996
Day of Week: *** Time: 2:00:00
DAYLIGHT SAVING OFF Date: 25.10.****
Day of Week: Sun Time: 3:00:00
DAYLIGHT SAVING OFF Date: 25.03.1996
Day of Week: Sun Time: 3: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 congured in the sub menu TIMEZONE.
After this a restart should be done.
LANTIME M300/GPS Date: 29th July 2014 25
Page 26
10.3.18 Menu: TIME CODE IRIG
The Time Code IRIG is an optional output.
10 Conguration User Interface
Time Code (IRIG, AFNOR, IEEE) Output
Code: B002+B122 Time: Local
This menu lets the user select the Timecodes to be generated by GPS-TC. Most IRIG-Codes do not carry any time zone information, hence UTC is selected for output by default. If desired, the clocks local time can be output by selecting "TIME: LOCAL".
Refer to chapter Timecode for details.
10.3.19 Option: Synthesizer Frequency Output
Setup Synthesizer Frequency Output
Frequency: 0.100 kHz Phase: 090.0°
This setup menu lets the user edit the frequency and phase to be generated by the on-board synthesizer.
Frequencies from 1/8 Hz up to 10 MHz can be entered using four digits and a range. The range can be selected if the UP or DOWN key is pressed while the cursor is positioned on the frequencys units string. If the least signicant range has been selected valid fractions of the frequency are .0, .1 (displayed as 1/8), .3 (displayed as 1/3), .5 and .6 (displayed as 2/3). Selection of 1/3 or 2/3 means real 1/3 or 2/3 Hz, not 0.33 or 0.66. If frequency is set to 0 the synthesizer is disabled.
The last line of the display lets the user enter the phase of the generated frequency from -360 ◦ resolution of 0.1
◦ to +360 ◦ with a
. Increasing the phase lets the signal come out later. Phase aects frequencies less than 10.00
kHz only, if a higher frequency is selected a message "(phase ignored)" informs the user that the phase value is ignored.
26 Date: 29th July 2014 LANTIME M300/GPS
10.4 Menu: Time Service Page 27
10.4 Menu: Time Service
The NTP conguration page is used to set up the additional NTP parameters needed for a more specic conguration of the NTP subsystem.
Reference Time Network
-> Time Service <- System
OK
-> external NTP <- Restart NTP
Local Stratum 2nd-Receiver
10.4.1 Menu: external NTP
The default conguration 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 synchronization. The stratum level of this local clock is set to 12, this ensures that clients recognize 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 anymore when the reference clock is out of order.
Ipv4 address of external NTP server 1
000.000.000.000
Ipv4 address of external NTP server 2
000.000.000.000
.
.
.
Seven additional external NTP servers can be set up to provide a high grade of redundancy for the internal reference clock.
10.4.2 Menu: Stratum of local clock
The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronization. The stratum level of this local clock is set to 12, this ensures that clients recognize 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 anymore when the reference clock is out of order. The eld Stratum of local clock is used to change the stratum level of the local clock (see above), default is 12.
Stratum of local clock
12
10.4.3 Menu: Restart NTP
If the time of the reference clock has changed (e.g. while testing with dierent times) the system time has to bet set with the time of the reference clock and the NTP has to be restarted.
Reset time and restart NTP ?
Press F2 to confirm reset time and NTP
LANTIME M300/GPS Date: 29th July 2014 27
Page 28 10 Conguration User Interface
10.5 Programmable pulse (Option)
At the male connector type VG64 there are optionally three programmable TTL outputs (Prog Pulse 1-3), which are arbitrarily programmable.
10.5.1 SETUP POUT X
This menu is used for conguration of the pulse outputs. There are three pulse outputs available (POUT 1-3).
With the "right arrow key" or OK Button the three pulse output can be set:
Programmable Pulses: Out1:Pulse Per Se..
Out2: Pulse Per Sec Out3:Pulse Per Se..
With the "down arrow key" the parameters of each programmable pulse output can be set:
Select Output
Programmable Pulses Output 1
Select Output
Programmable Pulses Output 2
With the OK button you can choose between "Mode" (Pulses) or "Holdover" (enables or disables the Pulses):
Select Output 1
--> Mode <-- Holdover
Select Output 2
--> Mode <-- Holdover
Mode:
Each programmable pulse output has its own Mode to be set. With the up and down arrow keys the mode can be selected:
Holdover:
With the adjustment "Holdover" the output can be enabled or disabled:
Select Output 1
--> Mode <-- Holdover
OK
Select Output 1
Mode: Pulse Per Second
Mode: Cyclic Pulse
Mode: Single Shot
Mode: Timer
Mode: Idle
Mode: All Sync
Mode: Time Sync
Mode: Position OK
Mode: DCF77 Marks
Mode: Pulse Per Hour
Mode: Pulse Per Min
Select Output 1
Mode --> Holdover <--
OK
Select Output 1
Holdover: disabled
Select Output 1
Holdover: enabled
28 Date: 29th July 2014 LANTIME M300/GPS
10.5 Programmable pulse (Option) Page 29
10.5.2 Mode
This eld selects the mode of operation of an output. Possible modes are Pulse Per Second, Cyclic Pulse, Single
Shot, Timer, Idle, All Sync, Time Sync, Position OK, DCF77 Marks, Pulse per Hour, Pulse Per Min.
10.5.3 Cyclic Pulse
Cyclic mode is used for generating periodically repeated pulses.
POUT1 CYCLIC: active:low
TIME: 00:00:02 Length: 00.10 sec
The value in eld 'Time' determines the time between two consecutive pulses (2 sec in example above). This cycle time must be entered as hours, minutes and seconds. The pulse train is synchronized at 0:00 o'clock local time, so the rst pulse of a day always occurs at midnight. A cycle time of 2 seconds for example, would cause pulses at 0:00:00, 0:00:02, 0:00:04 etc. Basically it is possible to enter any cycle time between 0 and 24 hours, however only a cycle times that causes a constant distance between all consecutive pulses make sense. For example a cycle time of 1 hour 45 minutes would generate a pulse every 6300 seconds (starting from 0 o'clock). The duration between the last pulse of a day and the rst pulse of the next day (0:00:00 o'clock) would only be 4500 sec.
10.5.4 Single Shot
Selecting Single Pulse generates a single pulse of dened length once per day.
POUT1 SINGLE: active:low
TIME: 12:00:00 Length: 00.10 sec
You can enter the time when the pulse is generated in the eld 'Time'. The value in eld 'Length' determines the pulse duration. A pulse duration from 10 msec to 10 sec in steps of 10 msec can be selected. The example shows a single pulse at 12:00 every day with a duration of 100 ms.
10.5.5 Timer mode
If Timer mode is selected, a window as shown above is displayed. The switching plan is assigned per day. Three turn-on and turn-o times are programmable for each output. If a switching time has to be congured, only the turn-on and turn-o time must be programmed. Thus the example shows switching times from 10:50 to 11:00,
13:00 to 14:00 and 23:45 to 09:30. A turn-o time earlier than the turn-o time would cause the output to be enabled over midnight.
OK
Select Output 1
TIMER 1
POUT1 TIMER1: active:low
ON: 10:50:00 OFF: 11:00:00
POUT1 TIMER2: active:low
ON: 10:50:00 OFF: 11:00:00
For example a program 'ON Time' 10:45:00, 'OFF Time' 9:30:00 would cause an active ouput from 10:45 to
9:30 (the next day!). If one or more of the three switching times are unused just enter the same time into the elds 'ON Time' and 'OFF Time'. In this case the switch time does not aect the output.
LANTIME M300/GPS Date: 29th July 2014 29
Page 30
10.5.6 Idle mode
Selecting 'Idle' deactivates the output.
10 Conguration User Interface
Setup Output 1 - diable Output
Press OK to confirm X
10.5.7 Position OK / TimeSync / AllSync
Position OK
Setup Output 1
Mode: Position OK
OK
POUT1 POS OK: Position ok
active: high
Time Sync
Setup Output 1
Mode: Time Sync
OK
POUT1 TimeSync:
active: high
All Sync
Setup Output 1
Mode: All Sync
OK
OK
Setup Output 1
TIMER 1
POUT 1 TIMER1 active: high
ON: 00:00:00 OFF: 00:00:00
Three dierent modes are selectable for output of the clocks synchronization state. The Mode 'position OK' activates the output when the receiver has sucient satellites in view to calculate its position. This mode corresponds to the modes 'Status' or 'Sync Status' as provided by older Firmware Version of GPS163. In 'time sync' mode the respective output is activated when the clocks internal timebase is synchronized to the GPS timing. The 'all sync' Mode performs a logical AND operation of the both states previously mentioned, i.e. the output is activated if the position can be calculated AND the internal timebase is synchronized to the GPS timing
30 Date: 29th July 2014 LANTIME M300/GPS
10.5 Programmable pulse (Option)
10.5.8 DCF Mark
OK
Setup Output 1
Mode: DCF77 Marks
POUT1 DCF77:
active: high Timeout: 00 min
Page 31
In 'DCF77 marks' mode the selected output simulates the telegram as transmitted by german time code transmitter DCF77 (see chapter DCF77 Emulation in radioclock manual). The generated time code is related to the local time zone.
If you want DCF simulation to be disabled when the clock is in free running mode, you can enter the delay
(given in minutes) for deactivating the DCF-Simulation in the entry eld 'Timeout'. DCF Simulation is never suspended, if the delay value is zero.
10.5.9 PPS, PPM, PPH Modes
POUT1 Pulse Per Sec (PPS):
output active:low LNG: 00.10 sec
POUT1 Pulse Per Min (PPM):
output active:low LNG: 00.10 sec
POUT1 Pulse Per Hour (PPH):
output active:low LNG: 00.10 sec
These modes generate pulses of dened length once per second, once per minute or one per hour. 'Time' determines the pulse duration (10 msec...10 sec). The respective output remains in active state, when selecting a pulse duration longer than 990ms in pulse per sec mode..
LANTIME M300/GPS Date: 29th July 2014 31
Page 32
10.6 Menu: Synthesizer Frequency Output
The Frequency Synthesizer is an optional output.
10 Conguration User Interface
Synthesizer Frequency Output
Frequence: 100.0 Hz Phase: 090.0
This setup menu lets the user edit the frequency and phase to be generated by the on-board synthesizer. Frequencies from 1/8 Hz up to 10 MHz can be entered using four digits and a range. The range can be selected if the UP or DOWN key is pressed while the cursor is positioned on the frequencys units string. If the least signicant range has been selected valid fractions of the frequency are .0, .1 (displayed as 1/8), .3 (displayed as 1/3), .5 and .6 (displayed as 2/3). Selection of 1/3 or 2/3 means real 1/3 or 2/3 Hz, not 0.33 or 0.66. If frequency is set to 0 the synthesizer is disabled.
The last line of the display lets the user enter the phase of the generated frequency from -360 with a resolution of 0.1
◦
◦
. Increasing the phase lets the signal come out later. Phase aects frequencies less than
10.00 kHz only, if a higher frequency is selected a message "(phase ignored)" informs the user that the phase value is ignored.
to +360 ◦
32 Date: 29th July 2014 LANTIME M300/GPS
10.7 Menu: TIME CODE IRIG
10.7 Menu: TIME CODE IRIG
The Time Code IRIG is an optional output.
Page 33
Time Code (IRIG, AFNOR, IEEE) Output
Code: B002+B122 Time: Local
This menu lets the user select the Timecodes to be generated by GPS-TC. Most IRIG-Codes do not carry any time zone information, hence UTC is selected for output by default. If desired, the clocks local time can be output by selecting "TIME: LOCAL".
Refer to chapter Timecode for details.
LANTIME M300/GPS Date: 29th July 2014 33
Page 34
10.8 Menu: Network
10 Conguration User Interface
Reference Time -> Network <-
Time Service System
OK
-> Global Cfg. <- Services
Interfaces
OK
->Hostname<- Namesrv. Netw.LED
Domain Syslog
Global Cfg. Services
-> Interfaces <-
OK
-> Ipv4 Parameter <- Link Mode
Ipv6 Parameter
Global Cfg. -> Services <-
Interfaces
OK
>SSH:on < TELN:on IPv6:on HTTPS:on
FTP:on SNMP:off HTTP:on NETB:off
In this submenu the network conguration 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 congured, additional network conguration can be done via network connection with TELNET, SSH or the WEB interface. Ask your network administrator for network specic parameters.
Every change of the network parameters will restart the NTP. All network specic parameters will be saved on the ash disk (/mnt/ash/cong/global_conguration) and will be reloaded after reboot. It is highly recommended not to edit this le manually but to congure the parameters via the several conguration 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.8.1 Setup Global Configuration
Interfaces Services
-> Global Cfg. <-
OK
->Hostname<- Namesrv. Netw.LED
Domain Syslog
In this sub menu you can change the global network settings like host and domain name, nameserver and syslog server. Further name- or syslog servers can be set up via HTTP interface or CLI Setup. In the nameserver and syslog server elds you have to enter an Ipv4 address.
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 congured to allow remote systems to create entries. A Linux SYSLOG daemon 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.
34 Date: 29th July 2014 LANTIME M300/GPS
10.8 Menu: Network Page 35
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.
SETUP: Check Network LinkUp on LAN Ports
ETH0:x ETH1: ETH2: ETH3: PTP0:
The submenu "Netw. LED" will monitor the network ports, which will be checked continuously if the network port is "LINKED UP". If one of these ports has no link up, the network LED on the front panel will change to red. An "L" for "LED" indicates if the port is checked. Please navigate through the list of ports with the
LEFT/RIGHT buttons and change the setting with the UP/DOWN buttons.
10.8.2 Setup Network Interfaces
In the network conguration parameters related to the network interfaces can be changed. The following submenus can be selected with the arrow keys and the OK button:
Global Cfg. Services
-> Interfaces <-
OK
-> Ipv4 Parameter <- Link Mode
Ipv6 Parameter
When congured an IP address once additionally network conguration can be done via network connection with
TELNET, SSH or the WEB interface. Ask your network administrator for network specic parameters. Every change of the network parameters will restart the NTP. All network specic parameters will be saved on the ash disk (/mnt/ash/cong/global_conguration) and will be reloaded after reboot.
10.8.3 Setup Network Ipv4 Parameter
-> ETH0 <- Def.Gateway
ETH1
OK
>DHCP: disabled< ADDR: 192.168.10.2
NETMASK: 255.255.255.0
There is a separate conguration 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 specic network.
If there is a DHCP (Dynamic Host Conguration 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/GPS Date: 29th July 2014 35
Page 36 10 Conguration User Interface
10.8.4 Menu: Setup Ipv6 Parameter
Ipv4 Parameter Link Mode
-> Ipv6 Parameter <-
OK
-> Link Local <- glob.Addr 1
Auto Config. glob Addr 2
The IPv6 parameters can be congured via the front panel display for the rst ethernet port (ETH0) only. Additional IPv6 conguration can be done via network connection with TELNET, SSH or the WEB interface.
You can specify up to three IPv6 addresses for your LANTIME timeserver (two via front panel display and another one via WEB interface). 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.
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.
10.8.5 Menu: Link Mode
SETUP: ETH0 Device Parameter
Link Speed/Mode: Autosensing
The parameters for speed and link mode of the net card can be changed with the menu item Link Mode. There are 5 modes available: Autosensing, 10 MBit/Half-Duplex, 100 MBit/Half-Duplex, 10 MBit/Full-Duplex, 100
MBit/Full-Duplex. Default setting is Autosensing.
10.8.6 Menu: Setup Network Services
Global Cfg. -> Services <-
Interfaces
OK
>SSH:on < TELN:on IPv6:on HTTPS:on
FTP:on SNMP:off HTTP:on NETB:off
The possible network protocols and access methods can be congured. 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).
36 Date: 29th July 2014 LANTIME M300/GPS
10.9 Menu: System
10.9 Menu: System
Reference Time Network
Time Service -> System <-
OK
->Set Time Zone<- Restart Menu
Factory Defaults
Page 37
In this submenu system specic parameters can be congured:
With Set Time Zone the time zone displayed on the front panel display can be congured (see below). With
Restart Menu you can stop and restart the currently running NTP daemon or you can reboot the Linux operating system. When Factory Defaults is called, all system parameters will be reset to initial values. However the parameters of each network interface do not change.
10.9.1 Set time zone
The time zone of the time that is shown on the front panel display can be set up here. The internal time zone of the timeserver and the time of NTP will always be UTC. These parameters will not aect the serial output lines and the timecode (IRIG) outputs. These parameters have to be congured in another menu
(Reference Time->Setup 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.
Front Panel Display: -> Set Timezone <-
DL_Save ON DL_Save OFF
OK
DAYLIGHT SAVING OFF: CET +01:00h
DAYLIGHT SAVING ON : CEST +02:00h
F
1
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 dened 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 specied. Then, starting from the congured date, daylight saving changes the rst day which matches the congured 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 specied day-of-week after a dened 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 specied and therefore is displayed as wildcards.
LANTIME M300/GPS Date: 29th July 2014 37
Page 38 10 Conguration User Interface
Front Panel Display: Set Timezone
-> DL_Save ON <- DL_Save OFF
OK
DAYLIGHT SAVING ON: Date: 25.03.****
Day of Week: Sun Time: 02:00:00
F
1
Front Panel Display: Set Timezone
DL_Save ON -> DL_Save OFF <-
OK
DAYLIGHT SAVING OFF: Date: 25.10.****
Day of Week: Sun Time: 03:00:00
F
1
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 congured in the sub menu TIMEZONE.
After this a restart should be done.
10.9.2 Restart Menu
Set Time Zone -> Restart Menu <-
Factory Defaults
OK
-> Reboot Time Server <-
Restart NTP
With Restart NTP you can stop the currently running NTP daemon and restart it afterwards. The command
Reboot Time Server reboots the Linux operating system the build-in reference clock will not be restarted.
38 Date: 29th July 2014 LANTIME M300/GPS
Page 39
11 The graphical user interfaces
The LANTIME oers three dierent options for conguration and status management: Web interface, Command
Line Interface Setup and SNMP. In order to use the SNMP features of your LANTIME, you need special software like management systems or SNMP clients. In order to use the web interface, all you need is a web browser
(LANTIME supports a broad range of browsers).
In addition to the SNMP and web interface, you can also manage your LANTIME conguration via a command line interface (CLI), which can be used via a TELNET or SSH connection. A setup tool can be started after login, just type setup and press ENTER at the prompt.
There are only a few dierences between the web interface and the CLI, most options are accessible from both interfaces (the CLI has no statistical functions).
The above screen shots show the web interface and the Command Line Interface setup tool. The CLI setup tool cannot be used by more than one user at a time, the web interface can be used by more than one user in parallel, but the two or more running sessions may inuence each other. We explicitly do not recommend the parallel usage of the conguration interfaces.
LANTIME M300/GPS Date: 29th July 2014 39
Page 40 12 The WEB Interface
12 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 certicate 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 reect 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
40 Date: 29th July 2014 LANTIME M300/GPS
12.1 Conguration: Main Menu Page 41
12.1 Configuration: Main Menu
After entering the right password, the main menu page shows up. This page contains an overview of the most important conguration and status parameters for the system.
The start page gives a short overview of the most important conguration 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 notication 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 conguration pages, which are described below.
LANTIME M300/GPS Date: 29th July 2014 41
Page 42
12.2 Configuration: Ethernet
12 The WEB Interface
In the network conguration 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 specied as a hostname, too).
42 Date: 29th July 2014 LANTIME M300/GPS
12.2 Conguration: Ethernet Page 43
12.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 congured 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 congured. 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.
LANTIME M300/GPS Date: 29th July 2014 43
Page 44 12 The WEB Interface
12.3 Network interface specific configuration
The interface specic 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.
12.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 specic network.
If there is a DHCP (Dynamic Host Conguration 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).
12.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:
"::" is the address, which simply consists of zeros
"::1" 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 prex.
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.
44 Date: 29th July 2014 LANTIME M300/GPS
12.3 Network interface specic conguration Page 45
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.
12.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.
LANTIME M300/GPS Date: 29th July 2014 45
Page 46 12 The WEB Interface
12.3.4 Additional Network Configuration
You can congure additional network parameter like special network routes or alias denitions. For this you will edit a script le which will be activated every time after the network conguration will run.
Also the Samba Conguration from /etc/samba/smb.conf can be edited:
46 Date: 29th July 2014 LANTIME M300/GPS
12.4 Conguration: Notication
12.4 Configuration: Notification
Page 47
LANTIME M300/GPS Date: 29th July 2014 47
Page 48 12 The WEB Interface
12.4.1 Alarm Events
On this page you can set up dierent notication 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 notication 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 specied 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 dened 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
NTPStopped
NTPNotSync
ReceiverNotResponding
ReceiverNotSync
AntennaFaulty
SecondaryRecNotSync
PowerSupplyFailure
NetworkDown
SecondaryRecNotResp
Cleared By
NTPNotSync or
NTP Sync
NTPSync
ReceiverNotSync or
ReceiverSync
ReceiverSync
AntennaReconnect
SecondaryRecSync
PowerSupplyUp
NetworkUp
RecNotSync or
RecSync
The following traps are notications that do not have a "clearing" trap:
• mbgLtTrapCongChanged
• mbgLtTrapLeapSecondAnnounced
• mbgLtTrapServerBoot
Every event can use a combination of those four notication types, of course you can disable notication for an event (by just disabling all notication types for this event). The conguration of the four notication types can be changed in the upper section of the page, you can control which notication is used for which event in the lower part of the page.
48 Date: 29th July 2014 LANTIME M300/GPS
12.4 Conguration: Notication Page 49
12.4.2 E-mail messages
You can specify the e-mail address which is used as the senders address of the notication 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 specied 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
12.4.3 Windows Popup Messages
Most Microsoft Windows operating systems provide you with a local notication 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 notication. On the Windows client side it is necessary to activate the Microsoft
Client for Windows in the network conguration.
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:
12.4.4 SNMP-TRAP messages
Up to two SNMP trap receiver hosts can be congured 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 conguration access (see SNMP conguration on the Security page).
12.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 notication 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.
12.4.6 User defined Alarm scripts
You can dene your own alarm script for every event by using the Edit user dened notication script. This script will be called automatically if one of the selected events occurs.
LANTIME M300/GPS Date: 29th July 2014 49
Page 50 12 The WEB Interface
This user alarm script will be stored on the Flash-Disk at /mnt/ash/user_dened_notication. This script will be called with index and the alarm message as text. The index value of the test message is 0.
12.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 congured clients:
12.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/notication_messages on the ash disk of your timeserver.
50 Date: 29th July 2014 LANTIME M300/GPS
12.5 Conguration: Security
12.5 Configuration: Security
Page 51
LANTIME M300/GPS Date: 29th July 2014 51
Page 52 12 The WEB Interface
12.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 conguration section in this manual.
12.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:
12.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 certicate, you have to accept the certicate, afterwards you are prompted for your password (which is congured 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 conguration afterwards in
52 Date: 29th July 2014 LANTIME M300/GPS
12.5 Conguration: Security Page 53 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.
LANTIME M300/GPS Date: 29th July 2014 53
Page 54 12 The WEB Interface
12.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
certicates and asymmetric crypto procedures. The timeserver uses these certicates 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 certicate of the web server. To make sure that you are talking to your known timeserver, check the certicate and accept it, if it matches the one stored on the LANTIME. All further connections are comparing the certicate with this one, which is saved in your web browser conguration. Afterwards you are prompted to verify the certicate only when it changed.
By using the button "Generate SSL certicate for HTTP" you can create a new certicate. Please enter your organisation, name, mail address and the location in the upcoming form and press Generate SSL certicate to nally generate it.
After the successful generation of the certicate, it is shown to you:
It is also possible to upload your own HTTPS certication. If you upload a non valid certication HTTPS will not work.
54 Date: 29th July 2014 LANTIME M300/GPS
12.5 Conguration: Security Page 55
12.5.5 NTP keys and certificates
The fourth and fth section of the Security page allow you to create the needed crypto keys and certicates for secure NTP operation (please see NTP authentication below).
The function Generate new NTP public key is creating a new self-signed certicate for the timeserver, which is automatically marked as trusted.
Important note: This certicate is depending on the hostname of your LANTIME, it is mandatory to re-create the certicate after changing the hostname. The certicates 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).
12.5.6 SNMP Parameter
In the last Section all parameters for SNMP can be congured. More information you can nd later in this manual.
LANTIME M300/GPS Date: 29th July 2014 55
Page 56
12.6 Configuration: NTP
12 The WEB Interface
The NTP conguration page is used to set up the additional NTP parameters needed for a more specic conguration of the NTP subsystem.
The default conguration 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 conguration 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 # GPS167 UNI Erlangen PPS fudge 127.127.8.0 time1 0.0042
server 127.127.22.0
fudge 127.127.22.0 ag3 1 enable stats
# relative to PPS
# ATOM (PPS)
# enable PPS API
56 Date: 29th July 2014 LANTIME M300/GPS
12.6 Conguration: NTP statsdir /var/log/ statistics loopstats driftle /etc/ntp.drift
# Edit /mnt/ash/ntpconf.add to add additional NTP parameters
Page 57
By using the NTP conguration 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 conguration 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 specic 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 conguration 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 conguration 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 conguration after a change. You can edit this le by using the button Edit additional NTP parameter.
LANTIME M300/GPS Date: 29th July 2014 57
Page 58 12 The WEB Interface
By choosing Show current NTP conguration, 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.
12.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 sucient 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 conguration le /etc/ntp.conf of a server using this authentication mode may look like this:
# peer conguration 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 peer 192.35.82.50 key 6
# umd1.umd.edu
# lilben.tn.cornell.edu
keys /mnt/ash/ntp.keys
# path for key le trustedkey 1 2 14 15 requestkey 15
# dene trusted keys
# key (mode 6) for accessing server variables
58 Date: 29th July 2014 LANTIME M300/GPS
12.6 Conguration: NTP
10
10
10
1
2
14
15
N 29233E0461ECD6AE
M RIrop8KPPvQvYotM
M sundial
A sundial
A SeCReT
N d3e54352e5548080
S a7cb86a4cba80101
Page 59 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 identies all key IDs, which have to be considered trusted or uncompromised. All other keys dened in the keyle 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 modication.
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)
# 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 denes the format of the key, which is following in column three. There are four dierent key formats:
• A 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).
• 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 specied 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 dened 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.
12.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 suciently 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 AU-
TOKEY 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:
LANTIME M300/GPS Date: 29th July 2014 59
Page 60 12 The WEB Interface a) Trusted Host
One or more trusted NTP servers. In order to become a trusted server, a NTP server must own a self-signed certicate 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 certicate, but only a self-signed certicate 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 fullled 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 congure 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 certicate. 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 certicate (without marking it as trusted). Because every certicate 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
60 Date: 29th July 2014 LANTIME M300/GPS
12.6 Conguration: NTP using shell access (via SSH).
Page 61
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/cong/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 certicate 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 certicate which lacks the trusted mark. The clients also hold the group key and a self-signed certicate. 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 certicates 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 ocial NTP website (http://www.ntp.org).
LANTIME M300/GPS Date: 29th July 2014 61
Page 62
12.7 Configuration: Local
12 The WEB Interface
62 Date: 29th July 2014 LANTIME M300/GPS
12.7 Conguration: Local Page 63
12.7.1 Administrative functions
In the rst section there are several functions which may be used by the administrator. The button Reboot LAN-
TIME 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 conguration you are able to change the main conguration by editing the conguration 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 conguration (this results in reloading several subsystems like NTPD,
HTTPD etc.).
The function Send test notication is generating a test alarm message and sends it using all congured 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 conguration parameters back to default values. The regular le /mnt/ash/global_conguration will be replaced with the le /mnt/ash/factory.conf, but rst a copy of the conguration is saved under /mnt/ash/global_conguration.old for backup reasons. The default password timeserver is replacing the actual password, too. After using this function, all certicates should be recreated because of the change of the unit's hostname.
Please be aware of the fact that the default conguration is not activated instantly. If you want to avoid setting up the IP address of your unit by locally conguring 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 congure 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 conguration from ash into memory and activate it.
The point Download SNMP MIB les can be used to download all Meinberg specic SNMP MIB les to your workstation. They can be distributed to all SNMP management clients afterwards.
12.7.2 User Management
For administration dierent users can be set up. 3 group memberships can be assigned to each user: the Super-
User has all properties for administration. The group membership Administrator can change all parameters via
LANTIME M300/GPS Date: 29th July 2014 63
Page 64 12 The WEB Interface the command line interface (CLI) conguartion 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.
12.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 congured an external SYSLOG server, all LANTIME syslog entries will be duplicated on this remote system and can be saved permanently this way.
Mar 15 13:35:17 LanGpsV4 ntpd[12948]:
Mar 15 13:35:17 LanGpsV4 ntpd[12948]:
Mar 15 13:35:17 LanGpsV4 ntpd[12948]:
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: ntpd [email protected] 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
Mar 15 13:35:17 LanGpsV4 ntpd[12948]:
Mar 15 13:38:36 LanGpsV4 lantime[417]: frequency initialized 45.212 PPM from /etc/ntp.drift
NTP sync to GPS
Mar 15 13:38:36 LanGpsV4 lantime[417]: NTP restart
Mar 15 13:45:36 LanGpsV4 proftpd[14061]: connect from 172.16.3.2 (172.16.3.2)
Mar 15 14:01:11 LanGpsV4 login[15711]:
Mar 15 14:01:17 LanGpsV4 login[15711]: 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.
64 Date: 29th July 2014 LANTIME M300/GPS
12.7 Conguration: Local
The function List LANTIME Options shows the hardware options installed in your LANTIME.
Page 65
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).
LANTIME M300/GPS Date: 29th July 2014 65
Page 66 12 The WEB Interface
12.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 conrm the start of the update process. The scope of the update only depends on the chosen le.
66 Date: 29th July 2014 LANTIME M300/GPS
12.7 Conguration: Local Page 67
12.7.5 Automatic configuration check
All parameters of the LANTIME can be checked for plausibility and all congured servers (e.g. SYSLOG servers, nameservers) are tested for reachability. All red coloured values should be reviewed by the administrator. Because all congured hostnames / IP addresses of the servers are processed during the reachabilitytests, the whole check process may take a while.
12.7.6 Get Diagnostics Information
The diagnostics information is a set of conguration 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 cong.zip to your local computer. If you have any questions or problems with your LANTIME please send this le cong.zip as an attachment of an e-mail to Meinberg support and describe your problem.
LANTIME M300/GPS Date: 29th July 2014 67
Page 68 12 The WEB Interface
12.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.
12.7.8 Web interface language
With the selector box Web interface language you can change the displayed language of the WEB interface.
68 Date: 29th July 2014 LANTIME M300/GPS
12.8 Conguration: Statistics
12.8 Configuration: Statistics
Page 69
LANTIME M300/GPS Date: 29th July 2014 69
Page 70 12 The WEB Interface
12.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:
- red:
- 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)
The last section will show some NTP specic informations about the refclock.
70 Date: 29th July 2014 LANTIME M300/GPS
12.9 Conguration: Manual
12.9 Configuration: Manual
Page 71
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 conguration changes and want to comment them, you can create a note called cong_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 conrmed these parameters with Add document, you are able to edit the text of your new note.
LANTIME M300/GPS Date: 29th July 2014 71
Page 72 12 The WEB Interface
12.10 Configuration: PTP
In the PTP section, all parameters of the PTP subsystem can be congured. 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 12.10.4).
- All conguration parameters of the PTP unit can be viewed and changed by editing the
"ptp2_global_conf_0" le (see 12.10.1).
- The IP address and VLAN conguration can be edited by altering the "ptp2_network_cong_0"
- If more than one PTP unit is built into the system, then the conguration 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 12.10.1 (Global PTP Parameters).
72 Date: 29th July 2014 LANTIME M300/GPS
12.10 Conguration: PTP Page 73
12.10.1 PTPv2 - Global Configuration
Parameter
PTP Mode
PTP is slave
PTP Delay Mechanism
PTP V1 Hardware Compatibility
PTP Domain Number
PTP Network Protocol
PTP Timescale
PTP priority1
PTP priority2
Value
[NUM]
[BOOL]
[0,1]
[0,1]
[NUM,0:255]
[NUM,1,3]
[NUM,0:1]
Description
0=Multicast (MC), 1=Unicast (UC)
1=Slave only, 0=Grandmaster only
0=End-to-End, 1=Peer-to-Peer
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)
Priority1 as used in Best Master Clock Algorithm
Priority2 as used in Best Master Clock Algorithm
PTP Sync Interval
PTP Announce Interval
PTP DelayRequest Interval
PTP Unicast interval duration [s]
PTP Unicast clockid of master
PTP Unicast IP address of master
[NUM:0:255]
[NUM:0:255]
[2
[2 x x
[2 x
[ASCII,50]
[IP]
]:0
]:1
]: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
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)
1=Power Prole Preset, 2=Telecom Prole Preset Feature Presets [NUM]
Power Prole Grandmaster ID [NUM,3:254]:0 ID of Grandmaster, 3 - 254 (Power Prole only)
Power Prole Network Inaccuracy [NUM]:0 accumulated time inaccuracy in worst network path in ns (Power Prole only)
User dened Fix Oset positive
User dened Fix Oset [ns]
[BOOL]
[NUM]
1=Positive PTP Phase shift to RefTime
Phase shift to RefTime (0..1000000 ns)
HQ Filter active [BOOL]:0
HQ Filter estimated accuracy [ns] [NUM]:5000
PDSC active [BOOL]:0
PTP Announce Receipt Timeout [2 x ]:3
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 ??) only used with Mulicast Master mode
LANTIME M300/GPS Date: 29th July 2014 73
Page 74 12 The WEB Interface
12.10.2 Option: PTP Client Monitoring
From Lantime Firmware Version 5.34m onwards
The PTP Client-Monitor can be congured via Front Panel Time Service -> PTP IEEE1588 -> Setup PTP0
IEEE1588 V2 -> PTP Settings -> PTP Parameters -> PTP Client Management (for conguration 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
EC4670FFFE002435 MASTER
9
6
-0.000000015
0.000000000
0.000010420
0.000000000
alias_0
0050C2FFFEB717EA
0050C2FFFED287DE
SLAVE
SLAVE
EC4670FFFE000801 PASSIVE
9
9
7
0.000000146
0.000000107
0.000000000
0.000020675
0.000020859
0.000000000
alias_2 alias_3
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
State text val offset
Slave 9 0.000000500
pathdelay
0.000025000
Alias alias_name
74 Date: 29th July 2014 LANTIME M300/GPS
12.10 Conguration: PTP Page 75
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
MASTER
PASSIV
9
6
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. Accessibility
2. PTP Status
3. If PTP Status = SLAVE: exceeding a given maximal absolute oset value (related to the PTP Master).
4. If PTP Status = SLAVE: exceeding a given maximal pathdelay value (related to the PTP Master).
The current status conditions are forwarded to the Notication Triggers respectively via "PTP State changed" notication. All notications are triggered only once until the state changes in the following way:
1. A node is again accessible.
2. PTP Status has changed again.
3. Oset value is below a given threshold again.
4. Pathdelay is below a given threshold again.
Menu Notication
LANTIME M300/GPS Date: 29th July 2014 75
Page 76
12.10.3 PTP Network Configuration
All network congurations of the selected PTP interface can be done with this menu:
12 The WEB Interface
Content of the PTP Network Conguration File:
Parameter Value Description
Hostname
Domainname
Nameserver 1
Nameserver 2
TCPIP address
NETMASK
Default Gateway
DHCP CLIENT
VLan enabled
VLan ID
VLan Priority
PTP IP TTL
[ASCII,50]:PTPv2
[ASCII,50]:
[ASCII,50]:
[ASCII,50]:
[IP]:192.168.100.10
[IP]:255.255.255.0
[IP]:192.168.100.1
[BOOL]:0
[BOOL]:0
[NUM]:
[NUM]:
[NUM]:
Hostname for PTP port
Domainname for PTP port
IP address of PTP port
Netmask of PTP port
Gateway
1=Activate DHCP client
Enable Virtual LAN interface (IEEE 802.1Q)
VLAN ID for virtual interface
VLAN priority for virtual interface
Multicast IP Packet Time To Live (TTL default:5)
76 Date: 29th July 2014 LANTIME M300/GPS
12.10 Conguration: PTP
12.10.4 PTP State Files
In diesem Menü werden alle Statusinformationen der gewählten TSU angezeigt:
Page 77
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
: [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;
LANTIME M300/GPS Date: 29th July 2014 77
Page 78 13 The Command Line Interface
13 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 conguration 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 notication 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 reects 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 conguration pages, that are described below.
78 Date: 29th July 2014 LANTIME M300/GPS
13.1 CLI Ethernet
13.1 CLI Ethernet
Page 79
In the network conguration 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 specied 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 congured 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 congured. 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 specic parameters, you can enter the Ethernet Conguration 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.
LANTIME M300/GPS Date: 29th July 2014 79
Page 80 13 The Command Line Interface
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 specic network.
If you are running a DHCP (Dynamic Host Conguration 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 EN-
ABLED. 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:
"::" is the address, which simply consists of zeros
"::1" 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 prex.
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
80 Date: 29th July 2014 LANTIME M300/GPS
13.2 CLI Notication Page 81 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.
13.2 CLI Notification
Alarm events
On this page you can set up dierent notication 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 notication 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 specied 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 stopped"
NTP is not synchronised to a reference time source
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"
"Antenna faulty"
Internal GPS clock is not synchronised to GPS time
GPS antenna disconnected
"Antenna reconnect"
"Cong changed"
GPS antenna reconnected
Conguration was changed by a user
Leap second announced A leap second has been announced
Every event can use a combination of those four notication types, of course you can disable notication for events by disabling all notication types. The conguration of the four notication types can be changed in the upper section of the page, you can control which notication is used for which event by using the button notication conditions in the lower part of the page.
LANTIME M300/GPS Date: 29th July 2014 81
Page 82 13 The Command Line Interface
E-mail messages
You can specify the e-mail address which is used as the senders address of the notication 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 congured 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 notication 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 notication. On the Windows client side it is necessary to activate the Microsoft Client for Windows in the network conguration.
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 congured 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 conguration (see SNMP conguration 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 notication 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.
If you want to use the display for other purposes, you can send text messages to it by using our command
82 Date: 29th July 2014 LANTIME M300/GPS
13.3 CLI Security Page 83 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 congured clients:
13.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 conguration section in this manual.
LANTIME M300/GPS Date: 29th July 2014 83
Page 84 13 The Command Line Interface
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 certicate, you have to accept the certicate, afterwards you are prompted for your password (which is congured in the rst section of this page).
If you generate a new SSH key, you can copy and paste it into your SSH client conguration 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 Certicate for HTTPS
HTTPS is the standard for encrypted transmission of data between web browser and web server. It relies on X.509
certicates and asymmetric crypto procedures. The timeserver uses these certicates 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 certicate of the web server. To make sure that you are talking to your known timeserver, check the certicate and accept it, if it matches the one stored on the LANTIME. All further connections are comparing the certicate with this one, which is saved in your web browser conguration. Afterwards you are prompted to verify the certicate only when it changed.
By using the button Generate SSL certicate for HTTP" you can create a new certicate. Please enter your organisation, name, mail address and the location in the upcoming form and press Generate SSL certicate to nally generate it.
NTP keys and certicates
The fourth and fth section of the Security page allow you to create the needed crypto keys and certicates for secure NTP operation (please see NTP authentication below).
The function Generate new NTP public key is creating a new self-signed certicate for the timeserver, which is automatically marked as trusted.
Important note: This certicate is depending on the hostname of your LANTIME, it is mandatory to recreate the certicate after changing the hostname. The certicates 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).
84 Date: 29th July 2014 LANTIME M300/GPS
13.4 CLI NTP Parameter
13.4 CLI NTP Parameter
Page 85
The NTP conguration page is used to set up the additional NTP parameters needed for a more specic conguration of the NTP subsystem.
The default conguration 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 conguration 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 enable stats statsdir /var/log/ statistics loopstats driftle /etc/ntp.drift
# local clock
# local stratum
# GPS167 UNI Erlangen PPS
# relative to PPS
# ATOM (PPS)
# enable PPS API
# Edit /mnt/ash/ntpconf.add to add additional NTP parameters
LANTIME M300/GPS Date: 29th July 2014 85
Page 86
13.4.1 CLI NTP Authentication
Please see the corresponding chapter in the web interface description.
13.5 CLI Local
13 The Command Line Interface
Administrative functions
In the rst section there are several functions which may be used by the administrator. The button Reboot LAN-
TIME 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 conguration you are able to change the main conguration by editing the conguration 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 conguration (this results in reloading several subsystems like NTPD,
HTTPD etc.).
The function Send test notication is generating a test alarm message and sends it using all congured 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 conguration parameters back to default values. The regular le /mnt/ash/global_conguration will be replaced with the le /mnt/ash/factory.conf, but rst a copy of the conguration is saved under /mnt/ash/global_conguration.old for backup reasons. The default password timeserver is replacing the actual password, too. After using this function, all certicates should be recreated because of the change of the unit's hostname.
Please be aware of the fact that the default conguration is not activated instantly. If you want to avoid setting up the IP address of your unit by locally conguring 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 congure 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 conguration 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 Super-
User has all properties for administration. The group membership Administrator can change all parameters via the command line interface (CLI) conguartion 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
86 Date: 29th July 2014 LANTIME M300/GPS
13.5 CLI Local Page 87 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 congured an external SYSLOG server, all LANTIME
SYSLOG entries will be duplicated on this remote system and can be saved permanently this way.
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: ntpd [email protected] Fri Mar 5 15:58:48 CET 2004 (3)
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: signal_no_reset: signal 13 had ags 4000000
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: precision = 3.000 usec
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: kernel time sync status 2040
Mar 15 13:35:17 LanGpsV4 ntpd[12948]: frequency initialized 45.212 PPM from /etc/ntp.drift
Mar 15 13:38:36 LanGpsV4 lantime[417]: NTP sync to GPS
Mar 15 13:38:36 LanGpsV4 lantime[417]: NTP restart
Mar 15 13:45:36 LanGpsV4 proftpd[14061]: connect from 172.16.3.2 (172.16.3.2)
Mar 15 14:01:11 LanGpsV4 login[15711]: invalid password for `root' on `ttyp1' from `172.16.3.45'
Mar 15 14:01:17 LanGpsV4 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
LANTIME M300/GPS Date: 29th July 2014 87
Page 88 13 The Command Line Interface
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 conrm the start of the update process. The scope of the update only depends on the chosen le.
88 Date: 29th July 2014 LANTIME M300/GPS
Page 89
14 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 specic 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 conguration 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:
Authentication support:
Encryption support: mibII, ucd_snmp, snmpv3mibs, notication, 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 = [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
LANTIME M300/GPS Date: 29th July 2014 89
Page 90
...mbgLtRefclock.mbgLtRefGpsState.0 = GPS State: sync
...mbgLtRefclock.mbgLtRefGpsStateVal.0 = 1
...mbgLtRefclock.mbgLtRefGpsPosition.0 = GPS Position: 51.9834
◦
...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
9.2259
◦ 181m
14 SNMP Support
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 conguration parameters is possible (the command snmpset is used to alter a variable, for example).
14.1 Configuration over SNMP
The LANTIME timeserver can be congured 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 conguration interface is available.
In order to use the SNMP conguration features of the timeserver, you need to full 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 conguration the read-write-access needs to be activated
The timeserver-specic 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 congure your SNMP client software to use them.
90 Date: 29th July 2014 LANTIME M300/GPS
14.1 Conguration over SNMP Page 91
14.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 conguration 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 sucient 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 conguration, which takes a few seconds. The request is acknowledged by the
SNMP agent afterwards.
To change a group of parameters without reloading the conguration 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 speciying 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 conguration reference part of this manual.
Additionally, it is recommended to also read the mentioned MIB les.
LANTIME M300/GPS Date: 29th July 2014 91
Page 92 14 SNMP Support
14.1.2 Further configuration possibilities
Because the timeserver uses a standard version of the net-snmp SNMP daemon (with extended features covering the timeserver-specic functions), all conguration parameters of the SNMPD can be used. The conguration 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 conguration 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.
14.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 conguration 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.
ReloadCong(3)
The parameters of the timeserver conguration (stored in
/mnt/ash/global_conguration) 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 conguration of the timeserver is reset to factory defaults, afterwards an automatic ReloadCong 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.
SendTestNotication(8)
A test message is sent by using all notication methods the timeserver has a conguration 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:/#
92 Date: 29th July 2014 LANTIME M300/GPS
14.1 Conguration over SNMP Page 93
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 dened in the MIB le MBG-SNMP-LANTIME-CMD.txt (and in the command list above).
If you want the timeserver to reload it's conguration 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 ReloadCong
MBG-SNMP-LANTIME-CMD-MIB::mbgLtCmdExecute.0 = INTEGER: ReloadCong(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.
LANTIME M300/GPS Date: 29th July 2014 93
Page 94
14.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 mbgSNMP.3
MbgLANTIME
Root node of the Meinberg-MIB
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 mbgLANTIME.5
mbgLtCmd
LANTIME conguration variables
LANTIME control commands
Further detailed information can be found in the Meinberg MIB les.
Reference of LANTIME SNMP conguration variables:
SNMP branch mbgLtCfgNetwork
14 SNMP Support
Variable mbgLtCfghostname mbgLtCfgDomainname mbgLtCfgNameserver1 mbgLtCfgNameserver2 mbgLtCfgSyslogserver1 mbgLtCfgSyslogserver2 mbgLtCfgTelnetAccess
Data type string
Description
The hostname of the timeserver string The Domainname of the timeserver string (IPv4 or
IPv6-address)
IP-address of rst nameserver string (IPv4 or
IPv6-address)
IP-address of second nameserver string (IPv4 or
IPv6-address or hostname)
IP-address or hostname of rst syslogserver string (IPv4 or
IPv6-address or hostname)
IP-address or hostname of second syslogserver integer (0 = disabled, 1 = enabled)
Telnet access activated?
mbgLtCfgFTPAccess mbgLtCfgHTTPAccess integer (0 = disabled, 1 = enabled)
FTP-access activated?
integer (0 = disabled, 1 = enabled)
Webinterface activated?
mbgLtCfgHTTPSAccess integer (0 = disabled, 1 = enabled)
Encrypted webinterface activated?
mbgLtCfgSNMPAccess integer (0 = disabled, 1 = enabled)
SNMP-daemon activated?
94 Date: 29th July 2014 LANTIME M300/GPS
14.1 Conguration over SNMP
SNMP branch mbgLtCfgNTP
Page 95
Variable mbgLtCfgSambaAccess mbgLtCfgIPv6Access
Data type integer (0 = disabled, 1 = enabled)
Description
LANManager-access activated?
integer (0 = disabled, 1 = enabled)
IPv6-protocol enabled?
mbgLtCfgSSHAccess mbgLtCfgNtpServer1IP integer (0 = disabled, 1 = enabled)
SSH-access activated?
string (IPv4 or
IPv6-address or hostname)
First external NTP-server mbgLtCfgNtpServer1KEY integer Link to the key which should be used for the rst NTP-server mbgLtCfgNtpServer2IP string (IPv4 or
IPv6-address or hostname)
Second external NTP-server mbgLtCfgNtpServer2KEY integer Link to the key which should be used for the second NTP-server mbgLtCfgNtpServer3IP string (IPv4 or
IPv6-address or hostname)
Third external NTP-server mbgLtCfgNtpServer3KEY integer mbgLtCfgStratumLocal
Clock integer(0..15)
Link to the key which should be used for the third NTP-server
Stratum-value 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)
IP-address, which has to be used for
NTP-broadcasts (or multicasts) mbgLtCfgNTPBroadcast
Key integer Link to the key which should be used for outgoing NTP-broadcasts mbgLtCfgNTPBroadcast
Autokey integer (0 = disabled, 1 = enabled)
Use autokey for NTP broadcasts?
mbgLtCfgAutokeyFeature integer (0 = disabled, 1 = enabled)
Use autokey feature of the NTP server?
LANTIME M300/GPS Date: 29th July 2014 95
Page 96 14 SNMP Support
SNMP branch mbgLtCfgEMail
Variable mbgLtCfgAtomPPS mbgLtCfgEMailTo
Data type integer (0 = disabled, 1 = enabled)
Description
Atom PPS (pulse per second) activated?
string (Liste von
EMail-addressn)
One or more (semicolon separated) email address(es). which should receive warnings and alarm notications from the timeserver mbgLtCfgEMailFrom string address)
(EMailThe EMail-address which is used as the senders address for email notifcations mbgLtCfgEMailSmarthost string (IPv4 or
IPv6-address or hostname)
The SMTP-host, which is used for sending mails mbgLtCfgSNMP mbgLtCfgWinpopup mbgLtCfgSNMPTrapRecei ver1 string (IPv4 or
IPv6-address or hostname)
First host, which receives notications sent as SMTP-traps mbgLtCfgSNMPTrapRecei ver1Community string The SNMP community used when sending SNMP-Traps to the rst host mbgLtCfgSNMPTrapRecei ver2 string (IPv4 or
IPv6-address or hostname)
Second host, which receives notications sent as SMTP-traps mbgLtCfgSNMPTrapRecei ver2Community mbgLtCfgSNMPRO
Community string string
The SNMP community used when sending SNMP-Traps to the second host
The SNMP community, which has readonly access and therefore can be used to only monitor status variables or conguration values (SNMP V2c) mbgLtCfgSNMPRW
Community string mbgLtCfgSNMPContact mbgLtCfgSNMPLocation mbgLtCfgWMailAddress1 mbgLtCfgWMailAddress2 string string string string
The SNMP community, which has readwrite access and there for can be used to monitor status variables and get/set conguration values (SNMP V2c)
Contact information (e.g. name of a contact person) of the timeserver
Location (e.g. building/room number) of the timeserver
First receiver of notications sent as windows popup messages
Second receiver of notications sent as windows popup messages
96 Date: 29th July 2014 LANTIME M300/GPS
14.1 Conguration over SNMP Page 97
SNMP branch Variable Data type mbgLtCfgWalldisplay mbgLtCfgVP100Display1IP string (IPv4 or
IPv6-address or hostname)
Description hostname or IP-address of the rst wallmount display used for showing notications mbgLtCfgVP100Display
1SN string (Hexstring) The serial number of the rst wall mount display used for showing notications
(can be found in the setup menu of the display) mbgLtCfgVP100Display
2IP string (IPv4 or
IPv6-address or hostname) hostname or IP-address of the second wall mount display used for showing notications mbgLtCfgNotify mbgLtCfgVP100Display
2SN string (Hexstring) The serial number of the rst wall mount display used for showing notications
(can be found in the setup menu of the display) mbgLtCfgNotifyNTPNot
Sync string(combination) Exactly one, none or a combination of the following notication 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 string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event NTP Daemon stopped mbgLtCfgNotifyNTP
Stopped mbgLtCfgNotifyServer
Boot string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event Timeserver reboot mbgLtCfgNotifyRefclock
NotResponding string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event Refclock not ready mbgLtCfgNotifyRefclock
NotSync string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event Refclock not synchron mbgLtCfgNotifyAntenna
Faulty string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event GPS antenna not connected or dammaged mbgLtCfgNotifyAntenna
Reconnect string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event GPS antenna reconnected mbgLtCfgNotifyCong
Changed string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event Conguration changed mbgLtCfgNotifyLeapSecond
Announced string (combination)
(see mbgLtCfgNotifyNTPNotSync) for the event Leap second announced
LANTIME M300/GPS Date: 29th July 2014 97
Page 98 14 SNMP Support
SNMP branch mbgLtCfgEthernet
Variable mbgLtCfgEthernetIf0IPv4
IP
Data type string (IPv4 IPaddress)
Description
IPv4-address of rst network interface of the timeserver mbgLtCfgEthernetIf0IPv4
Netmask string (IPv4 Netzmaske)
IPv4-netmask of rst network interface of the timeserver mbgLtCfgEthernetIf0IPv4
Gateway string (IPv4 IPaddress)
IPv4-address of the default gateway of the timeservers rst network interface mbgLtCfgEthernetIf0DHCP
Client integer (0 = disabled, 1 = enabled)
Congure the rst network interface of the timeserver with DHCP?
mbgLtCfgEthernetIf0IPv6
IP1 string (IPv6 IPaddress)
First IPv6-IP-address of the timeservers rst network interface mbgLtCfgEthernetIf0IPv6
IP2 string (IPv6 IPaddress)
Second IPv6-IP-address of the timeservers rst network interface mbgLtCfgEthernetIf0IPv6
IP3 string (IPv6 IPaddress)
Third IPv6-IP-address of the timeservers rst network interface mbgLtCfgEthernetIf0IPv6
Autoconf integer (0 = disabled, 1 = enabled)
Activate autoconf for the IPv6 - conguration of the timeservers rst network interface?
mbgLtCfgEthernetIf0
NetlinkMode integer (0..4) Conguration of the network-speed and 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!
98 Date: 29th July 2014 LANTIME M300/GPS
14.2 SNMP Traps Page 99
14.2 SNMP Traps
If congured, 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 specic 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 stopped"
"Server boot"
NTP not synchronised to refclock
NTP stopped
System has rebooted
"Receiver not responding" no answer from GPS
"Receiver not sync" GPS receiver not synchronised
"Antenna faulty"
"Antenna reconnect"
GPS antenna not connected
GPS antenna reconnected
"Cong changed" System parameter changed by user
Leap second announced Leap second announced
See the Notication page at the web interface and Command Line Interface description to learn how to congure the SNMP trap receivers.
14.2.1 SNMP Trap Reference
All traps can be found under the mbgLtTraps section in the Meinberg MIB. A special trap exists for every notication event the timeserver knows. Please note that the traps are only sent if you congured the notication 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:
• mbgLtTrapNTPNotSync (mbgLtTraps.1): Whenever the NTP daemon (ntpd) looses sync, it will generate this trap and send it to the congured SNMP trap receivers.
• mbgLtTrapNTPStopped (mbgLtTraps.2): This trap is sent when the NTP daemon stopped, manually or because of an error condition.
• mbgLtTrapServerBoot (mbgLtTraps.3): After nishing the boot process, this trap is generated.
• mbgLtTrapReceiverNotResponding (mbgLtTraps.4): Trap to be sent when the internal receiver of the timeserver is not responding.
• mbgLtTrapReceiverNotSync (mbgLtTraps.5): If the internal receiver looses sync, the SNMP trap receivers will receive this trap.
• mbgLtTrapAntennaFaulty (mbgLtTraps.6): This trap will be sent whenever the timeserver recognises a broken connection to the antenna of the receiver.
• mbgLtTrapAntennaReconnect (mbgLtTraps.7): After the connection to the antenna has been reestablished, this trap is sent.
• mbgLtTrapCongChanged (mbgLtTraps 8): After reloading its conguration, the timeserver generates this trap.
• mbgLtTrapLeapSecondAnnounced (mbgLtTraps 9): If a leap second has been announced by the internal
GPS receiver, this trap will be sent.
• mbgLtTrapTestNotication (mbgLtTraps 99): This trap is sent whenever you are requesting a test notication; it is only used for testing the connection between the timeserver and your SNMP trap receivers.
LANTIME M300/GPS Date: 29th July 2014 99
Page 100 15 Attachment: Technical Information
15 Attachment: Technical Information
15.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
100 Date: 29th July 2014 LANTIME M300/GPS
15.2 Technical Specications M600/300 Multipac
15.2 Technical Specifications M600/300 Multipac
HOUSING:
LC-DISPLAY:
Metal desktop case, Schro 282T
Front panel: 1U/84HP (43 mm high / 442 mm wide)
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 VDC
12 VDC
24 VDC
48 VDC
DC Input
+
INPUT FUSE:
PROTECTION
RATING:
POWER
CONSUMPTION:
PHYSICAL
DIMENSIONS:
AMBIENT
TEMPERATURE:
HUMIDITY:
Electronic
IP20
28W
442 mm wide x 43 mm high x 288 mm deep
(498 mm wide with mounting bracket, 85mm high as XL/2U model)
0 ... 50 ◦ C
85 % max.
Page 101
LANTIME M300/GPS Date: 29th July 2014 101
Page 102 15 Attachment: Technical Information
15.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 oce 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.
15.3.1 CE-Label
Low voltage directive:
EMV-directive:
2006/95/EC EN 60950-1
Safety of Information Technology Equipment, including Electrical Business Equipment
Electromagnetic compatibility.
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
102 Date: 29th July 2014 LANTIME M300/GPS
15.3 Safety instructions for building-in equipment Page 103
15.3.2 Compliance with International Standards
Safety: UL 60950-1:2007
CAN/CSA-C22.2 N0.60950-1-07
Information Technology Equipment - Safety - Part 1: General Requirements cTUVus Certicate No. CU 72091503 01
EMC: FCC 47 CFR Part 2
General Rules and Regulations
FCC 47 CFR Part 15
Radio Frequency Devices (Subpart B)
ANSI C63.4:2009
American National Standard for Methods of Measuring of Radio-Noise Emissions from Low-Voltage Electrical and Electronic Equipment in the Range of 9 kHz to 40 GHz.
NOTE: This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
Changes or modications of the devices not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
ICES-003 Issue 5
Spectrum Management and Telecommunications Policy.
Interference-Causing Equipment Standard.
Digital Apparatus
CAN ICES-3 (A)/NMB-3(A)
LANTIME M300/GPS Date: 29th July 2014 103
Page 104 15 Attachment: Technical Information
15.4 Front and Rear Panel Connectors
Name
Front panel
TERMINAL
Network
USB
Rear panel
Network (LAN0-LAN1)
PPS
10 MHz,
Error
COM 0, COM 1
Antenna
Power supply
Type
9pin. D-SUB
RJ-45
USB connector
Signal
RS-232
Ethernet
Cable shielded data line shielded data line
RJ-45
BNC
BNC
DFK
Ethernet
TTL
TTL screw terminal shielded data line shielded coaxial line shielded coaxial line
9pin. D-SUB female RS232
BNC 10 MHz / 35.4 MHz shielded data line shielded coaxial line power cord receptable power supply cord option
Network (LAN2-LAN3)
Time Code modulated
DCLS
PPS, PPM, PPH, progr. Pulse,
Synthesizer
10 MHz,
10 MHz sine,
RJ-45
BNC
BNC
BNC
BNC
BNC
Ethernet shielded data line
3Vpp into 50 Ohm shielded coaxial line
2.5Vpp into 50 Ohm shielded coaxial line
2.5Vpp into 50 Ohm shielded coaxial line
2.5Vpp into 50 Ohm shielded coaxial line
1.2Vpp into 50 Ohm shielded coaxial line
104 Date: 29th July 2014 LANTIME M300/GPS
15.5 Pin Assignment: Serial Connectors
15.5 Pin Assignment: Serial Connectors
15.5.1 Serial Time String
Page 105
TxD0_OUT
RxD0_IN
GND -
1
6
5
9
TxD1_OUT
RxD1_IN
GND -
1
6
5
9
COM0 COM1
The 9pin female connectors can be connected to a PC with a direct cable.
15.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 congure 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. Congure 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_OUT-
CTS_IN-
RI_IN-
6
9
1
5
-DCD_IN
-RXD_IN
-TXD_OUT
-DTR_OUT
-GND
TERM
LANTIME M300/GPS Date: 29th July 2014 105
Page 106 15 Attachment: Technical Information
15.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 notication conditions. In the notication 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 notication conditions will be reseted by any access via the WEB or CLI interface (if no TIME SYNC ERROR is active).
15.6.1 Technical Specification
SWITCHING VOLTAGE max.:
SWITCHING CURRENT max.:
SWITCHING LOAD max.: DC
AC
SWITCHING-CURRENT
UL/CSA:
RESPONSE TIME:
0.46A
0.46A
1A ca.2ms
125 VDC
150 VAC
1A
30 W
60 VA
150V AC
65V DC
30V DC
Normal Operation : CO - NO connected
Error: CO - NC connected
Error
CO NO NC
Error
VCC
106 Date: 29th July 2014 LANTIME M300/GPS
15.7 Technical Specications GPS receiver
15.7 Technical Specifications GPS receiver
RECEIVER:
ANTENNA:
6 channel C/A code receiver with external antenna/converter unit
Antenna/converter unit with remote power supply refer to chapter
"Technical Specications GPS Antenna"
ANTENNA
INPUT: Antenna circuit dc-insulated; dielectric strength: 1000 V
Length of cable: refer to chapter "Mounting the Antenna"
TIME TO
SYNCHRONIZATION: One minute with known receiver position and valid almanac
12 minutes if invalid battery buered memory
ACCURACY
OF PULSES: Depends on oscillator option, after synchronization and 20 minutes of operation:
< +- 250nsec (TCXO, OCXO-LQ)
< +- 100nsec (OCXO-MQ,-HQ,-DHQ)
SERIAL PORTS:
< +- 2
µ sec during the rst 20 minutes of operation
2 asynchronous serial connectors (RS-232)
COM0:
COM1: xed, internal used congurable, sending Standard Meinberg
Time String (once per second or per minute)
Page 107
LANTIME M300/GPS Date: 29th July 2014 107
Page 108
15.7.1 Oscillator specifications
15 Attachment: Technical Information
108 Date: 29th July 2014 LANTIME M300/GPS
15.7 Technical Specications GPS receiver
15.7.2 Technical Specifications GPS Antenna
ANTENNA: dielectrical patch antenna, 25 x 25 mm receive frequency: 1575.42 MHz
BANDWITH:
CONVERTER:
9 MHz local oscillator to converter frequency: rst IF frequency:
10 MHz
35.4 MHz
POWER
REQUIREMENTS: 12V ... 18V, @ 100mA
(provided via antenna cable)
N-Type, female CONNECTOR:
AMBIENT
TEMPERATURE:
HOUSING:
-40 ... +65 ◦ C
ABS plastic case for outdoor installation (IP66)
Physical Dimension:
Page 109
LANTIME M300/GPS Date: 29th July 2014 109
Page 110 15 Attachment: Technical Information
15.8 Technical Specifications LAN CPU
PROCESSOR: AMD Geode TM LX 800 (500 MHz, 128 KB L2 cache, 3.6 W)
MAIN MEMORY:
CACHE-MEMORY:
FLASHDISK:
NETWORK
CONNECTOR:
SERIAl -
INTERFACE: onboard 256 MByte
16 KB 2nd Level Cache
1 GB
10/100 MBIT with RJ45-Jack
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 :
VGA-CONNECTION:
KEYBOARD
CONNECTION:
STATE LEDs:
POWER
REQUIREMENTS:
FRONTPANEL:
CONNECTOR:
One LPT-Port male connector type C 96
10-pol pin contact strip
10-pol pin contact strip
- power supply
- 'Connect', 'Activity' and 'Speed' of the network connection
5 V +- 5 %, @ 1 A
LANTIME in 3U modular case
3U / 4 TE (128 mm high x 20,3 mm wide)
According to DIN 41612, type C 96, rows a+b+c (male)
DSUB-plug (9-pol) RJ45-jack, USB Port
AMBIENT
TEMPERATURE:
HUMIDITY:
0 ... 50 ◦ C
85 % max.
110 Date: 29th July 2014 LANTIME M300/GPS
15.9 Time Code Option Page 111
15.9 Time Code Option
15.9.1 Abstract of Time Code
The transmission of coded timing signals began to take on widespread importance in the early 1950s. Especially the US missile and space programs were the forces behind the development of these time codes, which were used for the correlation of data. The denition of time code formats was completely arbitrary and left to the individual ideas of each design engineer. Hundreds of dierent time codes were formed, some of which were standardized by the "Inter Range Instrumentation Group" (IRIG) in the early 60s.
Except these "IRIG Time Codes", other formats like NASA36, XR3 or 2137 are still in use. The M300/GPS however generates the IRIG-B, AFNOR NFS 87-500 code as well as IEEE1344 code which is an IRIG coded extended by information for time zone, leap second and date.
15.9.2 Block Diagram Time Code
10 Mhz
PPS
EPLD digital sinewave generator modulator timecode microcontroller
D/A converter driver
50 Ω unbalanced driver
TTL
Time Code AM
Time Code DCLS
LANTIME M300/GPS Date: 29th July 2014 111
Page 112
15.9.3 IRIG Standard Format
15 Attachment: Technical Information
112 Date: 29th July 2014 LANTIME M300/GPS
15.9 Time Code Option
15.9.4 AFNOR Standard Format
Page 113
LANTIME M300/GPS Date: 29th July 2014 113
Page 114 15 Attachment: Technical Information
57
58
59
60
54
55
56
49
50
51
52
53
61
62
63
64
65
69
70
71
72
66
67
68
73
74
75
15.9.5 Assignment of CF Segment in IEEE1344 Code
Bit No.
Designation Description
Position Identier P5
Year BCD encoded 1
Year BCD encoded 2
Year BCD encoded 4
Year BCD encoded 8 empty, always zero
Year BCD encoded 10
Year BCD encoded 20 low nibble of BCD encoded year high nibble of BCD encoded year
Year BCD encoded 40
Year BCD encoded 80
Position Identier P6
LSP - Leap Second Pending
Timezone Oset Sign
TZ Oset binary encoded 1 set up to 59s before LS insertion
LS - Leap Second 0 = add leap second, 1 = delete leap second
1.)
DSP - Daylight Saving Pending set up to 59s before daylight saving changeover
DST - Daylight Saving Time set during daylight saving time sign of TZ oset 0 = '+', 1 = '-'
Oset from IRIG time to UTC time.
Encoded IRIG time plus TZ Oset equals UTC at all times!
TZ Oset binary encoded 2
TZ Oset binary encoded 4
TZ Oset binary encoded 8
Position Identier P7
TZ Oset 0.5 hour
TFOM Time gure of merit
TFOM Time gure of merit
TFOM Time gure of merit
TFOM Time gure of merit
PARITY set if additional half hour oset time gure of merit represents approximated clock error.
0x00 = clock locked, 0x0F = clock failed parity on all preceding bits incl. IRIG-B time
2.)
1.) current rmware does not support leap deletion of leap seconds
2.) TFOM is cleared, when clock is synchronized rst after power up. see chapter Selection of generated timecode
114 Date: 29th July 2014 LANTIME M300/GPS
15.9 Time Code Option
15.9.6 Generated Time Codes
Besides the amplitude modulated sine wave signal, the board also provides unmodulated
DC-Level Shift TTL output in parallel. Thus six time codes are available.
a) B002: 100 pps, DCLS signal, no carrier
BCD time-of-year b) B122: c) B003: d) B123: e) B006: f) B126: g) B007: h) B127: i) AFNOR: j) IEEE1344: k) C37.118
100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year
100 pps, DCLS signal, no carrier
BCD time-of-year, SBS time-of-day
100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, SBS time-of-day
100 pps, DCLS Signal, no carrier
BCD time-of-year, Year
100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, Year
100 pps, DCLS Signal, no carrier
BCD time-of-year, Year, SBS time-of-day
100 pps, AM sine wave signal, 1 kHz carrier frequency
BCD time-of-year, Year, SBS time-of-day
Code according to NFS-87500, 100 pps, wave signal,
1kHz carrier frequency, BCD time-of-year, complete date,
SBS time-of-day, Signal level according to NFS-87500
Code according to IEEE1344-1995, 100 pps, AM sine wave signal,
1kHz carrier frequency, BCD time-of-year, SBS time-of-day,
IEEE1344 extensions for date, timezone, daylight saving and leap second in control functions (CF) segment.
(also see table 'Assignment of CF segment in IEEE1344 mode')
Like IEEE1344 - with turned sign bit for UTC-Oset
Page 115
LANTIME M300/GPS Date: 29th July 2014 115
Page 116 15 Attachment: Technical Information
15.9.7 Selection of Generated Time Code
The time code to be generated can be selected by Menu Setup IRIG-settings or the GPS Monitorprogram
GPSMON32 (except Lantime models). DC-Level Shift Codes (PWM-signal) B00x and modulated sine wave carrier B12x are always generated simultaneously. Both signals are provided at the VG64-Connector, i.e. if code
B132 is selected also code B002 is available. This applies for the codes AFNOR NFS 87-500 and IEEE1344 as well.
The TFOM eld in IEEE1344 code is set dependent on the 'already sync'ed' character ('#') which is sent in the serial time telegram. This character is set, whenever the preconnected clock was not able to synchronize after power up reset. The 'time gure of merit' (TFOM) eld is set as follows.
Clock synchronized once after power up:
Clock not synchronized after power up:
TFOM = 0000
TFOM = 1111
For testing purposes the output of TFOM in IEEE1344 mode can be disabled. The segment is set to all zeros then.
15.9.8 Outputs
The module M300/GPS provides modulated (AM) and unmodulated (DCLS) outputs. The format of the timecodes is illustrated in the diagramms "IRIG-" and "AFNOR standard-format".
AM - Sine Wave Output
The amplitude-modulated carrier is available at the VG-connector pin 14a. The carrier frequency depends on the code and has a value of 1 kHz (IRIG-B). The signal amplitude is 3 Vpp (MARK) and 1 Vpp (SPACE) into
50 Ohm. The encoding is made by the number of MARK-amplitudes during ten carrier waves. The following agreements are valid: a) binary "0": b) binary "1":
2 MARK-amplitudes, 8 SPACE-amplitudes
5 MARK-amplitudes, 5 SPACE-amplitudes c) position-identier: 8 MARK-amplitudes, 2 SPACE-amplitudes
PWM DC Output
The pulse width DCLS signals shown in the diagramms "IRIG" and "AFNOR standard format" are coexistent to the modulated output and is available at the VG connector pin 13a with TTL level.
15.9.9 Technical Data
OUTPUTS: Unbalanced AM-sine wave-signal:
3 VPP (MARK) / 1 VPP (SPACE) into 50 Ohm
DCLS signal: TTL
116 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 117
15.10 Time Strings
15.10.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:
<STX>D:dd.mm.yy;T:w;U:hh.mm.ss;uvxy<ETX>
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 dened below:
<STX> dd.mm.yy
w
Start-Of-Text, ASCII Code 02h sending with one bit accuracy at change of second the current date: dd mm yy the century (00..99) the day of the week day of month month year of
(01..31)
(01..12)
(1..7, 1 = Monday) hh.mm.ss
uv the current time: hh mm ss hours minutes
(00..23)
(00..59) seconds (00..59, or 60 while leap second) clock status characters (depending on clock type): u: `#' v:
` `
`*'
` `
GPS: clock is running free (without exact synchr.)
PZF: time frame not synchronized
DCF77: clock has not synchronized after reset
(space, 20h)
GPS: clock is synchronous (base accuracy is reached)
PZF: time frame is synchronized
DCF77: clock has synchronized after reset
GPS: receiver has not checked its position
PZF/DCF77: clock currently runs on XTAL
(space, 20h)
GPS: receiver has determined its position
PZF/DCF77: clock is syncronized with transmitter x y time zone indicator:
`U'
` `
UTC
CET
`S' anouncement of discontinuity of time, enabled during last hour before discontinuity comes in eect:
`!'
`A'
` ` announcement of start or end of daylight saving time announcement of leap second insertion
(space, 20h) nothing announced
<ETX> End-Of-Text, ASCII Code 03h
Universal Time Coordinated, formerly GMT
European Standard Time, daylight saving disabled
(CEST) European Summertime, daylight saving enabled
LANTIME M300/GPS Date: 29th July 2014 117
Page 118 15 Attachment: Technical Information
15.10.2 Format of the Meinberg GPS Time String
The Meinberg Standard Time String is a sequence of 36 ASCII characters starting with the STX (start-of-text) character and ending with the ETX (end-of-text) character. Contrary to the Meinberg Standard Telegram the
Meinberg GPS Timestring carries no local timezone or UTC but the direct GPS time without conversion into
UTC. The format is:
G y
<STX>D:tt.mm.jj;T:w;U:hh.mm.ss;uvGy;lll<ETX>
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 dened below:
<STX> tt.mm.jj
Start-Of-Text (ASCII code 02h) the current date: tt mm month jj day of month (01..31) year of the century
(01..12)
(00..99) w hh.mm.ss
the day of the week (1..7, 1 = monday) the current time: hh mm minutes ss hours seconds
(00..23)
(00..59)
(00..59, or 60 while leap second) uv clock status characters: u: '#'
' ' clock is running free (without exact synchr.)
(space, 20h) clock is synchronous (base accuracy is reached) v: `*'
` ` receiver has not checked its position
(space, 20h) receiver has determined its position time zone indicator 'GPS-Time' lll
<ETX> anouncement of discontinuity of time, enabled during last hour before discontinuity comes in eect:
`A' announcement of leap second insertion
` ` (space, 20h) nothing announced number of leap seconds between UTC and GPS-Time
(UTC = GPS-Time + number of leap seconds)
End-Of-Text, (ASCII Code 03h)
118 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 119
15.10.3 Format of the Meinberg Capture String
The Meinberg Capture String is a sequence of 31 ASCII characters terminated by a CR/LF (Carriage Return/Line
Feed) combination. The format is:
CHx_tt.mm.jj_hh:mm:ss.f <CR><LF>
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 dened below: x
_
0 or 1 corresponding on the number of the capture input
ASCII space 20h dd.mm.yy the capture date: dd mm yy day of month month year of the century
(01..31)
(01..12)
(00..99) hh:mm:ss.f the capture time: hh mm ss f hours minutes
(00..23)
(00..59) seconds (00..59, or 60 while leap second) fractions of second, 7 digits
<CR>
<LF>
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
LANTIME M300/GPS Date: 29th July 2014 119
Page 120 15 Attachment: Technical Information
15.10.4 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:
<STX>
<STX>dd.mm.yy/w/hh:mm:ssxxxxuv<ETX>
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 dened below:
Start-Of-Text, ASCII Code 02h sending with one bit accuracy at change of second dd.mm.yy
the current date: dd mm yy w day of month month year of the century the day of the week
(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday) hh:mm:ss the current time: hh mm ss hours minutes seconds xxxx u
(00..23)
(00..59)
(00..59, or 60 while leap second) time zone indicator:
`UTC`
`CET`
`CEST'
Universal Time Coordinated, formerly GMT
European Standard Time, daylight saving disabled
European Summertime, daylight saving enabled clock status characters:
`#'
` ` clock has not synchronized after reset
(space, 20h) clock has synchronized after reset v
<CR>
<LF>
<ETX> 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
120 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 121
15.10.5 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:
<STX>
<STX>tt.mm.jj; w; hh:mm:ss; voo:oo; acdfg i;bbb.bbbbn lll.lllle hhhhm<ETX>
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 dened below:
Start-Of-Text, ASCII Code 02h sending with one bit occuracy at change of second dd.mm.yy
the current date: dd mm yy day of month month w year of the century the day of the week hh.mm.ss
the current time: v oo:oo ac hh mm ss hours minutes seconds
(01..31)
(01..12)
(00..99)
(1..7, 1 = Monday)
(00..23)
(00..59)
(00..59, or 60 while leap second) sign of the oset of local timezone related to UTC oset of local timezone related to UTC in hours and minutes clock status characters: a: `#'
` ` c: `*'
` ` clock has not synchronized after reset
(space, 20h) clock has synchronized after reset
GPS receiver has not checked its position
(space, 20h) GPS receiver has determined its position i f d g time zone indicator:
`S'
` `
CEST
CET
European Summertime, daylight saving enabled
European Standard Time, daylight saving disabled 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 anouncement of discontinuity of time, enabled during last hour before discontinuity comes in eect:
`A'
` ` announcement of leap second insertion
(space, 20h) nothing announced leap second insertion
`L'
` ` leap second is actually inserted
(active only in 60th sec.)
(space, 20h) no leap second is inserted bbb.bbbb
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
LANTIME M300/GPS Date: 29th July 2014 121
Page 122 lll.llll
e hhhh
<ETX>
`S' south d. equator longitude of receiver position in degrees leading signs are replaced by a space character (20h) longitude, the following characters are possible:
`E'
`W' east of Greenwich west of Greenwich altitude above WGS84 ellipsoid in meters leading signs are replaced by a space character (20h)
End-Of-Text, ASCII Code 03h
15 Attachment: Technical Information
122 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 123
15.10.6 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: ddmmyy a hh
$
$GPRMC,hhmmss.ss,A,bbbb.bb,n,lllll.ll,e,0.0,0.0,ddmmyy,0.0,a*hh<CR><LF>
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 dened below:
Start character, ASCII Code 24h sending with one bit accuracy at change of second hhmmss.ss the current time: hh mm ss ss hours minutes seconds fractions of seconds
A
(00..23)
(00..59)
(00..59, or 60 while leap second)
(1/10 ; 1/100)
Status (A = time data valid)
(V = time data not valid) bbbb.bb
n lllll.ll
latitude of receiver position in degrees leading signs are replaced by a space character (20h) latitude, the following characters are possible:
`N'
`S' north of equator south d. equator longitude of receiver position in degrees leading signs are replaced by a space character (20h) e
<CR>
<LF> longitude, the following characters are possible:
`E'
`W' east of Greenwich west of Greenwich the current date: dd mm yy day of month month year of the century
(01..31)
(01..12)
(00..99) magnetic variation checksum (EXOR over all characters except `$' and `*')
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
LANTIME M300/GPS Date: 29th July 2014 123
Page 124 15 Attachment: Technical Information
15.10.7 Format of the NMEA 0183 String (GGA)
The NMEA (GGA) String is a sequence of characters starting with the `$GPRMC' character and ending with the characters CR (carriage return) and LF (line-feed). The format is: hhh.h
aaa.h
M ggg.g
M cs
<CR>
<LF>
$
$GPGGA,hhmmss.ss,bbbb.bbbbb,n,lllll.ll,e,A,vv,hhh.h,aaa.a,M,ggg.g,M0*cs<CR><LF>
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 dened below:
Start character, ASCII Code 24h sending with one bit accuracy at change of second hhmmss.ss the current time: hh mm ss ss hours minutes seconds fractions of seconds
A
(00..23)
(00..59)
(00..59, or 60 while leap second)
(1/10 ; 1/100)
Status (A = time data valid)
(V = time data not valid)
A vv bbbb.bbbbb latitude of receiver position in degrees leading signs are replaced by a space character (20h) n lllll.lllll
latitude, the following characters are possible:
`N'
`S' north of equator south d. equator longitude of receiver position in degrees leading signs are replaced by a space character (20h) e longitude, the following characters are possible:
`E'
`W' east of Greenwich west of Greenwich
Position x (1 = yes, 0 = no)
Satellites used (0..12)
HDOP (Horizontal Dilution of Precision)
Mean Sea Level altitude (MSL = altitude of WGS84 - Geoid Separation)
Units, meters (xed value)
Geoid Separation (altitude of WGS84 - MSL)
Units, meters (xed value) checksum (EXOR over all characters except `$' and `*')
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
124 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 125
15.10.8 Format of the NMEA 0183 String (ZDA)
The NMEA String is a sequence of 38 ASCII characters starting with the `$GPZDA' character and ending with the characters CR (carriage return) and LF (line-feed). The format is:
$GPZDA,hhmmss.ss,dd,mm,yyyy,HH,II*cs<CR><LF>
ZDA - Time and Date: UTC, day, month, year and local timezone.
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 dened below:
$ Start character, ASCII Code 24h sending with one bit accuracy at change of second hhmmss.ss the current UTC time: hh mm ss hours minutes seconds
HH,II
(00..23)
(00..59)
(00..59 or 60 while leap second) the local timezone (oset to UTC):
HH
II hours minutes
(00..+-13)
(00..59) dd,mm,yy the current date: dd mm yyyy day of month month year cs
<CR>
<LF> Line Feed, ASCII Code 0Ah
(01..31)
(01..12)
(0000..9999) checksum (EXOR over all characters except `$' and `*')
Carriage Return, ASCII Code 0Dh
LANTIME M300/GPS Date: 29th July 2014 125
Page 126 15 Attachment: Technical Information
15.10.9 Format of the ABB SPA Time String
The ABB SPA Time String is a sequence of 32 ASCII characters starting with the characters ">900WD" and ending with the <CR> (Carriage Return) character. The format is:
>900WD:yy-mm-tt_hh.mm;ss.f:cc<CR>
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 dened below: yy-mm-tt the current date: yy mm dd year of the century month day of month
_ Space (ASCII code 20h)
(00..99)
(01..12)
(01..31) hh.mm;ss.f the current time: hh mm ss f hours minutes seconds milliseconds cc
<CR>
(00..23)
(00..59)
(00..59, or 60 while leap second)
(000..999)
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
126 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 127
15.10.10 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
T:yy:mm:dd:ww:hh:mm:ss<CR><LF>
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 dened below:
Start character sending with one bit accuracy at change of second yy:mm:dd the current date: yy mm dd ww year of the century month day of month the day of the week hh:mm:ss the current time:
<CR>
<LF> hh mm ss hours minutes seconds
Carriage Return, ASCII Code 0Dh
Line Feed, ASCII Code 0Ah
(00..99)
(01..12)
(01..31)
(01..07, 01 = monday)
(00..23)
(00..59)
(00..59, or 60 while leap second)
LANTIME M300/GPS Date: 29th July 2014 127
Page 128 15 Attachment: Technical Information
15.10.11 Format of the RACAL standard Time String
The RACAL standard Time String is a sequence of 16 ASCII characters terminated by a X (58h) character and ending with the CR (Carriage Return, ASCII Code 0Dh) character. The format is:
<X>
<X><G><U>yymmddhhmmss<CR>
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 dened below:
Control character sending with one bit accuracy at change of second code 58h
<G>
<U> yymmdd
Control character
Control character code 47h code 55h hh:mm:ss the current date: yy mm dd year of the century month day of month the current time: hh mm ss hours minutes seconds
(00..99)
(01..12)
(01..31)
(00..23)
(00..59)
(00..59, or 60 while leap second)
<CR> Carriage Return, ASCII code 0Dh
Interface parameters: 7 Databits, 1 Stopbit, odd. Parity, 9600 Bd
128 Date: 29th July 2014 LANTIME M300/GPS
15.10 Time Strings Page 129
15.10.12 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:
<SOH>
<SOH>ddd:hh:mm:ssq<CR><LF>
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 dened 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 mm ss q hours minutes seconds
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)
<CR>
<LF>
Carriage-return (ASCII code 0Dh)
Line-Feed (ASCII code 0Ah)
LANTIME M300/GPS Date: 29th July 2014 129
Page 130 15 Attachment: Technical Information
15.10.13 Format of the ION Time String
The ION 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:
<SOH>
<SOH>ddd:hh:mm:ssq<CR><LF>
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 dened 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 mm ss q hours minutes seconds
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)
<CR>
<LF>
Carriage-return (ASCII code 0Dh)
Line-Feed (ASCII code 0Ah)
130 Date: 29th July 2014 LANTIME M300/GPS
15.11 Manual VP100/NET Display conguration
15.11 Manual VP100/NET Display configuration
send2display Version 0.1
usage: send2display -h hostname -s serialnumber [options]
Valid options are:
-h,
-s, host H Uses H as the hostname of the display unit serialnumber S Uses S as the serialnumber of the display (e.g. 03A00C7F)
-c, clear M
-b, beep
-a, clearall
-m, message M
Clear message M (0-31)
Beeper sound while showing the message
Clear all messages of the display
Create/change message M (0-31, default = 0)
-e,
-q, quiet
-v,
-?, executions E Sets number of consecutive executions to E (1-9, default = 1) verbose help
Quiet mode (no program output to stdout/stderr)
Verbose mode (output of debugging info on stdout)
Show help message
Dening messages a) Static or ashing text:
You can dene a maximum of 9 lines for a message.
Start with -(x) "text", where (x) represents the line number.
-1, line1 "text"
-2,
...
line2 "text"
Set text for line 1
Set text for line 2
You can set the duration and mode for each line separately. Speciy the following options directly after the text-denition of a line:
-f, noash
-d, duration X
Change line mode to static (default is ashing)
Set the duration of the line to x seconds (default is 3 seconds) b) Scrolling text:
You can dene 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, periodday D
-H, periodhour H
Display message every D days
Display message every H hours
-M, periodminute M 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
Page 131
LANTIME M300/GPS Date: 29th July 2014 131
Page 132
(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
15 Attachment: Technical Information
15.12 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_conguration:
##
# Conguration File #
##
# Conguration File Section
Conguration File Version Number:
Conguration File Last Change:
# 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
# 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
# EMail Section
EMail To Address
EMail From Address
EMail Smarthost
4.17
[ASCII,50] : LanGpsV4
[ASCII,50] : py.meinberg.de
[IP]
[IP]
[IP]
[IP]
[ASCII,50] :
[ASCII,50] :
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
[BOOL]
:
:
:
:
: 1
: 1
: 1
: 1
: 1
: 1
: 0
: 1
[ASCII,50] :
[NUM]
[BOOL]
[ASCII,50] :
[NUM]
[BOOL] :
:
:
:
:
[NUM]
[BOOL]
:
:
[NUM,0..15] : 12
[NUM]
[BOOL]
[BOOL]
[IP]
[NUM]
[BOOL]
[NUM]
:
: 0
: 1
: 0
:
: 0
: 0
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
132 Date: 29th July 2014 LANTIME M300/GPS
15.13 Global Option File
# SNMP Section
SNMP Trap Receiver Address 1
SNMP Trap Receiver Community 1
SNMP Trap Receiver Address 2
SNMP Trap Receiver Community 2
SNMP V3 User Name
SNMP Read Community String
SNMP Write Community String
SNMP Contact String
SNMP Location String
# Windows Messages Section
WMail Address 1
WMail Address 2
# VP100 Display Section
VP100 Display Address 1
VP100 Display Sernum 1
VP100 Display Address 2
VP100 Display Sernum 2
# Notication Section
Notication on NTP_not_sync
Notication on NTP_stopped
Notication on Server_boot
Notication on Refclock_not_respon.
Notication on Refclock_not_sync
Notication on Antenna_faulty
Notication on Antenna_reconnect
Notication on Cong_changed
Notication on Leap second announ.
# 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
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[ASCII,50] : root
[ASCII,50] : public
[ASCII,50] :
[ASCII,50] : Meinberg
[ASCII,50] : Germany
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[ASCII,50] :
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[CASE]
[IP]
[IP]
[BOOL]
[IP]
: 0
: 0
:
: 1
[IP]
[IP]
[BOOL]
[NUM,0:4] :
: 1
[NUM,0:4] :
:
:
:
:
:
:
:
:
:
:
:
Page 133
15.13 Global Option File
This le contains all global options for special hardware conguration 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 : 1
SYSTEM LAYOUT
SYSTEM ADV LAYOUT
SYSTEM LANGUAGE
SYSTEM PARAMETER
SYSTEM DESIGN
: 0
: 0
: 0
: server
: 0
LANTIME M300/GPS Date: 29th July 2014 133
Page 134 15 Attachment: Technical Information
15.14 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.
15.14.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
15.14.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
134 Date: 29th July 2014 LANTIME M300/GPS
15.14 Third party software Page 135
15.14.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 specic,
* 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/GPS Date: 29th July 2014 135
Page 136 15 Attachment: Technical Information
15.14.4 mini httpd
For our web based conguration 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 ([email protected]). All rights reserved.
Redistribution and use in source and binary forms, with or without modication, 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 MER-
CHANTABILITY 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 INTERRUP-
TION) 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
136 Date: 29th July 2014 LANTIME M300/GPS
15.14 Third party software Page 137
15.14.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 modied 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 reect 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 modication 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 modications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modication".) Each licensee is addressed as "you".
Activities other than copying, distribution and modication 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/GPS Date: 29th July 2014 137
Page 138 15 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 modications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modied 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 modied 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 modied work as a whole. If identiable 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 modications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface denition 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.
138 Date: 29th July 2014 LANTIME M300/GPS
15.14 Third party software Page 139
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 species 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/GPS Date: 29th July 2014 139
Page 140 15 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 LIM-
ITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PUR-
POSE. 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 SERVIC-
ING, 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 PRO-
GRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPE-
CIAL, 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 IN-
ACCURATE 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
15.15 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 conguration 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 certicates
(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)
The desired menu function can be chosen by using ↑ 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
Lock Front Panel
In this submenu you can copy the conguration le from your LANTIME to the USB storage device.Now you can
Unlock Front Panel
140
Restore Config. and REBOOT
LANTIME M300/GPS
15.15 USB Stick Page 141
USB Memory Stick Main Menu
Backup Config. to USB Stick
USB Stick Menu (OK to confirm)
15.15.2 Menu Write Diagnostic File to USB Stick
USB Stick Menu (OK to confirm)
Lock Front Panel
USB Stick Menu (OK to confirm)
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 Stick Menu (OK to confirm)
Restore Config. and REBOOT
USB Stick Menu (OK to confirm)
Restore Config. and REBOOT
LANTIME M300/GPS Date: 29th July 2014 141
Page 142 15 Attachment: Technical Information
15.15.3 Keypad locking
The USB stick can be used for locking the function buttons of 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 with /mnt/ash/cong/keypad_lock. So it is possible to 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:
Write Diagn. File to USB Stick
When activating this submenu the le /mnt/ash/cong/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 Stick Menu (OK to confirm)
Unlock Front Panel
USB Stick Menu (OK to confirm)
NOTE: Restore Config. and REBOOT
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 [email protected]
.
15.15.4 Menu Restore Configuration
This command is for restoring the LANTIME conguration. 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..."
142 Date: 29th July 2014 LANTIME M300/GPS
15.16 List of Literature Page 143
15.16 List of Literature
[Mills88] Mills, D. L., "Network Time Protocol (Version 1) - specication and implementation",
DARPA Networking Group Report RFC-1059, University of Delaware, July 1988
[Mills89] Mills, D. L., "Network Time Protocol (Version 2) - specication and implementation",
DARPA Networking Group Report RFC-1119, University of Delaware, September 1989
[Mills90] Mills, D. L., "Network Time Protocol (Version 3) - specication, 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/GPS Date: 29th July 2014 143
Page 144 16 Konformitätserklärung
Declaration of Conformity
Doc ID: LANTIME M300/GPS-2014-06-12
Hersteller
Manufacturer
Produktbezeichnung
Product Designation
Meinberg Funkuhren GmbH & Co. KG
Lange Wand 9, D-31812 Bad Pyrmont erklärt in alleiniger Verantwortung, dass das Produkt, declares under its sole responsibility, that the product
LANTIME M300/GPS auf das sich diese Erklärung bezieht, mit den folgenden Normen übereinstimmt to which this declaration relates is in conformity with the following standards
EN55022:2010, Class B Limits and methods of measurement of radio interference characteristics of information technology equipment
EN55024:2010 Limits and methods of measurement of Immunity characteristics of information technology equipment
Safety of information technology equipment EN 60950-1:2006
(+A11:2009 +A12:2011)
EN 50581:2012 Technical documentation for the assessment of electrical and electronic products with respect to the restriction of hazardous substances gemäÿ den Richtlinien 2004/108/EG (Elektromagnetische Verträglichkeit), 2006/95/EG (Niederspannungsrichtlinie),
2011/65/EU (Beschränkung der Verwendung bestimmter gefährlicher Stoe) und 93/68/EWG (CE Kennzeichnung) sowie deren Ergänzungen.
following the provisions of the directives 2004/108/EC (electromagnetic compatibility), 2006/95/EC (low voltage directive), 2011/65/EU (restriction of the use of certain hazardous substances) and 93/68/EEC (CE marking) and its amendments.
Bad Pyrmont, 2014-06-12
144 Date: 29th July 2014 LANTIME M300/GPS
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
GPS synchronized time
Network Time Protocol (NTP)
Web interface
Remote configuration
Alarm notifications
Frequently asked questions
You can configure the LANTIME M300's TCP/IP settings using the front panel buttons or through the web interface. Refer to the manual for detailed instructions.
You can monitor the LANTIME M300's status using the front panel display, web interface, Telnet, SSH, or serial terminal connection. The manual outlines all the available methods.
The LANTIME M300 supports multiple alarm notification methods like email, SNMP traps, and even displays on an external large display (VP100/20/NET). You can configure these settings through the web interface or Telnet connection.