openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sui Chen <suichen@google.com>
To: openbmc@lists.ozlabs.org
Subject: Re: 回覆: [phosphor-host-ipmid] Question about IPMI SDR
Date: Mon, 8 Nov 2021 18:48:47 -0800	[thread overview]
Message-ID: <91c35372-7329-a80c-8be0-3e9d79251fdc@google.com> (raw)
In-Reply-To: <DM6PR08MB5514160535BE1676DBC179E0DC919@DM6PR08MB5514.namprd08.prod.outlook.com>

On 11/8/21 3:37 AM, Chris Chen (TPI) wrote:
> Hi all,
> 
> I think I figured out the error message is due to the 
> phosphor-health-monitor package. The phosphor-health-monitor doesn't 
> have the interface of org.freedesktop.DBus.ObjectManager and with the 
> GetManagedObjects method call, so the getSensorMap() in the 
> intel-ipmi-oem would be failed.

Thanks for catching this, it seems there exists a change to make 
phosphor-health-monitor compatible with `ipmitool sdr`: 
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-health-monitor/+/41228

>  1.
>     is it only for monitoring CPU and memory sensor values?  it looks
>     like there is no explanation of it is in the phosphor-health-monitor
>     repo.

Yes it is for monitoring the BMC's CPU, memory and storage usage, and 
other metrics.

>  2.
>     can I remove it? If yes, will I miss any features?

Yes it is safe to remove, there are plans to use phosphor-health-monitor 
sensors in Redfish but the Schemas and bmcweb-side changes are still in 
progress, so you won't miss too many features for now.

  reply	other threads:[~2021-11-09  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08  4:01 [phosphor-host-ipmid] Question about IPMI SDR Chris Chen (TPI)
2021-11-08 11:37 ` 回覆: " Chris Chen (TPI)
2021-11-09  2:48   ` Sui Chen [this message]
2021-11-09  5:40     ` 回覆: " Chris Chen (TPI)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91c35372-7329-a80c-8be0-3e9d79251fdc@google.com \
    --to=suichen@google.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).