BA340021
Explanation: A logical partition event communication failure occurred when writing the BladeCenter open fabric
manager system initiator capabilities data to the service processor.
Response:
1. Reboot the server.
2. Check for server firmware updates; install the updates if available.
3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended
actions. If a firmware update is needed, see Updating the firmware
BA400001
Explanation: Informational message: DMA trace buffer full.
Response:
1. Reboot the server.
2. Check for server firmware updates; install the updates if available.
3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended
actions. If a firmware update is needed, see Updating the firmware
BA400002
Explanation: Informational message: DMA map-out size mismatch.
Response:
1. Reboot the server.
2. Check for server firmware updates; install the updates if available.
3. Search RETAIN tips and the firmware change history for the reference code to determine the recommended
actions. If a firmware update is needed, see Updating the firmware
POST progress codes (checkpoints)
When you turn on the compute node, the power-on self-test (POST) performs a series of tests to check
the operation of the compute node components. Use the management module to view progress codes that
offer information about the stages involved in powering on and performing an initial program load (IPL).
Progress codes do not indicate an error, although in some cases, the compute node can pause indefinitely
(hang). Progress codes for compute nodes are 9-word, 8-digit hexadecimal numbers that start with C and
D.
Checkpoints are generated by various components. The service processor and the partitioning firmware
are key contributors. The service processor provides additional isolation procedure codes for
troubleshooting.
A checkpoint might have an associated location code as part of the message. The location code provides
information that identifies the failing component when there is a hang condition.
Notes:
1. For checkpoints with no associated location code, see “Light path diagnostics” on page 485 to identify
the failing component when there is a hang condition.
2. For checkpoints with location codes, see “Location codes” on page 109 to identify the failing
component when there is a hang condition.
3. For eight-digit codes not listed here, see Progress codes overview in the Systems Hardware
information center.
BA340021 • BA400002
Chapter 8. Troubleshooting 233
To Next Page
Loading...
Need help?
General