Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1513138.1
Update Date:2015-05-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1513138.1 :   2540-M2, 2530-M2 Array Controller 7-Segment Display Reports AL Code.  


Related Items
  • Sun Storage 2540-M2 Array
  •  
  • Sun Storage 2530-M2 Array
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Arrays>SN-DK: ST25xx
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Applies to:

Sun Storage 2540-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Symptoms

A visual inspection of the 25X0-M2 array shows that the 7-segment display for the controller is not reporting the tray ID. Instead the display returns a code of AL. CAM may report the controller as Removed or non-Optimal.

Changes

 No Changes to the system.  In some cases, this is a new install.

Cause

Controller firmware either fails to finish SODmain complete (Start of Day Complete) or fails to properly boot due to corrupt Flash Firmware File on controller.

Solution

Contact support and open a new service request for assistance.

This solution is done with the serial shell interface of the raid controller. Access to the shell, is exclusive to trained, Oracle only, engineers. Your open service request needs to be routed to the appropriate level of engineering support to perform this work. 

This action plan needs to be carried out by a L2 engineer remotely or by a Field Engineer under the guidance of a L2 engineer.

The following shell commands can be used to identify problems with the flash file system:
-> ffsShow
-> ffsCrc

Issues can be identified by noticing inconsistencies in the version numbers of the ffsShow output, or looking for a NO in the Good column of the ffsCrc output.

The ffsCrc command may not provide output unless connected via the serial port of the controller. Using telnet has been seen to not produce any output.

 

Sample Output:
 

-> ffsShow
FLASH FILE SYSTEM
                                                 Flash   Flash   Load      Package
  FileName      Version          Timestamp       Offset  Length  Length ID Number  Index
============ ============ =================== ======= ======= ======= == ======= =====
PkgInfo      07.60.18.13  01/20/2010 22:24:45 0000000 0000196 0000196 04 00000001 00
System       07.60.18.13  01/20/2010 22:24:45 01A0000 014F430 033E300 02 00000001 02
DEBUG        07.60.18.13  01/20/2010 22:24:45 0640000 005DFA0 011E4F1 10 00000001 03
Diagnostics  07.60.18.13  01/20/2010 22:24:45 0760000 001D4A4 004A209 10 00000001 04
FBDT         07.60.18.13  01/20/2010 22:24:45 0780000 0000A3C 000909D 10 00000001 05
MAPI         07.60.18.13  01/20/2010 22:24:45 07A0000 001264C 003A0AF 10 00000001 06
RAID         07.60.18.13  01/20/2010 22:24:45 07C0000 0AE523C 256B561 30 00000001 07
SPY          07.60.18.13  01/20/2010 22:24:45 1A60000 000B840 001E2AE 10 00000001 08
TAPI         07.60.18.13  01/20/2010 22:24:45 1A80000 0002230 0007244 10 00000001 09
Config                    07/07/2005 21:03:55 0020000 0013857 0013857 08 00000001 01
Boot         07.60.18.13  01/20/2010 22:24:45 1F80000 003FFA0 003FFA0 01 00000001 0b
value = 0 = 0x0

-> ffsCrc
FLASH FILE 32 Bit CRC
  FileName      Version     FileCRC    Calc     FlashCRC  Calc     Good Index Comp
============  ============  ========  ========  ========  ======== ==== ===== ====
PkgInfo       07.60.18.13   E38D2574  E38D2574  E38D2574  E38D2574 yes  0000  0000
Config                      00000000  00000000  14048A2A  14048A2A yes  0001  0000
System        07.60.18.13   C6018785  C6018785  9E5401A8  9E5401A8 yes  0002  0001
DEBUG         07.60.18.13   518080C7  518080C7  C4F228FF  C4F228FF yes  0003  0001
Diagnostics   07.60.18.13   D0C4DBBB  D0C4DBBB  D2A13CE5  D2A13CE5 yes  0004  0001
FBDT          07.60.18.13   3D02D061  3D02D061  0B6713DF  0B6713DF yes  0005  0001
MAPI          07.60.18.13   A4E9D3FB  A4E9D3FB  FA3704D6  FA3704D6 yes  0006  0001
RAID          07.60.18.13   C8131017  3076BFE6  EF405E63  6FC93479 *NO* 0007  0001   --------> Indicates corrupt Flash File
SPY           07.60.18.13   DACE7293  DACE7293  FA5717A0  FA5717A0 yes  0008  0001
TAPI          07.60.18.13   FE8CC184  FE8CC184  B4882684  B4882684 yes  0009  0001
Boot          07.50.08.10   1E0D73B2  1E0D73B2  1E0D73B2  1E0D73B2 yes  000a  0000
Boot          07.60.18.13   5F09C919  5F09C919  5F09C919  5F09C919 yes  000b  0000
Boot          06.14.28.00   BCE601BE  BCE601BE  BCE601BE  BCE601BE yes  000c  0000

 

After confirming that a bad Flash file exists the firmware must be loaded to the controller displaying AL via the serial port.

Please refer to Document 2012610.1 Sun Storage 2500, 2500-M2 and 6000 Arrays: How to Load Firmware from the Controller Shell via the Serial Port for detailed instructions on how to do this.

 

References

<BUG:15866227> - 2540-M2: 7 SEGMENT DISPLAY SHOWING "AL"
<NOTE:2012610.1> - Sun Storage 2500, 2500-M2 and 6000 Arrays: How to Load Firmware from the Controller Shell via the Serial Port

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback