Enterprise Manager does not update incident with Exadata Managed Server event for PMEM replacement
(Doc ID 2612484.1)
Last updated on APRIL 13, 2021
Applies to:
Enterprise Manager for Exadata - Version 13.1.0.0.0 to 13.3.2.0.0 [Release 13c]Information in this document applies to any platform.
Symptoms
When a PMEM fault occurs Enterprise Manager will successfully create an incident based on an Exadata MS alert similar to the following example:
6_1 2019-11-04T10:09:33-08:00 critical "PMEM failed. Status : FAILED Manufacturer : Intel Model Number : NMA1XBD128GQS Size : 126GB Serial Number : 8089-a2-1838-00000944 Firmware : Unknown Slot Number : CPU: 1; DIMM: 10 Cell Disk : PM_07_cellserver1 "
However when the PMEM DIMM is replaced the warning and clear alerts are sent in rapid succession from Exadata MS to Enterprise Manager as in the following example.
6_2 2019-11-04T10:31:41-08:00 warning "PMEM was removed. Status : FAILED Manufacturer : Unknown Model Number : Unknown Size : 126GB Serial Number : 8089-a2-1838-00000944 Firmware : Unknown Slot Number : CPU: 1; DIMM: 10 Cell Disk : PM_07_cellserver1 PMEM Cache : Present"
6_3 2019-11-04T10:31:44-08:00 clear "PMEM was replaced. Status : NORMAL Manufacturer : Intel Model Number : NMA1XBD128GQS Size : 126GB Serial Number : 8089-a2-1838-00000a0d Firmware : Unknown Slot Number : CPU: 1; DIMM: 10 Cell Disk : PM_07_cellserver1 PMEM Cache : Present"
In this example the snmp trap for alert 6_2 above will get processed and will update the incident to warning. However Enterprise Manager processing of alert 6_3 will fail resulting in an incident in Enterprise Manager that is listed as a warning that will never clear. Users can also not manually clear the incident via the Enterprise Manager console as the incident is stateful.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |