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

Extreme FabricEdge Devices is discovered as "Extremeware" -> Needs to be FabricEdge (VOSS-like)

Details

    • Improvement
    • Resolution: Fixed
    • Trivial
    • None
    • None
    • Default
    • None

    Description

      Hi,

       

      a extreme networks universal hardware 5420M is discovered as "Extremeware". But this device is running VOSS - the so called FabricEdge mode.

      Because of this, some things are missing in observium overview (like FDB usage) - the device can be discovered and polled as "VOSS" devices.

      Attachments

        Activity

          [OBS-4798] Extreme FabricEdge Devices is discovered as "Extremeware" -> Needs to be FabricEdge (VOSS-like)

          Should be fixed in r13449.

          landy Mike Stupalov added a comment - Should be fixed in r13449.

          i attached the snmpwalk

          FloMeyer Florian Meyer added a comment - i attached the snmpwalk

          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
            FloMeyer Florian Meyer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: