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

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

Fixed in r10608.

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

good morning

seems this is a new sensor - all Aruba switches started showing PSUs since the last update. 

on the Aruba/HPE 3810M and 2930M devices this works very fine. 

on the 2930F, 2910al and 2540 devices it reports the wrong model/type for the PSU (HEX instead of letters) and 0 degree celsius. Throwing alarms for "out of threshold"

this is happening in professional (20.7.10549) and rolling ( 20.7.10586), too

attached diag from a HPE/Aruba 2930F stack on observium 20.7.10586 (rolling) - the one I can create easily.

2930F_debugs.zip

I will try to create the same from a 2540 on 20.7.10549 (stable) - as I don't have a 2930F on stable. (the 2540 is slow.. this takes a while)  

also from a 2920, there it shows 254 degrees Celsius with a high threshold of 406 degrees celsius.

I can also attach diag from a 2930M or a  where it works fine if that helps...  but they are all on customer locations so I need to check a couple things before I upload.

thanks, 

Andreas 

turnkey used very old version of observium, we not support them.

anyway, this commands should work in any distribution without errors, show screenshot with full command again.

I tried the commands you provided i still get the same output (Cannot find module).

I don't know why the commands doesn't work. (I used turnkey linux distribution)

Is there another option to get the information you need?

SNMP dump required (I can't check new Oids without it).
As I see, you missed options in snmpwalk line: -ObentxU

Copy-paste lines above and replace only <community> and <hostname>, by your screenshot, like this:

snmpwalk -v2c -c public  --hexOutputLength=0 -ObentxU 10.2.7.101 .1 > myagent.snmpwalk

snmpwalk -v2c -c public  --hexOutputLength=0 -ObentxU 10.2.7.101 .1.3.6.1.4.1 >> myagent.snmpwalk

I uploaded a screenshot. I tried the commands you provided, but it did not work.

I will add the MIB files

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> --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

Note, this comment is added automatically.