IBM P260, Installation And Service Manual

Page: 489 / 524

v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v See Chapter 7, “Parts listing for IBM Flex System p260 and p460 Compute Nodes,” on page 97 to determine
which components are CRUs and which components are FRUs.
v If an action step is preceded by Trained service technician only, that step must be performed only by a trained
service technician.
Isolation
procedure or
symbolic failing
item
Symptom Action
FSPSP32 The enclosure has
one of the following
problems:
v The enclosure
VPD cannot be
found.
v The enclosure
serial number is
not programmed.
v The enclosure
feature code is not
programmed.
Record the reason code, which is the last 4 digits of the first word from
the SRC. Perform one of the following procedures based on the value of
the reason code:
v Reason code A46F
1. Perform a firmware update. See “Updating the firmware” on page
22.
2. If the problem persists, replace the system-board and chassis
assembly, as described in “Replacing the system-board and chassis
assembly” on page 83.
v Reason code A460
This procedure must be performed by an authorized service provider
and requires a celogin user ID. If you are not an authorized service
provider, contact your next level of support.
1. Access the Advanced System Management Interface (ASMI). Expand
System Configuration
> Program Vital Product Data. Set the
enclosure serial number. This action automatically resets the service
processor.
2. Power on the compute node, as described in “Turning on the
compute node” on page 12.
v Reason code A45F
This procedure must be performed by an authorized service provider
and requires a celogin user ID. If you are not an authorized service
provider, contact your next level of support.
1. Access the Advanced System Management Interface (ASMI). Expand
System Configuration
> Program Vital Product Data. Set the
enclosure feature code. This action automatically resets the service
processor.
2. Power on the compute node, as described in “Turning on the
compute node” on page 12.
If you do not see your reason code listed, contact your next level of
support.
Chapter 8. Troubleshooting
477