How to Configure IPMI with Oracle Grid Infrastructure Clusterware
(Doc ID 1968744.1)
Last updated on JANUARY 31, 2020
Applies to:Oracle Exadata Storage Server Software - Version 18.104.22.168.2 to 22.214.171.124.0 [Release 11.2 to 12.1]
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Pre-requisite requirement however is to have iLOM IPMI chipset present.
In certain rare cases its possible Linux Kernel panic/crash in a Grid Infrastructure/Clusterware environment can manifest to an entire outage if the problematic node does not leave the cluster.
With Exadata for example the implementation of IPMI via the iLOM allows for CSSD daemon to communicate with the remote IPMI interface to initiate a reset of the host, alleviating unexpected
delays/outage to other nodes and avoiding any potential split-brain.
In the case of a node not leaving the cluster due to a kernel crash/panic and IPMI is NOT setup we see the following in the remote/surviving node ocssd.log ->
Therefore goal is to avoid such scenario's and allow surving CSSD daemon to trigger IPMI and reset the problem host.
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