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

Cisco 9200 temperature sensors sensor_limit_low

Details

    • Vendor Bug
    • Resolution: Not A Bug
    • Minor
    • None
    • Enterprise Edition
    • Alerting, Poller
    • None

    Description

      We have a bunch of 9200 switches where the tempsensor_limit_low seems off
      Min warn is set at 31c, so naturally all our devices with that limit set will warn

      Attachments

        Activity

          [OBS-4075] Cisco 9200 temperature sensors sensor_limit_low

          Thanks, will do

          cheri001 Christian Eriksson added a comment - Thanks, will do

          Exactly for your case I suggest set Limits manually.

          landy Mike Stupalov added a comment - Exactly for your case I suggest set Limits manually.

          As I see this is just as device report limits for this sensor (exactly warning limit have index .1010.3):

          CISCO-ENTITY-SENSOR-MIB::entSensorType.1010 = INTEGER: celsius(8)
          CISCO-ENTITY-SENSOR-MIB::entSensorScale.1010 = INTEGER: units(9)
          CISCO-ENTITY-SENSOR-MIB::entSensorPrecision.1010 = INTEGER: 0
          CISCO-ENTITY-SENSOR-MIB::entSensorValue.1010 = INTEGER: 29
          CISCO-ENTITY-SENSOR-MIB::entSensorStatus.1010 = INTEGER: ok(1)
          CISCO-ENTITY-SENSOR-MIB::entSensorValueTimeStamp.1010 = Timeticks: (1) 0:00:00.01
          CISCO-ENTITY-SENSOR-MIB::entSensorValueUpdateRate.1010 = INTEGER: 600 seconds
          CISCO-ENTITY-SENSOR-MIB::entSensorMeasuredEntity.1010 = INTEGER: 1000
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.1 = INTEGER: major(20)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.2 = INTEGER: minor(10)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.3 = INTEGER: minor(10)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.4 = INTEGER: major(20)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.1 = INTEGER: greaterOrEqual(4)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.2 = INTEGER: greaterOrEqual(4)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.3 = INTEGER: lessOrEqual(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.4 = INTEGER: lessOrEqual(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.1 = INTEGER: 56
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.2 = INTEGER: 46
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.3 = INTEGER: 31
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.4 = INTEGER: -10
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.1 = INTEGER: false(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.2 = INTEGER: false(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.3 = INTEGER: false(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.4 = INTEGER: false(2)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.1 = INTEGER: true(1)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.2 = INTEGER: true(1)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.3 = INTEGER: true(1)
          CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.4 = INTEGER: true(1)
          

          I not see smart way for ignore this warning limit (without breaking set all other limits by this MIB).

          Actually this is Vendor firmware issue, you need write to Cisco TAC about this trouble.

          landy Mike Stupalov added a comment - As I see this is just as device report limits for this sensor (exactly warning limit have index .1010.3): CISCO-ENTITY-SENSOR-MIB::entSensorType.1010 = INTEGER: celsius(8) CISCO-ENTITY-SENSOR-MIB::entSensorScale.1010 = INTEGER: units(9) CISCO-ENTITY-SENSOR-MIB::entSensorPrecision.1010 = INTEGER: 0 CISCO-ENTITY-SENSOR-MIB::entSensorValue.1010 = INTEGER: 29 CISCO-ENTITY-SENSOR-MIB::entSensorStatus.1010 = INTEGER: ok(1) CISCO-ENTITY-SENSOR-MIB::entSensorValueTimeStamp.1010 = Timeticks: (1) 0:00:00.01 CISCO-ENTITY-SENSOR-MIB::entSensorValueUpdateRate.1010 = INTEGER: 600 seconds CISCO-ENTITY-SENSOR-MIB::entSensorMeasuredEntity.1010 = INTEGER: 1000 CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.1 = INTEGER: major(20) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.2 = INTEGER: minor(10) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.3 = INTEGER: minor(10) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdSeverity.1010.4 = INTEGER: major(20) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.1 = INTEGER: greaterOrEqual(4) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.2 = INTEGER: greaterOrEqual(4) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.3 = INTEGER: lessOrEqual(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdRelation.1010.4 = INTEGER: lessOrEqual(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.1 = INTEGER: 56 CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.2 = INTEGER: 46 CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.3 = INTEGER: 31 CISCO-ENTITY-SENSOR-MIB::entSensorThresholdValue.1010.4 = INTEGER: -10 CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.1 = INTEGER: false(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.2 = INTEGER: false(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.3 = INTEGER: false(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdEvaluation.1010.4 = INTEGER: false(2) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.1 = INTEGER: true(1) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.2 = INTEGER: true(1) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.3 = INTEGER: true(1) CISCO-ENTITY-SENSOR-MIB::entSensorThresholdNotificationEnable.1010.4 = INTEGER: true(1) I not see smart way for ignore this warning limit (without breaking set all other limits by this MIB). Actually this is Vendor firmware issue, you need write to Cisco TAC about this trouble.

          snmpwalk attached

          cheri001 Christian Eriksson added a comment - snmpwalk attached

          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
            cheri001 Christian Eriksson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: