Oracle Ilom Deprecation Notice For Ipmi 2.0 Management Service Present Behavior - Oracle Sun Fire X4800 Product Notes

Oracle ILOM Deprecation Notice for IPMI 2.0 Management Service Present Behavior

Exit Code: 0x00
Note -
produces a MegaRAID controller event log with the given file name event.log.
The following SCSI sense key errors found in the event log in SAS data path failures indicate a
SAS data path fault:
B/4B/05 :SERIOUS: DATA OFFSET ERROR
B/4B/03 :SERIOUS: ACK/NAK TIMEOUT
B/47/01 :SERIOUS: DATA PHASE CRC ERROR DETECTED
B/4B/00 :SERIOUS: DATA PHASE ERROR
A communication fault between the disk and the host bus adapter causes these errors. The
presence of these errors, even on a single disk, means there is a data path issue. The RAID
controller, SAS cables, SAS expander, or disk backplanes might be causing the interruption to
the communication in the path between the RAID controller and the disks.
Oracle Service personnel can find more information about the diagnosis and triage of hard
disk and SAS data path failures on x86 servers at the My Oracle Support web site:
support.oracle.com. Refer to the Knowledge Article Doc ID 2161195.1 If there are multiple,
simultaneous disk problems on an Exadata server, Oracle Service personnel can refer to
Knowledge Article Doc ID 1370640.1.
Oracle ILOM Deprecation Notice for IPMI 2.0 Management
Service Present Behavior
Present Behavior: IPMI 2.0 Sessions - Enabled (Default). Support for IPMI 2.0 client
interfaces.
Future Behavior: The following IPMI Management Service changes will occur in future
Oracle ILOM firmware releases after firmware version 3.2.7.
First feature change: Oracle ILOM will add a new client interface as an alternative to the
■
IPMI 2.0 Client interface.
Second feature change: The default configuration property for IPMI 2.0 Sessions will
■
change from Enabled to Disabled in a future release. Clients relying on IPMI 2.0 will be
unable to communicate with Oracle ILOM unless the configuration property for IPMI 2.0
Sessions is manually enabled.
16 Sun Fire X4800 Server Product Notes • July 2017
Use the existing name of the event log as the name for the disk controller event log. This
https://