A P P E N D I X C

Failed Component Alarm Codes

This appendix describes failed component alarm codes.

Failed component alarm codes use Morse code dot and dash characters. The dot "." is a short tone sounding for one unit of time. The dash "-" is a long tone sounding for three units of time.

Alarms, also referred to as beep codes, are presented in a sequence, starting with the critical component failure alarm, which alerts you to a component problem or failure or a firmware mismatch. This alarm is then followed by alarms for whichever components or assemblies have failed. Once the beep code sequence is complete, it repeats. To understand the beep codes, listen to the sequence of codes until you can break down the sequence into its separate alarms. You can also check your software or firmware for alarms, error messages, or logs to isolate and understand the cause.For example, in the case of a fan failure in a power supply, you might first hear the critical component failure alarm, followed by a power supply failure alarm from power supply 0 or power supply 1, followed by a fan failure event alarm, followed by an event alarm. This sequence continues to repeat.


Failure	Morse Code Letter	Morse Code Sound Pattern
Critical component failure or mismatch	8 dashes	--------
Power supply 0 failure	P0	. -- . -----
Power supply 1 failure	P1	. -- . . ----
Event alarm	E	.
Fan failure	F	. . - .
Voltage failure	V	. . . -
Temperature failure	T	-
SES/PLD firmware mismatch	R	. - .

See Front Panel LEDs for more information about the SES/PLD firmware mismatch mentioned in TABLE C-1.

Caution - Be particularly careful to observe and rectify a temperature failure alarm. If you detect this alarm, shut down the controller and the server as well if it is actively performing I/O operations to the affected array. Otherwise, system damage and data loss can occur.