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

ArubaOS-CX Temperature Warnings

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      The used temperature limits arubaWiredTempSensorMinTemp/arubaWiredTempSensorMaxTemp is wrong.

       

      The MIB says: "Historic minimum/maximum temperature of the temperature sensor."

       

      Instead we should use arubaWiredTempSensorStateNotification.

      Attachments

        1. oscx-temp1.jpg
          oscx-temp1.jpg
          159 kB
        2. oscx-temp2.jpg
          oscx-temp2.jpg
          234 kB

        Activity

          [OBS-4072] ArubaOS-CX Temperature Warnings
          itz Jens Brückner added a comment -

          I will ask the support if we are missing something. Thank you!

          itz Jens Brückner added a comment - I will ask the support if we are missing something. Thank you!
          landy Mike Stupalov added a comment -

          Disabled in r11925.

          landy Mike Stupalov added a comment - Disabled in r11925.
          landy Mike Stupalov added a comment -

          Yah, true.. arubaWiredTempSensorMaxTemp incorrect for use in limits.

          But really this device(s) not report anything else for limits..
          I can complete remove set auto limits for this sensor oid.

          arubaWiredTempSensorStateNotification is trap notification, not possible for use in snmpget.

          landy Mike Stupalov added a comment - Yah, true.. arubaWiredTempSensorMaxTemp incorrect for use in limits. But really this device(s) not report anything else for limits.. I can complete remove set auto limits for this sensor oid. arubaWiredTempSensorStateNotification is trap notification, not possible for use in snmpget.
          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
            itz Jens Brückner
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: