Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3730

Wrong Error-Message when Meinberg NTP-Servers changes Stratum Level

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      When a Meinberg NTP-Server (in our case a Lantime M300 with the latest Release 6.24.028 from April 2021) changes the refernce time and/or stratum status this is recorded as "Hardware changed" in the logfile. Which is misleading.

      The attached Screenshot shows a Server "spamming" the logfile with these messages.

      The "Hardware change" just means that the reference time when in Stratum 2 mode changes from time to time from .12 to .15 (whoever has the most stable time that the NTP-Daemon chooses). The "Hardware change" to "GPS" just means that the server is back to Stratum 1 mode ...

       

      The Meinberg itself does not record the changes in reference time - but the change in Stratum-level :

       

      2021-04-26 09:22:28 UTC: LANTIME -> NTP Sync To GPS
      2021-04-26 09:22:28 UTC: LANTIME -> NTP stratum changed from 2 to 1
      2021-04-26 09:15:00 UTC: LANTIME -> CLK1 Sync

       

      It seems that observium does not record the change of the CLK1 status nor the stratum-change but gets this strange information from snmp.

       

      It's maybe a cosmetic bug - but it still might be something you can have a look to.

      Attachments

        Issue Links

          Activity

            [OBS-3730] Wrong Error-Message when Meinberg NTP-Servers changes Stratum Level

            Thanx !

            horke Bernhard Krönung added a comment - Thanx !

            Hardware detect should be fixed in r11264.

            landy Mike Stupalov added a comment - Hardware detect should be fixed in r11264.
            horke Bernhard Krönung added a comment - SNMP-MIBs : https://www.meinberg.de/german/sw/#snmp-mib

            [^myagent.snmpwalk]

            horke Bernhard Krönung added a comment - [^myagent.snmpwalk]

            Please make and attach additional information about the device:

            • full snmp dump from device:

              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

              If device not support SNMP version 2c, replace -v2c with -v1.

            • If you have problems with discovery or poller processes, please do and attach these debugs:

              ./discovery.php -d -h <device>
              ./poller.php -d -h <device>

            • additionally attach device and/or vendor specific MIB files

            Note, this comment is added automatically.

            bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

            People

              landy Mike Stupalov
              horke Bernhard Krönung
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: