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

OBS discovering same board from two different vendors as same vendor

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None
    • Debian 10, Observium 21.7.11458 (rolling)

    Description

      Support was added for this board in OBS-3782. The board itself is manufactured by Embedded Data Systems. The current discovery vendor - Proges Plus - purchases this board from EDS and applies slightly customized firmware to display its own branding. Simple version is that there are two hardware identical products out there, with slightly different firmware. OBS discovers both of them as Proges Plus instead of differentiating between the two. Ideally, there is some way for OBS to discover EDS products as EDS and Proges Plus as Proges Plus.

      I have attached the full set of requested support files for both boxes - labeled as EDS and Proges.

      Attachments

        Issue Links

          mentions

          Improvement - An improvement or enhancement to an existing feature or task. OBS-3782 Embedded Data Systems - Not discovering / polling temperature sensors

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-3807] OBS discovering same board from two different vendors as same vendor
            landy Mike Stupalov added a comment -

            Improved in r11472.

            landy Mike Stupalov added a comment - Improved in r11472.
            elcid89 Darren Watts added a comment -

            Files attached

            elcid89 Darren Watts added a comment - Files attached
            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.

            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
              elcid89 Darren Watts
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: