回覆: [phosphor-host-ipmid] Questions about IPMI event message

[Chris Chen (TPI)]

Hi Andrei,

>>Disclaimer: here and below I talk only about file-based implementation
>>for logs.

>>It is known limitation. First of all, you should aware that there are
>>two completely different logs: Redfish Log and SEL log. When an
>>internal sensor triggers threshold event, two different messages are
>>sent: one for redfish log and another to SEL.

>>The sel-logger currently designed to only handle threshold events from
>>internal sensors, thus it requires dbus path to the sensor as an
>>argument for IpmiSelAdd.
>>When you send external IPMI event/SEL add message, ipmi daemon doesn't
>>know how to handle it. Instead, intel-ipmi-oem, tries to parse the
>>event according to some rules and if it fails just adds this weird
>>"OpenBMC.0.1.SELEntryAdded,2C0401300109FFFF" to the redfish log, saying
>>"we got some ipmi event, but we don't know what is it".
Now I get it. I have to say this explanation help me to understand more details. Thanks a lot.
Another, may I consult you other related questions? That is

  *   I had a question about "sel-logger" before, and Lei suggested I to enable "send-to-logger" option, does this have any relevance you mentioned above?
  *   I saw some companies have the xxx-yaml-config folder with "xxx-ipmi-sensors.yaml" etc. and also have the "entity-manager" folder with "xxx.json". But some companies only have "entity-manager" folder. So I would like to understand what differences they are? Should I need them both? I for now use "entity-manager" only.

>>I extended sel-logger with AddExt method, to store any random SEL entry
>>to /var/log/ipmi_sel, but this patches are for our internal Intel-BMC
>>fork and not applied for upstream version.
>>It is on my roadmap to update patches and submit them. If there is
>>demand for this work, I can try to prioritize it.
It definitely will be helpful for me if you are able to prioritize this feature.:)

Regards,
Chris Chen


________________________________
寄件者: Andrei Kartashev <a.kartashev at yadro.com>
寄件日期: 2021年11月3日 下午 10:06
收件者: Chris Chen (TPI) <Chris.Chen3 at flex.com>; openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>
主旨: Re: [phosphor-host-ipmid] Questions about IPMI event message


Hi Chris,

> So, I have 2 questions for this and hope someone who had experience
> with this could share ideas with me, I'll appreciate it:
>    1. Why the event doesn't appear in the "var/log/ipmi_sel" or can't
> be seen by using "ipmitool sel elist"? I expected it should appear.

Disclaimer: here and below I talk only about file-based implementation
for logs.

It is known limitation. First of all, you should aware that there are
two completely different logs: Redfish Log and SEL log. When an
internal sensor triggers threshold event, two different messages are
sent: one for redfish log and another to SEL.

The sel-logger currently designed to only handle threshold events from
internal sensors, thus it requires dbus path to the sensor as an
argument for IpmiSelAdd.
When you send external IPMI event/SEL add message, ipmi daemon doesn't
know how to handle it. Instead, intel-ipmi-oem, tries to parse the
event according to some rules and if it fails just adds this weird
"OpenBMC.0.1.SELEntryAdded,2C0401300109FFFF" to the redfish log, saying
"we got some ipmi event, but we don't know what is it".

I extended sel-logger with AddExt method, to store any random SEL entry
to /var/log/ipmi_sel, but this patches are for our internal Intel-BMC
fork and not applied for upstream version.
It is on my roadmap to update patches and submit them. If there is
demand for this work, I can try to prioritize it.

>    2. What does "Get SDR 0004 command failed: Invalid data field in
> request" mean?
>
> Things to Note:
>    1. The version of OprnBMC codebase I used is 2.10-rc1.
>    2. The image I built included "intel-ipmi-oem", "phosphor-logging",
> "phosphor-sel-logger", "rsyslog" and "entity-manager".
>
> Thank you.
>
> Regards,
> Chris Chen
> Legal Disclaimer :
> The information contained in this message may be privileged and
> confidential.
> It is intended to be read only by the individual or entity to whom it
> is addressed
> or by their designee. If the reader of this message is not the intended
> recipient,
> is strictly prohibited. If you have received this message in error,
> please immediately notify the sender and delete or destroy any copy of
> this message!

--
Best regards,
Andrei Kartashev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20211104/1a4b49c9/attachment-0001.htm>