LogEntry Schema - EntryCode enum map with IPMI event code

AMI_Mani
Tuna

AMI

Posts: 178

LogEntry Schema - EntryCode enum map with IPMI event code Oct 29, 2019 18:42:18 GMT

Quote

Post by AMI_Mani on Oct 29, 2019 18:42:18 GMT

Hi ,

In IPMI Sel we have many Event code and when we map Processor Presence Detected to Entry code, getting below error in Redfish-Service-Validator
conformance report

ERROR - EntryCode: Invalid DeprecatedEnum value 'Processor Presence Detected' found, expected ['Assert', 'Deassert', 'Lower Non-critical - going low', 'Lower Non-critical - going high', 'Lower Critical - going low', 'Lower Critical - going high', 'Lower Non-recoverable - going low', 'Lower Non-recoverable - going high', 'Upper Non-critical - going low', 'Upper Non-critical - going high', 'Upper Critical - going low', 'Upper Critical - going high', 'Upper Non-recoverable - going low', 'Upper Non-recoverable - going high', 'Transition to Idle', 'Transition to Active', 'Transition to Busy', 'State Deasserted', 'State Asserted', 'Predictive Failure deasserted', 'Predictive Failure asserted', 'Limit Not Exceeded', 'Limit Exceeded', 'Performance Met', 'Performance Lags', 'Transition to OK', 'Transition to Non-Critical from OK', 'Transition to Critical from less severe', 'Transition to Non-recoverable from less severe', 'Transition to Non-Critical from more severe', 'Transition to Critical from Non-recoverable', 'Transition to Non-recoverable', 'Monitor', 'Informational', 'Device Removed / Device Absent', 'Device Inserted / Device Present', 'Device Disabled', 'Device Enabled', 'Transition to Running', 'Transition to In Test', 'Transition to Power Off', 'Transition to On Line', 'Transition to Off Line', 'Transition to Off Duty', 'Transition to Degraded', 'Transition to Power Save', 'Install Error', 'Fully Redundant', 'Redundancy Lost', 'Redundancy Degraded', 'Non-redundant:Sufficient Resources from Redundant', 'Non-redundant:Sufficient Resources from Insufficient Resources', 'Non-redundant:Insufficient Resources', 'Redundancy Degraded from Fully Redundant', 'Redundancy Degraded from Non-redundant', 'D0 Power State', 'D1 Power State', 'D2 Power State', 'D3 Power State', 'OEM']

Do we have any plan to add all IPMI events codes(e.g Processor, Memory etc) to EntryCode enum?

Thanks,
Mani

mraineri
Administrator

Posts: 1,138

LogEntry Schema - EntryCode enum map with IPMI event code Oct 31, 2019 14:32:55 GMT

Quote

Post by mraineri on Oct 31, 2019 14:32:55 GMT

The Event Data portion of the IPMI SEL does not end up as an enum for that case; that data is just put into the "MessageId" string as raw hex data (for the three Event Data bytes). EntryCode is meant to only convey the higher order generic event types (not the sensor type specific event codes in chapter 42.2).

Specifically for your event, I would expect "EntryCode" to be either "Assert" or "Deassert" (depending on the event direction), and "MessageId" contains the three Event Data bytes that will decode as "Processor Presence Detected".

AMI_Mani
Tuna

AMI

Posts: 178

LogEntry Schema - EntryCode enum map with IPMI event code Nov 13, 2019 17:38:11 GMT

Quote

Post by AMI_Mani on Nov 13, 2019 17:38:11 GMT

Hi,

Thanks for the information.
As per schema for MessageId it mentioned as This value is only used for registries - for more information, see the specification and referred to spec which is telling A string indicating a specific MessageId from the message registry. Since MessageId is a string can we add value as "Processor Presence Detected" or add value under description attribute as "Processor Presence Detected"

"MessageId": {
"description": "This property decodes from EntryType: If it is Event then it is a message id. Otherwise, it is SEL or Oem specific. This value is only used for registries - for more information, see the specification.",
"longDescription": "The value of this property shall the MessageId property of the event if the EntryType is Event, the EventData if EntryType is SEL and OEM Specific if the EntryType is OEM. The format of this property shall be as defined in the Redfish specification.",
"readonly": true,
"type": "string"
}

Thanks,
Mani

mraineri
Administrator

Posts: 1,138

LogEntry Schema - EntryCode enum map with IPMI event code Nov 15, 2019 13:07:33 GMT

Quote

Post by mraineri on Nov 15, 2019 13:07:33 GMT

That looks like an older version of the description. We have clarified it over time, and the latest version has that sentence removed. I vaguely remember an issue that was raised about that a while ago.

Here's the latest descriptions for that property:

"MessageId": {
    "description": "The MessageId, event data, or OEM-specific information.  This property decodes from the entry type.  If the entry type is `Event`, this property contains a Redfish Specification-defined MessageId.  If the entry type is `SEL`, this property contains the Event Data.  Otherwise, this property contains OEM-specific information.",
    "longDescription": "This property shall contain the MessageId, event data, or OEM-specific information.  This property decodes from the entry type.  If the entry type is `Event`, this property contains a Redfish Specification-defined MessageId property of the event.  If the entry type is `SEL`, this property contains the three IPMI Event Data bytes.  In this case, the format should follow the `^0[xX](([a-fA-F]|[0-9]){2}){3}$` pattern, where Event Data 1 is the first byte in the string, Event Data 2 is the second byte in the string, and Event Data 3 is the third byte in the string.  Otherwise, this property contains OEM-specific information.",
    "readonly": true,
    "type": "string"
},

AMI_Mani
Tuna

AMI

Posts: 178

LogEntry Schema - EntryCode enum map with IPMI event code Nov 15, 2019 20:03:03 GMT

Quote

Post by AMI_Mani on Nov 15, 2019 20:03:03 GMT

Hi,
Thanks for the details. Seems schema was updated in 1.8 specification and I will refer that
Do we have any link between Schema Version(bundle version like 2019.1, 2019.2) and Specification version(1.5, 1.6, 1.7). In Release Overview we are able to see Specification version(1.8) and corresponding schema bundle like 2019.2.

Is there any attribute to describe schema version like 2019.1 like Redfish version?
We can refer odata.context for schema version of that particular resource

Thanks,
Mani

mraineri
Administrator

Posts: 1,138

LogEntry Schema - EntryCode enum map with IPMI event code Nov 18, 2019 18:26:31 GMT

Quote

Post by mraineri on Nov 18, 2019 18:26:31 GMT

The schema bundle and specification are not really tied together; both can be updated independently. However, we tend to release both at the same time during our release cycles.

Implementations are not required to update their schemas to a given bundle; some implementations may just pick which schema files they'd like updates for, and leave other ones at older versions if they have no need for added functionality. "@odata.type" can be used to get the particular version of a resource; for example, "#LogEntry.v1_5_0.LogEntry" means the resource is following the LogEntry schema with version 1.4.0. We do document in the schema which release bundle the version was added though; you should see terms at the bottom of the schema file like this:

    "owningEntity": "DMTF",
    "release": "2019.3",
    "title": "#LogEntry.v1_5_0.LogEntry"
}

This was relatively new term we've been using in schema files (maybe in the last 18 months), so older schemas won't have the "release" term.

AMI_shirleyh
Guppy

Posts: 54

LogEntry Schema - EntryCode enum map with IPMI event code Nov 21, 2019 5:53:32 GMT

Quote

Post by AMI_shirleyh on Nov 21, 2019 5:53:32 GMT

We have a requirement here in which we want to specifically include one of the properties in the 2019.1 Schema of ManagerAccount version 1.3.0 in 2018.1 Schema bundle for RTP 1.5 Specification. So can we take this Schema alone and use this version in RTP 1.5 (2018.1 Schema bundle) ?

mraineri
Administrator

Posts: 1,138

LogEntry Schema - EntryCode enum map with IPMI event code Nov 21, 2019 15:44:13 GMT

Quote

Post by mraineri on Nov 21, 2019 15:44:13 GMT

Yes, that is perfectly legal to do. The service itself has a property within ServiceRoot to identify the protocol version of Redfish in which it conforms, and each resource independently identifies its schema version. So, you can mix the different combinations as you need to based on your own requirements for what needs to be supported for your service.

AMI_shirleyh Guppy Posts: 54	LogEntry Schema - EntryCode enum map with IPMI event code Nov 22, 2019 7:17:12 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by AMI_shirleyh on Nov 22, 2019 7:17:12 GMT Thanks for allowing this flexibility. Great...Yahoooo...

LogEntry Schema - EntryCode enum map with IPMI event code

Post by AMI_Mani on Oct 29, 2019 18:42:18 GMT

Post by mraineri on Oct 31, 2019 14:32:55 GMT

Post by AMI_Mani on Nov 13, 2019 17:38:11 GMT

Post by mraineri on Nov 15, 2019 13:07:33 GMT

Post by AMI_Mani on Nov 15, 2019 20:03:03 GMT

Post by mraineri on Nov 18, 2019 18:26:31 GMT

Post by AMI_shirleyh on Nov 21, 2019 5:53:32 GMT

Post by mraineri on Nov 21, 2019 15:44:13 GMT

Post by AMI_shirleyh on Nov 22, 2019 7:17:12 GMT