Understanding Ibm Bladecenter S Sas Raid Controller Module Alerts; Active Alerts - IBM BladeCenter S SAS RAID Controller Module Installation And User Manual

15. Verify the visual indicators on each RAID Controller, ensuring the amber

Understanding IBM BladeCenter S SAS RAID Controller Module alerts

This topic details how to read alerts you might see while administering your RAID
Controller.
The IBM BladeCenter S SAS RAID Controller Module displays alert information
that keeps you informed as to the state of your system while providing for
advanced diagnosis and guidance to correct errors and device failures. The alert
function creates a requirement making it necessary for you to interact with the
system to acknowledge critical errors and confirm actions taken in the course of
system debug and repair. All of which are logged and creates a history that can be
used to maintain the system and troubleshoot any future system events.

Active Alerts

Active alerts are created by events or state changes in the RAID Controller and are
uniquely identified by instance ID, alert code, and primary ID parameter.
Every alert created remains active until cleared in one of the following ways:
v Timeout
v User acknowledgement
v Change in controller state
Once an alert is cleared, the alert is recorded in two places: The alert history buffer,
and the alert history log file. You can also use the RAID Controller CLI to record
alerts into the history log file and download them from the RAID Controller.
Note: The RAID Controller automatically updates the alert history log upon shut
down.
If your RAID Controllers are in a redundant configuration, an active alert causes
the information indicators on both RAID Controllers to light up, however each
RAID Controller generates and maintains its own active alerts and alert history
independent of the other. When the RAID Controllers are not in a bound
configuration, or are not able to communicate through a serial port interconnect,
you have to retrieve the active alerts from each RAID Controller separately.
Note: The mechanism for downloading the alert history logs is not inherently
bound, and must always be executed separately for each RAID Controller.
b. Verify the status of the RAID Controller. Type list controller. Ensure
that the status is PRIMARY and SECONDARY.
c. To verify that no RAID Controller critical alerts exist. Type alert –get If a
critical alert exists in the active alert list, go to the alert section of this
document to begin your problem determination and repair procedure.
System Information and Fault LEDs are off.
Chapter 11. Troubleshooting and support
105