Setting sensor thresholds with ipmitool has flaws

[AlexanderAmelkin]

Reported by: Unknown User (*anonymous) Original Ticket: ipmitool/bugs/48

Execute set sensor threshold command to change only one of the thresholds of a sensor. As per IPMI specification, the comparison of thresholds must be in the order LNR < LC < LNC < sensor's reading < UNC < UC < UNR. So only after comparing the sensor's readings as above the status of the sensor is determined. But with the ipmitool 1.8.11, the status of the sensor changes even if one of the threshold changes.

Example: 1.[root@localhost ~]# ipmitool -H device_ip -U username -P password raw 4 0x26 1 0x20 1 2 3 0xf0 0xf1 4

2. [root@localhost ~]# ipmitool -H device_ip -U username -P password sdr voltage_33SBV | 3.32 Volts | nr Voltage_33V | 3.32 Volts | ok voltage_5V | 4.99 Volts | ok Voltage_VCC | 2.30 Volts | ok Fan_Presence | 0x01 | ok Temp_1 | 26 degrees C | ok Temp_2 | 26 degrees C | ok Fan_1 | 5000 RPM | ok Fan_2 | 5000 RPM | ok Fan_3 | 5000 RPM | ok Chassis_Intr | 0x01 | ok

As you can see from the step1, the byte 0x20 indicates that I'm going to set only upper non recoverable threshold and not upper critical and upper non critical values. Still sdr command shows the status of the sensor as Non recoverable (nr) even though UC and UNC values are higher than sensor readings. This applies to all combinations of threholds.

[AlexanderAmelkin]

This was posted by me before creating login id.

Original comment by: Unknown User (*anonymous)

[AlexanderAmelkin]

• assigned_to: Jim Mankovich
• Group: --> version-cvs

Original comment by: Zdenek Styblik

[AlexanderAmelkin]

Jim,

please, can you give this some thought? Is this still valid or has it been fixed by all those changes to SDR?

Thanks, Z.

Original comment by: Zdenek Styblik