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

False positive on OS detection with newer firmware on switch

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • CE-22.5
    • Discovery
    •  Ubuntu 24.04.1 LTS (GNU/Linux 6.8.0-40-generic x86_64)

    Description

      I just recently deployed an Observium server to monitor the network.  So far it has been great and no issues adding devices.    I have a few Ruggedcom switches some with up to date FW and one that needs a FW update.    On the older FW v5.5 the device are discovered and added as a generic device.  With v5.7 Observium gives a false positive of a Wowza Streaming engine after what appears to be a re-detect.

       

      o Re-Detect OS matched (wowza-engine: Wowza Streaming Engine):

       

      I'm pretty new at this so hopefully someone can point me in the right direction on how to resolve the issue.   Attached are both 5.5 and 5.7 discovery debugs.

      Attachments

        Activity

          [OBS-4892] False positive on OS detection with newer firmware on switch

          Thanks so much for your help.

          Andrew MacLeod Andrew Neil macleod added a comment - Thanks so much for your help.
          landy Mike Stupalov made changes -
          Issue Type Original: Vendor Bug [ 10000 ] New: Add New Device / OS [ 10002 ]
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          This is new OS.

          Added support in r13651.

          landy Mike Stupalov added a comment - This is new OS. Added support in r13651.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
          landy Mike Stupalov made changes -
          Attachment Original: Walk timeout.txt [ 21441 ]
          landy Mike Stupalov made changes -
          Attachment Original: myagent.snmpwalk [ 21440 ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          landy Mike Stupalov added a comment - - edited

          Seems this device is shit...

          Oid three 1.3.6.1.4.1 required for vendor private entities.
          Try more vendor specific Oids (but exacly with all options):

          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-ent.snmpwalk
          

          if this still get timeout, try same with bulk option:

          snmpbulkwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-bulk.snmpwalk
          

          landy Mike Stupalov added a comment - - edited Seems this device is shit... Oid three 1.3.6.1.4.1 required for vendor private entities. Try more vendor specific Oids (but exacly with all options): snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-ent.snmpwalk if this still get timeout, try same with bulk option: snmpbulkwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.15004 > myagent-bulk.snmpwalk
          Andrew MacLeod Andrew Neil macleod added a comment - - edited

          The first command worked and is attached.  Second timed out.   A regular walk on that OID "snmpwalk -v2c -c <community> <host> .1.3.6.1.4.1" starts walking but eventually times out.  Attached the output.

           

           

          Andrew MacLeod Andrew Neil macleod added a comment - - edited The first command worked and is attached.  Second timed out.   A regular walk on that OID "snmpwalk -v2c -c <community> <host> .1.3.6.1.4.1" starts walking but eventually times out.  Attached the output.    
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]

          People

            landy Mike Stupalov
            Andrew MacLeod Andrew Neil macleod
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: