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

Tycon device is not pulled

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Community Edition
    • OS
    • None
    • Tycon, Ubuntu 18.04.5

    Description

      Hi.

      I added a tycon device but I can't watch the sensors, ports, etc.... In the web page the TPDIN2-MIB is not available, but in the MIBS files in the server  it is.  What do I need to poll the device? 

      Thanks

      Attachments

        1. discovery Obs.txt
          47 kB
        2. poller Obs.txt
          74 kB
        3. snmpwalks obs.png
          snmpwalks obs.png
          10 kB

        Activity

          [OBS-3779] Tycon device is not pulled
          spect-jhdz spect-jhdz added a comment -

          Now, what I need to do? 

          I deleted the device and configure again but I still continue without watch the sensors and ports.

          spect-jhdz spect-jhdz added a comment - Now, what I need to do?  I deleted the device and configure again but I still continue without watch the sensors and ports.
          landy Mike Stupalov added a comment -

          Added in r11428.

          landy Mike Stupalov added a comment - Added in r11428.
          spect-jhdz spect-jhdz added a comment -

          Oh! ok, I just attach the snmpwalk file. 

          spect-jhdz spect-jhdz added a comment - Oh! ok, I just attach the snmpwalk file. 
          adama Adam Armstrong added a comment -

          The poller and discovery output is sort of useless for this purpose, we need the snmpwalks. You need to replace the community and hostname with the correct ones.

          there will be no output, it'll be in the myagent.snmpwalk file

          adama Adam Armstrong added a comment - The poller and discovery output is sort of useless for this purpose, we need the snmpwalks. You need to replace the community and hostname with the correct ones. there will be no output, it'll be in the myagent.snmpwalk file
          spect-jhdz spect-jhdz added a comment - - edited

          I already try to run the commands:

          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

          but, don't show any info. 

          And I attached the files with te results of discovery and poller commands. 

          The device is Tycon 

          spect-jhdz spect-jhdz added a comment - - edited I already try to run the commands: 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 but, don't show any info.  And I attached the files with te results of discovery and poller commands.  The device is Tycon 
          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.

          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
            spect-jhdz spect-jhdz
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: