Table of Contents
Advertisement
A700yyyy Licensed internal code SRCs
An A7xx SRC is a licensed internal code SRC that is deprecated in favor of a
corresponding B7xx SRC. B7xx SRCs are described in "B700xxxx Licensed internal
code SRCs" on page 39.
Table 8. A700yyyy Licensed internal code SRCs
Attention code
Description
A7003000
A user-initiated platform dump occurred.
A700yyyy
See the description for the B700yyyy error
code with the same yyyy value.
AA00E1A8 to AA260005 Partition firmware attention codes
AAxx attention codes provide information about the next target state for the
platform firmware. These codes might indicate that you need to perform an action.
Table 9 describes the partitioning firmware codes that may be displayed if POST
detects a problem. Each message description includes a suggested action to correct
the problem.
Table 9. AA00E1A8 to AA260005 Partition firmware attention codes
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 7998," on page 235 to determine which components are CRUs and which
components are FRUs.
Attention code
AA00E1A8
AA00E1A9
AA00E1B0
Description
The system is booting to the open
firmware prompt.
The system is booting to the System
Management Services (SMS) menus.
Waiting for the user to select the
language and keyboard. The menu
should be visible on the console.
Action
No service action required.
Perform the action in the B700yyyy error code
with the same yyyy value.
Action
At the open firmware prompt, type dev
/packages/gui obe and press Enter; then, type
1 to select SMS Menu.
1. If the system or partition returns to the
SMS menus after a boot attempt failed, use
the SMS menus to check the progress
indicator history for a BAxx xxxx error,
which may indicate why the boot attempt
failed. Follow the actions for that error code
to resolve the boot problem.
2. Use the SMS menus to establish the boot
list and restart the blade server.
1. Check for server firmware updates.
2. Apply any available updates.
3. If the problem persists:
a. Go to "Checkout procedure" on page
186.
b. Replace the system-board and chassis
assembly, as described in "Replacing the
Tier 2 system-board and chassis
assembly" on page 270.
Chapter 2. Diagnostics
25
Advertisement
Table of Contents
