IBM PS703 Service Manual page 61

Table 16. B2xxyyyy Logical partition SRCs (continued)
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved. If an action solves the problem, then you can stop performing the remaining actions.
v See Chapter 3, "Parts listing, type 7891," on page 225 to determine which components are CRUs and which
components are FRUs.
Reference Code Description
B2008151 System firmware detected an error.
B2008152 No active system processors.
B2008160 A problem occurred during the
migration of a partition.
B2008161 A problem occurred during the
migration of a partition.
B200A100 A partition ended abnormally; the
partition could not stay running and
shut itself down.
B200A101 A partition ended abnormally; the
partition could not stay running and
shut itself down.
B200A140 A lower priority partition lost a
usable processor to supply it to a
higher priority partition with a bad
processor.
B200B07B Informational system log entry only.
B200B215 A problem occurred after a partition
ended abnormally.
There was a communications
problem between this partition's
service processor and the platform's
service processor.
B2005127 Timeout occurred during a main
store dump IPL.
B2D03001 Informational system log entry only.
B2D03002 Informational system log entry only.
B200C1F0 An internal system firmware error
occurred during a partition
shutdown or a restart.
B200D150 A partition ended abnormally; there
was a communications problem
between this partition and the code
that handles resource allocation.
B200E0AA A problem occurred during the
power off of a partition.
B200F001 A problem occurred during the
startup of a partition. An operation
has timed out.
Action
Use the Integrated Virtual Manager (IVM) to increase the
Logical Memory Block (LMB) size, and to reduce the
number of virtual devices for the partition.
Verify that processor resources are assigned to the
partition.
Contact IBM support.
Contact IBM support.
1. Check the error logs and take the actions for the error
codes that are found.
2. Go to "Isolating firmware problems" on page 216.
1. Check the error logs and take the actions for the error
codes that are found.
2. Go to "Isolating firmware problems" on page 216.
Evaluate the entire LPAR configuration. Adjust partition
profiles with the new number of processors available in
the system.
No corrective action is required.
Restart the platform.
There was not enough memory available for the dump to
complete before the timeout occurred. Retry the main
store dump IPL, or else power on the partition normally.
No corrective action is required.
No corrective action is required.
Go to "Isolating firmware problems" on page 216.
Check for server firmware updates; then, install the
updates if available.
Go to "Isolating firmware problems" on page 216.
Look for other errors and resolve them.
49
Chapter 2. Diagnostics