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

Most of devices identified as generic after upgrade to 22.5.12042

Details

    • Help
    • Resolution: Not A Bug
    • Major
    • None
    • None
    • Discovery
    • None
    • Observium Community Edition 22.5.12042
      Linux|3.10.0-1160.15.2.el7.x86_64|amd64|CentOS|7|vmware|

    Description

      Good morning,

      After upgrading to version 22.5.12042, all of monitored devices turned to "Generic"

       

      Any help will be appreciated.

      Thanks.

      Jacob

      Attachments

        Activity

          [OBS-4126] Most of devices identified as generic after upgrade to 22.5.12042
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          landy Mike Stupalov made changes -
          Issue Type Original: Vendor Bug [ 10000 ] New: Help [ 10200 ]
          Resolution New: Not A Bug [ 6 ]
          Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]
          landy Mike Stupalov added a comment -

          Clean mibs indexes, follow this FAQ guide:
          https://docs.observium.org/faq/#all-my-hosts-seem-down-to-observium-snmp-doesnt-seem-to-work-anymore

          landy Mike Stupalov added a comment - Clean mibs indexes, follow this FAQ guide: https://docs.observium.org/faq/#all-my-hosts-seem-down-to-observium-snmp-doesnt-seem-to-work-anymore
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          ghattasjacob Jacob Ghattas created issue -
          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --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

          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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

          People

            landy Mike Stupalov
            ghattasjacob Jacob Ghattas
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: