Confirming Initial Error Code - IBM eserver p Series Service Manual

Hide thumbs Also See for eserver p Series:
Table of Contents

Advertisement

e. Select option 6. Verify that the state changes to currently disabled. Disabling fast system boot
automatically enables slow boot.
f. Select Option 98 to exit the system power control menu.
g. Use the HMC to power up the system to the SMS menus in a full system partition.
3. When the system has stopped at the SMS menus, use the HMC to power off the system. At this point,
the service processor menus should be available to examine the service processor error log.

Confirming Initial Error Code

The service processor may have recorded one or more symptoms in its error log. If the system has
attempted to boot since an error terminated normal operation, there may be specific fault information in the
service processor error log. Examine this error log before proceeding (see "System Information Menu" on
page 490).
In the service processor error log, the most recent error is at the top of the list and the oldest error is at
the bottom. It is also important to look at the time stamp associated with each error. (The time stamps in
the service processor error log reflect coordinated universal time (UTC), which is also referred to as
Greenwich mean time.)
On this system, the error code displayed in the operator panel may not be indicative of the root cause of
the problem. This is also true of the most recent error in the service processor error log.
Attempt to find the error code that originally sent you to the "Checkpoints and Error Codes Index" on page
245 table.
1. If you can not find the error code in the service processor error log, start with the error code at the
bottom of the list. Proceed to 3 below.
2. If you can find the error code in the service processor error log, observe the time stamps and look for
a group of failures that happened within minutes prior to this error code. In this group, start at the error
code with the earliest time stamp. Proceed to 3.
3. Examine the list of error codes you obtained from 1 or 2 and look for any of the form 4xxB xxxx.
Can you find any error codes of the form 4xxB xxxx?
No
Proceed to step 6.
Yes
Proceed to step 4.
4. Do any of the error codes of the form 4xxB xxxx have the same first two characters on the left as the
first two characters on the left of the error code that sent you to the MAP?
No
Proceed to step 6.
Yes
Proceed to step 5.
5. Adjust the order of the list of error codes you obtained from steps 1 or 2 by placing the error codes of
the form 4xxB xxxx with the same first two characters as the error code that sent you to this MAP on
the bottom of the list. Start step 6 at the bottom of the adjusted list of error codes. Proceed to step 6.
6. To get a list of possible FRUs, select the detail screen for each error code. Record the listed location
codes and their order.
Note: If the error code that results from this procedure is 406x 0EA0, 406x 0EA1, 406x 0EA2, or 406x
0EA4, do not go back to the "Checkpoints and Error Codes Index" on page 245 with this error
code. Look for a hardware error in the service processor error log of the form 450x yyyy, 460x
yyyy, or 4B2x yyyy that occurred just prior to the 406x 0EAy error. Use this hardware error code
instead when returning to the "Checkpoints and Error Codes Index" on page 245.
Return to the step in the "Checkpoints and Error Codes Index" on page 245 table immediately after the
step that sent you to this "Confirming Initial Error Code" procedure to perform the listed repair actions.
If the repair actions for an error code are ineffective, continue to work upward through this group of
242
EserverpSeries 650 Service Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Eserver p650

Table of Contents