path: root/systemenvironments.tex
diff options
authorMatthias P. Braendli <matthias.braendli@mpb.li>2019-11-25 16:23:12 +0100
committerMatthias P. Braendli <matthias.braendli@mpb.li>2019-11-25 16:23:12 +0100
commit891031ddc40a019605ab1250fc631429a965e437 (patch)
tree57c5b10bb547769f34106bc551ca5d759d9be270 /systemenvironments.tex
parentb24baf8a1a59f87fae84a80115beaa73d3e5cd4f (diff)
Mention NTP startup check
Diffstat (limited to 'systemenvironments.tex')
1 files changed, 8 insertions, 3 deletions
diff --git a/systemenvironments.tex b/systemenvironments.tex
index 1267c0d..14e656f 100644
--- a/systemenvironments.tex
+++ b/systemenvironments.tex
@@ -146,13 +146,18 @@ synchronised to the clock time which is being transmitted by the multiplex to
which it has been tuned.
The system needs to run a NTP client that synchronises the system time over the
-network. Correct synchronisation can be checked using the \texttt{lpeers}
-command of the \texttt{ntpq} tool. The magnitude of the offset should be below
+network. Correct synchronisation can be checked using \texttt{chronyc tracking}
+or the the \texttt{lpeers} command of the \texttt{ntpq} tool, depending on if
+you use chrony or openntp.
+The magnitude of the offset should be below $10$\ms.
The performance of the NTP synchronisation should also be monitored permanently
during operation.
+ODR-DabMux can run a command at startup to verify if the NTP client is properly
+working, using the \texttt{startupcheck} setting. This can be used to call
+\texttt{ntp-wait} or \texttt{chronyc waitsync} to wait for proper NTP sync.
\subsection{Monitoring through SNMP}
There is ongoing work to make the monitoring of the tools possible using SNMP.
Please see \url{https://wiki.opendigitalradio.org/SNMP} for information about