IBM 1911, Service Manual

Page: 241 / 268

8. At the firmware splash screen, press F3 when prompted to restore to the
primary bank. The server boots from the primary bank.
Service processor (IMM) error codes
Use this information to view the IMM error log.
The Integrated Management Module (IMM) log contains up to 512 of the most
recent service processor errors, in IPMI format. These messages are a combination
of plain text and error-code numbers. You can view the IMM log from the
Configuration/Setup Utility menu by selecting
Advanced Setup
→
Integrated
Management Module(IMM) Settings
→
IMM System Event Log .
You can view additional information and error codes in plain text by viewing the
Advanced-Management-Module event log in your BladeCenter unit.
Solving SAS hard disk drive problems
Use this information to diagnose and resolve SAS hard disk drive issues.
For any SAS error message, one or more of the following devices might be causing
the problem:
v A failing SAS device (adapter, drive, or controller)
v
An incorrect SAS configuration
For any SAS error message, make sure that the SAS devices are configured
correctly.
Solving shared BladeCenter resource problems
Use this information to diagnose and resolve shared BladeCenter resource issues.
Problems with BladeCenter shared resources might appear to be in the blade
server. The following sections provide procedures to help you isolate blade server
problems from shared BladeCenter resource problems. If the problem is thought to
be with a shared resource, see the
Problem Determination and Service Guide for your
BladeCenter unit and other BladeCenter component documentation for additional
information. If the problem cannot be solved, see “Solving undetermined
problems” on page 232.
To check the general function of shared BladeCenter resources, complete the
following tasks:
v
Make sure that:
– The BladeCenter unit has the required power modules and is connected to a
working power source.
– Power management has been correctly set for your BladeCenter unit
configuration.
v
Determine whether the problem is being experienced with more than one blade
server. Perform a test of the function on a known-good blade server.
v
Try the blade server in a different blade server bay.
v
Try a known-good blade server in the blade server bay.
Chapter 6. Diagnostics
227