Table 16. BA000010 to BA400002 Partition firmware 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 8406,” on page 229 to determine which components are CRUs and which
components are FRUs.
Error code
Description
Action
BA210020
I/O configuration exceeded the
maximum size allowed by partition
firmware.
1.
Increase the logical memory block size to
256 MB and restart the blade server.
2.
If the problem persists:
a.
Go to “Checkout procedure” on page
184.
b.
Replace the system-board, as described
in “Replacing the FRU system-board
and chassis assembly” on page 260.
BA210100
An error may not have been sent to the
management module event log.
1.
Reboot the blade server.
2.
If the problem persists:
a.
Go to “Checkout procedure” on page
184.
b.
Replace the system-board, as described
in “Replacing the FRU system-board
and chassis assembly” on page 260.
BA210101
The partition firmware event log queue
is full
1.
Reboot the blade server.
2.
If the problem persists:
a.
Go to “Checkout procedure” on page
184.
b.
Replace the system-board, as described
in “Replacing the FRU system-board
and chassis assembly” on page 260.
BA210102
There was a communication failure
between partition firmware and the
hypervisor. The lpevent that was
expected from the hypervisor was not
received.
1.
Review the event log for errors that
occurred around the time of this error.
2.
Correct any errors that are found and
reboot the blade server.
3.
If the problem persists:
a.
Reboot the blade server.
b.
If the problem persists:
1)
Go to “Checkout procedure” on
page 184.
2)
Replace the system-board, as
described in “Replacing the FRU
system-board and chassis assembly”
on page 260.
Chapter 2. Diagnostics
77
