A P P E N D I X C -

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. This sequence continues to repeat.

TABLE C-1 Failed Component Alarm Codes
Failure	Morse Code Letter	Code Sound Pattern
Critical component failure or mismatch	8 dashes	--------
Event alarm	E	.
Fan failure	F	..-.
Power supply 0 failure	P0	.--. -----
Power supply 1 failure	P1	.--. .----
Temperature failure	T	-
Voltage failure	V	...-
SES/PLD firmware mismatch	R	.-.
Unrecoverable alarm status from RAID controller	SOS	... --- ...
Informational tone status from RAID controller ^[1]	1 dash, 3 dots, 1 dash	-...-
Non-critical tone status from RAID controller ^[2]	8 dots	........

TABLE C-1 Failed Component Alarm Codes

Failure

Morse Code Letter

Code Sound Pattern

Critical component failure or mismatch

8 dashes

--------

Event alarm

Fan failure

..-.

Power supply 0 failure

.--. -----

Power supply 1 failure

.--. .----

Temperature failure

Voltage failure

...-

SES/PLD firmware mismatch

.-.

Unrecoverable alarm status from RAID controller

SOS

... --- ...

Informational tone status from RAID controller ^[1]

1 dash, 3 dots, 1 dash

-...-

Non-critical tone status from RAID controller ^[2]

8 dots

........

An event alarm can be triggered by a hardware error, a heartbeat error, or a missing I/O module. Refer to the event log for details of the event condition. See Section 6.2, Front Panel LEDs for more information about the SES/PLD firmware mismatch.

The controller issues additional beep codes that do not use Morse code dots and dashes. These codes consist of beeps and wait periods as shown in TABLE C-2. The beeps have a duration of 0.25 sec.

TABLE C-2 Non-Morse Component Alarm Codes
Conditions	Beep Code Pattern	Frequency
Controller initialization	* (0.25 sec wait) * (0.25 sec wait)	Repeat until problem solved
Disk drive failure detected Logical drive rebuild failed or aborted Peripheral device failure (e.g. power supply failure or temperature out of range)	* (0.75 sec wait) * (0.75 sec wait) * (2.5 sec wait)	Repeat until problem solved
Rebuilding logical drive Regenerating parity of logical drive Adding drive to logical drive	* (0.5 sec wait) * (6 sec wait)	Repeat until process completes
Redundant controller failure detected Firmware download completed with OK status During controller initialization: drive cannot be scanned by controller due to disk command being blocked During controller initialization: any logical drive has a status other than GOOD	* (0.25 sec wait) * (0.5 sec wait) * (0.75 sec wait) * (1 sec wait) * ((1.25 sec wait) *	Repeat sequence twice

TABLE C-2 Non-Morse Component Alarm Codes

Conditions

Beep Code Pattern

Frequency

Controller initialization

* (0.25 sec wait) * (0.25 sec wait)

Repeat until problem solved

Disk drive failure detected
Logical drive rebuild failed or aborted
Peripheral device failure (e.g. power supply failure or temperature out of range)

* (0.75 sec wait) * (0.75 sec wait) * (2.5 sec wait)

Repeat until problem solved

Rebuilding logical drive
Regenerating parity of logical drive
Adding drive to logical drive

* (0.5 sec wait) * (6 sec wait)

Repeat until process completes

Redundant controller failure detected
Firmware download completed with OK status
During controller initialization: drive cannot be scanned by controller due to disk command being blocked
During controller initialization: any logical drive has a status other than GOOD

* (0.25 sec wait) * (0.5 sec wait) * (0.75 sec wait) * (1 sec wait) * ((1.25 sec wait) *

Repeat sequence twice

^{1 (TableFootnote) Indicates that an informational event has occurred. Refer to the event log for details.}

^{2 (TableFootnote) Indicates that a non-critical event has occurred. Refer to the event log for details.}