Bull Escala BL460, Руководство по диагностике и обслуживанию, Страница: 85 / 266

Chapter 2. Diagnostics
65
• 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.
•
See Chapter 3 , “ Parts listing ,” on page 197 to determine which components are CRUs and which
components are FRUs.
Error code Description Action
BA210010
The transfer of control to the SLIC loader
failed
1. Go to “ Checkout procedure ” on page 148 .
2. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
BA210011
The transfer of control to the IO Reporter
failed
1. Go to “ Checkout procedure ” on page 148 .
2. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
BA210012
There was an NVRAMRC forced-boot
problem; unable to load the previous
boot’s operating system image
1. Use the SMS menus to verify that the partition firmware
can still detect the operating system image.
2. If the problem persists:
a. Go to “ Checkout procedure ” on page 148 .
b. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
BA210013
There was a partition firmware error
when in the SMS menus.
1. Reboot the blade server.
2. If the problem persists:
a. Go to “ Checkout procedure ” on page 148 .
b. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
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 148 .
b. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
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 148 .
b. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
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 148 .
b. Replace the system-board and chassis assembly, as
described in “ Replacing the Tier 2 system-board and
chassis assembly ” on page 229 .
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 148 .
2) Replace the system-board and chassis assembly,
as described in “ Replacing the Tier 2 system-board
and chassis assembly ” on page 229 .