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

On the new Aruba 2930F en some older switches temperature sensor doesn't work anymore

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Alerting

    Description

      The temperature sensor for the Aruba 2930F series switches en some other switches doesn't work anymore. about one and half months ago I updated Observium to the newest version, after that the sensory couldn't read anymore the temperature. I updated this week to newest version again and it still doesn't work.

      Attachments

        1. 2020-07-10_11-47-07.png
          2020-07-10_11-47-07.png
          197 kB
        2. 2930F_debugs.zip
          579 kB
        3. screenshot-1.png
          screenshot-1.png
          67 kB

        Activity

          [OBS-3403] On the new Aruba 2930F en some older switches temperature sensor doesn't work anymore
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

          Just note, you use firmware WC.16.07.0003.

          Latest in this series is WC.16.07.000*6*, and newest is WC.16.10.0009

          landy Mike Stupalov added a comment - Just note, you use firmware WC.16.07.0003. Latest in this series is WC.16.07.000*6*, and newest is WC.16. 10 .0009
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Fixed in r10608.

          landy Mike Stupalov added a comment - Fixed in r10608.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
          landy Mike Stupalov made changes -
          Status Original: In Progress [ 3 ] New: Pending Response [ 10000 ]

          Ok, As I see this is vendor firmware (or hardware trouble).
          Device report all temperetature (and some other) sensors as 0, see hpicfPsTemp:

          POWERSUPPLY-MIB::hpicfPsState.1 = INTEGER: psPowered(3)
          POWERSUPPLY-MIB::hpicfPsState.2 = INTEGER: psPowered(3)
          POWERSUPPLY-MIB::hpicfPsFailures.1 = Counter32: 0
          POWERSUPPLY-MIB::hpicfPsFailures.2 = Counter32: 0
          POWERSUPPLY-MIB::hpicfPsTemp.1 = INTEGER: 0
          POWERSUPPLY-MIB::hpicfPsTemp.2 = INTEGER: 0
          POWERSUPPLY-MIB::hpicfPsVoltageInfo.1 = STRING: AC 120V/240V
          POWERSUPPLY-MIB::hpicfPsVoltageInfo.2 = STRING: AC 120V/240V
          POWERSUPPLY-MIB::hpicfPsWattageCur.1 = INTEGER: 0
          POWERSUPPLY-MIB::hpicfPsWattageCur.2 = INTEGER: 0
          POWERSUPPLY-MIB::hpicfPsWattageMax.1 = INTEGER: 65
          POWERSUPPLY-MIB::hpicfPsWattageMax.2 = INTEGER: 65
          POWERSUPPLY-MIB::hpicfPsLastCall.1 = Counter32: 964244386
          POWERSUPPLY-MIB::hpicfPsLastCall.2 = Counter32: 964244386
          POWERSUPPLY-MIB::hpicfPsModel.1 = STRING: Not Av...
          POWERSUPPLY-MIB::hpicfPsModel.2 = STRING: Not Av...

          indirectly, this is confirmed by the fact that the power supply model is not correctly determined (see hpicfPsModel).
          I will add ignore 0 (zero) values, but correctly is write to Vendor support (or check new firmware).

          Seems as you not only updated Observium, but devices firmware too

          landy Mike Stupalov added a comment - Ok, As I see this is vendor firmware (or hardware trouble). Device report all temperetature (and some other) sensors as 0, see hpicfPsTemp : POWERSUPPLY-MIB::hpicfPsState.1 = INTEGER: psPowered(3) POWERSUPPLY-MIB::hpicfPsState.2 = INTEGER: psPowered(3) POWERSUPPLY-MIB::hpicfPsFailures.1 = Counter32: 0 POWERSUPPLY-MIB::hpicfPsFailures.2 = Counter32: 0 POWERSUPPLY-MIB::hpicfPsTemp.1 = INTEGER: 0 POWERSUPPLY-MIB::hpicfPsTemp.2 = INTEGER: 0 POWERSUPPLY-MIB::hpicfPsVoltageInfo.1 = STRING: AC 120V/240V POWERSUPPLY-MIB::hpicfPsVoltageInfo.2 = STRING: AC 120V/240V POWERSUPPLY-MIB::hpicfPsWattageCur.1 = INTEGER: 0 POWERSUPPLY-MIB::hpicfPsWattageCur.2 = INTEGER: 0 POWERSUPPLY-MIB::hpicfPsWattageMax.1 = INTEGER: 65 POWERSUPPLY-MIB::hpicfPsWattageMax.2 = INTEGER: 65 POWERSUPPLY-MIB::hpicfPsLastCall.1 = Counter32: 964244386 POWERSUPPLY-MIB::hpicfPsLastCall.2 = Counter32: 964244386 POWERSUPPLY-MIB::hpicfPsModel.1 = STRING: Not Av... POWERSUPPLY-MIB::hpicfPsModel.2 = STRING: Not Av... indirectly, this is confirmed by the fact that the power supply model is not correctly determined (see hpicfPsModel ). I will add ignore 0 (zero) values, but correctly is write to Vendor support (or check new firmware). Seems as you not only updated Observium, but devices firmware too
          landy Mike Stupalov made changes -
          Issue Type Original: Bug [ 1 ] New: Vendor Bug [ 10000 ]
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
          landy Mike Stupalov made changes -
          Assignee Original: Adam Armstrong [ adama ] New: Mike Stupalov [ landy ]

          People

            landy Mike Stupalov
            dghjfsg Henk-Jan Dennenberg
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: