Adding IPMI support to an existing implementation

Adding IPMI support to an existing implementation

[Wim Vervoorn]

Hello,

We have an existing AST2400 based implementation for OpenBMC 2.6.0 and are trying to add IPMI support to it.

At this moment we don't have a good set of documentation on the ipmi implementation included in OpenBMC.

Can anyone point me to this documentation? Or is the only way to do this to go over the various packages?

Best regards,

Wim Vervoorn

Re: Adding IPMI support to an existing implementation

[Vijay Khemka]

Hi Wim,
What are trying here, adding extra ipmi support for your oem commands? IPMI support is already there in phosphor-image. Please see if "ipmid" daemon is running. You can check package phosphor-ipmi-host which provides support for ipmi daemon.

Regards
-Vijay

On 2/15/19, 3:23 AM, "openbmc on behalf of Wim Vervoorn" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of wvervoorn@eltan.com> wrote:

    Hello,
    
    We have an existing AST2400 based implementation for OpenBMC 2.6.0 and are trying to add IPMI support to it.
    
    At this moment we don't have a good set of documentation on the ipmi implementation included in OpenBMC.
    
    Can anyone point me to this documentation? Or is the only way to do this to go over the various packages?
    
    Best regards,
    
    Wim Vervoorn
    

Re: Adding IPMI support to an existing implementation

[Wim Vervoorn]

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

At this point I'm not looking for additional OEM commands.

My main goal is just to add all support request to enable inband ipmi with KCS interface.  The most important thing is that the system is capable to provide the inventory and eventlog information to the BMC during boot.

The information I am looking for are items like. Which services need to be included and what do I need to configure to make it work.

Best regards,

Wim Vervoorn

Op 15 feb. 2019 9:31 p.m. schreef Vijay Khemka <vijaykhemka@fb.com>:
Hi Wim,
What are trying here, adding extra ipmi support for your oem commands? IPMI support is already there in phosphor-image. Please see if "ipmid" daemon is running. You can check package phosphor-ipmi-host which provides support for ipmi daemon.

Regards
-Vijay

On 2/15/19, 3:23 AM, "openbmc on behalf of Wim Vervoorn" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of wvervoorn@eltan.com> wrote:

    Hello,

    We have an existing AST2400 based implementation for OpenBMC 2.6.0 and are trying to add IPMI support to it.

    At this moment we don't have a good set of documentation on the ipmi implementation included in OpenBMC.

    Can anyone point me to this documentation? Or is the only way to do this to go over the various packages?

    Best regards,

    Wim Vervoorn



[-- Attachment #2: Type: text/html, Size: 2436 bytes --]

Re: Adding IPMI support to an existing implementation

[Emily Shaffer]

[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]

Wim,

phosphor-ipmi-host contains the inband implementation; kcsbridged provides
the KCS interface bridge. Start by making sure those packages are included
in your build; inventory and eventlog implementations are included within
phosphor-ipmi-host.

Emily

On Fri, Feb 15, 2019 at 11:19 PM Wim Vervoorn <wvervoorn@eltan.com> wrote:

> At this point I'm not looking for additional OEM commands.
>
> My main goal is just to add all support request to enable inband ipmi with
> KCS interface.  The most important thing is that the system is capable to
> provide the inventory and eventlog information to the BMC during boot.
>
> The information I am looking for are items like. Which services need to be
> included and what do I need to configure to make it work.
>
> Best regards,
>
> Wim Vervoorn
>
> Op 15 feb. 2019 9:31 p.m. schreef Vijay Khemka <vijaykhemka@fb.com>:
> Hi Wim,
> What are trying here, adding extra ipmi support for your oem commands?
> IPMI support is already there in phosphor-image. Please see if "ipmid"
> daemon is running. You can check package phosphor-ipmi-host which provides
> support for ipmi daemon.
>
> Regards
> -Vijay
>
> On 2/15/19, 3:23 AM, "openbmc on behalf of Wim Vervoorn"
> <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org on behalf of
> wvervoorn@eltan.com> wrote:
>
>     Hello,
>
>     We have an existing AST2400 based implementation for OpenBMC 2.6.0 and
> are trying to add IPMI support to it.
>
>     At this moment we don't have a good set of documentation on the ipmi
> implementation included in OpenBMC.
>
>     Can anyone point me to this documentation? Or is the only way to do
> this to go over the various packages?
>
>     Best regards,
>
>     Wim Vervoorn
>
>
>

[-- Attachment #2: Type: text/html, Size: 2886 bytes --]

RE: Adding IPMI support to an existing implementation

[Wim Vervoorn]

[-- Attachment #1: Type: text/plain, Size: 3106 bytes --]

Hello Emily,

Thanks. We added the ipmi-host and the kcsbridge and got it to work to some extend.

One issue we see is that Linux enters an endless loop trying to read the eventlog. I would expect this to stop when the eventlog is read (especially as there are no items).

Another thing we are running into is the fact that the system we have doesn’t have a FRU eeprom for the mainboard. Our initial thought was to upload the information using SetFru ipmi calls. Infortunately this is not supported in the current ipmi-host implementation.

What would be the correct approach for this. I am considering to put the FRU information for the mainboard in a file in the BMC and use this instead of the eeprom. Is this the correct approach and is this somehow supported already or should we implement this ourselves?

Thanks in advance for your input.

Best regards,

Wim Vervoorn




Verzonden vanuit Mail<https://go.microsoft.com/fwlink/?LinkId=550986> voor Windows 10

Van: Emily Shaffer<mailto:emilyshaffer@google.com>
Verzonden: dinsdag 19 februari 2019 20:44
Aan: Wim Vervoorn<mailto:wvervoorn@eltan.com>
CC: Vijay Khemka<mailto:vijaykhemka@fb.com>; openbmc@lists.ozlabs.org<mailto:openbmc@lists.ozlabs.org>
Onderwerp: Re: Adding IPMI support to an existing implementation

Wim,

phosphor-ipmi-host contains the inband implementation; kcsbridged provides the KCS interface bridge. Start by making sure those packages are included in your build; inventory and eventlog implementations are included within phosphor-ipmi-host.

Emily

On Fri, Feb 15, 2019 at 11:19 PM Wim Vervoorn <wvervoorn@eltan.com<mailto:wvervoorn@eltan.com>> wrote:
At this point I'm not looking for additional OEM commands.

My main goal is just to add all support request to enable inband ipmi with KCS interface.  The most important thing is that the system is capable to provide the inventory and eventlog information to the BMC during boot.

The information I am looking for are items like. Which services need to be included and what do I need to configure to make it work.

Best regards,

Wim Vervoorn

Op 15 feb. 2019 9:31 p.m. schreef Vijay Khemka <vijaykhemka@fb.com<mailto:vijaykhemka@fb.com>>:
Hi Wim,
What are trying here, adding extra ipmi support for your oem commands? IPMI support is already there in phosphor-image. Please see if "ipmid" daemon is running. You can check package phosphor-ipmi-host which provides support for ipmi daemon.

Regards
-Vijay

?On 2/15/19, 3:23 AM, "openbmc on behalf of Wim Vervoorn" <openbmc-bounces+vijaykhemka=fb.com@lists.ozlabs.org<mailto:fb.com@lists.ozlabs.org> on behalf of wvervoorn@eltan.com<mailto:wvervoorn@eltan.com>> wrote:

    Hello,

    We have an existing AST2400 based implementation for OpenBMC 2.6.0 and are trying to add IPMI support to it.

    At this moment we don't have a good set of documentation on the ipmi implementation included in OpenBMC.

    Can anyone point me to this documentation? Or is the only way to do this to go over the various packages?

    Best regards,

    Wim Vervoorn



[-- Attachment #2: Type: text/html, Size: 5953 bytes --]