Meinberg NTP Server

General
#1

Hey,

We have two Meinberg Lantime M300 MRS timeservers with GPS antennas. We are monitoring them through the integrated SNMP server using Check MK (Enterprise Edition 2.1.0p2) . Unfortunately, we are unable to retrieve any information regarding the state of the GPS receiver. The only Meinberg specific information we are able to retrieve is ‘LANTIME State’ which reads ‘synchronized’ even if the antenna isn’t even plugged in and the server is only synced to the backup public NTP-servers. According to this page, we should be able to retrieve the actual state of the receiver:

How can you retrieve Information like ‘mbg_lantime_ng_refclock_gps’ from the servers using Check MK.

Thanks

1 Like
#2

There could be two reasons for this behaviour.

  1. The SNMP agent on the device does not hand out the required OIDs for the check.
  2. The SNMP agent on the device identifies itself different and the check never goes active.

For 1. try to fetch the OID .1.3.6.1.4.1.5597.3.2 with snmpwalk.
For 2. fetch the OID .1.3.6.1.2.1.1.2.0, it should contain .1.3.6.1.4.1.5597.3

This info can be found in the check plugin code: checkmk/mbg_lantime_refclock at master · tribe29/checkmk · GitHub

#3

Thanks for your help.

I make an snmpwalk and get the following

iso.3.6.1.4.1.5597.3.2.4.0 = INTEGER: 1
iso.3.6.1.4.1.5597.3.2.6.0 = INTEGER: 1

iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.5597.30

I think the error is in the fetch 2. The result ist .30 and not only .3

#4

The scan function of the check plugin has to be adapted. Talk to your support contact about that.

#5

Hi,
i have working legacy checks for this so i could send you but i think for best would be to open contract as r.sander mentioned.

#6

I try to modify the check and change it to 30

After this the Check comes up, but as UNKOWN and crashed

#7

Then maybe more has changed than just the sysObjectID. The check may need to be rewritten.

#8

Hi,
I have a Meinberg M1000 where the check shows critical alarms for the fan units. But when looking in the Meinberg GUI they show ok.

What is the procedure to “report” that the check probably needs to be adapted for that as well?