[sr #110938] IPMI sensors on Cisco Server

[Albert Chu]

Follow-up Comment #1, sr #110938 (project freeipmi):

Hi,

I don't think there is a mistake.  Different motherboards may implement their
sensors differently than others.

It simply appears that your motherboard ouputs an "event" for open vs closed
(i.e. 0001h vs 0002h).  Whereas the software probably assumes closed means
h (i.e. "no event") and open means != h.

I think the software monitoring this motherboard would simply have to be
tweaked.

Al


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[sr #110938] IPMI sensors on Cisco Server

[anonymous]

URL:
  

 Summary: IPMI sensors on Cisco Server
   Group: GNU FreeIPMI
   Submitter: None
   Submitted: Mon 02 Oct 2023 07:13:29 AM UTC
Category: ipmi-sensors
Priority: 5 - Normal
Severity: 3 - Normal
  Status: None
 Privacy: Private
 Assigned to: None
Originator Email: k.cim...@yahoo.com
 Open/Closed: Open
 Discussion Lock: Any
Operating System: GNU/Linux


___

Follow-up Comments:


---
Date: Mon 02 Oct 2023 07:13:29 AM UTC By: Anonymous
Hello,
I have Cisco server C220 M5 with  Chassis Intrusion Switch - UCSC-INT-SW01 and
RedHat 8.0 installed on it.
Then I have software who uses ipmi-sensors to check for tamper, the software
is executing "ipmi-sensors -t Physical_Security --output-event-bitmask
--no-sensor-type-output --comma-separated-output --no-header-output | cut
-d',' -f5" and waiting for h result, but on this serveros I get 0001h(For
closed) and 0002h(For opened).
If i execut ipmi-sensors -t Physical_Security i get "180 | CHASSIS_OPEN |
Physical Security | N/A| N/A   | 'State Deasserted'" for closed server
and 'State Asserted' for opened server, I also see these events in logs. 
So maybe you got some advice about this situation and tell where is mistake.

Regards,
Kristians







___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/