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. This sequence continues to repeat.
Informational tone status from RAID controller[1] |
||
Non-critical tone status from RAID controller[2] |
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.
* (0.25 sec wait) * (0.5 sec wait) * (0.75 sec wait) * (1 sec wait) * ((1.25 sec wait) * |
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.