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

Garbled output from CDP neighbours discovery

Details

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

    Description

      Hi,
      We see some garbled output specially from CDP from the neighbours discovery.
      Seems maybe the cdpCacheDeviceId is the macaddr in HEX ?
      This causes sql errors and excessive entries to the event log on every discovery.
      See the attached debug

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. OBS-3809 More garbled output from neighbours discovery

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-3672] Garbled output from CDP neighbours discovery
            kentbjoh Kent Johannessen added a comment -

            I see another device throwing things like this;
            SQL WARNINGS[: Incorrect string value: '\xACD"\x88\xEE' for column `observium`.`neighbours`.`remote_port` at row 1

            Also something to look at ? See attached

            kentbjoh Kent Johannessen added a comment - I see another device throwing things like this; SQL WARNINGS[: Incorrect string value: '\xACD"\x88\xEE' for column `observium`.`neighbours`.`remote_port` at row 1 Also something to look at ? See attached
            kentbjoh Kent Johannessen added a comment -

            Most excellent, thanks!

            kentbjoh Kent Johannessen added a comment - Most excellent, thanks!
            landy Mike Stupalov added a comment -

            Fixed in r11135.

            landy Mike Stupalov added a comment - Fixed in r11135.
            kentbjoh Kent Johannessen added a comment -

            attached

            kentbjoh Kent Johannessen added a comment - attached
            landy Mike Stupalov added a comment -

            Ouch, something new.. but in cisco style

            cdpCacheDeviceId.1.1 = ,Y.a..
            		 
            cdpCacheDeviceId.3.1 = .9....
            		 
            cdpCacheDeviceId.25.1 = ,Y.a..
            		 
            cdpCacheDeviceId.27.1 = .9....
            		 
            cdpCacheDeviceId.30.1 = 8<90><A5><A1><FE><80>
            		 
            cdpCacheDeviceId.31.1 = 8<90><A5><A1><FE><80>
            		 
            cdpCacheDeviceId.32.1 = 8<90><A5><A1><FE><80>

            please provide snmp dump as Bot requested

            landy Mike Stupalov added a comment - Ouch, something new.. but in cisco style cdpCacheDeviceId.1.1 = ,Y.a.. cdpCacheDeviceId.3.1 = .9.... cdpCacheDeviceId.25.1 = ,Y.a.. cdpCacheDeviceId.27.1 = .9.... cdpCacheDeviceId.30.1 = 8<90><A5><A1><FE><80> cdpCacheDeviceId.31.1 = 8<90><A5><A1><FE><80> cdpCacheDeviceId.32.1 = 8<90><A5><A1><FE><80> please provide snmp dump as Bot requested
            kentbjoh Kent Johannessen added a comment -

            Anymore info needed to continue? This is such annoying issue

            kentbjoh Kent Johannessen added a comment - Anymore info needed to continue? This is such annoying issue
            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
              kentbjoh Kent Johannessen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: