9 LTOS7 Management and Monitoring
9.2.2 MIB Objects of a LANTIME
An LTOS operating systems running on Meinberg LANTIME servers supports all SNMP versions (v1,v2c and
v3) with a full functionality. The LANTIME propriatery OIDs are structured into subtrees, which define a par-
ticular system component or a mode of operation. The main subtree with OIDs referring to the LANTIME status
of different modes is called LantimeNGStatus, NG standing for New Generation of LANTIME features in the
V6 firmware. The LantimeNGStatus consists of eight subtrees, where Refclock, NTP, PTP, SystemHardware,
Cluster and Misc are the most important to monitor.
9.2.2.1 Refclock subtree
Here is a short list of OIDs from the NGStatus subtree with corresponding descriptions:
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.
1:
synchronized:
The reflock of your system is correctly synchronized to the
selected time source (GPS or MRS). In an MRS system, a refclock can be synchronized
to a reference time source from the priority list. See an example in the next figure.
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.
It is recommended configuring your network management software to check
this status regularly, if possible every 60 s.
LANTIME CPU Expansion Shelf
Date: 2nd July 2020
149
