Bull Escala BL460, Problem Determination And Service Manual, Page: 181 / 266

Chapter 2. Diagnostics
161
2.10.6 Memory problems
Identify memory problem symptoms and what corrective actions to take.
•
Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
•
See Chapter 3 , “ Parts listing ,” on page 197 to determine which components are CRUs and which components are
FRUs.
•
If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Symptom Action
The amount of system memory
displayed is less than the amount
of physical memory installed.
1. Make sure that:
− All installed memory is recognized in the Display Vital Product Data
of lscfg -vp.
− The memory modules are seated properly.
−
You have installed the correct type of memory.
−
If you changed the memory, you updated the memory configuration
with the Configuration/Setup Utility program.
− All banks of memory on the DIMMs are enabled. The blade server
might have automatically disabled a DIMM bank when it detected a
problem or a DIMM bank could have been manually disabled.
2. Check the management-module event log for error message (checkpoint or
firmware error codes).
−
If the DIMM was disabled by a system-management interrupt (SMI),
replace the DIMM.
−
If the DIMM was disabled by POST, obtain the eight-digit error code
and replace the failing DIMM.
3. Reseat the DIMM.
4. Replace the DIMM.
5. Replace the system-board and chassis assembly.
2.10.7 Microprocessor problems
Identify microprocessor problem symptoms and what corrective actions to take.
•
Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
•
See Chapter 3 , “ Parts listing ,” on page 197 to determine which components are CRUs and which components are
FRUs.
•
If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Symptom Action
The blade server will not boot or
a checkpoint or firmware error
code is logged in the
management-module event log
(the startup microprocessor is not
working correctly)
1. If a checkpoint or firmware error was logged in the management module event
log, correct that error.
2. If no error was logged, restart the blade server and check the management module
event log again for error codes.
3. Replace the system-board and chassis assembly.