Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None

    Description

      Hi,

      Would it be possible to get a lldp discovered device like below automatically added in some way?

      SQL[SELECT `device_id` FROM `devices` WHERE `sysName` = '<FQDN>' AND `disabled` = '0']
      ROWS[0]
      SQL RUNTIME[0.00030303s]
      AUTODISCOVERY DEVEL: hostname & ip DB found

       > $db_entry /opt/observium/includes/discovery/functions.inc.php:636 
      array(
        [autodiscovery_id]      => string(4) "2967"
        [poller_id]             => string(1) "0"
        [device_id]             => string(3) "235"
        [remote_hostname]       => string(31) "<FQDN>"
        [remote_ip]             => string(7) "0.0.0.0"
        [remote_device_id]      => null
        [protocol]              => string(4) "LLDP"
        [added]                 => string(19) "2022-05-16 16:35:51"
        [last_checked]          => string(19) "2022-05-19 14:27:47"
        [last_reason]           => string(12) "no_ip_permit"
        [last_checked_unixtime] => string(10) "1652963267"
      )
      Remote device checked 26s ago (less than 1 day)
       o Trying to discover host <****> (0.0.0.0) through LLDP (xdp)
      <FQDN> passed with invalid IP (0.0.0.0), not permitted for autodiscovery.

      SQL[UPDATE `autodiscovery` set `last_checked` =CURRENT_TIMESTAMP() WHERE `autodiscovery_id` = '2967']
      ROWS[1]

      Real FQDN replaced with <FQDN>.

       

      It seems like we can't get passed the fact that discovery use remote_address or remote_ip (0.0.0.0), even thou remote_hostname value <FQDN> is resolvable.

      We can add device manually using <FQDN>.

      Is there any trick available to fix this?

       

      Best Regards
      Emil Vedin

      Attachments

        Activity

          [OBS-4117] Discover on hostname

          Should be improved in r12037.

          landy Mike Stupalov added a comment - Should be improved in r12037.
          landy Mike Stupalov added a comment - - edited

          you mean LLDP show correct hostname, but discover show incorrect IP address 0.0.0.0?

          Send me please discovery device (with LLDP neighbours) to my personal mail: mike@observium.org

          landy Mike Stupalov added a comment - - edited you mean LLDP show correct hostname, but discover show incorrect IP address 0.0.0.0? Send me please discovery device (with LLDP neighbours) to my personal mail: mike@observium.org
          eemived Emil Vedin added a comment -

          Hi,

          I forgot to edit away FQDN in one place, if you please can mask this in some way for me?

          Best Regards
          Emil Vedin

          eemived Emil Vedin added a comment - Hi, I forgot to edit away FQDN in one place, if you please can mask this in some way for me? Best Regards Emil Vedin

          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
            eemived Emil Vedin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: