Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery, Poller
    • None
    • Switch OS: Dell OS10 10.5.0.4
      Observium: 20.7.10549

    Description

      I have a Dell S3048 switch. Port 17 is connected to the dedicated management interface of a Dell S5232F. Both switches ahve the same OS and LLDP enabled.

      Observium shows the neighbour information for the S3048 correctly:

      Ethernet1/1/17 <-> S5232F mgmt/1/1/1

       

      However, the neighbour information for the S5232 is incorrect:

      Enternet1/1/7(down) <-> S3048 1/1/17

       

      (S5232 1/1/7 is a 100Gbe port that is not in use)

       

      I have rebooted the S5232 and re-run discovery and poller processes on it.

       

      Poller, discovery, and snmpwalks attached.

       

      Attachments

        1. 3048_discovery.txt
          262 kB
          Tom King
        2. 3048_poller.txt
          471 kB
          Tom King
        3. 5232_discovery.txt
          237 kB
          Tom King
        4. 5232_poller.txt
          333 kB
          Tom King
        5. lldp.PNG
          9 kB
          Tom King

        Activity

          [OBS-3406] LLDP neighbour incorrect

          Sure, fixed in r10601.

          landy Mike Stupalov added a comment - Sure, fixed in r10601.
          kingtrw Tom King added a comment -

          Thanks - that worked!

          All seems well now except there's a hangover of the incorrect information: In the Ports > Details view, in the last column (which shows connected devices) the 5232s still have an incorrect entry (screenshot attached).

          kingtrw Tom King added a comment - Thanks - that worked! All seems well now except there's a hangover of the incorrect information: In the Ports > Details view, in the last column (which shows connected devices) the 5232s still have an incorrect entry (screenshot attached).

          switch without https variant:

          svn switch http://svn.observium.org/svn/observium/trunk
          svn update

          Command will work after switch to rolling (not in stable):

          ./discovery.php -U 430

          after all rediscover S5232.

          landy Mike Stupalov added a comment - switch without https variant: svn switch http://svn.observium.org/svn/observium/trunk svn update Command will work after switch to rolling (not in stable): ./discovery.php -U 430 after all rediscover S5232.
          kingtrw Tom King added a comment -

          Thanks! I have updated MariaDB (Centos 7 uses 5.5 by default) using the process:

           

           

           # systemctl stop crond
           # systemctl stop httpd
           # systemctl stop mariadb
           # vim /etc/yum.repos.d/mariadb10.repo
           
          Use repo from
          https://downloads.mariadb.org/mariadb/repositories/
           
           # yum update
           # systemctl start mariadb
           # mysql_upgrade --user=root --password
          (using previously configured mysql root password)
           # reboot

           

          Obs still seems happy, but the update command you suggested just returns as 'up to date' for both database and obs.

          I'm also having trouble switching to the rolling branch:

           # svn switch https://svn.observium.org/svn/observium/trunk
          svn: E155025: 'http://svn.observium.org/svn/observium/branches/stable'
          is not the same repository as
          'https://svn.observium.org/svn'

          Now if I do svn update it says "At revision 10595." even though I'm still on 10549 - so I'm not sure what's happened here.

           

          kingtrw Tom King added a comment - Thanks! I have updated MariaDB (Centos 7 uses 5.5 by default) using the process:     # systemctl stop crond # systemctl stop httpd # systemctl stop mariadb # vim /etc/yum.repos.d/mariadb10.repo Use repo from https: //downloads.mariadb.org/mariadb/repositories/   # yum update # systemctl start mariadb # mysql_upgrade --user=root --password (using previously configured mysql root password) # reboot   Obs still seems happy, but the update command you suggested just returns as 'up to date' for both database and obs. I'm also having trouble switching to the rolling branch: # svn switch https: //svn.observium.org/svn/observium/trunk svn: E155025: 'http://svn.observium.org/svn/observium/branches/stable' is not the same repository as 'https://svn.observium.org/svn' Now if I do svn update it says "At revision 10595." even though I'm still on 10549 - so I'm not sure what's happened here.  

          Should be fixed in r10592.

          I see you use stable branch, currently fixed only in rolling, see here.

          Another trouble I found - you use unsupported (old) mariadb 5.5, minimum required version is MariaDB 10.0. Because of this, you have a problem with incorrect db Schema.

          SQL ERROR[Error in query: (Table 'observium.autodiscovery' doesn't exist) 1146]
          

          Please update if possible your MariaDB server and run force update db schema by:

          cd /opt/observium
          svn update
          ./discovery.php -U 430
          

          landy Mike Stupalov added a comment - Should be fixed in r10592. I see you use stable branch, currently fixed only in rolling, see here . Another trouble I found - you use unsupported (old) mariadb 5.5, minimum required version is MariaDB 10.0. Because of this, you have a problem with incorrect db Schema. SQL ERROR[Error in query: (Table 'observium.autodiscovery' doesn't exist) 1146] Please update if possible your MariaDB server and run force update db schema by: cd /opt/observium svn update ./discovery.php -U 430

          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
            kingtrw Tom King
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: