Proposal for operations on isolated hardware units using Redfish logging
Gunnar Mills
gmills at linux.vnet.ibm.com
Sat Dec 12 03:12:45 AEDT 2020
On 12/10/2020 10:29 AM, Ed Tanous wrote:
> On Thu, Dec 10, 2020 at 7:49 AM dhruvaraj S <dhruvaraj at gmail.com> wrote:
>>
>>
>> Listing isolated hardware units.
>> redfish >> v1 >> Systems >> system >> LogServices >> IsolatedHardware >> Entries
>> {
>> "@odata.id": "/redfish/v1/Systems/system/LogServices/IsolatedHardware/Entries",
>> "@odata.type": "#LogEntryCollection.LogEntryCollection",
>> "Description": "Collection of Isolated Hardware Components",
>> "Members": [
>> {
>> "@odata.id":
>> "/redfish/v1/Systems/system/LogServices/IsolatedHardware/Entries/1",
>> "@odata.type": "#LogEntry.v1_7_0.LogEntry",
>> "Created": "2020-10-15T10:30:08+00:00",
>> "EntryType": "Event",
>> "Id": "1",
>> "Resolved": "false",
>
> LogEntry doesn't have a "Resolved" field that I can see.
Part of Redfish's 2020.4. Matches OpenBMC's
https://github.com/openbmc/phosphor-dbus-interfaces/blob/05dd96872560bc6f11616be48b1873f539904142/xyz/openbmc_project/Logging/Entry.interface.yaml#L29
>
>> "Name": "Processor 1",
>> "links": {
>> "OriginOfCondition": {
>> "@odata.id":
>> "/redfish/v1/Systems/system/Processors/cpu1"
>> },
>> "Severity": "Critical",
>> "SensorType" : "Processor",
>
More information about the openbmc
mailing list