Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller
    • None
    • Tycon TPDIN Environmental Monitor

    Description

      Hi Mike,

       

      As discussed the Tycon TPDIN V1 is not reading correctly - let me know if you need more info.

       

      Sam

      Attachments

        1. observium tycon tpdin.png
          observium tycon tpdin.png
          25 kB
        2. Tycon snmp walk.png
          Tycon snmp walk.png
          36 kB
        3. Tycon TPDIN.png
          Tycon TPDIN.png
          12 kB
        4. tycontpdinv1.snmpwalk
          1 kB
        5. tycontpdinv11.snmpwalk
          1.0 kB

        Activity

          [OBS-3340] Tycon TPDIN

          not in stable, currently in trunk(rolling).
          All new additions by first released in trunk(rolling).

          landy Mike Stupalov added a comment - not in stable, currently in trunk(rolling). All new additions by first released in trunk(rolling).

          Hi Mike,

           

          Ive updated to 20.4.10371 (stable) and removed a test device and readded and it still appears to show with the old MIB. Is the support included in this version or will i need to change to something else?

           

          Thanks,

          Sam

          skoerner Sam Koerner added a comment - Hi Mike,   Ive updated to 20.4.10371 (stable) and removed a test device and readded and it still appears to show with the old MIB. Is the support included in this version or will i need to change to something else?   Thanks, Sam

          This device use same Oid tree as ServersCheck, but complete different MIB.

          Added support for Tycon device in r10430.
          (Need device rediscovery after update).

          landy Mike Stupalov added a comment - This device use same Oid tree as ServersCheck, but complete different MIB. Added support for Tycon device in r10430. (Need device rediscovery after update).

          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
            skoerner Sam Koerner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: