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
r.sander
(Robert Sander)
June 20, 2022, 2:48pm
2
There could be two reasons for this behaviour.
The SNMP agent on the device does not hand out the required OIDs for the check.
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
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
r.sander
(Robert Sander)
June 21, 2022, 7:59am
4
The scan function of the check plugin has to be adapted. Talk to your support contact about that.
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.
I try to modify the check and change it to 30
After this the Check comes up, but as UNKOWN and crashed
r.sander
(Robert Sander)
June 22, 2022, 10:54am
7
Then maybe more has changed than just the sysObjectID. The check may need to be rewritten.
e95fja
June 22, 2022, 3:35pm
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?
Psych05
(Psych05)
July 27, 2022, 12:25pm
9
It’s a bug that has already been reported here:
BUG: Fehler im Plugin mbg_lantime_ng_fan - Feedback - Checkmk Community
Unfortunately, it is still not fixed.
e95fja
July 27, 2022, 6:14pm
10
Ok. Thanks for the info. I turned on “watching” for that BUG… hard to follow since it is in german though
e95fja
July 27, 2022, 6:20pm
11
Hm… it was actually closed since it was 1 year old…
Anyway, I have one M1000 and one M3000 so if someone do any development on that check just let me know if you need anything for testing or verification.
Made a PR on Github for the changes from the mentioned post.
tribe29:master
← Yogibaer75:meinberg_fan
opened 09:20PM - 27 Jul 22 UTC
In the check the state was switched between on and off.
Correct values from her… e
mbgLtNgSysFanStatus | 1.3.6.1.4.1.5597.30.0.5.1.2.1.2
Status of fan
Status: current
OBJECT-TYPE | INTEGER | notAvailable(0), off(1), on(2)
This bug affects all versions 1.6/2.0/2.1 and so on :)
Thank you for your interest in contributing to Checkmk!
Unfortunately, due to our current work load, we only consider pure bug fixes as stated in our [Readme](https://github.com/tribe29/checkmk#want-to-contribute).
This means any new pull request that is not a pure bug fix will be closed.
Instead of creating a PR, please consider sharing new check plugins, agent plugins, special agents or notification plugins via the [Checkmk Exchange](https://exchange.checkmk.com/).
## General information
Please give a brief summary of the affected device, software or appliance.
Keep in mind that we are experts in monitoring, but we cannot be experts on all supported devices.
A little context will help us assess your proposed change.
## Bug reports
Please include:
+ Your operating system name and version
+ Any details about your local setup that might be helpful in troubleshooting
+ Detailed steps to reproduce the bug
+ An agent output or SNMP walk
+ The ID of a submitted crash report for reference (if applicable)
## Proposed changes
Sometimes it is hard for us to assess the quality of a fix.
While it may work for you, it is our job to ensure that it works for everybody.
These are some ways to help us:
+ What is the expected behavior?
+ What is the observed behavior?
+ If it's not obvious from the above: In what way does your patch change the current behavior?
+ Consider writing a unit test that would have failed without your fix.
+ Is this a new problem? What made you submit this PR (new firmware, new device, changed device behavior)?
[mbgLtNgSysFanStatus](https://www.circitor.fr/Mibs/Html/M/MBG-SNMP-LTNG-MIB.php#mbgLtNgSysFanStatus) 1.3.6.1.4.1.5597.30.0.5.1.2.1.2
Status of fan
Status: current Access: read-only
OBJECT-TYPE
INTEGER notAvailable(0), off(1), on(2)
2 Likes
system
(system)
Closed
July 27, 2023, 9:22pm
13
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.