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

Some sensors being ignored on Vertiv Geist WD100

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Hello,

       

      I have found this unusual behavior on Observium Professional 21.9.11575 and CE 21.10.11666.

       

      My company uses Vertiv Geist WD100 environmental monitors, which have internal sensors as well as plug-n-play external sensors.  I have found that Observium isn't monitoring some external sensors.  For example, their "RTAFHD3 - remote temperature/humidity/dewpoint" sensor (.1.3.6.1.4.1.21239.5.1.4) appears to work, but the "GT3HD - triple temperature, humidity, dewpoint" sensor (.1.3.6.1.4.1.21239.5.1.8) is ignored.

       

      In my spare time, I have been developing an ESP8266-based monitor based on the Geist MIB, to try to make it work seamlessly in Observium (while being cheap enough to use at home).  For testing, I have made it respond to every OID in the MIB, and I'm seeing the same behavior where most of the external sensors are ignored.  Only .1.3.6.1.4.1.21239.5.1.4 (Remote temperature sensor), .1.3.6.1.4.1.21239.5.1.5 (airflow sensor), and .1.3.6.1.4.1.21239.5.1.9 (temperature/humity/dewpoint sensor) are recorded by the system.  Ignored are .1.3.6.1.4.1.21239.5.1.6 (Dewpoint sensor), .1.3.6.1.4.1.21239.5.1.9 (CCAT sensor), .1.3.6.1.4.1.21239.5.1.8 (T3HD sensor), .1.3.6.1.4.1.21239.5.1.10 (RPM sensor), .1.3.6.1.4.1.21239.5.1.11 (A2D sensor).

       

      I have attached snmpwalk output and console output from a discovery and poll.

       

      Thanks!

       

      Attachments

        Issue Links

          Activity

            [OBS-4062] Some sensors being ignored on Vertiv Geist WD100

            Done.  OBS-4149.  Thanks!

            cbaranoski Casey Baranoski added a comment - Done.  OBS-4149 .  Thanks!

            Create new issue with file attached please.

            landy Mike Stupalov added a comment - Create new issue with file attached please.

            Hi Mike,

            I finally received my shipment of sensors.  I have attached an SNMP dump for their A2D sensor (.1.3.6.1.4.1.21239.5.1.11).

            Thanks!

            cbaranoski Casey Baranoski added a comment - Hi Mike, I finally received my shipment of sensors.  I have attached an SNMP dump for their A2D sensor (.1.3.6.1.4.1.21239.5.1.11). Thanks!

            Thanks, Mike!

             

            I'm awaiting delivery of a bunch of other sensors, but everything is backlogged because of "unprecidented times" or whatever.  I'll post more dumps whenever they arrive.

            cbaranoski Casey Baranoski added a comment - Thanks, Mike!   I'm awaiting delivery of a bunch of other sensors, but everything is backlogged because of "unprecidented times" or whatever.  I'll post more dumps whenever they arrive.

            Will reopen if you add new dump files.

            landy Mike Stupalov added a comment - Will reopen if you add new dump files.

            Added support for t3hdSensorTable (.1.3.6.1.4.1.21239.5.1.8) in r11912.

            These sensors are not being ignored, it's just that we don't have the data to add support for them.

            For other unsupported tables also need snmpdump with real sensors:

            • .1.3.6.1.4.1.21239.5.1.6 (Dewpoint sensor),
            • .1.3.6.1.4.1.21239.5.1.9 (CCAT sensor),
            • .1.3.6.1.4.1.21239.5.1.10 (RPM sensor),
            • .1.3.6.1.4.1.21239.5.1.11 (A2D sensor)

            if you have such devices, make snmpdump them as well.

            landy Mike Stupalov added a comment - Added support for t3hdSensorTable (.1.3.6.1.4.1.21239.5.1.8) in r11912. These sensors are not being ignored, it's just that we don't have the data to add support for them. For other unsupported tables also need snmpdump with real sensors: .1.3.6.1.4.1.21239.5.1.6 (Dewpoint sensor), .1.3.6.1.4.1.21239.5.1.9 (CCAT sensor), .1.3.6.1.4.1.21239.5.1.10 (RPM sensor), .1.3.6.1.4.1.21239.5.1.11 (A2D sensor) if you have such devices, make snmpdump them as well.

            Yes, I did.  It is lines 506 through 653 in the attached text file.

            cbaranoski Casey Baranoski added a comment - Yes, I did.  It is lines 506 through 653 in the attached text file.

            You not added snmpdump to issue.

            landy Mike Stupalov added a comment - You not added snmpdump to issue.

            All output was attached when opening the ticket.

            cbaranoski Casey Baranoski added a comment - All output was attached when opening the ticket.

            General questions and device support can be discussed in our Discord channel, click here to join.


            Please make and attach additional information about the device:

            • full snmp dump from device:

              snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community> -t 3 -Cc --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

            This comment is added automatically.

            bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

            People

              landy Mike Stupalov
              cbaranoski Casey Baranoski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: