On 08/16/10 20:07, Albert Chu:
In the fact, it would be better to use the function as part of
interpret-oem-data within ipmi-sel, but it require better knowledge of
current implementation of ipmi-sel than I have. Someone with better
skills may implement it (using the code from patch). Then I can help
with testing, if necessary.
I had intended to add this into ipmi-sel, but w/o a mobo to test on I
let it pass. If you're game to test a patch for me, I'd be glad to
implement it into ipmi-sel.
Yes, I can test patch. I can debug others code, so I can respond with
more meaningful responses than "it doesn't work as expected".
In advance, but there should be one spare computer - if I will found it
and then I will install OS on it then you may test it by self, if you
wish. But I must verify it's here.
I'm busy right now
As me. As almost anybody in the IT bussines ;-)
Short term, I think we can add this patch into ipmi-oem as an extra OEM
option for Fujitsu motherboards.
OK
BTW, what mobo are you running this on, so I can document in the future.
Here:
FRU Inventory Device: RDSA (ID 01h)
FRU OEM Manufacturer ID: Fujitsu Siemens Computers (2880h)
FRU OEM Code Mask: 00h 00h 00h 00h 00h 00h 00h 00h
FRU Inventory Device: Chassis (ID 02h)
FRU Chassis Type: Rack Mount Chassis
FRU Chassis Part Number: 9154Y01Z01G
...
FRU Chassis Custom Info: RX100S51
FRU Product Manufacturer Name: FSC
FRU Product Name: PRIMERGY RX100 S5
FRU Product Part/Model Number: ABN:K1160-V101-28
FRU Product Version: GS02
...
FRU Product Asset Tag: 15h
FRU FRU File ID: 70h
FRU Product Custom Info: 19h DFh 65h
FRU Product Custom Info: 0225
FRU Inventory Device: MainBoard (ID 03h)
FRU Chassis Type: Rack Mount Chassis
FRU Chassis Part Number: 9154Y01Z01G
...
FRU Chassis Custom Info: RX100S51
FRU Board Manufacturing Date/Time: 05/17/08 - 12:25:00
FRU Board Manufacturer: FSC
FRU Board Product Name: D2542
...
FRU Board Part Number: S26361-D2542-B10
FRU FRU File ID: 84h
FRU Board Custom Info: WGS02 GS02
FRU Board Custom Info: 02h
FRU Product Manufacturer Name: FSC
FRU Product Name: PRIMERGY RX100 S5
FRU Product Part/Model Number: ABN:K1160-V101-28
FRU Product Version: GS02
...
FRU Product Asset Tag: 15h
FRU FRU File ID: 70h
FRU Product Custom Info: 19h DFh 65h
FRU Product Custom Info: 0225
FRU Inventory Device: LocalView (ID 04h)
ipmi_fru_parse_open_device_id: internal IPMI error
Dan
The Fujitsu's iRMC has implemented proprietary function that return text
representation of SEL. It's important especially for OEM-Reserved
events. For example, the ipmi-sel show something like this:
ipmi-sel --interpret-oem-data --display=1008
ID | Date | Time | Name | Type |
Event
1008 | Dec-16-2009 | 15:40:29 | iRMC | OEM Reserved |
Event Offset = 00h ; OEM Event Data2 code = 83h ; OEM Event Data3 code = 4Dh
or
ipmi-sel --interpret-oem-data --display=1032
ID | Date | Time | Name | Type |
Event
1032 | Dec-16-2009 | 15:41:42 | iRMC | System Firmware Progress |
System Firmware Error ; Unspecified ; OEM Event Data3 code = 5Fh
utilising the OEM function we can get something like this:
ipmi-oem -- fujitsu get-sel-entry-long-text 1008
1008 | Dec-16-2009 | 15:40:29 | INFORMATIONAL: Online firmware flash EEPROM 2
Version 3.77
or
ipmi-oem -- fujitsu get-sel-entry-long-text 1032
1032 | Dec-16-2009 | 15:41:42 | Server Management Configuration NVRam bad,
default configuration is used
The implementation si based on (not so good) documentation:
http://*manuals.ts.fujitsu.com/file/4390/irmc-s2-ug-en.pdf
The patch that add the support for OEM/fujitsu/get-sel-entry-long-text
into ipmi-oem is attached. It's tested on iRMC with firmware 3.77
In the fact, it would be better to use the function as part of
interpret-oem-data within ipmi-sel, but it require better knowledge of
current implementation of ipmi-sel than I have. Someone with better
skills may implement it (using the code from patch). Then I can help
with testing, if necessary.
_______________________________________________
Freeipmi-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/freeipmi-devel
