Post by mwalton on Aug 24, 2017 15:03:37 GMT
Hi All,
I'm a developer working on Redfish for our BMC and I'm in the process of implementing the log service for the BMC which renders the SEL entries.
The schema for LogEntry (redfish.dmtf.org/schemas/v1/LogEntry.v1_2_0.json) specifies the enumerations for SensorType and LogEntryCode which map all of the generic sensor types and event types for IPMI.
However the SensorType enumeration doesn't appear to allow for OEM types 0xC0 - 0xFF. Our system has a few OEM sensors, so if I translate the sensor type for SEL events for OEM sensors the Sensor Type field will fail JSON or CSDL schema validation as the value isn't in the supported list.
Similarly, for the LogEntryCode enumeration, it doesn't appear to allow for 'Sensor Specific' event types (which are defined in the IPMI specification) or OEM event types, so again if I translate the events the entry will fail schema validation.
The questions I have are as follows:
1. Is there a plan to extend these enumerations to cater for OEM sensor or events types, or add some other mechanism to allow them in the schema?
2. Since the 'Sensor Specific' events are defined in the IPMI specification, is there a plan to add support for at least these sensor specific events?
3. In lieu of points 1 and 2, is it reasonable to render the SensorType and LogEntryCode fields as NULL and instead use the OEM object (with reference to an OEM schema) to render the full range for our system, or is it more appropriate to render this into the Message/MessageId fields?
Thanks,
Mark
I'm a developer working on Redfish for our BMC and I'm in the process of implementing the log service for the BMC which renders the SEL entries.
The schema for LogEntry (redfish.dmtf.org/schemas/v1/LogEntry.v1_2_0.json) specifies the enumerations for SensorType and LogEntryCode which map all of the generic sensor types and event types for IPMI.
However the SensorType enumeration doesn't appear to allow for OEM types 0xC0 - 0xFF. Our system has a few OEM sensors, so if I translate the sensor type for SEL events for OEM sensors the Sensor Type field will fail JSON or CSDL schema validation as the value isn't in the supported list.
Similarly, for the LogEntryCode enumeration, it doesn't appear to allow for 'Sensor Specific' event types (which are defined in the IPMI specification) or OEM event types, so again if I translate the events the entry will fail schema validation.
The questions I have are as follows:
1. Is there a plan to extend these enumerations to cater for OEM sensor or events types, or add some other mechanism to allow them in the schema?
2. Since the 'Sensor Specific' events are defined in the IPMI specification, is there a plan to add support for at least these sensor specific events?
3. In lieu of points 1 and 2, is it reasonable to render the SensorType and LogEntryCode fields as NULL and instead use the OEM object (with reference to an OEM schema) to render the full range for our system, or is it more appropriate to render this into the Message/MessageId fields?
Thanks,
Mark
