IBM BladeCenter JS21 Types 8844 Service Manual page 55

Problem determination and service guide
Hide thumbs Also See for BladeCenter JS21 Types 8844:
Table of Contents

Advertisement

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
B2008113
B2008114
B2008115
B2008117
B2008121
B2008123
B2008125
B2008127
B2008129
B200A100
B200A101
B200B07B
B200C1F0
B200D150
B200F003
B200F004
B200F005
Description
During the startup of a partition, an error
occurred while mapping memory for the
partition startup.
During the startup of a partition, there
was a failure verifying the VPD for the
partition resources during startup.
During the startup of a partition, there
was a low level partition-to-partition
communication failure.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
During the startup of a partition, the
partition did not start up due to a system
firmware error.
A partition ended abnormally; the
partition could not stay running and shut
itself down.
System log entry only.
An internal system firmware error
occurred during a partition shutdown or a
restart.
A partition ended abnormally; there was
a communications problem between this
partition and the code that handles
resource allocation.
During the startup of a partition, the
partition processor(s) did not start the
firmware within the time-out window.
A partition had a communications
problem during a shutdown of the
partition.
Action
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.
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.
Go to "Firmware problem isolation" on page
127.
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.
No service action required.
Go to "Firmware problem isolation" on page
127.
Check for server firmware updates; then, install
the updates if available.
Collect the partition dump information; then, go
to "Firmware problem isolation" on page 127.
Collect the partition dump information; then, go
to "Firmware problem isolation" on page 127.
Chapter 2. Diagnostics
39

Advertisement

Table of Contents
loading

Table of Contents