Follow-up Comment #1, sr #110940 (project freeipmi):
I had to research this as I had forgotten specifics.
Most vendors implement a "Physical Security" via the "physical security
chassis intrusion" specific sensor. See IPMI specification section 42.2 (just
a few lines down in table). Thus 0000h is "no intrusion" and != 0000h is one
of the different intrusions listed in that table.
It appears your vendor chose to do differently, implementing asserted vs
deasserted for the sensor. It has to always be set to asserted or deasserted
(0001h of 0002h).
While not as common, it's not wrong to do that.
I think the developer simply has to recognize that a different type of sensor
for "physical security" exists and handle it.
As an example, the ipmi-sensors --output-sensor-state option handles a wide
variety of "combos" that have been discovered over the years. It appears
"Physical Security" and "asserted/deasserted" is not yet supported, because
you're the first one to report it :P I'll add it to my TODO list.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110940>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
