Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1610353.1
Update Date:2013-12-30
Keywords:

Solution Type  Problem Resolution Sure

Solution  1610353.1 :   During node reboot, DB Node hangs during OS boot at loading IPMI Drivers (ipmi-si)  


Related Items
  • Exadata Database Machine V2
  •  
  • Exadata Database Machine X2-2 Hardware
  •  
  • Exadata X3-2 Hardware
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: EXADATA
  •  


On reboot, DB Node hangs on OS reboot loading IPMI Drivers (ipmi-si)
Performing ILOM reset /SP does not correct issue.
Can also be seen on Storage Cell

In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-8272915591>

Applies to:

Exadata Database Machine V2 - Version All Versions to All Versions [Release All Releases]
Exadata X3-2 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata Database Machine X2-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

On reboot, a Database Node (DB Node) may hang loading IPMI Drivers (ipmi-si)
Performing ILOM reset /SP does not correct issue.

The issue may also be seen on Storage cell.

Cause

ILOM (BMC) related (memory leak or hang) causing improper sensing of physical hardware.

This issue is most often seen in older version of ILOM firmware that comes with Exadata software versions earlier than 11.2.3.2.0.

Solution

Perform ILOM shutdown of node and power off.

      "This may allow node to reboot, but may take an extra-ordinary amount of time to boot-up (up to 2 hours)"

If this does not correct issue or if excessive reboot time is seen, the next step is to:

1: Perform ILOM power down of effected node.

2: Physically unplug the electric cord from the effected node for 3-5 minutes.

      If customer is unsure or uncomfortable in performing this task, a Field Service task can be opened for steps 2 and 3.

3: Plug power cable back into node and re-start. 

4: When node re-starts, gather a sundiag and SOS report, forward to support for review.

 

If node does not re-start, gather an ILOM snapshot and forward to support for review.

To help prevent this and other similar issues, it is recommended on being up-to-date on patching levels.

 

References

<NOTE:761868.1> - Oracle Exadata Diagnostic Information required for Disk Failures and some other Hardware issues
<NOTE:1310539.1> - Exadata ILOM memory leak in older ILOM firmware
<NOTE:1020204.1> - Collecting snapshot on ILOM 3.x and later platforms
<NOTE:1500235.1> - How To Collect an Sosreport on Oracle Linux

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback