Ltos 6-24
Ltos 6-24
Ltos 6-24
1 Imprint 1
4 Introduction 17
4.1 Network Configuration Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.2 Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.3 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.4 Input and Output Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.5 Network Time Protocol (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.5.1 NTP Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.6 Option: Precision Time Protocol (PTP) / IEEE 1588 . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.6.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.2 Functionality in Master Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6.3 Functionality in Slave Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6.4 PTPv2 IEEE 1588-2008 Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5 Unboxing 31
6 LANTIME Installation 33
3
8.1.6 TCR Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.2 GNSS Signal Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.2.1 Meinberg GPS Antenna/Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
8.2.2 General GNSS Antennae . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
8.2.3 Powering up a GNSS Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.3 Long Wave Signal Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
8.3.2 Mounting and Installation of a Longwave Antenna . . . . . . . . . . . . . . . . . . . . . . . 67
8.3.3 DCF77 / PZF Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
8.4 Cable Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
12 Appendix 372
12.1 LANTIME CPU - Central Processing Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
12.1.1 Technical Specifications LAN CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
12.2 Time Telegrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
12.2.1 Format of the Meinberg Standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . 374
12.2.2 Format of the Meinberg GPS Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
12.2.3 Format of the Meinberg Capture String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
12.2.4 Format of the SAT Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
12.2.5 Format of the Uni Erlangen String (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12.2.6 Format of the NMEA 0183 String (RMC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
12.2.7 Format of the NMEA 0183 String (GGA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
12.2.8 Format of the NMEA 0183 String (ZDA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
12.2.9 Format of the ABB SPA Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
12.2.10 Format of the Computime Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
12.2.11 Format of the RACAL standard Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
12.2.12 Format of the SYSPLEX-1 Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
12.2.13 Format of the ION Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
12.2.14 Format of the ION Blanked Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
12.2.15 Format of the IRIG J Time String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
12.3 SyncMon Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
12.4 Third party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
12.4.1 Operating System GNU/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
12.4.2 Samba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
12.4.3 Network Time Protocol Version 4 (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
12.4.4 lighttpd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
12.4.5 GNU General Public License (GPL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
12.5 List of Literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
1 Imprint
Meinberg Funkuhren GmbH & Co. KG
Lange Wand 9, 31812 Bad Pyrmont / Germany
Phone: + 49 (0) 52 81 / 93 09 - 0
Fax: + 49 (0) 52 81 / 93 09 - 230
Internet: https://www.meinbergglobal.com
Mail: [email protected]
Date: 2019-03-13
If a procedure is marked with the following signal words, you may only continue, if you have understood and
fulfilled all requirements. In this documentation dangers and indications are classified and illustrated as follows:
DANGER!
The signal word indicates an imminently hazardous situation with a high risk level . This notice
draws attention to an operating procedure or similar proceedings, of which a non-observance may
result in serious personal injury or death .
WARNING!
The signal word indicates a hazard with a medium risk gradient . This notice draws attention to an
operating procedure, a procedure or the like which, if not followed, can lead to serious injuries ,
possibly resulting in death .
CAUTION!
The signal word indicates a hazard with a low risk gradient . This notice draws attention to an
operating procedure, a procedure or the like which, if not followed, can lead to minor injuries .
ATTENTION!
This notice draws attention to an operating procedure, a procedure or the like which, if not followed,
can cause damage to the product or loss of important data .
This manual contains important safety instructions for the installation and operation of the
device. Please read this manual completely before using the unit.
This device may only be used for the purpose described in this manual. In particular, the given
limits of the device must be observed. The safety of the installation in which the unit is
integrated is the responsibility of the installer!
Non-observance of these instructions can lead to a reduction in the safety of this device!
This manual is intended exclusively for electricians or persons trained by an electrician who are familiar with
the applicable national standards and safety rules. Installation, commissioning and operation of this device may
only be carried out by qualified personnel.
WARNING!
When the built-in unit is used in a terminal (e.g., housing cabinet), additional requirements
according to Standard IEC 60950-1 must be observed and complied with. In particular, the general
requirements and the safety of electrical equipment (such as IEC, VDE, DIN, ANSI) as well as the
applicable national standards are to be observed.
The device has been developed for use in the industrial sector as well as in residential areas and
can only be used in such environments. For environments with higher levels of soiling, additional
measures, e.g. Installation in an air-conditioned control cabinet required.
When unpacking, setting up, and before operating the equipment, be sure to read the information on
the hardware installation and the specifications of the equipment. These include, for example,
dimensions, electrical characteristics, and necessary ambient and climatic conditions, etc.
For mounting, the housing must not be damaged. No holes may be drilled in the housing.
For safety reasons, the device with the highest mass should be installed in the lowest position of
the rack. Other devices must be placed from the bottom to the top.
The device must be protected against mechanical stress such as vibration or shock.
When wiring the devices, the cables must be connected or disconnected in the order of the
arrangement described in the user documentation accompanying the device. Always attach all cables
to the plug during connection and removal. Never pull the cable itself. Pulling the cable can cause
the cables to disconnect from the plug.
Install the cables in way that they do not constitute a hazard (danger of tripping) and are not
damaged, i.e. kinked.
Before connecting to the power supply, a grounding cable must be connected to the earth connection
of the device.
Before operation, check that all cables and lines work properly and are undamaged. Pay particular
attention to the facts that the cables do not have kinks or that they are not too short around corners,
and no objects are placed on the cables. Also make sure that all connections are secure.
Faulty shielding or cabling will endanger your health (electrical shock) and may destroy other
equipment.
Ensure that all necessary safety precautions have been taken. Make all connections to a unit before
turning on the power. Observe the safety instructions on the device (see safety symbols).
The metal housing of the device is grounded. It must be ensured that enough air and creepage
distances to neighboring voltage-carrying parts are provided during assembly in the control cabinet
and no short circuits are caused.
In the case of malfunctions or servicing (e.g. in the event of a damaged housing or power cable or
when fluids or foreign objects enter), the current flow can be interrupted. Questions about the
house installation, need to be clarified with your house administration.
ATTENTION!
In order to ensure safe operation and to meet the requirements of IEC 62368-1, the device
must be correctly connected to the protective earth conductor via the protective earth
connection terminal.
Note:
Please use a grounding cable ≥ 1.5 mm2
Always pay attention to a correct crimp connection!
WARNING!
Avoiding Short-Circuits
Make sure not to get any objects or liquids inside the unit. Electric shock or short circuit
could result.
Ventilation Slots
Make sure that the ventilation slots are not covered or dusty, as there is a danger of overheating
during operation. Disturbances during operation can result.
Normal Operation
The normal operation and the observance of the EMC limits (electromagnetic compatibility) are only
ensured if the housing cover is properly installed and when the doors are closed (cooling, fire protection,
shielding against electrical, magnetic and electromagnetic fields).
WARNING!
When you are expanding the device, use only device parts that are approved for the system.
Non-observance may result in injury to the EMC or safety standards and cause malfunction
of the device.
If device parts, which are released for the system, are extended or removed there may be a
risk of injury in the area of the hands, due to the pull-out forces (approx. 60 N).
The device must not be opened, repairs to the device may only be carried out by the
manufacturer or by authorized personnel. Improper repairs can result in considerable
danger to the user (electric shock, fire hazard).
Unauthorized opening of the device or of individual parts of the device can also lead to
considerable risks for the user and result in a loss of warranty as well as an exclusion
of liability.
- Device parts can become very hot during operation. Do not touch these surfaces!
If necessary, switch off the unit before installing or removing any equipment,
and allow it to cool down.
CAUTION!
The lithium battery on the receiver modules has a service life of at least 10 years.
If an exchange is necessary, the following notes must be observed:
The device is equipped with a lithium battery. The battery must not be short-circuited
or recharged. Replacement of the lithium battery may only be carried out by the manufacturer
or authorized personnel.
Risk of explosion if the battery is not replaced correctly. Replace only with the same or
equivalent type recommended by the manufacturer.
When disposing used batteries, observe the local regulations for the disposal of
hazardous waste.
ATTENTION!
Do not wet clean the appliance! Penetrating water can cause considerable dangers to
the user (e.g., electric shock).
Liquid can destroy the electronics of the device! Liquid penetrates into the housing
of the device and can cause a short circuit of the electronics.
Only clean with a soft, dry cloth. Never use solvents or cleaners.
ATTENTION!
The designation ESD (Electrostatic Sensitive Devices) refers to measures which are used
to protect electrostatically endangered components from electrostatic discharge and thus
to prevent destruction. Systems and assemblies with electrostatically endangered components
usually have the following characteristics:
Ensure that you wear a grounding strap on the wrist when working with such assemblies, which
you attach to an unpainted, non-conductive metal part of the system.
Use only tools and devices that are free from static electricity.
Transporting Assemblies
Assemblies may only be touched at the edge. Do not touch any pins or conductors on assemblies.
Storing Assemblies
Always keep assemblies in ESD protective covers. These protective covers must be undamaged.
ESD protective covers, which are extremely wrinkled or even have holes, no longer protect against
electrostatic discharge.
ESD protective covers must not be low-resistance and metallically conductive if a lithium battery
is installed on the assembly.
ATTENTION!
Separate Collection
Product Category: According to the device types listed in the WEEE Directive, Appendix 1,
this product is classified as an IT and communication device.
This product meets the labeling requirements of the WEEE Directive. The product symbol on
the left indicates that this electronic product must not be disposed of in domestic waste.
The withdrawal may be refused in the case of waste equipment which presents a risk to
human health or safety due to contamination during use.
- cmd/www-upload.htm
#Program code and CLI commands are displayed in a grey box with monospace
font.
User passwords:
The following characters are currently allowed for user passwords and shared secret:
validchars[] = abcdefghijklmnopqrstuvwxyz
ABCDEFGHIJKLMNOPQRSTUVWXYZ
0123456789
=-_.:#*?@/+![]
Mounting TORX T20 TORX T20 TORX T20 INBUS 2,5mm INBUS 2,5mm x
Rackears
Mounting Phillips
DIN rail x x x x x PH1 x 80
LANTIME SERIES
LANTIME M100 LANTIME M200 LANTIME M300 LANTIME M400 LANTIME M600 LANTIME M900
Replacing TORX T8
Modules x x x x x
4 Introduction
A LANTIME is a multi-purpose time and frequency synchronization solution with a flexible approach to support
a large number of synchronization requirements in different applications and network environments. The system
combines a powerful CPU with dedicated hardware like reference clocks or I/O modules, creating a powerful
network appliance that supports almost all commonly used time and frequency synchronization protocols and
signals.
The basic installation of a LANTIME Server is a very easy and straightforward process. After installing
the hardware, the network address, the netmask and the default gateway have to be configured to be able to
access the web GUI. If everything is set up correctl,y as soon as the device is reachable over the network, it
can start serving time via NTP and/or PTP.
In addition to the time sync protocols NTP and PTP, the LANTIME system supports a number of additional net-
work protocols primarily used for remote management of the system: HTTP(S), FTP, SSH and Telnet. Remote
configuration, status checks and other maintenance procedures like firmware updates or configuration backups
can be controlled from any WEB browser. For security reasons, every protocol can be enabled or disabled for
each configured IP address, allowing to reduce potential attack vectors and effectively control access to the
device.
Status changes, alarms or other important events are logged in local log files and additionally can be forwarded
to external SYSLOG servers. A number of notification protocols are supported to integrate the LANTIME system
into already existing IT monitoring solutions. For example, SNMP traps or automatically generated e-mails
are two potential options for notifying IT administrators about important events.
Installing multiple LANTIME devices in one network is a way to create redundancy for important network
time synchronization services.
Each LANTIME server has at least one physical ethernet interface which is provided by the CPU module
(lan0). Additional network interfaces can be provided by network expansion cards (LNE or TSU cards) or on
backplanes (depending on model). These additional physical interfaces can be used to provide synchronization
services to multiple physical network segments, to separate management and synchronization networks or to
combine multiple ethernet interfaces to form redundant connections ("bonding"). The 6th generation of LANTIME
OS6 Firmware firmware (LTOS7) can manage up to 99 physical network interfaces as a theoretical maxmium.
Configuration of IPv4 and IPv6 addresses is done based on logical interface configurations. Each logical
interface is assigned to one physical ethernet port and can be configured to use one IEEE 802.1q VLAN ID. The
current firmware version supports up to 99 logical interfaces per server and all of those could be theoretically
assigned to a single physical port.
The network ports of TSU modules (for PTP and Hardware-NTP) are not providing this logical interface
functionality and are limited, at least in the current firmware version, to one IPv4/IPv6 address and one VLAN
ID per physical interface. Redundancy and connectivity to multiple network segments and VLANs can be
achieved by adding multiple TSU cards in a system.
For each logical interface the available network services for synchronization (NTP, TIME, ..) and manage-
ment (HTTP, HTTPS, SSH, SNMP, TELNET, ...) can be enabled/disabled individually. This allows to only
provide synchronization on one IP address and remote access the unit for management tasks over a different IP
address.
NTP operates in a way that is basically different from that of most other timing protocols. NTP does not
synchronize all connected clocks; instead it forms a hierarchy of timeservers and clients. Each level in this
hierarchy is called a stratum, and Stratum 1 is the highest level. Timeservers at this level synchronize them-
selves by means of a reference time source such as a radio controlled clock, satelliet receiver or modem time
distribution. Stratum 1 Servers distribute their time to several clients in the network which are called Stratum 2.
Highly precise synchronization is feasible because of the several time references. Every computer synchro-
nizes itself with up to three valued time sources. NTP enables the comparison of the hardware times and the
adjustment of the internal clock. A time precision of 128 ms, and often better than 1 ms, is possible.
The following WEB site is recommended to get the latest version of NTP:
http://www.ntp.org
You can find more information on our web page at: https://www.meinbergglobal.com/english/sw/ntp.htm
In PTP networks there is only one recognized active source of time, referred to as the Grandmaster Clock.
If two or more Grandmaster Clocks exist in a single network, an algorithm defined in the PTP standard is
used to determine which one is the „best“ source of time. This „Best Master Clock“ algorithm must be imple-
mented on every PTP/IEEE1588 compliant system to insure that all clients („Slave Clocks“) will select the same
Grandmaster. The remaining deselected Grandmaster Clocks will „step back“ and enter a passive mode, mean-
ing that they do not send synchronization packets as long as that is being done by the designated Grandmaster.
The existing network infrastructure components play a big role in a PTP network and directly influence the
level of accuracy that can be achieved by the clients. Asymmetric network connections degrade the accuracy,
therefore classic layer 2 and 3 Ethernet switches with their “store and forward” technology are not suitable for
PTP networks and should be avoided. With activating the HQ-Filter (see chapter HQ-Filter) the Jitter can be
eliminated. Simple Ethernet hubs with fixed pass-through times are not a problem. In large networks, special
switches with built-in PTP functionality help to maintain high accuracy even over several subnets and longer
distances. These components act as "Boundary Clocks" (BC) or "Transparent Clocks" (TC). They compensate their
internal packet processing times by using timestamping units on each port. When acting as a Boundary Clock,
they synchronize to the Grandmaster clock, and in turn act as a Master to the other subnets they are connected
to. When acting as a Transparent Clock, then the "residence time" of the Masters’ Sync-Packet is measured and
added to the packet as a correction value. Internally the PTP timescale TAI (see chapter Timescale in Global
Parameters).
10MHz PPS
The Time Stamp Unit, integrated in an FPGA (Field Programmable Gate Array, a programmable logic device),
checks the data traffic on the MII-interface between the PHY receiver (physical connection to the network) and
the Ethernet controller (MAC) on the PTP module. If a valid PTP packet is detected, the time stamp unit takes
a time stamp of that packet which is read by a single board computer (SBC) running the PTP software. The
configuration and status traffic between the PTP board and main SBC is done over a USB connection.
10M/activity
RJ45 with USB 1.1
10/100MBit 100M/activity MII interface
MAC
magnetics PHYceiver USB USB hub to computer
LAN controller
and LEDs Rx/Tx
module
USB
After power up, the module accepts the absolute time information (PTP seconds) of a reference time source (e.g.
GPS reference clock) only once, and the PTP nanoseconds are set to zero. If the oscillator frequency of the
reference time source has reached its nominal value, the nanoseconds are reset again. This procedure leads to
a maximum deviation of 20 nsec of the pulse per second (1PPS) of the PTP Master compared to the 1PPS of
the GPS reference clock. The reference clock of the PTP board’s time stamp unit (50 MHz) is derived from the
GPS disciplined oscillator of the reference time source using a PLL (Phase Locked Loop) of the FPGA. The
achieves a direct coupling of the time stamp unit to the GPS system.
10M/activity
RJ45 with USB 1.1
10/100MBit 100M/activity MII interface
MAC
magnetics PHYceiver USB USB hub to computer
LAN controller
and LEDs Rx/Tx
module
USB
status
status LEDs
clock
control FPGA
modulated filter and voltage
oscillator DAC configuration
time code driver circuit
memory
After decoding valid time information from a PTP Master, the system sets its own PTP seconds and nanoseconds
accordingly. The PTP offset calculated by the PTP driver software of the single board computer is used to
adjust the master oscillator of the TSU-USB. This allows the PTP Slave to generate very high accuracy output
signals (10 MHz/1PPS/IRIG).
It is therefore very important to start with making decisions how the to-be-installed PTP synchronization
solution should operate, e.g. should the communication between the devices be based on multicast or unicast
network traffic or how often should the masters send SYNC messages to the slaves.
This chapter lists the most important options and their implications on a synchronization environment in general.
A detailed explanation of the configuration settings within the LANTIME configuration interfaces can be found
later within this documentation.
The above options need to be defined for the whole setup, if devices do not stick to the same settings, they
will not be able to establish a working synchronization link.
Layer 3 is the recommended mode, because it works in most environments. For Layer 2 mode the network
needs to be able to provide Ethernet connections between master and slave devices, which is often not the case
when your network is divided into different network segments and you have no layer 2 routing capabilities in
your network infrastructure.
The only benefit of using Layer 2 mode would be a reduced traffic load, because the transmitted network
frames do not need to include the IP and UDP header, saving 28 bytes per PTP packet/frame. Due to the fact
that PTP is a low traffic protocol (when compared to other protocols), the reduced bandwidth consumption only
plays a role when low-bandwidth network links (e.g. 2Mbit/s) have to be used or in pay-per-traffic scenarios,
for example over leased-line connections.
In version 2 of the protocol (IEEE 1588-2008) the unicast mode was introduced in addition to the multicast
mode. In unicast mode, the master has to send one packet each to every slave device, requiring much more CPU
performance on the master and producing orders of magnitudes more traffic.
On the other hand, some switches might block multicast traffic, so that in certain environments, Unicast mode
has to be used.
IEEE 1588-2008 offers two different mechanisms for performing the delay measurements. A slave can either
measure the delay all the way to the master, this is called End-To-End (or E2E in short) or to its direct network
neighbors (which would in almost all cases be a switch – or two in a redundant setup), using the Peer-To-Peer
delay measurement mechanism (P2P). The delay measurements of all links between the master and the slave
are then added and accumulated while a SYNC packet is traversing the network.
The advantage of this method is that it can dramatically reduce the degradation of accuracy after topology
changes. For example: in a redundant network ring topology the network delay will be affected when the ring
breaks open and network traffic needs to be redirected and flows into the other direction. A PTP slave in a
sync infrastructure using E2E would in this case apply the wrong delay correction calculations until it performs
the next delay measurement (and finds out that the network path delay has changed). The same scenario in a
P2P setup would see much less time error, because the delay of all changed network links were already available.
The drawback: the P2P approach requires that all involved PTP devices and all switches support this mecha-
nism. A switch/hub without P2P support would in the best case simply pass the so-called PDELAY messages
through and as a result degrade the accuracy of the delay measurements. In the worst case it would block/drop
the PDELAY messages completely, which effectively would result in no delay measurements at all.
So, E2E is the only available choice if you are running PTP traffic through non-PTP-aware switches. It is a
reasonable choice if you are not using redundant network topologies or can accept that the delay measurements
are wrong for a certain amount of time.
A possible example is a situation where the PTP infrastructure is integrated within an environment with high
network load. In this case, the PTP packets can be affected by the effect of packet delay variation (PDV). An
increase of the PTP message rate(s) can avoid synchronization problems due to packet queuing within non-PTP
compliant switches which might cause false measurements. At higher rates, these false measurements can be
detected and corrected faster as compared to lower rates at the cost of increased traffic.
The message rates for the following message types can be changed:
1) ANNOUNCE messages
2) SYNC/FOLLOWUP messages
3) (P)DELAY_REQUEST messages
The procedure used to decide which of the available devices (that could become masters) is selected is called the
“best master clock algorithm” (BMCA). The values that are used in this BMCA are read from the ANNOUNCE
messages that potential masters send out periodically.
The rate at which these messages are sent out are directly affecting the time that is required by a slave
device to select a master and to switch to a different master in case the selected one fails.
Multiple devices can simultaneously transmit ANNOUNCE messages during periods in which no master has
been selected (yet). This happens for example when a PTP network is powered up, i.e. all devices are starting
to work at the same time. In this case all devices that consider themselves (based on their configuration and
status) being capable of providing synchronization to all the other PTP devices will start to send out AN-
NOUNCE messages. They will receive the other candidates’ ANNOUNCE messages as well and perform the
BMCA. If they determine that another candidate is more suitable to become the master clock, they stop sending
ANNOUNCE messages and either become slave devices or go into "PASSIVE" mode, waiting for the selected
master to stop sending ANNOUNCE messages. This is determined to be the case when no ANNOUNCE
message is received within 3 ANNOUNCE message intervals.
As an example, if the ANNOUNCE interval has been configured to be 2 seconds (one message every 2 sec-
onds, the default value), the master is considered to have failed when no message has been received for 6 seconds.
In order to choose a master (a backup master clock or the primary one during initialization) the devices require
to receive at least two consecutive ANNOUNCE messages. Continuing our example, it would take the 6 seconds
to determine that the current master has failed and another 4 seconds to select the new one. That means an
ANNOUNCE interval of 2 seconds translates into at least 10 seconds of “switching time” and 4 seconds of
“initial master clock selection time”. So, choosing a shorter ANNOUNCE message interval will allow a faster
switching to a backup master clock, but it can lead to false positives when the chosen interval is too short for
the network environment.
For Meinberg slave devices, the default one-SYNC-every-second setting is more than enough to achieve the
highest possible synchronization accuracy.
Meinberg slave devices will limit the effect of an outdated path delay measurement by using filters and opti-
mized PLL algorithms. This avoids that a clock “jumps around” and basically monitors the time difference to the
master clock carefully for a certain amount of time before adjusting its own clock. With a low cost time base this
is not possible, because the instability (i.e. temperature-dependent drift and overall short term stability/aging
effects) and therefore these slaves would require to perform as many delay measurements and receive as many
SYNC/FOLLOWUP messages as possible.
For P2P mode the delay request interval is not as critical, simply because the delay variation on a single-hop link
(i.e. from your slave device to its switch) is very stable and does not change dramatically in typical environments.
Current firmware versions of Meinberg Grandmaster clocks (V5.32a and older) do not offer changing the Delay
message rate in Multicast mode, it is fixed to one delay request every 8 seconds. Since this is actually a value
that is transmitted in the DELAY_RESPONSE message as a maximum value, the slave devices are not allowed
to perform delay measurements more often.
Functionality
After activating the HQ-Filter some PTP measurements will be done first without controlling the timing of
the PTP slave. This phase will be indicated by an extra hint "init" in the current status of the PTP slave.
During this phase the maximum jitter of the PTP offset, the path delay and the current drift of the internal
oscillator will be calculated by statistical methods. The only filter parameter which can be set by the user is
the estimated accuracy which will set the maximum expected range of the incoming time jitter. All input values
that are out of this range will be dropped. The maximum jitter of the input will be updated continuously during
normal operation. By default estimated accuracy will be set to 1s to determine the maximum jitter automatically.
PDSC
PDSC means "Path Delay Step Compensation". The PDSC feature tries to eliminate jumps of the PTP path
delay, so that there will be no effect on the timing accuracy. Such a jump of the PTP path delay (which
should be usually constant) will be caused by changing the topology of the PTP network which could happen
in SDH networks for example. The change of the PTP path delay is only detected, if the step is larger than
the measured time jitter. This feature is an extension of the HQ-Filter and therefore the HQ-Filter has to be
activated.
5 Unboxing
After unpacking the LANTIME time server, please check the contents for completeness - regarding to the in-
cluded packing list.
11
13
8 10
A
9
12
M200 - optional 2
3
7 6
1
4
M300/M600
5
!
A LANTIME Package Contents
———————————————————————————————————-
1. Assembly brackets for 19 Inch rack mounting (optional for LANTIME M200)
2. Protection spacer (M200 / M300 / M600)
3. Screws for brackets (M200 / M300 / M600)
4. 3-pin DFK connector or 5-pin DFK connector
(additional connector in case of AC/DC or DC power supply)
5. USB stick with software and documentation
6. Power cord (only in case of AC power supply)
7. Option: power cable with 5-pin connector
2x
2x 8
2x
4x 4x
Note: Please read the safety instructions and the manual carefully to familiarize yourself
with the safe and proper handling of electronic devices. The product documentation
can be found on the USB Flash Memory.
6 LANTIME Installation
• Connecting the LANTIME
• Entering the IP Address
• Connecting the Antenna
• Configuration via the Web Interface
PPS Out
LAN 1 LAN 2 O
LAN 0 LAN 3 Error COM 1 I
Reference
100M 10M 100M 10M Signal In CO NO NC COM 0 100 - 240V / 50-60 Hz
10MHz Out
Figure: LANTIME Connection diagram * TCG = Time Code Generator, LW = Long Wave Receiver, GNSS
= Global Navigation Satellite System
Make sure that the power switch (if available) is in the "0" position (off), and plug the power cord into the
power socket of your LANTIME. Then connect the device to your computer network using a suitable network
cable. After switching on power, the following message is displayed:
MEINBERG LANTIME
is booting ...
please wait ...
......
After running a number of power-on self tests, the time server is in operation mode and the main screen appears.
OK
OK
Navigate to "Interfaces" using the arrow keys and press OK to change to the configuration menu of the connected
network interface. You can select the network port with the "Down" and "Up" arrow keys (↓ | ↑).
The cursor can be moved using the ← | → arrow keys, the value underneath the cursor can be modified
with ↓ | ↑. Confirm your changed values with OK and F2.
ANTENNA
SHORT-CIRCUIT
DISCONNECT POWER
! ! !
In such a case, switch off the device and check the antenna cable. Instructions for installing the antenna are
included in the corresponding chapter „Mounting the Antenna“ of the manual which is available in the „Manual“
folder of the USB flash drive.
Connect to the web interface by entering the IP address of the LANTIME into the address field
of your web browser:
2. LOGIN
user: root
password: timeserver
The general knowledge about public key infrastructures, RSA, symmetric keys and the protocols SSL, SSH,
NTP and SNMP is assumed.
Table 7.1 shows the security goals of the protocols in short. The accountability is given through a detailed
syslog of the actions performed by every user or process. It is not guaranteed that entries are not manipulated
by admins and for that, the system can not prove the non-repudiation. The most, possible availability of the
services is realized through current updates and IP banning. For more protection, implement web application
firewalls and traditional firewalls in the network, that are able to identify and prevent DOS/DDOS attacks.
This list has no claim of completeness! It is only the minimum amount you should always check. We can
not give you a complete list, because we do not know which configuration will be changed due to security
enhancements in the future.
Most GNSS signals can be received world-wide, while long wave signals can only be received up to a certain
distance around the transmitting station. Also, GNSS receivers can usually track the signals from several
satellites at the same time, so the signal propagation delay can be determined and compensated automatically,
while long wave receivers usually receive only the signal from a single station. Last but not least the available
bandwidths and signal propagation characteristics are another reason why GNSS reception usually yields a
higher degree of time accuracy than long wave reception.
This system has been installed by the United States Department of Defense (Defense Department) and provides
two levels of accuracy: the Standard Positioning Services (SPS) and the Precise Positioning Services (PPS).
The structure of the sent data of the PLC has been released and the reception has been made available
for general use, while the time and navigation data of the even more accurate PPS are transmitted encrypted
and therefore only accessible to certain users (mostly military). The principle of location and time determination
with the aid of a GPS receiver is based on the most possible accurate measurement of the signal propagation
time from the individual satellites to the receiver.
The GPS satellites orbit the earth on six orbital tracks in 20,000 km of altitude once in about 12 hours.
This ensures that at any time at least four satellites are in sight at any point on the earth. Four satellites must
be received at the same time so that the receiver can determine its spatial position (x, y, z) and the deviation
of its clock from the GPS system time.
Control stations on earth measure the orbits of the satellites and record the deviations of the atomic clocks
carried on board from the GPS system time. The determined data are sent to the satellites and sent to earth as
navigation data by the satellites. The highly precise track data of the satellites, called ephemerides, are needed
so that the receiver can calculate the exact position of the satellites in space at any time. A set of track data
with reduced accuracy is called almanac. With the aid of the almanacs, the receiver calculates at approximately
known position and time, which of the satellites are visible from its location. Each of the satellites transmits its
own ephemerides as well as the almanacs of all existing satellites. The GPS clock operates with the "Standard
Positioning Service". The data stream of the satellites are decoded and evaluated by the microprocessor of
the system, like that the GPS system time is reproduced with a deviation of less than 100 nsec. Different
running times of the signals from the satellites to the receiver are automatically compensated by determining
the receiver position. By tracking the main oscillator, a frequency accuracy of 1e-12 is achieved, depending on
the oscillator type. At the same time, the age-related drift is compensated. The current correction value of the
oscillator is stored in a non-volatile memory of the system.
The Global Positioning System (GPS) is a GNSS operated by the US department of defense. Its purpose
is to provide position, velocity and time for civilian and defense users on a global basis. The system currently
consists of 32 medium earth orbit satellites and several ground control stations.
GLONASS is a GNSS operated by Russian Federation department of defense. Its purpose is to provide
position, velocity and time for civilian and defense users on a global basis. The system consists of 24 medium
earth orbit satellites and ground control stations. The GLONASS satellites circle the earth once on three
orbital lanes in height of 19100km in about 12 hours.
Galileo is a GNSS operated by the European Union. Its purpose is to provide position, velocity and time
for civilian users on a global basis. The system is currently not fully operational. It is eventually expected to
consist of 30 medium earth orbit satellites. At the time of writing (early 2016), the Galileo system was still
under development with only a few fully operational SVs. Therefore, the precise performance and reliability of
u-blox receivers when receiving Galileo signals is effectively impossible to guarantee.
BeiDou is a GNSS operated by China. Its purpose is to initially provide position, velocity and time for
users in Asia. In a later stage when the system is fully deployed it will have worldwide coverage. The full
system will consist of five geostationary, five inclined geosynchronous and 27 medium earth orbit satellites, as
well as control, upload and monitoring stations.
Characteristics
The GNS module is a combined GPS / Galileo / GLONASS / BeiDou receiver and operates with the "Standard
Positioning Service" (GPS) or "Standard Precision" (Galileo, GLONASS, BeiDou). The data stream from the
satellites is decoded by the microprocessor of the system. By analyzing the data, the GNSS system time can
be reproduced very precisely. Different running times of the signals from the satellites to the receiver are auto-
matically compensated by determining the receiver position. By tracking the main oscillator (Oven Controlled
Xtal Oscillator, OCXO) a high frequency accuracy is achieved. At the same time, the aging-induced drift of the
quartz is compensated. The current correction value for the oscillator is stored in a non-volatile memory of the
system. This receiver is suitable not only for stationary operation but also for mobile use.
The Meinberg GLN receiver is the predecessor of the GNS clock and receives GPS, Glonass and BeiDou.
The carrier frequency of 77.5 kHz is amplitude modulated with time marks each second. The BCD-coding
of the time telegram is done by shifting the amplitude to 25% for a period of 0.1s for a logical ’0’ and for 0.2s
for a logical ’1’. The receiver reconstructs the time frame by demodulating this DCF-signal. Because the AM
signal is normally superimposed by interfering signals, filtering of the received signal is required. The resulting
bandwidth-limiting causes a skew of the demodulated time marks which is in the range of 10 ms. Variations of
the trigger level of the demodulator make the accuracy of the time marks worse by additional +/-3 ms. Because
this precision is not sufficient for lots of applications, the PTB (Physical and Technical Institute of Germany)
began to spread time information by using the correlation technique.
The DCF-transmitter is modulated with a pseudo-random phase noise in addition to the AM. The pseudo-
random sequence (PZF) contains 512 bits which are transmitted by phase modulation between the AM-time
marks. The bit sequence is built of the same number of logical ’0’ and logical ’1’ to get a symmetrical PZF to
keep the average phase of the carrier constant. The length of one bit is 120 DCF-clocks, corresponding to 1.55
ms. The carrier of 77.5 kHz is modulated with a phase deviation of +/-10 per bit. The bit sequence is transmitted
each second, it starts 200ms after the beginning of an AM second mark and ends shortly before the next one.
Compared to an AM DCF77-receiver, the input filter of a correlation receiver can be dimensioned wideband
width. The incoming signal is correlated with a reconstructed receiver-PZF. This correlation analysis allows the
generation of time marks which have a skew of only some microseconds. In addition, the interference immunity
is increased by this method because interference signals are suppressed by averaging the incoming signal. By
sending the original or the complemented bit sequence, the BCD-coded time information is transmitted.
The absolute accuracy of the generated time frame depends on the quality of the receiver and the distance
to the transmitter, but also on the conditions of transmission. Therefore, the absolute precision of the time frame
is better in summer and at day than in winter and at night. The reason for this phenomenon is a difference in
the portion of the sky wave which superimposes the ground wave. To check the accuracy of the time frame, the
comparison of two systems with compensated propagation delay is meaningful.
M
80
40
20
(reserved)
8
4 0
2
1 A1 Announcement of a change in daylight saving
10
8 50 10
Month of Year 4 Z1, Z2 Time zone identification
2
1 R Z1, Z2 = 0, 1: Daylight saving disabled
4 A1
Day of Week 2 Z1
1 Z2
Z1, Z2 = 1, 0: Daylight saving enabled
40 20
20 A2
S A2 Announcement of a leap second
10 1
8
4 30 2
Day of Month
S Start of time code information
2
4
1
8
P2
10
Minute
20
20
10
40
8
1 P1
Hour
The PZF radio clock is a precision receiver system for the time signal transmitter DCF77. It is available as a
module for use in systems such as Meinberg IMS, LANTIME M300 models and as a computer plug-in card. The
microprocessor of the system performs the correlation of a reproduced pseudo-random bit sequence with the PZF
of the transmitter side and simultaneously decodes the AM time and date information of the DCF telegram. By
evaluating the pseudo-random phase noise, a time raster can be generated which is up to a factor of a thousand
more accurate than the ones of conventional AM radio clocks. In this way, an exact adjustment of the main
oscillator of the radio-controlled clock is also possible, this allows it to be also used as a normal frequency
generator, in addition to being used as a pure time receiver. If the PZF signal is temporarily unavailable for
some reason, i.e. because a source of interference is in the vicinity, the radio clock will automatically switch
to the AM signal - provided this is still receivable. The correlation receiver has a battery-buffered hardware
clock, which takes over the time and date in the event of failure of the supply voltage.
The first second of the minute begins with a period of 500 ms with the carrier "off", to serve as a minute marker.
The other 59 (or, exceptionally, 60 or 58) seconds of the minute always begin with at least 100 ms "off’ and end
with at least 700 ms of carrier "on". Seconds 01-16 carry information for the current minute about the difference
(DUT1) between astronomical time and atomic time, and the remaining seconds convey the time and date code.
The time and date code information is always given in terms of UK clock time and date, which is UTC in winter
and UTC+1h when Summer Time is in effect, and it relates to the minute following that in which it is transmitted.
The MSF radio clock is a radio clock receiver system for the time signal transmitter MSF. It is available
as a module for use in systems such as Meinberg IMS and LANTIME M300 models. The microprocessor of
the system decodes the time and date information of the incoming AM signal. In this way, an exact adjustment
of the main oscillator of the radio-controlled clock is also possible. The MSF receiver is equipped with a
battery-buffered hardware clock, which takes over the time and date in the event of failure of the supply voltage.
Code Format
carrier on
Second 00 possible 100 bits/s information
carrier off
25 ms 330 ms 500 ms
DUT Code
The DUT1 is signaled to the nearest 100ms in the range of +/-800ms. A positive figure means that GMT is at
a higher count than UTC. Bits 01B to 16B are used to signal the DUT code in the following way.
Other Codes
Minute Identifier
Bits 53A to 58A are all set permanently at ’1’ and are always preceded by bit 52A at ’0’ and followed by bit
59A at ’0’. This sequence ’01111110’ never appears elsewhere in bit xxA, so it uniquely identifies the following
second 00 minute marker. In minutes lengthened or shortened by a positive or negative leap second all these
numbers are correspondingly increased or decreased by one (i.e. during these 61- or 59-second minutes the
position of the time and date code is shifted by one second relative to the start of minute).
Parity Bits
The parity bits are providing and odd number of 1’s.
Bit 54B taken with bits 17A to 24A
Bit 55B taken with bits 25A to 35A
Bit 56B taken with bits 36A to 38A
Bit 57B taken with bits 39A to 51A
Summer Time
When UK civil time is subject to an one-hour positive offset during part of the year, this period is indicated by
setting bit 58B to ’1’. Bit 53B is set to ’1’ during the 61 consecutive minutes immediately before a change, the
last being minute 59, when bit 58B changes.
Unused Bits
The unused bits are currently set to ’0’, but may be used in the future.
WWVB continuously broadcasts a time and frequency signal at 60 kHz. The carrier frequency provides a
stable frequency reference traceable to the national standard. There are no voice announcements on the sta-
tion, but a time code is synchronized with the 60 kHz carrier and broadcast continuously at the rate of 1 bit
per second using pulse width modulation. The carrier power level is modulated to encode the time data. The
carrier power is reduced by 17 dB at the start of each second, so that the leading edge of every negative going
pulse is on time. Full power is restored 0.2 s later for a binary #0#, 0.5 s later for a binary #1#, or 0.8 s later
to convey a position marker. The binary coded decimal (BCD) format is used, which combines binary digits to
represent decimal numbers. The time code contains the year, day of year, hour, minute, second, and flags that
indicate the status of Daylight Savings Time, leap year, and leap seconds. WWVB identifies itself by advancing
its carrier phase 45 degrees at 10 minutes after the hour and returning to normal phase at 15 minutes after the
hour. If you plot WWVB phase, this results in a phase step of approximately 2.08 microseconds.
The receivers automatic gain control allows the reception of signals within a range from abt. 600mVpp up
to 8Vpp. The potential free input can be jumper selectable terminated in either 50 Ohm, 600 Ohm or 5 kOhm.
Modulated codes are applied to the board via an on board SMB connector.
Except these "IRIG Time Codes", other formats like NASA36, XR3 or 2137 are still in use. The TCR receiver
generates the IRIG-B, AFNOR NFS 87-500 code as well as IEEE1344 code which is an IRIG code, extended
by information for time zone, leap second and date.
GNSS receivers need to track at least four satellites to determine their own position in space (x, y, z) as
well as their time offset from the GNSS system time (t). Only if the receiver can determine its own position
accurately the propagation delay of the satellite signals can also be compensated accurately, which is require-
ment to yield an accurate time. If the receiver position can only be determined less accurately then the accuracy
of the derived time is also degraded.
GNSS satellite signals can only be received directly if no building is in the line-of-sight from the antenna
to the satellite. The signals can eventually be reflected at buildings, etc., and the reflected signals can then be
received. However, in this case the true signal propagation path is longer than expected, which causes a small
error in the computed position, which in turn yields less accurate time.
Since most of the satellites are not stationary, the antenna has to be installed in a location with as much
clear view of the sky as possible (e.g. on a rooftop) to allow for continuous, reliable reception and operation.
Best reception is achieved when the antenna has a free view of 8◦ angular elevation above the horizon. If
this is not possible then the antenna should be installed with the best free view to the sky in direction of the
equator. Since the satellite orbits are located between latitudes 55◦ North and 55◦ South, this allows for the
best possible reception.
Meinberg provides their own GPS receivers which operate with an antenna/converter unit and thus allow
for very long antenna cables, but some devices also include GNSS receivers which support other satellite sys-
tems like GLONASS, or Galileo in addition to GPS. These receivers usually require a different type of antenna
equipment which is described in chapter (4.1.2).
Surge protectors are optionally available and should be used in the antenna line to protect the receiver from
high voltages spikes e.g. due to lightning strikes close to the antenna. The antenna/converter unit is remotely
powered by the connected GPS receiver via the antenna cable, so no external power supply is required near
the location of the antenna if a coaxial cable is used.
If more than a single GPS receiver are to be operated then a GPS antenna splitter can be used to distribute
the GPS signal from a single antenna. The GPS antenna splitter provides 4 outputs and can be cascaded to
supply even more than 4 receivers with the GPS signal.
Alternatively there is also a GPS Optical Antenna Link (GOAL) available which uses a fiber optic connection
between the antenna and the receiver which allows for a length up to 2000 meters (6500 ft), and provides a
high level of insulation and surge protection due to the optical transmission. Since the fiber optic connection is
unable to provide the antenna with DC current, an extra power supply is required in this case at the location
of the antenna.
Due to the specific requirements for remote powering and frequency conversion the Meinberg GPS equipment
is not necessarily compatible with GPS equipment from 3rd party manufacturers.
GPS Antenna
N-Norm female
N-Norm male
Cable Slot
N-Norm male
N-Norm female
as short as possible
Figure: GPS Antenna mounted on a pole with a free view of the sky. The optional surge protector keeps high
voltage strikes through the antenna cable away from the receiver.
Mounting material (plastic pole and holders, clamps for wall or pole mounting) is shipped with all Mein-
berg GPS antennae for easy installation. A standard RG58 antenna cable of 20 meters length is included by
default. If a different cable length is required then this can be ordered accordingly.
Surge protectors should be installed indoors, directly where the antenna cable comes in. The optionally
delivered protection kit is not for outdoor usage. The ground lead should be kept as short as possible and has
to be connected to building’s ground rod.
Up to four GPS receivers can be fed by a single antenna/down-converter unit by using an antenna splitter
which can optionally be cascaded. The total length of an antenna cable from the antenna to each receiver must
not exceed the specified maximum length according to the cable type. The position of the splitter in the antenna
line does not matter.
Note:
If the antenna cable is assembled locally instead of using a cable shipped with the GPS receiver it has to be
made sure that the connectors have been soldered and assembled properly, and that there is no short-circuit
in the cable or in one of the connectors. Otherwise GPS reception may be degraded, or the GPS receiver can
even be damaged.
There are two different antenna versions available, one of which is more suited for stationary installation,
while the other one should be preferred for mobile applications.
The antenna cable length can be up to 70 meters if a H155 low-loss coaxial cable is used.
Type-N female
Type-N male
as short as possible
MEINBERG GNSS
Connection to earth rail Type SMA male female
(Protective Earth)
cable diameter ca. 1,5 mm Ø
WARNING!
Working on the antenna system during thunderstorms
WARNING!
Antenna mounting without effective anti-fall protection
WARNING!
Working on the antenna system during thunderstorms
If the receiver has some valid almanac data in its battery buffered memory and the receiver’s position has
not changed significantly since its last operation the receiver can determine which satellites are in view. Only
a single satellite needs to be received to synchronize and generate output pulses, so synchronization can be
achieved at least one minute (OCXO-LQ) until 10 minutes (OCXO-MQ / HQ) after power-up. After 20 minutes
of operation the OCXO is fully adjusted and the generated frequencies are within the specified tolerances.
If the receiver position has changed by some hundred kilometers since last operation, the expected satel-
lites may not be in view after power-up. In this case the receiver switches to Warm Boot mode where it starts
scanning for all possible satellites one after the other. Once the receiver can track at least 4 satellites at the
same time it updates its own position and switches to Normal Operation.
If no valid data can be found in the battery buffered memory, e.g. because the battery has been discon-
nected or replaced, the receiver has to scan for satellites and collect the current almanac and ephemeris data
first. This mode is called Cold Boot, and it takes at least 12 minutes until all required data have been collected.
The reason is that the satellites send all data repeatedly once every 12 minutes. After data collection is com-
plete the receiver switches to Warm Boot mode to scan for more satellites, and finally enters Normal Operation.
In the default configuration neither pulse and synthesizer outputs, nor the serial ports are enabled after power-
up until synchronization has been achieved. However, it is possible to configure some or all of those outputs to
be enabled immediately after power-up.
If the system starts up in a new environment (e. g. receiver position has changed or new power supply
has been installed) it can take some minutes until the oscillator’s output frequency has been adjusted properly.
In this case the accuracy of the output frequency and pulses is also reduced until the receiver’s control loops
have settled again.
On the frontpanel ("Reference Time → Info GPS → GPS Satellites") as well as via the Web GUI ("Clock
→ Receiver Information") you can check the number of satellites that are in view (i.e. above the horizon) and
considered good (i.e. are healthy and can be tracked).
The variant AW02-MSF is available for the longwave transmitter MSF which is located in Anthorn / U.K., and
transmits the time and frequency maintained by the U.K. National Physical Laboratory (NPL). The signal can
be received throughout the U.K., and in wide parts of Northern and Western Europe.
Another variant is the AW02-WWVB which has been adapted for the WWVB radio station which is located in
the United States near Fort Collins, Colorado, and is maintained by U.S. National Institute of Standards and
Technology (NIST).
Even though these antenna variants are slightly different according to the characteristics of the associated
transmitter, the basic requirements for installation are identical.
The longwave antennae can be operated with a cable length up to 300 meters (1000 ft) if standard RG58
coaxial cable is used. They are remotely powered by the receiver via the antenna cable, so no external power
supply is required near the location of the antenna if a direct coaxial cable is used.
Surge protectors are optionally available and should be used in the antenna line to protect the receiver
from high voltages spikes e.g. due to lightning strikes close to the antenna.
For longer distances from the antenna to the receiver an optional amplifier can be used, which requires an
extra power supply. The BLV device is an amplifier with integrated surge protector.
Alternatively there is a DCF Optical Antenna Link (DOAL) available which uses a fiber optic connection
between the antenna and the receiver which allows for a length up to 2000 meters (6500 ft), providing a high
level of insulation and surge protection due to the optical transmission. Again, the default device has been de-
signed for DCF77, but there are also variants for MSF and WWVB available. Since the fiber optic connection
is unable to provide the antenna with DC current, an extra power supply is required in this case at the location
of the antenna.
Longwave receiver equipment from Meinberg has specifically been designed for Meinberg devices and is not
necessarily compatible with receivers from 3rd party manufacturers.
For this reason we always recommend to mount the antenna outside of buildings. This has the advantage
that the signal interference distance to electronic devices in buildings is usually enhances and the reliability
of the synchronisation is thus significantly increased.
Proper installation of an antenna for DCF77, MSF, or WWVB is illustrated in the figure below:
DCF Antenna
Antenna aligned to the transmitter
N-Norm female
N-Norm male
Cable slot
N-Norm male
N-Norm female
as short as possible
Figure: Longwave antenna mounted on a wall. The optional surge protector keeps high voltage strikes through
the antenna cable away from the receiver.
The antenna has to be aligned horizontally in longitudinal direction to the transmitter, i.e. in direction to
Mainflingen near Frankfurt / Main in case of DCF77, or in direction to the location of the MSF or WWVB
receiver accordingly.
If the antenna is not aligned properly then signal reception is degraded, which can result in a limited time
accuracy. The antenna should be installed with a minimum distance of 30 cm away from all metal objects and
possibly any microcomputers and electrical devices (engines, electricity, etc.). A distance of several meters from
TV and computer monitors should be considered as well.
The best method to align a longwave antenna is to turn the antenna slowly until the monitored signal level
is minimized, and then turn the antenna by 90o to achieve maximum reception. However, a high signal level
alone is not a guarantee for good reception since it can even be caused by electrical noise in the associated
frequency range. For standard longwave receivers it is important that the modulation mark is blinking exactly
once per second, without intermediate flickering.
DCF77/PZF receivers use correlation techniques to decode the phase modulation provided by DCF77, and
with these types of receiver the maximum interference immunity can be found by looking at the autocorrelation
parameter displayed in the display menu "PZF-STATE". The displayed value should be as close as possible to
100 % for best reception.
WARNING!
Antenna mounting without effective anti-fall protection
WARNING!
Working on the antenna system during thunderstorms
To check the field strength and the signal correlation value, select in the Front Panel "Reference Time →
Info PZF → Correlation & Field".
The correlation "State" starts in a "raw" mode, when the receiver tries to find the initial correlation. When
good correlation has been found the receiver checks it 20 times: this state is labeled "check" and the correlation
value is increased from 1 to 20. If the correlation quality stays good the state changes to the "fine" mode. The
signal strength should be 100 or higher.
If no correlation with the incoming signal is possible then the clock changes automatically to DCF77 AM
reception mode and tries to decode the second marks.
For further detailed clock configuration, please refer to the Chapter Clock".
* DCF77 (Germany, Middle Europe), MSF (GB), WWVB (US), JJY (Japan)
** Fiber Optic - GOAL - GPS Optical Antenna Link; DOAL - DCF Optical Antenna Link
This chapter provides you with configuration options and status information of your LANTIME system ac-
cesssed via Web GUI. The main page contatins an overview of the most important configuration and status
parameters for the system.
By using the navigation on top of the page you can reach a number of configuration menus, which are de-
scribed in the following chapters.
9.1.1.1 Introduction
To start a http or a secured https session with the Web Interface running on the CPU of your LANTIME system,
you need to open your internet browser and type in the IP address of the interface you are using for this con-
nection . Both http and https protocols are per default enabled at each assigned network interface. If you wish
to use only one dedicated network interface for management and monitoring and the rest for other services you
can find the corresponding configuration options in the Chapter "LTOS Configuration → Via Web → Network"
in the submenu Network Services.
If the connection with the LANTIME is established correctly you will be prompted to enter login data to
start the web session. Per default the entering user-name/password are: root/timeserver. For security reasons
you are advised to change the default credentials after the first login. The corresponding user administration
settings can be found in the Chapter "LTOS6 Configuration → Via Web → System" in the submenu User Man-
agement.
After entering the correct password, the main menu page of the web interface of a LANTIME system shows up.
The main page contains an overview of the most important configuration and status parameters of the sys-
tem, including:
• general information (model name, serial number, uptime since last reboot)
• assigned network and PTP interfaces (both in IPv4 or IPv6 configuration)
• receiver status information (sync or not, for GNSS receivers some additional satellite data)
• SHS (Secure Hybrid System) status in redundant receiver configuration, which provides a plausibility
mode where the incoming times of both time signals are continuously compared against each other. For
more information about the SHS mode and the corresponding settings you can find in Chapter "LTOS6
Configuration → Web GUI → Security → SHS Configuration".
Scrolling down the main page you will find a section containing last log messages generated during the
LANTIME operation. The messages in this field are limited to the last 50 and are chronologically ordered.
The messages are stored in the file /var/log/lantime_messages, which is created after every start of the system
(and is lost after a power off or reboot).To view all log messages in the log file you would have to use the CLI
(Command Line Interface). For your reference, a list of available CLI commands for LANTIME management and
monitoring is provided in the Chapter "LTOS6 Configuration → Via CLI".
Please note: startup of the system can take a several minutes, depending on the hardware configuration
of your system.
Next to the status LEDs you will see displayed all active alarms currently present on a LANTIME with critical
and error severity levels. With a mouse click over the alarms you will reach a table of notification events with
red marked indicators at the events which triggered the alarms.
For further information how to eliminate a cause of each individual alarm, proceed to the Chapter on Trou-
bleshooting and Alarming.
Next to the alarm area in the main page there is a field with informational data about your login status
and information to which access-level group you belong as a current user. There are three types of users:
Super-User, Admin-User and Info-User. The exact definitions of the three different user types and their access-
level rights you can find in Chapter "LTOS6 → Web GUI → System-> User Management".
At the top right corner of the main page you can see a few icons. The displayed flag indicates the lan-
guage pack which is currently activated for the web interface display. For the moment you can choose between
English and German languages packs.
Next to the language flag, there is an icon showing a doctor’s stethoscope linked with a diagnostic file of
the system, which includes all the necessary data for diagnostic and troubleshooting of the device. By clicking
this icon a current diagnostic file will immediately start to download for you to save it to your local computer for
a further use. The downloading can take up to 60 seconds, depending on the file size, which can be several MB.
In the diagnostic file all the data about the system configuration and log messages are stored. The diagnostic
file can be also an important tool for the Meinberg support team if you need some help with the configuration
or you experience issues which you can not solve on your own. More about the diag file see Chapter "LTOS6
Configuration → via Web GUI → System → Download Diagnostic File".
The web interface is divided into several dialogue menus, where some of the dialogues (e.g. PTP; IO Con-
fig and TimeMon) depend on the hardware components which are integrated in the LANTIME system and only
appear in systems with a corresponding configuration. The rest of the dialogues are common to all LANTIME
and IMS systems.
You can move between the dialogues by clicking each individual name tag at the top of the menu line. When
you click on the Logout tag, your Web session with the LANTIME device will be terminated immediately.
The two dialogues Main and XtraStats deliver you the status information about the LANTIME system af-
ter the last reboot. The rest of the dialogues provide configurations of features for the LANTIME operation and
services. The dialogues with feature configurations are presented in a tree structure, where each submenu can
be extended into a subtree by clicking at the "+" sign at the beginning of the submenu row. When you open the
dialogue, the "+" will turn in "-" and when you click the "-" icon the currently open dialogue will close. You can
have a few dialogues open at the same time in the currently selected menu (see the example on the next page).
Generally, in any configuration menu you are located, when you fill in or edit one or more feature fields
at the end you need to confirm the setting by clicking the “Save Settings” button at the bottom of the page. By
doing so and if the setting has been carried out successfully, you will receive a dialogue in the Main Menu with
a confirmation message written on a green field. At the same time when a new configuration has been applied
a log message will appear in the list of last messages in the Main Menu saying: "Device Configuration Changed".
A Saving startup configuration dialogue. Options for saving, discarding the current configuration and showing
changes between the startup configuration and the current one.
Apart of the configuration message you will receive also an attention notice displayed on a yellow bar, saying:
"Current configuration is not yet marked as a startup configuration". This means that you need to confirm the new
configuration first by clicking on a "Save as startup configuration now" button if you want to keep it as a startup
configuration by the next startup of the system. By clicking this button you will receive another confirmation
message saying: "Activate current configuration really as startup configuration?" which you confirm by click-
ing the "OK" button. The new configuration has now become the startup configuration on your LANTIME system.
On the other hand, if you want to return to the last saved startup configuration then you select "Discard
current configuration" button when the message on a yellow bar appears.
Each entry you fill in in the provided dialogues is checked for plausibility for that particular field. If you
for example used wrong characters (e.g. letters in the IP Address configuration or any special characters which
are not allowed) or you provided an invalid network configuration then you will receive a message displayed on
a red bar saying a type of error and at which feature entry it occurred. The false entry will not be accepted by
the system, neither the rest of any new settings you may have configured by that time, therefore you will have to
redo the configuration steps again. See an example of a warning message if an error by entering a feature occurs.
Figure: A display of a warning message with a type of error and indication to which feature it belongs
Allowed signs and special characters which you can use to fill in dialogue boxes you can find in the chap-
ter "Before you Start → Text and Syntax Conventions".
For configuration of the system features now proceed to the dedicated menu which is described in a corre-
sponding chapter.
Hostname
The hostname of the LANTIME is a unique name of a computer in a network. Each IP address configured on
the LANTIME is assigned to this hostname.
Domain
This field is used to configure the network domain name. A network domain name is a text-based label easier
to memorize than the numerical addresses used in the Internet protocol (e.g. meinberg.de).
Nameserver1
IP Address of the primary DNS Server in the network.
The DNS server is used to resolve IP addresses as well as hostnames in a network.
Nameserver2
Here can a alternate Nameserver be defined
In this menu you can configure default gateways to be used for IPv4 and IPv6. For a default gateway, a
"default" entry is created in the main routing table of a LANTIME. If the LANTIME does not have a direct route
or a routing rule to a destination IP, it will always attempt to reach the destination via the default gateway.
In this submenu you can enable or disable various services for the existing virtual network interfaces. The
+/- buttons can be used to select or deselect entire rows or columns in the matrix.
• A service has been activated for at least one virtual interface and is active.
• Service has not been activated for any virtual interface and is therefore stopped.
TCP Port 10000 Login to a command line of a Lantime via a webbrowser. TCP port 4200
WEBSHELL: Input in the web browser: [IP/HOSTNAME]:4200
The default value AUTO (Autonegotiation) can remain unchanged under normal circumstances. Autonegoti-
ation refers to a method which allows two interconnected Ethernet devices to independently negotiate the
maximum possible transmission speed and the duplex method and to configure them accordingly.
Bonding
Here, 2 or more physical network ports can be grouped into a bond (group). The LANTIME supports the bond-
ing modes "Active - Backup" and "LACP". The mode to be used can be selected in the submenu "Network →
Miscellaneous → Bonding-Mode". For more information about how the two modes work, see the "Miscellaneous"
submenu.
IPv6 Mode
Activation or deactivation of the IPv6 protocol.
MAC Address
Media Access Control, shows the MAC address of the given physical interface.
In this menu the virtual interfaces of the LANTIME are managed. Up to 99 virtual interfaces can be as-
signed to the available physical ports. The name of the virtual interface consists of a consecutive number of a
physical interface and the number of a virtual interface (starting with zero).
The example above shows a configuration in which a total of three virtual interfaces are assigned to the
physical interface lan0, namely lan0:0, lan0:1 and lan0:2.
In the case of an active bond, the physical interface is replaced by the name of the bonding group, for ex-
ample Bond0: 0.
Add interface
With this button a new virtual interface can be created. The new interface is assigned by default to the physical
port lan0 and is added at the end of the row of the existing virtual interfaces. The assignment can be changed
in the "Miscellaneous" tab.
Submenu IPv4:
In this submenu the IPv4 parameters can be configured or the current configuration given by the DHCP server
can be displayed.
Enable DHCP-Client: With this setting a DHCP client can be activated for the automatic assignment of the
network configuration by a DHCP server.
Submenu IPv6:
In this menu the IPv6 parameters can be configured or the configuration given by a DHCP server can be displayed.
Submenu Misc:
Assigned Interface: Determines which physical network is associated with the currently selected
virtual interface.
"Virtual Interface"
Delete Button: Deletes the currently selected virtual interface.
Submenu VLAN:
Enable VLAN Option: Activation of the tagged VLAN function for the selected virtual interface.
VLAN-Tag (0-4094): VLAN tags from 0-4094 can be entered here. The selected tag is inserted into
the data area of an Ethernet packet.
Priority: PCP (Priority Code Point). Sets the priority of an Ethernet frame. Priorities can be
set between a low priority, value 1 and a high priority, value 7.
Submenu Cluster:
The Cluster mode is a method for providing redundant time synchronization by groupping (clustering) multiple
LANTIME NTP servers. Within this group, the participating NTP servers continuously exchange status and
quality information with each other. The status information is compared among each other and by a special
algorithm a decision is made, which of the NTP servers should act as a current MASTER in the network. The
rest of the group acts as SLAVE and stays passive as a backup. If the current master loses its synchronization
source or any other failure occurs, another NTP server from the cluster takes over the master role. The current
master responds to requests from NTP clients via a common cluster IP. Even if the master is replaced by another
NTP server, this IP does not change.
The configuration of a NTP cluster is useful if at the side of NTP clients only one IP address for an ex-
ternal NTP server can be configured and redundancy is still required.
The current master is selected according to the following parameters in this order:
Enable Cluster Option: The cluster function can be activated via this selection box.
Mode: The cluster members can share their status information either via multicast or unicast
messages. For multicast, a cluster multicast address 239.192.0.1 is used by default.
This setting can be changed in the menu "Network → Miscellaneous". In addition,
the network port which is used for the cluster communication can be changed there.
By default, port 7000 is used for the cluster messages.
TCP/IP Address: IP address of the NTP cluster interface. The same cluster IP needs to be configured on all
cluster members. It is recommended to configure a cluster IP in the same subnet as the
corresponding virtual interface.
Priority: The priority set here is taken into account when the MASTER is determined by the cluster
algorithm. The lowest value has the highest priority.
In the Unicast cluster, the IP addresses of the cluster members must be entered in the "Other IPv4 Member"
field.
Cluster Port:
Configuration of a free network port for the cluster communication. Per default this port is set to 7000.
Bonding-Mode:
In the menu “Network → Physical Network Configuration", two or more physical network ports can be grouped
into a bond (group). The Bonding Mode is used to configure either the “ACTIVE BACKUP” or the "LACP" mode
(Link Aggregation Control Protocol), which are supported on the LANTIME.
ACTIVE-BACKUP:
One physical interface in the bonding group acts as an "active slave". All network traffic of a LANTIME Bond
runs through this interface. The other physical interfaces in the bonding group are passive. In case the current
active interface loses the network connection, the passive interface seamlessly takes over. Even the MAC ad-
dress of the network port remains unchanged.
LACP: LACP (802.3ad) allows a combination of multiple physical connections to a logical one. This results
in a load sharing and, in addition, increases the safety in case of a failure compared to "Active Backup". It
is important that other connected network devices also support LACP and the network ports are configured
accordingly.
In the Extended Network Configuration, a bash script can be edited, which is executed automatically each
time the LANTIME is rebooted or a network-related configuration changes.
Depending on the physical interfaces you want to configure for PRP, you have to search for the specific
sections in the file. For this example, we will configure LAN1 ( → [PHYSICAL INTERFACE 1]) and LAN2
( → [PHYSICAL INTERFACE 2]) to a particular PRP group. The configuration below is showing a default
configuration of the physical interfaces of a LANTIME.
[PHYSICAL INTERFACE 1]
MAC-ADDRESS = ab:cd:ef:00:11:22
NET-LINK-MODE = AUTO
BONDING =
INDICATE-LINK = OFF
SUPPORTED-MODES = AUTO 10HD 10FD 100HD 100FD
IPV6-MODE = DEACTIVATED
IMS-SLOT-NUM = 0
POWER-OFF = NO
PRPGROUP = -
[PHYSICAL INTERFACE 2]
MAC-ADDRESS = ab:cd:ef:33:44:55
NET-LINK-MODE = AUTO
BONDING =
INDICATE-LINK = OFF
SUPPORTED-MODES = AUTO 10HD 10FD 100HD 100FD
IPV6-MODE = DEACTIVATED
IMS-SLOT-NUM = 0
POWER-OFF = NO
PRPGROUP = -
The PRPGROUP parameter is responsible for the PRP configuration of the LANTIME. By default, PRP is
deactivated, which is indicated with a "-" as value. In order to activate PRP on LAN1 and LAN2, just change
the value from "-" to a single digit. This value has to be configured on all physical interfaces, which shall run
in the same PRP group. After editing the file, press "Save Settings". You will be forced to confirm a message,
which gives you a hint that you have changed a configuration file manually.
Please reload the configuration by confirming with "OK". It is not allowed to configure a Bonding on an
interface where PRP is already running. On the other hand do not configure PRP on an interface, which is
assigned to a Bond.
Syslog-Adress(s):
You can enter up to 2 external Syslog Servers via the webinterface. As standard, the reachability of the Syslog
Server is checked via Ping/ICMP. If the registered Syslog Server cannot be reached, it will not be entered into
the Syslog configuration file /etc/syslog-ng/syslog-ng.conf. In case IMCP is not allowed in the network, due to
firewall regulations, you can switch off the pingcheck via the manual network configuration. To proceed navigate
as described down below:
"System Page → Services and Functions → Manual Configuration → Network Configuration": Enter the value
"NO" for the Parameter "SYSLOGPINGCHECK" and save the new settings:
Transport-Protocol:
Transport - Protocol Configuration:
UDP - connectionless transmission
TCP - connection oriented
Port:
Configuration of the network port which is to be used. As default, IANA has registered port 514 for syslog
messages.
Username/ Password: Please enter a valid access for the e-mail server.
Additional
E-mail Recipients: Configuration of additional e-mail recipients.
Serial number: You have to enter the correct serial number of the display here.
The serial number is displayed after pressing the red SET button four times.
9.1.3.5 Notifications
User-defined Notifications
A freely definable script which should be executed when certain system events occur, can be created via the
"User-defined notification" menu item. This script can be viewed and edited via the button "Notification Edit".
Upon delivery this script contains a few comments:
In the submenu "Notification Events", you can select the system events on which the script should be exe-
cuted.
Miscellaneous
The network heartbeat describes a function, with which the LANTIME cyclically sends an SNMP trap to
the configured SNMP trap receivers to report itself as "alive" and "active".
EMAIL: Sends an e-mail based on the e-mail configuration (see chapter "E-mail Information")
SNMP: Sends an SNMP Trap to the configured SNMP Trap (see chapter "SNMP Trap Receivers")
ALED: When the event occurs, the alarm LED of the LANTIME will light up
RELAY: When the event occurs, the error relay at the LANTIME is set to ERROR
Automatic Event Repeat: An interval can be configured, with which notifications are sent again.
Max. Number of Repetitions: The number of repetitions can be limited by this parameter.
NTP Not Sync Warning or Critical NTP Service is not sync -> NTP
Messages
CLK[NR] Not Sync Warning or Critical Receiver module is not sync ->
Ref. Clock Messages
SHS Time Limit OK Info event The set SHS time limit value has
not been exceeded
SHS Time Limit Warning Warning or Critical The set threshold for an SHS
warning has been exceeded
SHS Time Limit Error Critical The set threshold for an SHS er-
ror has been exceeded -> SHS
Configuration
XMR Limit Exceeded Warning Set MRS limits have been ex-
ceeded -> Ref. Clock Messages
XMR Reference Changed Info or Warning The active MRS source has
changed
PTP State Changed Info or Warning The current PTP status has
changed
NTP Offsetlimit exceeded Warning or Critical Maximum NTP offset value has
been exceeded -> Sync Monitor-
ing
This page allows to configure access restrictions and snmp. It also provides the functionality to handle SSH
keys and the HTTPS certificate.
If unsure of required values please contact the network security administrator and provide these parameters.
Login/Access
The "Login" menu allows you to set general security settings for the login behavior of the LANTIME.
Shell Timeout:
Defines a timeout in seconds. After expiration of this period without any user interaction, the current session
on the command line will be terminated for the logged-in user.
Front Panel:
Contains general security settings for the front panel of the LANTIME.
To make sure that you are talking to your known timeserver, check the certificate and accept it, if it matches the
one stored on the LANTIME. All further connections are comparing the certificate with this one, which is saved
in your web browser configuration. Afterwards you are prompted to verify the certificate only when it is changed.
Note: Per default there is a self-signed certificate installed on the LANTIME which is not signed by a Cer-
tificate Authority (CA). Therefore some web browsers will state that the connection is not secure. If you want
to install a certificate which was signed by a trusted Certificate Authority the “Upload SSL Certificate” button
can be used. More details on this in the following instructions.
IMPORTANT: The certificate should not be protected with a password, otherwise the web server cannot start
automatically.
In addition to SSL certificates, also multi-level / chained certificates are supported. In this case, a private
key and a certificate chain are divided into two files, which are both in a PEM format. The actual PEM file
contains the private key which is enclosed between BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY
line as shown above. The CA-file on the other hand contains the certificate chain, where each single certificate
is enclosed between BEGIN and END CERTIFICATE line as shown above.
The PEM file that contains the private key should be copied manually to "/etc/https.pem" and the CA to
"/etc/https_cert.pem".
Subsequently, the line ’ssl.ca-file = "/etc/https_cert.pem"’ should be added in a server configuration file "/etc/httpsd.conf".
Running the command "saveconfig" saves the settings persistently, the command "restart https" applies the
settings.
Please Note: The certificates should not be protected with a password, otherwise the web server cannot
start automatically.
9.1.4.4 SNMP
The Simple Network Management Protocol (SNMP) is used in network management systems to monitor status
of devices. SNMP works by querying "Objects". An object is simply something that we can gather information
about a network device. The so called management information base (MIB) is a file which contains all objects
that can be managed through SNMP.
The Meinberg SNMP MIB Files can be downloaded on the "System" page → Services and Functions →
Download SNMP MIB". The files named "MBG-SNMP-ROOT-MIB.mib" and "MBG-LANTIME-NG-MIB.mib"
need to be used to monitor a LANTIME V6 system.
(see also configuration chapter 9.1.8.2 "Web GUI → System → Services and Functions")
By default the SNMP service is not activated on a LANTIME V6 system. The service can be activated on
each interface at the "Network page → Network Services".
(see also configuration chapter 9.1.2.3 "Web GUI → Network → Network Services")
Read Community:
The read community is only used for SNMP versions V1 and V2. It is like a user id or password that al-
lows access to the LANTIME SNMP objects. The SNMP Monitoring system sends the read community string
along with all SNMP requests. If the community string is correct, the LANTIME responds with the requested
information. If the community string is incorrect, the LANTIME simply discards the request and does not respond.
Write Community:
The write community is only used for SNMP versions V1 and V2. It is like a user id or password that allows
access to the LANTIME SNMP objects. The SNMP Monitoring system sends the write community string along
with all SNMP-SET commands. If the community string is correct, the SNMP-SET command is executed. If
the community string is incorrect, the SNMP-SET command is not executed.
V3 Parameter
Security Name:
SNMP V3 User name
Security Level:
Messages can be sent unauthenticated, authenticated, or authenticated and encrypted by setting the Security
Level to use:
Engine ID:
Within an administrative domain, a SNMP V3 Engine ID is an unique identifier of an SNMP engine. A string
with a maximum of 27 characters can be entered here. The string is used to generate the hex engineID by using
the text format scheme described in RFC3411. If for example the string "hello" is configured as engineID, the
generated hex engineID would be 800015dd0468656c6c6f
Rights:
Configuration of the access level (Read access or Read/Write access).
Authentication Protocol:
The protocols used for Authentication are MD5 and SHA (Secure Hash Algorithm).
Authentication-Passphrase:
User passphrase that must be at least 8 characters in length.
Privacy Protocol:
The protocols used for Encryption are DES (Data Encryption Standard) and AES (Advanced Encryption Stan-
dard).
Privacy Passphrase:
A passphrase which is used when encrypting packets. It must be at least 8 characters in length.
In this respect SHS is different from a redundant mode. In redundant mode a switching unit switches be-
tween one or the other clock, depending on its availability and sync status and the active clock passes the
timing signal on the NTP service.
SHS mode takes care for a secure operation and it steps into action when a time difference between both
receivers exceeds a configurable time limit.
When this happens the alarms will be trigged and send out via configured notification channels (e.g SNMP trap,
email, syslog message). Besides, the NTP should be stopped in this case too to support the secure operation
of the timing service, therefore you have to select “Stop NTP Service on Time Limit Error” at this step.
On the other hand, in IMS Systems with two reference clocks the timing signal coming from the clocks is
continuously measured with a RSC card (Redundant Switch Control unit) and compared against each other.
The measurements are forwarded to the SHS mode if this is enabled. Similar as in LANTIME systems with
SHS, the alarms can be triggered when a difference of the two signals exceeds the configured time limit settings
and the NTP service should be configured to stop.
SHS-Mode
The SHS mode can be selectively enabled or disabled via this selection box. If the SHS mode is disabled, no
time comparison takes place and the times of both receivers are transferred directly to the NTP service. The
NTP service then decides autonomously which time is used for synchronization (redundant mode).
In LANTIME IMS systems with a built-in RSC, the parameter is configured in nanoseconds. For systems
without an RSC in milliseconds.
In LANTIME IMS systems with a built-in RSC, the parameter is configured in nanoseconds. For systems
without an RSC in milliseconds.
The NTP configuration page is used to set up the additional NTP parameters needed for a more specific
configuration of the NTP subsystem.
Examples:
a) A LANTIME, which is synchronized by its internal reference clock such as GPS or DCF77,
acts as a Stratum 1 NTP server. If the "Disable Stratum Change" function is activated,
the NTP server will act as Stratum 1 server, if the reference clock goes asynchronous and
no other time sources are available.
b) A LANTIME, which is only synchronized by an external NTP server with Stratum 3, acts in a
network as Stratum 4 NTP server. If the "Disable Stratum Change" function is activated, the
NTP server will still act as Stratum 4 NTP server, even if the connection to the external NTP
server is lost.
c) If NTP of the LANTIME with activated "Disable Stratum Change" function, changes from its internal
reference clock to an external NTP server with Stratum 2, the Stratum of the LANTIME will change
from 1 to 3.
NTP Trustime
This setting defines for how long NTP should "trust" the internal reference clock of a server after this has become
asynchronous. The status of an asynchronous reference clock is also called "free running". The accuracy of a
"free running" reference clock depends on the type of the integrated oscillator. The trust time should therefore
be set dependent on the accuracy of the "free running" reference clock.
Figure: relation between holdover time (x) and offset (y) by using of built-in Meinberg oscillators
Procedure: First you should find out which oscillator is used. Go to the web interface menu "Monitoring
and Management → Clock → Receiver Information → Oscillator Type". Then you can define an offset, from
which the NTP should lose its stratum or the trust time.
You can find a list of oscillators available for Meinberg reference clocks here:
https://www.meinbergglobal.com/english/specs/gpsopt.htm
By activating this setting the following lines will be written into the NTP configuration of the Server:
These settings cause that the server no longer responds to NTP requests. In the submenu "NTP Restric-
tions" you can configure a “white list” of client IP addresses or even entire subnets whose requests are allowed
to be answered by the server.
Server Address:
IP oder Hostname of an external Server.
Symmetric Keys:
In this optional field, you can enter the ID of a symmetric key, which is to be used for authentication with the
external server.
To carry out with the authentication, we must pay attention to the following:
a) The NTP key file of the server must contain the ID. You can edit the key file in the submenu
"NTP → NTP Symmetric Keys" on the NTP page.
b) Additionally you must enter the ID into the field "Trustable Keys" under "NTP → General Settings".
c) The same key with the same ID must be configured on the external server.
Use Iburst:
The iburst activation accelerates the initial synchronization with an external server.
With an MRS, the external NTP servers are not written into the NTP configuration of the server. They
are queried internally every 32 seconds with the help of an "ntpdate" command. The determined time offset to
the internal reference is filtered and sent to the MRS unit.
Due to this particularity, the configuration possibilities for external NTP server are different:
The parameters Minpoll, Maxpoll and Iburst cannot be configured on a LANTIME/MRS. Regarding the au-
thentication only a symmetric key which is used for all configured external servers, can be configured. It is not
possible to use different keys for individual servers.
For a LANTIME/MRS you can adjust the default polling interval of 32 seconds via the manual configura-
tion of the server. To proceed follow this menu navigation:
Web Interface - "System Page → Services and Functions → Manual Configuration → Standard Configura-
tion → Miscellaneous Configuration"
You can use the parameter "MRS NTP POLL INTERVAL" to adjust the polling interval of the external server.
As per default this value is set to 0, which means that external are queried every 32 seconds. Values can be
set between 1 and 10 and are used as a power of 2. For example if this value is set to 6, this is equal to = 2(6
= 64 seconds for a polling interval.
Use the parameter „MRS NUM NTP PACKETS PER POLL“ to set the number of NTP queries sent per
polling interval. Per default this value is set to 0, which means that 4 packets are sent in a given polling
interval. Set a value between 1 and 8, which corresponds to the actual number of packets.
If the NTP time should be distributed in Broadcast mode in a local network, you can enter a valid broad-
cast address into this menu. Please note: starting with NTP4 version, the broadcast mode must always be used
with authentication.
Broadcast Address:
A valid broadcast address of a local network, to which the LANTIME is connected must be entered here.
Broadcast Interval:
The interval at which the server sends the NTP packets to the configured broadcast address.
Symmetric Keys:
In this field you can enter the ID of a symmetric key, which is to be used for authentication with the NTP clients.
a) The NTP key file of the server must contain the ID. You can edit the key file in the submenu
"NTP → NTP Symmetric Keys" on the NTP page.
b) Additionally you must enter the ID into the field "Trustable Keys" under "NTP → General Settings".
c) The same key with the same ID must be configured on the NTP client.
The following is an excerpt from the NTP configuration of a client, which is configured as a broadcast client
with authentication:
Broadcast Interval: The interval at which the server sends the NTP packets to the
configured broadcast address.
TTL: The configured TimeToLive (TTL) value determines how many hops NTP packets can
pass in the network. Each network hop reduces this value by 1. When the value
reaches zero, the network packet is dropped.
Symmetric Keys: For NTP Multicast, an authentication is recommended, but not mandatory.
However, if the authentication is configured on the server side, it is also necessary
to do so on the client side.
b) Additionally you must enter the ID into the field "Trustable Keys" under
"NTP → General Settings".
c) The same key with the same ID must be configured on the NTP client.
The following is an excerpt from the NTP configuration of a client, which is configured as a multicast client
with authentication:
NTP Manycast describes the possibility that one or more NTP servers are behind a multicast address. However,
contrary to the multicast method, the servers do not send NTP packets periodically to this mutlicast IP. The
Manycast feature is much more a method to automatically reconfigure the NTP service of a requesting client.
The NTP service of the client selects up to 3 servers automatically, which seem to be "best" for him. The NTP
service then reconfigures itself independently, and establishes a unicast communication with these servers. As
with multicasting, it is recommended to use authentication methods.
Manycast Address: Address field for entering the manycast address (mutlicast address space)
Symmetric Keys: For NTP Manycast, a key method for authentication is recommended, but not mandatory.
However, if the authentication method is configured on the server side, it is necessary
to do so on the client side.
In the field "Symmetric Keys" you can therefore enter the ID of a symmetric key, which
is to be used for authentication with the NTP clients.
a) The NTP key file of the server must contain the ID. You can edit the key file in the
submenu "NTP → NTP Symmetric Keys" on the NTP page.
b) Additionally you must enter the ID into the field "Trustable Keys" under "NTP → General Settings".
c) The same key with the same ID must be configured on the NTP client.
Since NTP version 3, NTP has been providing an authentication method using symmetric keys. The "NTP
MD5 Edit key" button can be used to edit the NTP key file of the server. Upon delivery of the server, the
file contains a sample key. The "Automatically Generate MD5 Keys" button allows MD5 keys to be generated
automatically.
The first column contains a unique key ID (value range 1 - 65535). The second column contains the key type
( "M" or "MD5" for an MD5 key, or "SHA1" for a SHA1 key). The third column contains the key string, which
may be between 1 and 32 characters long.
2. Enter the IDs of these keys into the "Trusted Keys" field under "NTP → General Settings", for example:
3. 3. The following is a sample excerpt from the NTP configuration of a Linux client which uses the key
with the ID 2 for authentication with the server 192.168.100.1 and the key with the ID 3 for authentication with
the server 192.168.100.2:
In this case, the key file of the client must contain the keys with the IDs 2 and 3, which must be identical to
the keys of the server.
The current NTP configuration file is displayed via the "Show current NTP configuration" button. This file
is automatically generated by the system at every restart or change of the NTP configuration and cannot be
edited directly.
If additional settings are required for NTP (Authentication, Restriction ...), which are not covered with the
existing settings on the NTP page, an additional configuration file must be used. This file can be edited and
managed using the "Edit Additional NTP Parameters" button. Every time the ’ntp.conf’ is created this additional
file is automatically attached to it.
The "NTP Restrictions" page can be used to restrict NTP access to specific IP addresses.
For example, to allow access for all addresses from the subnet 192.168.100.x, enter 192.168.100.0 under IP
Address and 255.255.255.0 under Netmask. Access can also be allowed for individual IP addresses.
In order to enable the restricted access, the "Activate Access Restriction" option must be activated under "NTP"
page, under → "General settings". Client IP addresses, which are not covered in the allowed IP address ranges,
will no more receive NTP responses from the LANTIME.
Some protocols or methods for transferring the time information, e.g. GPS, NTP, PTP, DCF77 and IRIG can
pre-announce leap seconds to give a receiver the opportunity to prepare for a leap second in advance. The GPS
satellite system distributes the leap second announcement six months before the leap second event. Meinberg
LANTIMEs with GPS receivers receive this announcement automatically via the GPS signal. In the log file of
the LANTIME, the entry "Leap Second Announced" is generated when the date of the leap second is received.
Other synchronization methods do not offer this announcement possibility, which can lead to a one second
time jump. Therefore, it is necessary to keep the NTP leap second file up-to-date on these systems, so that a
leap second is correctly inserted at the midnight (UTC).
In the menu "NTP Leap Second Handling", you can view the currently stored leap second file, you can manually
upload the file or configure an automatic download from the following source pages:
2. IERS (Earth Rotation and reference systems Service) Leap Second File:
https://hpiers.obspm.fr/iers/bul/bulc/ntp/ (directory listing)
https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list (current leapseconds file)
3. Meinberg Leap Second File (Copy of the IERS Leap Second File):
https://www.meinberg.de/download/ntp/leap-seconds.list
https://www.meinberg.de/download/ntp/leap_second
Time Scale
This setting configures the time zone of the NTP. The default setting is "UTC", since NTP is based on UTC by
default and standard NTP clients expect UTC time.
The setting ""LOCAL TIME" should only be selected, if the time server is used to synchronize specific clients
that require local time. If you select "LOCAL TIME" here, the exact time zone must be configured in the menu
"System → Display".
Attention: The use of "LOCAL TIME" is a violation of the NTP standard and causes standard NTP clients
to accept faulty time and to make a time jump accordingly.
Attention: The use of a "Fixed Offset" is a violation of the NTP standard and causes standard NTP clients
to accept faulty time and to make a time jump accordingly.
9.1.6 PTP
All parameters for proper PTP functionality can be configured in a clear and user friendly Web GUI. The
set of parameters which can be configured in the Web GUI corresponds to the PTP card version currently
installed in the system. Some features are available with TSU-GbE cards and above only and these are marked
as optional (*) in this manual.
When you log in to the Web GUI, please follow to the PTP dialog. In the main menu the following sub-
menus are listed:
• PTPv2 Status
• PTPv2 Configuration
If more than one PTP unit (PTP ports) is built into the system, then the status and configuration for each port
can be edited separately and will be listed on this page.
UUID
The UUID is the unique identifier of the PTP port which is based on the MAC address of the PTP port.
Port States
Uninitialized The PTP module is booting up, the software daemon has not yet started,the IP address
is not yet assigned.
Initializing In this state the port initializes its data sets, hardware, and communication facilities.
Stopped The PTP service has been stopped or it has not started due to a missing link on the PTP
port or a not-synchronized master clock after a startup.
Listening The port is waiting for the announceReceiptTimeout to expire or to receive an Announce
message from a master.
Passive The port is in passive mode, meaning there is another master clock active in the PTP
domain. The port can enter master state when it wins the BMCA (Best Master Clock
Algorithm) due to a failure/service degradation of the current master.
Uncalibrated The port wants to become a slave in the PTP domain and has already detected a suitable
grandmaster. The TSU is waiting to calculate the path delay to a Grandmaster.
Clock Accuracy The clock accuracy of the active grandmaster. This value is used in the Best Master
Clock Algorithm to select the best master.
PTP Seconds Current value of the raw PTP seconds value (seconds since 1970).
UTC Offset This value represent the current Offset to the PTP time based on TAI to calculate UTC.
Domain Number A PTP domain is a logical group of PTP devices within a physical network which is
defined by the same domain number. Slave devices that should sync to a certain master
in the network must be configured with a unique domain number which is the same as for
the master.
Port Link up Status 0: the port is down, check the link LED and the connection to the link partner.
If faulty, the network card should be replaced.
Delay Asymmetry If a static asymmetry offset in the network is known, this value may be entered (in ns)
to compensate it before the PTP start.
Clock Class PTP Clock class of the currently selected PTP grandmaster. This value is used in the
Best Master Clock Algorithm.
Time Source The type of a time source as used by the Grandmaster (informative only).
Leap Second Leap second announcement flag, set up to 24 hours prior the leap second event, depending
on the GM implementation.
You can check if SyncE functionality is activated on the card or not (if supported by the PTP module).
The configuration parameters are grouped in the submenus as follows. Submenus marked with * are avail-
able in TSU-GbE (and higher version) cards only.
• Network
• Global
• SyncE*
• Misc*
• Outputs*
Network Configuration
Monitor Interface Monitoring of network port’s link status.
As soon as the selected PTP network connection no longer detects a link,
this state triggers a "PTP Link Down" event. This event is displayed in
the menu "Notification → Notification Events".
If the PTP module is not required and is therefore not connected to the
network, the checkbox "Monitor Interface " can be unchecked. No error event
will be triggered then.
Hostname Hostname, a unique alphanumeric label, which distinguishes the selected PTP port
from others in the network can be entered here.
Enable DHCP-Client Activation / deactivation of DHCP service. If a DHCP Client is activated the field
for static IP configuration is deactivated. The opposite is the case when DHCP Client
is deactivated.
IP-Address from DHCP If DHCP service is found in the network, a valid IP for a PTP port will be assigned
automatically and displayed here.
Netmask from DHCP If DHCP service is found in the network, a valid Netmask for a PTP port will be
assigned automatically.
Gateway from DHCP If DHCP service is found in the network, a valid Gateway for a PTP port will be
assigned automatically.
TCP / IP Address If the DHCP Client is deactivated, this field can be edited to assign a valid
static IP address for the selected PTP interface.
Netmask If the DHCP Client is deactivated, this field can be edited to assign a netmask
for the selected PTP interface.
Default Gateway If the DHCP Client is deactivated, this field can be edited to assign a default
gateway for the selected PTP interface.
IPv6 Mode IPv6 addressing via DHCPv6 / Static assignment / Router Advertisement are available.
IPv6 Address Ipv6 Address assigned to the selected PTP port. If Static option is activated for
Ipv6 Mode, then a valid static IP address can be configured in this field.
IPv6 Multicast Scope The prefix of IPv6 multicast addresses specifies their scope. A specific scope in
case of multicast mode can be selected here.
Enable VLAN Option Activation / deactivation of Virtual LAN (IEEE 802.1Q) service on the PTP interface.
VLAN-Tag (1-4094) A 12-bit value specifying a VLAN ID to which a PTP port belongs.
Priority Values 0 (default, lowest priority) to 7 (highest priority) which can be used to
prioritize network traffic for different types of data.
Disable SSH Service If checked then SSH Access for this PTP port is deactivated.
DCSP PTP Classification Differentiated Services Code Point. This is a QoS parameter within the IP header
of the Classification PTP packet to prioritize the traffic.
Multicast TTL Time-To-Live. By default, the PTP multicast traffic is not routed and this value is
defined as "1" by the PTP standard. However a user defined configuration of the
TTLvalue can be entered here to change the default value.
Operating Mode
PTP or NTP
If supported, it is possible to run an NTP service in server mode with hardware timestamp support. In this step,
choose between PTP and NTP mode. It is not possible to run both modes simultaneously on one TSU card.
To monitor PTP network elements and generate statistics, a HPS100 can operate in monitor mode. Only
if this mode is activated, it is possible to monitor PTP-nodes in the network via the HPS100.
Select Profile
User can choose among preselected sets of PTP parameters defined in profiles usually used in different indus-
tries. If the default setting “Custom“ is selected, the user can select any parameter combination available in the
global configuration section as long as the PTP standard allows it. Depending on the selected profile, there
might be profile specific parameters available which can be found in the “Profile Specific Parameters“ section
below the standard PTP parameters sections.
SMPTE ST 2059-2
____________________________________________
In Multicast Master / Slave Mode:
____________________________________________
IEEE 802.1AS
DOCSIS 3.1
PTP Mode:
A PTP port can operate in one mode only: master or slave. When the mode is selected the user can choose
between multicast or unicast-only protocol. In the newest firmware a combined unicast multicast master mode
of operation is also supported.
Hybrid Mode:
In thsi mode PTP messages Sync, FollowUp and Announce are sent in Multicast whereas the DelayRequest
and DelayResponse Messages are sent in Unicast.
Delay Mechanism:
Two options possible:
E2E (End-to-end) where delay measurement messages are sent directly from a slave to the master (two end
nodes).
P2P (Peer-to-peer): each device (a peer) in the network exchanges peer-daly measurement messages. This
way each node can keep a track of the delays between itself and its immediately connected neighbour. P2P
mechanism can be used in 1588 PTP-capable networks only.
Network Protocol:
Two options for network protocol are possible:
ETH-IEEE 802.3 / Ethernet (Layer 2): Ethernet frames including MAC addresses of a slave and master.
UDP-UDP/IPv4/IPv6 (Layer 3): User Data Protocol one of the main protocols used for the Internet.
Priority 1:
The attribute is used in the execution of the best master clock algorithm (BMCA). Lower values take precedence.
Configurable range: 0..255. The operation of the BMCA selects clocks from a set with a lower value of priority1
over clocks from a set with a greater value of priority1.
Priority 2:
The attribute is used in the execution of the BMCA. Lower values tkae precedence.
Configurable range: 0..255.
In the event that the operation of the BMCA fails to order the clocks based on the values of priority1, clockClass,
clockAccuracy and scaledOffsetLogVariance, the priority2 attribute allows the creation of up to 256 priorities to
be evaluated before the tiebreaker. The tiebreaker is based on the clockIdentity. The values clockClass, clock-
Accuracy and scaledOffsetLogVariance depend on the internal state of the grandmaster and cannot be configured.
Msg. Intervals:
Specify the settings for PTP message rates.
Announce Interval:
Specifies the rate for sending announce messages between masters in order to select the current Grand Master.
Available settings are: 16/s, 8/s, 4/s . . . 2s, 4s, 8s, 16s with a default value 2 seconds.
Sync Interval:
Specifies the rate for sending sync messages from a master to slave.
Available settings are: 128/s, 64/s . . . 64s,128s, with a default value 1 second.
Domain Number:
A PTP domain is a logical group of PTP devices within a physical network which is defined by the same domain
number. Slave devices that should sync to a certain master in the network must be configured with a unique
domain number which is the same as for the master.
This submenu allows all relevant settings for the Synchronous Ethernet functionality. SyncE is an ITU-T
standard for computer networking that facilitates the transference of clock signals over the Ethernet physical
layer.
Note:
The SyncE signal can only be used as a reference input signal, when a TSU-GbE card operates in an MRI
Slot (see menu - “Configuration Receiver → MRS Settings“).
Enable SyncE
Activation / Deactivation if SyncE signal on a PTP port. SyncE runs on the PHY network layer therefore it
does not disturb PTP on Layer 2 or Layer 3. They both can run in parallel on the same port.
Fixed Input SSM Fixed Quality level of the SyncE input signal.
Fixed Output SSM Fixed Quality level of the SyncE output signal.
Mode
User can select if the copper port should be forced to act as the clock master or clock slave depending on the
role (Master/Slave) that this SyncE port should have. Missconfiguration can lead to link loss, so the user needs
to take care about the proper configuration of the link partners.
Port
The port can operate in a SyncE clock master or clock slave mode. A configuration is only necessary for the
copper port but not for Fibre Optic connections.
Two Step approach: The PTP protocol requires the master to periodically send SYNC messages to slave
devices. The hardware time stamping approach of PTP requires that the master records the exact time when
such a SYNC packet is going on the network wire and needs to communicate this time stamp to the slaves.
This can be achieved by sending this time stamp in a separate packet (a so-called FOLLOW-UP message).
One Step operation enabled: the SYNC messages itself is time stamped on- the- fly just before it leaves
the network port. Therefore, not FOLLOW-UP message is needed.
Disable PTP
A protocol within PTP use to query and update the PTP data sets maintained by master clocks. These messages
are also used to customize a PTP system and for initialization and fault management. Management messages
are used between management nodes and clocks. This feature is enabled per default.
TSU-GbE card comprises one Gigabit Ethernet SFP/RJ45 Combo Port for network synchronization and two
female BNC ouput interfaces with a list of available signals as follows:
A preconnected reference is necessary to provide a serial time string, a PPS (pulse per second) signal and
10MHz frequency. The accuracy of the measurements is derived from these signals.
The module calculates the frequency as well as the time, based on the mains frequency. The time deviation (TD)
is the difference of this calculated time (PLT) to the reference time (REF). This time deviation as well as the fre-
quency itself is sent out via serial interface or is being converted to an analog voltage output provided by a DAC.
Reference Time: REF - the time of the reference clock (i.e. GPS)
Power Line Time: PLT - the time of the monitored power line
Receiver State
With the FDM configuration menu the following parameters can be set:
Min Frequency: an error occurs if the frequency reaches the min constraint
Max Frequency: an error occurs if the frequency reaches the max constraint
Max Negative Time Deviation: an error occurs if the frequency reaches the max negative constraint
Max Positive Time Deviation: an error occurs if the frequency reaches the max positive constraint
Timezone: used local timezone for reference time and powerline time
Framing 7N2,7E1,7E2,8N1,8N2,8E1,7O2,8O1
The FDM180 provides two analog outputs (A0/A1) via the 16-pin X1 connector. These outputs have a voltage
range of -2.5V ... + 2.5V, divided into 65,536 steps (16-bit resolution).
Either the frequency deviation or the difference time of each analog output can be selected as display-value.
Mode:
Time Deviation: Depends on the defined constraints for Min Time Deviation and Max Time Deviation
Example: min:-100s and max:+100s if the time deviaton reach -100s the analog output
is at -2.5 V and if +100s then at +2.5 V with a resolution of 16bit DAC
Frequency Deviation: Depends on the defined constraints for Min Frequency Deviation and
Max Frequency Deviation
Example: min: 45Hz and max: 55Hz @ 50Hz line frequency if the frequency deviation
reach 45Hz the analog output is at -2.5 V and if 55Hz then at +2.5V with a resolution
of 16bit DAC
Time Deviation set a value to preconfigure the time deviation 0 for reset
(example: if you already had one FDM an get another one and want that both FDM
have the same time deviation value).
In this section, the user can add a new receiver for FDM telegrams. Any number of receivers (network displays
and/or PCs for analysis and display of status messages or frequencies), which are connected to the same net-
work, can be configured here.
Extended: Extended FDM time telegram with intermediate measurements and sequence ID
Sent once per second
i.e. "F:50.006 F:50.004 F:50.013 F:50.012 F:50.010 F:50.010 F:50.006 F:50.012 F:50.020"
or "F:50.013 FD:+00.013 REF:15:19:10 PLT:15:19:10.071 TD:+00.071 SEQ:0000000004"
Custom: Customized FDM time telegram, which consists of prefix, string and suffix
Sent once per second
Transport
Protocol: Used protocol for telegram transmission (TCP/UDP)
The following example will show the Powerline Frequency for 20 seconds, then the
Reference Time for 30 seconds, then the Frequency Deviation for 10 seconds. Afterwards,
it will start over with the PLF display:
PLF %PLFRQ Hz@20,REF %REFTIME@30,FDV %FRQDEV@10
Append
Timestamps: Indicates, whether a timestamp shall be appended to the message
Overview: Information about the used FDM module, model name, serial number, software revision, used serial
ports and display of the temperature sensors (degrees Celsius).
F:49.984_FD:-00.016_REF:15:03:30_PLT:15:03:30.378_TD:+00.378<CR><LF>
TD:+00.378 The time deviation between REF time and PL time, with sign character
(+/-), resolution: 1ms, maximum: +-99.999s
FD:-00.016_TD:+00.378<CR><LF>
<STX> 02049.984<CR><LF>
021-0.016<CR><LF>
022+00.378<CR><LF>
02315_03_30.378<CR><LF>
024068_15_03_30_<CR><LF>
<ETX>
<SOH>288:10:11:29 -00.03F+50.01<CR><LF>
-00.03 the mains frequency deviation from the setpoint, resolution 1mHz
T:10:03:09:02:15:03:30D:+000.378F:49.984<CR><LF>
T:10:03:09:02 The date of the reference time from the preconnected clock,
(year:month:day:day-of-the-week / Monday = 01, Sunday = 07)
Example of Fringrid:
Date: 20 March 2017
Time: 08:13:55 (UTC)
Time Deviation: +6.780s
Frequency Deviation: +0.012Hz
068:12:17:55?T-01.537F+0.123SF+60.095ST12:17:53.463<CR><LF>
9.1.7.13 Error-Bits
The FDM module registers errors and overflows and sets or deletes eight error bits then. In this way, the user
can find out if an "Overflow" occurs for example. These error bits document various error causes that occurred
during operation.
The error bits can be read out serially on request by an "E" (ASCII code 45h) via the interfaces COM 0/1.
Contact:
An input field for storing the contact information. The information is also displayed on the main page of the
web interface and can be queried via SNMP.
Location:
An input field for storing the device location. The information is also displayed on the main page of the web
interface and can be queried via SNMP.
Web Timeout:
The parameter Web Timeout defines how many minutes of inactivity can pass before a user is automatically
logged out of the Web interface.
Each configuration change can then be saved as start configuration by confirming with "Save as startup config-
uration now" button.
Reboot Device:
Initiates a restart of the LANTIME operating system. The built-in reference clock and output signals generated
by the clock remain unaffected.
Manual Configuration:
The "Manual Configuration" button allows a direct access to the configuration files of the LANTIME. This feature
should only be used by experienced administrators.
• Notification Settings
• Miscellaneous Configuration
• Network Configuration
• NTP Configuration
• NTP Broadcast Configuration
With "Manual configuration" you are able to change the main configuration by editing the configuration file
by hand. After editing, press the “Save file” button to preserve your changes, afterwards you are asked if your
changes should be activated by reloading the configuration (this results in reloading several subsystems like
NTPD, HTTPD etc.).
Create User
It is possible to create multiple user accounts on a LANTIME system, each account can be assigned one of three
access levels: the Super-User level has full read-write access to the configuration of the LANTIME system, it
can modify all parameters and has full shell access to the system when logging in via Telnet, SSH or serial
console port. Administrator level accounts can only modify parameters via the WEB interface but does not
have shell access. The access level "Info" can only review status and configuration options but is not allowed to
modify any parameters or configuration files.
User List
This submenu gives you an overview of all configured LANTIME users. By clicking "Delete User" a single user
can be deleted.
Timeout (ms):
Period of time how long to wait for an "access accept" packet from an authentication server.
RADIUS:
Radius stands for Remote Authentication Dial In User Service and provides centralized authentication for LAN-
TIME devices. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport
protocol.
The LANTIME RADIUS authentication requires that each account that should be able to login to the LANTIME
has a Vendor Specific Attribute (VSA) called MBG-Management-Privilege-Level configured. This VSA has to
be added to the RADIUS configuration of an external authentication server. Here some additional Information
on the attribute:
Name = MBG-Management-Privilege-Level
Datatype = Integer
Vendor-Code = 5597
Vendor assigned attribute number = 1
Value range = 100, 200, 300
In addition you need to assign a value of 100 (Super User), 200 (Admin User) or 300 (Info User) for this
attribute for each RADIUS user, which should be able to login to the LANTIME.
The LANTIME TACACS authentication requires that each account that should be able to login to the LANTIME
has configured an attribute called "priv-lvl". This attribute needs to be configured on the TACACS Server.
For a Super-User account the attribute has to be "100", for an Admin account "200" and for an Info User
account "300". In the following an example of a tac_plus server configuration file:
# This is the shared secret that clients have to use to access Tacacs+
key = meinberg
# User Groups
group = lantime_super_user {
service = lantime_mgmt {
priv-lvl = 100
}
}
group = lantime_admin_user {
service = lantime_mgmt {
priv-lvl = 200
}
}
group = lantime_info_user {
service = lantime_mgmt {
priv-lvl = 300
}
}
# User
Through this form you can add an external authentication server to the LANTIME configuration. The ex-
ternal authentication has to be enabled first in the "External Authentication Options" menu.
Authentication Method:
Configuration of the authentication method to use, either Radius or TACACS+.Detailed information on both
methods can be found in the menu "External Authentication Options".
Authentication Server:
The IP or Host of the selected Authentication Server (IPv4 and IPv6 are supported).
Shared Secret:
A shared secret is used for a basic authentication between a LANTIME and the authentication server. The
shared secret of the external authentication server has to be entered in this field. A list of allowed signs which
can be used for the shared secret you can find in the chapter "Before you Start → Text and Syntax Conventions")
Port:
Depending on the authentication method, the default port is already configured here. If needed, the port can
be changed.
This table gives you a quick overview of the configured authentication servers. Each server can be removed by
either a Super- or Admin-User by clicking the "Delete Server" button.
A list of allowed signs which can be used as special characters you can find in the chapter "Before you
Start → Text and Syntax Conventions")
- Monthly
- Quarterly
- Half-Yearly
- Yearly
The "System Information" menu offers the possibility to view important log files and setups of the LANTIME.
Show System Messages: Displaying the LANTIME SYSLOG file stored in /var/log/messages
Show Device Version: Displaying the additional device information (model, firmware,
serial number, built-in hardware components, etc.)
Show Receiver Information: Displaying the additional status information on the built-in reference clock.
Show Reboot Log: Displaying the reboot logs stored in /mnt/flash/data/reboot.log. The log file
contains information about past system reboots.
If you need to update the software of your LANTIME, you need a specific update file. You can download the
latest LANTIME firmware version from our website: https://www.meinbergglobal.com/english/sw/firmware.htm
The update file can be uploaded to the LANTIME by first choosing the file on your local computer with
the "Browse" button and then press "Start Update". Afterwards you are prompted to confirm the start of the
update process.
A diagnostic file which includes all status data of a LANTIME system logged since the last reboot can be
downloaded from all LANTIME servers. The file format of the diagnostic file is a tgz-archive. The archive
contains all the important configuration and logfiles. In most support cases it is the first action to ask the user
to download the diagnostic file, because it is very helpful to identify the current state of the LANTIME and to
find possible errors.
With this menu you can save different configuration files for backup on the flash memory of the LANTIME.
By using the "Activate" button a stored configuration can be loaded, the "Delete" button can be used to delete
a configuration file and the "Download" button in order to download a file.
Additionally more than one Firmware version can be archived on the LANTIME. If an updated version is
not corresponding correctly in the environment, then it is possible to reactivate one of the established versions
again on the LANTIME.
9.1.8.11 Display
Time Zone:
Time Zone setting for the front panel display of the LANTIME and the time which is shown in the "Date/Time"
section of the Main page in the web interface. Note: This setting does not affect the time which is provided by
the LANTIME through NTP, PTP, serial time strings or IRIG.
Exception:
In the case NTP is configured to provide local time instead of UTC you need to configure the exact local time
zone here in the display time zone setting. This setting is then used for NTP as well.
Example:
(UTC+1) - CET/CEST,CEST,0,25.03.****,+,02:00,02:00:00,CET,0,25.10.****,+,01:00,03:00:00
The string above is the time zone definition for middle Europe. If you require a new time zone setting, this needs
to be configured in the same format. The string contains different information, each information is separated
by a comma. A detailed description of different string parts shown by an example of the time zone setting for
middle Europe is as follows:
2. Field: Abbreviation of time zone with daylight saving (max 4 letter) → CEST
Control Mode: Setting of the operating mode. The following options are available:
Automatically: With this mode, the fans switch on automatically as soon as the current
system temperature exceeds the configured temperature threshold.
Temperature Threshold (C◦ ): Specification of the system temperature threshold in degrees Celsius.
The configured temperature value is taken into account for control of fans
when the fan mode "Automatically" is selected.
As long as a value below 50W is displayed in the "Current Power" row, one power supply is sufficient to
power up the system. With a value exceeding 50W, a total of three power supplies are required to ensure
redundancy.
Consumer Load
This table lists all consumers of the system. The backplane, the CPU, the power supplies, the receivers and all
other modules used. The sum of all consumers gives the value that is displayed as Current Power.
9.1.9 Statistics
The red lines and the primary Y-axis represent the offset between the system time and the NTP reference
time source (in ms). The blue line and the secondary Y-axis, on the other hand, illustrate the frequency ad-
justment of the oscillator which is built on the CPU by the ntpd (in PPM), to adjust the system time to the
reference time source.
The minimum and maximum measured value of the frequency deviation and offsets can be read in the up-
per right corner.
This graphic is only available if the LANTIME is equipped with a PTP module, which is configured as PTP
SLAVE.
The red line shows the time offset between the time of the built-in reference clock and the incoming PTP
signal (in micro s). The blue line shows the path delay determined by the PTP module.
Remote IP:
IP address of the NTP peer or 127.127.x.x if it is a hardware time reference, e.g. a radio clock or a GPS receiver.
A legend of codes standing next to each IP address of NTP peers is the following:
Remote Host:
Resolved DNS name
RefID:
The time reference of the NTP peer.
Stratum:
Stratum value of the NTP peer.
Type:
Type of the NTP Peer:
When:
Value in seconds. Indicates when the NTP peer was last queried.
Poll:
Period in seconds. Specifies the interval at which the NTP peer is queried.
Delay:
Value in ms. Displays the runtime of the NTP packet.
Offset:
The NTP software compares its own system time at regular intervals with its reference time sources. This
process is called "polling". After each polling operation, the packet trip time is determined, calculated, and the
current time difference ("offset") is calculated and displayed in milliseconds.
Jitter:
The packet trip time changes more or less depending on the characteristics of the network during the "polling"
of external NTP sources at each time comparison, and the calculated time offset also varies. For this reason,
the results of successive time comparisons are filtered by calculating weighted mean values for packet run time
and time offset. The deviations of the individual values from these mean values are referred to as "jitter", and the
higher the jitter value, the less accurate is the calculated time offset. On the other hand, a steadily increasing
mean time offset indicates that the system time drifts away from the reference time. The value is displayed in
milliseconds.
More information about the NTP Query Tool can be found in the NTP documentation at
http://doc.ntp.org/current-stable/ntpq.html
Last:
Time in seconds. Specifies when the client requested the time from the LANTIME.
Avg Interval:
Interval: Average time in seconds between two NTP requests.
Rstr:
Shows if there are active Restrict Flags for this remote IP.
R:
Indicates whether the "Rate Control" is active or not.
M:
NTP package identification
0→ reserved
1→ symmetric active
2→ symmetric passive
3→ client
4→ server
5→ broadcast
6→ NTP control message
7→ reserved
V:
NTP Version
Count:
Number of packets received from the remote address
Rport:
"Source Port" of the last received packet
Remote Address:
IP Address of the requesting device
• „clockvar“
• „associations“
• „readvar“
More information about the query tool can be found in the NTP documentation at
http://doc.ntp.org/current-stable/ntpq.html
Activate Logging:
Activates the feature on the LANTIME.
Duration of Recording:
The duration for which the LANTIME maintains the client list. When configuring continuous recording, old
daily statistics are automatically cleared after a few days in order to save space.
Log Level:
Determines which version of the IP protocol is taken into account. Available are IPv4, IPv6 or both versions in
combination.
A click on Details will now also show you detailed information about the received NTP packets of a par-
ticular client.
9.1.10 Clock
On this page of the web interface, configurations can be made on the respective installed reference clocks or
the changeover card.
Depending on the design of the system, which means whether it is a single reference clock or a system with two
installed remote clocks and a changeover card, the web interface builds up accordingly. This also applies to the
type of reference clock and its options. In case of a redundant receiver configuration the common settings for
"IRIG In/Out", "Serial Ports", "Time Zone", "Enable Outputs", "Programmable Pulses" and "Synthesizers" appears
into the "Switch Card" menu.
Status: No Connection,
No signal → the reference source is not available.
Offset: Time difference of the reference clock to the specified time source.
Figure: Activated IRSA mode with estimated precision values for available references.
1. Configure a priority list of available reference signals in descending order from the superior to inferior
one in the MRS Settings menu (see chapter MRS Source Priority).
2. Activate IRSA in the IRSA menu. As per default the IRSA is deactivated.
3. Fill in the estimated precision values for the input reference signals in for this provided "Precision" column.
According to the estimated precision values the holdover time between current source and the next source from
the priority list will be calculated.
Here are some estimated precision values which you can load as defaults:
- GPS / GNSS as the first priority has the highest estimated precision :100 ns
- ext. Osc. (e.g. Rubidium): 120 ns
- PTP IEEE 1588: 100 ns
- PPS plus string: 100 ns
- NTP: 100 us
The Time of Day (ToD) information represents a “wall clock time” – a specific time with hours, minutes, seconds
and the corresponding date. The ToD information cannot be delivered by an atomic clock alone. Therefore,
if you need the ToD in your system, you need to select one of the reference signal which includes the ToD
information, for example GPS, NTP, PTP, PPS plus string.
If you use the mixed mode the reference clock will be steered first by a reference signal which includes the ToD.
The oscillator will be roughly adjusted until it reaches the highest level of accuracy that can be achieved by
this reference. After that the reference clock switches automatically to a more accurate source, for example a
1PPS coming from an external atomic clock that provides highly stable phase or a 10MHz signal to provide a
stable frequency.
As per default both ToD and Phase are enabled for each available reference source. If you want to use
the mixed mode, then select the ToD for one reference signal and phase for another. The reference sources
you wish to use should be configured first in the Source Priority list. See MRS Settings → MRS Source Priority.
Figure: An example for a mixed combination of ToD and Phase source for given reference signals.
To activate this feature, select "Use Trusted Source" check box for the GPS reference signal. It means that
GPS reference will be checked for consistency by another reference source which is acknowledged as a Trusted
Source. In our case the trusted source is a Rubidium atomic clock. It is denoted as ext.Osc. (external oscillator)
in the table of Extended Options. Therefore select this check box "Is Trusted Source".
The external Rubidium acts as an external oscillator that is synchronized by the GPS or GNSS Master as
long as the master is available and its precision is better than the precision of the XHE. If the Master fails
or for some reason uses corrupted or manipulated data the TRS will detect this as an offset limit violation.
Consequently, the reference selection algorithm will discard the current master and the XHE Rubidium source
will become the new master for synchronization.
Both GNSS and Rubidium reference signals need to be configured first in the Source Priority list, GPS or
GNSS as "Source 1" and external Oscillator as "Source 2". All other positions should be left empty (see chapter
MRS Source Priority).
Second, the IRSA Reference algorithm should be activated with corresponding precisions (see chapter IRSA -
Intelligent Reference Selection Algorithm).
The precision for GPS or GNSS is at same time also the TRS limit, that the reference should comply with. If the
TRS limit is violated the reference selection algorithm discards the current master and switches automatically to
the Trusted Source - XHE Rubidium. For the GPS or GNSS precision value we take 250ns which is maximum
time deviation allowed for the receiver.
Finally, the GPS or GNSS source should have enabled "Time of Day Source" and "Phase Source", which
means that the receiver is a source for both Time of Day and Phase. At the XHE Rubidium only the Phase
Source should be enabled, since the atomic clock alone does not deliver the ToD information (see chapter MRS
Features).
So, if you choose for example GPS as a reference signal at priority 1 while having "Auto Bias Master" ac-
tivated for GPS, then GPS will be used as a measurement reference for all other sources as long as GPS is
available.
If PTP is configured as a secondary priority with "Auto Bias Slave" activated, the constant offset of the PTP
input signal is measured against the current “Auto Bias Master” reference (e.g. GPS) and will be compensated
automatically.
1 GPS / GNSS: The Trusted Source (TRS) feature will only work with GPS180 and GNS181 receivers.
Furthermore, even if PTP becomes a reference signal in case that a Master is not available, the PTP off-
sets will include a compensation for the initial offset measured against the previous Master automatically. In
this operating mode a smooth transition from GPS to PTP will be possible without a time step in case GPS
becomes unavailable.
If PTP is then a primary sync source and an asymmetry step suddenly occurs in the network (due to path
rearrangements e.g.), the occurring asymmetry step will therefore be automatically compensated as well in case
"Asymmetry Step Detection" is activated.
Limit:
Here you can configure a limit value. If the reference source exceeds this limit, a notification is triggered. A
configuration in the Web Interface is required on the Notification page "Notification → Notofication Event →
XMR Limit Exceed".
Depending on the system configuration, the configuration of the incoming and / or outgoing time codes can
be configured in this menu. There are three common time codes:
IEEE1344 In addition to a two-digit year, the offset to the UTC time, the current
daylight saving time status and announcements from the start and the end
of the summer time, as well as information about an upcoming leap second
are transmitted.
Input Code:
Configuration of the incoming IRIG / AFNOR / IEEE 1344 time code (MRS systems only).
UTC Offset:
If the applied timecode is impinged with a constant time offset to UTC, this time offset must be configured here,
so that the clock can convert the received time to UTC.
Output code:
If the system has direct TC output options, you can set the parameters in this menu section.
Time Scale:
The output of the selected time code can be done with UTC or the local time. When "LOCAL TIME" is used, it
refers to the configuration of the menu point "Time zone".
Mode: You can configure an interval (per second, per minute, on request "?" Only)
for the outgoing time string. If the operating mode is set on "Request", a
connected client must send a "?" to receive the time telegram in response.
Features:
Two operating modes are available for the output of the capture time stamps, "on request ? Only" and "au-
tomatically".
automatically
In this mode, the capture events are output directly on the serial interface.
The data of the time zone are used from the time zone table (see chapter 9.1.8.11 System → Display).
Optionally, the outputs of the reference clock can be set to always supply a signal when the device is switched
on, or only when the internal clock is running synchronously.
Cycle: For "Cycle Pulse" mode, an interval can be configured in hh: mm: ss.
Time: In the configured mode "Single Shot", the time for the pulse can be parameterized
in hh:mm:ss.
DCF Suspend In the "DCF77 Marks" mode, you can configure a shutdown time for the output port,
After (min): so that in the case of an asynchrony of the reference clock, no DCF mark is available
at the output.
On / Off Time: For the "Timer" mode, it is possible to configure start and stop times in hh:mm:ss.
Disable output If the reference clock is asynchronous, the output signal is immediately deactivated
in Holdover mode: when the checkbox is activated.
Note: In the clock-submenu "Enabling the Outputs" the Pulses option "if sync"
must be select so that the outputs can be switched off in holdover mode.
9.1.10.13 Synthesizer
The output frequency and phase of the integrated synthesizer can be set here.
Frequency: Frequencies from 1/3 Hz up to 10 MHz can be set by entering four digits and a
frequency range. By entering the frequency 0 Hz, the synthesizer can be switched off.
Phase: With phase you can enter the phase position of the set frequency in the range -180◦ to +180◦
with a resolution of 0.1. When the phase angle is increased, the delay of the output signal
gets bigger. If a frequency higher than 10 kHz has been set, the phase cannot be changed.
GPS since 1st of January 1980 - GPS System Time: monotonous time scale without leap seconds.
Includes the leap seconds from 1970-1980.
TAI since the 1st of January 1970 - International Atomic Time: monotonous time
scale without leap seconds. Difference to GPS Time: 19 seconds.
If you change the timescale in the drop-down menu a warning message will appear in the browser window.
Please Note:
If the GPS receiver is configured to output GPS or TAI timescale instead of UTC, the distributed time via NTP
isn’t based on UTC then. This is a protocol violation and this time server can’t be used to synchronize standard
NTP clients which expect UTC time.
Time/Date:
With this function, the reference clock can manually be set to a specific date and time.
This menu item lists all the important information and options of the reference clock.
Explanation of GPS Satellite Status "Satellites in View" and "Number of Good Satellites"
Satellites of the GPS and other GNSS systems are usually not stationary, but circle around the globe on
well-known tracks, so each individual satellite may be above or below the horizon at a given location and time.
Satellites that are below the horizon can’t be tracked anyway, so the receiver uses its last known position and
almanac data from the satellites to determine which satellites are currently expected to be above the horizon
at its geographic position, and can potentially be tracked. All these satellites are called to be in view.
However, even some the satellites that are in view may be shielded by buildings, mountains, etc., so the
receiver may be unable to track these satellites. Also, individual satellites may be temporarily in maintenance
mode, so they must not be used even if they can be tracked. Only satellites that can be tracked and are not in
maintenance mode are considered good and used to determine the current position and time.
So the number of good satellites can never exceed the number of satellites in view, but it can be signifi-
cantly less if the antenna has been installed in a location with limited view to the sky. In worst case this can
lead to limited accuracy, or only temporary synchronization.
In order to avoid unnecessary switching operations, for example during periodic free running of a system,
the order of the active and the reserve system is exchanged at every change-over. For example, if the active
system switches to the free running mode while the reserve system is operating synchronously, it is switched
over to the synchronous reserve system. A reset to the old state occurs only if the now active system (formerly
the reserve system) loses synchronization, while the reserve system (previously active system) operates syn-
chronously. If both systems operate in the free-running mode, no changeover is made and the current state is
retained.
This menu item lists all the important information and options of the switch card.
Each MRI card is dedicated to one clock module. If a redundant solution requires external synchronization
inputs for both clock modules, two MRI cards have to be installed. The MRI card is available with 4x BNC or
4x FO connectors
For further and detailed configuration settings of the MRI card please look at chapter 9.1.10 - "Web GUI
→ Clock → MRS Settings".
The clock inputs are configurable (1 kHz - 10 Mhz). Furthermore a 1PPS input is provided as well.
An ESI card is, as the MRI card, dedicated to one specific clock module (depending on the slot it is in-
stalled in) and can be installed in both ESI as well as MRI slots.
Type – PPS in
Input 2: The input 2 accepts as input either 2048/1544 kHz frequency or configurable frequency in range
between 1kHz and 10 MHz, also 1.544kHz if required.
Input 3:
See Input 2, but with RJ45 Connector and as default Frequency input 2048 kHz.
Input 4: As fixed frequency you can choose between E1 framed and T1 framed.
Quality Maximum SSM / Maximum BOC (quality levels for T1 framed signal)
Synchronization Status Message (SSM) in accordance with ITU G.704-1998 standard includes 4 bit long SSM
quality messages received via incoming E1 framed signal. The lower is the bit sequence the higher is quality
of the source clock. The clock source quality levels according to G.704-1998 are as follows:
With the Quality Selection box, you can select the Minimum SSM level of the incoming signal that is still
acceptable as input signal. If clock reports a lower quality level than the configured minimum SSM level the
system will not use it for synchronization.
Example:
User configured QL-SSU-B as Minimum QL for his system. An E1 input signal reporting either QL-SSU-A or
QL-PRC will be allowed for synchronization, whereas a signal with quality level QL-EEC1/SEC will not be
accepted.
Sa Bits Group
Here you can select between the Sa4 to Sa8 bit group to choose the location for SSM quality bits.
There are no other configration settings for a BPE card in the I/O Chapter. For further detailed settings on
output signals of the BPE card please proceed to the Clock Configuration Chapter 9.1.10.
• 1PPS, 10 MHz
• Time Codes: IRIG A/B/E/G/AFNOR/IEEE1344/C37.118/NASA36
• Frequency Synthesizer (sine- wave + TTL)
• Programmable Pulses: 1PPS, 1PPM, 1PPH, Timer. Single Shot
• Cyclic Pulses; DCF77 Mark, Sync Status
• Serial Timestrings (RS232 o RS 422 / 485)
Mode:
Timer Mode This mode simulates a programmable day assigned timer. Three turn-off and turn-on
times are programmable for each output. If you want to program a switch time, change
the turn-on time "On time" and the corresponding turn-off time "Off time".
A turn-on time later than the turn-off time would cause a switch program running over
midnight. For example a program "On time" 10:45:00, "Off time" 9:30:00 would cause an
active output 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 values "On time" and "Off time".
In this case the switch time does not affect the output.
Single Shot Modus Selecting Single Shot generates a single pulse of defined length once per day. You can
enter the time when the pulse is generated with the "Time" value. The value "Length"
determines the pulse duration. The pulse duration can vary from 10 msec to 10 sec in
steps of 10 msec.
For example: a cycle time of 1 hour 45 minutes would cause a pulse every 6300
seconds (starting from 0 o’clock). The appearing distance between the last pulse of a
day and the first pulse of the next day (0:00:00 o’clock) would be only 4500 sec. The
value in entry field "Cycle" turns red, when entering a time that causes this asymmetry.
DCF77 Marks In "DCF77 Marks" mode the selected output simulates the telegram as transmitted by
german time code transmitter DCF77. 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
with the "Timeout" value. DCF Simulation is never suspended, if the delay value is zero.
Submenu Common:
Submenu Synthesizer:
Phase 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. If frequency is
set to 0 the synthesizer is disabled. With "Phase" It is possible to enter the phase
of the generated frequency from -360◦ to +360◦ with a resolution of 0.1◦ . Increasing
the phase lets the signal come out later. Phase affects frequencies less than
10.00 kHz only!
IRIG Out
IRIG Output Code Output code which is distribute in the system to all cards.
Submenu Output 1:
Output Type
Clock Outputs: 2.048 MHz (E1-mode) or 1.544 MHz (T1-mode), G.703, 75 Ohm, unbalanced
or 2.048 MHz (E1-mode) or 1.544 MHz (T1-mode), G.703, 120 Ohm, balanced.
With the pull-down menu "Output Configuration" the available outputs of the I/O slots can be configured:
T1 or E1?
T1 is a digital carrier signal that transmits the DS - 1 signal. It has a data rate of about 1.544 Mbit/second. It
contains 24 digital channels and therefore requires a device that has a digital connection.
E1 is the european equivalent to T1. T1 is the North American term whereas E1 is a European term for
digital transmission. The data rate of E1 is about 2 Mbit/second. It has 32 channels at the speed of 64
Kbit/second. 2 channels among 32 are already reserved.
One channel is used for signaling while the other is used for controlling. The difference between T1 and
E1 lies in the number of channels here.
Sa Bits
ITU-T Recommendations allow for bits Sa4 to Sa8 to be used in specific point-to-point applications (e.g.
transcoder equipment) within national borders. When these bits are not used and on links crossing an interna-
tional border they should be set to 1.
The Sa4 bit may be used as a message-based data link for operation, maintenance and performance moni-
toring. The SSM Bit (Synchronization Status Message) can be selected in the Web GUI for clock quality
information. Sa4 is selected as default.
This module is not only designed for our IMS series and generates various audio frequencies for studio appli-
cations. The SCG module can also operate in our 19-inch rackmount and 1U Multipac chassis.
Output Type Studio Clock Out (Word Clock) or Digital Audio Out (DARS)
State on or off
In the menu "IO Configuration" you can set the output on DARS for every output of the SCG-B. The four
available outputs can optionally be switched off.
Functionality
The board is synchronized by an external 10MHz signal. It generates configurable video signals in different
formats. The generated signals have a phase reference to 1PPS.
• Four BNC outputs @ 75Ω with configurable video formats and Sync Signals
– Out 1: HD-Syncs (Tri-Level Sync)
– Out 2: SD-Syncs (Bi-Level-Sync)
– Out 3: Sync Signale (H-Sync, V-Sync, . . . )
– Out 4: DARS
• Four LEDs: Signal status of module and outputs
• Supported Video-Formats:
– PAL, NTSC(SD)
– 720p/50Hz (SMPTE296M3)(HD)
– 1080i/25Hz (SMPTE274M6)(HD)
– 720p/59,94Hz (SMPTE296M1)(HD)
– 1080i/29,97Hz (SMPTE274M7)(HD)
The card has a high quality oscillator, which is locked to an external 10MHz signal. The microprocessor
monitors the lock status of the PLL and the warm up phase of the oscillator. It activates the outputs only after
the phase is locked.
This condition is signalized by the LEDs. In the phase locked state, the output levels of the four outputs are
monitored, and in case of a failure signalized by an associated LED.
Non-IMS-Systems IMS-Systems
LNE
The LNE card adds additional network interfaces to the management CPU, increasing the number of NTP and
management ports available.
The additional ports can be used to separate network traffic on physical network segments. For further config-
uration options please see the chapter "Ref -> Chp. Network".
For further detailed configuration settings for this card please see chapter 9.1.2, "Web GUI → Network menu".
The ability to select Master and Slave operation for either Default, Power, Telecom or SMPTE profile makes
this product the most flexible PTP solution on the market, suitable for a wide range of applications.
A lot of IEEE 1588 slave devices or NTP clients from different market segments can be synchronized, even
over IPv6 networks, for example eNodeB’s for LTE base stations, Linux servers with hardware-assisted time
stamping support for high-frequency trading applications, IEEE 1588 compatible IEDs in Smart Grid environ-
ments or IP-interconnected Audio / Video devices in broadcast studios.
The Synchronous Ethernet function provides a high accurate frequency transport over Ethernet networks. The
card can be used either to take a SyncE signal from the network as a source or generate SyncE as a Master.
For further information on PTP features and detailed configuration for this card please proceed to Chapter
9.1.6, "Web GUI → PTP menu".
Via the web interface, each port can be set separately to "Input" or "Output". If a port is set to "Output",
the system PPS or the 10 MHz reference frequency is output signal at this port. If a port is set to "Input" the
incoming signal is compared to the system PPS or to the 10MHz reference frequency. The offset values are
displayed in the status window.
PTP nodes need to support the Meinberg TLV approach or standard PTPv2 Management messages, other-
wise they cannot be monitored. NTP nodes can only be monitored if they are configured to respond to NTP
client requests (Note: A NTP client that is using the Windows Time Service W32Time does not respond to
NTP client requests per default configuration. W32Time needs to configured to act as client and server at the
same time. Otherwise the node cannot be monitored via SyncMon.
However, also all configured MRS and ESI inputs (like PPS and Freq inputs) can be monitored if an ESI
(Extension Signal Input) card is available. The Sync Monitor feature is now available on Meinberg IMS Sys-
tems with firmware version 6.22 or later and for PTP monitoring with integrated HPS-100 PTP card with a
minimum 1024 client performance license.
The Sync Monitor can run either as a node independent from a master clock. In this case a Sync Monitor
node can be located basically anywhere in the network; but most probably as close as possible to the slaves to
be able to measure their actual accuracy. At the same time you can monitor also the performance of a GM and
measure the potential network asymmetry which is present in the link between a GM and the Sync Monitoring
Node.
It is possible to configure up to 1000 nodes for monitoring in the Sync Monitoring interface running on a
standard LANTIME or IMS System. You can specify monitoring and logging intervals for each individual node
separately. Besides, an offset limit can be configured for each node which triggers an alarm notification (via
SNMP, email, relay output or a user defined channel) if the limit for this particular node is exceeded. For NTP
nodes you can define also a stratum limit, which can also trigger an alarming when the defined limit is exceeded.
Moreover, for each node it is possible to download all the monitoring data and its log files which can be
used to generate a report or for further statistical analysis.
Figure: Sync Monitor user interface on LANTIME systems with a FW 6.24 or later.
In the Sync Monitor Status and Configuration dialogue you can add new members for measuring their ac-
curacy and monitoring their sync performance. By selecting a "+" Add member button you will proceed to an
enter configuration dialog in order to add a new node for monitoring.
The features in the "Add Member" configuration dialog have the following configuration options:
Monitoring via:
Select a monitoring instance from the drop down list. The drop down list appears differently in different
HW configurations. The following options are available:
Main CPU: This monitoring instance is always available and is not dependent on HW configuration of
the LANTIME system. It can monitor native NTP nodes only, which are responing to NTP client
requests (Note: A NTP client that is using the Windows Time Service W32Time does not respond
to NTP client requests per default configuration. W32Time needs to configured to act as client
and server at the same time. Otherwise the node cannot be monitored via SyncMon). All assigned
interfaces can be monitored at the same time or you can select a particular interface from a
list if available.
HPS: [Slot card position,e.g IO4] - this monitoring instance can monitor PTP nodes, supporting
protocols PTP with TLV (proprietary for a Meinberg Sync Node), PTP with MGMT (defined in
the IEEE 1588v2 standard) and NTP with software time stamping.
ESI: This monitoring instance can monitor PPS and Freq nodes with Extension Signal Input (ESI)
card. From a dropdown list you can select which particular signal you wish to monitor.
Options available are: PPS0, Freq In0, Freq In1, BITS In2
MRS-CLK: This monitoring instance can monitor all activated MRS/XMR input signals for each
MRS-reference clock. From a dropdown list you can select which signal you want to monitor.
Options available are: GNSS/ GPS, NTP, PTP, PPS, IRIG, 10MHz, E1, 2048kHz, -
(depending on HW options → see Clock tab in the Web interface.
Alias:
Alias name for a monitoring node to find it easily in the complete table overview. The alias name which is
configured by the user will define the name of the directory on flash disc (’Base Path for logfiles for history of
days’) of each node. The alias name has to be unique and one word without blanks with a maximum length of 63
characters. It is possible to monitor the same node (e.g. the same IP-address) with different alias names - this
may be useful if you want to monitor the same node from different monitoring modules (e.g. different HPS100
IMS cards with separate network paths).
Location:
Enter a physical location of a monitoring node for you to recognize this node easily in the complete table. The
location name has to be one word without blanks with a maximum length of 63 characters.
Group Index:
You can group monitored nodes within a logical group by assigning them the same index, (e.g. nodes with the
same group index may be of the same kind (NTP, PTP, PPS), or at the same location, etc.)
Stratum Limit:
Threshold value for a NTP stratum level. If the stratum level of a monitored client is higher than the configured
stratum limit, it will generate an alarm (sent by eMail, SNMP trap or to an external syslog server).
If a HPS card at a corresponding slot [IMS Slot card position, e.g IO5] is the selected monitoring instance
with a PTP option then you will get an additional feature to configure instead of a stratum value and besides,
no symmetric keys are available.
Domain:
A logical group of PTP devices defined within a physical network. Only nodes with the same domain number
can see PTP messages from other nodes in the same domain.
When you are finished with configuration of a new monitored node, save the current configuration by click-
ing the "Save Member" button. By clicking the "Remove Member" button you will remove the currently selected
node from the complete list of all monitored nodes. All sampled data for the particular node will be lost if you
did not back-up the saved data prior its removal.
By clicking the "Remove Existing Data" button all data for only this specific node will be erased.
Scan for new Nodes is an automatic search for NTP and PTP nodes within your network.
Figure: Scan for new Nodes dialog. Only newly found nodes will appear in this temporary table. Select nodes
which you wish to add in the overall monitoring node table.
Figure: To scan the network for PTP nodes a HPS card with activated monitoring has to be selected first in
the Search for Nodes dropdown list.
PTP Domain:
The network connected to that HPS card will be scanned in the domain, which was defined here by user. The
following mappings as defined in IEEE 1588-2008 will be scanned:
- UDP/IPv4/Ethernet,
- UDP/IPv6/Ethernet,
- Ethernet (IEEE 802.3, layer 2).
When starting the scan first a PTP Management message will be sent in broadcast mode to get the "port
state" of each PTP node - this will be done with IPv4, IPv6 and Layer2.
All PTP nodes which answer to this request will ask for the "current status" and "clock status" with man-
agement messages that follow. The result will be displayed as a list of all available PTP nodes. Each new
PTP Node will be entered in an overview table of the available nodes.
Only new nodes which have not yet been configured will be shown in the table. For each node the PTP-UUID,
MAC-Address, IP-Address, Vendor name, Feature (if a node supports PTP with extended TLV for monitoring
or PTP management messages only), Domain number, Status (the current PTP status like Slave, Master, Lis-
tening . . . ), Offset and Delay (current measured values from PTP management message) will be automatically
displayed in the table. With select-boxes new nodes can be added automatically to the list of the monitored
nodes. The parameters for Location, Group Index, Request Interval, Logging Interval, Offset Limit and Stratum
Limit can be defined in the next step before adding the selected nodes.
The monitoring engine will start to send PTP/NTP requests in the configured intervals to each node from
the list and measure the time received in the responses with its own time (which is traceable to UTC, GNSS
sync for example). The current offset and status information can be checked in the status overview table in the
Node Monitoring menu.
In the status overview table of monitored nodes, next to the status information you will find 3 action but-
tons: Graph, Error Logs and Edit.
By selecting the Graph button a Graphical Diagram for the selected node will show up. At this page you
find several features for different representation options.
Figure: Graphical diagram of offset values for each node, selectable for different time ranges (day, week, month
or manual selection). With given buttons at the "Select Time Range" you can select either past or future intervals
for the graphical representation.
Offsets are collected for each NTP/PTP or PPS monitored node and can be depicted as graphical repre-
sentation for selectable time intervals in the web UI of the SyncMon node.
The monitored data are continuously saved on the Sync node "Base Path for logfiles for current day" and
will be saved automatically to the Flash Card (’Base Path for logfiles for history of days’) at change of a day
at 0:00 UTC. Data are available at any time for further statistic processing.
The red line represents the offset between a Sync node reference time and the measured time of a moni-
tored device. For PTP and PPS signals, the sync node reference is an internal reference time from the receiver
(e.g. multi GNSS (GPS, GLONASS, Galileo, Beidou), external UTC time service, IRIG TC, long wave time
reference: eg. PZF, MSF, WWVB . . . ). The sync node reference is depicted as a green line. For multi GNSS
reference clock in normal operation you will see something in the lower nano second range with 5ns resolution.
For NTP monitored signal the Sync node is synchronized the internal NTP that is in sync by an internal
reference clock (multi GNSS or IRIG TC, long wave ...). In this case the green line in the graph represents the
internal NTP system time.
Select Y Range:
Different options available: autoscale, or fixed Y ranges in decade intervals: 100ns,1us, 10us, 100us, 1ms, 10ms
and 100ms.
Select Graph:
Different graph options are available for NTP and PTP nodes.
For NTP nodes it is possible to view a graph either as raw data or with applied Median Filter or a graph of
the internal reference only (the green line).
Measured offset to a PTP node (offset of a PTP slave measured against the internal reference). The mea-
surements are available only for PTP slaves which support monitoring PTP protocol with TLVs. Along with the
measured values obtained by reverse PTP, also reported value curve is available and MTIE filled curve if MIN
and MAX value measurement is supported on the monitored node.
For PPS nodes monitored via an ESI input card at the Sync node, you will have the graph modes available:
raw data, data with applied Median Filter and Internal Reference only (a PPS from an internal reference clock.)
If the request-interval is less than the log-interval then additional Min/Max values for that log-interval will be
stored in the data files. These Min/Max values will be added automatically as a filled curve in the graphical
diagram and the mean value will be shown as red line in that filled Min/Max curve.
Report Button:
With this selection the current data of the monitored node will be prepared in a form of a report.
You can also select a time frame for sampled data from which a report will be generated. The report includes the
current status data, monitor configuration, monitoring statistical values over the selected time frame, a graphical
diagram and a full sync map related to the monitored node.
Figure: Generated report for a selected node. The report includes a status information of the selected monitored
nodes, monitor configuration, main monitor statistics and graphical diagrams.
With this selection the data of current selected time range of the monitoring node will be shown
as a scrollable box with the raw measured data. These data can be selected manually and copied to other
applications.
Error Log
Back in the main Sync Mon menu, by selecting the Error Logs button you will enter the Error Logs page of
the selected monitored node. At this page the log messages are shown since the last system reboot. When the
flash memory card gets full, the older logs will be overwritten.
At the bottom of the page there is a button "Show Global Error Logs" by which you can switch to view all
Error Messages coming from all monitored nodes.
In case of "Offset Limit exceeded" and "not reachable" an icon with the count of events will be shown in the
table of monitored nodes in the Events column. These events will be updated automatically every 10s. With
the "Reset Events" button which can be found above the overview table you can reset the current counter for
the events. These events are shown also in the SyncMap.
To deselect a node which has been selected, either click again into its check box and it will be deselected
or click the "-" icon in the top row and you will deselect all nodes at the same time.
If you click the button "Actions for selected nodes" you will find actions which you can apply over the nodes.
Besides, the report also provides a light version of a sync map, which includes only the selected nodes from the
table. In the sync map each individual node is highlighted and the rest are depicted in the background to get
a comparison of how the given node is performing in relation to other nodes considered in the report.
The monitored devices are called nodes. Nodes have to support one of the following signals: NTP (RFC1305),
PTP (IEEE 1588v2) or PPS connected to ESI (Extension Signal Input) IMS card.
The goal is to visualize an absolute offset of monitored nodes in terms of predefined offset limits. The data can
be shown according to the current offset status or over a selectable time range (e.g. one day). It is also possible
to animate the dynamic behavior of the monitored nodes of the last 60min, where SyncMaps are generated
automatically every minute. This mode is called SyncMap Cyclic Mode.
Figure: The SyncMap as a graphical representation of the monitored nodes in a network visualized as a polar
diagram. It can display nodes which support: NTP, PTP (IEEE 1588v2) or PPS signals.
Figure: A node representation in the SyncMap. The meaning of different color codes and parts which belong
to a node are explained in the text.
The Time Monitor reference with its reference clock stands in the middle, labeled as the "Time Monitor" [1]. It
provides a timing reference by a controlled oscillator (synchronized by GPS, GLN, PZF, Galileo, Beidou or an
external clock supply). The Time Monitor node in the center [1] is shown in green color when the reference
clock is synchronous. In addition the current offset between the controlled oscillator and the reference time
source is shown as a value [1].
Around the center four concentric circles representing the scaling of the polar diagram are drawn. All nodes
[3] are connected concentrically by a line [2] from the central node. The distance from the center to the nodes
represents the absolute average time offset between the Time Monitor and each individual node. The average
value is calculated over the selected "Time Range". Each node is shown as a circle with a color inside [3] that
corresponds the status and an outer ring [4],that corresponds its type.
Additionally, the statistical values: the standard deviation [8] is represented as circle segments. These values
represent the temporal jitter of the measured values around the mean value. When the circle segment color is
red, then the deviation is dependent on the scaling and it exceeds the half of range of the decade -> example:
if the middle deviation is in the range 1us - 10us and the largest found maximum >5us, then the individual
segment is drawn red, otherwise blue [10].
If one of the events occur "Offset Limit Exceeded" or "not reachable" then the circle segment will become dark
red and a white value which represents the count of each event. The circle slide near the center [5,7] represent
the Events “not reachable” and the outer circle slide [6,7] represent the Events "Offset Limit Exceeded".
While sliding with the mouse over a node in the syncmap without clicking a corresponding info window with
the name and some statistical values will be shown:
By selecting a specific node in the SyncMap with a left mouse click the following menu will be opened:
• Show reachable: currently reachable nodes are shown in the Sync Map.
• Show all Nodes: all nodes configured in the monitoring list are shown in the Sync Map, even unreachable
ones.
• Show NTP only: only nodes which are monitored via NTP protocol are shown in the Sync Map. They
will appear encircled with a yellow ring.
• Show PTP only: only nodes which are monitored via PTP protocol will be shown in the Sync Map. Nodes
will appear with a dark blue ring if the PTP with TLV protocol is used for monitoring or with a light blue
ring if the PTP protocol with Management Messages is used.
Time Range: the Sync Map can be generated using the monitoring data sampled in the past
30 min, past 5 min, in the past 24 hrs or within a manually selected time range.
Also the statistical values are calculated using the data in the selected time
interval respectively.
Scaling: possible scaling options: decade steps or linear for different time accuracy ranges.
For PTP nodes it may be suitable to use scaling in lower microsecond range, whereas
for NTP you can select ranges in a few 100microseconds or millisecond range.
Refresh Button: Immediately refreshes the Sync Map based on the currently available statistics of each
single node. A new SyncMap with the selected time range will be generated- it is like
a reload of this WEB page with the latest measurements.
Start Cyclic: will activate the SyncMap animation mode. In this mode every minute a new SyncMap with
the latest measurements will be generated. The last 60 SyncMaps will be then displayed
as an animation. A new sequence will start with a blank SyncMap. The statistics time
range will be set by default to 5min.
Help Button: will show the online help page for a SyncMap feature.
A short legend:
1 The Time Monitor node and the current offset measured between its oscillator and the reference time.
2 Line connecting each node with the SyncMon. Its length represents the absolute average time offset
between Reference of SyncMon and the node.
The color defines the sign of the average: yellow=negative blue=positive
3 A measured node, its color inside corresponds to its status.
4 Outer ring which corresponds the type of the node.
5 Event counter for "Node not reachable".
6 Event counter for "Node Offset Limit exceeded".
7 If Event counter > 0 then this slide is dark red. If Event counter = 0 the Standard Deviation is
light red or light blue.
8 Standard deviation measurement. If light red, it exceeds the 100 percent of current offset,
otherwise is blue.
The System Monitoring is an optional feature and as per default it is disabled. It has to be enabled in
the menu "SyncMon → System Settings" in the System Parameters dialog.
If the System Monitoring is enabled, then all signals will be measured and logged automatically in the same
way like Node Monitoring, namely System Monitoring page will be visible.
Figure: An overview table for internal signals as shown in the System Monitoring page. The system signals
you wish to monitor, need to be first selected in the Source Priority list for each reference clock individually.
The number of MRS References (CLK1-GPS-0, CLK1-NTP-1, CLK1-PTP-2 . . . ) depends on the activated
Source Priorities for each reference clock – this can be configured on the "Clock" page in the "MRS Settings"
for each clock.
Global Error Log gives the option to track all error events.
Error Log Statistics: categorization of error logs for each specific node.
Clear Error Logs: deletes the list of logged errors.
Figure: Memory card status, available space left and logfiles archiving options.
There is an indicator implemented which informs about the available flash space "Available Space on Flash"
and the number of days left for monitoring of the current sync node setup. The current data will be stored on
the flash card. However you can choose an additional path for saving the current data into a RAM. The data
from RAM will be stored automatically to the flash card each day at UTC 0:00.
There is an extra button "Save Logfiles now" to store the files from the RAM to the flash card at any time.
With the button "Remove Logfiles" all files on the flash card will be removed without a backup.
Two extra synchronization scripts can be activated to copy each measured data to an external server. One
will be activated after every request interval of each monitored node and the other will be activated after every
log-interval. These scripts will be activated after every cycle when the monitoring of all devices has been
finished. For example you can use the following command to copy all files to a server with rsync:
In the next example all changes at request or log-interval will be sent via syslog message to an exter-
nal syslog server (these files can be edited via CLI in /config/syncmon_sync_script_for_req and /config/sync-
mon_sync_script_for_log):
#!/bin/bash
#
# /config/syncmon_sync_script_for_req
#
LAN_0="172.22.13.244"
LOG_PROG="syncmon"
LOG_LEVEL="info"
LOG_FILE="/var/log/syncmon_last_req_measurement.log"
while read LINE
do
logger -t $LOG_PROG -p $LOG_LEVEL "$LAN_0 $LINE"
done < $LOG_FILE
As Network Protocol options you can choose between the UDP or TCP/IP protocols, running as per de-
fault on a port:514.
Name of this SyncMon device: you can monitor your network by different Sync Monitoring devices. You
can give them unique names to recognize it easily in the database server, where the data come from.
When you finish the server configuration, save it by clicking the "Save Syslog" button.
Figure: Configuration options for an external database server where the monitoring data can be automatically
stored.
Figure: System Parameters settings within the Sync Mon feature. Here you can set the current path where
the data for the current day and history data is stored. Be aware when the flash card is full, the oldest data
will be overwritten.
Enable System Monitoring: the monitoring of internal signals like CPU-Utilization, local NTP, ESI inputs,
MRS-References and Refclock parameters, depending on integrated hardware of the system will be activated.
By default the monitoring of the system is disabled.
The measured data of the monitored nodes will be stored in separate directories on a flash disc. The base
path of the stored data files can be configured by the user, therefore it is also possible to use an external flash
disc (e.g. USB stick). The data will be stored separately for each day and each monitored node.
/data
| /stats
| /syncmon
| /alias-name1
| | ntp_mon_stats.20170201
| | ntp_mon_stats.20170202
| | ntp_mon_stats.20170203
| | ...
| /alias-name2
| ntp_mon_stats.20170201
| ntp_mon_stats.20170202
| ntp_mon_stats.20170203
| ...
Figure: Example for default path structure of history of days datafiles on the flash card.
Example for NTP data files with request interval less than log-interval:
# Day Sec Modified_Julian_day_time Raw_offset Median_offs Path_delay NTP_stratum Min Max
58043 21705 2017-10-17T06:01:45+00:00 -0.000000129 -0.000000053 0.000007667 1 R -0.0001 0.0001
The size of a data file per day depends on the logging interval and has a size of about 110kB if log-interval is
64s.
Examples:
• 10 monitoring nodes with log-interval = 1s will store 70MBytes (69194kBytes) per day – the default size
of the flash used for SyncMon logging is about 400MB – so 5 days can be stored on internal flash disk.
• 100 monitoring nodes with log-interval = 1s will store 700MB per day – then data logging will stop if the
flash is full – the log rotating for SyncMon will be started at 00:00 UTC and will erase data files older
than 2 days. The CPU utilization will increase about 10%.
• 100 monitoring nodes with request interval = 1s and log-interval = 64s will store about 12MBytes per
day – so about 40 days can be stored on internal flash disk. The CPU utilization will increase about 7%.
• 900 monitoring nodes with request interval = 1s and log-interval = 64s will store about 100MBytes per
day – so about 4 days can be stored on internal flash disk. The CPU utilization will increase about 45%
- this is critical for the NTP server performance of the device.
# Node-Address NTP:Offset -filtered Delay NTP-Stratum Auth MTIE CntErr CntErr Error Message
# PTP:OffsNode -measured PTP-Status Offset Reach
# -------------------------------------------------------------------------------------------------------------
172.16.100.65: -0.000113960 0.000055254 0.001663415 2 0 0 3 0 0 Normal Operation
172.16.3.11: -0.005109103 -0.005896857 0.001891819 1 0 0 0 0 0 Normal Operation
172.16.3.12: -0.028305041 -0.028305041 0.001669302 2 0 0 0 0 1 Error: Offset Limit exceeded
172.27.101.90: -0.000037604 -0.000002865 0.000352269 2 0 0 0 0 0 Normal Operation
172.27.100.32: 0.000008375 0.000008375 0.000209699 1 0 0 0 0 0 Normal Operation
172.27.100.1: 0.000000899 -0.000027105 0.000416735 1 2 0 0 0 7 Error: Authentication failed
ESI-Module: 0.000001819 0.000001839 0.000000000 0 0 0 0 0 0 Normal Operation
EC:46:70:00:8F:64: 0.000000000 0.000000000 0.000000000 0 0 0 0 0 6 Error: Time Monitor not active
172.27.19.68: 0.000000109 -0.000000013 0.000007451 9 0 0 0 0 0 Normal Operation
EC:46:70:00:8F:64: -0.000000049 -0.000000171 0.000006273 9 0 0 0 0 0 Normal Operation
172.27.19.70: 0.000000030 -0.000000035 0.000007749 9 0 0 0 0 0 Normal Operation
172.27.19.98: 0.000000000 0.000000000 0.000000000 0 0 0 0 0 3 Error: Not reachable
172.27.101.143: 0.000000000 0.000000000 0.000000000 0 0 0 0 0 3 Error: Not reachable
172.27.19.11: -0.000010202 -0.000090331 0.000052625 8 0 1 0 0 0 Normal Operation
172.27.101.90: 0.000000000 0.000000000 0.000352269 2 0 0 0 0 3 Error: Not reachable
For each of these external servers the following parameters can be set:
The Meinberg Standard Format corresponds to the SyncMon data format stored in a file system on a LANTIME.
This will be later used for the SyncMon Manager. The SyncMon Manager is currently in development and will
be able to visualize the data stored on an external server and generate reports.
For more Details about SyncMon formats see chapter SyncMon Formats.
The XtraStats page is used for monitoring available reference sources and system parameters like CPU load
and memory consumption. To start recording data for a certain aspect of the system just press the "Start" link
in the Actions column. If enough data is available a new link appears to show the data as a text file or as a
graph. The graph will be created when clicking the link. Only the data that has been collected so far will be
shown. To update the graph just reload the page.
It’s recommended to stop the monitoring if not needed anymore to reduce the workload and disk storage
consumption of the unit.
The system comes with a certain set of predefined statistics definitions and will add new ones based on
the hardware and software configuration of the unit. It is also possible to add own definitions. To do this please
contact the Meinberg Tech Support and they will provide a guideline.
All collected data are available in the /var/log for further processing. The data is saved in the volatile memory
and will be lost if the unit is shut down. If the data is needed for further processing please make sure to save
them externaly.
An MRS LANTIME logs the offset statistics of all configured MRS time sources independently.
Data:
A selection of daily statistics. mrs_stats0 always stands for the present day.
Graph:
Select the MRS source for which a graphic is to be generated. The link "Graph" is used to create the graphic.
The LANTIME documents can be downloaded from here in order to read / print them on your workstation.
The "Docs & Support" Tab does also provide some important weblinks. It furthermore gives you information
about the Meinberg Sync Academy - MSA.
The Meinberg Sync Academy offers and develops tutorials in the field of time- and frequency synchronization,
such as NTP, PTP IEEE-1588 and many more. This Part of the LANTIME "Docs & Support" Tab provides basic
information about the Sync Academy followed by some links to helpful informations on http://www.meinberg.academy.
The Support Information chapter gives you all necessary information how to contact the technical support.
Apart from that it provides a link to the firmwareportal of Meinberg.
The command line interface (CLI) of the sixth LANTIME firmware generation is using a text-only (non-graphical)
approach. It can be accessed using local connections (serial console ports) or remote network connections (SSH
or Telnet). The CLI is based on a standard Unix shell interpreter called Bourne Again Shell (Bash), offering
comfortable editing of a command line by using the cursor keys and delete/backspace. By accessing a command
history using the up/down cursor keys, the shell allows to modify an already used command or simply execute
it again, without modification, if required. The tabulator key (Tab) can be used to auto-complete a command
and saves the user from having to type in the full command name.
By using a standard shell the LTOS6 firmware environment can benefit from a number of additional advan-
tages. A Unix system administrator will certainly already know how to work with a shell and by making use of
the script language elements of the shell, very sophisticated or recurring command sequences can be automated.
In addition to the Bourne Again Shell the so-called Debian Almquist Shell ("Dash") and the standard Almquist
Shell ("ash") are available on the system and can be used in addition or as a replacement to the standard shell.
This reference manual does not contain a description for every of the more than 400 commands that are available
on a LTOS6 system. It tries to cover the most popular commands, especially those that are LANTIME specific
and that are not existing on other Unix- or GNU Linux based systems. A number of commands allows to read
a short help text describing the parameters and use of the command by executing "commandname -h".
For any questions regarding the LANTIME command line interface, please contact your Meinberg Technical
Support.
Serial Console
Serial console ports are located on the front panel or (in modular systems) on the CPU module (some devices
come with both a front port and a CPU console port). These ports can be accessed with a serial terminal
running at 38400 baud and using 8 data bits, no parity, 1 stop bit (8N1).
Logging in
The default configuration knows one user account (root) with a standard password (timeserver). Other users can
access the CLI only if their access level has been set to "Super User". If that is not the case, the system will
reject the user and does not allow to access the command line interface.
A "Super User" will be presented with a system status overview after successfully authentication, followed
by a shell prompt.
Automatic Logout
The CLI will automatically terminate a CLI session if a user does not enter a command for more than 300 seconds
(5 minutes). This timeout can be disabled by entering the "no_shell_timeout" command. It can be changed by
using the "set TMOUT=x" command (x represents the new timeout in seconds).
To edit a command line, the left/right cursor keys (or, alternatively, CTRL+B and CTRL+F) can be used
to move the cursor. Entering ESC+F and ESC+B will move the cursor to the beginning of the next or previous
word. And BACKSPACE (CTRL+H) deletes the character to the left of the cursor.
Conventions
The command names in this chapter are shown in bold characters, parameters (if supported) are represented in
italic characters. If a parameter or part of the commandline is optional, i.e. it does not have to be entered, it is
surrounded by brackets [ ].
The character "#" at the beginning of a line represents the shell prompt, which will contain different char-
acters depending on the configuration and status of the device.
Examples:
# pwd
(shows the name of the currently selected directory)
# ls [path]
(shows the content of the specified path [path] or - if no [path] parameter has been entered, the content of the
current directory.
Purpose
This command lists all files included in a saved configuration (i.e. a so-called "configset") for a given pack-
age. It can also list all saved configsets for a given package.
If both package and configset have been specified, the command will show all files included in the speci-
fied configset for the given package. If only the package is provided, lsconfig will output a list of all available
configsets that include saved configuration files for the specified package. If "all" is specified as the package
name, the command covers all installed packages.
Examples
# lsconfig network myconfig1
(shows all files of the network configuration which are included in the saved config set "myconfig1")
# lsconfig snmp startup
(lists the SNMP related configuration files in the startup configset. This configset is automatically loaded
during system startup.)
# rmconfig all myconfig2
(this lists the files for all pacakges in the configset myconfig2)
Purpose
This command deletes a saved configuration (i.e. a so-called "configset"). Attention: rmconfig does not ask
for a confirmation, it immediately removes the selected configutation from the flash memory of the device. This
is non-reversible and therefore requires you to be very careful when using this command.
The parameter package specifies the package whose configuration should be deleted. This could be "net-
work" or "lantime" or "snmp". The available packages can be found by looking at the contents of the /package
directory, in which you can find a subdirectory for each package installed. If the given package name is "all",
the whole configuration set will be deleted.
The configset parameter defines the saved configuration ("configset") from which the package configuration shall
be deleted. It is not allowed to use "default" because the default configuration of a package cannot be deleted. By
specifying the configset "startup", the default package configuration will be restored during the next system start.
Examples
# rmconfig network myconfig1
(removes the network configuration from the saved config set "myconfig1")
Purpose
With this command a saved configuration (i.e. a so-called "configset") can be compared with the current config-
uration. This allows to check for unsaved configuration changes.
The parameter package specifies the package whose configuration should be compared. Examples would be
"network" or "lantime" or "snmp". If the given package name is "all", the complete configuration set will be com-
pared. This is the default behavior if no package name is specified on the command line.
The configset parameter defines with which saved configuration ("configset") the currently running configu-
ration should be compared.If this is not specified on the command line, the configset "startup" is used as a
default.
Examples
# diffconfig network myconfig1
(compares the current network configuration with the saved config set "myconfig1")
# diffconfig
(shows the differences between the current configuration to the "startup" configset, i.e. for all packages)
Purpose
This command shows whether an unsaved configuration change has been detected or not. It does not show
any details on configuration changes (like diffconfig).
Examples
# checkconfig
No configuration changes.
Purpose
This command saves the currently active configuration in a configuration set ("configset"). It can be used to
persistently store configuration changes (by saving them to the "startup" configset that is loaded during the
powerup/boot sequence) and to backup a configuration.
package specifies the package whose configuration should be saved. Examples for this are "snmp" or "ssh"
or "network". If no package name is provided on the command line, the configuration for all packages is saved
as a standard behavior.
The configset parameter defines the saved configuration ("configset") to which the package configuration(s)
shall be saved. It is not allowed to use "default" because the default configuration of a package cannot be
overwritten/changed. By specifying the configset "startup", the configuration will be restored during the next
system start. If no configset name is specified, the startup configuration set ("startup") is used as a default.
Examples
# saveconfig snmp
(saves the SNMP configuration to the startup configuration "startup")
Purpose
The loadconfig command loads the configuration for the whole system (all packages) or a given package from a
previously saved configuration set ("configset"). It can be used to restore the default configuration, the startup
configuration or a configuration backup.
The package parameter specifies the package whose configuration should be loaded. Using "all" will load
the configuration for all packages. If no package name is provided on the command line, "all" is assumed as the
standard behavior.
With the configset parameter the name of the previously saved configuration ("configset") is defined. The pack-
age configuration(s) is loaded from this configuration set. Specifying "default" will load the default values of the
package and "startup" loads the startup configuration set that is automatically loaded during the powerup/boot
process. If no configset is given, the "startup" configset is loaded.
Examples
# loadconfig snmp
(loads the SNMP configuration from the startup configuration "startup")
Purpose
The pwd command prints the name and path of the current working directory.
Examples
# pwd snmp
/var/run
Purpose
The cd command changes the current working directory.
The system changes the working directory to the given directory or, if no directory has been specified, to
the home directory of the current user.
Examples
# cd /etc
(sets the working directory to /etc)
# cd
(changes to the home directory of the current user, e.g. /root for the root user)
Purpose
With this command, the contents of a given directory can be listed.
The content of the given directory are printed. A large number of options is available which control how the ls
command lists all the files and subdirectories. Please use the "–help" option to get a list of all supported options.
Examples
# ls /var/log
(shows the content of the /var/log directory in standard output format)
# ls -l /var/run
(lists the files and subdirectories of the /var/run directory, using the "long" output format (-l) which shows a
number of details like file sizes)
Purpose
The "cp" command copies files or whole directories.
One or more files can be specified as the source(s), wildcards (like * or ?) are allowed. The target can
either be a directory or, if the source is one single file, a target filename.
Copying a whole directory structure is possible by using the "-r" (recursive) option.
Examples
# cp /etc/hosts /var/tmp
(copies the file hosts from the /etc directory into the target directory /var/tmp where it will be stored under the
same name, i.e. hosts)
# cp /config/global_configuration /var/tmp/mycopy
(copies the file global_configuration from the /config directory into the target directory /var/tmp using the target
filename mycopy)
# cp /etc/ssh/ssh_* /tmp/
(copies all files form /etc/ssh with a filename beginning with "ssh_" into the directory /tmp)
# cp -r /etc/udev /tmp/
(creates a copy of the /etc/udev directory with all subdirectories and containing files in the target directory
/tmp)
Purpose
The "mv" command moves files or whole directories from one location to another. It can be used to rename
files and directories, too.
One or more files can be specified as the source(s), wildcards (like * or ?) are allowed. The target can
either be a directory or, if the source is one single file, a target filename. In this case, the original file will be
moved and renamed at the same time.
Examples
# mv /dir_a/file_a /dir_b/file_b
(moves the file file_a from the /dir_a directory into the target directory /dir_b and renames it to file_b)
# mv /dir_a/file_a /dir_b/
(moves the file file_a from the /dir_a directory into the target directory /dir_b but preserves the filename)
# mv /dir_a/file_*.txt /tmp/
(moves all files from /dir_a with a filename beginning with "file_" and ending on ".txt" into the directory /tmp)
# mv /dir_a/ /tmp/
(moves the whole directory /dir_a with all its subdirectories and included files into the /tmp directory)
Purpose
The "rm" command deletes one or more files or whole directories (including all their content, i.e. files and subdi-
rectories). It is possible to use wildcard characters to delete a group of similar named files, e.g. "*.bak" includes
all filenames that end on ".bak". Since deleting files and directories can lead to system malfunction and all kinds
of failures, the "rm" command should only be used if you are 100% sure that the specified files/directories are
not required for proper operation of the LANTIME system. If you are in doubt, please contact Meinberg support.
Deleted files and directores cannot be restored and are lost forever. Because of this, the "rm" command should
be used with the greatest caution.
One or more files can be specified, wildcards (like * or ?) are allowed. If a whole directory and all its
contents shall be deleted, the "-r" option needs to be specified.
There is no "Are you sure?" prompt shown before the deletion is carried out, the system will immediately
delete the specified files. In order to avoid system failures, please triple check whether the file(s) and/or
directories you specify are really OK to be deleted.
Examples
# rm /dir_a/file_a
(deletes the file file_a from the /dir_a directory)
# rm -r /dir_b/
(deletes the whole /dir_b directory and all included files and subdirectories - forever)
Purpose
The "cat" command shows the contents of a given file.
The content of the given file is printed. The "cat" command can be combined with the "less" command to
allow paginated output and offers an easier way to review a file.
Examples
# cat /var/log/messages
(shows the content of the file messages in the /var/log directory)
Purpose
The "fwlist" command prints a list of all firmware images which are installed on the device.
The [searchpattern] parameter can be used to filter the list of installed firmware images. If no searchpat-
tern is specified, all installed images are listed. The "-v" option will show the version number of each firmware
image behind its name.
Examples
# fwlist
(shows all installed firmware images)
# fwlist -v fw_*
(shows all installed firmware images with a name beginning with "fw_" and their respective firmware revision)
# fwlist OSV
(shows the installed firmware image with the name "OSV")
Purpose
With the "fwselect" command it is possible to activate an installed firmware image, i.e. that firmware image
is started during the next boot sequence. If an error occurs during the activation, the system will roll back to
the previous state.
If fwselect is started without any parameters, it will show the name of the activated firmware image, i.e. the
image that is going to be used at the next system start.
The [FWImage] parameter specifies which firmware image is going to be used at the next system start. Without
this parameter, "fwselect" will print the name of the currently selected image and exits.
Examples
# fwselect
(shows the currently activated firmware image)
# fwselect fw_6.12.004
(selects the image "fw_6.12.004" and tries to prepare the system to use this image at the next boot sequence)
Purpose
The "fwrm" command can be used to delete one or more firmware images from the internal flash memory to
regain space.
or
The FWImage parameter defines which image will be deleted. The secon form (–wipe-all) deletes all firmware
images except the OSV image, the currently running image and - if different from the running image - the
firmware image that has been selected to be activated at the next system start. The optional "keep" parameter
allows to specify how many firmware images should be preserved in addition to the non-deletable images men-
tioned above.
Examples
# fwrm fw_6.14.021
(deletes the firmware image fw_6.14.021)
Purpose
Starting with version 6.15 all firmware updates will be installed in compressed form to preserve flash space.
Such an image is read-only and cannot be modified, i.e. it is not possible to add or remove files or change their
content in any way. Under normal circumstances this is not required and therefore it is recommended to use
compressed images instead of uncompressed ("standard") ones. If it is necessary for a specific user requirement
to change the contents of a firmware image, the "fwuncompress" command can extract the contents of a com-
pressed image and create a new, uncompressed copy of it. The (compressed) source image will not be touched
or changed in any way by "fwuncompress" and, if not required anymore, would have to be deleted manually
afterwards using the "fwrm" command.
It is possible to uncompress the currently running firmware image without any problems.
The specified image (name usually starts with "fw_") will be used to create an uncompressed copy of it. The
newly created image will get a prefix "u", i.e. uncompressing a firmware image "fw_6.15.015" will create an
uncompressed image named "ufw_6.15.015".
Examples
# fwuncompress fw_6.16.002
(extract the contents of the compressed firmware image fw_6.616.002, creating a new image named ufw_6.16.002)
The main configuration file for network related settings is /etc/mbg/net.cfg which contains definitions and
parameters for all physical and logical ("virtual") network interfaces. This file, its structure and content, is
described in detail in the Configuration Files chapter.
9.2.3.23 netconfig - Check for Network Configuration Changes and Apply them
Purpose
With netconfig the system will compare the state of all network interfaces (both physical and virtual) with
their configuration. If any required changes are detected, they will be applied.
If, for example, a virtual interface has been configured but is missing, it will be created and configured ac-
cording to the net.cfg contents.
Examples
# netconfig
(checks all network interfaces and applies changes, if the configuration differs from the current state)
Purpose
nicinfo displays the configuration status of physical network interfaces. It lists the MAC address, the as-
signed bonding group, the link speed and duplex mode as well as the IPv6 mode.
-s Short Mode
This option leads to a very compact output, only indicating the current configuration state of an interface:
If an interface name is specified with the INTERFACE parameter, "nicinfo" will only show information about the
specified interface (e.g. lan0). If this parameter is not specified or empty, the command will output information
about all interfaces.
Examples
# nicinfo
# nicinfo -s
=lan0
!lan1/1
=lan2
=lan3
(shows configuration state for all interfaces, in this case there is a pending change for lan1)
# nicinfo -c lan0
Please wait ...
Current state of lan0:
Status of physical interface lan0 is 100FDX LINK_CHECK=ON
(shows the link state of lan0 - 100Mbit/s Full Duplex - and whether it is monitored or not)
Purpose
The "nicmgr" command allows to add unconfigured physical network interfaces to the network configuration
in order to be able to assign virtual network interfaces to them. This is necessary whenever new network
interface cards are added to an existing system, for example by inserting a new LNE module into a device.
It is also possible to remove network interfaces from the configuration with nicmgr, if those physical network
interfaces have been permanently removed from the system.
or
or
or
# nicmgr autoassign
or
# nicmgr autoreplace
The FREE_IF parameter represents an unconfigured/uninitialized network interface. These interfaces are named
ethX (X is a running number which is assigned at startup or directly after a network expansion module has
been inserted into the system). When a LANTIME Network Expansion (LNE) card is added to the system, the
four new interfaces will be named "eth0, eth1, eth2 and eth3. As soon as they have been correctly added to the
configuration, they will be renamed lanX (where X is also a number that has been assigned by the user or the
system). The first physical network interface is always located on the management CPU module and is named
"lan0".
IFNUMBER is the number of an already added (configured) port, therefore IFNUMBER=1 refers to the phys-
ical interface lan1, a "5" means lan5 and so on.
The two commands "autoassign" and "autoreplace" simplify the addition or the replacement of multiple ports.
"autoassign" automatically adds all detected and currently unconfigured network interfaces to the configuration.
The "autoreplace" command searches for configured but missing interfaces (e.g. if a LNE card has been removed
due to a failure, its interfaces are still in the configuration but they are missing). If it finds missing interfaces and
unconfigured interfaces, it will replace the configuration of the first missing interface with the first unconfigured
interface, the second missing interface with the second unconfigured interface and so on.
Examples
# nicmgr assign eth0 7
(adds the currently unconfigured interface eth0 as lan7 to the system)
# nicmgr remove 6
(removes lan6 from the system configuration)
# nicmgr autoassign
(automatically adds all unconfigured/unassigned interfaces to the system configuration)
# nicmgr autoreplace
Purpose
netinfo displays the configuration status of logical ("virtual") network interfaces, it shows IP addresses and
the configuration state of the interface(s), i.e. if an interface state corresponds to the configured state.
-s Short Mode
This option leads to a very compact output, only indicating the current configuration state of an interface:
If an interface name is specified with the INTERFACE parameter, "nicinfo" will only show information about the
specified interface (e.g. lan0:0). If this parameter is not specified or empty, the command will output information
about all interfaces.
Examples
# netinfo
Current state of logical interfaces:
bond0:2 matches configuration (STATIC 10.99.109.11 255.255.255.0 - NONE)
lan0:0 matches configuration (DHCP - - - NONE)
lan1:1 [Virtual Interface 1] is not active and requires to be configured
bond0:3 has no configuration
# netinfo -s
=bond0:2
=lan0:0
+lan1:1
_bond0:3
# netcinfo -s -i lan0:0
=lan0:0/0
(like above, but now contains the interface number, too: /0)
In certain situations, it can be necessary to check the status of a service or manually start or stop it. Af-
ter a manual configuration file change it is often required to restart a related service to force it to apply the
changed configuration.
With the command "status all", the running state of all registered services will be listed and therefore can
be used to find out which services are available on a certain device.
This chapter describes the various CLI commands that control the system services.
Purpose
The status command shows whether a specified system service is currently running or not. It is also pos-
sible to get the status for all services.
The only parameter is the name of the service for which the running state should be shown. Specifying
"all" instead of a certain service name will result in showing the state of all services.
Examples
# status ssh
(shows whether the SSH service is currently running or not)
# status all
(lists the state of all system services)
Purpose
With this command, a specified system service can be started if it is not already running.
The service parameter specifies which service should be started. The system first checks whether the ser-
vice is already running or not. If it is, nothing will happen. You can check the running state of a service with
the status command.
Examples
# start ssh
(starts the SSH service if it is not already running)
# start http
(starts the HTTP service)
Purpose
The stop command will stop a specified system service, i.e. the relevant processes are terminated.
With the service parameter you can specify which service should be stopped. The system first checks whether
the service is currently running or not. It will only try to stop the service if it is running, otherwise nothing
will happen. The system stops a network related service automatically if it has been disabled on all interfaces.
Stopping such a service will immediately result in terminating any active connections and disables connectivity
on all interfaces.
Examples
# stop ssh
(stops the SSH service if it is running - ATTENTION: this will immediately terminate any active SSH connec-
tion, including the one that you used to enter this command)
# stop https
(stops the HTTPS service)
Purpose
The restart command stops a service (if it is running) and then restarts it. If it was not running when the
restart command has been called, it is started normally (omitting the "stop" command).
service specifies which service should be restarted. The system first checks whether the service is already
running or not. If it is, it will stop the service and then restart it. A non-running service will simply be started.
Examples
# restart ssh
(restarts the SSH service, active connections are terminated)
# restart http
(restarts the HTTP service)
Purpose
The reload command forces a service to reload its configuration, for most services this is achieved by restarting
them. See "restart" command, but "reload" automatically chooses the applicable way for each service.
The service parameter specifies for which service the configuration should be reloaded.
Examples
# reload ssh
(reloads the SSH service configuration by restarting it)
# reload http
(reloads the HTTP service configuration by restarting it)
9.2.3.33 svcconfig - Check for System Service Configuration Changes and Apply them
Purpose
The svcconfig command will check for all services if one of the registered configuration files changed (since
the last start of the service). If such a change is detected, the corresponding service is forced to reload its
configuration (with the reload command). A list of all registered configuration changes can be found in the
/var/run/services/svccfg.db file. This file can be inspected by using the cat command.
This command does not support any parameters. It will always check all registered files for all services.
Examples
# svcconfig
(checks all registered configuration files for all services and, if a file change has been detected, reloads the
corresponding service)
This information can be requested by using one of the two commands "show" and "monitor". While "show"
will display the current status and then returns to the command prompt, "monitor" will keep running and updates
its output in a fixed time interval. In order to return to the command prompt, "monitor" has to be stopped by
pressing CTRL+C.
After the "show" or "monitor" command word it is necessary to specify which type of information should be
displayed. The different types of information are provided by so-called plugins, each of them generating a
specific type of status information. The "ip" plugin for example can generate and output a list of all IP addresses
currently used by the system. In order to get this information, the user either has to enter the command "show
ip" (will generate and show a list of all IP addresses and then returns to the command prompt) or "monitor ip"
(the IP address list is shown and will for example be updated every 10 seconds until CTRL+C is pressed to
stop the monitor command).
The following sections will explain the available plugins and, if necessary, their additional parameters.
Purpose
The "cpuload" module shows the current CPU utilization metrics of the system.
or
# monitor cpuload
This command does not have any additional parameters. The following output line will be generated once
(using the "show" command) or every 5 seconds (using the "monitor" command):
Tue Jan 21 12:52:26 UTC 2014 Cpu(s): 3.0%us, 4.8%sy, 0.0%ni, 92.1%id,
0.0%wa, 0.0%hi, 0.1%si, 0.0%st Loadavg: 0.36 0.21 0.19 1/80 12803
"Tue Jan 21 12:52:26 UTC 2014" is the current date/time, "Cpu(s): 3.0%us, 4.8%sy, 0.0%ni, 92.1%id, 0.0%wa,
0.0%hi, 0.1%si, 0.0%st" indicates the CPU utilization for each CPU state (us=User, sy=System, ni=nice, wa=I/O
wait, hi=Hardware IRQ, si=Software IRQ, st=Steal Time), "Loadavg: 0.36 0.21 0.19" represents the load average
values for the last 1, 5 and 10 minutes and "1/80 12803" shows the number of currently running/total processes
and the last assigned process ID.
Examples
# show cpuload
(shows the current CPU utilization)
# monitor cpuload
(continously shows the CPU utilization every 5 seconds)
# sc
(shortcut for "show cpuload")
# mc
(shortcut for "monitor cpuload")
Purpose
The "devices" module shows the system details and a list of detected Meinberg hardware components.
or
# monitor devices
This command does not have any additional parameters. The following output line will be generated once
(using the "show" command) or every 10 seconds (using the "monitor" command):
System Details
System ID: M200
Backplane: P
CPU Carrier: V33
Platform: AMDCONGA
CPU Board: E900
CPU ID: CPU=AuthenticAMD CPUID=AuthenticAMD MODELID=...
RAM: 100868 kB
System Components
Bus/Id Device Product Ver Serial Status
USB 001/005: 1938:0101 Meinberg CPC - Control Panel Controller 1.12 1.0.0
0x0001
Examples
# show devices
(shows the system details and the list of detected Meinberg components)
# monitor devices
(continously repeats the "show devices" command until CTRL+C has been pressed)
# sd
(shortcut for "show devices")
# mc
(shortcut for "monitor devices")
Purpose
The "ip" plugin generates a list of all currently active IP addresses.
or
# monitor ip [Filter]
The "[Filter]" parameter is optional and allows to filter the output of "show ip" or "monitor ip" using a search
keyword.
In the "monitor" mode, the list of IP addresses is automatically refreshed every 10 seconds, until CTRL+C
has been pressed.
The output of "show ip" / "monitor ip" looks like this (example):
The first column represents the interface name, which is composed from the name of the physical port (e.g.
"lan0" for the first Ethernet port or "bond2" for an interface that is part of the bonding group 3) and the ID of the
logical ("virtual") network interface. This can be either the interface number (":0" for the first virtual interface)
or the VLAN ID (".120" for VLAN ID 120) .
The second column lists the type of the address, this can be "static" for manually configured static IP addresses,
"dhcp" for IP addresses automatically assigned by DHCP/DHCPv6, "linklocal" for IPv6 Linklocal addresses or
"ra" for IPv6 addresses assigned by a router advertiser.
Whether an IP address entry is an IPv4 or IPv6 address is specified in the third column.
The fourth and last column finally shows the IP address and either the netmask (for IPv4) or the prefix length
(for IPv6).
Examples
# show ip
(shows the current list of all active IP addresses)
# monitor ip
(like "show ip", but automatically refreshes every 10s)
# show ip lan0
(shows all IP addresses assigned to the physical port "lan0")
# show ip ipv6
(shows only the IPv6 addresses)
# show ip dhcp
# monitor ip bond
(lists all IP addresses assigned to one of the bonding interfaces and refreshes automatically every 10s)
Purpose
This "show" plugin lists the entries of the LANTIME log file (/var/log/lantime_messages), a file that only
contains the most important events.
or
In the "monitor" mode, only the most recent protocol entries are shown, afterwards the command will wait
for new entries and prints them as soon as they are created. The CTRL+C key combination aborts waiting for
new events and returns to the command prompt.
If a Filter parameter has been added, only those lines in the log file will be printed that contain the given filter
string (this is not case sensitive). If no filter is specified, all entries will be listed.
# show lantimelog
2014-11-20 13:26:55 UTC: LANTIME -> OSCILLATOR ADJUSTED [Refclock: 1 ]
2014-11-20 13:26:07 UTC: LANTIME -> NORMAL OPERATION
2014-11-20 13:26:03 UTC: LANTIME -> NETWORK LINK UP [Affected LAN
Interface: 1 ]
2014-11-20 13:25:57 UTC: LANTIME -> NTP RESTART
2014-11-20 13:25:57 UTC: LANTIME -> NTP SYNC TO GPS
#
Examples
# show lantimelog
(shows the full LANTIME protocol file )
# monitor lantimelog
(lists the last 20 entries and then waits for new entries, cancel waiting with CTRL+C)
# s la
(short form of "show lantimelog")
# m la
(short form of "monitor lantimelog")
Purpose
The "linkstate" plugin shows the current network connection state of one or more physical network interfaces.
or
The "[Filter]" parameter is optional and can be specified to limit the output to only those network interfaces
containing the filter string either in their name or MAC address.
The "monitor" mode automatically refreshes the output every 10 seconds until CTRL+C has been pressed.
The first column contains the name of the interface, e.g. "lan0" for the first physical port.
The second column represents the MAC address of the interface and the third column indicates the current
connection state. This can be either "NO_LINK", if no active connection could be established, or it shows the
current connection speed (10, 100, 1000 or 10000) in MBit/s plus the duplex mode (FDX for full duplex or HDX
for half duplex).
Examples
# show linkstate
(shows the connection state of all physical network interfaces)
# monitor linkstate
(like "show linkstate", but refreshing the output every 10s until CTRL+C has been pressed)
# s li
(short form of "show linkstate")
# m li
(short form of "monitor linkstate")
Purpose
This "modules" plugin shows a list of all loaded kernel modules and drivers. If you want to show all de-
tected hardware modules and components in your system, please check out the "show devices" command.
or
# monitor modules
This command does not have any additional parameters. The following output line will be generated once
(using the "show" command) or every 10 seconds (using the "monitor" command):
Examples
# show modules
(shows all currently loaded kernel modules)
# monitor modules
(continously repeats the "show modules" command until CTRL+C has been pressed)
# sm
(shortcut for "show modules")
# mm
(shortcut for "monitor modules")
Purpose
This command shows an overview of the currently active network configuration, including the assigned IP
addresses, the link state of the physical network interfaces and, if appropriate, the state of bonding groups.
This command does not have any additional parameters. The following output line will be generated:
Examples
# show network
(shows the currently active network configuration)
# sn
(shortcut for "show network")
Purpose
The "show processes" command generates a list of all processes currently running on the system. In com-
bination with a filter string it is possible to check if a certain command or software component has been started
and is still running.
or
The "[Filter]" parameter is optional and allows to filter the output of "show processes" or "monitor processes"
using a search keyword (case insensitive). The filter string can contain either a part of a command name or a
process ID.
In the "monitor" mode, the list of processes is automatically refreshed every second until CTRL+C is pressed.
The output of "show processes" / "monitor processes" looks like this (example):
The first column represents the process ID and the second column contains the terminal name (TTY), which
can be "?" for internal processes not bound to a specific terminal.
In the fourth column the cumulative CPU time used by this process and - after that - the command itself,
typically with its parameters, is listed.
Examples
# show processes
(shows the current list of all processes currently running on the system)
# monitor processes
(like "show ip", but automatically refreshes every second)
# sp
(short form of "show processes")
# m p ntp
(short form of "monitor processes ntp")
Purpose
The "route" plugin show all currently active IP routes and routing rules.
The "[Filter]" parameter is optional and allows to filter the output of "show route" or "monitor route" using a
search keyword. This can be used to limit the output to only those entries that contain the specified search
term.
In the "monitor" mode, the routing entry list is automatically refreshed every 10 seconds, until CTRL+C has
been pressed.
The output of "show route" / "monitor route" looks like this (example):
Routing Rules:
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
Examples
# show route
(shows the current list of all active IP network routes)
# monitor route
(like "show route", but automatically refreshes every 10s)
# sr
(short form of "show route")
# mr
(short form of "monitor route")
Purpose
This "show" plugin lists the entries of the system log file (/var/log/messages), a file that contains all events
and status changes.
or
In the "monitor" mode, only the most recent protocol entries are shown, afterwards the command will wait
for new entries and prints them as soon as they are created. The CTRL+C key combination aborts waiting for
new events and returns to the command prompt.
If a Filter parameter has been added, only those lines in the log file will be printed that contain the given filter
string (this is not case sensitive). If no filter is specified, all entries will be listed.
# show syslog
Dec 15 10:41:08 timeserver root: Restarting syslog due to configuration
change ...
Dec 15 10:41:08 timeserver syslog-ng[7864]: Termination requested via
signal, terminating;
Dec 15 10:41:08 timeserver syslog-ng[7864]: syslog-ng shutting down;
version=’2.0.9’
Dec 15 10:41:08 test_tr0_lt04 syslog-ng[22289]: syslog-ng starting up;
version=’2.0.9’
Dec 15 11:19:40 test_tr0_lt04 sshd[5061]: Accepted password for root from
172.16.3.120 port 41449 ssh2
Dec 15 11:19:40 test_tr0_lt04 sshd[5061]: pam_unix(sshd:session): session
opened for user root by (uid=0)
Dec 15 11:19:46 test_tr0_lt04 sshd[5061]: Received disconnect from
172.16.3.120: 11: PECL/ssh2 (http://pecl.php.net/packages/ssh2)
Dec 15 11:19:46 test_tr0_lt04 sshd[5061]: pam_unix(sshd:session): session
closed for user root
#
Examples
# show syslog
(shows the full system protocol file )
# monitor syslog
(lists the last 20 entries and then waits for new entries, cancel waiting with CTRL+C)
# ss
(short form of "show syslog")
# ms
(short form of "monitor syslog")
# m
(short form of "m s")
Purpose
The "version" module shows the firmware version of the currently running firmware image.
Examples
# show version
(shows the firmware version)
# sv
(shortcut for "show version")
Purpose
The reboot command initiates a restart of the whole system. This includes stopping all services and reset-
ting the CPU. Please note that any unsaved configuration changes are not automatically saved, therefore the
system comes back up with the last startup configuration that was saved using saveconfig.
It is possible to specify a delay, i.e. the reboot process waits for a given time before carrying out the system
restart. Such a delay can be applied in the background, allowing a user to continue to work in the foreground,
e.g. changing configuration files and applying changes. A backgrounded reboot process kan be canceled at
any time during the waiting period, allowing a user to set a reboot time before trying to change the system
configuration. If one of these changes results in the system becoming unreachable (e.g due to a network IP
address configuration error), the backgrounded reboot process will automatically restart the system after the
specified time and restores the last saved startup configuration, resulting in a restore of the network connectivity.
Once the user completed and tested all configuration changes successfully and verified that the system is still
reachable, the waiting reboot process can be canceled.
reboot notifies all logged in users in active SSH, TELNET and serial console sessions about the reboot and
the specified waiting period. This enables everyone to save any changes made and log out correctly or cancel
the restart, as long as the reboot process is still in a waiting state.
If a delay is specified, the reboot-command will wait for the given time before restarting the system. This
delay can be specified as a simple numeric value representing the number of seconds to wait. It can also be
specified in minutes or hours by using a "m" or "h" suffix to the numeric value (see examples).
In order to be able to continue to work in the same SSH/TELNET/serial console session, the reboot com-
mand can be told to wait in the background instead of blocking the shell prompt. This background mode is
enabled by adding a "&" character at the end of the command line.
A waiting reboot process can be canceled by specifying "stop" instead of a delay. This can be used to stop a
restart process that is waiting in the background but it can also be used to cancel the reboot process of another
user.
If no parameter is given, reboot will restart immediately, i.e. after the default waiting time of 2 seconds.
Examples
# reboot
(immediately restarts the system, i.e. after the 2s default waiting period)
# reboot 20
(restarts in 20 seconds)
# reboot 1h
(restarts in 1 hour)
# reboot 5m &
(restarts in 5 minutes, but waits in the background allowing the user to enter additional commands in the
meantime)
Purpose
The make_noise command allows to identify a device in a server room or rack via beep sounds and peri-
odical blinking (Alarm LED). This is useful if a device needs to be physically identified, for example in a large
server room.
The audio-visual signals can be switched off if the device has a display and front panel buttons. In that
case the display shows a note saying that the F2 button can be used to stop this mode. It is also possible to
cancel the command by pressing CTRL+C, which will also result in stopping the audio-visual identification mode.
This command does not support any parameters. It causes the device to beep every 2 seconds and switch
the red Alarm LED on and off peridocally.
Examples
# make_noise
(initiates the audio-visual identification mode, can be stopped/canceled by pressing CTRL+C or the F2 front
panel button of the device)
This file can be edited with a text editor directly in the command line of the system or can be replaced by an
external prepared file. The monitor program will check this configuration file for changes automatically after
every full scan of the configured nodes.
On earlier versions of LANTIME OS the nano text editor could be started with the command
vi [filename]
which is still available on V6 for compatibility reasons. However, this command will show a short note telling
you about the two possible editors available on V6 and then asks you to choose which one to use for editing
the file [filename] you specified on the commandline.
9.2.5.1 nano
The nano text editor is a fast, small and easy-to-use opensource program (see http://www.nano-editor.org/ for
further information). This editor has been used as the standard CLI tool for modifying text files in earlier LTOS
versions (in which it was started using the vi command).
starts nano and opens the file [filename]. If no filename is specified, nano will start with an empty file and
will ask for a filename when you use the save/close function afterwards.
Search/Replace
To find a certain search term in the current file, press CTRL+W. If you want to replace a search string, use the
CTRL+\ key combination. The nano Editor supports regular expressions as search terms.
More Functions
A number of additional editor commands and functions can be accessed with specific key combinations. A
help screen listing all of them is available with the CTRL+G command key combination.
9.2.5.2 edit
The edit text editor is a part of the Midnight Commander opensource project and is normally called mcedit (see
http://www.midnight-commander.org/ for further information). This editor has a rich feature set, a menu system
and color options (if supported by the terminal).
starts edit and opens the file [filename]. If no filename is specified, the editor will start with an empty file
and will ask for a filename when you use the save/close function afterwards.
This editor uses Function Keys to perform most program functions. If your terminal does not support send-
ing the correct key codes for the function keys or if you cannot use the function keys for some other reason,
you can emulate a function key by pressing the escape key (ESC) first, followed by the digit 1-9 (for F1 to F9)
or 0 (for F10). F10 is important as it is used to quit the editor and return to the CLI prompt.
Search/Replace
In order to search for a certain search string in the file, please press F7 (ESC+7). If a search string needs to
be replaced by another string, press F4 to open the search/replace dialogue. This function has a large number
of options which can be selected, for example the "prompt on replace" option to bring up a confirmation dialogue
before each replacement is performed or the "replace all" flag to select that multiple/all occurrences of the search
string shall be replaced.
More Functions
The mcedit Editor has a large number of functions and useful features, most of them are accessible via the on
screen menu. In order to open the menu, please press F9 (or ESC+9) and then navigate with the cursor keys
and ENTER to select a menu option or ESC to leave the menu and return to the file editor.
starts vim and opens the file [filename]. If no filename is specified, vim will start with an empty file and
requires you to specify a file name later, when you save the file.
The high-resolution VF-Display, which is used in our LANTIME M600 systems, also offers a graphical repre-
sentation of the measured input signals (NTP, PTP, IRIG, PPS ...). The graphic VF-Display is described in the
following chapter.
The illustrations of the configuration menus is reacted with a four-line graphics, the menus of the respec-
tive systems may differ in the display of it (see Figure 1.0).
M200 / M300
The main menu of the Lantime (where time and date in the selected time zone are displayed).
F1
12:00:00
UTC Thu, 01.01.2011
Choose Reference Time ↓, MRS Management, MRS Status and Setup, and eventually MRS Status. Now you
can choose whether the numerical offsets of all available input signals should be displayed or if a graphical
display program should start. If the graphical option is selected you have to choose one of the input signals as
a reference.
By pressing buttons ↑ and ↓ one can change among several reference signals and select one by pressing
the OK button. In the graphic mode one can choose among four different display options how the offset of a
given reference signal shall be displayed (online mode, full graph, statistics and scrolling mode).
The cursor position and consequently the option selection can be modified with the ↑ and ↓ buttons. In
the upper right corner one can find the selected reference source signal, which offset is graphically displayed.
With the OK or → button the selected graphical mode can be started.
Each of these modes contains an information menu accessed by F1. One can find here some current status
information as well as selection buttons and options of the current mode. With the ESC button one can always
return to the menu on the upper level.
1 Offset: an offset is a time difference between two systems. In our example, the offset is time difference between a given input signal and
an oscillator, which disciplines its local clock.
2 Input signals: GPS, PTP, PPS, NTP, TCR, FRQ- which of these input signals are available can be identified from the numerical status
(Numerical Status)
3
Each graphic mode is displayed within a range of values:
SCROLLING MODE
/var/log/loopstats
After one of the graphical menu options is selected, the current mode appears for one second on the display.
Under the current mode the origin file from which the graphic is generated appears in small fonts.
08:17 09:20
With the ↑ (zoom in) and ↓ (zoom out) buttons the range of the y-axis can be changed any time in order to
display graph larger or smaller.
Graph of Online Mode (zoomed out)
10.0us
08:17 09:20
Thus a mean value graph is generated which looks similar to this one: An example of a generated graph
with the corresponding range of values (here: FULL GRAPHIC)
10.0us
08:17 09:20
3 The display has an x and y axis: the y-axis displays the offset value, which is the higher between absolute minimum and maximum value
and is computed automatically at the first start of the menu. It is step-wisely ordered as follows: +- 1, 2, 5, 10, 20, . . . (in 30 day [d]
units – one picosecond [ps]). The x-axis is a time axis. It shows from and until when particular offset values occur.
4 The xth value is the number of available values divided with the display length.
A legend can be displayed by pressing the F2 button. It contains the value range, as well as the mini-
mum and maximum of the graphic. By pressing a F2 button for the second time the legend disappears.
+5.000us
max:+3.999us
min:-3.000us
-5.000us
09:20
The help menu appears by pressing the F1- information button in the “FULL GRAPHIC MODE”. It shows all
available options in this mode. Other options are only partially available from here. To end this function one
has to press ESC-, OK- or again the F2- button.
In the “FULL GRAPHIC MODE” the graph can be maximized or minimized with ↑ (zoom in) and ↓ (zoom
out) buttons. If the legend is currently displayed, selecting the zoom-buttons causes that the range of y-axis
gets automatically adjusted and the legend renewed. With the ESC-button one can get back to the main menu
of the graphical program where the legend is not displayed. Alternatively, a display returns back to a “FULL
GRAPHIC MODE” with a default value range.
The „Statistic“ - option comes next in the graphic menu. When you select it, you can decide if the mini-
mum or the maximum value of the current statistics file shall be displayed or not.
The minimum or the maximum values are plotted in the middle of a display, as long as at least 128 values
(a half of the display length) are available. A legend is shown on the display at the same time and apart of the
minimum or maximum value also the corresponding UTC time is displayed 5 .
Minimum: -25.000 us
UTC: 09.04.2010 01:14:59 Uhr
Maximum: -25.000 us
UTC: 09.04.2010 01:14:59 Uhr
When the ← button is selected the displayed graph moves half of a display to the left if the „SCROLLING
MODE“ has not been stopped beforehand. Even here the value range of the y-axis can be changed or the graph
can be shifted a few more steps to the left. In order to continue the scrolling mode one has to press the OK or
→ button. If you select the ESC button then you come back to the main menu of the graphical program.
With an integrated time code receiver it might be possible, that the message "NO DATA" appears on the
display - in this case the correct value can be set in the time-code parameter submenu.
Current time and date of the timeserver with the name of the time zone (NTP uses UTC time zone) will be
monitored in the bottom line. If the "SIMULATION MODE" option is enabled an "*" will be shown behind the time.
The multicolor LEDs will reflect the current state of the device:
„Ref. Time“
green: the reference clock produce valid time.
red: the reference clock produce no valid time (e.g. not synchronized)
„Time Service“
green: NTP has been synchronized to reference clock.
red: NTP is not synchronous to reference clock or sync to „local clock“
„Network“
green: all watched network ports has been “link up“ detected
red: at least one of the watched network ports (look at „Setup Device
Parameter / Check Network Linkup“) is not connected
„Alarm“
off: no error at moment
red: general error – more information will be shown on display.
If the symbol „F1“ will be shown in the upper right corner a help page can be displayed when pressing
the „F1“ button. When pressing „F1“ from main menu a short description for menu navigation will be displayed:
Use and to
select different
main menus. Use
and to enter.
When pressing the „OK“ button from main menu the version of the LANTIME software, the NTP and the LINUX
kernel version will be displayed.
ELX800 VX.XXx
SN: 000000000000
NTP: [email protected]
Krn.: X.X.XX.X
The following main menus will be displayed when pressing the arrow buttons:
NORMAL MODE
NTP: Offs. 1ms
Wed, dd.mm.yyyy
UTC 12:00:00
OK OK OK OK
->Setup MRS <- ->external NTP<- ->Interfaces <- ->Time Zone <-
Info REFCLK Local Strat. Global Cfg. Restart Menu
Setup REFCLK Restart NTP Services Factory Reset
Set Outputs PTP IEEE1588
YES YES
MRS
Select Setup
Clock >Set MRS & Info< MRS
IRIG Receiver
The Reference Clock menu and all its sub menus will manage all status information and parameters of the
reference clock. To enter the following sub menus press the "OK" button.
Ref. Time 1
->Switch Unit <-
Ref. Time 2
OK
OK OK OK
With this menue you can check all important status information about the switch card unit. The example above
shows a perfect mode of operation. Both power supplies (PSU1, PSU2) are connected - the two receivers are
working in "normal operation mode" (CLK1, CLK2). If the second clock is not connected or in free running mode,
the display shows "CLK2:0". If there is no power connected on PSU1, you can see the status "PSU1:0" on the
display of the LANTIME.
With the submenue SCU Cntl you can configure the following parameters:
REMOTE: disabled/enabled
disable or enable remote control of the SCU
OUTPUTS: enabled/disabled
disable or enable outputs of the SCU
MRS
> MRS Status < MRS Status MRS Status MRS Status
Priorities > Priorities < Priorities Priorities
Fix Offsets Fix Offsets > Fix Offsets < Fix Offsets
Precisions Precisions Precisions > Precisions <
OK OK OK OK
With the OK and arrow buttons you can choose the current status of the MRS. All possible reference clocks
will be shown with the number of priority, the name of the reference clock and the current offset to the inter-
nal reference clock (OCXO). The current master will be signed with an “*” behind the name of the reference clock.
In the next menu the user can define in which order the references will be used to control the internal os-
cillator. The reference clock with the highest priority will be used always if this is available.
The "Fixed Offsets" can be set up in the next sub menu, if you know the constant offset (bias) of an exter-
nal reference source. By default this value is 0 ns. The bias of the internal GPS receiver can not be set up –
indirectly this can be done via the antenna cable length.
This precision value will determine the hold over time when switching to the next reference clock if the current
master is not available anymore. If the precision is 0 the next reference clock will be switched at once. If the
precision value is greater then 0 the time for switching to the next reference (hold over time) will be calculated
by the following formula:
Example:
The GPS receiver with an precision of 10ns is the current master. If this master is no longer available it will
switch to the next reference source of the priority order – in this case the PPS input with a precision of 100us.
With the formula ((100ns/10ns)*11.4) we get hold over time of 114 seconds/1.9 min. The online display of the
MRS status will show the remaining time and the calculated time. The hold over time will be recalculated if
the status of the reference clocks will change.
GNSS Refclock:
Galileo / BeiDou / GPS / GLONASS
IRIG
PZF MSF, WWVB, JJY ...
Setup MRS ->Info PZF <- ->Status <- -> Info TCR <-
->Info GNSS <- Setup PZF Version Setup TCR
Setup GNSS Serial Outputs Tran. Distance
Set Outputs
OK OK OK OK
>CLK Status < >Status & Version< ->Status <- ->Version Info <-
CLK Version Corr. & Field Version Recv. State
CLK Position Trans.Distance
CLK Satellites
In this menu all relevant information about the reference clock, the internal oscillator and in case of a GNSS
receiver, the visible and good satellites will be shown in the display.
Receiver Pos.
LAT: 51°58’57”N
LON: 09°13’32”E
ALT: 176 m
Receiver Pos.
X: 3885662 m
y: 631131 m
z: 5001761 m
PZF
>Status & Version< Status & Version
Corr. & Field >Corr. & Field <
OK OK
PZF STATE
CORR.:
1 State:check
FIELD:94
PZF STATE
CORR.:
97 State:fine
FIELD:94
OK OK OK
This first menu will monitor the current state („sync“ or „not sync“). The next line will reflect the firmware
version, the serial number of the internal GPS and the type of the integrated oscillator.
OK OK
Invalid UTC parameter: This bit is set to one if the checksum of the ‘Offset from UTC’ parameter, which must
be used if no IEEE1344 extensions are available, is invalid. User must enter new ‘Offset from UTC’ data to
clear this bit. Please note that the IRIG-receiver never leaves freewheeling mode if IEEE1344 is disabled and
the UTC-Parameter are invalid!
TCAP exceeded, jitter out of range: If the jitter between two consecutive IRIG-telegrams exceeds +/- 100us
the receiver switches into freewheeling mode and the ‘TCAP exceeded’ Bit is set. ‘TCAP exceeded’ is cleared
if the measured jitter is below +/- 100us.
Lock on: ‘Lock On’ is set whenever the receiver is in synchronous mode and the internal oscillator correc-
tion value has settled.
Telegram error: This bit is set if the consistency check of two consecutive IRIG-telegrams fails. The IRIG-
receiver switches into free wheling mode if ‘telegram error’ is set.
Data available: ‘data available’ is set if the receiver can read the timecode.
Invalid sysconf: If ‘invalid sysconf’ is set the checksum of the system configuration data is invalid. In this
case the default mode ‘IEEE1344 disabled’ is selected. User must cycle the system or enter a new system
configuration in the IRIG-parameter menu.
Pulses enabled: The pulse per second (PPS) signal which increases the NTP’s accuracy is turned when
‘lock on’ is set the first time. The ‘pulses enabled’ bit is set if the PPS signal is enabled.
Setup MRS
>Antenna Length<
Info REFCLK OK Simulation Mode
->Setup REFCLK<-
Init CLK
Set Outputs
PZF
Status Setup:
Version OK Receiver Position
->Tran. Distance<- Tran. Distance
1200km
IRIG
Info TCR ->UTC Offset <-
-> Setup TCR <- OK IRIG Code
Initial Time
Ignore Lock
In the Reference Time -> Setup Clock menu the receiver clock parameters can be configure. The antenna cable
length of satellite based receivers must be entered here. The GPS and GLONASS reference clocks can be run
in simulation mode.
Meinbergs PZF correlation receivers can be operate in simulation mode as well. In addition to that, the
distance to the transmitter must be set in the setup menu.
For our long wave receivers (WWVB, MSF, JJY ...) there is only the setting for "Transmitter Distance" available
- in the Submenu Reference Time -> Info Refclock. The setup for our IRIG time code receivers includes the
settings for the UTC offset and the corresponding time code. The time code receiver can also operate in simu-
lation mode with IGNORE LOCK. With Initial Time and Init Clock (GPS, GLONASS), the time and date for
the simulation mode is set.
Setup MRS
Info GNS
->Setup GNS <-
Set Outputs
OK
OK OK F2
OK OK F2
OK OK
When the antenna is disconnected it is possible to set the system with any time. Note that the NTP will
not synchronize to GNSS 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.
OK OK
Enable Outputs:
The submenu Output Options -> Enable Outputs lets the user configure at which time after power up the serial
ports and pulse/frequency outputs 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 incoming signals and has checked or corrected its on-board clock. The default setting
for all outputs is ’if Sync’.
Time Zone:
See Chapter "Set Time Zone of Serial Outputs".
COM0 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.
This topic is used to select one of several different 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.
• Meinberg Standard
• SAT
• NMEA RMC (Rev. 2.2)
• Uni Erlangen
• Computime
• Sysplex 1
• Meinberg Capture
• SPA
• RACAL
• Meinberg GPS
• NMEA GGA (Rev. 2.2)
• NMEA RMC GGA (Rev. 2.2)
• NMEA ZDA (Rev. 2.2)
• ION
• 6021
• IRIG-J
The menu Set Timezone lets the user enter the names of the local time zone with daylight saving disabled
and enabled, together with the zones time offsets from UTC. These parameters are used to convert UTC to local
time, e.g. CET = UTC + 1h and CEST = UTC + 2h for central Europe. The values of daylight saving are
configurable using the Time Zone setup menu.
OK OK OK
Beginning and ending of daylight saving may either be defined by exact dates for a single year or using an
algorithm which allows the receiver to re-compute the effective dates year by year.The figure show how to enter
parameters for the automatic mode. If the number of the year is displayed as wildcards ’****’, a day-of-week
must be specified. Then, starting from the configured date, daylight saving changes the first day which matches
the configured day-of-week. In the figure October 25th is a Saturday, so the next Sunday is October 26th.
All changeover rules for the daylight saving like "the first/the second/the second to last/the last Sunday/-
Monday etc. in the x-th month," can be described by the used format "first specified day-of-week after a defined
date".
If the number of the year is not displayed as wildcards the complete date exactly determines the day daylight
saving has to change, so the day-of-week does not need to be specified.
If no changeover in daylight saving is wanted, identical dates and times must be entered in both of the submenus
(DAYLIGHT SAV ON/OFF). After this a restart should be done.
This menu lets the user select the Timecodes to be generated by internal reference clock. 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".
• IRIG B002+B122
• IRIG B006+B126
• IRIG B007+B127
• AFNOR NF S87-500
• C37.M8
• IEEE1344
OK
Pulse Outputs
Out1:Pulse Per S
Out2:Pulse Per S
Out3:Pulse Per S
OK
OK OK
As already mentioned, the outputs home position is selected by "active: high or low".
For example: a cycle time of 1 hour 45 minutes would cause a pulse every 6300 seconds (starting from 0
o’clock). The appearing distance between the last pulse of a day and the first pulse of the next day (0:00:00
o’clock) would be only 4500 sec. The value in entry field "Cycle" turns red, when entering a time that causes
this asymmetry.
DCF77 Marks
In "DCF77 Marks" mode the selected output simulates the telegram as transmitted by german time code trans-
mitter DCF77. 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 deactivat-
ing the DCF-Simulation with the "Timeout" value. DCF Simulation is never suspended, if the delay value is zero.
Idle Mode
Selecting "Idle" deactivates the output.
Holdover
If "enabled" is selected the operation of the output remains. Otherwise ("disabled") the operation of the output
will be switched off when synchronization is lost.
Synthesizer
Setup Pulses OK Frequency:
->Setup Synth. <- 0000 Hz
Phase: 000.0°
This setup menu lets the user edit the frequency and phase to be generated by the on-board synthesizer. Fre-
quencies 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 frequency´s units string. If the least
significant 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◦ to +360◦
with a resolution of 0.1◦ . Increasing the phase lets the signal come out later. Phase affects 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.
Ref. Time
->Time Service<-
Network
System
OK
YES
->NTP Settings<- OK
2nd Receiver
PTP IEEE1588
12
The internal reference clock always has priority over the external NTP servers. If the internal reference clock
is not synchronized or has failed, the NTP will automatically switch to an external NTP server. With this menu
item some external NTP server can be configured.
12
NTP Settings
2nd Receiver
->PTP IEEE1588<-
OK
The menu for PTP IEEE 1588 configuration is located in the "Time Service" main menu. A device with more
than one PTPv2 cards (also called TSU - Time Stamp Units) lists all cards in the sub menu which follows.
With ↓ and ↑ buttons one can select among different PTP cards available in the system. A slot number, MAC
address and the current state of the selected TSU will be displayed.
The page "TSU Info" gives an overview of the state of the most important PTP parameters from the time
stamp unit which is connected to the PTP0 interface. The appearance of this page is depending on the mode
of the PTP engine. There are different states of a TSU possible. For example, if the unit is configured as a
PTP Grandmaster clock, then this page shows the "Master" state. On the other hand in MRS (Multi Reference
Source) devices, the PTP mode "Slave" is displayed here.
uninitialized: The port is booting up, the software daemon has not yet started, the IP address is not yet
assigned.
initializing: In this state the port initializes its data sets, hardware, and communication facilities.
disabled: PTP service has been disabled on this port, either by user configuration or because the
module is in a standby mode.
listening: The port is waiting for the announceReceiptTimeout to expire or to receive an Announce
message from a master.
passive: The port is in passive mode, meaning there is another master clock active in the PTP domain.
The port can enter master state when it wins the BMCA (Best Master Clock Algorithm) due to
a failure/service degradation of the current master.
uncalibrated: One or more master ports have been detected in the same domain. The TSU is waiting to
calculate the path delay to a Grandmaster.
slave: The port has successfully subscribed to a master and receives all expected messages. It also
successfully measured the path delay using delay request messages.
"Slave" state: they show the offset to the Grandmaster and the mean network delay between the master and a
slave.
Link: status 0: The queried port is down, check the link LED. If faulty, replace the network card.
status 1: The port of interest is in normal operation.
P2P (Peer-to-peer): where each device (a peer) in the network exchanges peer-delay
measurement messages. This way each device can keep track of the delays between itself
and its immediately connected neighbors. P2P mechanism can be used in 1588 PTP-capable
networks only.
UDP-UDP/IPv4 (Layer 3): User Data Protocol one of the main protocols used for the Internet.
OK
OK OK OK
The Set Dbg Level menu is for maintenance and debugging purposes only, therefore leave it unchanged unless
advised by a technician. The Level of debugging can be increased from 0 (default) to 3 with additional data
being logged at each increased debugging level.
Set temp Offs is an offset value set temporarily, mainly for a debugging purpose. With the next warm boot the
value is set back to 0.
Enable Stats option is also mainly for debugging. Per default it is disabled.
Multicast Slave
Multicast Auto
Unicast Master
Unicast Slave
The number of different PTP operation modes depends on the feature set of the purchased unit.
Custom
Telecom Profile
Power Profile
P2P Dflt Profile
Note: Whenever a PTP preset is selected, all previously saved PTP parameters will be overwritten!
———————————————————–
In Unicast or Multicast Master / Slave Mode:
———————————————————–
SMPTE ST 2059-2
-Ann Msg. Rate: 4/sec
-Sync Msg. Rate: 8/sec
-Del Req Rate: 8/sec
-Priority 1: 128
-Priority 2: 128
-Delay Mech: "E2E" or "P2P"
Custom Profile
By selecting "Custom" settings all parameters are ready for editing.
MULTICAST MASTER
UNICAST MASTER
MULTICAST SLAVE
OK OK OK
UNICAST SLAVE
OK OK OK
PTPv2 Domain
Number: 0
In Multicast mode all PTP messages will be sent as Multicast packets where receiving nodes (slave clocks)
do not require to know the identity of the time sources in the network. The selection of the active time source
(the Grandmaster) follows the so-called "Best Master Clock Algorithm" a mechanism that all participating PTP
masters must follow. The multicast communication model requires a minimized configuration of all participating
nodes and this advantage is beneficial in smaller networks. In larger newtorks it is considered inefficient as
the content of message is forwarded to all nodes, requiring them to spend network bandwidth and CPU resources.
Priority1: The attribute is used in the execution of the best master clock algorithm (BMCA).
Lower values take precedence.
The operation of the BMCA selects clocks from a set with a lower value of priority1
over clocks from a set with a greater value of priority1.
Priority2: The attribute is used in the execution of the BMCA. Lower values take precedence.
In the event that the operation of the BMCA fails to order the clocks based on the
values of priority1, clockClass, clockAccuracy, and scaledOffsetLogVariance, the
priority2 attribute allows the creation of up to 256 priorities to be evaluated before
the tiebreaker. The tiebreaker is based on the clockIdentity. The values clockClass,
clockAccuracy, and scaledOffsetLogVariance depend on the internal state of the
grandmaster and cannot be configured.
PTPv2 Domain: A PTP domain is a logical group of PTP devices within a physical network that belong to
the same domain number. Slave devices that shall sync to a certain master within a network
must have configured a unique domain number which is the same on the master.
One Step approach: the SYNC message itself is time stamped on- the- fly just before it leaves
the network port. Therefore, not FOLLOW-UP message is needed.
Management Msg: A protocol within PTP used to query and update the PTP data sets maintained by master
clocks. These messages are also used to customize a PTP system and for initialization and
fault management. Management messages are used between management nodes and clocks.
Per default are enabled.
P2P (Peer-to-peer): where each device (a peer) in the network exchanges peer-delay
measurement messages. This way each device can keep track of the delays between itself
and its immediately connected neighbors. P2P mechanism can be used in 1588 PTP-capable
networks only.
UDP-UDP/IPv4/IPv6 (Layer 3): User Data Protocol one of the main protocols used for the Internet.
Msg. Intervals: specify the settings for the PTP timing messages.
Anno. Intv specifies the time for sending announce messages between masters to select the
Grand Master. Available settings are: 16/s, 8/s, 4/s ... 2s, 4s, 8s, 16s with a default value 2
seconds.
Sync. Intv specifies the time for sending sync messages from a master to a slave. Available
settings are: 128/s, 64/s ... 64s, 128s, with a default value 1 second.
Requ. Intv specifies an interval how often delay request messages are sent from a slave to
the master. Delay request messages intervals 128/s, 64/s,... 64s, 128s, with a default
value 2 seconds.
Ann. Recei value specifies the time for announce receipt timeout messages which is 2-10
times the Announce interval, with a default of 3. This is the time for a BMCA to determine
a Grand master.
When one or more masters have been identified the slave can use Unicast Negotiation to get Announce and
Sync messages sent from the master, and to get Delay Requests answered with Delay Responses.
The PTP message sequences between the master and a slave are repeated until the duration of a negoti-
ated interval expires. For example a slave might ask for 4 Sync messages per second, for a period of 60 seconds.
In this case after 60 seconds the master would stop sending Sync messages until another Sync message contract
was negotiated.
If unicast mode is selected then an additional sub menu will appear to configure or display unicast spe-
cific parameters.
Priority1: The attribute is used in the execution of the best master clock algorithm (BMCA).
Lower values take precedence.
The operation of the BMCA selects clocks from a set with a lower value of priority1
over clocks from a set with a greater value of priority1.
Priority2: The attribute is used in the execution of the BMCA. Lower values take precedence.
In the event that the operation of the BMCA fails to order the clocks based on the
values of priority1, clockClass, clockAccuracy, and scaledOffsetLogVariance, the
priority2 attribute allows the creation of up to 256 priorities to be evaluated before
the tiebreaker. The tiebreaker is based on the clockIdentity. The values clockClass,
clockAccuracy, and scaledOffsetLogVariance depend on the internal state of the
grandmaster and cannot be configured.
PTPv2 Domain: A PTP domain is a logical group of PTP devices within a physical network that belong
to the same domain number. Slave devices that shall sync to a certain master within a
network must have configured a unique domain number which is the same on the master.
One / Two Step: Two Step approach: The PTP protocol requires the master to periodically send SYNC messages
to the slave devices. The hardware time stamping approach of PTP requires that the master
records the exact time when such a SYNC packet is going on the network wire and needs to
communicate this time stamp to the slaves. This can be achieved by sending this time stamp
in a separate packet (a so-called FOLLOW-UP message).
One Step approach: the SYNC message itself is time stamped on- the- fly just before it leaves
the network port. Therefore, not FOLLOW-UP message is needed.
Management Msg: A protocol within PTP used to query and update the PTP data sets maintained by
master clocks. These messages are also used to customize a PTP system and for
initialization and fault management. Management messages are used between management
nodes and clocks.
NetPr: in unicast mode only one option for the network protocol possible:
UDP-UDP / IPv4 / IPv6 (Layer 3): User Data Protocol is one of the main protocols
used for the Internet.
Msg. Intervals: specify the settings for the PTP timing messages.
Anno. Intv specifies the time for sending announce messages between masters to
select the Grand Master. Available settings are: 16/s, 8/s, 4/s ... 2s, 4s, 8s, 16s with
a default value 2 seconds.
Sync. Intv specifies the time for sending sync messages from a master to a slave.
Available settings are: 128/s, 64/s ... 64s, 128s, with a default value 1 second.
Requ. Intv specifies an interval how often delay request messages are sent from a slave to
the master. Delay request messages intervals 128/s, 64/s,... 64s, 128s, with a default
value 2 seconds.
Ann. Recei value specifies the time for announce receipt timeout messages which is 2-10
times the Announce interval, with a default of 3. This is the time for a BMCA to determine
a Grand master.
OK OK OK
Asym: or Default Asymmetry is an initial calibration value (in ns) and can be entered here
if a certain asymmetry offset in the network path is known before the PTP unit starts.
This occurs in SDH networks for example.
Max.Path Delay: If a measured path delay exceeds the value of this parameter (in ns), then the PTP unit
is able to detect a change in the asymmetry offset and can take this into account for
its delay measurements.
Note: Keep defaults settings here (0 ns for both parameters) unless some problems with the
client synchronization accuracy are observed and only if the asymmetry offset can be
measured beforehand.
PTPv2 Domain: A PTP domain is a logical group of PTP devices within a physical network that belong to
the same domain number. Slave devices that shall sync to a certain master within a network
must have configured a unique domain number which is the same on the master.
P2P (Peer-to-peer): where each device (a peer) in the network exchanges peer-delay
measurement messages. This way each device can keep track of the delays between itself
and its immediately connected neighbors (for example a switch or a router). P2P mechanism
can be used in 1588 PTP capable networks only.
UDP-UDP/IPv4/IPv6 (Layer 3): User Data Protocol one of the main protocols used for the Internet.
Msg. Intervals: specify the settings for the PTP timing messages.
Anno. Intv specifies the time for sending announce messages between masters to select the
Grand Master. Available settings are: 16/s, 8/s, 4/s ... 2s, 4s, 8s, 16s with a default value 2
seconds.
Sync. Intv specifies the time for sending sync messages from a master to a slave. Available
settings are: 128/s, 64/s ... 64s, 128s, with a default value 1 second.
Requ. Intv specifies an interval how often delay request messages are sent from a slave to
the master. Delay request messages intervals 128/s, 64/s,... 64s, 128s, with a default
value 2 seconds.
Ann. Recei value specifies the time for announce receipt timeout messages which is 2-10
times the Announce interval, with a default of 3. This is the time for a BMCA to determine a
Grand master.
HQ Filter: In heavy loaded networks when using non-PTP compliant switches, the "HQ Filter" can be
activated to reduce the jitter. Detailed information about the usage and the configuration
of the HQ filter can be found in the "PTPv2 Configuration Guide" in chapter PTP Option.
The Default setting is with HQ Filter disabled.
OK OK OK
OK OK
Asym: or Default Asymmetry is an initial calibration value (in ns) and can be entered here
if a certain asymmetry offset in the network path is known before the PTP unit starts.
This occurs in SDH networks for example.
Max. Path Delay: If a measured path delay exceeds the value of this parameter (in ns), then the PTP unit
is able to detect a change in the asymmetry offset and can take this into account for
its delay measurements.
Note: Keep defaults settings here (0 ns for both parameters) unless some problems with the
client synchronization accuracy are observed and only if the asymmetry offset can be
measured beforehand.
PTPv2 Domain: A PTP domain is a logical group of PTP devices within a physical network that belong to
the same domain number. Slave devices that shall sync to a certain master within a network
must have configured a unique domain number which is the same on the master.
Msg Intervals: specify the settings for the PTP timing messages.
Anno. Intv specifies the time interval of announce messages between master servers
to select the Grand Master. Note: This value should be the same as for the master. Available
settings are: 1, 2, 4, 8 or 16 seconds, with a default value of 2 seconds.
Sync. Intv specifies the time interval of sync messages that a slave requests from
a master. Available settings are 0.5, 1, or 2 seconds, with a default value of 1 second.
Requ. Intv specifies an interval how often delay request messages are sent from a
slave to the master. Delay request messages intervals of 1, 2, 4, 8, 16 or 32 seconds,
with a default value of 8 seconds.
The Duration parameter is used to set a timeout for the grandmaster that sends out
the sync packages until the timeout expires. A slave sends a new signaling message to
refresh the request before the end of the Duration timeout. Thus it is receiving the requested
sync packages continuously. The duration parameter will handle all message types and should
be in the range between 10-300 s.
Master IPv4: The correct IP address of the Master’s PTP port must be entered in this field.
HQ Filter: In heavy loaded networks when using non-PTP compliant switches, the "HQ Filter" can be
activated to reduce the jitter. Detailed information about the usage and the configuration
of the HQ filter can be found in the "PTPv2 Configuration Guide "in chapter in chapter PTP Option.
The Default setting is with HQ Filter disabled.
IP configuration for the PTPx interface. It can be selected if either a static IP address shall be used or if
a dynamic IP address via DHCP should be assigned.
VLAN Config:
Configuration of Virtual LAN (IEEE 802.1Q) settings for the PTPx interface:
• VLAN ID: A 12-bit value (0..4096) specifying the VLAN to which the network port belongs.
• VLAN Priority: The priority indicates the frame priority level from 0 (lowest) to 7 (highest), which can be
used to prioritize different classes of traffic (voice, video, data,...)
NTP Settings
->2nd Receiver<-
PTP IEEE1588
OK
Ref. Time
Time Service
->Network <-
System
OK
OK OK OK
In this submenu the network configuration 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 configured, additional network configuration can be done via network connec-
tion with TELNET, SSH or the WEB interface. Ask your network administrator for network specific parameters.
Every change of the network parameters will restart the NTP. All network specific parameters will be saved
on the flash disk (/mnt/flash/config/global_configuration) and will be reloaded after reboot. It is highly recom-
mended not to edit this file manually but to configure the parameters via the several configuration interfaces
(HTTP, CLI or SNMP). If this file is not present, an empty file will be created. See Appendix for the default
settings of this file.
When configured an IP address once additionally network configuration can be done via network connection
with TELNET, SSH or the WEB interface. Ask your network administrator for network specific parameters.
Every change of the network parameters will restart the NTP. All network specific parameters will be saved on
the flash disk (/mnt/flash/config/global_configuration) and will be reloaded after reboot.
There is a separate configuration 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: 172.160.100.200
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 specific
network.
If there is a DHCP (Dynamic Host Configuration 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
fields (IPv4 Address, Netmask, Default Gateway).
IPv4 Parameter
>IPv6 Parameter<
Link Mode
OK
OK OK OK OK
Show current Set IPv6 Auto- Set IPv6 Link Set IPv6 Link
Link Local Addr configuration Global Address 1 Global Address 2
IPv6 lan0:0 : Flag: lan0:0 : IPv6 lan0:0 : IPv6 lan0:0 :
not assigned []disabled [] []
The IPV6 parameter can be configured via the front panel display for the first ethernet port (ETH0) only. Ad-
ditionally IPV6 configuration 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. Additionally you can switch off
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 net-
work and if you enabled the IPv6 autoconf feature, your LANTIME will be set up with up to three link global
addresses automatically.
10HD
10FD
100HD
100FD
1000HD
1000FD
With the Link Mode submenu the parameters for link speed and duplex mode of the first ethernet interface (ETH0)
can be configured. There are 5 modes available: Autosensing, 10 Mbit/Half Duplex, 100 Mbit/Half-Duplex, 1000
Mbit/Half-Duplex (Gigabit Support), 10MBit/Full-Duplex, 100 Mbit/Full-Duplex and 1000 Mbit/Full-Duplex
(Gigabit Support).
OK
OK OK OK OK
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 fields you have to enter an Ipv4 address.
All information written to the LANTIME SYSLOG (/var/log/messages) can be forwarded to one or two re-
mote SYSLOG servers. The SYSLOG daemon of this remote SYSLOG needs to be configured 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 fields 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 off 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 off the LANTIME.
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.
The possible network protocols and access methods can be configured. 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).
Ref. Time
Time Service
Network
->System <-
OK
>Set Time Zone< >Restart NTP < >CPU Temperatur< >Show Fan State<
DL Sav ON Restart System IMS Info Fan Control
DL Sav OFF Show CPU Temp.
Reset Factory
OK
OK OK OK
This menu lets the user enter the names of the local time zone with daylight saving disabled and enabled,
together with the zones´ time offsets from UTC. 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
effect can be entered using the next two pages of the setup menu.
Beginning and ending of daylight saving may either be defined by exact dates for a single year or using
an algorithm which allows the receiver to re-compute the effective dates year by year. The figures 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 specified. Then, starting from the configured date, daylight saving changes the first day which matches
the configured day-of-week. In the figure below October 25th, 2008 is a Saturday, so the next Sunday is
October 26th, 2008.
All changeover rules for the daylight saving like "the first/the second/the second to last/the last Sunday/Mon-
day etc. in the x-th month," can be described by the used format "first specified day-of-week after a defined date".
If the number of the year is not displayed as wildcards the complete date exactly determines the day day-
light saving has to change (October 26th, 2008 in the figures below), so the day-of-week does not need to be
specified and therefore is displayed as wildcards.
If no changeover in daylight saving is wanted, identical dates and times must be entered in both of the submenus
(DAYLIGHT SAV ON/OFF).
In menu option you can make the following settings or request setting information:
Time Zone: The converted time (offset to UTC) for the configured time zone, which is shown
in the display. This has no effect on the time strings that are outputted via the
serial interfaces.
You can make this setting via the menu "Ref. Time -> Set Outputs -> Time Zone".
Options: In this sub menu you can reset the system to the state of delivery by using
"Reset Factory". The network settings remain unchanged.
With "Restart NTP" you can restart the NTP service and with "Restart System"
the LINUX operating system of the CPU.
System Info: With "System Info" you can request the current operating temperature of the CPU.
If the LANTIME is used in an IMS System, information about the system configuration,
like the allocation of single slots, can be displayed in this menu section.
Fan Control: If an active cooling is installed, the cooling status can be displayed via this menu item
and via "Fan Control" you can set the mode of the active cooling:
Auto: (temperature independent - the threshold value can be adjusted via the
webinterface - menu "System -> Fan Control".
OK OK OK
If the time of the reference clock has changed (e.g. while testing with different times) the system time has to
bet set with the time of the reference clock and the NTP has to be restarted.
The command Reboot System reboots the Linux operating system – the built-in reference clock will not be
restarted.
When Reset to factory defaults is called, all system parameters will be reset to initial values. However the
parameters of each network interface do not change.
In the "System Info" submenu, the CPU temperature can be queried. In IMS systems a detailed overview of the
system configuration can be shown.
Note: This display menu is visible only in case of an IMS system. Here a detailed overview of the modules,
used in the selected slots, are given.
OK
This menu shows which module is inserted into the selected slot.
Time Zone
Restart
System Info
>Fan Control <
OK
>Show Fan State < Show Fan State Show Fan State
Fan Control >Fan Control < Fan Control
Show CPU Temp Show CPU Temp >Show CPU Temp <
OK OK OK
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.
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.
Please Note:
Even if you are currently making changes to a LANTIME, you can only save the configuration on the USB stick
which you have confirmed via the web interface as "Startup configuration". This has the advantage that you can
save your "old" configuration even if you make extensive changes to the settings of your system.
This submenu is an easy way to get the contents of the LANTIMEs diagnostic files. After you push the OK
button, the system will copy a file archive to your USB device: /Lantime/Diag/ltdiag.tgz
The keypad locking will be activated with a submenu from the USB stick:
When activating this submenu the file /mnt/flash/config/keypad_lock will be copied to the internal flash. When
de-activating the keypad locking this file will be removed from the internal flash.
Note:
Make sure, that you never loose the "Keypad_Lock" file or the USB storage device! If you have problems, please
contact Meinberg Radio clocks: Mail to [email protected] .
2. The backup will only be imported, if a directory with the appropriate SN is available (or "ANY_SN")
3. After "Restore" the config is not bootable yet. To activate this, you must first execute the
’saveconfig’ command via a CLI (console program) or use the web interface and press the
"Save as Startup Configuration" button.
After the connection is successfully established use your login credentials in the welcome screen to enter
a console.
After successful registration change the current path to /wizard/. Start now the LANTIME Basic Configu-
ration Wizard with “startwizard”.
Confirm with "y" to start the configuration for all the following settings.
After the lantime has been assigned to a correct IP address, all other settings can be done via the exten-
sive and powerful web interface (see chapter Via Web GUI).
The way it works is each network element has an Agent which communicates with the Manager via SNMP.
Each Agent has a corresponding Management Information Base, or MIB. The MIBs organize data elements in
a tree structure. It is written in a standard, highly structured language so that the MIBs from all of the devices
on the network can be compiled into the same Manager.
MIB elements are called Object Identifiers or OIDs. They consist of configuration variables, status variables,
tree structure labels and notifications. The OIDs can be read or changed using SNMP SET and GET commands.
There are also recursive commands which allow the Manager to ask for all of the OIDs in a branch (subtree), or
even the whole tree. This process is referred to as “walking the MIB”. Event Notifications, commonly referred
to as traps, are a special type of OID. A trap can be configured so that when the status of the device changes
a message is immediately sent from the Agent to the Manager.
mbgLtNgRefclockState
This OID describes a current state of a LANTIME refclock (hardware clock module) referring to GNSS
or any other time source signal in MRS (Multi Reference Source) model.
Status Description
———————————————————————————————————————————————–
0: refclock is not available: See the possible troubleshooting:
1. Refclock module cannot be accessed.
2. Check if it is damaged and replace it if necessary.
The MRS system above synchronizes first to GPS, but if the GPS signal is unavailable,
the refclock switches to the next time source from the priority list (PTP in our case).
The switch happens only after a trust time of the unavailable time source (GPS signal)
has run out. This is to prevent hopping from one time source to another in short time
periods. If GPS becomes available again, the refclock switches back to GPS, without
waiting for the PTP trust time in this case, since GPS itself a higher precision than PTP.
2: not synchronized: Obviously the refclock is not synchronized to its time source. Here is
the possible troubleshooting:
A) Check if the GPS antenna is connected and reference time received. More about how
to mount and position Meinberg GPS antenna correctly learn here.
B) If GPS is the current time source, check number of satellites in view. There should
be at least four to provide sync information.
C) Start “warm boot” to refresh current satellite position. This is useful especially if
the physical position of your LANTIME has been displaced by more than 100 km from its
previous location and therefore obsolete satellite data are still stored in the system.
D) Start "cold boot" to update a satellite almanac.
E) If nothing from above helps, the GPS clock module needs to be changed.
Here is short summary of the leap seconds. There are two different timescales we usually talk about in
the sync environment: GPS, which stands for Global Positioning System time and UTC (Universal Time Co-
ordinated), formerly known as GMT (Greenwich Mean Time). They differ from each other by number of leap
seconds introduced since beginning of GPS time on 6-Jan-1980. In the moment of writing the UTC is 16 seconds
behind the GPS time, which is due to the uneven rotation of the Earth.
Since the introduction of a new leap second influences the time in the
whole system being synchronized, we suggest to check this status regularly,
e.g. 1/hour.
Next in a row of OIDs are those referring to NTP status. They can be found in the “mbgLtNgNtp” subtree.
mbgLtNgNtpCurrentState
This is one of the most important OID in this subtree to check regularly. It informs about the NTP service of
your LANTIME. There are three states possible:
Status Description
———————————————————————————————————————————————–
0: not available: See the possible troubleshooting:
A) Check if NTP service is actually enabled at a given LAN interface.
To check it, log in to a webinterface. Factory default credentials:
root/timeserver. Go to menus: "Network → Network Services" and
activate the service of the corresponding interface. See Figure 3 for details.
1: not synchronized: In case of "not synchronized" the NTP service is not yet synchronized
to a reference clock. Possible causes for this state are as follows:
A) NTP daemon is still in its initialization phase for which it needs approx. 3-5 min.
Therefore wait a while and see if the status changes.
B) If a refclock is not sync, the same is indicated in the NTP status. In such case
NTP daemon is switched to synchronize to its local clock and its stratum value
changes to 12. Please check the possible troubleshooting for a refclock status
as described above.
2. synchronized: The NTP service is in normal operation. The LANTIME is now working properly.
Status Description
——————————————————————————————————————————————-
0: notAvailable: The queried power supply unit is not recognized by a system. Check to see
if it is damaged, and replace it if necessary.
1: down: The power supply unit of interest is not in service. Check to see if it is damaged,
and replace it if necessary.
Status Description
———————————————————————————————————————————————–
0: notAvailable: The queried port is down, check the link LED. If faulty,
replace the network card.
mbgLtNgPtpPortState
The following PTP Port States are possible:
Status Description
———————————————————————————————————————————————–
0: uninitialized: The port is booting up, the software daemon has not yet started, the
IP address is not yet assigned.
1: initializing: In this state the port initializes its data sets, hardware, and communication
facilities.
3: disabled: PTP service has been disabled on this port, either by user configuration or because
the module is in a standby mode.
7: passive: The port is in passive mode, meaning there is another master clock active in the
PTP domain. The port can enter master state when it wins the BMCA due to a failure/service
degradation of the current master.
8: uncalibrated: One or more master ports have been detected in the domain.
9: slave: The port has successfully subscribed to a master and receives all expected messages.
It also successfully measured the path delay using delay request messages.
NTP Stopped /
The NTP service stopped • Info: After every configuration change relevant
to the NTP, the NTP service is stopped and
restarted. In this case, a message ’NTP Stopped’
is written into the system log of the LANTIME.
• Contact the Meinberg TechSupport and provide
a LANTIME diagnostic file, if ’NTP Stopped’ is
permanently displayed as NTP status in the front
panel or in the web interface.
XMR Limit Exceed / • Check the current MRS time source status in the
LANTIME generates this message when the measured Web Interface under "Clock → GNSS Clock →
time offset of an MRS time source has exceeded the MRS Status".
configured threshold value.
• Check the MRS configuration in the Web Inter-
face under "Clock → GNSS Clock → MRS Set-
tings". Are the configured threshold values (check
the "Limit" column) configured possibly too strict?
• Contact your Meinberg TechSupport and provide
a LANTIME diagnostic file, if you need further
assistance at solving the problem.
Network Link Down / • Check which ports are physically connected and
There was no link detected at one of the the link should be available.
LANTIME’s network interface. • Check for compatible network settings on switch
and LANTIME.
• Check the settings for link monitoring via the
Web Interface: "Network → Physical Network
Configuration → Indicate Link on Front Panel
LED".
– The LANTIME monitors a link status for
the ports where the "Indicate Link on Front
Panel LED" option is activated.
• Contact your Meinberg TechSupport and provide
a LANTIME diagnostic file, if you need further
assistance at solving the problem.
Fan Failure /
• If the fan module has not been intentionally re-
The LANTIME has detected a fault on a fan module,
moved, contact the Meinberg TechSupport and
or a fan module has been removed during system op-
provide a LANTIME diagnostic file.
eration.
CPU No Response (This error message can only ap- Troubleshooting / Additional information
pear on a display) /
The display does not receive any information from the
installed LANTIME CPU unit. • Check whether the LANTIME is still available
over the network (try to ping, SSH, HTTP /
HTTPS)
• Does a power cycle solve this problem?
• If the LANTIME is still accessible via HTTP /
HTTPS, please download a diagnostic file via
the web interface and send it to the Meinberg
TechSupport. If no connection to the LANTIME
is possible, contact the Meinberg TechSupport
with the serial number of your LANTIME.
Depending on the product this level also includes a 2 or 3 year hardware warranty. You can extend the
hardware warranty period after the standard warranty of your Meinberg product ends.
Technical Support
E-Mail [email protected]
Service hotline +49 (0) 5281 / 9309-888
Mon – Thu 8:00 – 17:00, Fri 8:00 – 16:00 (CET/CEST)
Service hours hotline
Not available on Sat/Sun and German Public Holidays
Office (Sales/Purchase)
E-Mail [email protected]
Service hotline +49 (0) 5281 / 9309-888
Mon – Thu 7:30 – 17:00, Fri 07:30 – 15:00 (CET/CEST)
Service hours hotline
Not available on Sat/Sun and German Public Holidays
In order to assist you with configuration, installation, monitoring and diagnostics of your Meinberg products, you
can download a remote support software that allows Meinberg technical support to remote control your computer.
https://www.meinbergglobal.com/english/support/remote.htm
you can find all necessary information and to download the support.
https://www.meinbergglobal.com/english/sw/firmware.htm
and fill out the form. Available firmware updates will be provided by e-mail (LANTIME firmware V5 or older
versions) or with a direct download link (LANTIME firmware V6).
The diagnostic file includes all status data of a LANTIME system logged since the last reboot. It can be
downloaded from all LANTIME timeservers or you can save the file on a USB stick connected to the device.
The file format of the diagnostic file is a tgz-archive. The archive contains all the important configuration and
logfiles.
• The file will take some time to be created as its size is several MBs. After the file has been created it
will be automatically sent to your web browser. Then save the file to your local hard disk.
• The diagnostic file is named "lt_diag_SERIALNUMBER.tgz" and the file format is a tgz archive. You can
open the tgz archive e.g. with 7Zip (https://www.7-zip.org/).
The blog provides you also the opportunity to write a comment or a question to our experts and get their
reply.
Categories:
Configuration Guidelines, IEEE 1588, Industry Applications, NTP and Security.
If you are planning or re-designing synchronization for your networks and you need additional knowledge,
see our agenda for the upcoming courses.
Homepage: https://www.meinberg.academy/
E-Mail: [email protected]
https://www.meinbergglobal.com/english/contact/newslett.htm
12 Appendix
12.1 LANTIME CPU - Central Processing Unit
Booting the Single Board Computer
The LINUX operating system is loaded from a packed file on the flash disk of the single board computer to a
RAM disk. All files of the flash disk are stored in the RAM disk after booting. Because of that it is guaranteed
that the file system is in a defined condition after restart. This boot process takes approx. two minutes. During
this time the following message appears on the display:
MEINBERG LANTIME
is booting ...
please wait ...
......
After starting up the LINUX system the network function is initiated and the program for communication with
the reference clock and the NTPD (NTP daemon) is started. After that NTPD starts synchronization with
the reference clockss (usual the hardware clock of the single board computer and the used receiver). Until
synchronization is finished the following message is displayed:
For the synchronization of the NTPD, e.g. with a GPS creceiver, it is necessary that the GPS receiver is
synchronous with the GPS time. In this case the following message is shown on the display:
NORMAL OPERATION
NTP: Offs. 2ms
Wed, dd.mm.yyyy
UTC 12:00:00
The second line shows the user that the NTPD is synchronized with the GPS with an offset 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 offset. The NTPD tries to keep the offset below +-128 ms; if the offset becomes too large the
system time is set with the GPS time. Typically values for the offset are +-5 ms after the NTPD has already
synchronized.
Flashdisk: 1 GB
Network
Connector: 10/100 MBIT with RJ45-Jack
Power
Requirements: 5 V +- 5 %, @ 1 A
Ambient
Temperature: 0 ... 50 ◦ C
Storage
Temperature: -20 ... 70 ◦ C
Humidity: 85 % max.
<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 defined below:
w the day of
the week (1..7, 1 = Monday)
y anouncement of discontinuity of time, enabled during last hour before discontinuity comes in effect:
‘!’ announcement of start or end of daylight saving time
‘A’ announcement of leap second insertion
‘‘ (space, 20h) nothing announced
<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 defined below:
CHx_tt.mm.jj_hh:mm:ss.fffffff <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 defined below:
<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 defined below:
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 defined below:
$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 defined below:
a magnetic variation
$GPGGA,hhmmss.ss,bbbb.bbbbb,n,lllll.ll,e,A,vv,hhh.h,aaa.a,M,ggg.g,M„0*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 defined below:
aaa.h Mean Sea Level altitude (MSL = altitude of WGS84 - Geoid Separation)
$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 defined below:
>900WD:yy-mm-tt_hh.mm;ss.fff: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 defined below:
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 defined below:
T Start character
sending with one bit accuracy at change of second
<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 defined below:
Interface
parameters: 7 Databits, 1 Stopbit, odd. Parity, 9600 Bd
Please note:
To receive the Timestring on a selected terminal correctly you have to send a " C " (once, without quotation marks).
<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 defined below:
<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 defined below:
<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 defined below:
• 1 start bit
• 7 data bits
• 1 parity bit (odd)
• 1 stop bit
The on-time marker is represented by the leading edge of the start bit. The time code consists of 15 characters,
sent once per second at a baud rate of 300 or greater. The format is:
<SOH>DDD: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 defined below:
HH, MM, SS time of the start bit given in hour (HH), minute (MM), second (SS)
Key-Value-Pairs
The Format with Key-Value-Pairs can be accessed directly from a SPLUNK database server
and has the following format:
JSON
The JSON format can be processed directly by most databases and has the following format:
{
"IsoTime": "2018-02-05T09: 40: 13 + 00: 00",
"syncMonName": "SyncMon",
"optInterfaceIp": "172.27.100.32",
"utcTime": 1517823613,
"node": "M3000_100_57_NTP_LAN0_test",
"offset1": 0.000000494,
"offset2": 0.000041453,
"pathDelay": 0.000073266,
"status": "stratum 1 / [10]",
"offset1Min": - 0.000011100,
"offset1Max": 0.000041453,
"type": "NTP / SW / CPU"
}
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.
12.4.2 Samba
The Samba software suite is a collection of programs, which implement the Server Message Block (SMB) pro-
tocol 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.
*************************************************************************
* *
* 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 specific, *
* 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. *
* *
*************************************************************************
- Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer.
- Neither the name of the ’incremental’ nor the names of its contributors may
be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
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 software–to 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 re-
cipients 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) offer 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 modified 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
reflect 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 effect making the program propri-
etary. 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 modification follow.
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
modifications and/or translated into another language. (Hereinafter, translation is included without limitation
in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are out-
side 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.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer war-
ranty 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 modifications or work under the terms of Section 1 above, provided
that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files 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 modified 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 modified work as a whole. If identifiable 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 offer, 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 cor-
responding 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 offer 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 offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable
work, complete source code means all the source code for all modules it contains, plus any associated interface
definition files, 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.
If distribution of executable or object code is made by offering access to copy from a designated place, then
offering 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 automat-
ically 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 gen-
erous 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 differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies 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.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH
YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY
SERVICING, REPAIR OR CORRECTION.
[Mills89] Mills, D. L., "Network Time Protocol (Version 2) - specification and implementation",
DARPA Networking Group Report RFC-1119, University of Delaware, September 1989
[Mills90] Mills, D. L., "Network Time Protocol (Version 3) - specification, implementation and analysis",
Electrical Engineering Department Report 90-6-1, University of Delaware, June 1989