Table of Contents
Advertisement
Management module service processor problems
Determine if a problem is a management module service processor problem and, if
so, the corrective action to take.
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 3, "Parts listing, Type 7998," on page 235 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.
Symptom
Service processor in the
management module reports a
general monitor failure.
Memory problems
Identify memory problem symptoms and what corrective actions to take.
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 3, "Parts listing, Type 7998," on page 235 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.
Symptom
The amount of system memory
displayed is less than the
amount of physical memory
installed.
Action
Disconnect the BladeCenter unit from all electrical sources, wait for 30 seconds,
reconnect the BladeCenter unit to the electrical sources, and restart the blade
server.
If the problem remains, see "Solving undetermined problems" on page 231. Also
view the online information or the Hardware Maintenance Manual and
Troubleshooting Guide or Problem Determination and Service Guide for your
BladeCenter unit.
Action
1. Make sure that:
v All installed memory is recognized in the Display Vital Product Data of
lscfg -vp.
v The memory modules are seated properly.
v You have installed the correct type of memory.
v If you changed the memory, you updated the memory configuration with
the Configuration/Setup Utility program.
v 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).
v If the DIMM was disabled by a system-management interrupt (SMI), replace
the DIMM.
v 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.
197
Chapter 2. Diagnostics
Advertisement
Table of Contents
