10 Troubleshooting and Alarming
10.1 NTP Messages
Error and System message / Explanation
NTP Not Sync
/
The NTP service of a LANTIME is not sync.
Troubleshooting / Additional information
•
For LANTIMEs with built-in reference clock,
please check the status of the clock on the main
page. If the reference clock is not synchronized,
please refer to the troubleshooting information
for "CLK Not Sync".
•
For LANTIMEs, which are to be synchronized by
external NTP servers, make sure that the exter-
nal NTP servers are reachable.
•
For MRS devices, check whether MRS reference
time sources are configured in the Web interface
(
→
Clock
→
MRS settings) and corresponding
signals are available (
→
Clock
→
MRS status).
•
Contact your Meinberg TechSupport and provide
a LANTIME diagnostic file, if you need further
assistance at solving the problem.
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.
NTP Offset Limit Exceeded
/
LANTIME generates this message if the internal time
offset between LANTIME system time and the ref-
erence clock is higher than the configured threshold
value.
•
Check the configured threshold value in the Web
Interface: "NTP
→
Special Settings
→
Max. In-
ternal Offset (ms.)“
•
Note: After restarting the LANTIME it takes
several minutes, depending on the reference time
source, until the internal offset is <
±
1 ms.
•
Contact your Meinberg TechSupport and provide
a LANTIME diagnostic file, if you need further
assistance at solving the problem.
162
Date: 2nd July 2020
LANTIME CPU Expansion Shelf
Summary of Contents for LCES
Page 2: ......