BladeCenter JS21 Types 7988 and 8844
P roblem Dete rminatio n an d Se rvi ce Gui de
BladeCenter JS21 Types 7988 and 8844
P roblem Dete rminatio n an d Se rvi ce Gui de
Note: Before using this information and the product it supports, read the general information in Appendix B, “Notices,” on page
173, and the Warranty and Support Information document on the IBM BladeCenter Documentation CD.
Sixth Edition (November 2010)
© Copyright IBM Corporation 2007.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Safety ............................vii
Guidelines for trained service technicians ...............viii
Inspecting for unsafe conditions .................viii
Guidelines for servicing electrical equipment .............viii
Safety statements ........................ix
Chapter 1. Introduction......................1
Related documentation ......................1
Notices and statements in this document................2
Features and specifications .....................3
Blade server control panel buttons and LEDs ..............4
Turning on the blade server.....................6
Turning off the blade server.....................7
System-board layouts .......................7
System-board connectors ....................7
System-board jumpers .....................8
System-board LEDs ......................8
Chapter 2. Diagnostics ......................9
Diagnostic tools .........................9
POST checkpoint codes ......................9
Progress codes........................10
Attention codes ........................34
Error codes .........................37
Location codes ........................66
Error logs ..........................66
Service request numbers .....................67
Using the SRN tables .....................67
SRN tables .........................67
Failing function codes .....................104
Checkout procedure ......................106
About the checkout procedure ..................106
Performing the checkout procedure ................106
Verifying the partition configuration .................108
Running the diagnostics program ..................108
Starting AIX concurrent diagnostics ................108
Starting standalone diagnostics from a CD .............109
Starting standalone diagnostics from a NIM server ..........110
Using the diagnostics program ..................111
Boot problem resolution .....................112
Troubleshooting tables......................113
CD or DVD drive problems ...................114
Diskette drive problems ....................115
General problems ......................115
Hard disk drive problems ....................116
Intermittent problems .....................116
Keyboard problems ......................117
Memory problems ......................118
Microprocessor problems ....................118
Monitor or video problems ...................119
Network connection problems ..................120
Optional device problems ...................121
Power problems .......................122
© Copyright IBM Corp. 2007 iii
Service processor problems...................123
Software problems ......................123
Universal Serial Bus (USB) port problems .............123
Light path diagnostics ......................124
Viewing the light path diagnostics LEDs ..............124
Light path diagnostics LEDs ..................125
Firmware problem isolation ....................127
Recovering the system firmware ..................127
Starting the PERM image ...................127
Recovering the TEMP image from the PERM image..........128
Verifying the system firmware levels ...............129
Committing the TEMP system firmware image ............129
Solving shared BladeCenter resource problems ............130
Keyboard problems ......................130
Media tray problems .....................131
Network connection problems ..................133
Power problems .......................133
Video problems .......................134
Solving undetermined problems ..................135
Calling IBM for service .....................136
Chapter 3. Parts listing, Types 7988 and 8844 ............137
Chapter 4. Removing and replacing blade server components .....141
Installation guidelines ......................141
System reliability guidelines ...................142
Handling static-sensitive devices .................142
Returning a device or component ................142
Removing the blade server from a BladeCenter unit ...........143
Installing the blade server in a BladeCenter unit ............144
Removing and replacing Tier 1 CRUs ................145
Removing the blade server cover.................145
Installing the blade server cover .................146
Removing the bezel assembly ..................147
Installing the bezel assembly ..................148
Removing a SAS hard disk drive .................149
Installing a SAS hard disk drive .................150
Removing a memory module ..................151
Installing a memory module ...................152
Removing and installing an I/O expansion card ...........153
Removing the battery .....................157
Installing the battery .....................157
Removing a hard disk drive tray .................159
Installing a hard disk drive tray .................160
Removing the expansion bracket .................161
Installing the expansion bracket .................162
Removing and replacing Tier 2 CRUs ................163
Replacing the system-board and chassis assembly ..........163
Chapter 5. Configuration information and instructions ........165
Updating the firmware ......................165
Configuring the blade server ...................165
Using the SMS utility ......................166
Starting the SMS utility ....................166
SMS utility menu choices ...................166
Configuring the Gigabit Ethernet controllers ..............167
iv BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Creating a CE login .......................168
Blade server Ethernet controller enumeration .............168
Configuring a SAS RAID array...................169
Updating IBM Director ......................169
Checking the status of the media tray ................170
Appendix A. Getting help and technical assistance ..........171
Before you call ........................171
Using the documentation .....................171
Getting help and information from the World Wide Web .........171
Software service and support ...................172
Hardware service and support ...................172
IBM Taiwan product service ....................172
Appendix B. Notices ......................173
Trademarks..........................174
Important notes ........................174
Product recycling and disposal ..................175
Battery return program .....................176
Electronic emission notices ....................178
Federal Communications Commission (FCC) statement ........178
Industry Canada Class A emission compliance statement ........178
Avis de conformité à la réglementation d'Industrie Canada .......178
Australia and New Zealand Class A statement ............178
United Kingdom telecommunications safety requirement ........178
European Union EMC Directive conformance statement ........178
Taiwanese Class A warning statement ...............179
Chinese Class A warning statement ................179
Japanese Voluntary Control Council for Interference (VCCI) statement 179
Index ............................181
Contents v
vi BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Safety
Before installing this product, read the Safety Information.
Antes de instalar este produto, leia as Informações de Segurança.
Pred instalací tohoto produktu si prectete prírucku bezpecnostních instrukcí.
Læs sikkerhedsforskrifterne, før du installerer dette produkt.
Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.
Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information.
Avant d'installer ce produit, lisez les consignes de sécurité.
Vor der Installation dieses Produkts die Sicherheitshinweise lesen.
Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.
Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.
Antes de instalar este produto, leia as Informações sobre Segurança.
Antes de instalar este producto, lea la información de seguridad.
Läs säkerhetsinformationen innan du installerar den här produkten.
© Copyright IBM Corp. 2007 vii
Guidelines for trained service technicians
This section contains information for trained service technicians.
Inspecting for unsafe conditions
Use the information in this section to help you identify potential unsafe conditions in
an IBM product that you are working on. Each IBM product, as it was designed and
manufactured, has required safety items to protect users and service technicians
from injury. The information in this section addresses only those items. Use good
judgment to identify potential unsafe conditions that might be caused by non-IBM
alterations or attachment of non-IBM features or options that are not addressed in
this section. If you identify an unsafe condition, you must determine how serious the
hazard is and whether you must correct the problem before you work on the
product.
Consider the following conditions and the safety hazards that they present:
v Electrical hazards, especially primary power. Primary voltage on the frame can
cause serious or fatal electrical shock.
v Explosive hazards, such as a damaged CRT face or a bulging capacitor.
v Mechanical hazards, such as loose or missing hardware.
To inspect the product for potential unsafe conditions, complete the following steps:
1. Make sure that the power is off and the power cord is disconnected.
2. Make sure that the exterior cover is not damaged, loose, or broken, and
observe any sharp edges.
3. Check the power cord:
v Make sure that the third-wire ground connector is in good condition. Use a
meter to measure third-wire ground continuity for 0.1 ohm or less between
the external ground pin and the frame ground.
v Make sure that the power cord is the correct type, as specified in the
documentation for your BladeCenter unit type.
v Make sure that the insulation is not frayed or worn.
4. Remove the cover.
5. Check for any obvious non-IBM alterations. Use good judgment as to the safety
of any non-IBM alterations.
6. Check inside the blade server for any obvious unsafe conditions, such as metal
filings, contamination, water or other liquid, or signs of fire or smoke damage.
7. Check for worn, frayed, or pinched cables.
8. Make sure that the power-supply cover fasteners (screws or rivets) have not
been removed or tampered with.
Guidelines for servicing electrical equipment
Observe the following guidelines when servicing electrical equipment:
v Check the area for electrical hazards such as moist floors, nongrounded power
extension cords, and missing safety grounds.
v Use only approved tools and test equipment. Some hand tools have handles that
are covered with a soft material that does not provide insulation from live
electrical current.
v Regularly inspect and maintain your electrical hand tools for safe operational
condition. Do not use worn or broken tools or testers.
viii BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Do not touch the reflective surface of a dental mirror to a live electrical circuit.
The surface is conductive and can cause personal injury or equipment damage if
it touches a live electrical circuit.
v Some rubber floor mats contain small conductive fibers to decrease electrostatic
discharge. Do not use this type of mat to protect yourself from electrical shock.
v Do not work alone under hazardous conditions or near equipment that has
hazardous voltages.
v Locate the emergency power-off (EPO) switch, disconnecting switch, or electrical
outlet so that you can turn off the power quickly in the event of an electrical
accident.
v Disconnect all power before you perform a mechanical inspection, work near
power supplies, or remove or install main units.
v Before you work on the equipment, disconnect the power cord. If you cannot
disconnect the power cord, have the customer power-off the wall box that
supplies power to the equipment and lock the wall box in the off position.
v Never assume that power has been disconnected from a circuit. Check it to
make sure that it has been disconnected.
v If you have to work on equipment that has exposed electrical circuits, observe
the following precautions:
– Make sure that another person who is familiar with the power-off controls is
near you and is available to turn off the power if necessary.
– When you are working with powered-on electrical equipment, use only one
hand. Keep the other hand in your pocket or behind your back to avoid
creating a complete circuit that could cause an electrical shock.
– When using a tester, set the controls correctly and use the approved probe
leads and accessories for that tester.
– Stand on a suitable rubber mat to insulate you from grounds such as metal
floor strips and equipment frames.
v Use extreme care when measuring high voltages.
v To ensure proper grounding of components such as power supplies, pumps,
blowers, fans, and motor generators, do not service these components outside of
their normal operating locations.
v If an electrical accident occurs, use caution, turn off the power, and send another
person to get medical aid.
Safety statements
Important:
Each caution and danger statement in this documentation begins with a number.
This number is used to cross reference an English-language caution or danger
statement with translated versions of the caution or danger statement in the Safety
Information document.
For example, if a caution statement begins with a number 1, translations for that
caution statement appear in the Safety Information document under statement 1.
Be sure to read all caution and danger statements in this documentation before
performing the instructions. Read any additional safety information that comes with
your blade server or optional device before you install the device.
Safety ix
Statement 1:
DANGER
Electrical current from power, telephone, and communication cables is
hazardous.
To avoid a shock hazard:
v Do not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical
storm.
v Connect all power cords to a properly wired and grounded electrical
outlet.
v Connect to properly wired outlets any equipment that will be attached to
this product.
v When possible, use one hand only to connect or disconnect signal
cables.
v Never turn on any equipment when there is evidence of fire, water, or
structural damage.
v Disconnect the attached power cords, telecommunications systems,
networks, and modems before you open the device covers, unless
instructed otherwise in the installation and configuration procedures.
v Connect and disconnect cables as described in the following table when
installing, moving, or opening covers on this product or attached
devices.
To Connect: To Disconnect:
1. Turn everything OFF.
2. First, attach all cables to devices.
3. Attach signal cables to connectors.
4. Attach power cords to outlet.
5. Turn device ON.
1. Turn everything OFF.
2. First, remove power cords from outlet.
3. Remove signal cables from connectors.
4. Remove all cables from devices.
x BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Statement 2:
CAUTION:
When replacing the lithium battery, use only IBM Part Number 33F8354 or an
equivalent type battery recommended by the manufacturer. If your system has
a module containing a lithium battery, replace it only with the same module
type made by the same manufacturer. The battery contains lithium and can
explode if not properly used, handled, or disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Statement 3:
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable
parts inside the device.
v Use of controls or adjustments or performance of procedures other than
those specified herein might result in hazardous radiation exposure.
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser
diode. Note the following.
Laser radiation when open. Do not stare into the beam, do not view directly
with optical instruments, and avoid direct exposure to the beam.
Safety xi
Statement 4:
≥ 18 kg (39.7 lb) ≥ 32 kg (70.5 lb) ≥ 55 kg (121.2 lb)
CAUTION:
Use safe practices when lifting.
Statement 5:
CAUTION:
The power control button on the device and the power switch on the power
supply do not turn off the electrical current supplied to the device. The device
also might have more than one power cord. To remove all electrical current
from the device, ensure that all power cords are disconnected from the power
source.
1 2
xii BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Statement 8:
CAUTION:
Never remove the cover on a power supply or any part that has the following
label attached.
Hazardous voltage, current, and energy levels are present inside any
component that has this label attached. There are no serviceable parts inside
these components. If you suspect a problem with one of these parts, contact
a service technician.
Statement 10:
CAUTION:
Do not place any object on top of rack-mounted devices.
Safety xiii
xiv BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Chapter 1. Introduction
This Problem Determination and Service Guide contains information to help you
solve problems that might occur in your IBM
8844 blade server. It describes the diagnostic tools that come with the blade server,
error codes and suggested actions, and instructions for replacing failing
components.
Replaceable components are of three types:
v Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your
responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for
the installation.
v Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or
request IBM to install it, at no additional charge, under the type of warranty
service that is designated for your blade server.
v Field replaceable unit (FRU): FRUs must be installed only by trained service
technicians.
For information about the terms of the warranty and getting service and assistance,
see the Warranty and Support Information document.
Related documentation
In addition to this document, the following documentation also comes with the blade
server:
v Installation and User’s Guide
This printed document contains general information about the blade server,
including how to install supported options and how to configure the blade server.
v Safety Information
This document is in Portable Document Format (PDF) on the Documentation CD.
It contains translated caution and danger statements. Each caution and danger
statement that appears in the documentation has a number that you can use to
locate the corresponding statement in your language in the Safety Information
document.
v Warranty and Support Information
This document is in PDF on the Documentation CD. It contains information about
the terms of the warranty and about service and assistance.
®
BladeCenter®JS21 Type 7988 or
Depending on the blade server model, additional documentation might be included
on the Documentation CD.
The blade server might have features that are not described in the documentation
that comes with the blade server. The documentation might be updated occasionally
to include information about those features, or technical updates might be available
to provide additional information that is not included in the blade server
documentation. The most recent versions of all BladeCenter documentation are at
http://www.ibm.com/systems/support/.
In addition to the documentation in this library, be sure to review the IBM
BladeCenter Planning and Installation Guide for your BladeCenter unit type for
information to help you prepare for system installation and configuration. This
document is also available at http://www.ibm.com/systems/support/.
© Copyright IBM Corp. 2007 1
Notices and statements in this document
The caution and danger statements that appear in this document are also in the
multilingual Safety Information document, which is on the Documentation CD. Each
statement is numbered for reference to the corresponding statement in the Safety
Information document.
The following notices and statements are used in this document:
v Note: These notices provide important tips, guidance, or advice.
v Important: These notices provide information or advice that might help you avoid
inconvenient or problem situations.
v Attention: These notices indicate potential damage to programs, devices, or
data. An attention notice is placed just before the instruction or situation in which
damage could occur.
v Caution: These statements indicate situations that can be potentially hazardous
to you. A caution statement is placed just before the description of a potentially
hazardous procedure step or situation.
v Danger: These statements indicate situations that can be potentially lethal or
extremely hazardous to you. A danger statement is placed just before the
description of a potentially lethal or extremely hazardous procedure step or
situation.
2 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Features and specifications
The following table is a summary of the features and specifications of the JS21
Types 7988 and 8844 blade servers operating in a non-NEBS/ETSI (a non-Network
Equipment Building System/European Telecommunications Standards Institute)
environment.
Notes:
v Power, cooling, removable-media drives, external ports, and advanced system
management are provided by the BladeCenter unit.
v The operating system in the blade server must provide USB support for the blade
server to recognize and use the removable-media drives and front-panel USB
ports. The BladeCenter unit uses USB for internal communications with these
devices.
Microprocessor:
Support for:
v Two single-core, 64-bit, IBM
PowerPC
(2.7 GHz in BladeCenter H unit, 2.6
GHz in other BladeCenter units) or
v Two dual-core, 64-bit, IBM
PowerPC 970MP microprocessors
(2.5 GHz in BladeCenter H unit, 2.3
GHz in other BladeCenter units)
Memory:
v Dual-channel (DDR2) with 4 DIMM
slots
v Supports 512 MB, 1 GB, 2 GB, and
4 GB DIMMs, for a maximum of 16
GB (as of the date of this
publication)
v Supports 2-way interleaved, DDR2,
PC2-3200 or PC2-4200, ECC
SDRAM registered x4 (Chipkill)
DIMMs
Drives: Support for two internal
small-form-factor Serial Attached SCSI
(SAS) drives
®
970MP microprocessors
Integrated functions:
v Two 1 Gigabit Ethernet controllers
v Expansion card interface
v Intelligent Platform Management
Interface (IPMI)
v Baseboard management controller
(BMC) with IPMI firmware
v ATI RN50 ES1000 video controller
v SAS RAID controller
v Light path diagnostics
v Local service processor (BMC)
v RS-485 interface for
communication with the
management module
v Automatic server restart (ASR)
v Serial over LAN (SOL)
v Four Universal Serial Bus (USB)
buses for communication with
keyboard, diskette drive, and CD
drive
Predictive Failure Analysis (PFA)
alerts:
v Microprocessor
v Memory
Electrical input: 12Vdc
Environment:
v Air temperature:
– Blade server on: 10° to 35°C (50°
to 95°F). Altitude: 0 to 914 m
(3000 ft)
– Blade server on: 10° to 32°C (50°
to 90°F). Altitude: 914 m to 2133
m (3000 ft to 7000 ft)
– Blade server off: -40° to 60°C
(-40° to 140°F)
v Humidity:
– Blade server on: 8% to 80%
– Blade server off: 5% to 80%
Size:
v Height: 24.5 cm (9.7 inches)
v Depth: 44.6 cm (17.6 inches)
v Width: 2.9 cm (1.14 inches)
v Maximum weight: 5.0 kg (11 lb)
Chapter 1. Introduction 3
Blade server control panel buttons and LEDs
This section describes the blade server control panel buttons and LEDs.
Note: The control panel door is shown in the closed (normal) position in the
following illustration. To access the power-control button, you must open the control
panel door.
Activity LED
Location LED
Keyboard/video select button
Information LED
Blade-error LED
Media-tray select
button
Power-control button
Power-on LED
Keyboard/video select button: When using a supported Linux operating system,
press this button to associate the shared BladeCenter unit keyboard and video
ports with the blade server.
Notes:
v The use of a mouse or pointing device is not supported by the JS21 blade
server.
v The Linux operating system in the blade server must provide USB support for the
blade server to recognize and use the keyboard, even if the keyboard has a
PS/2-style connector.
v The keyboard and video are available after the Linux operating system loads.
Power-on self-test (POST) codes and diagnostics are not supported using the
keyboard and video.
v For information about supported Linux operating systems, see
http://www.ibm.com/servers/eserver/serverproven/compat/us/.
The LED on this button flashes while the request is being processed, then is lit
when the ownership of the keyboard and video has been transferred to the blade
server. It can take approximately 20 seconds to switch the keyboard and video
control to the blade server.
Using a keyboard that is directly attached to the management module, you can
press keyboard keys in the following sequence to switch keyboard and video control
between blade servers:
NumLock NumLock blade_server_number Enter
4 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Where blade_server_number is the two-digit number for the blade bay in which
the blade server is installed. When using some keyboards, such as the 28L3644
(37L0888) keyboard, you will need to hold down the Shift key while entering this
key sequence.
If there is no response when you press the keyboard/video select button, you can
use the management-module Web interface to determine whether local control has
been disabled on the blade server.
Activity LED: When this green LED is lit, it indicates that there is activity on the
hard disk drive or network.
Location LED: When this blue LED is lit, it has been turned on by the system
administrator to aid in visually locating the blade server. The location LED can be
turned off through the management-module Web interface or through IBM Director
Console.
Information LED: When this amber LED is lit, it indicates that information about a
system error for the blade server has been placed in the Management Module
Event Log. The information LED can be turned off through the management-module
Web interface or through IBM Director Console.
Blade-error LED: When this amber LED is lit, it indicates that a system error has
occurred in the blade server. The blade-error LED will turn off only after the error is
corrected.
Media-tray select button: Press this button to associate the shared BladeCenter
unit media tray (removable-media drives and front-panel USB ports) with the blade
server. The LED on the button flashes while the request is being processed, then is
lit when the ownership of the media tray has been transferred to the blade server. It
can take approximately 20 seconds for the operating system in the blade server to
recognize the media tray.
If there is no response when you press the media-tray select button, you can use
the management-module Web interface to determine whether local control has been
disabled on the blade server.
Note: The operating system in the blade server must provide USB support for the
blade server to recognize and use the removable-media drives and USB ports.
Power-control button: This button is behind the control panel door. Press this
button to turn on or turn off the blade server.
Note: The power-control button has effect only if local power control is enabled for
the blade server. Local power control is enabled and disabled through the
management-module Web interface.
Power-on LED: This green LED indicates the power status of the blade server in
the following manner:
v Flashing rapidly: The service processor (BMC) on the blade server is
communicating with the management module.
v Flashing slowly: The blade server has power but is not turned on.
v Lit continuously: The blade server has power and is turned on.
Chapter 1. Introduction 5
Turning on the blade server
After you connect the blade server to power through the BladeCenter unit, the blade
server can start in any of the following ways:
v You can press the power-control button on the front of the blade server (behind
the control panel door, see “Blade server control panel buttons and LEDs” on
page 4) to start the blade server.
Notes:
1. Wait until the power-on LED on the blade server flashes slowly before
pressing the blade server power-control button. If the power-on LED is
flashing rapidly, the service processor in the management module is
initializing; therefore, the power-control button on the blade server does not
respond.
2. While the blade server is starting, the power-on LED on the front of the blade
server is lit. See “Blade server control panel buttons and LEDs” on page 4 for
the power-on LED states.
v If a power failure occurs, the BladeCenter unit and then the blade server can
start automatically when power is restored (if the blade server is configured
through the management module to do so).
v You can turn on the blade server remotely by using the management module.
v If the blade server is connected to power (the power-on LED is flashing slowly),
the operating system supports the Wake on LAN feature, and the Wake on LAN
feature has not been disabled through the management module, the Wake on
LAN feature can turn on the blade server. However, the blade server can only
receive the Wake on LAN command through the ethernet ports that are
integrated into the system board, not through the ethernet ports on an installed
I/O expansion card.
6 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Turning off the blade server
When you turn off the blade server, it is still connected to power through the
BladeCenter unit. The blade server can respond to requests from the service
processor, such as a remote request to turn on the blade server. To remove all
power from the blade server, you must remove it from the BladeCenter unit.
Shut down the operating system before you turn off the blade server. See the
operating-system documentation for information about shutting down the operating
system.
The blade server can be turned off in any of the following ways:
v You can press the power-control button on the blade server (behind the control
panel door, see “Blade server control panel buttons and LEDs” on page 4). This
also starts an orderly shutdown of the operating system, if this feature is
supported by the operating system.
Note: After turning off the blade server, wait at least 5 seconds before you press
the power-control button to turn on the blade server again.
v If the operating system stops functioning, you can press and hold the
power-control button for more than 4 seconds to turn off the blade server.
v The management module can turn off the blade server.
System-board layouts
The following illustrations show the connectors, jumpers, and LEDs on the system
board. The illustrations in this document might differ slightly from your hardware.
System-board connectors
The following illustration shows the connectors on the system board.
I/O expansion option (J18)
I/O expansion option (J22)
Blade expansion option (J200)
Hard disk drive 0 (J500)
Hard disk drive 1 (J501)
DIMM 1 (J400)
DIMM 2 (J401)
DIMM 3 (J402)
DIMM 4 (J403)
Control panel (J4)
Battery (BH1)
Chapter 1. Introduction 7
System-board jumpers
The following illustration shows the jumpers on the system board.
System-board LEDs
The following illustration shows the LEDs on the system board. You have to remove
the blade server from the BladeCenter unit, open the cover, and press the light path
diagnostics switch to light any error LEDs that were turned on during processing.
BIOS code page jumper (J14)
3
2
1
DIMM 1 error LED (CR40)
DIMM 2 error LED (CR45)
DIMM 3 error LED (CR46)
DIMM 4 error LED (CR53)
I/O expansion option
error LED (CR34)
System-management processor error LED (CR27)
NMI error LED (CR17)
Temperature error LED (CR16)
System board error LED (CR20)
Microprocessor 1 error LED (CR19)
Microprocessor 0 error LED (CR58)
Light path diagnostics
switch (SW1)
Hard disk drive 1 error LED (CR3)
Hard disk drive 0 error LED (CR4)
8 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Chapter 2. Diagnostics
This chapter describes the diagnostic tools that are available to help you solve
problems that might occur in the blade server.
If you cannot locate and correct the problem using the information in this chapter,
see Appendix A, “Getting help and technical assistance,” on page 171 for more
information.
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related
problems:
v POST checkpoints
The power-on self-test (POST) in the firmware generates eight-digit checkpoint
codes. If the firmware detects a problem during POST, an eight-digit error code
will be displayed. See “POST checkpoint codes” for more information.
v Troubleshooting tables
These tables list problem symptoms and actions to correct the problems. See
“Troubleshooting tables” on page 113 for more information.
v Light path diagnostics
Use the light path diagnostics to diagnose system errors quickly. See “Light path
diagnostics” on page 124 for more information.
POST checkpoint codes
When you turn on the blade server, it performs a series of tests to check the
operation of the blade server components. This series of tests is called the
power-on self-test, or POST. During POST, a series of eight-digit progress codes
(also known as checkpoints) is displayed on the console to indicate that the blade
server is initializing system resources.
Note: You must establish an SOL session with the blade server to view the codes
described in this section; the shared BladeCenter unit video cannot display these
codes.
If the POST is completed without detecting any problems, the firmware displays a
checkpoint indicating that an operating system is being loaded. Location code
information may also display on the operator panel during this time (see “Location
codes” on page 66).
If POST detects a problem, an eight-digit error code will be displayed and logged in
the BladeCenter management module event log. See “Attention codes” on page 34
and “Error codes” on page 37 for more information. A location code might be
displayed at the same time on the second line (see “Location codes” on page 66).
Note: Some POST codes may not display on the operator panel, these codes can
be viewed using the Progress Indicator History option in the SMS utility (see “Using
the SMS utility” on page 166).
© Copyright IBM Corp. 2007 9
Progress codes enable users and service personnel to know what the system is
doing as it initializes. These codes are not intended to be error indicators, but in
some cases a system could hang at one of the progress codes without displaying
an eight-digit error code. Any actions associated with the progress codes should be
taken only if the system hangs.
Progress codes
The following table lists the progress codes that may be displayed by the POST,
and the suggested actions to take if the system hangs on the progress code.
In the following progress codes, X can be any number or letter.
Notes:
1. For checkpoints with no associated location code, see “Light path diagnostics”
on page 124 to identify the failing component.
2. For checkpoints with location codes, see “Location codes” on page 66.
3. For problems persisting after completing the suggested actions, see “Checkout
procedure” on page 106 and “Solving undetermined problems” on page 135.
4. For eight-digit codes not listed here, see “Checkout procedure” on page 106.
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2001000 Partition auto-startup during a platform
startup
C2001010 Startup source
C2001100 Adding partition resources to the
secondary configuration
C20011FF Partition resources added successfully
C2001200 Checking if startup is allowed
C20012FF Partition startup is allowed to proceed
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
10 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2001300 Initializing ISL roadmap
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20013FF ISL roadmap initialized successfully
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2001400 Initializing SP Communication Area #1
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2001410 Initializing startup parameters
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20014FF Startup parameters initialized
successfully
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2002100 Power on racks
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2002110 Issuing a power on command
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C200211F Power on command successful
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20021FF Power on phase complete
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2002200 Begin acquiring slot locks
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 11
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C20022FF End acquiring slot locks
C2002300 Begin acquiring VIO slot locks
C20023FF End acquiring VIO slot locks
C2002400 Begin powering on slots
C2002450 Waiting for power on of slots to complete
C20024FF End powering on slots
C2002500 Begin power on VIO slots
C20025FF End powering on VIO slots
C2003100 Validating ISL command parameters
C2003111 Waiting for bus object to become
operational
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
12 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2003112 Waiting for bus unit to become disabled
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2003115 Waiting for creation of bus object
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2003150 Sending ISL command to bus unit
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20031FF Waiting for ISL command completion
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20032FF ISL command complete successfully
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2003300 Start SoftPOR of a failed ISL slot
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2003350 Waiting for SoftPOR of a failed ISL slot
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20033FF Finish SoftPOR of a failed ISL slot
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2004100 Waiting for load source device to enlist
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2004200 Load source device has enlisted
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 13
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2004300 Preparing connection to load source
device
C20043FF Load source device is connected
C2006000 Locating first LID information on the load
source
C2006005 Clearing all partition main store
C2006010 Locating next LID information on the
load source
C2006020 Verifying LID information
C2006030 Priming LP configuration LID
C2006040 Preparing to initiate LID load from load
source
C2006050 LP configuration LID primed successfully
C2006060 Waiting for LID load to complete
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
14 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2006100 LID load completed successfully
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2006200 Loading raw kernel memory image
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20062FF Loading raw kernel memory image
completed successfully
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2008040 Begin transfer slot locks to partition
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2008060 End transfer slot locks to partition
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2008080 Begin transfer VIO slot locks to partition
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20080A0 End transfer VIO slot locks to partition
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C20080FF Hypervisor low-level session manager
object is ready
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2008100 Initializing service processor
communication area #2
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
C2008104 Loading data structures into main store
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 15
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C2008110 Initializing event paths
C2008120 Starting processor(s)
C2008130 Begin associate of system ports
C2008138 Associating system ports to the partition
C200813F End associate of system ports
C20081FF Processors started successfully, now
waiting to receive the continue
acknowledgement from system firmware
C2008200 Continue acknowledgement received
from system firmware
C20082FF VSP startup complete successfully
C400E200 U4 I2C Master interface Initialization
C400E201 Flash RAM CRC checksum is valid
C400E202 MPIC initialization
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Recovering the system firmware” on
page 127.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
16 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C400E203 Disabling TB
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E204 CRC check of the image in RAM
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E206 Checking KCS interface for good
communication with BMC
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E209 SIO/COM1/GPIO initialization
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E20A Loading 256K flash code into L2 cache
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E20C Finish Platform Hardware Probing.
Process Firmware LID directory
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E20F Executing from L2 cache
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E211 CRC check of the image in flash RAM
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E212 Getting CPU status and presence
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E213 Memory initialization
1. Verify that DIMMs are correctly installed and
seated, then restart server.
2. Start server from PERM image and recover
TEMP image.
3. Replace the system-board and chassis
assembly.
C400E214 Pattern 1 memory test
1. Verify that DIMMs are correctly installed and
seated, then restart server.
2. Start server from PERM image and recover
TEMP image.
3. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 17
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C400E215 Pattern 2 memory test
C400E216 Clear memory
C400E217 Initialize LLFW global data structure
C400E218 Copying the set of flash RAM to memory
C400E219 Saving the DIMM SPDs and the CPU
status and presence
C400E21A Executing code from memory
C400E21B Load PFW into memory
C400E21C Executing HT initialization
C400E21D Executing PCI initialization
C400E21E Execute I/O APIC test
C400E220 Read 4K system VPD eeprom Data
1. Verify that DIMMs are correctly installed and
seated, then restart server.
2. Start server from PERM image and recover
TEMP image.
3. Replace the system-board and chassis
assembly.
1. Verify that DIMMs are correctly installed and
seated, then restart server.
2. Start server from PERM image and recover
TEMP image.
3. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
18 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
C400E22A Temp-side flash image is corrupted
1. Force the blade server to boot from the
PERM image and reject the TEMP image.
2. Replace the system-board and chassis
assembly.
C400E22B Perm-side flash image is corrupted
1. Force the blade server to boot from the
TEMP image and commit the TEMP image.
2. Replace the system-board and chassis
assembly.
C400E230 Read an LID entry from the LID directory
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E231 Check CRC of a PHYPL LID
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E232 Decompress a PHYPL LID image into its
final memory location
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E23E Checking a PHYPL LID size
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E23F Searching for a PHYPL LID
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
C400E298 Transfer control to PHYPL following
MSD start up
1. Shutdown and restart the blade server.
2. Replace the system-board and chassis
assembly.
C400E299 Transfer control to PHYPL following cold
start up
1. Shutdown and restart the blade server from
the permanent-side image.
2. Replace the system-board and chassis
assembly.
C700 xxxx A problem has occurred with the system
firmware during startup.
1. Shutdown and restart the blade server from
the permanent-side image.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
CA000000 Process control now owned by partition
firmware
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 19
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA000020 Checking firmware levels
CA000030 Attempting to establish a communication
link by using lpevents
CA000032 Attempting to register lpevent queues
CA000034 Attempting to exchange cap and allocate
lpevents
CA000038 Attempting to exchange virtual continue
lpevents
CA000040 Attempting to obtain RTAS firmware
details
CA000050 Attempting to load RTAS firmware
CA000060 Attempting to obtain open firmware
details
CA000070 Attempting to load open firmware
CA000080 Preparing to start open firmware
CA000090 Open firmware package corrupted
(phase 1)
CA000091 Attempting to load the second pass of C
code
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
20 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA0000A0 Open firmware package corrupted
(phase 2)
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D001 PCI probe process completed, create
PCI bridge interrupt routing properties
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D002 PCI adapter NVRAM hint created;
system is rebooting
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D003 PCI probing complete
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D004 Beginning of install-console, loading GUI
package
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D008 Initialize console and flush queues
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D00C The partition firmware is about to search
for an NVRAM script
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D00D Evaluating NVRAM script
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00D010 First pass open firmware initialization
complete; establish parameters for
restart
CA00D011 First pass open firmware initialization
complete; control returned to initialization
firmware
CA00D012 Second pass open firmware initialization
complete; control returned to initialization
firmware
CA00D013 Run-time open firmware initialization
complete; control returned to initialization
firmware
CA00E101 Create RTAS node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 21
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E102 Load and initialize RTAS
CA00E105 Transfer control to operating system
(normal mode boot)
CA00E10A Load RTAS device tree
CA00E10B Set RTAS device properties
CA00E110 Create KDUMP properties
CA00E130 Build device tree
CA00E131 Create root node properties
CA00E134 Create memory node
CA00E135 Create HCA node
CA00E136 Create BSR node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Go to “Boot problem resolution” on page 112.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
22 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E137 Create HEA node
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA00E138 Create options node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E139 Create aliases node and system aliases
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E13A Create packages node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E13B Create HEA node
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA00E13C Create HEA port node
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA00E140 Loading operating system Go to “Boot problem resolution” on page 112.
CA00E141 Synchronizing the operating system
bootlist to the management module
bootlist.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
Chapter 2. Diagnostics 23
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E142 The management module bootlist is
being set from the operating system
bootlist.
CA00E143 The operating system bootlist is being
set from the management module
bootlist.
CA00E149 Create boot manager node
CA00E14C Create terminal emulator node
CA00E14D Load boot image Go to “Boot problem resolution” on page 112.
CA00E150 Create host (primary) node
CA00E151 Probing PCI bus
CA00E152 Probing for adapter FCODE; evaluate if
present
CA00E153 End adapter FCODE probing and
evaluation
CA00E154 Create PCI bridge node
CA00E155 Probing PCI bridge secondary bus
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
24 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E156 Create plug-in PCI bridge node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E15B Transfer control to operating system
Go to “Boot problem resolution” on page 112.
(service mode boot)
CA00E15F Adapter VPD evaluation
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E170 Start of PCI bus probe
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E172 First pass of PCI device probe
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E174 Establishing host connection
1. Make sure that:
v The bootp server is correctly configured;
then, retry the operation.
v The network connections are correct;
then, retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with bootp server
or network, replace the system-board and
chassis assembly.
CA00E175 Bootp request
1. Make sure that:
v The bootp server is correctly configured;
then, retry the operation.
v The network connections are correct;
then, retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with bootp server
or network, replace the system-board and
chassis assembly.
CA00E176 TFTP file transfer
1. Make sure that:
v The bootp server is correctly configured;
then, retry the operation.
v The network connections are correct;
then, retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with bootp server
or network, replace the system-board and
chassis assembly.
Chapter 2. Diagnostics 25
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E177 Transfer failure due to TFTP error
condition
CA00E178 Initiating TFTP file transfer
CA00E179 Closing BOOTP
CA00E17B Microprocessor clock speed
measurement
CA00E198 The system is rebooting to enact
changes specified in
ibm,client-architecture-support
1. Make sure that:
v The bootp server is correctly configured;
then, retry the operation.
v The network connections are correct;
then, retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with bootp server
or network, replace the system-board and
chassis assembly.
1. Make sure that:
v The bootp server is correctly configured,
then retry the operation.
v The network connections are correct,
then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with the bootp
server or network, replace the system board
and chassis assembly.
1. Make sure that:
v The bootp server is correctly configured,
then retry the operation.
v The network connections are correct,
then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with the bootp
server or network, replace the system board
and chassis assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Make sure that:
v The bootp server is correctly configured,
then retry the operation.
v The network connections are correct,
then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with the bootp
server or network, replace the system board
and chassis assembly.
26 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E199 The system is rebooting to enact
changes that were specified in the boot
image ELF header
1. Make sure that:
v The bootp server is correctly configured;
then, retry the operation.
v The network connections are correct;
then, retry the operation.
2. Go to “Checkout procedure” on page 106.
3. If no problems are found with bootp server
or network, replace the system-board and
chassis assembly.
CA00E19A NVRAM auto-boot? variable not found -
assume FALSE
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E19B NVRAM menu? variable not found -
assume FALSE
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E19D Create NVRAM node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1A0 User requested boot to SMS menus
using keyboard entry
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1A1 User requested boot to open firmware
prompt using keyboard entry
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1A2 User requested boot using default
service mode boot list using keyboard
entry
CA00E1A3 User requested boot using customized
service mode boot list using keyboard
entry
CA00E1A4 User requested boot to SMS menus
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1A5 User requested boot to open firmware
prompt
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1A6 User requested boot using default
service mode boot list
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 27
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E1A7 User requested boot using customized
service mode boot list
CA00E1AA System boot check for NVRAM settings
CA00E1AB System booting using default service
mode boot list
CA00E1AC System booting using customized
service mode boot list
CA00E1AD System booting to the operating system
CA00E1AE System booted to SMS multiboot menu
using NVRAM settings
CA00E1AF System booted to SMS utilities menu
using NVRAM settings
CA00E1B1 System booting system-directed
boot-device repair
CA00E1B2 XOFF received, waiting for XON
CA00E1B3 XON received
CA00E1B4 System-directed boot-string did not load
an operating system repair
CA00E1B5 Checking for iSCSI disk aliases
CA00E1D0 Create PCI SCSI node
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
28 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E1D3 Create SCSI block device node (SD)
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1D4 Create SCSI byte device node (ST)
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1DC Dynamic console selection
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1DD A graphics adapter has been selected as
the firmware console, but the USB
keyboard is not attached.
1. Make sure that there is a USB keyboard
attached to a USB port that is assigned to
the partition.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
CA00E1F0 Start out-of-box experience
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F1 Start self test sequence on one or more
devices
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F2 Power on password prompt
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F3 Privileged-access password prompt
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F4 End self-test sequence on one or more
boot devices; begin system management
services
CA00E1F5 Build boot device list
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F6 Determine boot device sequence
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E1F7 No boot image located Go to “Boot problem resolution” on page 112.
Chapter 2. Diagnostics 29
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E1F8 Building boot device list for SCSI
adapters. (The location code of the SCSI
adapter being scanned is also
displayed.)
CA00E1F9 Building boot device list for fibre-channel
adapters. (The location code of the SAN
adapter being scanned is also
displayed.)
CA00E1FA Building device list for SCSI adapters
(The device ID and device LUN of the
device being scanned is also displayed.)
CA00E1FB Scan SCSI bus for attached devices
CA00E1FC Building boot device list for SSA
adapters. (The location code of the SSA
adapter being scanned is also
displayed.)
CA00E1FE Building device list for fibre-channel
(SAN) adapters. (The WWPN of the SAN
adapter being scanned is also
displayed.)
CA00E1FF Building device list for fibre-channel
(SAN) adapters. (The LUN of the SAN
adapter being scanned is also
displayed.)
CA00E440 Validate NVRAM, initialize partitions as
needed
CA00E441 Generate /options node NVRAM
configuration variable properties
CA00E442 Validate NVRAM partitions
CA00E443 Generate NVRAM configuration variable
dictionary words
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Check for server firmware updates; then,
install the updates if available and retry the
operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
30 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E444 The NVRAM size is less than 8K bytes
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA00E701 Create memory VPD
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E800 Initialize RTAS
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E810 Initializing ioconfig pfds
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E820 Initializing lpevent
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E830 Initializing event scan
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E840 Initializing hot plug
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E843 Initializing interface/aix access
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E850 Initializing dynamic reconfiguration
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E860 Initializing sensors
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E865 Initializing VPD
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
CA00E870 Initializing pfds memory manager
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 31
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA00E875 Initializing rtas_last_error
CA00E876 Initializing rtas_error_inject
CA00E877 Initializing dump interface
CA00E879 Initialize platform-assisted KDUMP
interface
CA00E885 Initializing set-power-level
CA00E886 Initializing exit2c
CA00E887 Initialize gdata for activate_firmware
CA00E890 Starting to initialize open firmware
CA00E891 Finished initializing open firmware
CA00EAA1 Probe PCI-PCI bridge bus
CA060203 An alias was modified or created
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
32 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v If the system hangs on a progress code, follow the suggested actions in the order in which they are listed
in the Action column until the problem is resolved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Progress code Description Action
CA26FFFF An extended waiting time was required
for lpevent to finish
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA26ttss Waiting for lpevent of type tt and subtype
ss.
1. Restart the blade server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
CA279001 The firmware image contains a firmware
module that is not already on the server.
1. Look for a BA27xxxx error in the error logs
to see if a firmware installation error
occurred. Resolve any problems that are
found and retry the firmware installation.
2. Retry the firmware installation with another
firmware image.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
CA2799FD A firmware update module is being read. Shut down the blade server; then, restart it
using the permanent boot image and reject the
temporary image.
CA2799FF A firmware update module is being
written.
Shut down the blade server; then, restart it
using the permanent boot image and reject the
temporary image.
Chapter 2. Diagnostics 33
Attention codes
The following table describes the partitioning firmware attention codes that may be
displayed if POST detects a problem and suggested actions to correct the problem.
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Attention code Description Action
AA00E1A8 The system is booting to the open
firmware prompt.
AA00E1A9 The system is booting to the System
Management Services (SMS) menus.
AA00E1B0 Waiting for the user to select the
language and keyboard. The menu
should be visible on the console.
AA00E1B1 Waiting for the user to accept or decline
the license agreement. The user must
accept the license agreement.
AA060007 A keyboard was not found. Make sure that a keyboard is attached to the
AA06000B The system or partition was not able to
find an operating system on any of the
devices in the boot list.
AA06000C The media in a device in the boot list
was not bootable.
At the open firmware prompt, type dev
/packages/gui obe and press Enter; then, type
1 to select SMS Menu.
1. If the system or partition returns to the SMS
menus after a boot attempt failed, use the
SMS menus to check the progress indicator
history for a BAxx xxxx error, which may
indicate why the boot attempt failed. Follow
the actions for that error code to resolve the
boot problem.
2. Use the SMS menus to establish the boot
list and restart the blade server.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
USB port that is assigned to the partition.
1. Use the SMS menus to modify the boot list
so that it includes devices that have a
known-good operating system and restart
the blade server.
2. If the problem remains, go to “Boot problem
resolution” on page 112.
1. Replace the media in the device with
known-good media or modify the boot list to
boot from another bootable device.
2. If the problem remains, go to “Boot problem
resolution” on page 112.
34 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Attention code Description Action
AA06000D The media in the device in the bootlist
was not found under the I/O adapter
specified by the bootlist.
1. Make sure that the media from which you
are trying to boot is bootable or modify the
boot list to boot from another bootable
device.
2. If the problem remains, go to “Boot problem
resolution” on page 112.
AA06000E The adapter specified in the boot list is
not present or is not functioning.
v For an AIX operating system:
1. Try booting the blade server from another
bootable device; then, run AIX online
diagnostics against the failing adapter.
2. If AIX cannot be booted from another
device, boot the blade server using the
Standalone Diagnostics CD or a NIM
server; then, run diagnostics against the
failing adapter.
v For a Linux operating system, boot the blade
server using the Standalone Diagnostics CD
or a NIM server; then, run diagnostics
against the failing adapter.
AA060010 The FAT file system on the boot disk is
configured in a way that might cause a
boot failure.
AA060011 The firmware did not find an operating
system image and at least one hard disk
in the boot list was not detected by the
firmware. The firmware is retrying the
entries in the boot list.
AA100001 There was a communication failure
between partition firmware and the
hypervisor. The event that was expected
from the hypervisor was not received.
Increase the FAT partition size by 10% to keep
the number of data clusters fewer than
approximately 4080.
Make sure that:
v The boot disk belongs to the partition from
which you are trying to boot.
v The boot list in the SMS menus is correct.
1. Look at the error logs for errors that
occurred around the time that this attention
code was logged. Resolve those errors,
then reboot the blade server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
AA100002 There was a communication failure
between partition firmware and the
hypervisor.
1. Look at the error logs for errors that
occurred around the time that this attention
code was logged. Resolve those errors,
then reboot the blade server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
AA130013 Bootable media is missing from a USB
CD-ROM
Make sure that a bootable CD is properly
inserted in the CD or DVD drive and retry the
boot operation.
Chapter 2. Diagnostics 35
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Attention code Description Action
AA130014 The media in a USB CD-ROM has been
changed.
AA170210 Setenv/$setenv parameter error - the
name contains a null character.
AA170211 Setenv/$setenv parameter error - the
value contains a null character.
AA190001 The hypervisor function to get/set the
time-of-day clock reported an error.
AA260001 The system is waiting for the machine
type, model, and serial number to be
entered.
BA00E820 lpevent communication failure
BA00E830 ibm,event-scan init failure
1. Retry the operation.
2. Check for server firmware updates; then,
install the updates if available and retry the
operation.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Use the operating system to set the system
clock.
2. Check for server firmware updates; then,
install the updates if available.
Enter the machine type, model, and serial
number of the blade server at the prompt.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
36 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Error codes
The following table describes the error codes that may be displayed if POST
detects a problem and suggested actions to correct the problem.
Note: For problems persisting after completing the suggested actions, see
“Checkout procedure” on page 106 and “Solving undetermined problems” on page
135.
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
A200yyyy See the description for B200yyyy error
code with same yyyy value.
A7003000 A user-initiated platform dump occurred. No service action required.
A700yyyy See the description for B700yyyy error
code with same yyyy value.
B2001150 During the startup of a partition, a
partitioning configuration problem
occurred.
B2001230 During the startup of a partition, a
partitioning configuration problem
occurred; the partition is lacking the
necessary resources to start up.
B2001266 The partition could not start up; you are
attempting to start up an operating
system that is not supported.
B2002250 During the startup of a partition, an
attempt to toggle the power state of a
slot has failed.
B2002300 During the startup of a partition, an
attempt to toggle the power state of a
slot has failed.
B2002310 During the startup of a partition, the
partition firmware attempted an operation
that failed.
B2002320 During the startup of a partition, the
partition firmware attempted an operation
that failed.
B2002425 During the startup of a partition, the
partition firmware attempted an operation
that failed.
B2002426 During the startup of a partition, the
partition firmware attempted an operation
that failed.
B2002475 During the startup of a partition, a slot
that was needed for the partition was
either empty or the device in the slot has
failed.
Perform the action described in B200yyyy error
code with same yyyy value.
Perform the action in B700yyyy error code with
same yyyy value.
Go to “Verifying the partition configuration” on
page 108.
Go to “Verifying the partition configuration” on
page 108.
Install a supported operating system and restart
the partition.
Check for server firmware updates; then, install
the updates if available.
Check for server firmware updates; then, install
the updates if available.
Go to “Firmware problem isolation” on page
127.
Go to “Firmware problem isolation” on page
127.
Go to “Firmware problem isolation” on page
127.
Go to “Firmware problem isolation” on page
127.
Check for server firmware updates; then, install
the updates if available.
Chapter 2. Diagnostics 37
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B2002485 During the startup of a partition, the
partition firmware attempted an operation
that failed.
B2003081 During the startup of a partition, the
startup did not complete due to a copy
error.
B2003125 During the startup of a partition, the
blade server firmware could not obtain a
segment of main storage within the
blade server to use for managing the
creation of a partition.
B2006006 During the startup of a partition, a
system firmware error occurred when the
partition memory was being initialized;
the startup will not continue.
B2006012 During the startup of a partition, the
partition LID failed to completely load
into the partition main storage area.
B2006027 During the startup of a partition, a failure
occurred when allocating memory for an
internal object used for firmware module
load operations.
B200690A During the startup of a partition, an error
occurred while copying open firmware
into the partition load area.
B2008080 System log entry only. No service action required.
B2008081 During the startup of a partition, an
internal firmware time-out occurred; the
partition may continue to start up but it
may experience problems while running.
B2008105 During the startup of a partition, there
was a failure loading the VPD areas of
the partition; the load source media has
been corrupted or is unsupported on this
server.
B2008107 During the startup of a partition, there
was a problem getting a segment of
main storage in the blade server main
storage.
B2008109 During the startup of a partition, a failure
occurred; the startup will not continue.
B2008112 During the startup of a partition, a failure
occurred; the startup will not continue.
Go to “Firmware problem isolation” on page
127.
Check for server firmware updates; then, install
the updates if available.
Check for server firmware updates; then, install
the updates if available.
Go to “Firmware problem isolation” on page
127.
Go to “Firmware problem isolation” on page
127.
1. Make sure that enough main storage was
allocated to the partition.
2. Retry the operation.
Go to “Firmware problem isolation” on page
127.
Check for server firmware updates; then, install
the updates if available.
Check for server firmware updates; then, install
the updates if available.
Check for server firmware updates; then, install
the updates if available.
1. Make sure that there is enough memory to
start up the partition.
2. Check for server firmware updates; then,
install the updates if available.
Check for server firmware updates; then, install
the updates if available.
38 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B2008113 During the startup of a partition, an error
occurred while mapping memory for the
Check for server firmware updates; then, install
the updates if available.
partition startup.
B2008114 During the startup of a partition, there
was a failure verifying the VPD for the
Check for server firmware updates; then, install
the updates if available.
partition resources during startup.
B2008115 During the startup of a partition, there
was a low level partition-to-partition
Check for server firmware updates; then, install
the updates if available.
communication failure.
B2008117 During the startup of a partition, the
partition did not start up due to a system
Check for server firmware updates; then, install
the updates if available.
firmware error.
B2008121 During the startup of a partition, the
partition did not start up due to a system
Go to “Firmware problem isolation” on page
127.
firmware error.
B2008123 During the startup of a partition, the
partition did not start up due to a system
Go to “Firmware problem isolation” on page
127.
firmware error.
B2008125 During the startup of a partition, the
partition did not start up due to a system
Go to “Firmware problem isolation” on page
127.
firmware error.
B2008127 During the startup of a partition, the
partition did not start up due to a system
Go to “Firmware problem isolation” on page
127.
firmware error.
B2008129 During the startup of a partition, the
partition did not start up due to a system
Go to “Firmware problem isolation” on page
127.
firmware error.
B200A100
B200A101
A partition ended abnormally; the
partition could not stay running and shut
itself down.
1. Check the error logs and take the actions
for the error codes that are found.
2. Go to “Firmware problem isolation” on page
127.
B200B07B System log entry only. No service action required.
B200C1F0 An internal system firmware error
occurred during a partition shutdown or a
Go to “Firmware problem isolation” on page
127.
restart.
B200D150 A partition ended abnormally; there was
a communications problem between this
Check for server firmware updates; then, install
the updates if available.
partition and the code that handles
resource allocation.
B200F003 During the startup of a partition, the
partition processor(s) did not start the
Collect the partition dump information; then, go
to “Firmware problem isolation” on page 127.
firmware within the time-out window.
B200F004
B200F005
A partition had a communications
problem during a shutdown of the
Collect the partition dump information; then, go
to “Firmware problem isolation” on page 127.
partition.
Chapter 2. Diagnostics 39
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B200F006 During the startup of a partition, the code
load operation for the partition startup
timed out.
B200F007 During a shutdown of the partition, a
time-out occurred while trying to stop a
partition
B400BAD0
00000000
B400BAD0
0000XXYY
No DIMMs detected
DIMM failure where:
v XX is:
01=DIMM4 missing; 02=DIMM2
unsupported and DIMM4 missing;
04=DIMM2 failed and DIMM4 missing;
10=DIMM2 missing; 12=DIMM2
unsupported; 14=DIMM2 failed;
20=DIMM2 missing and DIMM4
unsupported; 21=DIMM4 unsupported;
22=DIMM2 and DIMM4 unsupported;
24=DIMM2 failed and DIMM4
unsupported; 40=DIMM2 missing and
DIMM4 failed; 41=DIMM4 failed;
42=DIMM2 unsupported and DIMM4
failed; 44=DIMM2 and DIMM4 failed;
88=DIMM2 and DIMM4 mismatch
v YY is:
01=DIMM3 missing; 02=DIMM1
unsupported and DIMM3 missing;
04=DIMM1 failed and DIMM3 missing;
10=DIMM1 missing; 12=DIMM1
unsupported; 14=DIMM1 failed;
20=DIMM1 missing and DIMM3
unsupported; 21=DIMM3 unsupported;
22=DIMM1 and DIMM3 unsupported;
24=DIMM1 failed and DIMM3
unsupported; 40=DIMM1 missing and
DIMM3 failed; 41=DIMM3 failed;
42=DIMM1 unsupported and DIMM3
failed; 44=DIMM1 and DIMM3 failed;
88=DIMM1 and DIMM3 mismatch)
1. Check the error logs and take the actions
for the error codes that are found.
2. Go to “Firmware problem isolation” on page
127.
Check for server firmware updates; then, install
the updates if available.
1. Reseat the DIMMs and restart the blade
server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Reseat the DIMMs and restart the blade
server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
40 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B400BAD1
83A00702 (x)
TEMP side firmware image corruption
was detected (blade server will
automatically restart using the PERM
side image after 4 minutes).
1. Go to “Recovering the system firmware” on
page 127.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
B400BAD1
XXXXXXXX (>)
PHYPL LID XXXXXXXX exceeds its
maximum size.
where XXXXXXXX is: 83A00702,
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
80A00701, or 80A00711
B400BAD1
XXXXXXXX (-)
B400BAD1
XXXXXXXX (x)
PHYPL LID XXXXXXXX is not found.
where XXXXXXXX is: 83A00702,
80A00701, or 80A00711
PHYPL LID XXXXXXXX CRC
mismatches.
where XXXXXXXX is: 80A00701 or
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
80A00711
B400BADC
2B200X31
B400BADD
25C10002
Processor x is faulty Replace the system-board and chassis
assembly.
Memory DIMM is not supported
1. Make sure that:
v All DIMMs are supported; replace all
unsupported DIMMs and restart the blade
server
v All DIMMs are installed in pairs; install
DIMMs properly and restart the blade
server.
2. Replace the following components one at a
time, in the order shown, restarting the
blade server each time:
a. Each DIMM, until the failing DIMM is
isolated
b. System-board and chassis assembly.
B400BADD
25C10001
Memory DIMM error
1. Reseat the DIMMs and restart the blade
server.
2. Replace the following components one at a
time, in the order shown, restarting the
blade server each time:
a. DIMM specified by the location code
b. Companion DIMM of the DIMM
specified by the location code
c. System-board and chassis assembly.
Chapter 2. Diagnostics 41
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B400BADD
25C10003
B400BADD
25C10004
B7000102 System firmware detected an error. A
B7000103 System firmware detected a failure Collect the error log and platform dump
B7000104 System firmware failure. Machine check,
B7000105 System firmware detected an error. More
B7000106 System firmware failure. Collect the error log and platform dump
B7000107 System firmware failure. The system
B70001F5 A processor failure has occurred. Replace the blade server.
B70001F6 A memory failure has occurred Replace the DIMM specified by the location
B7000302 System firmware failure Collect the platform dump information; then, go
B7000441 Service processor failure. The platform
B7000443 Service processor failure. Replace the blade server.
Companion (in the pair) of the memory
DIMM specified by the location code is
unmatched
Companion (in the pair) of the memory
DIMM specified by the location code is
missing, failing, or unsupported
machine check occurred during startup.
undefined error occurred.
than one request to terminate the system
was issued.
detected an unrecoverable machine
check condition.
encountered an error early in the startup
or termination process.
1. Reseat all DIMMs and restart the blade
server.
2. Replace the following components one at a
time, in the order shown, restarting the
blade server each time:
a. DIMM specified by the location code
b. Companion DIMM of the DIMM
specified by the location code
c. System-board and chassis assembly.
1. Reseat all DIMMs and restart the blade
server.
2. Replace the following components one at a
time, in the order shown, restarting the
blade server each time:
a. DIMM specified by the location code
b. Companion DIMM of the DIMM
specified by the location code
c. System-board and chassis assembly.
Collect the error log information; then, go to
“Firmware problem isolation” on page 127.
information; then, go to “Firmware problem
isolation” on page 127.
Check for server firmware updates; then, install
the updates if available.
Go to “Firmware problem isolation” on page
127.
information; then, go to “Firmware problem
isolation” on page 127.
Collect the error log and platform dump
information; then, go to “Firmware problem
isolation” on page 127.
code that is reported with the error code.
to “Firmware problem isolation” on page 127.
Replace the blade server.
42 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B7000601 Informational system log entry. No corrective action is required.
Note: This code and associated data can be
used to determine why the time of day for a
partition was lost.
B7000602 System firmware detected an error
condition.
B7000611 There is a problem with the system
hardware clock; the clock time is invalid.
Collect the error log information; then, go to
“Firmware problem isolation” on page 127.
Use the operating system to set the system
clock.
B7000621 Informational system log entry only. No corrective action is required.
B7000631 The hardware real-time clock has
Replace the system battery.
detected that the battery is low.
B7000650 System firmware detected an error.
Resource management was unable to
allocate main storage. A platform dump
Collect the error log, platform dump, and
partition configuration information; then, go to
“Firmware problem isolation” on page 127.
was initiated.
B7004400 There is a platform dump to collect Use the method provided by your operating
system to collect the platform dump information;
then, go to “Firmware problem isolation” on
page 127.
B7004401 System firmware failure. The system
firmware detected an internal problem.
B7004407 Informational only: system firmware has
Go to “Firmware problem isolation” on page
127.
No corrective action is required.
deleted a platform dump.
B7004408 A platform dump has occurred. (The
system issues this error code during the
Collect the platform dump information; then, go
to “Firmware problem isolation” on page 127.
first startup after a dump is requested.)
B7004409 A platform dump has occurred. A
previous attempt to startup failed; the
Collect the platform dump information; then, go
to “Firmware problem isolation” on page 127.
dump from the previous B7004408 error
code has been lost.
B7005190 Operating system error. The server
firmware detected a problem in an
operating system.
B7005191 System firmware detected a virtual I/O
configuration error.
Check for error codes in the partition that is
reporting the error and take the appropriate
actions for those error codes.
1. Use the partition manager to verify or
reconfigure the invalid virtual I/O
configuration.
2. Check for server firmware updates; then,
install the updates if available.
B7005300 System firmware detected a failure while
partitioning resources. The platform
partitioning code encountered an error.
Check the management module event log and
the SMS progress indicator history for error
codes; then, take the actions associated with
those error codes.
B7005301 User intervention required. The system
detected a problem with the partition
Use the partition manager to reallocate the
system resources.
configuration.
Chapter 2. Diagnostics 43
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
B7005401 The system encountered a correctable
memory failure.
B7005402 through
B7005406
B7005601 System firmware failure. There was a
B7005700 The system firmware has experienced a
B7006951 An error occurred because a partition
B700BAD1 The platform firmware detected an error. Go to “Firmware problem isolation” on page
B700F103 System firmware failure Collect the error log and platform dump
B700F104 Operating system error. System firmware
B700F105 System firmware detected an internal
BA000010 The device data structure is corrupted
BA000020 The firmware levels are incompatible.
BA000031 lpevent communication failure
A correctable processor failure occurred. Replace the blade server.
problem initializing, reading, or using
system location codes.
low storage condition.
needed more NVRAM than was
available.
terminated a partition.
error
Replace the DIMM specified by the location
code that is reported with the error code.
Go to “Firmware problem isolation” on page
127.
At your earliest convenience, use the method
provided by your operating system to force a
platform dump; then, go to “Firmware problem
isolation” on page 127.
Use the partition manager to delete one or
more partitions.
127.
information; then, go to “Firmware problem
isolation” on page 127.
Check the management module event log and
the SMS progress indicator history for partition
firmware error codes (especially BA00F104);
then, take the appropriate actions for those
error codes.
Collect the error log and platform dump
information; then, go to “Firmware problem
isolation” on page 127.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
44 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA000030 An lpevent communication failure
occurred
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000032 The firmware failed to register the
lpevent queues
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000034 The firmware failed to exchange capacity
and allocate lpevents
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000038 The firmware failed to exchange virtual
continuation lpevents
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000040 The firmware was unable to obtain the
RTAS code lid details
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000050 The firmware was unable to load the
RTAS code lid
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000060 The firmware was unable to obtain the
open firmware code lid details
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000070 The firmware was unable to load the
open firmware code lid
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA000080 The user did not accept the firmware
license agreement.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
BA000081 Failed to get the firmware license policy.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
Chapter 2. Diagnostics 45
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA000082 Failed to set the firmware license policy.
BA000091 Unable to load the second-pass C code
BA00E840 PCI hot-plug init failure
BA00E843 Initialization of the rtas-call interface
failed.
BA00E850 There was a failure when initializing
dynamic reconfiguration.
BA00E860 There was a failure when initializing the
sensors.
BA010000 There is insufficient information to boot
the systems
BA010001 The client IP address is already in use
by another network device
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Make sure that all of the IP addresses on the
network are unique; then, retry the operation.
46 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA010002 Cannot get gateway IP address Perform the actions for progress code
CA00E174 (see “Progress codes” on page 10).
BA010003 Cannot get server hardware address Perform the actions for progress code
CA00E174 (see “Progress codes” on page 10
BA010004 Bootp failed Perform the actions for progress code
CA00E174 (see “Progress codes” on page 10
BA010005 File transmission (TFTP) failed Perform the actions for progress code
CA00E174 (see “Progress codes” on page 10
BA010006 The boot image is too large Start up from another device with a bootable
image.
BA010010 There was a partition firmware error
while in the SMS menus
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA010011 SET-ROOT-PROP could not find / (root)
package
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA012010 Opening the TCP node failed.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA012011 TCP failed to read from the network.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA012012 TCP failed to write to the network.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA012013 Closing TCP failed.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA017020 Failed to open the TFTP package Verify that the TFTP parameters are correct.
Chapter 2. Diagnostics 47
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA017021 Failed to load the TFTP file Verify that the TFTP server and network
connections are correct.
BA01B010 Opening the BOOTP node failed.
BA01B011 BOOTP failed to read from the network Refer to the actions for checkpoint CA00E174.
BA01B012 BOOTP failed to write to the network Refer to the actions for checkpoint CA00E174.
BA01B013 The discover mode is invalid
BA01B014 Closing the BOOTP node failed
BA01B015 The BOOTP discover server timed out. Refer to the actions for checkpoint CA00E174.
BA01D001 Opening the DHCP node failed
BA01D020 DHCP failed to read from the network
BA01D030 DHCP failed to write to the network
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Verify that the network cable is connected,
and that the network is active.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Verify that the network cable is connected,
and that the network is active.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
48 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA01D040 The DHCP discover server timed out
1. Insure that the DHCP server has addresses
available.
2. Insure that the DHCP server's configuration
file is not overly constrained such that it
was not able to meet the configuration
requested by the client.
3. Refer to the actions for checkpoint
CA00E174.
BA01D050 DHCP::discover no good offer DHCP discover did not receive any DHCP
offers from the server(s) the meet the clients's
requirements. Insure that the DHCP server's
configuration file is not overly constrained such
that it was not able to meet the configuration
requested by the client.
BA01D051 DHCP::discover DHCP request timed out
1. DHCP discover did receive a DHCP offer
from the server(s) the meet the clients's
requirements, but the server did not send
DHCP ack (the acknowledgement) to the
client's DHCP request. It is possible that
another client was using the address that
was served.
2. Insure that the DHCP server has addresses
available.
BA01D052 DHCP::discover: 10 incabable servers
were found
Ten DHCP servers have sent DHCP offers,
none of which met the requirements on the
client. Check the configuration that the client is
requesting, and the server's DHCP
configuration files, for compatibility.
BA01D053 DHCP::discover received a reply, but
without a message type
BA01D054 DHCP::discover: DHCP nak received
Insure that the DHCP server is properly
configured.
1. DHCP discover did receive a DHCP offer
from the server(s) the meet the clients's
requirements, but the server did sent DHCP
nak (not acknowledged) to the client's
DHCP request. (It is possible that another
client was using the address that was
served.) This usually occurs when there are
multiple DHCP servers on the same
network, and server A does not know the
subnet configuration of server B, and
vice-versa. This can also occur when the
pool of addresses is not truly divided.
The DHCP server's configuration file should
also be set to "authoritative".
2. Insure that the DHCP server is functioning
properly.
Chapter 2. Diagnostics 49
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA01D055 DHCP::discover: DHCP decline
BA01D056 DHCP::discover: unknown DHCP
message
BA01D0FF Closing the DHCP node failed.
BA04000F Self test failed on device; no error or
location code information available
BA040010 Self test failed on device; can't locate
package
BA040020 The machine type and model are not
recognized by the blade server firwmare
BA040030 The firmware was not able to build the
UID properly for this system. As a result,
problems may occur with the licensing of
the AIX operating system
BA040035 The firmware was unable to find the
“plant of manufacture” in the VPD. This
may cause problems with the licensing
of the AIX operating system.
1. DHCP discover did receive a DHCP offer
from the server(s) the meet the clients's
requirements, but the client performed an
ARP test on the address and found that
another client was using the address.
DHCP decline was sent to the server, but
no additional DHCP offers were received by
the client. The client still does not have a
valid address.
2. Insure that the DHCP server is functioning
properly.
DHCP discover received an unknown DHCP
message type. Insure that the DHCP server is
functioning properly.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. If a location code is displayed with the error,
replace the device specified by the location
code.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. If a location code is displayed with the error,
replace the device specified by the location
code.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Check for server firmware updates; then,
install the updates if available.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Make sure that the machine type, model, and
serial number are correct for this server. If this
is a new server, check for server firmware
updates; then, install the updates if available.
50 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA040040 Setting the machine type, model, and
serial number failed.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA040050 The h-call to switch off the boot
watchdog timer failed.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA040060 Setting the firmware boot side for the
next boot failed.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA050001 Failed to reboot a partition in logical
partition mode
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA050004 Failed to locate service processor device
tree node.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA05000A Failed to send boot failed message
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA060003 IP parameter requires 3 period
characters “.”
Enter a valid IP parameter using the format:
XXX.XXX.XXX.XXX, where X is any digit 0 -
255.
BA060004 Invalid IP parameter Enter a valid IP parameter using the format:
XXX.XXX.XXX.XXX, where X is any digit 0 -
255.
BA060005 Invalid IP parameter (>255) Enter a valid IP parameter using the format:
XXX.XXX.XXX.XXX, where X is any digit 0 -
255.
BA060008 No configurable adapters found by the
Remote IPL menu in the SMS utilities
This error occurs when the firmware cannot
locate any LAN adapters that are supported by
the remote IPL function. Make sure that the
devices in the remote IPL device list are correct
using the SMS menus.
BA06000B The system was not able to find an
Go to “Boot problem resolution” on page 112.
operating system on the devices in the
boot list.
BA06000C A pointer to the operating system was
found in non-volatile storage.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA060020 The environment variable “boot-device”
exceeded the allowed character limit.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 51
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA060021 The environment variable “boot-device”
contained more than five entries.
BA060022 The environment variable “boot-device”
contained an entry that exceeded 255
characters in length
BA060030 Logical partitioning with shared
processors is enabled and the operating
system does not support it.
BA060040 The partition is configured with large
pages but the operating system does not
support large pages.
BA060060 The operating system expects an IOSP
partition, but it failed to make the
transition to alpha mode.
BA060061 The operating system expects a
non-IOSP partition, but it failed to make
the transition to MGC mode.
BA060070 The operating system does not support
the server's processors.
BA060071 An invalid number of vectors was
received from the operating system
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Using the SMS menus, set the boot list to
the default boot list. Shut down; then, start
up the blade server. Use SMS menus to
customize the boot list as required.
2. If the problem remains, go to “Checkout
procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Install or boot a level of the operating
system that supports shared processors.
2. Disable logical partitioning with shared
processors in the operating system.
3. Go to “Checkout procedure” on page 106.
4. Replace the system-board and chassis
assembly.
Boot a version of the operating system that
supports large pages.
1. Make sure that
v The alpha-mode operating system image
is intended for this partition.
v The configuration of the partition supports
an alpha-mode operating system.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Make sure that
v The non-alpha-mode operating system
image is intended for this partition.
v The configuration of the partition supports
a non-alpha-mode operating system.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
Boot a version of the operating system that
supports the server's processors.
Boot a newer version of the operating system
52 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA060072 client-arch-support software error
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA060075 client-arch-support firmware error
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA060200 Failed to set the operating system's boot
list from the management module boot
list.
1. Verify that the boot list is set up in the MM.
2. Check for server firmware and MM firmware
updates; apply if available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
BA060201 Failed to read the "boot path" value in
the VPD
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA060202 Failed to read the "boot path" value in
the VPD with the new value.
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA07xxxx SCSI controller failure
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA090001 SCSI DASD: test unit ready failed;
hardware error
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA090002 SCSI DASD: test unit ready failed; sense
data available
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA090003 SCSI DASD: send diagnostic failed;
sense data available
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 53
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA090004 SCSI DASD: send diagnostic failed:
devofl cmd
BA09000A There was a vendor specification error.
BA09000B Generic SCSI sense error
BA09000C The media is write-protected
BA09000D The media is unsupported or not
recognized.
BA09000E The media is not formatted correctly.
BA09000F Media is not present
BA090010 The request sense command failed.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Check the vendor specification for additional
information.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Change the setting of the media to allow
writing, then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Insert new media of the correct type, then
retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Insert new media with the correct format,
then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Insert new media, then retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
54 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA090011 The retry limit has been exceeded.
1. Verify that the SCSI cables and devices are
properly
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA090012 There is a SCSI device that is not
supported.
1. Replace the SCSI device that is not
supported with supported device.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA120001 On an undetermined SCSI device, test
unit ready failed; hardware error
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA120002 On an undetermined SCSI device, test
unit ready failed; sense data available
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA120003 On an undetermined SCSI device, send
diagnostic failed; sense data available
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA120004 On an undetermined SCSI device, send
diagnostic failed; devofl command
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA120010 Failed to generate the SAS device's
physical location code. The error log
entry has the details.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA130001 SCSI CD-ROM test unit ready failed;
hardware error.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA130002 SCSI CD-ROM test unit ready failed;
sense data available.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
Chapter 2. Diagnostics 55
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA130003 SCSI CD-ROM send diagnostic failed;
sense data available.
BA130004 SCSI CD-ROM send diagnostic failed:
devofl command.
BA130010 USB CD-ROM in the media tray: device
remained busy longer than the time-out
period
BA130011 USB CD-ROM in the media tray:
execution of ATA/ATAPI command was
not completed with the allowed time.
BA130012 USB CD-ROM in the media tray:
execution of ATA/ATAPI command failed.
BA130013 USB CD-ROM in the media tray:
bootable media is missing from the drive
BA130014 USB CD-ROM in the media tray: the
media in the USB CD-ROM drive has
been changed.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Remove the CD or DVD in the drive and
replace it with a known-good disk.
2. Go to “Checkout procedure” on page 106.
3. Replace the USB CD or DVD drive.
4. Replace the system-board and chassis
assembly.
1. Insert a bootable CD in the drive and retry
the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the USB CD or DVD drive.
4. Replace the system-board and chassis
assembly.
1. Retry the operation.
2. Go to “Checkout procedure” on page 106.
3. Replace the USB CD or DVD drive.
4. Replace the system-board and chassis
assembly.
56 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA130015 USB CD-ROM in the media tray:
ATA/ATAPI packet command execution
failed.
1. Retry the operation.
2. Remove the CD or DVD in the drive and
replace it with a known-good disk.
3. Go to “Checkout procedure” on page 106.
4. Replace the USB CD or DVD drive.
5. Replace the system-board and chassis
assembly.
BA131010 The USB keyboard has been removed.
1. Reseat the keyboard cable in the
management module USB port.
2. Check for server firmware updates; then,
install the updates if available.
BA140001 The SCSI read/write optical test unit
ready failed; hardware error.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA140002 The SCSI read/write optical test unit
ready failed; sense data available.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA140003 The SCSI read/write optical send
diagnostic failed; sense data available.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA140004 The SCSI read/write optical send
diagnostic failed; devofl command.
1. Verify that the SCSI cables and devices are
properly plugged; correct any problems that
are found.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA150001 PCI Ethernet BNC/RJ-45 or PCI Ethernet
AUI/RJ-45 adapter: internal wrap test
Replace the adapter specified by the location
code.
failure
Chapter 2. Diagnostics 57
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA150070 The receive operation failed.
BA151001 10/100 Mbps Ethernet PCI adapter:
internal wrap test failure
BA151002 10/100 Mbps Ethernet card failure
BA153002 Gigabit Ethernet adapter failure Make sure that the MAC address programmed
BA153003 Gigabit Ethernet adapter failure
BA154010 HEA software error
BA154020 The required open firmware property
was not found.
BA154030 Invalid parameters were passed to the
HEA device driver.
BA154040 The TFTP package open failed
BA154050 The transmit operation failed.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
Replace the adapter specified by the location
code.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
in the FLASH/EEPROM is correct.
1. Check for server firmware updates; then,
install the updates if available.
2. Replace the Gigabit Ethernet adapter.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
58 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA154060 Failed to initialize the HEA port or queue
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA170000 NVRAMRC initialization failed; device
test failed
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA170100 NVRAM data validation check failed
1. Shut down the blade server; then, restart it.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
BA170201 The firmware was unable to expand
target partition - saving configuration
variable
BA170202 The firmware was unable to expand
target partition - writing error log entry
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA170203 The firmware was unable to expand
target partition - writing VPD data
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA170210 Setenv/$Setenv parameter error - name
contains a null character
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA170211 Setenv/$Setenv parameter error - value
contains a null character
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA170220 Unable to write a variable value to
NVRAM due to lack of free memory in
NVRAM.
BA170221 Setenv/$setenv had to delete stored
firmware network boot settings to free
memory in NVRAM.
BA170998 NVRAMRC script evaluation error -
command line execution error.
1. Reduce the number of partitions, if possible,
to add more memory in NVRAM to this
partition.
2. Go to the checkout procedure on page xx.
3. Replace the system board and chassis
assembly.
The user may need to reenter adapter and
network parameters for network boot or
installation.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
Chapter 2. Diagnostics 59
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA180014 MSI software error.
BA180020 No response was received from a slot
during PCI probing.
BA180099 PCI probe error; bridge in freeze state,
slot in reset state
BA180100 The FDDI adapter Fcode driver is not
supported on this server. IBM may
produce a compatible driver in the future,
but does not guarantee one.
BA188000 There is an unsupported adapter in the
PCI slot
BA188001 EEH recoved a failing I/O adapter Replace the adapter.
BA188002 EEH was not able to recover the failing
I/O apdater.
BA180008 PCI device Fcode evaluation error
BA180009 The Fcode on a PCI adapter left a data
stack imbalance
BA180010 PCI probe error, bridge in freeze state
BA180011 PCI bridge probe error, bridge is not
usable
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for adapter firmware updates; apply
if available.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
Remove the adapter.
Replace the adapter.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Check for adapter firmware updates; then,
install the updates if available.
2. Check for server firmware updates; then,
install the updates if available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
60 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA180012 PCI device runtime error, bridge in
freeze state
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA180101 Stack underflow from fibre-channel
adapter
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA190001 Firmware function to get/set time-of-day
reported an error
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA201001 The serial interface dropped data
packets
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA201002 The serial interface failed to open
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA201003 The firmware failed to handshake
properly with the serial interface
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA210000 Partition firmware reports a default catch
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA210001 Partition firmware reports a stack
underflow was caught
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA210002 Partition firmware was ready before
standout was ready
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA210003 A data storage error was caught by
partition firmware
1. If the location code reported with the error
points to an adapter, check for adapter
firmware updates; apply if available.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
BA210013 There was a partition firmware error
while in the SMS menus
1. Look for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
Chapter 2. Diagnostics 61
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA210020 I/O configuration exceeded the maximum
size allowed by partition firmware.
BA210100 An error may not have been sent to the
management module event log.
BA210101 The partition firmware error log queue is
full
.BA220010 There was a partition firmware error
during USB hotpug probing. USB hotplug
may not work correctly on this partition.
BA220010 There was a partition firmware error
during USB hotpug probing. USB hotplug
may not work correctly on this partition.
BA220020 There was a CRQ registration error; the
partner vslot is not valid.
BA278001 Failed to flash firmware: invalid image
file
BA278002 Flash file is not designed for this
platform
BA278003 Unable to lock the firmware update lid
manager
BA278004 An invalid firmware update lid was
requested
1. Increase the logical memory block size to
256 MB and restart the blade server.
2. Go to “Checkout procedure” on page 106.
3. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
1. Check the error logs for EEH-related
entries; resolve any entries that are found,
then reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Check the error logs for EEH-related
entries; resolve any entries that are found,
then reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
Verify that this client virtual slot device has a
valid server virtual slot device in a hosting
partition.
Download a new firmware update image and
retry the update.
Download a new firmware update image and
retry the update.
1. Restart the blade server.
2. Make sure that the operating system is
authorized to update the firmware. If the
system is running multiple partitions, make
sure that this partition has service authority.
Download a new firmware update image and
retry the update.
62 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA278005 Failed to flash a firmware update lid Download a new firmware update image and
retry the update.
BA278006 Unable to unlock the firmware update lid
Restart the blade server.
manager
BA278007 Failed to reboot the system after a
Restart the blade server.
firmware flash update
BA278009 The operating system tools to update the
blade server firmware are incompatible
with this system.
Go to the IBM microcode download web site
(http://techsupport.services.ibm.com/server/
lopdiags) and download the latest version of the
service aids package for Linux.
BA27800A A server firmware update failed due to a
hardware error.
1. Check the error logs for hardware-related
entries; resolve any entries that are found,
then reboot the blade server and retry the
server firmware update.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
4.
BA280000 RTAS discovered an invalid operation
that may cause a hardware error
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA290000 RTAS discovered an internal stack
overflow
1. Go to “Checkout procedure” on page 106.
2. Replace the system-board and chassis
assembly.
BA290001 RTAS low memory corruption was
detected
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
BA290002 RTAS low memory corruption was
detected
1. Reboot the blade server.
2. Look for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
BA310010 Unable to obtain the SRC history
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
Chapter 2. Diagnostics 63
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA310020 An invalid SRC history was obtained.
BA310030 Writing the MAC address to the VPD
failed.
BA330000 Memory allocation error.
BA330001 Memory allocation error.
BA330002 Memory allocation error.
BA330003 Memory allocation error.
BA330004 Memory allocation error.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
1. Reboot the blade server.
2. Check for server firmware updates; apply if
available.
3. Go to “Checkout procedure” on page 106.
4. Replace the system board and chassis
assembly.
64 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 3, “Parts listing, Types 7988 and 8844,” on page 137 to determine which components are
CRUs and which components are FRUs.
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error code Description Action
BA400001 Informational message: DMA trace buffer
full.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
BA400002 Informational message: DMA map-out
size mismatch.
1. Check for server firmware updates; apply if
available.
2. Go to “Checkout procedure” on page 106.
3. Replace the system board and chassis
assembly.
4.
Chapter 2. Diagnostics 65
Location codes
Location codes are displayed with some error codes to identify the component that
caused the error.
Note: Location codes do not indicate the location of the blade server within the
BladeCenter unit, they only identify components of the blade server.
Location code Component
Um-E1 Battery
Um-P1-C1 DIMM 1
Um-P1-C2 DIMM 2
Um-P1-C3 DIMM 3
Um-P1-C4 DIMM 4
Um-P1-C5 I/O expansion adapter
Um-P1
Um-P1-T1
Um-P1-T2
Um-P1-T3
Um-P1-T4
Um-P1-T5
Um-P1-T6
Um-P1-T7
Um-P1-T8
Um-P1-T9
Um-P1-T10
Um-P1-T11
Um-P1-T12
Um-P1-T10-L0-L0 SAS hard disk drive 1
Um-P1-T11-L0-L0 SAS hard disk drive 2
Un-Y1 Firmware version
Um = Uffff.001.sssssss (where: ffff =
Enclosure feature code, sssssss = serial
number)
Un = Utttt.mmm.sssssss (where: tttt =
machine type, mmm = model number,
sssssss = serial number)
System-board and chassis assembly
Um is for enclosure locations
Un is for system VPD and Firmware
Error logs
Any errors that are detected by the POST are sent to the BladeCenter management
module event log (see the BladeCenter Management Module User’s Guide for
information about the event log). Depending on your operating system and the
utilities you have installed, error messages might also be stored in an operating
system log (see the documentation that comes with the operating system for more
information).
66 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Service request numbers
Service request numbers (SRNs) are error codes that contain a hyphen. The codes
have three digits before the hyphen, and three or four digits after the hyphen. SRNs
can be viewed using the AIX diagnostics or the Linux service aid “diagela” (if it is
installed).
Note: The “diagela” service aid is part of the Linux service aids for hardware
diagnostics. The service aids are separate from the operating system and are
available for download from the following Web site: http://
techsupport.services.ibm.com/server/lopdiags.
Using the SRN tables
The SRN list is in numerical sequence. The failing function codes (FFCs) are
provided to aid in locating a failing component (see “Failing function codes” on page
104).
Notes:
1. If the SRN does not appear in the table, see “Solving undetermined problems”
on page 135.
2. After replacing a component, verify the replacement part and perform a
log-repair action using the AIX diagnostics.
SRN tables
This section lists SRNs 101-711 through 2D02 (AIX) and A00-(x)xxx through
A1D-50x.
SRNs 101-711 through 2D02
Replace the parts in the order that the FFCs are listed.
Note: An x in the following SRNs represents any digit or character.
SRN FFC Description and action
101-711 to
101-726
101-888 210
101-2020 The system hung while trying to configure the Infiniband Communication Manager.
101-2021 The system hung while trying to configure the Infiniband TCP/IP Interface. This
101-xxxx xxxx The system hung while configuring a resource. The last three or four digits after the
103-151 151 The time-of-day battery failed. Action: go to battery replacement procedure
109-200 The system crashed while being run by the customer. Action: Use general checkout
xxx The system hung while trying to configure an unknown resource. Action: Run the
standalone diagnostics problem determination procedure. If the problem remains,
refer to “Failing function codes” on page 104 to find the FFC that matches the last
three digits of the SRN. Suspect the device adapter or device itself.
Note: xxx corresponds to the last three digits of the SRN.
The system does not IPL. Action: System checkout or undetermined problem
227
procedure.
This problem may be attributed to software. Report this problem to the AIX Support
Center.
problem may be attributed to software. Report this problem to the AIX Support
Center.
dash (-) identify the failing function code for the resource being configured. Go to
undetermined problem procedure.
procedure, problem determination procedure and get a new SRN.
Chapter 2. Diagnostics 67
SRN FFC Description and action
110-101 The diagnostics did not detect an installed resource. Action: If this SRN appeared
when running concurrent diagnostics, then run concurrent diagnostics using the diag
-a command.
110-921 to
110-926
110-935 812 The system halted while diagnostics were executing. Action: Use the problem
110-xxxx xxxx
111-107 A machine check occurred. Action: Go to “Performing the checkout procedure” on
111-108 An encoded SRN was displayed. Action: Go to “Performing the checkout procedure”
111-121 There is a display problem. Action: Go to “Performing the checkout procedure” on
111-78C 227 PCI adapter I/O bus problem. Action: Go to “Performing the checkout procedure” on
111-999 210 System does not perform a soft reset. Action: Go to “Performing the checkout
252B-101 252B Adapter configuration error.
252B-710 252B Permanent adapter failure.
252B-711 252B Adapter failure.
252B-712 252B Adapter failure.
812
xxx
221
The system halted while diagnostics were executing.
Note: xxx corresponds to the last three digits of the SRN. Action: Go to general
checkout or problem resolution.
determination procedure.
The system halted while diagnostics were executing.
Note: xxxx corresponds to the last three or four digits of the SRN following the dash
(-). If your 110 SRN is not listed, substitute the last three or four digits of the SRN for
xxxx, then proceed to the FFC table using the substituted digits as your FFC. Action:
Run standalone diagnostics, problem determination procedure for AIX and Linux. If
you still get the same SRN, refer to “Failing function codes” on page 104 to find the
FFC that matches the last three digits of the SRN.
page 106.
on page 106.
page 106.
page 106. Perform “Solving undetermined problems” on page 135.
procedure” on page 106.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
68 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
252B-713 252B Adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-714 252B Temporary adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-715 252B Temporary adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-716 252B
293
PCI bus error detected by EEH.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-717 252B
293
PCI bus error detected by adapter.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-718 252B
293
Temporary PCI bus error detected by adapter.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-719 252B Device bus termination power lost or not detected.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-720 252B Adapter detected device bus failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
Chapter 2. Diagnostics 69
SRN FFC Description and action
252B-721 252B Temporary adapter detected device bus failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-722 252B Device bus interface problem.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
252B-723 252B Device bus interface problem.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
256D-201 256D
221
256D-601 256D Error log analysis indicates adapter.
256D-602 256D Error log analysis indicates an error attention condition.
256D-603 256D Error Log Analysis indicates that the microcode could not be loaded on the adapter.
256D-604 256D
210
Adapter configuration error.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
Error Log Analysis indicates a permanent adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
70 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
256D-605 256D Error Log Analysis indicates permanent adapter failure is reported on the other port of
this adapter.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
256D-606 256D Error Log Analysis indicates adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
256D-701 256D
221
Error Log Analysis indicates permanent adapter failure.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
256D-702 256D
221
Error Log Analysis indicates permanent adapter failure is reported on the other port of
this adapter.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
650-xxx 650 Disk drive configuration failed.
651-xxx The CEC reported a non-critical error. Action: Schedule deferred maintenance. Refer
to the problem determination procedure for this system, with the 8-digit error and
location codes, for the necessary repair action. If the 8-digit error and location codes
were NOT reported, then run AIX diagnostics in problem determination procedure and
record and report the 8-digit error and location codes for this SRN.
651-140 221 Display Character test failed.
Note: Diagnostic will provide this SRN but there is no action to be taken. Do not
perform operator panel test from diagnostics.
651-150 166 2E0 Sensor indicates a fan has failed. Action: Go to “Performing the checkout procedure”
on page 106.
651-151 152 2E2 Sensor indicates a voltage is outside the normal range. Go to “Performing the
checkout procedure” on page 106.
651-152 2E1 Sensor indicates an abnormally high internal temperature. Action: Make sure that:
1. The room ambient temperature is within the system operating environment.
2. There is unrestricted air flow around the system.
3. All system covers are closed.
651-153 152
E19
Sensor indicates a power supply has failed. Action: Go to “Performing the checkout
procedure” on page 106.
651-159 210 Sensor indicates a FRU has failed. Action: use the failing function codes, use the
physical location code(s) from the diagnostic problem report screen to determine the
FRUs.
Chapter 2. Diagnostics 71
SRN FFC Description and action
651-161 2E2 Sensor indicates a voltage is outside the normal range. Action: Go to “Performing the
checkout procedure” on page 106.
651-162 2E1 Sensor indicates an abnormally high internal temperature. Action: Make sure that:
1. The room ambient temperature is within the system operating environment.
2. There is unrestricted air flow around the system.
3. There are no fan or blower failures in the BladeCenter unit.
If the problem remains, check the management module event log for possible causes
of overheating.
651-163 E19 Sensor indicates a power supply has failed. Action: Contact your support person.
651-169 Sensor indicates a FRU has failed. Action: Contact your support person.
651-170 Sensor status not available. Action: Contact your support person.
651-171 Sensor status not available Action: Contact your support person.
651-600 Uncorrectable memory or unsupported memory. Action: Examine the memory
modules and determine if they are supported types. If the modules are supported,
then replace the appropriate memory modules.
651-601 Missing or bad memory. Action: If the installed memory matches the reported memory
size, then replace the memory; otherwise, add the missing memory.
651-602 2C7 Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-603 2C6
2C7
651-605 2C6 Memory module has no matched pair. Action: The most probable failure is the
651-608 D01 Bad L2 cache.
651-609 D01 Missing L2 cache.
651-610 210 CPU internal error.
651-611 210 CPU internal cache controller error.
651-612 D01 External cache ECC single-bit error.
651-613 D01 External cache ECC single-bit error.
651-614 214 System bus time-out error.
651-615 292 Time-out error waiting for I/O.
651-619 Error log analysis indicates an error detected by the CPU. Action: Use failing function
651-621 2C6 ECC correctable error Action: Go to “Performing the checkout procedure” on page
651-623 2C6 Correctable error threshold exceeded Action: Go to “Performing the checkout
651-624 214 Memory control subsystem internal error.
651-625 214 Memory address error (invalid address or access attempt).
651-626 214 Memory data error (bad data going to memory).
651-627 214 System bus time-out error.
651-628 210 System bus protocol/transfer error.
651-629 210 Error log analysis indicates an error detected by the memory controller. Action: Go to
Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
memory module paired with the memory module identified by the location code.
codes and the physical location codes from the diagnostic problem report screen to
determine the FRUs.
106.
procedure” on page 106.
“Performing the checkout procedure” on page 106.
72 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
651-632 308 Internal device error.
651-639 210 Error log analysis indicates an error detected by the I/O. Action: Use the problem
determination procedure and failing function codes, use the physical location codes
from the diagnostic problem report screen to determine the FRUs.
651-640 2D5 I/O general bus error.
651-641 2D6 Secondary I/O general bus error.
651-642 2D3 Internal service processor memory error.
651-643 2D3 Internal service processor firmware error.
651-644 2D3 Other internal service processor hardware error.
651-659 2CD ECC correctable error. Action: Go to “Performing the checkout procedure” on page
106.
651-65A 2CE ECC correctable error. Action: Go to “Performing the checkout procedure” on page
106.
651-65B 2CC ECC correctable error. Action: Go to “Performing the checkout procedure” on page
106.
651-664 302 Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-665 303 Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-666 304 Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-669 2CD Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-66A 2CE Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-66B 2CC Correctable error threshold exceeded. Action: Go to “Performing the checkout
procedure” on page 106.
651-674 302 Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-675 303 Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-676 304 Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-679 2CD Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-67A 2CE Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-67B 2CC Failed memory module. Action: Go to “Performing the checkout procedure” on page
106.
651-685 303 Memory module has no matched pair. Action: The most probable failure is the
memory module paired with the memory module identified by the location code. Go to
“Performing the checkout procedure” on page 106.
651-686 304 Memory module has no matched pair. Action: The most probable failure is the
memory module paired with the memory module identified by the location code. Go to
“Performing the checkout procedure” on page 106.
651-710 214
System bus parity error.
2C4
Chapter 2. Diagnostics 73
SRN FFC Description and action
651-711 210
2C4
651-712 214 System bus parity error.
651-713 214 System bus protocol/transfer error.
651-714 2C4 System bus protocol/transfer error.
651-715 2C4 System bus protocol/transfer error.
651-720 2C7
214
651-721 2C6
2C7
214
651-722 2C4 System bus parity error.
651-723 2C4 System bus protocol/transfer error.
651-724 292 I/O host bridge time-out error.
651-725 292 I/O host bridge address/data parity error.
651-726 Software I/O host bridge timeout caused by software. Action: This error is caused by a
651-731 2C8 Intermediate or system bus address parity error.
651-732 2C8 Intermediate or system bus data parity error.
651-733 2C8 Intermediate or system bus address parity error.
651-734 292 Intermediate or system bus data parity error.
651-735 292 Intermediate or system bus time-out error.
651-736 292 Intermediate or system bus time-out error.
651-740 2D3 Note: Ensure that the system IPLROS and service processor are at the latest
651-741 2D3 Service processor error accessing special registers.
651-742 2D3 Service processor reports unknown communication error.
651-743 2D5 Service processor error accessing Vital Product Data EEPROM.
651-745 2D9 Service processor error accessing power controller.
651-746 2D4 Service processor error accessing fan sensor.
651-747 2D5 Service processor error accessing thermal sensor.
651-748 2E2 Service processor error accessing voltage sensor.
651-750 2D4 Service processor detected NVRAM error.
651-751 2D4 Service processor error accessing real-time clock/time-of-day clock.
651-752 2D4 Service processor error accessing JTAG/COP controller/hardware.
651-753 151
2D4
651-770 292 Intermediate or system bus address parity error.
651-771 292 Intermediate or system bus data parity error.
651-772 292 Intermediate or system bus time-out error.
651-773 227 Intermediate or system bus data parity error.
System bus parity error.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
software or operating system attempt to access an invalid memory address. Contact
software support for assistance.
firmware level before removing any parts from the system.
Service processor detects loss of voltage from the time-of-day clock backup battery.
74 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
651-780 2C7
214
651-781 2C7
214
651-784 302
214
651-785 303
214
651-786 304
214
651-789 2CD
214
651-78A 2CE
214
651-78B 2CC
214
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
Uncorrectable memory error. Action: Go to “Performing the checkout procedure” on
page 106.
651-809 Power fault warning due to unspecified cause. Action: Go to “Performing the checkout
procedure” on page 106.
651-810 2E2 Over-voltage condition was detected. Action: Shut the system down and do the
following before replacing any FRUs:
1. Visually inspect the power cables and reseat the connectors.
2. Run the following command diag -Avd sysplanar0. When the Resource Repair
Action menu displays, select sysplanar0.
651-811 2E2 Under voltage condition was detected Action: Shut the system down and do the
following before replacing any FRUs.
1. Visually inspect the power cables and reseat the connectors.
2. Run the following command diag -Avd sysplanar0. When the Resource Repair
Action menu displays, select sysplanar0.
651-813 System shutdown due to loss of ac power to the site. Action: System resumed normal
operation, no action required.
651-818 Power fault due to manual activation of power-off request. Action: Resume normal
operation.
651-820 2E1 An over-temperature condition was detected. Action:
1. Make sure that:
v The room ambient temperature is within the system operating environment
v There is unrestricted air flow around the system
2. Replace the system-board and chassis assembly.
651-821 2E1 System shutdown due to an over maximum temperature condition being reached.
Action:
1. Make sure that:
v The room ambient temperature is within the system operating environment
v There is unrestricted air flow around the system
2. Replace the system-board and chassis assembly.
651-822 2E1 System shutdown due to over temperature condition and fan failure. Use the physical
FRU location(s) as the probable cause(s). Action: Use the physical location codes to
replace the FRUs that are identified on the diagnostics problem report screen.
651-831 2E2 Sensor detected a voltage outside of the normal range. Action: Go to “Performing the
checkout procedure” on page 106.
Chapter 2. Diagnostics 75
SRN FFC Description and action
651-832 G2E1 Sensor detected an abnormally high internal temperature. Action: Make sure that:
1. The room ambient temperature is within the system operating environment.
2. There is unrestricted air flow around the system.
3. There are no fan failures.
651-841 152
2E2
651-842 2E1 Sensor detected an abnormally high internal temperature. Action: Make sure that:
651-90x Platform-specific error. Action: Call your support center.
652-600 A non-critical error has been detected: uncorrectable memory or unsupported
652-610 210 A non-critical error has been detected: CPU internal error. Action: Schedule deferred
652-611 210 A non-critical error has been detected: CPU internal cache or cache controller error.
652-612 D01 A non-critical error has been detected: external cache parity or multi-bit ECC error.
652-613 D01 A non-critical error has been detected: external cache ECC single-bit error. Action:
652-623 2C6 A non-critical error has been detected: correctable error threshold exceeded. Action:
652-630 307 A non-critical error has been detected: I/O expansion bus parity error. Action:
652-631 307 A non-critical error has been detected: I/O expansion bus time-out error. Action:
652-632 307 A non-critical error has been detected: I/O expansion bus connection failure. Action:
652-633 307 A non-critical error has been detected: I/O expansion unit not in an operating state.
652-634 307 A non-critical error has been detected: internal device error. Action: Schedule deferred
652-664 302 A non-critical error has been detected: correctable error threshold exceeded. Action:
652-665 303 A non-critical error has been detected: correctable error threshold exceeded. Action:
Sensor detected a voltage outside of the normal range. Go to “Performing the
checkout procedure” on page 106.
1. The room ambient temperature is within the system operating environment.
2. There is unrestricted air flow around the system.
3. All system covers are closed.
4. There are no fan failures.
memory. Action: Schedule deferred maintenance. Examine the memory modules and
determine if they are supported types. If the modules are supported, then replace the
appropriate memory modules.
maintenance. Go to “Performing the checkout procedure” on page 106.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
maintenance. Go to “Performing the checkout procedure” on page 106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
76 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
652-666 304 A non-critical error has been detected: correctable error threshold exceeded. Action:
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
652-669 2CD A non-critical error has been detected: correctable error threshold exceeded. Action:
Schedule deferred G maintenance. Go to “Performing the checkout procedure” on
page 106.
652-66A 2CE A non-critical error has been detected: correctable error threshold exceeded. Action:
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
652-66B 2CC A non-critical error has been detected: correctable error threshold exceeded. Action:
Schedule deferred maintenance. Go to “Performing the checkout procedure” on page
106.
652-731 2C8 A non-critical error has been detected: intermediate or system bus address parity
error. Action: Schedule deferred maintenance. Go to “Performing the checkout
procedure” on page 106.
652-732 2C8 A non-critical error has been detected: intermediate or system bus data parity error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-733 2C8
292
A non-critical error has been detected: intermediate or system bus address parity
error. Action: Schedule deferred maintenance. Go to “Performing the checkout
procedure” on page 106.
652-734 2C8
292
A non-critical error has been detected: intermediate or system bus data parity error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-735 2D2
292
A non-critical error has been detected: intermediate or system bus time-out error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-736 2D2
292
A non-critical error has been detected: intermediate or system bus time-out error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-770 2C8
292
A non-critical error has been detected: intermediate system bus address parity error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-771 2C8
292
A non-critical error has been detected: intermediate or system bus data parity error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-772 2D2
292
A non-critical error has been detected: intermediate or system bus time-out error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-773 227 A non-critical error has been detected: intermediate or system bus data parity error.
Action: Schedule deferred maintenance. Go to “Performing the checkout procedure”
on page 106.
652-88x The CEC or SPCN reported a non-critical error. Action: Schedule deferred
maintenance. Refer to the entry MAP in this system unit's system service guide, with
the 8-digit error and location codes, for the necessary repair action. If the 8-digit error
and location codes were NOT reported, then run diagnostics in problem determination
mode and record and report the 8-digit error and location codes for this SRN.
652-89x The CEC or SPCN reported a non-critical error. Action: Schedule deferred
maintenance. Refer to the entry MAP in this system unit's system service guide, with
the 8-digit error and location codes, for the necessary repair action. If the 8-digit error
and location codes were NOT reported, then run diagnostics in problem determination
mode and record and report the 8-digit error and location codes for this SRN.
Chapter 2. Diagnostics 77
SRN FFC Description and action
814-112 814 The NVRAM test failed.
814-113 221 The VPD test failed.
814-114 814 I/O Card NVRAM test failed.
815-100 815 The floating-point processor test failed.
815-101 815 Floating point processor failed.
815-102 815 Floating point processor failed.
815-200 815
7C0
815-201 815 Processor has a status of failed. Processors with a failed status are deconfigured and
817-123 817 The I/O planar time-of-day clock test failed.
817-124 817 Time of day RAM test failed.
817-210 817 The time-of-day clock is at POR.
817-211 817 Time of day POR test failed.
817-212 151 The battery is low.
817-213 817 The real-time clock is not running.
817-215 817 Time of day clock not running test failed.
817-217 817 Time of day clock not running.
887-101 887 POS register test failed.
887-102 887I/O register test failed.
887-103 887 Local RAM test failed.
887-104 887 Vital Product Data (VPD) failed.
887-105 887 LAN coprocessor internal tests failed.
887-106 887 Internal loopback test failed.
887-107 887 External loopback test failed.
887-108 887 External loopback test failed.
887-109 887 External loopback parity tests failed.
887-110 887 External loopback fairness test failed.
887-111 887 External loopback fairness and parity tests failed.
887-112 887 External loopback (twisted pair) test failed.
887-113 887 External loopback (twisted pair) parity test failed.
887-114 887 Ethernet loopback (twisted pair) fairness test failed.
887-115 887 External loopback (twisted pair) fairness and parity tests failed.
887-116 887 Twisted pair wrap data failed.
887-117 887 Software device configuration fails.
887-118 887 Device driver indicates a hardware problem.
887-120 887 Device driver indicates a hardware problem.
887-121 B08 Ethernet transceiver test failed.
887-122 B09 Ethernet 10 base-2 transceiver test failed.
887-123 887 Internal loopback test failed.
887-124 887 Software error log indicates a hardware problem.
Power-on self-test indicates a processor failure.
therefore cannot be tested or used by the system.
78 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN FFC Description and action
887-125 887 Fuse test failed.
887-202 887 Vital Product Data test failed.
887-203 887 Vital Product Data test failed.
887-209 887 RJ-45 converter test failed.
887-304 887 Coprocessor internal test failed.
887-305 887 Internal loopback test failed.
887-306 887 Internal loopback test failed.
887-307 887 External loopback test failed.
887-319 887 Software device driver indicates a hardware failure.
887-400 887 Fuse test failed.
887-401 887 Circuit breaker for Ethernet test failed.
887-402 887 Ethernet 10 Base-2 transceiver test failed.
887-403 887 Ethernet 10 Base-T transceiver test failed.
887-405 887 Ethernet- network Rerun diagnostics in advanced mode for accurate problem
determination.
254E-201 254E
Adapter configuration error.
221
254E-601 254 Error log analysis indicates adapter failure.
254E-602 254 Error log analysis indicates an error attention condition.
254E-603 254 Error log analysis indicates that the microcode could not be loaded on the adapter.
254E-604 254 Error log analysis indicates a permanent adapter failure.
254E-605 254 Error log analysis indicates permanent adapter failure is reported on the other port of
this adapter.
254E-606 254 Error log analysis indicates adapter failure.
254E-701 254E
Error log analysis indicates permanent adapter failure.
221
254E-702 254E
221
Error log analysis indicates permanent adapter failure is reported on the other port of
this adapter.
2567 USB integrated system-board and chassis assembly.
25A0 2631 Configuring I/O planar control logic for IDE bus devices.
25C4 Broadcom adapter
2631 2631 IDE controller - system-board and chassis assembly
2640-114 2640 IDE disk diagnostic failure
2640-115 2640
2631
IDE disk error on open or configuring device system-board and chassis assembly IDE controller
2640-121 2640 Physical volume hardware error.
2640-131 2640 Smart status threshold exceeded.
2640-132 2640 Command timeouts threshold exceeded.
2640-133 2640 Command timeout with error condition.
2640-134 2640 Hardware command or DMA failure.
2640-135 2640 IDE DMA error with no error status.
2640-136 2640
Timeout waiting for controller or drive with no busy status.
2631
Chapter 2. Diagnostics 79
SRN FFC Description and action
25C4-201 25C4 Configuration error. Go to “Performing the checkout procedure” on page 106.
25C4-701 25C4 Permanent adapter failure. Go to “Performing the checkout procedure” on page 106.
25C4-601 25C4 Download firmware error. Go to “Performing the checkout procedure” on page 106.
25C4-602 25C4 EEPROM read error. Go to “Performing the checkout procedure” on page 106.
2D02 2631 Generic reference for USB controller/adapter - system-board and chassis assembly
FFC-724 FFC Temporary device bus interface problem.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
FFC-725 FFC Temporary device bus interface problem.
1. Check the BladeCenter management module event log. If an error was recorded
by the system or if a checkpoint code is displayed on the console, see “POST
checkpoint codes” on page 9.
2. Replace any parts reported by the diagnostic program.
3. Replace the system-board and chassis assembly.
SRNs A00-(x)xxx through A24-(x)xxx
Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash
(–).
The x in the following SRNs will have a value of 1, 2, 4, or 8, with a meaning as
follows:
Number Meaning
1 Replace all FRUs listed
2 Hot swap supported
4 Software might be the cause
8 Reserved
SRN Description FRU/action
A00-FF0 Error log analysis is unable to determine the
error. The error log indicates the following
physical FRU locations as the probable
causes.
A01-00x Error log analysis indicates an error detected
by the CPU, but the failure could not be
isolated.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
80 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN Description FRU/action
A01-01x GCPU internal error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A01-02x CPU internal cache or cache controller error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A01-05x System bus time-out error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A01-06x Time-out error waiting for I/O.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A01-07x System bus parity error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A01-08x System bus protocol/transfer error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A02-00x Error log analysis indicates an error detected
by the memory controller, but the failure
1. Check the BladeCenter management module event
could not be isolated.
2. If no entry is found, replace the system-board and
A02-01x Uncorrectable Memory Error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
Chapter 2. Diagnostics 81
SRN Description FRU/action
A02-03x Correctable error threshold exceeded.
A02-04x Memory Control subsystem internal error.
A02-05x Memory Address Error (invalid address or
access attempt).
A02-06x Memory Data error (Bad data going to
memory).
A02-09x System bus parity error.
A02-10x System bus time-out error.
A02-11x System bus protocol/transfer error.
A02-12x I/O Host Bridge time-out error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console,
see“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
82 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
SRN Description FRU/action
A02-13x I/O Host Bridge address/data parity error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-00x Error log analysis indicates an error detected
by the I/O device, but the failure could not be
1. Check the BladeCenter management module event
isolated.
2. If no entry is found, replace the system-board and
A03-01x I/O Bus Address parity error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-05x I/O Error on non-PCI bus.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-07x System bus address parity error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-09x System bus data parity error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-11x System bus time-out error.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
A03-12x Error on System bus.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
Chapter 2. Diagnostics 83
SRN Description FRU/action
A03-13x I/O Expansion bus parity error.
A03-14x I/O Expansion bus time-out error.
A03-15x I/O Expansion bus connection failure.
A03-16x I/O Expansion unit not in an operating state.
A05-00x Error log analysis indicates an environmental
and power warning, but the failure could not
be isolated.
A05-01x Sensor indicates a fan has failed.
A05-02x System shutdown due to a fan failure.
A05-03x Sensor indicates a voltage outside normal
range.
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
1. Check the BladeCenter management module event
2. If no entry is found, replace the system-board and
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
log; if an error was recorded by the system or if a
checkpoint code is displayed on the console, see
“POST checkpoint codes” on page 9.
chassis assembly.
84 BladeCenter JS21 Types 7988 and 8844: Problem Determination and Service Guide
Loading...