| Asset ID: |
1-71-1021109.1 |
| Update Date: | 2012-10-09 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
1021109.1
:
Sun StorageTek[TM] 6140, 6540, and Flexline 380 Array Controller 7-Segment LED
| Related Items |
- Sun Storage 6140 Array
- Sun Storage Flexline 380 Array
- Sun Storage 6540 Array
|
| Related Categories |
- PLA-Support>Sun Systems>DISK>Arrays>SN-DK: FLX300_65xx_6780
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Modular Disk - Flexline FLX FLA FLC Arrays
|
PreviouslyPublishedAs
271029
Applies to:
Sun Storage Flexline 380 Array - Version Not Applicable and later
Sun Storage 6140 Array - Version Not Applicable and later
Sun Storage 6540 Array - Version Not Applicable and later
All Platforms
Goal
The purpose of this document is to describe how the seven(7) segment display on the RAID controller module works, for a Sun StorageTek[TM] 6540, StorageTek[TM] Flexline 380, and Sun StorageTek[TM] 6140. Additionally, it will describe the codes that can be displayed.
The seven segment displays on these arrays are static. Under optimal conditions they will display the tray ID, which is 85 by default.
On boot, the array controllers will go through a rapid sequence of displays, which indicate the points in the boot cycle that the controllers are performing. This document is intended to describe the static display, which does not change after the boot sequence has stopped. The static display indicates the reason why the boot sequence is stopped, and will be accompanied by an Amber Fault LED next to the display that indicates that the controller is offline as well.
Fix
Follow the steps below to reference the meaning of the tray ID.
1. Verify that you're looking at the RAID module or controller.
The RAID module is a piece of hardware that contains only the RAID controllers and power distribution components for the module,
pictured here in the Sun System Handbook. This applies to a Flexline 380 and a 6540 array.
The RAID controller tray is a tray of drives that contains a pair of RAID controllers, instead of expansion modules. The difference
being that the controllers have ethernet network ports on them. An example is pictured here in the Sun System Handbook. This applies to a 6140 array.
If your array is not a 6140, 6540, or Flexline 380, but has a seven segment display on the RAID controller tray or module, you are likely looking at a 6580, 6780, or 6180 array. Please reference <Document 1021110.1> Sun Storage[TM] 6x80 and 2500-M2 Array Controller 7-Segment Display. Otherwise, continue.
2. Review the tables below against what you are seeing on your display for it's meaning.
Common Codes
| Code |
Description |
| 5d or Sd |
Controller is booting it's operating system |
| 85 |
This is the DEFAULT TRAY ID, displayed during normal operation
Although it can be set to anything between 85 - 93 it is not recommended to do so. |
| 88 |
Controller is being held offline by it's alternate controller |
Lockdown Codes
These codes are display if the controller has been "locked down", which generally means the controller is non-operational.
| Code |
Description |
| L0 |
Mismatched Controller Types
The Board IDs of the controllers (or any of their daughter card IDs) do not match. |
| L1 |
Missing Interconnect Cannister
An expected controller interconnect device (used for intercontroller communication) is not present. |
| L2 |
Persistent Memory Errors
Persistent ECC memory errors in either processor or RPA memory. |
| L3 |
Persistent Hardware Errors
Either PCI errors or memory initialisation errors have occurred. |
| L4 |
Persistent Data Protection Errors
Persistent EDC errors have occurred. |
| L5 |
Automatic Code Synchronisation (ACS) Failure
Alternate controller has incompatible firmware, and Automatic Code Synchronisation (ACS) is not permitted. |
| L6 |
Unsupported Host Card
The current level of firmware does not support the host card. |
| L7 |
Sub Model Identifier Not Set or Mismatched
The sub-model ID of the controllers do not match, or the controller's sub-model is not set or is set to an value unsupported by the firmware. |
| L8 |
Memory Configuration Error
Unsupported memory configuration - unsupported memory present, or memory is not in the correct memory slots |
| L9 |
Link speed mismatch |
| LF |
Lock-down with limited Management access |
| LH |
Controller firmware mismatch |
| LU |
Controller Reboot Limit Exceeded |
Hardware Initialization Patterns
These codes are displayed momentarily while the controller hardware is initialised.
These codes are typically not visible, unless the controller firmware hangs while executing that function.
| Code |
Description |
| E5 |
Invoke ABS |
| EE |
BIST Failure |
| F1 |
Processor Set-up |
| F2 |
TXC Chip Set-up |
| F3 |
Cache Disable |
| F4 |
Memory Test |
| F5 |
Invoke Boot Firmware |
| F6 |
Invoke Core Initialisation |
| F7 |
Clear Boot Memory |
| F8 |
Enable Protected Mode |
| F9 |
Memory Test Failure |
| FA |
440BX Chip set-up |
| FB |
Start Mode Determination |
| FC |
Intel Processor Initialisation |
| FD |
Intel Chipset Initialisation |
| FE |
Intel Memory Initialisation |
Hardware Initialization Errors
These codes are display if the controller encounters an error during hardware initialization.
If these codes persist after powercycling the controller then the controller should be replaced.
| Code |
Description |
| E3 |
Wrong number of host channel devices on the PCI bus
(probably because one or more host chips are dead) |
| E4 |
Wrong number of drive channel devices on the PCI bus
(probably because one or more of the drive chips are dead) |
| E5 |
No RPA device on the PCI bus
(probably because the RPA chip is dead) |
References
Attachments
This solution has no attachment
