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

Missing support for Schneider chiller BCEF0401A

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Default
    • None

    Description

      We have a Schneider Electric BCEF0401A chiller of which the information is not shown correctly in observium.
      We received a mib from our supplier, but there already seems to be a newer version in the observium mibs that is not attached to the chiller's OS or gets wrongly discovered.
      (/opt/observium/mibs/carel/CAREL-bce-bcwc-MIB)
      Can you please add support for this chiller So all information is shown correctly?
      Thanks

      Attachments

        1. AQUACENTR_v1.4_SNMP_pCOWeb_mib.mib
          117 kB
        2. chiller-1a.zav.snmpwalk
          107 kB
        3. discovery-php.output
          245 kB
        4. poller-php.output
          179 kB

        Activity

          [OBS-5002] Missing support for Schneider chiller BCEF0401A
          adama Adam Armstrong made changes -
          Comment [ _*General questions and device support can be discussed in [our Discord channel, click here to join|https://discord.gg/GjpNXKWm8W].*_
          ----

          Please make and attach additional information about the device:
           * full snmp dump from device:
          {noformat}
          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
          {noformat}
            _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:
          {noformat}
          ./discovery.php -d -h <device>
          ./poller.php -d -h <device>
          {noformat}
           
          * additionally attach device and/or vendor specific MIB files

          ----
          {color:#505F79}_This comment is added automatically._{color} ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          adama Adam Armstrong added a comment -

          This looks like a job for the undocumented "static" sensors ability.

          We have problems with devices that have undefined/one-off SNMP layouts, but those can just be manually added using the static sensors.

          These Carel controllers all have broken/unusable MIBs, and it's even worse when they're in Schneider devices, because they care even less about keeping the SNMP functional.

          The only realistic way to use these devices is to manually define each sensor in config.php so that Observium can use it. To do that you'll need to reverse engineer the OIDs to figure out which ones are the datapoints you want (or somehow get a mapping file from Schneider, it might be called a DDT).

          static sensors are defined like this. it's straightforward, but time consuming: 

          $config['sensors']['static'][] = ['device_id' => '798', 'class' => 'load', 'oid' => '1.3.6.1.4.1.49314.1.1.1.4.9.1', 'descr' => 'Supply Fan A1', 'multiplier' => 1];
          $config['sensors']['static'][] = ['device_id' => '798', 'class' => 'temperature', 'oid' => '1.3.6.1.4.1.49314.1.1.1.4.9.17', 'descr' => 'External A1', 'multiplier' => 0.1];

          adama Adam Armstrong added a comment - This looks like a job for the undocumented "static" sensors ability. We have problems with devices that have undefined/one-off SNMP layouts, but those can just be manually added using the static sensors. These Carel controllers all have broken/unusable MIBs, and it's even worse when they're in Schneider devices, because they care even less about keeping the SNMP functional. The only realistic way to use these devices is to manually define each sensor in config.php so that Observium can use it. To do that you'll need to reverse engineer the OIDs to figure out which ones are the datapoints you want (or somehow get a mapping file from Schneider, it might be called a DDT). static sensors are defined like this. it's straightforward, but time consuming:  $config ['sensors'] ['static'] [] = ['device_id' => '798', 'class' => 'load', 'oid' => '1.3.6.1.4.1.49314.1.1.1.4.9.1', 'descr' => 'Supply Fan A1', 'multiplier' => 1] ; $config ['sensors'] ['static'] [] = ['device_id' => '798', 'class' => 'temperature', 'oid' => '1.3.6.1.4.1.49314.1.1.1.4.9.17', 'descr' => 'External A1', 'multiplier' => 0.1] ;
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]

          I'm uncertain what you mean.
          Can we schedule a zoom call to discuss & debug this together?

          beens Steven Bens added a comment - I'm uncertain what you mean. Can we schedule a zoom call to discuss & debug this together?
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]

          Also your attached mib seems as unrelated with snmpdump. No one snmp value is connected with clear variable.

          I just cant understand which values what mean...

          landy Mike Stupalov added a comment - Also your attached mib seems as unrelated with snmpdump. No one snmp value is connected with clear variable. I just cant understand which values what mean...
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]

          This is mostly derp MIB and os (for monitoring).
          This units not report any hardware/vendor unique values, MIBs is vendor/hardware specific.
          We not found ways for detect correct MIB files for specific models.

          landy Mike Stupalov added a comment - This is mostly derp MIB and os (for monitoring). This units not report any hardware/vendor unique values, MIBs is vendor/hardware specific. We not found ways for detect correct MIB files for specific models.

          People

            landy Mike Stupalov
            beens Steven Bens
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: