Where can I find Chassis code doc for HP9K D220 Series?

[Joe Ventura]

Just shipped a HP9000 D220 across country (out of warranty not on support) and It won't boot.

Getting FLT (fault codes) on Chassis LCD display.

Where can I look these up?

Thanks!

[RAC_1]

what is the error code??

Check man isl

Anil

[Robert-Jan Goossens · Accepted solution]

Hi,

Document description: HP 9000 D-Class Servers: System and Memory Hard Failure Faults
Document id: DCKBCA00000127

Europe
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000078389716

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000078389716

[Admin :the above links are no longer valid and removed]

Regards,
Robert-Jan

[Joe Ventura]

RAC -

man isl?

Box won't boot how would I do that.

Nevermind I got the answer above

[Robert Bennett_3]

Here's another document that could be handy - good luck.

http://docs.hp.com/en/A3262-90013/A3262-90013.pdf

[Admin :the above links are no longer valid and removed]

[Stf]

I hope this could be very helpfull for you !!!

http://www.openpa.net/systems/ultralight.html

Stf ;-)

[vinod_25]

hi jo

have some chasis codes collected for D class and R class servers...for diagnostics... i will share it with you all...


CE00 isl is executing.
CE01 isl is autobooting from the autoexecute file.
CE02 Cannot find an autoexecute file. autoboot aborted.
CE03 No console found, isl can only autoboot.
CE05 Directory of utilities is too big, isl reads only 2K bytes.


CE06 autoexecute file is inconsistent. autoboot aborted.
CE07 Utility file header inconsistent: SOM values invalid.
CE08 autoexecute file input string exceeds 2048 characters. autoboot aborted.
CE09 isl command or utility name exceeds 10 characters.
CE0F isl has transferred control to the utility.
CE10 Internal inconsistency: Volume label - FATAL.
CE11 Internal inconsistency: Directory - FATAL.
CE12 Error reading autoexecute file.
CE13 Error reading from console - FATAL.
CE14 Error writing to console - FATAL.
CE15 Not an isl command or utility.
CE16 Utility file header inconsistent: Invalid System ID.
CE17 Error reading utility file header.
CE18 Utility file header inconsistent: Bad magic number.
CE19 Utility would overlay isl in memory.
CE1A Utility requires more memory than is configured.
CE1B Error reading utility into memory.
CE1C Incorrect checksum: Reading utility into memory.
CE1D Console needed - FATAL.
CE1E Internal inconsistency: Boot device class - FATAL.
CE21 Destination memory address of utility is invalid.
CE22 Utility file header inconsistent: pdc_cache entry.
CE23 Internal inconsistency: iodc_entry_init - FATAL.
CE24 Internal inconsistency: iodc_entry_init - console - FATAL.
CE25 Internal inconsistency: iodc_entry_init - boot device - FATAL.
CE26 Utility file header inconsistent: Bad aux_id.
CE27 Bad utility file type.



Date: 3/9/01
Document description: HP 9000 D-Class Servers: System and Memory Hard Failure Faults
Document id: DCKBCA00000127


You may provide feedback on this document

HP 9000 D-Class Servers: System and Memory Hard Failure Faults
DocId: DCKBCA00000127 Updated: 5/15/05 7:44:00 PM
PROBLEM
How can I use Chassis Codes to troubleshoot system and memory hard failure faults on the HP 9000 D-Class Servers?
RESOLUTION
Listed below are chassis code tables describing system and memory hard failure faults. These faults occur before the operating system is launched, during the power-up selftests and system initialization processes. After determining the chassis code from the LCD display, refer to the appropriate chassis code table for the corresponding chassis code. Then note the cause of the failure and follow the steps listed in the action column.
Contents

* Description of Front Panel LCD
* System Hardware Failure Chassis Codes
* D200/D210/D310 Memory Failure Chassis Codes
* Dx20/Dx30 Memory Failure Chassis Codes
* Dx50/Dx60/Dx70/Dx80/R380/D390/R390 Memory Failure Chassis Codes

Description of Front Panel LCD

The front panel displays firmware and HP-UX operating system progress codes. See the example below:

RUN1 FXYF2 REMOTE3

HP - D3505 CPUxx4

Item Description
1 System State, sometimes referred to as operating state (Ostat)
2 Chassis Code (For detailed description of individual codes, refer to one of the appropriate tables below.)
3 REMOTE: indicates REMOTE enabled
< blank >: indicates REMOTE disabled
4 Processor Information
5 System Information / Model Identity

The possible System States are listed below.

* FLT - A hardware error has been detected
* TEST - Hardware being tested
* INIT - Hardware being initialized
* SHUT - System being shutdown
* WARN - A non-optimal operating condition exists
* RUN - System is running the operating system
* OFF
* ALL

When the system is operating normally, the RUN message should display. If an FLT or WARN message displays, write down all of the information displayed and contact your System Administrator.

Each Chassis Code consists of four hex digits: d0, d1, d2, d3.

Return to Contents

System Hardware Failure Chassis Codes

Code Cause Action
1xxx CPU, TLB, Coprocessor, or MFIOC Contact the Response Center
2xxx

21xx (for Dx20, Dx30)
Cache errors. 2nd level cache errors. Contact the Response Center
3xxx (except 30FF) Processor Dependent Hardware (PDH). Contact the Response Center
4xxx Late Selftest errors. Contact the Response Center
5xxx

5007 or 500D (for Dx50 only)
Bus Transaction errors. HSC bus error (or HPPB bus on AP card).

1. Replace I/O cards on GSC.
2. For D250/D350, replace AP card.
3. If problem persists, contact the Response Center

7xxx Memory Subsystem Fault. Refer to the appropriate 'Memory Failure Chassis Code' table.
8000 to 8004 (except Dx50)

801x or 831x (for Dx50 only)


I/O Bus adapter fault (located on AP card)

Second digit is AP slot number; 0 or 3


1. Replace Access Port card.
2. If problem persists, contact the Response Center.

802B or 803D (for Dx50 only) I/O bus overlap or too many graphics. HSC slot 3 (10/12).

1. Check graphics configuration.
2. Replace graphics card.
3. Replace other HSC cards.
4. If problem persists, contact the Response Center.

84xx to 85xx I/O Device fault or MFIOC error. Contact the Response Center.
9xxx Console Initialization errors.

1. Check console path and actual configured path.
2. Check console cable and connections.
3. If problem persists, contact the Response Center.

A088 Unable to boot and no console found.

1. Check console path and configured boot path.
2. Check boot device cable, console cable and connections.
3. If problem persists, contact the Response Center.

A0FF Unknown launch error

1. Check system configuration.
2. If problem persists, contact the Response Center.

C5F0 Error reading IPL from primary boot media, and no console.

1. Attempt to boot from alternate media or device.

a. If alternate boot succeeds, replace the primary boot device.

b. If boot fails, contact the Response Center.


2. If problem persists, contact the Response Center.

CBFF Nested HPMC

1. Perform a Transfer of Control (TOC) to collect a core dump.
2. Contact the Response Center

Return to Contents
D200/D210/D310 Memory Failure Chassis Codes

Code Cause Action
700y HPMC memory error (y=0 or 1, the bank number) Replace memory SIMM in slot 0
701y HPMC memory error Replace memory SIMM in slot 1
702y HPMC memory error Replace memory SIMM in slot 2
703y HPMC memory error Replace memory SIMM in slot 3
704y HPMC memory error Replace memory SIMM in slot 4
705y HPMC memory error Replace memory SIMM in slot 5
706y HPMC memory error Replace memory SIMM in slot 6
707y HPMC memory error Replace memory SIMM in slot 7
70Dy No memory found

1. Reseat memory SIMMs
2. If problem persists, contact the Response Center.

Return to Contents
Dx20/Dx30 Memory Failure Chassis Codes

Code Cause Action
7000 HPMC in the memory system Contact the Response
70FF Unknown HPMC Contact the Response
7301 SIMM 0 bytes are not equal Refer to the memory configuration table for the deallocated memory bank.
7302 SIMM 1 bytes are not equal Refer to the memory configuration table for the deallocated memory bank.
7303 SIMM 0 data and SIMM 1 data bytes are not equal Refer to the memory configuration table for the deallocated memory bank.
7304 SIMM pair not equal size Refer to the memory configuration table for the deallocated memory bank.
7307 ECC test failed on bank Refer to the memory configuration table for the deallocated memory bank.
7403 Address did not map to bank Contact the Response Center
7406 Failed second level cache to memory access Contact the Response Center
7407 Second level cache tag parity error Contact the Response Center
7500 No RAM found

1. Re-seat or install SIMM pairs.
2. If problem persists, contact the Response Center.

7604 No bits set in test status Contact the Response Center
7Fxy Memory failure Replace memory SIMM.

x equals slot number, y equals bank (A or B).

Return to Contents
Dx50/Dx60/Dx70/Dx80/R380/D390/R390 Memory Failure Chassis Codes

Code Cause Action
7000 HPMC in the memory system Contact the Response Center
7001 Icache parity fault in memory test Contact the Response Center
7002 Dcache parity fault in memory test Contact the Response Center
7003 MSI read time-out (usually caused by an invalid memory address) Contact the Response Center
7004 MSI write time-out (usually caused by an invalid memory address) Contact the Response Center
7005 Processor/Memory bus parity fault Contact the Response Center
7006 Write bomb fault (Processor/Memory bus parity detected on incoming data) Contact the Response Center
7007 Memory address ECC fault Contact the Response Center
7008 Multi-bit memory fault Replace memory SIMM pair
7009 Dx70/Dx80 only, single bit memory error Replace memory SIMM pair
70FF Unknown HPMC Contact the Response Center
7FFF Catastrophic memory fault Contact the Response Center
7101 Master Memory controller not responding Contact the Response Center
7102 Master Memory controller not ready fault Contact the Response Center
7103 Master Memory controller failed to clear Contact the Response Center
7104 Master Memory controller sticky bits Contact the Response Center
7105 Master Memory controller bad revision Contact the Response Center
7106 Master Memory controller register fault Contact the Response Center
7107 Master Memory controller fault in ECC test Contact the Response Center
7200 No slave Memory Controller available Contact the Response Center
721x Slave Memory Controller failed, x = SMC number Contact the Response Center
722x Bad Slave Memory Controller revision, x = SMC number Contact the Response Center
723x Slave memory Controller failed to respond, x = SMC number Contact the Response Center
7301 SIMM 0 bytes are not equal Refer to the memory configuration tables for the deallocated memory bank.
7302 SIMM 1 bytes are not equal Refer to the memory configuration tables for the deallocated memory bank.
7303 SIMM 0 data and SIMM 1 data not equal Refer to the memory configuration tables for the deallocated memory bank.
7304 SIMM pair not equal size Refer to the memory configuration tables for the deallocated memory bank.
7305 Multi-bit error occurred during selftest Refer to the PDT for SIMM pair number
7306 Address test failed on bank Refer to the memory configuration tables for the deallocated memory bank.
7307 ECC test failed on bank Refer to the memory configuration tables for the deallocated memory bank.
7308 Single bit memory error caused HPMC This is a selftest error, should not occur during normal operation. Contact the Response Center
7401 No memory SIMMS installed

1. Re-seat or install SIMM pairs
2. If problem persists, Contact the Response Center

7402 Both EDO and STD memory SIMMs installed EDO SIMMs not supported
7403 Address did not map to bank Contact the Response Center
7404 Invalid memory address Contact the Response Center
7405 Dual issue processor test failed Contact the Response Center
7500 No RAM found

1. Re-seat or install SIMM pairs
2. If problem persists, contact the Response Center

7501 Not enough good memory to run Operating System Very memory configuration using PDC ME command
7502 Not enough good memory to run Boot Console Handler (BCH) Very memory configuration using PDC ME command
7604 No bits set in test status Contact the Response Center
7702 Warning, abbreviated memory test Fast Boot is Enabled
7703 SIMM loading warning Verify memory configuration using PDC ME command. Large SIMM sizes should be loaded first
7704 RAM bus warning Verify memory configuration using PDC ME command.
7705 Not enough good memory to run OS Verify memory configuration using PDC ME command.
7800 Dx50/Dx60 only, PDT disabled Warning/Halt PDT is full of multi-bit entries as another Multi-bit error (MBE) occurred. Verify PDT level with PCD PDT command and replace failed SIMM pair.
7801 Dx50/Dx60 only, overwrite single bit error with MBE in PDT Check PDT level with PDC PDT command
7802 Dx50/Dx60 only, duplicate PDT entry Contact the Response Center
7803 Dx50/Dx60 only, EEPROM fault while updating PDT Contact the Response Center
7804 Dx50/Dx60 only, PDT table is full of MBE Verify PDT level with PDC PDT command and replace failed SIMM pair
7D03 Dx50/Dx60 only, MSI read time-out (HPMC, caused by an invalid memory address) Contact the Response Center
7D04 Dx50/Dx60 only, MSI write time-out (HPMC, caused by an invalid memory address) Contact the Response Center
7D05 Dx50/Dx60 only, Processor/Memory bus parity fault (HPMC) Contact the Response Center
7D06 Dx50/Dx60 only, write bomb fault (Processor/Memory bus parity error detected on incoming data) Contact the Response Center
7D07 Dx50/Dx60 only, memory address fault (HPMC) Contact the Response Center
7D08 Dx50/Dx60 only, multi-bit memory fault (HPMC) Verify PDT level with PDC PDT command and replace failed SIMM pair
7D09 Dx50/Dx60 only, single bit memory fault (HPMC, unexpected HPMC during memory self test) Contact the Response Center
7D0A Dx50/Dx60 only, address did not map to bank (HPMC) Contact the Response Center
7FXY Memory HPMC error Y = SIMM pair number, replace SIMM pair indicated by Y
7FFF Catastrophic memory fault Contact the Response Center

Hope this is what you expected in this forum....

Regards

Vinod