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

          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?

          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...

          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.

          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 -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

            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 -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 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
            beens Steven Bens
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: