<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bmcweb/redfish-core/include/registries, branch master</title>
<subtitle>OpenBMC Web server</subtitle>
<id>https://git.raptorcs.com/git/bmcweb/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/bmcweb/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/'/>
<updated>2020-02-11T05:00:01+00:00</updated>
<entry>
<title>Add message entry for BMC kernel panic event</title>
<updated>2020-02-11T05:00:01+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2020-02-10T07:15:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=bd5db5221f1a295da61a3e4dba0c48724e090825'/>
<id>urn:sha1:bd5db5221f1a295da61a3e4dba0c48724e090825</id>
<content type='text'>
Log the BMC kernel panic event into redfish.

Tested:
Trigger a kernel panic by "echo c &gt; /proc/sysrq-trigger",
After BMC reboot, check the below message entry in
redfish/v1/Systems/system/LogServices/EventLog/Entries:
{
 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
 "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/68627",
 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
 "Created": "1970-01-01T19:03:47+00:00",
 "EntryType": "Event",
 "Id": "68627",
 "Message": "BMC rebooted due to kernel panic.",
 "MessageArgs": [],
 "MessageId": "OpenBMC.0.1.BMCKernelPanic",
 "Name": "System Event Log Entry",
 "Severity": "OK"
}

Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
Change-Id: Ibc3075a48514b3288ba1a1b1fbe716f5e9deeb26
</content>
</entry>
<entry>
<title>Correct Redfish message severity values</title>
<updated>2020-01-22T21:33:26+00:00</updated>
<author>
<name>Jason M. Bills</name>
<email>jason.m.bills@linux.intel.com</email>
</author>
<published>2020-01-13T22:48:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=4228a1609a9f9751604a1e636de11a34ed58b840'/>
<id>urn:sha1:4228a1609a9f9751604a1e636de11a34ed58b840</id>
<content type='text'>
Redfish specifies only "OK", "Warning", and "Critical" as valid
values for message severity, but some messages have a severity
of "Error".

This changes the incorrect "Error" severity values to "Critical".

Tested:
Checked that all severity values are "OK", "Warning", or "Critical".
Passed the Redfish service validator.

Change-Id: If65665c76915e1730e6ae12c36003242aa9a85c6
Signed-off-by: Jason M. Bills &lt;jason.m.bills@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>msg_registry: updated MemoryThermTrip msg entry</title>
<updated>2020-01-17T17:45:52+00:00</updated>
<author>
<name>jayaprakash Mutyala</name>
<email>mutyalax.jayaprakash@intel.com</email>
</author>
<published>2019-12-24T19:15:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=bc6be2376b4a5407e51deab72b1a4c8a1b7fd425'/>
<id>urn:sha1:bc6be2376b4a5407e51deab72b1a4c8a1b7fd425</id>
<content type='text'>
Updated "MemoryThermTrip" message entry for CPU Memory
Thermal Trip events.

Tested:
1. Redfish validator - passed for this new addition
2. Verified in Redfish, MemoryThermTrip message populated properly

Redfish URI:
GET: https://&lt;BMC IP&gt;/redfish/v1/Systems/system/LogServices/EventLog
               /Entries
{
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
                    Entries/506",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "1970-01-01T00:08:26+00:00",
      "EntryType": "Event",
      "Id": "506",
      "Message": "Memory ThermTrip asserted: CPU 1.",
      "MessageArgs": [
        "CPU 1"
      ],
      "MessageId": "OpenBMC.0.1.MemoryThermTrip",
      "Name": "System Event Log Entry",
      "Severity": "Critical"
}
{
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
                    Entries/506_2",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "1970-01-01T00:08:26+00:00",
      "EntryType": "Event",
      "Id": "506_2",
      "Message": "Memory ThermTrip asserted: CPU 2.",
      "MessageArgs": [
        "CPU 2"
      ],
      "MessageId": "OpenBMC.0.1.MemoryThermTrip",
      "Name": "System Event Log Entry",
      "Severity": "Critical"
}

Signed-off-by: jayaprakash Mutyala &lt;mutyalax.jayaprakash@intel.com&gt;
Signed-off-by: Chalapathi &lt;chalapathix.venkataramashetty@intel.com&gt;
Change-Id: I89271d28012c7f01a6cc37e1ef35c7e15f5e9965
</content>
</entry>
<entry>
<title>bmcweb: Message entry for user security Event</title>
<updated>2020-01-08T03:53:10+00:00</updated>
<author>
<name>Suryakanth Sekar</name>
<email>suryakanth.sekar@linux.intel.com</email>
</author>
<published>2019-12-12T16:09:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=8988dda41319950476ebb146df06c2e7b3fbf44d'/>
<id>urn:sha1:8988dda41319950476ebb146df06c2e7b3fbf44d</id>
<content type='text'>
Message entry for
BMC should detect the following intrusion or non-allowed configuration and
log the security event with description.
1. Password storing hash algo changes from SHA2-256 to MD5 in Linux pwd file
2. When any user other than root has its UID set to 0 in Linux pwd file
3. When any unsupported shells (not bash or sh) are present in Linux pwd file
4. When the root user is assigned a password in Linux password file

Tested:
1. Ran Redfish validator - passed for this new addition.

 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/75_1",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:01:15+00:00",
  "EntryType": "Event",
  "Id": "75_1",
  "Message": "weak password computing hash algorithm is enabled = MD5 Hash algorithm .",
  "MessageArgs": [
         "MD5 Hash algorithm"
     ],
  "MessageId": "OpenBMC.0.1.SecurityUserWeakHashAlgoEnabled",
  "Name": "System Event Log Entry",
  "Severity": "Critical"
 },
 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/240",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:04:00+00:00",
  "EntryType": "Event",
  "Id": "240",
  "Message": "other than /bin/bash,/bin/sh, Unsupported shell is enabled",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserUnsupportedShellEnabled",
  "Name": "System Event Log Entry",
  "Severity": "Critical"
 },
 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/246",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:04:06+00:00",
  "EntryType": "Event",
  "Id": "246",
  "Message": "Unsupported shell is removed",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserUnsupportedShellRemoved",
  "Name": "System Event Log Entry",
  "Severity": "OK"
 },

 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/604",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:10:04+00:00",
  "EntryType": "Event",
  "Id": "604",
  "Message": "password computing hash algorithm is changed to sha256/sha512.",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserHashAlgoChanged",
  "Name": "System Event Log Entry",
  "Severity": "OK"
 }
 {
 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
 "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/75",
 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
 "Created": "1970-01-01T00:01:15+00:00",
 "EntryType": "Event",
 "Id": "75",
 "Message": "root user is enabled.",
 "MessageArgs": [],
 "MessageId": "OpenBMC.0.1.SecurityUserRootEnabled",
 "Name": "System Event Log Entry",
 "Severity": "Critical"
 },
 {
 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
 "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/1153",
 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
 "Created": "1970-01-01T00:19:13+00:00",
 "EntryType": "Event",
 "Id": "1153",
 "Message": "uid Zero is assigned with non-root user",
 "MessageArgs": [],
 "MessageId": "OpenBMC.0.1.SecurityUserNonRootUidZeroAssigned",
 "Name": "System Event Log Entry",
 "Severity": "Critical"
 }

Signed-off-by: Suryakanth Sekar &lt;suryakanth.sekar@linux.intel.com&gt;
Change-Id: I8a3a10be2cc85614baa7b0d2f56b3376c3301e01
</content>
</entry>
<entry>
<title>msg_registry:Added PowerSupplyConfigErrRecovered</title>
<updated>2019-12-20T19:21:53+00:00</updated>
<author>
<name>jayaprakash Mutyala</name>
<email>mutyalax.jayaprakash@intel.com</email>
</author>
<published>2019-12-19T12:15:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=7f68549fe40af716551e6de7db90bfb9fb5b8dd6'/>
<id>urn:sha1:7f68549fe40af716551e6de7db90bfb9fb5b8dd6</id>
<content type='text'>
Added PowerSupplyConfigurationErrorRecovered message entry in
openbmc_message_registry as it is required when PSU deassert event
occurred.
This is continuation of below patch.
https://gerrit.openbmc-project.xyz/#/c/openbmc/dbus-sensors/+/27701/

Tested:
1. Verified redfish validator passed
2. verified in Redfish, PowerSupplyConfigurationErrorRecovered message populated
properly
Get: https://&lt;BMC IP&gt;/redfish/v1/Systems/system/LogServices/
     EventLog/Entries
    {
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/42519",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "1970-01-01T11:48:39+00:00",
      "EntryType": "Event",
      "Id": "42519",
      "Message": "Power supply PSU2 configuration error recovered.",
      "MessageArgs": [
        "PSU2"
      ],
      "MessageId": "OpenBMC.0.1.PowerSupplyConfigurationErrorRecovered",
      "Name": "System Event Log Entry",
      "Severity": "OK"
    },

Signed-off-by: jayaprakash Mutyala &lt;mutyalax.jayaprakash@intel.com&gt;
Change-Id: Ifef9d323241f49124df7b85f85d42041e7ecdf83
</content>
</entry>
<entry>
<title>Adjust the PSU related log level</title>
<updated>2019-12-20T03:02:40+00:00</updated>
<author>
<name>Yong Li</name>
<email>yong.b.li@linux.intel.com</email>
</author>
<published>2019-12-19T09:57:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=9c6b0159a6d9f71d0bbc1301d1f605add3f91da3'/>
<id>urn:sha1:9c6b0159a6d9f71d0bbc1301d1f605add3f91da3</id>
<content type='text'>
Based on the spec, these PSU related logs should be warning.

Tested:
With two PSUs, remove one AC cable, and then remove the PSU,
Check the PSU related log in
https://$BMCIP/redfish/v1/Systems/system/LogServices/EventLog/Entries

Signed-off-by: Yong Li &lt;yong.b.li@linux.intel.com&gt;
Change-Id: Iebce710d7d003731cbb956738d8be212bf04ad0b
</content>
</entry>
<entry>
<title>bmcweb: Message entry for At-Scale Debug Event</title>
<updated>2019-12-10T04:57:55+00:00</updated>
<author>
<name>Suryakanth Sekar</name>
<email>suryakanth.sekar@linux.intel.com</email>
</author>
<published>2019-11-26T17:10:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=4dcc3f92c8725e2424c7792908c44311e484a429'/>
<id>urn:sha1:4dcc3f92c8725e2424c7792908c44311e484a429</id>
<content type='text'>
Message entry for
1. At-Scale Debug session established and closed.
2. Whenever At-Scale Debug user is enabled or disabled
3. At-scalde Debug feature is enabled or disabled in platform
4. At-sclde Debug service is enabled or disabled

Tested:
1. Ran Redfish validator - passed for this new addition.

Log will be shown as below:

       {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/254",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T00:04:14+00:00",
            "EntryType": "Event",
            "Id": "254",
            "Message": "At-Scale Debug Feature is enabled in hardware.",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugFeatureEnabledAtHardware",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },
        {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/254_1",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T00:04:14+00:00",
            "EntryType": "Event",
            "Id": "254_1",
            "Message": "At-Scale Debug service is started.",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugFeatureEnabled",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },
        {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/30630_2",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T08:30:30+00:00",
            "EntryType": "Event",
            "Id": "30630_2",
            "Message": "At-scale-debug service is now connected 198.164.11.12",
            "MessageArgs": [
                "198.164.11.12"
            ],
            "MessageId": "OpenBMC.0.1.AtScaleDebugConnected",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },
        {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/30630_3",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T08:30:30+00:00",
            "EntryType": "Event",
            "Id": "30630_3",
            "Message": "At-scale-debug connection aborted/failed",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugConnectionFailed",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },
       {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/30629_2",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T08:30:29+00:00",
            "EntryType": "Event",
            "Id": "30629_2",
            "Message": "At-scale-debug service is now disconnected",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugDisconnected",
            "Name": "System Event Log Entry",
            "Severity": "OK"
        },
        {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/262",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T00:04:22+00:00",
            "EntryType": "Event",
            "Id": "262",
            "Message": "At-Scale Debug special user is disabled",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugSpecialUserDisabled",
            "Name": "System Event Log Entry",
            "Severity": "OK"
        },
       {
            "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
            "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/154",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "1970-01-01T00:02:34+00:00",
            "EntryType": "Event",
            "Id": "154",
            "Message": "At-Scale Debug special user is enabled",
            "MessageArgs": [],
            "MessageId": "OpenBMC.0.1.AtScaleDebugSpecialUserEnabled",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },

Signed-off-by: Suryakanth Sekar &lt;suryakanth.sekar@linux.intel.com&gt;
Change-Id: Id5369c36547c4a5d7ae6f1f1dbd4dae8317a26d7
</content>
</entry>
<entry>
<title>Add constexpr to registries</title>
<updated>2019-11-12T18:29:35+00:00</updated>
<author>
<name>Ed Tanous</name>
<email>ed.tanous@intel.com</email>
</author>
<published>2019-10-24T17:16:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=be380cb11299957665d061b65df4afe03e4218d1'/>
<id>urn:sha1:be380cb11299957665d061b65df4afe03e4218d1</id>
<content type='text'>
Because these structures are known at compile time, they can be
constexpr with no ill effect.

Tested:  Code compiles, clang-tidy checks pass no functional change.

Signed-off-by: Ed Tanous &lt;ed.tanous@intel.com&gt;
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
Change-Id: Id78e3638b3dddd740f1a22e22d17fb0d6f8437d3
</content>
</entry>
<entry>
<title>Register redfish log</title>
<updated>2019-11-07T23:03:19+00:00</updated>
<author>
<name>Chen,Yugang</name>
<email>yugang.chen@linux.intel.com</email>
</author>
<published>2019-11-04T06:34:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=8ae37025d83533889be862d73d8ec701a818275a'/>
<id>urn:sha1:8ae37025d83533889be862d73d8ec701a818275a</id>
<content type='text'>
Need to Log security event for enabling uart-port-debug, P2A-bridge and
BMC 2nd boot flash to redfish.

tested:
By settng the SCU registers for uart-port-debug disable bit, P2A-bridge
enable bit and BMC 2nd boot flash enable bit, trigger security events, can
see their redfish log.

Change-Id: I75a7ed679c6b20d454a831e52d96dea30eea22bd
Signed-off-by: Chen,Yugang &lt;yugang.chen@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Add Drive Error Registry Message</title>
<updated>2019-11-06T18:20:38+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2019-11-04T21:29:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=c75f1e9afc97310f4d8e486dab4be3ccb055dae5'/>
<id>urn:sha1:c75f1e9afc97310f4d8e486dab4be3ccb055dae5</id>
<content type='text'>
This allows logging of drive errors.

Tested:

 "DriveError": {
            "Description": "Indicates that a Drive Error occurred of the specified type or cause.",
            "Message": "Drive Error Occurred: %1.",
            "NumberOfArgs": 1,
            "ParamTypes": [
                "string"
            ],
            "Resolution": "None.",
            "Severity": "Warning"
        }

Change-Id: Ic97611e26710f57b09a7f89e0470f1277f710d5d
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
</feed>
