Add BMCBootReason Redfish message
In order to demarcate separate FW boots within a continuous stream of
Redfish event logs, add a BMCBootReason message which is logged during
every BMC FW bootup. This message also provides the current FW version
string, as well as a reason describing why the boot happened (e.g. power
loss, user request, watchdog timeout).
Tested: Inserted message into journal using logger-systemd and observed
Redfish event at redfish/v1/Systems/system/LogServices/EventLog/Entries.
Change-Id: I0f0a10ebf300e1a9f2e18bb6735d95e96aeb8473
Signed-off-by: Jonathan Doman <jonathan.doman@intel.com>
diff --git a/redfish-core/include/registries/openbmc_message_registry.hpp b/redfish-core/include/registries/openbmc_message_registry.hpp
index 042a83a..0da82b1 100644
--- a/redfish-core/include/registries/openbmc_message_registry.hpp
+++ b/redfish-core/include/registries/openbmc_message_registry.hpp
@@ -29,7 +29,7 @@
"0.1.0",
"OpenBMC",
};
-constexpr std::array<MessageEntry, 183> registry = {
+constexpr std::array<MessageEntry, 184> registry = {
MessageEntry{
"ADDDCCorrectable",
{
@@ -226,14 +226,17 @@
{},
"None.",
}},
- MessageEntry{"BMCKernelPanic",
+ MessageEntry{"BMCBootReason",
{
- "Indicates that BMC kernel panic occurred.",
- "BMC rebooted due to kernel panic.",
+ "Indicates the reason why BMC firmware booted.",
+ "BMC firmware version %1 booted due to %2.",
"OK",
"OK",
- 0,
- {},
+ 2,
+ {
+ "string",
+ "string",
+ },
"None.",
}},
MessageEntry{"BMCFirmwarePanicReason",
@@ -272,6 +275,16 @@
},
"None.",
}},
+ MessageEntry{"BMCKernelPanic",
+ {
+ "Indicates that BMC kernel panic occurred.",
+ "BMC rebooted due to kernel panic.",
+ "OK",
+ "OK",
+ 0,
+ {},
+ "None.",
+ }},
MessageEntry{"ChassisIntrusionDetected",
{
"Indicates that a physical security event "