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

New Switch Engine (EXOS) devices are seen as Extremeware

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery, Poller, Web Interface
    • 25.1.13841 (rolling) (15th January 2025)

    Description

      Hello all,

      Recently we added 3 new models of Switch Engine (EXOS):

      • 7720 (running onie-32.7.1.9-patch1-49)
      • 5420 (running summit_arm-32.7.1.9-patch1-26)
      • 4220 (running summit_arm-32.7.1.9-patch1-26)

      All three are seen as "extremeware" instead of "exos".

      I think something changed on those new models that needs to be re-added on observium MIBS.

      Attached to the ticket a snmpwalk of each model and the MIB.

      Thanks.

      EM

      Attachments

        Activity

          [OBS-4974] New Switch Engine (EXOS) devices are seen as Extremeware
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          landy Mike Stupalov added a comment -

          Improved support in r13880.

          landy Mike Stupalov added a comment - Improved support in r13880.
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: In Progress [ 3 ]
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          emiliomejias Emilio MEJIAS 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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            emiliomejias Emilio MEJIAS
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: