Re: IPMI and Redfish support in openbmc Linux

Re: IPMI and Redfish support in openbmc Linux

[Henbin Chang]

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

H Ed,
I built bmcweb into my machine, and check the 'bmcweb' daemon was started
up.

ps aux | grep bmcweb
  919 root       0:00 /usr/bin/bmcweb
 8662 root       0:00 grep bmcweb

But I couldn't access Redfish API through the below command.
curl -b cjar -k https://10.99.241.79/redvish/v1/

Could you help provide the suggestion?

Thanks.
-Henbin.

There are several servers that support Redfish, and we have a working group
> that meets weekly to talk through technical issues each week, which you're
> welcome to attend. The only one checked into the upstream project is
> bmcweb. If you need help getting it started, I'm happy to help.
> https://github.com/openbmc/bmcweb

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

Re: IPMI and Redfish support in openbmc Linux

[Ratan Gupta]

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

Hi Henbin,

Can you try "curl -b cjar -k https://<ip>:*18080*/redfish/v1"?

Ratan Gupta


On Tuesday 10 July 2018 10:06 AM, Henbin Chang wrote:
> H Ed,
> I built bmcweb into my machine, and check the 'bmcweb' daemon was 
> started up.
>
> ps aux | grep bmcweb
>   919 root       0:00 /usr/bin/bmcweb
>  8662 root       0:00 grep bmcweb
>
> But I couldn't access Redfish API through the below command.
> curl -b cjar -k https://10.99.241.79/redvish/v1/
>
> Could you help provide the suggestion?
>
> Thanks.
> -Henbin.
>
>     There are several servers that support Redfish, and we have a
>     working group that meets weekly to talk through technical issues
>     each week, which you're welcome to attend. The only one checked
>     into the upstream project is bmcweb. If you need help getting it
>     started, I'm happy to help.
>     https://github.com/openbmc/bmcweb
>
>


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

Re: IPMI and Redfish support in openbmc Linux

[Hariharasubramanian Ramasubramanian]

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

"openbmc" <openbmc-bounces+hramasub=in.ibm.com@lists.ozlabs.org> wrote on 
07/10/2018 02:04:49 PM:


> 
> But I couldn't access Redfish API through the below command.
> curl -b cjar -k https://10.99.241.79/redvish/v1/
> 

1) Looks like you have a typo in the URI : It must be redfish and not 
redvish ?
2) Also try removing the trailing forward slash : redfish/v1 instead of 
redfish/v1/
3) Is the service running in the standard 443 port ? If not append the 
port number to the IP in the URI.

-Hari !


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

RE: IPMI and Redfish support in openbmc Linux

[Tanous, Ed]

Bmcweb will launch under one of two ports.  If launched manually, it will launch under port 18080.  If launched via systemd, it will use socket activation to launch under port 883 (to avoid conflicting with the existing phosphor-rest server).

Another thing to recognize is that there is a debug html interface built into the redfish interface, so the easiest way to test is to use a web browser, and you will get the graphical interface with clickable links.  Try pointing a web browser at https://10.99.241.79:18080/redfish/v1 and see if that works.

PS, the trailing backslash is unimportant.  Bmcweb is designed to strip the trailing backslash for you in either case, so redfish/v1 is the same as redfish/v1/

-Ed



From: openbmc [mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org] On Behalf Of Hariharasubramanian Ramasubramanian
Sent: Tuesday, July 10, 2018 2:21 AM
To: Ratan Gupta <ratagupt@linux.vnet.ibm.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: IPMI and Redfish support in openbmc Linux


"openbmc" <openbmc-bounces+hramasub=in.ibm.com@lists.ozlabs.org> wrote on 07/10/2018 02:04:49 PM:


> 
> But I couldn't access Redfish API through the below command.
> curl -b cjar -k https://10.99.241.79/redvish/v1/
> 

1) Looks like you have a typo in the URI : It must be redfish and not redvish ?
2) Also try removing the trailing forward slash : redfish/v1 instead of redfish/v1/
3) Is the service running in the standard 443 port ? If not append the port number to the IP in the URI.

-Hari !

Re: IPMI and Redfish support in openbmc Linux

[Henbin Chang]

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

Thank your support.

It did work after I used the default port 18080.
curl -k https://10.99.241.79:18080/redfish/v1

I had to indicate the account/password if I would like to access other node.
curl -k https://root:0penBmc@10.99.241.79:18080/redfish/v1/Managers/

Bmcweb will launch under one of two ports. If launched manually, it will
> launch under port 18080. If launched via systemd, it will use socket
> activation to launch under port 883 (to avoid conflicting with the existing
> phosphor-rest server). Another thing to recognize is that there is a debug
> html interface built into the redfish interface, so the easiest way to test
> is to use a web browser, and you will get the graphical interface with
> clickable links. Try pointing a web browser at
> https://10.99.241.79:18080/redfish/v1 and see if that works. PS, the
> trailing backslash is unimportant. Bmcweb is designed to strip the trailing
> backslash for you in either case, so redfish/v1 is the same as redfish/v1/
> -Ed



2018-07-10 16:39 GMT+08:00 Ratan Gupta <ratagupt@linux.vnet.ibm.com>:

> Hi Henbin,
>
> Can you try "curl -b cjar -k https://<ip>:18080/redfish/v1"?
>
> Seems default port is 18080
>
> https://github.com/openbmc/bmcweb/blob/master/src/webserver_main.cpp#L24
>
> Regards
>
> Ratan Gupta
>
>
>
> On Tuesday 10 July 2018 10:06 AM, Henbin Chang wrote:
>
> H Ed,
> I built bmcweb into my machine, and check the 'bmcweb' daemon was started
> up.
>
> ps aux | grep bmcweb
>   919 root       0:00 /usr/bin/bmcweb
>  8662 root       0:00 grep bmcweb
>
> But I couldn't access Redfish API through the below command.
> curl -b cjar -k https://10.99.241.79/redvish/v1/
>
> Could you help provide the suggestion?
>
> Thanks.
> -Henbin.
>
> There are several servers that support Redfish, and we have a working
>> group that meets weekly to talk through technical issues each week, which
>> you're welcome to attend. The only one checked into the upstream project is
>> bmcweb. If you need help getting it started, I'm happy to help.
>> https://github.com/openbmc/bmcweb
>
>
>
>

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

Re: IPMI and Redfish support in openbmc Linux

[Henbin Chang]

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

Hi Ed,

I upgraded my openbmc REPO with the Github and used the latest bmcweb
(commit id: 7885954af734ae61a2e1358740f84ad39248f18d.)

But I got the below error for compiling.
...
6: error: 'async_result_init' is not a member of 'boost::asio::detail'
     boost::asio::detail::async_result_init<
                          ^~~~~~~~~~~~~~~~~
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:84:26:
note: suggested alternative: 'async_result_helper'
     boost::asio::detail::async_result_init<
                          ^~~~~~~~~~~~~~~~~
                          async_result_helper
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:23:
error: expected primary-expression before ',' token
         MessageHandler, void(boost::system::error_code, message)>
                       ^
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:25:
error: expected primary-expression before 'void'
         MessageHandler, void(boost::system::error_code, message)>
...

Suppose this is because the boost-dbus is too old.

Do you any suggestion?

Thanks.


2018-07-12 8:05 GMT+08:00 Henbin Chang <henbinchang@gmail.com>:

> Thank your support.
>
> It did work after I used the default port 18080.
> curl -k https://10.99.241.79:18080/redfish/v1
>
> I had to indicate the account/password if I would like to access other
> node.
> curl -k https://root:0penBmc@10.99.241.79:18080/redfish/v1/Managers/
>
> Bmcweb will launch under one of two ports. If launched manually, it will
>> launch under port 18080. If launched via systemd, it will use socket
>> activation to launch under port 883 (to avoid conflicting with the existing
>> phosphor-rest server). Another thing to recognize is that there is a debug
>> html interface built into the redfish interface, so the easiest way to test
>> is to use a web browser, and you will get the graphical interface with
>> clickable links. Try pointing a web browser at
>> https://10.99.241.79:18080/redfish/v1 and see if that works. PS, the
>> trailing backslash is unimportant. Bmcweb is designed to strip the trailing
>> backslash for you in either case, so redfish/v1 is the same as redfish/v1/
>> -Ed
>
>
>
> 2018-07-10 16:39 GMT+08:00 Ratan Gupta <ratagupt@linux.vnet.ibm.com>:
>
>> Hi Henbin,
>>
>> Can you try "curl -b cjar -k https://<ip>:18080/redfish/v1"?
>>
>> Seems default port is 18080
>>
>> https://github.com/openbmc/bmcweb/blob/master/src/webserver_main.cpp#L24
>>
>> Regards
>>
>> Ratan Gupta
>>
>>
>>
>> On Tuesday 10 July 2018 10:06 AM, Henbin Chang wrote:
>>
>> H Ed,
>> I built bmcweb into my machine, and check the 'bmcweb' daemon was started
>> up.
>>
>> ps aux | grep bmcweb
>>   919 root       0:00 /usr/bin/bmcweb
>>  8662 root       0:00 grep bmcweb
>>
>> But I couldn't access Redfish API through the below command.
>> curl -b cjar -k https://10.99.241.79/redvish/v1/
>>
>> Could you help provide the suggestion?
>>
>> Thanks.
>> -Henbin.
>>
>> There are several servers that support Redfish, and we have a working
>>> group that meets weekly to talk through technical issues each week, which
>>> you're welcome to attend. The only one checked into the upstream project is
>>> bmcweb. If you need help getting it started, I'm happy to help.
>>> https://github.com/openbmc/bmcweb
>>
>>
>>
>>
>

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

RE: IPMI and Redfish support in openbmc Linux

[Tanous, Ed]

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

There have been quite a few changes to bmcweb in the last month, and some of the dependencies didn’t get synchronized like we expected them to.

The good news is that we’ve merged quite a few patches, including a number of new Redfish schemas, as well as the patch that moves bmcweb over to sdbusplus and beast.  Moving forward, we are going to deprecate boost-dbus, as sdbusplus now has a superset of functionality at this point in time.  The error you’re seeing is caused by boost-dbus not being updated to the interfaces used in boost 1.66, which was merged with the last yocto patch.

The bad news is that some of the sdbusplus patches for adding unit tests and fixing bugs has caused product regressions, and are holding up the merge of the recipe bump.  Because of the order in which the recipes got merged into upstream, bmcweb builds require the below recipe bump for the moment.

https://gerrit.openbmc-project.xyz/#/c/11456/

Checking out that patchset should let you build bmcweb against tip, and we’ll work on getting the regression squashed and fixes merged into mainline, hopefully shortly.

-Ed

From: Henbin Chang [mailto:henbinchang@gmail.com]
Sent: Wednesday, July 11, 2018 10:55 PM
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>; Tanous, Ed <ed.tanous@intel.com>
Subject: Re: IPMI and Redfish support in openbmc Linux

Hi Ed,

I upgraded my openbmc REPO with the Github and used the latest bmcweb (commit id: 7885954af734ae61a2e1358740f84ad39248f18d.)

But I got the below error for compiling.
...
6: error: 'async_result_init' is not a member of 'boost::asio::detail'
     boost::asio::detail::async_result_init<
                          ^~~~~~~~~~~~~~~~~
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:84:26: note: suggested alternative: 'async_result_helper'
     boost::asio::detail::async_result_init<
                          ^~~~~~~~~~~~~~~~~
                          async_result_helper
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:23: error: expected primary-expression before ',' token
         MessageHandler, void(boost::system::error_code, message)>
                       ^
/common/code_ref/s2600wf_openbmc/openbmc/build/tmp/work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:25: error: expected primary-expression before 'void'
         MessageHandler, void(boost::system::error_code, message)>
...

Suppose this is because the boost-dbus is too old.

Do you any suggestion?

Thanks.


2018-07-12 8:05 GMT+08:00 Henbin Chang <henbinchang@gmail.com<mailto:henbinchang@gmail.com>>:
Thank your support.

It did work after I used the default port 18080.
curl -k https://10.99.241.79:18080/redfish/v1

I had to indicate the account/password if I would like to access other node.
curl -k https://root:0penBmc@10.99.241.79:18080/redfish/v1/Managers/

Bmcweb will launch under one of two ports. If launched manually, it will launch under port 18080. If launched via systemd, it will use socket activation to launch under port 883 (to avoid conflicting with the existing phosphor-rest server). Another thing to recognize is that there is a debug html interface built into the redfish interface, so the easiest way to test is to use a web browser, and you will get the graphical interface with clickable links. Try pointing a web browser at https://10.99.241.79:18080/redfish/v1 and see if that works. PS, the trailing backslash is unimportant. Bmcweb is designed to strip the trailing backslash for you in either case, so redfish/v1 is the same as redfish/v1/ -Ed


2018-07-10 16:39 GMT+08:00 Ratan Gupta <ratagupt@linux.vnet.ibm.com<mailto:ratagupt@linux.vnet.ibm.com>>:

Hi Henbin,

Can you try "curl -b cjar -k https://<ip>:18080/redfish/v1<https://%3cip%3e:18080/redfish/v1>"?

Seems default port is 18080

https://github.com/openbmc/bmcweb/blob/master/src/webserver_main.cpp#L24

Regards

Ratan Gupta



On Tuesday 10 July 2018 10:06 AM, Henbin Chang wrote:
H Ed,
I built bmcweb into my machine, and check the 'bmcweb' daemon was started up.

ps aux | grep bmcweb
  919 root       0:00 /usr/bin/bmcweb
 8662 root       0:00 grep bmcweb

But I couldn't access Redfish API through the below command.
curl -b cjar -k https://10.99.241.79/redvish/v1/

Could you help provide the suggestion?

Thanks.
-Henbin.

There are several servers that support Redfish, and we have a working group that meets weekly to talk through technical issues each week, which you're welcome to attend. The only one checked into the upstream project is bmcweb. If you need help getting it started, I'm happy to help.
https://github.com/openbmc/bmcweb





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

Re: IPMI and Redfish support in openbmc Linux

[Henbin Chang]

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

 Understood.

Thanks Ed's response.

2018-07-13 1:57 GMT+08:00 Tanous, Ed <ed.tanous@intel.com>:

> There have been quite a few changes to bmcweb in the last month, and some
> of the dependencies didn’t get synchronized like we expected them to.
>
>
>
> The good news is that we’ve merged quite a few patches, including a number
> of new Redfish schemas, as well as the patch that moves bmcweb over to
> sdbusplus and beast.  Moving forward, we are going to deprecate boost-dbus,
> as sdbusplus now has a superset of functionality at this point in time.
> The error you’re seeing is caused by boost-dbus not being updated to the
> interfaces used in boost 1.66, which was merged with the last yocto patch.
>
>
>
> The bad news is that some of the sdbusplus patches for adding unit tests
> and fixing bugs has caused product regressions, and are holding up the
> merge of the recipe bump.  Because of the order in which the recipes got
> merged into upstream, bmcweb builds require the below recipe bump for the
> moment.
>
>
>
> https://gerrit.openbmc-project.xyz/#/c/11456/
>
>
>
> Checking out that patchset should let you build bmcweb against tip, and
> we’ll work on getting the regression squashed and fixes merged into
> mainline, hopefully shortly.
>
>
>
> -Ed
>
>
>
> *From:* Henbin Chang [mailto:henbinchang@gmail.com]
> *Sent:* Wednesday, July 11, 2018 10:55 PM
> *To:* OpenBMC Maillist <openbmc@lists.ozlabs.org>; Tanous, Ed <
> ed.tanous@intel.com>
> *Subject:* Re: IPMI and Redfish support in openbmc Linux
>
>
>
> Hi Ed,
>
>
>
> I upgraded my openbmc REPO with the Github and used the latest bmcweb
> (commit id: 7885954af734ae61a2e1358740f84ad39248f18d.)
>
>
>
> But I got the below error for compiling.
>
> ...
>
> 6: error: 'async_result_init' is not a member of 'boost::asio::detail'
>
>      boost::asio::detail::async_result_init<
>
>                           ^~~~~~~~~~~~~~~~~
>
> /common/code_ref/s2600wf_openbmc/openbmc/build/tmp/
> work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+
> gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:84:26:
> note: suggested alternative: 'async_result_helper'
>
>      boost::asio::detail::async_result_init<
>
>                           ^~~~~~~~~~~~~~~~~
>
>                           async_result_helper
>
> /common/code_ref/s2600wf_openbmc/openbmc/build/tmp/
> work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+
> gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:23:
> error: expected primary-expression before ',' token
>
>          MessageHandler, void(boost::system::error_code, message)>
>
>                        ^
>
> /common/code_ref/s2600wf_openbmc/openbmc/build/tmp/
> work/armv6-openbmc-linux-gnueabi/boost-dbus/1.0+
> gitAUTOINC+2ec8037525-r0/git/include/dbus/connection_service.hpp:85:25:
> error: expected primary-expression before 'void'
>
>          MessageHandler, void(boost::system::error_code, message)>
>
> ...
>
>
>
> Suppose this is because the boost-dbus is too old.
>
>
>
> Do you any suggestion?
>
>
>
> Thanks.
>
>
>
>
>
> 2018-07-12 8:05 GMT+08:00 Henbin Chang <henbinchang@gmail.com>:
>
> Thank your support.
>
>
>
> It did work after I used the default port 18080.
>
> curl -k https://10.99.241.79:18080/redfish/v1
>
>
>
> I had to indicate the account/password if I would like to access other
> node.
>
> curl -k https://root:0penBmc@10.99.241.79:18080/redfish/v1/Managers/
>
>
>
> Bmcweb will launch under one of two ports. If launched manually, it will
> launch under port 18080. If launched via systemd, it will use socket
> activation to launch under port 883 (to avoid conflicting with the existing
> phosphor-rest server). Another thing to recognize is that there is a debug
> html interface built into the redfish interface, so the easiest way to test
> is to use a web browser, and you will get the graphical interface with
> clickable links. Try pointing a web browser at https://10.99.241.79:18080/
> redfish/v1 and see if that works. PS, the trailing backslash is
> unimportant. Bmcweb is designed to strip the trailing backslash for you in
> either case, so redfish/v1 is the same as redfish/v1/ -Ed
>
>
>
>
>
> 2018-07-10 16:39 GMT+08:00 Ratan Gupta <ratagupt@linux.vnet.ibm.com>:
>
> Hi Henbin,
>
> Can you try "curl -b cjar -k https://<ip>:18080/redfish/v1"?
>
> Seems default port is 18080
>
> https://github.com/openbmc/bmcweb/blob/master/src/webserver_main.cpp#L24
>
> Regards
>
> Ratan Gupta
>
>
>
>
>
> On Tuesday 10 July 2018 10:06 AM, Henbin Chang wrote:
>
> H Ed,
>
> I built bmcweb into my machine, and check the 'bmcweb' daemon was started
> up.
>
>
>
> ps aux | grep bmcweb
>
>   919 root       0:00 /usr/bin/bmcweb
>
>  8662 root       0:00 grep bmcweb
>
>
>
> But I couldn't access Redfish API through the below command.
>
> curl -b cjar -k https://10.99.241.79/redvish/v1/
>
>
>
> Could you help provide the suggestion?
>
>
>
> Thanks.
>
> -Henbin.
>
>
>
> There are several servers that support Redfish, and we have a working
> group that meets weekly to talk through technical issues each week, which
> you're welcome to attend. The only one checked into the upstream project is
> bmcweb. If you need help getting it started, I'm happy to help.
> https://github.com/openbmc/bmcweb
>
>
>
>
>
>
>
>
>

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

RE: IPMI and Redfish support in openbmc Linux

[Tanous, Ed]

There is no KCS bridge merged with master yet, although I submitted one for code review last week.   Your best bet at making it available on master would be to provide review feedback to the Gerrit reviews below, which should help get it merged quickly.

https://gerrit.openbmc-project.xyz/#/c/10946/
https://gerrit.openbmc-project.xyz/#/c/10951/

Alternately, you can simply pull in those commits and add the phosphor-ipmi-kcs component to your build while it's in code review.  I already have a few reports of people having used it successfully. 

-Ed


From: openbmc [mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org] On Behalf Of Brad Chou
Sent: Sunday, June 3, 2018 10:39 PM
To: openbmc@lists.ozlabs.org
Subject: RE: IPMI and Redfish support in openbmc Linux

Hi Ed,
May I know how to use kcs with host ipmi ?
Any recipe need to be changed ?

Thanks.


On Jun 2, 2018, at 00:46, openbmc-request@lists.ozlabs.org wrote:

A subset of Ipmi 2.0 is provided by the Ipmi daemons here:
https://github.com/openbmc/phosphor-host-ipmid
https://github.com/openbmc/phosphor-net-ipmid

Net IPMI supports the out of band ipmi over network.  Host ipmi supports in band ipmi over kcs or block transfer.

There are several servers that support Redfish, and we have a working group that meets weekly to talk through technical issues each week, which you're welcome to attend.  The only one checked into the upstream project is bmcweb.  If you need help getting it started, I'm happy to help.
https://github.com/openbmc/bmcweb

Yes, ipmitool works compiles for the target, and includes an extra transport to be able to connect directly to dbus and do ipmi transactions from there.

-Ed

From: openbmc [mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org] On Behalf Of AKASH G J
Sent: Friday, June 1, 2018 2:23 AM
To: openbmc@lists.ozlabs.org
Subject: IPMI and Redfish support in openbmc Linux

Hi Team,

I build the Linux image using the steps given in https://github.com/openbmc/openbmc, target machine as Zaius. Whether support is available for IPMI 2.0 and Redfish interface? Is it possible to use ipmitool in the cross compiled Linux?

RE: IPMI and Redfish support in openbmc Linux

[Brad Chou]

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

Hi Ed,
May I know how to use kcs with host ipmi ?
Any recipe need to be changed ?

Thanks.

> On Jun 2, 2018, at 00:46, openbmc-request@lists.ozlabs.org wrote:
> 
> A subset of Ipmi 2.0 is provided by the Ipmi daemons here:
> https://github.com/openbmc/phosphor-host-ipmid <https://github.com/openbmc/phosphor-host-ipmid>
> https://github.com/openbmc/phosphor-net-ipmid <https://github.com/openbmc/phosphor-net-ipmid>
> 
> Net IPMI supports the out of band ipmi over network.  Host ipmi supports in band ipmi over kcs or block transfer.
> 
> There are several servers that support Redfish, and we have a working group that meets weekly to talk through technical issues each week, which you're welcome to attend.  The only one checked into the upstream project is bmcweb.  If you need help getting it started, I'm happy to help.
> https://github.com/openbmc/bmcweb <https://github.com/openbmc/bmcweb>
> 
> Yes, ipmitool works compiles for the target, and includes an extra transport to be able to connect directly to dbus and do ipmi transactions from there.
> 
> -Ed
> 
> From: openbmc [mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org <mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org>] On Behalf Of AKASH G J
> Sent: Friday, June 1, 2018 2:23 AM
> To: openbmc@lists.ozlabs.org <mailto:openbmc@lists.ozlabs.org>
> Subject: IPMI and Redfish support in openbmc Linux
> 
> Hi Team,
> 
> I build the Linux image using the steps given in https://github.com/openbmc/openbmc <https://github.com/openbmc/openbmc>, target machine as Zaius. Whether support is available for IPMI 2.0 and Redfish interface? Is it possible to use ipmitool in the cross compiled Linux?


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

RE: IPMI and Redfish support in openbmc Linux

[Tanous, Ed]

A subset of Ipmi 2.0 is provided by the Ipmi daemons here:
https://github.com/openbmc/phosphor-host-ipmid
https://github.com/openbmc/phosphor-net-ipmid

Net IPMI supports the out of band ipmi over network.  Host ipmi supports in band ipmi over kcs or block transfer.

There are several servers that support Redfish, and we have a working group that meets weekly to talk through technical issues each week, which you're welcome to attend.  The only one checked into the upstream project is bmcweb.  If you need help getting it started, I'm happy to help.
https://github.com/openbmc/bmcweb

Yes, ipmitool works compiles for the target, and includes an extra transport to be able to connect directly to dbus and do ipmi transactions from there.

-Ed

From: openbmc [mailto:openbmc-bounces+ed.tanous=intel.com@lists.ozlabs.org] On Behalf Of AKASH G J
Sent: Friday, June 1, 2018 2:23 AM
To: openbmc@lists.ozlabs.org
Subject: IPMI and Redfish support in openbmc Linux

Hi Team,

I build the Linux image using the steps given in https://github.com/openbmc/openbmc, target machine as Zaius. Whether support is available for IPMI 2.0 and Redfish interface? Is it possible to use ipmitool in the cross compiled Linux?

IPMI and Redfish support in openbmc Linux

[AKASH G J]

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

Hi Team,

I build the Linux image using the steps given in
https://github.com/openbmc/openbmc, target machine as *Zaius*. Whether
support is available for IPMI 2.0 and Redfish interface? Is it possible to
use ipmitool in the cross compiled Linux?

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