How to Configure IPMI with Oracle Grid Infrastructure Clusterware
Last updated on FEBRUARY 09, 2015
Applies to:Oracle Exadata Storage Server Software - Version 220.127.116.11.2 to 18.104.22.168.0 [Release 11.2 to 12.1]
Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.2 to 12.1]
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms