Hi,
I did notice that many of our supermicro servers were reporting the same
unknown event in the ipmi log:
$ /usr/local/Cellar/freeipmi/1.6.2/sbin/ipmi-sel -h *** -u *** -p ***
--output-oem-event-strings --interpret-oem-data -vvvv
ID | Date | Time | Name | Type | Event
Direction | Event
1 | Aug-04-2014 | 10:15:06 | Sensor #255 (Generator ID 20h) | Session Audit
| Assertion Event | Invalid Username or Password
2 | Aug-04-2014 | 10:15:16 | Sensor #255 (Generator ID 20h) | Session Audit
| Assertion Event | Invalid Username or Password
3 | Oct-09-2018 | 09:47:55 | Sensor #255 (Generator ID 1Fh) | OEM Reserved
| Assertion Event | Event Offset = 08h (Event Type Code = 6Fh)
$
Correlating this with the web interface shows that event 3, the OEM
Reserved would translate to sensor type "OOB" with the event "Activate
BIOS Product Key - Asserted".
The board in question is the following:
$ /usr/local/Cellar/freeipmi/1.6.2/sbin/bmc-info -h *** -u *** -p *** -l admin
Device ID : 32
Device Revision : 1
Device SDRs : unsupported
Firmware Revision : 3.47
Device Available : yes (normal operation)
IPMI Version : 2.0
Sensor Device : supported
SDR Repository Device : supported
SEL Device : supported
FRU Inventory Device : supported
IPMB Event Receiver : supported
IPMB Event Generator : supported
Bridge : unsupported
Chassis Device : supported
Manufacturer ID : Super Micro Computer Inc. (10876)
Product ID : 1583
Device GUID : 00000000-0000-0000-0000-000000000000
System GUID : 00000000-0e4e-d990-2500-534d31303037
ipmi_cmd_get_system_info_parameters_system_firmware_version_first_set:
privilege level insufficient
$
Maybe this is useful enough to include the appropriate mapping in the next
release.
cheers,
Andreas
_______________________________________________
Freeipmi-devel mailing list
Freeipmi-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/freeipmi-devel
