Details

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

    Description

      Add Padtec equipment to observium

      Attachments

        Activity

          [OBS-4099] Add Padtec to Observium

          Basic os detect added in r12575.

          landy Mike Stupalov added a comment - Basic os detect added in r12575.

          I got the os to detect with the attached include file.

          southfront Jason M Hanke added a comment - I got the os to detect with the attached include file.

          Looks like the Padtec MIB got added in r11999. The NMS is still getting detected as Generic.

          southfront Jason M Hanke added a comment - Looks like the Padtec MIB got added in r11999. The NMS is still getting detected as Generic.

          I saw padtec mib got added to observium rolling. I added the device back in and it detected as generic.

          It looks like they are returning an incorrect value for 

          .1.3.6.1.2.1.1.2.0 = OID: .1.3.6

          It should be something more like:

          .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.14846.1.11.1.1

          Is that correct?

          southfront Jason M Hanke added a comment - I saw padtec mib got added to observium rolling. I added the device back in and it detected as generic. It looks like they are returning an incorrect value for  .1.3.6.1.2.1.1.2.0 = OID: .1.3.6 It should be something more like: .1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.14846.1.11.1.1 Is that correct?

          Ok there was return stuff with that command [^myagent.snmpwalk]

          southfront Jason M Hanke added a comment - Ok there was return stuff with that command [^myagent.snmpwalk]

          hrm. last chance with this?

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

          I need to sure, that device complete not have support for any common MIB/Oid (except own).

          landy Mike Stupalov added a comment - hrm. last chance with this? snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6 > myagent.snmpwalk I need to sure, that device complete not have support for any common MIB/Oid (except own).

          Came back with a single line file

          .0.1 = No more variables left in this MIB View (It is past the end of the MIB tree)

          southfront Jason M Hanke added a comment - Came back with a single line file .0.1 = No more variables left in this MIB View (It is past the end of the MIB tree)
          landy Mike Stupalov added a comment - - edited

          It seems as snmpdump not full.
          Please try make it again with little different command:

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

          landy Mike Stupalov added a comment - - edited It seems as snmpdump not full. Please try make it again with little different command: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> . > myagent.snmpwalk

          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
            southfront Jason M Hanke
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: