Add message registry entry for Memhot event
Add "ComponentOverTemperature" event message entry in RedFish for
Memhot monitor to log based on the MEMHOT pins.
Tested:
1. Redfish validator - passed for this new addition
2. Verified in Redfish, ComponentOverTemperature event logged properly.
GET:
https:/<BMC-IP>/redfish/v1/Systems/system/LogServices/EventLog/Entries
{
"@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
Entries/1644553991",
"@odata.type": "#LogEntry.v1_8_0.LogEntry",
"Created": "2022-02-11T04:33:11+00:00",
"EntryType": "Event",
"Id": "1644553991",
"Message": "CPU 1 component over temperature and being throttled.",
"MessageArgs": [
"CPU 1"
],
"MessageId": "OpenBMC.0.1.ComponentOverTemperature",
"Name": "System Event Log Entry",
"Severity": "Critical"
}
Signed-off-by: Hardik Panchal <hardikx.panchal@intel.com>
Signed-off-by: Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com>
Change-Id: I6f5f42111ae7db39a4618b2b1ba8c864f9f55824
diff --git a/redfish-core/include/registries/openbmc_message_registry.hpp b/redfish-core/include/registries/openbmc_message_registry.hpp
index 6cf503f..edb39ae 100644
--- a/redfish-core/include/registries/openbmc_message_registry.hpp
+++ b/redfish-core/include/registries/openbmc_message_registry.hpp
@@ -21,15 +21,15 @@
const Header header = {
"Copyright 2018 OpenBMC. All rights reserved.",
"#MessageRegistry.v1_4_0.MessageRegistry",
- "OpenBMC.0.2.0",
+ "OpenBMC.0.3.0",
"OpenBMC Message Registry",
"en",
"This registry defines the base messages for OpenBMC.",
"OpenBMC",
- "0.2.0",
+ "0.3.0",
"OpenBMC",
};
-constexpr std::array<MessageEntry, 188> registry = {
+constexpr std::array<MessageEntry, 189> registry = {
MessageEntry{
"ADDDCCorrectable",
{
@@ -307,6 +307,17 @@
{},
"None.",
}},
+ MessageEntry{
+ "ComponentOverTemperature",
+ {
+ "Indicates that the specified component is over temperature.",
+ "%1 component over temperature and being throttled.",
+ "Critical",
+ "Critical",
+ 1,
+ {"string"},
+ "None.",
+ }},
MessageEntry{"CPLDFirmwarePanicReason",
{
"Indicates the reason for CPLD firmware panic.",