IPMI SEL logs from phosphor-logging

[George Hung (洪忠敬)]

Hi Lei,

It can work now.

# ipmitool sel list
   1 | 06/24/21 | 10:28:13 UTC | Watchdog2 #0xfb | Hard reset | Asserted
   2 | 06/24/21 | 10:29:01 UTC | System Event #0xfe | Undetermined system hardware failure | Asserted


Thanks a lot for your suggestion.

Best Regards
George Hung

>-----Original Message-----
>From: openbmc
><openbmc-bounces+george.hung=quantatw.com at lists.ozlabs.org> On Behalf
>Of Lei YU
>Sent: Thursday, June 24, 2021 4:51 PM
>To: George Hung (洪忠敬) <George.Hung at quantatw.com>
>Cc: openbmc at lists.ozlabs.org; yulei.sh at bytedance.com; Fran Hsu (徐誌謙)
><Fran.Hsu at quantatw.com>; Brandon Kim <brandonkim at google.com>
>Subject: Re: IPMI SEL logs from phosphor-logging
>
>On Thu, Jun 24, 2021 at 1:21 PM George Hung (洪忠敬)
><George.Hung at quantatw.com> wrote:
>>
>> Hi Lei,
>>
>> I enable SEL_LOGGER_SEND_TO_LOGGING_SERVICE option for
>phosphor-sel-logger and then would generate IPMI SEL logs from
>phosphor-logging successfully.
>>
>> But the phosphor-logging still has other events issued from elog function
>and also put them in the "/var/lib/phosphor-logging/errors" directory.
>>
>> For example:
>>
>> 00000000  03 00 00 00 03 00 00 00  03 00 00 00 67 ff e6 38
>|............g..8|
>> 00000010  7a 01 00 00 32 00 00 00  00 00 00 00 78 79 7a 2e
>|z...2.......xyz.|
>> 00000020  6f 70 65 6e 62 6d 63 5f  70 72 6f 6a 65 63 74 2e
>|openbmc_project.|
>> 00000030  43 65 72 74 73 2e 45 72  72 6f 72 2e 49 6e 76 61
>> |Certs.Error.Inva|
>> 00000040  6c 69 64 43 65 72 74 69  66 69 63 61 74 65 01 00
>> |lidCertificate..|
>> 00000050  00 00 00 00 00 00 09 00  00 00 00 00 00 00 5f 50
>> |.............._P|
>> 00000060  49 44 3d 38 37 35 34 00  00 00 00 00 00 00 00 00
>> |ID=8754.........|
>> 00000070  19 00 00 00 00 00 00 00  76 33 2e 37 2e 30 2d 34
>> |........v3.7.0-4|
>> 00000080  2d 67 66 32 36 39 36 39  66 64 34 2d 64 69 72 74
>|-gf26969fd4-dirt|
>> 00000090  79 67 ff e6 38 7a 01 00  00                     |yg..8z...|
>> 00000099
>>
>> This event type is not IPMI System/OEM SEL, so "ipmitool sel elist" would
>result in the unspecified error:
>>
>> # ipmitool sel elist
>> Get SEL Entry 0 command failed: Unspecified error Get SEL Entry 0
>> command failed: Unspecified error
>>
>> How do you deal with these events that not belong to IPMI SEL logs ?
>
>Such logs are mapped to the system sensor as "Undetermined system
>hardware failure".
>e.g.
>
>  23 | 06/21/2021 | 06:26:35 | System Event #0xf0 | Undetermined system
>hardware failure | Asserted
>
>See
>https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>om%2Fopenbmc%2Fphosphor-host-ipmid%2Fblob%2Fmaster%2Fselutility.cpp
>%23L365&data=04%7C01%7Cgeorge.hung%40quantatw.com%7Cf68ba01
>df9e346e8e30608d936ed2fa3%7C179b032707fc4973ac738de7313561b2%7C1
>%7C0%7C637601215194095440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4
>wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&am
>p;sdata=phOO0fROGy4ibYIxmmzeXcE5tNnBKy5oyKft2E4PJAQ%3D&reserv
>ed=0
>for details.
>
>So you need to define the inventory sensor of
>"/xyz/openbmc_project/inventory/system" in the system's
>ipmi-inventory-sensors.yaml, then such events could be mapped to this
>inventory if there is no CALLOUT or no SEL metadata in the logging entry.