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

Add the ability to view devices that were identified but failed to be added

Details

    • New Feature
    • Resolution: Fixed
    • Major
    • None
    • None
    • Web Interface

    Description

      One of the best features of Observium is automatic discovery by spidering a network using CDP/LLDP. However, the current implementation will only add a device if the discovered hostname matches a usable DNS name (or local hosts file).

      The web-interface needs a way to show admins which devices were identified during discovery, but then failed to be added for some reason. This information may already exist in the "Links" table.

      With this information, admins can correct the the problem and Observium will discover the fixed devices during the next discovery.

      Attachments

        Activity

          [OBS-1184] Add the ability to view devices that were identified but failed to be added

          Fixed in recent (rolling) versions.

          landy Mike Stupalov added a comment - Fixed in recent (rolling) versions.

          This is exacly what I am looing for, any progress on this?

          To be able to see if devices fail autodiscovery due to hostname not being resolvable or wrong SNMP community would be great(also to display the IP address)

          Under ports, neighbours I can filter on unknown devices but can't see the actual IP adress without logging into the local device and doing a "show....cdp/lldp details"

          Keep up the good work
          Regards

          cheri001 Christian Eriksson added a comment - This is exacly what I am looing for, any progress on this? To be able to see if devices fail autodiscovery due to hostname not being resolvable or wrong SNMP community would be great(also to display the IP address) Under ports, neighbours I can filter on unknown devices but can't see the actual IP adress without logging into the local device and doing a "show....cdp/lldp details" Keep up the good work Regards

          Just to be clear, I don't see how this is fixed?

          tristanrhodes Tristan Rhodes added a comment - Just to be clear, I don't see how this is fixed?

          Where is this information found on the web-interface? I am running Observium 0.15.2.6240.

          I did find a temporary work-around to get this information:

          1) Perform a debug discovery and save the output to a file > "output.log"
          2) Search that log for "autodiscovery fails".

          grep "autodiscovery fails" output.log

          This will give you the hostnames of the devices that failed discovery, perhaps because:

          "Host AVX5BE9F3 not resolved, autodiscovery fails."

          Actually, this will not help in many cases when the admin doesn't know the IP of that hostname. Observium needs to tell admins the "Management IP" that was gathered from xDP.

          tristanrhodes Tristan Rhodes added a comment - Where is this information found on the web-interface? I am running Observium 0.15.2.6240. I did find a temporary work-around to get this information: 1) Perform a debug discovery and save the output to a file > "output.log" 2) Search that log for "autodiscovery fails". grep "autodiscovery fails" output.log This will give you the hostnames of the devices that failed discovery, perhaps because: "Host AVX5BE9F3 not resolved, autodiscovery fails." Actually, this will not help in many cases when the admin doesn't know the IP of that hostname. Observium needs to tell admins the "Management IP" that was gathered from xDP.

          Fixed in r6239.

          landy Mike Stupalov added a comment - Fixed in r6239.

          People

            landy Mike Stupalov
            tristanrhodes Tristan Rhodes
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: