Details

    • Bug
    • Resolution: Fixed
    • Trivial
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      Observium uses the wrong MIB for fan speed on 'Aruba JL676A 6100 48G 4SFP+ Swch PL.10.09.0002' with ArubaOS-CX.

       

      Instead of 'ENTITY-SENSOR-MIB' you should use 'ARUBAWIRED-FAN-MIB::arubaWiredFanRPM' if a fan is present.

      Attachments

        Activity

          [OBS-4077] ArubaOS-CX wrong Fan MIB

          Already was fixed long time ago in r11696.

          landy Mike Stupalov added a comment - Already was fixed long time ago in r11696.

          You need create snmpdump as Bot written.

          We use by default common ENTITY-SENSOR-MIB, Because on all previously tested devices, all sensors were polled correctly.

          P.S. If you Enterprise customer, better to use mail for support: support@observium.org

          landy Mike Stupalov added a comment - You need create snmpdump as Bot written. We use by default common ENTITY-SENSOR-MIB, Because on all previously tested devices, all sensors were polled correctly. P.S. If you Enterprise customer, better to use mail for support: support@observium.org

          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
            itz Jens Brückner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: