Important – Install Latest OS Updates, Patches, and Firmware
root#
./MegaCli64 adpeventlog getevents –f event.log aall
Success in AdpEventLogExit
Code: 0x00
Note -
Use the existing name of the event log as the name for the disk controller event log. This
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 backplane 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:
. 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 Notices and Important
Operating Notes
■
“Deprecation Notice for IPMI 2.0 Management Service ” on page 16
■
“Deprecation Notice for Default Self-Signed Certificate” on page 17
Deprecation Notice for IPMI 2.0 Management Service
Present Behavior
: IPMI 2.0 Management 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.
16
Sun Fire X4170 M2 and X4270 M2 Servers Product Notes • July 2018
