Seven-segment display overview
The DE2000/DE4000/DE6000 controllers have a two-digit, seven-segment display at the back, which shows the following information.
| Controller state | Seven-segment display |
|---|---|
| Functioning correctly | Tray ID |
| Not functioning correctly | Diagnostic codes to help identify errors |
The following figure shows the seven-segment display for the DE2000 controller shelf, the DE4000 controller shelf, and the DE6000 controller shelf.
| LED | Status | Description |
|---|---|---|
| 1 Heartbeat (dot in the lower right) | Blinking green | This indicates normal activity. |
| 2 Tray ID | Green | This shows the ID of the controller shelf when the controller operates normally. If the controller is not operating normally and the Diagnostic LED is on, the diagnostic code is displayed instead. |
| 3 Diagnostic (dot in the upper left) | Green | The seven-segment display shows the diagnostic code. |
| Off | The seven-segment display shows the tray ID. |
Seven-segment display sequence codes
Seven-segment display sequences enable you to understand errors and operational states of the various components in your storage array. Each sequence shows a two-digit category code, followed by a two-digit detail code. The category code appears at the start of a sequence and the detail code follows the category code with more specific information about the error. After each category code is displayed, the LED goes blank. The detail code then appears and disappears, and the entire sequence is repeated. For example, if there is a power-on validation error during startup, you see the following codes displayed on the seven-segment display: SE, followed by Sx, in which SE is the category code and Sx is the detail code.
When the seven-segment display sequence starts, the Diagnostic LED is on (green).
| Category | Category code | Detail code |
|---|---|---|
| Startup error | SE |
|
| Operational error | OE |
|
| Operational state | OS |
|
| Component failure | CF |
|
| Diagnostic failure | dE |
|
| Category delimiter | -- The double hyphen (--) is the separator between category-detail code pairs when more than one pair exists in the sequence. | |
| End-of-sequence delimiter | Blank; display turns off at the end of a sequence |
Seven-segment display codes when controller turns on
| Code | Description |
|---|---|
| 0xEA | DDR4 training failed |
| 0xE8 | No memory installed |
| 0x22 | No master boot record found on any boot device |
| 0x23 | No SATA drive installed |
| 0xAE | Booting OS |
| 0xAB | Alternate boot code |
| 0x40 | Invalid DIMMs |
| 0x41 | Invalid DIMMs |
| 0x42 | Memory test failed |
| 0x2A, 0x2B | Stuck bus, unable to read DIMM SPD data |
| 0x51 | DIMM SPD read failure |
| 0xA0, 0xA1, 0xA2, and 0xA3 | SATA drive initialization |
| 0x92 – 0x96 | PCI bus initialization |
Seven-segment display use cases
| Use case | Display sequence |
|---|---|
| Controller power-on | |
| SE 88 blank |
| Operational states | |
| Normal operation | xy (static controller tray ID) |
| Start-of-day (SOD) processing | OS Sd blank |
| The controller is placed in reset while showing the tray ID | OS OL blank |
| The controller is operating on batteries (cache backup) | OS bb blank |
| The CPU temperature has exceeded the warning level | OS OH blank |
| Component failure when the controller is operational | |
| Failed host interface card (HIC) | OS CF HX blank |
| Failed flash drive | OS CF Fx blank |
| Power-on diagnostic failure | |
| Failure of a component that is not a field replaceable unit | SE dF blank- |
| Processor DIMM failure | SE dF -- CF Px blank- |
| Cache memory DIMM failure | SE dF -- CF Cx blank- |
| Processor DIMM or cache memory DIMM failure | SE dF -- CF dx blank- |
| Host interface card failure | SE dF -- CF Hx blank- |
| Incorrect number of cache backup devices | SE LC -- CF Fx blank- |
| The controller is suspended and there are no other errors to report | |
| All lock-down conditions | OH Lx blank- |
| The controller is suspended because of component errors | |
| Persistent processor DIMM error correcting code (ECC) errors | OE L2 -- CF Px blank- |
| Persistent cache DIMM ECC errors | OE L2 -- CF Cx blank- |
| Persistent processor or cache DIMM ECC errors | OE L2 -- CF dx blank- |
| The controller is suspended as a result of persistent cache backup configuration errors | |
| The write-protect switch is set during cache restore | OE LC blank- |
| The memory size changed with dirty data in the flash drives | OE L2 -- CF dx blank- |
| The controller is suspended as a result of diagnostic errors | |
| Cache memory diagnostic failure | dE L2 -- CF Cx blank- |
| Base controller diagnostic failure | dE L3 -- CF b1 blank- |
| Base controller I/O Controller chip (IOC) diagnostic failure | dE L3 -- CF b2 blank- |
Seven-segment display lock-down codes
Diagnostic lock-down codes are displayed when the controller is not operational, either because of a configuration problem or a hardware fault. The lock-down code is displayed as part of the seven-segment display sequence.
| Lock-down code | Description |
|---|---|
| L0 | The controller types in a two-controller configuration are mismatched. |
| L1 | Missing interconnect canister. |
| L2 | A persistent memory error has occurred. |
| L3 | A persistent hardware error has occurred. |
| L4 | A persistent data protection error has occurred. |
| L5 | An auto-code synchronization (ACS) failure has been detected. |
| L6 | An unsupported HIC has been detected. |
| L7 | A sub-model identifier either has not been set or has been mismatched. |
| L8 | A memory configuration error has occurred. |
| L9 | A link speed mismatch condition has been detected in either the I/O module (IOM) or the power supply. |
| Lb | A HIC configuration error has been detected. |
| LC | A persistent cache backup configuration error has been detected. |
| Ld | A mixed cache memory DIMMs condition has been detected. |
| LE | Uncertified cache memory DIMM sizes have been detected. |
| LF | The controller has locked down in a suspended state with limited SYMbol support. |
| LH | Controller in Simplex Mode installed in the wrong slot. |
| LJ | The controller does not have enough memory to support the configuration. |
| LL | The controller cannot access either midplane SBB EEPROM. |
| Ln | A module is not valid for a controller. |
| LP | Drive port mapping tables are not detected. |
| Lr | A component that is not a field replaceable unit (FRU) has been replaced. |
| Lt | A configuration data base corruption has been detected. |
| LU | The SOD reboot limit has been exceeded. |
| Startup error code | Description |
|---|---|
| S1 | The controller detects a checksum failure in EEPROM. |
| S2 | The SBB Signature/Revision is invalid. |
| S3 | An unsupported enclosure is detected in the storage array. |
| S4 | The power supplies are incapable of powering the controller. |
| S5 | The SBB pairing has failed. |