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

LLDP discovery wrong

Details

    • Vendor Bug
    • Resolution: Incomplete
    • Major
    • None
    • CE-22.5
    • Discovery, Web Interface
    • None

    Description

      On Observium 24.3.13371 (stable)

      192.168.100.244 Dell Networking N1548P

      192.168.100.240 HPE OfficeConnect Switch 1920S 48G 4SFP JL382A

      LLDP discovery data is wrong depending on view,  the connection actually goes from Gi1/0/1 to 14 on 192.168.100.240 as in the second picture.
      So there is a discrepancy between reality and sometimes from where you look.
      I have verified by looking directly in the switches, seen this error on some of our sites now so there is something fishy going on here ( otherwise it is an excellent piece of software )

      Is there any logs we can check or is it a bug ?
      We have not seen this error before, we just recently saw this.

      WRONG

       ** 

      CORRECT

      Attachments

        Activity

          [OBS-4789] LLDP discovery wrong
          landy Mike Stupalov added a comment -

          Not attached discovery debug and snmpdump.

          landy Mike Stupalov added a comment - Not attached discovery debug and snmpdump.
          adama Adam Armstrong added a comment -

          Likely yet another shitty vendor bug where they're returning off-by-one ifindexes and the like. not uncommon for lldp.

          No walks as requested by bot, so nothing we can do.

          adama Adam Armstrong added a comment - Likely yet another shitty vendor bug where they're returning off-by-one ifindexes and the like. not uncommon for lldp. No walks as requested by bot, so nothing we can do.
          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            nc_anders Anders Jönsson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: