| Asset ID: |
1-71-1574251.1 |
| Update Date: | 2017-09-18 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1574251.1
:
OPS-Center displays the following message regularly: HARDWARE FAULT: Component error detected. Component Name: SMI Handler
| Related Items |
- Oracle Exalogic Elastic Cloud X2-2 Hardware
- Exalogic Elastic Cloud X3-2 Hardware
|
| Related Categories |
- PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
|
In this Document
Applies to:
Exalogic Elastic Cloud X3-2 Hardware - Version All Versions and later
Oracle Exalogic Elastic Cloud X2-2 Hardware - Version All Versions and later
Linux x86-64
Oracle Solaris on x86-64 (64-bit)
Goal
In Ops Center the following message is reported:
HARDWARE FAULT: Component error detected. Component Name: SMI Handler
What does this error mean and what consequences does it have?
Solution
This SMI Handler message reported by Ops Center has been known to be caused by node reboot via power button.
You will see this message if a node is rebooted and is not an indication of a real hardware fault.
240 | 08/02/2013 | 15:36:30 | Button | Power Button pressed | Asserted
241 | 08/02/2013 | 15:37:57 | Button | Power Button pressed | Asserted
242 | 08/02/2013 | 15:38:02 | Button | Power Button pressed | Asserted
243 | 08/02/2013 | 15:38:13 | Button | Power Button pressed | Asserted
244 | 08/02/2013 | 15:38:22 | System ACPI Power State ACPI | S0/G0: working | Deasserted
245 | 08/02/2013 | 15:38:22 | System ACPI Power State ACPI | S5/G2: soft-off | Asserted
246 | 08/02/2013 | 15:40:46 | Button | Power Button pressed | Asserted
247 | 08/02/2013 | 15:40:47 | System Firmware Progress | Management controller initialization | Asserted
248 | 08/02/2013 | 15:42:16 | Button | Power Button pressed | Asserted
249 | 08/02/2013 | 15:42:18 | System Firmware Progress | Management controller initialization | Asserted
24a | 08/02/2013 | 15:42:30 | System Firmware Progress | Management controller initialization | Asserted
24b | 08/02/2013 | 15:42:35 | System Firmware Progress | Memory initialization | Asserted
24c | 08/02/2013 | 15:42:37 | System Boot Initiated | Initiated by warm reset | Asserted
24d | 08/02/2013 | 15:42:37 | System Firmware Progress | Management controller initialization | Asserted
24e | 08/02/2013 | 15:42:40 | System ACPI Power State ACPI | S0/G0: working | Asserted
24f | 08/02/2013 | 15:42:40 | System ACPI Power State ACPI | S5/G2: soft-off | Deasserted
250 | 08/02/2013 | 15:42:43 | System Firmware Progress | Memory initialization | Asserted
251 | 08/02/2013 | 15:43:03 | System Firmware Progress | Primary CPU initialization | Asserted
252 | 08/02/2013 | 15:43:04 | System Firmware Progress | Secondary CPU Initialization | Asserted
253 | 08/02/2013 | 15:43:15 | System Firmware Progress | PCI resource configuration | Asserted
254 | 08/02/2013 | 15:43:15 | System Firmware Progress | PCI resource configuration | Asserted
255 | 08/02/2013 | 15:43:16 | System Firmware Progress | PCI resource configuration | Asserted
256 | 08/02/2013 | 15:43:16 | System Firmware Progress | PCI resource configuration | Asserted
257 | 08/02/2013 | 15:43:17 | System Firmware Progress | Video initialization | Asserted
258 | 08/02/2013 | 15:43:17 | System Firmware Progress | Option ROM initialization | Asserted
259 | 08/02/2013 | 15:43:24 | System Firmware Progress | Keyboard controller initialization | Asserted
25a | 08/02/2013 | 15:43:30 | System Firmware Progress | Hard-disk initialization | Asserted
25b | 08/02/2013 | 15:43:30 | System Firmware Progress | Option ROM initialization | Asserted
25c | 08/02/2013 | 15:43:38 | System Firmware Progress | Option ROM initialization | Asserted
25d | 08/02/2013 | 15:43:46 | System Firmware Progress | Option ROM initialization | Asserted
25e | 08/02/2013 | 15:44:09 | System Firmware Progress | Option ROM initialization | Asserted
25f | 08/02/2013 | 15:44:17 | System Firmware Progress | Option ROM initialization | Asserted
260 | 08/02/2013 | 15:44:36 | System Firmware Progress | System boot initiated | Asserted
So, when you see this error you need to check the causes of the reboots to find if they were normal expected reboots or unexpected due to some other issues.
In the majority of cases they will just be normal manual reboots. However, if you discover that a reboot was unexpected or there was an unexpected or unexplainable reset of a node, then this might be a time to check for other issues which may be needed further investigation. In that case, please open Service Request with Oracle Customer Support.
Attachments
This solution has no attachment
