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

Problem with Janitza Device Support

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Hi!

      We have just added some Janitza Power Meters to our datacenter and were pretty happy about existing support for devices of this vendor.

      But unfortunately it seems like Janitza has a different MIB for every device and the same OIDs are used for different values across their devices. Enclosed I am sending you the MIB File for our device. I tried to add modify the "janitza.inc.php" File - see enclosed. But it didn't do the trick.

      The OID for the device is: .1.3.6.1.4.1.34278.8.6 

      Any help would be appreciated.

      Attachments

        Activity

          [OBS-4059] Problem with Janitza Device Support
          swfeldkirch Siegfried Gumilar added a comment -

          Looks great! Thanks Mike!!!

          swfeldkirch Siegfried Gumilar added a comment - Looks great! Thanks Mike!!!
          landy Mike Stupalov added a comment -

          Support added in r11910.

          landy Mike Stupalov added a comment - Support added in r11910.
          swfeldkirch Siegfried Gumilar added a comment -

          I have attached the file. I had to use v1 as this device is not supporting v2c properly...

          swfeldkirch Siegfried Gumilar added a comment - I have attached the file. I had to use v1 as this device is not supporting v2c properly...
          landy Mike Stupalov added a comment -

          Hrm, the trouble is that in snmp dump only Enterprise Oid tree (.1.3.6.1.4.1).

          Make additional snmpwalk:

          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > myagent136.snmpwalk

          landy Mike Stupalov added a comment - Hrm, the trouble is that in snmp dump only Enterprise Oid tree (.1.3.6.1.4.1). Make additional snmpwalk: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > myagent136.snmpwalk
          swfeldkirch Siegfried Gumilar added a comment -

          I used the commands from the bot reply. Do I have to add a MIB path oder something else?

          swfeldkirch Siegfried Gumilar added a comment - I used the commands from the bot reply. Do I have to add a MIB path oder something else?
          landy Mike Stupalov added a comment -

          Did you add an incomplete snmp dump (as bot requested)?

          landy Mike Stupalov added a comment - Did you add an incomplete snmp dump (as bot requested)?
          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.

          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
            swfeldkirch Siegfried Gumilar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: