Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Default

    Description

      we found old and wrong entries as well in our observium database.
      1. When replacing a switch and rediscovering the device, the new details like "entPhysicalDescr" and Serialnumber will be added, but the old details will stay in the database. 
      2. after our last replacement, even the adding of the new details seems not be happend.
      how can we force the full rediscover without deleting and adding as a new device (we want to keep older metrics and graphs) and of course, cleaning up orphaned entries in the database

      I added two scrennshots from an DB export 

      Attachments

        Activity

          [OBS-4924] wrong entries in device database

          Hi again.

          we were able to mitigate topic #2 by just renaming the "old" device which was not completely discoverd and adding it new.
          the new discovery process of the new device recognized the device correctly.
          we can keep it this way, 

          the other topic with the "old" entries was my mistake, i overlooked the deleted flag. so we are fine here.

          nsoc@deutz.com Network & Security Operating Center DEUTZ AG added a comment - Hi again. we were able to mitigate topic #2 by just renaming the "old" device which was not completely discoverd and adding it new. the new discovery process of the new device recognized the device correctly. we can keep it this way,  the other topic with the "old" entries was my mistake, i overlooked the deleted flag. so we are fine here.

          Old entries remained in DB but with deleted flag (deleted field in db).

          Make and attach device debug discovery:

          ./discovery.php -d -h <device>
          

          landy Mike Stupalov added a comment - Old entries remained in DB but with deleted flag (deleted field in db). Make and attach device debug discovery: ./discovery.php -d -h <device>

          Hi again.
          Problem 1 is not really a problem, just a Layer8 mistake

          But for the second topic: it seems, that the device is not properly discovered or "linked" to the correct MIB 
          I added the same device new (with a different "name" and then it worked properly but then i will loose all historical data which i want to avoid.

          nsoc@deutz.com Network & Security Operating Center DEUTZ AG added a comment - Hi again. Problem 1 is not really a problem, just a Layer8 mistake But for the second topic: it seems, that the device is not properly discovered or "linked" to the correct MIB  I added the same device new (with a different "name" and then it worked properly but then i will loose all historical data which i want to avoid.

          People

            landy Mike Stupalov
            nsoc@deutz.com Network & Security Operating Center DEUTZ AG
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: