This section contains information for trained service technicians.
Inspecting for unsafe conditions
Use the information in this section to help you identify potential unsafe conditions in
an IBM product on which you are working. Each IBM product, as it was designed
and manufactured, has required safety items to protect users and service
technicians from injury. The information in this section addresses only those items.
Use good judgment to identify potential unsafe conditions that might be caused by
non-IBM alterations or attachment of non-IBM features or optional devices that are
not addressed in this section. If you identify an unsafe condition, you must
determine how serious the hazard is and whether you must correct the problem
before you work on the product.
Consider the following conditions and the safety hazards that they present:
v Electrical hazards, especially primary power. Primary voltage on the frame can
cause serious or fatal electrical shock.
v Explosive hazards, such as a damaged CRT face or a bulging capacitor.
v Mechanical hazards, such as loose or missing hardware.
To inspect the product for potential unsafe conditions, complete the following steps:
1. Make sure that the power is off and the power cord is disconnected.
2. Make sure that the exterior cover is not damaged, loose, or broken, and
observe any sharp edges.
3. Check the power cord:
v Make sure that the third-wire ground connector is in good condition. Use a
meter to measure third-wire ground continuity for 0.1 ohm or less between
the external ground pin and the frame ground.
v Make sure that the power cord is the correct type, as specified in Chapter 4,
“Parts listing,” on page 109 and “Power cords” on page 119.
v Make sure that the insulation is not frayed or worn.
4. Remove the cover.
5. Check for any obvious non-IBM alterations. Use good judgment as to the safety
of any non-IBM alterations.
6. Check inside the server for any obvious unsafe conditions, such as metal filings,
contamination, water or other liquid, or signs of fire or smoke damage.
7. Check for worn, frayed, or pinched cables.
8. Make sure that the power-supply cover fasteners (screws or rivets) have not
been removed or tampered with.
Guidelines for servicing electrical equipment
Observe the following guidelines when you service electrical equipment:
v Check the area for electrical hazards such as moist floors, nongrounded power
extension cords, and missing safety grounds.
v Use only approved tools and test equipment. Some hand tools have handles that
are covered with a soft material that does not provide insulation from live
electrical current.
v Regularly inspect and maintain your electrical hand tools for safe operational
condition. Do not use worn or broken tools or testers.
viiiSystem x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 11
v Do not touch the reflective surface of a dental mirror to a live electrical circuit.
The surface is conductive and can cause personal injury or equipment damage if
it touches a live electrical circuit.
v Some rubber floor mats contain small conductive fibers to decrease electrostatic
discharge. Do not use this type of mat to protect yourself from electrical shock.
v Do not work alone under hazardous conditions or near equipment that has
hazardous voltages.
v Locate the emergency power-off (EPO) switch, disconnecting switch, or electrical
outlet so that you can turn off the power quickly in the event of an electrical
accident.
v Disconnect all power before you perform a mechanical inspection, work near
power supplies, or remove or install main units.
v Before you work on the equipment, disconnect the power cord. If you cannot
disconnect the power cord, have the customer power-off the wall box that
supplies power to the equipment and lock the wall box in the off position.
v Never assume that power has been disconnected from a circuit. Check it to
make sure that it has been disconnected.
v If you have to work on equipment that has exposed electrical circuits, observe
the following precautions:
– Make sure that another person who is familiar with the power-off controls is
near you and is available to turn off the power if necessary.
– When you work with powered-on electrical equipment, use only one hand.
Keep the other hand in your pocket or behind your back to avoid creating a
complete circuit that could cause an electrical shock.
– When you use a tester, set the controls correctly and use the approved probe
leads and accessories for that tester.
– Stand on a suitable rubber mat to insulate you from grounds such as metal
floor strips and equipment frames.
v Use extreme care when you measure high voltages.
v To ensure proper grounding of components such as power supplies, pumps,
blowers, fans, and motor generators, do not service these components outside of
their normal operating locations.
v If an electrical accident occurs, use caution, turn off the power, and send another
person to get medical aid.
Safety statements
Important: Each caution and danger statement in this document is labeled with a
number. This number is used to cross reference an English-language
caution or danger statement with translated versions of the caution or
danger statement in the Safety Information document.
For example, if a caution statement is labeled “Statement 1,”
translations for that caution statement are in the Safety Information
document under Statement 1.
Be sure to read all caution and danger statements in this document
before you perform the procedures. Read any additional safety
information that comes with your server or optional device before you
install the device.
Safetyix
Page 12
Statement 1:
DANGER
Electrical current from power, telephone, and communication cables is
hazardous.
To avoid a shock hazard:
v Do not connect or disconnect any cables or perform installation,
maintenance, or reconfiguration of this product during an electrical
storm.
v Connect all power cords to a properly wired and grounded electrical
outlet.
v Connect to properly wired outlets any equipment that will be attached to
this product.
v When possible, use one hand only to connect or disconnect signal
cables.
v Never turn on any equipment when there is evidence of fire, water, or
structural damage.
v Disconnect the attached power cords, telecommunications systems,
networks, and modems before you open the device covers, unless
instructed otherwise in the installation and configuration procedures.
v Connect and disconnect cables as described in the following table when
installing, moving, or opening covers on this product or attached
devices.
To Connect:To Disconnect:
1. Turn everything OFF.
2. First, attach all cables to devices.
3. Attach signal cables to connectors.
4. Attach power cords to outlet.
5. Turn device ON.
1. Turn everything OFF.
2. First, remove power cords from outlet.
3. Remove signal cables from connectors.
4. Remove all cables from devices.
xSystem x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 13
Statement 2:
CAUTION:
When replacing the lithium battery, use only IBM Part Number 33F8354 or an
equivalent type battery recommended by the manufacturer. If your system has
a module containing a lithium battery, replace it only with the same module
type made by the same manufacturer. The battery contains lithium and can
explode if not properly used, handled, or disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Statement 3:
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable
parts inside the device.
v Use of controls or adjustments or performance of procedures other than
those specified herein might result in hazardous radiation exposure.
DANGER
Some laser products contain an embedded Class 3A or Class 3B laser
diode. Note the following.
Laser radiation when open. Do not stare into the beam, do not view directly
with optical instruments, and avoid direct exposure to the beam.
Safetyxi
Page 14
Statement 4:
≥ 18 kg (39.7 lb)≥ 32 kg (70.5 lb)≥ 55 kg (121.2 lb)
CAUTION:
Use safe practices when lifting.
Statement 5:
CAUTION:
The power control button on the device and the power switch on the power
supply do not turn off the electrical current supplied to the device. The device
also might have more than one power cord. To remove all electrical current
from the device, ensure that all power cords are disconnected from the power
source.
12
xiiSystem x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 15
Statement 8:
CAUTION:
Never remove the cover on a power supply or any part that has the following
label attached.
Hazardous voltage, current, and energy levels are present inside any
component that has this label attached. There are no serviceable parts inside
these components. If you suspect a problem with one of these parts, contact
a service technician.
Statement 10:
CAUTION:
Do not place any object on top of rack-mounted devices.
Safetyxiii
Page 16
xivSystem x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 17
Chapter 1. Start here
You can solve many problems without outside assistance by following the
troubleshooting procedures in this Problem Determination and Service Guide and
on the IBM
perform, troubleshooting procedures, and explanations of error messages and error
codes. The documentation that comes with your operating system and software
also contains troubleshooting information.
Diagnosing a problem
Before you contact IBM or an approved warranty service provider, follow these
procedures in the order in which they are presented to diagnose a problem with
your server:
1. Determine what has changed.
Determine whether any of the following items were added, removed, replaced,
or updated before the problem occurred:
v IBM System x
v Device drivers
v Firmware
v Hardware components
v Software
If possible, return the server to the condition it was in before the problem
occurred.
2. Collect data.
Thorough data collection is necessary for diagnosing hardware and software
problems.
a. Document error codes and system-board LEDs.
v System-board LEDs: See “System-board LEDs and controls” on page 13
for information about system-board LEDs.
v System error codes: See “Event logs” on page 25 for information about
a specific error code.
v Software or operating-system error codes: See the documentation for
the software or operating system for information about a specific error
code. See the manufacturer's Web site for documentation.
b. Collect system data.
Run Dynamic System Analysis (DSA) to collect information about the
hardware, firmware, software, and operating system. Have this information
available when you contact IBM or an approved warranty service provider.
See “Diagnostic programs, messages, and error codes” on page 39 for the
instructions to run the DSA program.
If you need to download the latest version of DSA, go to
http://www.ibm.com/systems/support/supportsite.wss/
docdisplay?brandind=5000008&lndocid=SERV-DSA or complete the
following steps.
®
Web site. This document describes the diagnostic tests that you can
®
Server Firmware (formerly called BIOS code)
Note: Changes are made periodically to the IBM Web site. The actual
procedure might vary slightly from what is described in this
document.
3) Under Popular links, click Software and device drivers.
4) Under Related downloads, click Dynamic System Analysis (DSA).
For information about DSA command-line options, go to
http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp?topic=/
com.ibm.xseries.tools.doc/erep_tools_dsa.html or complete the following
steps:
1) Go to http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp.
2) In the navigation pane, click IBM System x and BladeCenter ToolsCenter.
3) Click Tools reference > Error reporting and analysis tools > IBMDynamic System Analysis.
3. Follow the problem-resolution procedures.
The four problem-resolution procedures are presented in the order in which they
are most likely to solve your problem. Follow these procedures in the order in
which they are presented:
a. Check for and apply code updates.
Most problems that appear to be caused by faulty hardware are actually
caused by server firmware, device firmware, or device drivers that are not at
the latest levels.
1) Determine the existing code levels.
In DSA, click Firmware/VPD to view system firmware levels, or click
Software to view operating-system levels.
2) Download and install updates of code that is not at the latest level.
Important: Some cluster solutions require specific code levels or
coordinated code updates. If the device is part of a cluster
solution, verify that the latest level of code is supported for
the cluster solution before you update the code.
To display a list of available updates for your server, go to
http://www.ibm.com/systems/support/supportsite.wss/
docdisplay?brandind=5000008&lndocid=MIGR-4JTS2T or complete the
following steps.
Note: Changes are made periodically to the IBM Web site. The actual
procedure might vary slightly from what is described in this
document.
a) Go to http://www.ibm.com/systems/support/.
b) Under Product support, click System x.
c) Under Popular links, click Software and device drivers.
d) Click System x iDataPlex dx360 M2 server to display the list of
downloadable files for the server.
You can install code updates that are packaged as an UpdateXpress
System Pack or UpdateXpress CD image. An UpdateXpress System
Pack contains an integration-tested bundle of online firmware and
device-driver updates for your server.
Be sure to separately install any listed critical updates that have release
dates that are later than the release date of the UpdateXpress System
Pack or UpdateXpress image.
2System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 19
When you click an update, an information page is displayed, including a
list of the problems that the update fixes. Review this list for your
specific problem; however, even if your problem is not listed, installing
the update might solve the problem.
b. Check for and correct an incorrect configuration.
If the server is incorrectly configured, a system function can fail to work
when you enable it; if you make an incorrect change to the server
configuration, a system function that has been enabled can stop working.
1) Make sure that all installed hardware and software are supported.
If any hardware or software component is not supported, uninstall it to
determine whether it is causing the problem. You must remove
nonsupported hardware before you contact IBM or an approved warranty
service provider for support.
2) Make sure that the server, operating system, and software are
installed and configured correctly.
Many configuration problems are caused by loose power or signal
cables or incorrectly seated adapters. You might be able to solve the
problem by turning off the server, reconnecting cables, reseating
adapters, and turning the server back on. See “Checkout procedures” on
page 27 for the instructions to perform the checkout procedures.
If the problem is associated with a specific function (for example, if a
RAID hard disk drive is marked offline in the RAID array), see the
documentation for the associated controller and management or
controlling software to verify that the controller is correctly configured.
Problem determination information is available for many devices such as
RAID and network adapters.
For problems with operating systems or IBM software or devices,
complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual
procedure might vary slightly from what is described in this
document.
a) Go to http://www.ibm.com/systems/support/.
b) Under Product support, click System x.
c) From the Product family list, select System x iDataPlex dx360 M2
server.
d) Under Support & downloads, click Documentation, Install, and
Use to search for related documentation.
c. Check for troubleshooting procedures and RETAIN tips.
Troubleshooting procedures and RETAIN tips document known problems
and suggested solutions. To search for troubleshooting procedures and
RETAIN tips, complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual
procedure might vary slightly from what is described in this document.
1) Go to http://www.ibm.com/systems/support/.
2) Under Product support, click System x.
3) From the Product family list, select System x iDataPlex dx360 M2server.
4) Under Support & downloads, click Troubleshoot.
Chapter 1. Start here3
Page 20
5) Select the troubleshooting procedure or RETAIN tip that applies to your
problem:
v Troubleshooting procedures are under Diagnostic.
v RETAIN tips are under Troubleshoot.
d. Check for and replace defective hardware.
If a hardware component is not operating within specifications, it can cause
unpredictable results. Most hardware failures are reported as error codes in
a system or operating-system log. See “Troubleshooting tables” on page 31
and Chapter 5, “Removing and replacing server components,” on page 123
for more information. Hardware errors are also indicated by diagnostics
LEDs.
A single problem might cause multiple symptoms. Follow the troubleshooting
procedure for the most obvious symptom. If that procedure does not
diagnose the problem, use the procedure for another symptom, if possible.
If the problem remains, contact IBM or an approved warranty service
provider for assistance with additional problem determination and possible
hardware replacement. To open an online service request, go to
http://www.ibm.com/support/electronic/. Be prepared to provide information
about any error codes and collected data.
Undocumented problems
If you have completed the diagnostic procedure and the problem remains, the
problem might not have been previously identified by IBM. After you have verified
that all code is at the latest level, all hardware and software configurations are valid,
and no diagnostics LEDs or log entries indicate a hardware component failure,
contact IBM or an approved warranty service provider for assistance. To open an
online service request, go to http://www.ibm.com/support/electronic/. Be prepared to
provide information about any error codes and collected data and the problem
determination procedures that you have used.
4System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 21
Chapter 2. Introduction
This Problem Determination and Service Guide contains information to help you
solve problems that might occur in your IBM System x iDataPlex
system-board tray (dx360 M2 Type 6380, 7321, and 7323 system-board tray),
System x iDataPlex 2U Flex Chassis (Type 6313, 6385, and 7831 2U chassis), or
System x iDataPlex 3U Chassis (Type 6386 and 7834 3U chassis). It describes the
diagnostic tools that are available, error codes and suggested actions, and
instructions for replacing failing components.
Replaceable components are of three types:
v Consumable parts: Purchase and replacement of consumable parts
(components, such as batteries and printer cartridges, that have depletable life)
is your responsibility. If IBM acquires or installs a consumable part at your
request, you will be charged for the service.
v Tier 1 customer replaceable unit (CRU): Replacement of Tier 1 CRUs is your
responsibility. If IBM installs a Tier 1 CRU at your request, you will be charged for
the installation.
v Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or
request IBM to install it, at no additional charge, under the type of warranty
service that is designated for your server.
v Field replaceable unit (FRU): FRUs must be installed only by trained service
technicians.
For information about the terms of the warranty and getting service and assistance,
see the Warranty and Support Information document on the IBM Documentation
CD.
™
dx360 M2
Related documentation
In addition to the printed Important Notices document and this document, the
following documentation for the dx360 M2 system-board tray, 2U chassis, and 3U
chassis is provided in Portable Document Format (PDF) on the IBM Documentation
CD:
v Environmental Notices and User's Guide
This document is in PDF on the IBM Documentation CD. It contains translated
environmental notices.
v Safety Information
This document contains translated caution and danger statements. Each caution
and danger statement that appears in the documentation has a number that you
can use to locate the corresponding statement in your language in the SafetyInformation document.
v User’s Guide
This document contains general information about how to use, upgrade, and
configure the dx360 M2 system-board tray, the 2U chassis, the 3U chassis, the
System x iDataPlex I/O enclosure (I/O enclosure), and the System x iDataPlex
Storage enclosure (storage enclosure).
v Warranty and Support Information
This document contains information about the terms of the warranty and getting
service and assistance.
Depending on the hardware configuration, additional documentation might be
included on the IBM Documentation CD.
The iDataPlex documentation might be updated occasionally, or technical updates
might be available to provide additional information that is not included in the
documentation. These updates are available from the IBM Systems Information
Center. To check for updated iDataPlex information and technical updates, go to
http://publib.boulder.ibm.com/infocenter/idataplx/documentation/index.jsp.
The updated iDataPlex documentation also is available from the IBM Support Web
site. To check for updated documentation and technical updates, complete the
following steps.
Note: Changes are made periodically to the IBM Web site. The actual procedure
might vary slightly from what is described in this document.
1. Go to http://www.ibm.com/systems/support/.
2. Under Product support, click System x.
3. Under Popular links, click Publications lookup.
4. From the Product family menu, select System x iDataPlex dx360 M2 server
and click Go.
Notices and statements in this document
The caution and danger statements in this document are also in the multilingual
Safety Information document, which is on the IBM Documentation CD. Each
statement is numbered for reference to the corresponding statement in your
language in the Safety Information document.
The following notices and statements are used in this document:
v Note: These notices provide important tips, guidance, or advice.
v Important: These notices provide information or advice that might help you avoid
inconvenient or problem situations.
v Attention: These notices indicate potential damage to programs, devices, or
data. An attention notice is placed just before the instruction or situation in which
damage might occur.
v Caution: These statements indicate situations that can be potentially hazardous
to you. A caution statement is placed just before the description of a potentially
hazardous procedure step or situation.
v Danger: These statements indicate situations that can be potentially lethal or
extremely hazardous to you. A danger statement is placed just before the
description of a potentially lethal or extremely hazardous procedure step or
situation.
6System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 23
Features and specifications
The following information is a summary of the features and specifications of the
hardware. Depending on the hardware configuration, some features might not be
available, or some specifications might not apply.
Racks are marked in vertical increments of 4.45 cm (1.75 inches). Each increment
is referred to as a unit, or “U.” A 1U-high device is 1.75 inches tall.
Microprocessor: One or two
quad-core Intel Xeon microprocessors
with integrated memory controllers in
each system-board tray
Note: Use the Setup utility to
determine the type and speed of the
microprocessor.
Hard disk drives: The system-board
tray supports one 3.5-inch
simple-swap SAS (with the optional
SAS controller), one 3.5-inch
simple-swap SATA, or two 2.5-inch
simple-swap SATA hard disk drives or
solid-state drives. The system-board
tray with an attached enclosure can
support the following drive
configurations:
v Up to four 3.5-inch simple-swap
SAS hard disk drives with the
storage enclosure and optional
SAS controller
v Up to five 3.5-inch simple-swap
SATA hard disk drives with the
storage enclosure
v Up to four 3.5-inch simple-swap
SATA hard disk drives with up to
two 2.5-inch simple-swap SATA
hard disk drives or solid-state
drives with the storage enclosure
v Up to two 3.5-inch simple-swap
SATA hard disk drives with the I/O
enclosure
v Up to two 3.5-inch simple-swap
SAS hard disk drives with the I/O
enclosure and optional SAS
controller
v Up to eight 2.5-inch hot-swap SAS
hard disk drives with the I/O
enclosure and optional SAS
controller
v Up to twelve 3.5-inch hot-swap
SAS or SATA (with the optional
SAS controller) hard disk drives in
a 3U chassis
Memory:
v Sixteen DIMM connectors (eight
per microprocessor)
v Minimum: Two DIMMs per
microprocessor
v Maximum: 64 GB (as of the date
of this publication)
v Type: Registered ECC
double-data-rate 3 (DDR3) -800,
-1066, and -1333 MHz DIMMs
only
v Sizes: 1 GB single-rank, 2 GB
dual-rank, and 4 GB dual-rank
v Chipkill supported with selected
DIMMs
Integrated functions:
v Integrated management module
(IMM), which provides service
processor control and monitoring
functions, video controller, and
(when the optional virtual media
key is installed) remote keyboard,
video, mouse, and remote hard
disk drive capabilities
v Dedicated or shared management
network connections
v Six Serial ATA (SATA) ports
v Serial over LAN (SOL) and serial
redirection over Telnet or Secure
Shell (SSH)
v Dual-port Gigabit Ethernet
controller
v Front connectors for USB 2.0 (2
ports), serial, video, and RJ-45 (3
ports)
– One systems-management
RJ-45 port for connection to a
dedicated systemsmanagement network
– Two RJ-45 LAN ports
Predictive Failure Analysis (PFA)
alerts:
v Memory
v Hard disk drives
Expansion slots: Up to two PCI
Express slots total. Support for the
following riser cards:
v One PCI Express x16 slot (x16)
v Two PCI Express x16 slots (x8)
v One PCI Express x8 slot (x8)
supports an optional RAID controller
only (some configurations)
Environment:
v Air temperature:
– Server on: 10°C to 35°C (50°F to
95°F); altitude: 0 to 914.4 m (0 to
3000 ft). Derate maximum
temperature by 1°C for every
304.8 m (1000 ft) increase in
elevation to a maximum of 3048.0
m (10000 ft) at an ambient
temperature of 28°C
– Server off: 10°C to 43°C (59°F to
109.4°F); maximum altitude: 2133
m (7000 ft)
v Humidity:
– Server on: 10% to 80%
– Server off: 8% to 80%
Size:
v Height:
– 2U chassis: 8.6 cm (3.39 inches)
– 3U chassis: 13.0 cm (5.1 inches)
v Depth: 51.3 cm (20.2 inches)
v Width: 44.6 cm (17.6 inches)
v Weight:
– 2U chassis:
- Fully loaded: 22.7 kg (46.1 lb)
- Without system-board trays:
7.1 kg (15.6 lb)
– 3U chassis:
- Fully loaded: 28.1 kg (62.0 lb)
- Without hard disk drives: 15.4
kg (34.0 lb)
Electrical Input:
v Input voltage low range: 100 V ac
(minimum) to 127 V ac (maximum),
sine-wave input (50 - 60 Hz)
v Input voltage high range: 200 V ac
(minimum) to 240 V ac (maximum),
sine-wave input (50 - 60 Hz)
Chapter 2. Introduction7
Page 24
Operator panel controls, connectors, and LEDs
This section describes the controls, connectors, and light-emitting diodes (LEDs)
and how to turn the system-board tray on and off.
Front view
The following illustration shows the controls, connectors, and LEDs on the front of
the server. The operator panel on the system-board tray is the same for all server
configurations.
Power-control button: Press this button to turn the system-board tray on and off
manually or to wake the system-board tray from a reduced-power state. Note that
the power-control button is recessed to prevent the system-board tray from being
turned on or off accidentally. There is a power-control button cover that can be
removed for easier access to the power-control button.
USB connectors: Connect USB 2.0 devices to these connectors.
Ethernet link activity/status LED: This LED is on each Ethernet connector. When
this LED is lit, it indicates that there is an active connection on the Ethernet port.
When this LED is flashing, it indicates that there is activity between the server and
the network.
Ethernet connectors: Use these connectors to connect the server to a network.
Ethernet connection speed LED: This LED is on each Ethernet connector. The
status of this LED indicates the connection speed, in megabits-per-second (Mbps),
between the server and the network as follows:
v LED off: 10 Mbps connection
v LED lit amber: 100 Mbps connection
v LED lit green: 1000 Mbps connection
Systems-management Ethernet connector: Use this connector to connect the
server to a network for systems-management information control.
Video connector: Connect a monitor to this connector.
Serial connector: Connect a 9-pin serial device to this connector. The serial port is
shared with the integrated management module (IMM). The IMM can take control of
the shared serial port to perform text console redirection and to redirect serial
traffic, using Serial over LAN (SOL).
System-error LED: When this LED is lit, it indicates that a system error has
occurred. The source of the error is logged in the system-event log that is accessed
in the Setup utility.
8System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 25
Locator LED: This LED can be lit remotely by the system administrator to aid in
visually locating the system-board tray. In an IPMI environment, the system
administrator can light the LED by using the IPMI chassis identify command.
Hard disk drive activity LED: When this LED is lit or flashing, it indicates that an
associated hard disk drive is in use.
In configurations that contain hot-swap hard disk drives, each hot-swap hard disk
drive has the following LEDs.
v Hot-swap hard disk drive activity LED: When this LED is flashing, it indicates
that the drive is in use.
v Hot-swap hard disk drive status LED: When this LED is lit, it indicates that the
drive has failed.
Power-on LED: The states of the power-on LED are as follows:
v Off: AC power is not present, or the power supply or the LED itself has failed.
v Flashing rapidly (4 times per second): The system-board tray is turned off and
is not ready to be turned on. The power-control button is disabled.
v Flashing slowly (once per second): The system-board tray is turned off and is
ready to be turned on. You can press the power-control button to turn on the
system-board tray.
v Lit: The system-board tray is turned on.
v Fading on and off: The system-board tray is in a reduced-power state. To wake
the system-board tray, press the power-control button or use the IMM Web
interface.
Rear view
Note: If this LED is off, it does not mean that no electrical power is present. The
LED might be burned out. To remove all electrical power, you must remove
the system-board tray from the chassis, remove the chassis from the rack, or
disconnect the power cord from the power source.
The following illustration shows the connector on the rear of the 2U chassis. The 3U
chassis is similar.
Power-cord connector: Connect the power cord to this connector. When the
chassis is installed in an iDataPlex rack, it is automatically connected to power
through a power cord that is mounted to the rack rail.
Chapter 2. Introduction9
Page 26
Turning on the system-board tray
After you install the system-board tray in a chassis, the system-board tray can start
in any of the following ways:
Important: To avoid potential problems during startup, disconnect any USB flash
drives from the system that contain the Smart Launch Utility before you
turn on the system-board tray.
v You can press the power-control button on the front of the system-board tray
(see “Operator panel controls, connectors, and LEDs” on page 8) to start the
system-board tray.
v In an IPMI environment, the system administrator can turn on the system-board
tray by using the IPMI chassis control command.
v If a power failure occurs, the system-board tray can start automatically when
power is restored, if it is configured to do so.
Turning off the system-board tray
When you turn off the system-board tray, it is still connected to ac power through
the chassis power supply. The system-board tray still can respond to requests from
the IMM, such as a remote request to turn on the system-board tray. To remove all
power from the system-board tray, you must remove the tray from the chassis.
Shut down the operating system before you turn off the system-board tray. See the
operating-system documentation for information about shutting down the operating
system.
The system-board tray can be turned off in any of the following ways:
v You can press the power-control button on the front of the system-board tray
(see “Operator panel controls, connectors, and LEDs” on page 8). This starts an
orderly shutdown of the operating system, if this feature is supported by the
operating system.
v You can turn off the system-board tray from the operating system, if the operating
system supports this feature. After an orderly shutdown of the operating system,
the system-board tray will be turned off automatically.
v In an IPMI environment, the system administrator can turn off the system-board
tray by using the IPMI chassis control command.
v If the operating system stops functioning, you can press and hold the
power-control button for more than 4 seconds to turn off the system-board tray.
v You might be able to turn off the system-board tray by using an optional
management appliance.
– If the system is not operating correctly, the management appliance might
automatically turn off the system-board tray.
– Through the management appliance control interface, you might also be able
to configure the management appliance to turn off the system-board tray. For
additional information, see the documentation for your management appliance.
System-board layouts
The following illustrations show the connectors, jumpers, and LEDs on the system
board.
Note: The illustrations in this document might differ slightly from your hardware.
10System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 27
System-board connectors
The following illustration shows the connectors on the system board.
Chapter 2. Introduction11
Page 28
System-board jumpers
The following illustration shows the locations of the jumpers on the system board.
The following table defines the function of each jumper on the system board.
JumperDescription
Clear CMOS (JP1)
UEFI boot recovery (JP2)
v Pins 1 and 2: Normal (default)
v Pins 2 and 3: Clear the CMOS data
v Pins 1 and 2: Normal (default)
v Pins 2 and 3: Use the secondary page during
startup
12System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 29
System-board LEDs and controls
Note: Any error LED can be lit after ac power has been removed from the
system-board tray so that you can isolate a problem. After ac power has
been removed from the system-board tray, power remains available to these
LEDs for up to 90 seconds. To view the error LEDs, press and hold the
reminder button on the system board to light the error LEDs. The error LEDs
that were lit while the system-board tray was running will be lit again while
the button is pressed.
The following illustration shows the locations of the LEDs and controls on the
system board.
LED nameDescription
Error LEDsWhen an error LED is lit, it indicates that the associated
component has failed.
H8 heartbeatWhen this LED is flashing, it indicates that the power
management controller is functioning normally.
Chapter 2. Introduction13
Page 30
LED nameDescription
IMM heartbeatWhen this LED is flashing at a constant rate of every other
second, it indicates normal operation of the IMM controller. When
this LED is flashing at a constant rate of every other half-second,
it indicates that the IMM controller is initializing or is not
functional.
Microprocessor
mismatch
Standby powerWhen this LED is lit, it indicates that the server is connected to
When this LED is lit, it indicates that microprocessor 1 is not
installed, or the microprocessors do not have the same cache
size and type, and clock speed.
an ac power source and that the power supply has supplied the
5–volt standby voltage to the system board.
14System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 31
Chapter 3. Diagnostics
This section describes the diagnostic tools that are available to help you solve
problems that might occur in the system-board tray and chassis.
To update the firmware, you might have to use an external USB CD-RW/DVD drive
such as the IBM and Lenovo part number 73P4515 or 73P4516. To run the Setup
utility or the Dynamic System Analysis (DSA) Preboot, you must have the following
additional hardware:
v Monitor
v Combination USB keyboard and pointing device such as IBM part number
40K5372
Optionally, to run the DSA Preboot, you can use a USB flash drive (memory key).
If you cannot diagnose and correct a problem by using the information in this
section, see Appendix A, “Getting help and technical assistance,” on page 233 for
more information.
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related
problems:
v POST error messages, and event logs
The power-on self-test (POST) generates messages to indicate the detection of a
problem. See “POST” on page 16 for more information.
v Checkout procedures
Checkout procedures are available to help you diagnose server problems. The
basic checkout procedure is designed for anyone to use. The advanced checkout
procedure is intended for trained service technicians only. See “Checkout
procedures” on page 27 for more information.
v Troubleshooting tables
These tables list problem symptoms and actions to correct the problems. See
“Troubleshooting tables” on page 31 for more information.
v Dynamic System Analysis (DSA) Preboot diagnostic programs
The DSA Preboot diagnostic programs collect and analyze system information to
aid in diagnosing problems. The diagnostic programs collect the following
information:
– System configuration
– Network interfaces and settings
– Installed hardware
– Service processor status and configuration
– Vital product data, firmware, and server firmware configuration
– Hard disk drive health
– RAID controller configuration
– Event logs for RAID controllers and the IMM
The diagnostic programs create a merged log that includes events from all
collected logs. The information is collected into a file that you can send to IBM
service and support. Additionally, you can view the server information locally
through a generated text report file. You can also copy the log to removable
media and view the log from a Web browser.
POST
When you turn on the system-board tray, it performs a series of tests to check the
operation of the components and some optional devices in the chassis. This series
of tests is called the power-on self-test, or POST.
If the system-board tray is configured to require entry of a password to complete
the system startup, you need to type both the administrator password and power-on
password to complete the system startup, if either password is set.
If POST detects a problem, an error message is displayed. See “POST error
messages” for more information.
POST error messages
The following table describes the POST error messages and suggested actions to
correct the detected problems.
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0010002Microprocessor not supported
0011000Invalid microprocessor type
1. Reseat the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. (Trained service technician only) Microprocessor 1
b. (Trained service technician only) Microprocessor 2 (if
installed)
2. (Trained service technician only) Remove microprocessor
2 and restart the system-board tray.
3. (Trained service technician only) Remove microprocessor
1 and install microprocessor 2 in the microprocessor 1
connector. Restart the system-board tray. If the error is
corrected, microprocessor 1 is bad and must be replaced.
4. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. (Trained service technician only) Microprocessor 1
b. (Trained service technician only) Microprocessor 2
c. (Trained service technician only) System board
1. Update the system firmware (see “Firmware updates” on
page 213).
2. (Trained service technician only) Remove and replace the
affected microprocessor (error LED is lit) with a supported
type.
16System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 33
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0011002Microprocessor mismatch
1. Run the Setup utility and view the microprocessor
information to compare the installed microprocessor
specifications.
2. (Trained service technician only) Remove and replace
one of the microprocessors so that they both match.
0011004Microprocessor failed BIST
1. Update the system firmware (see “Firmware updates” on
page 213).
2. (Trained service technician only) Reseat microprocessor
2.
3. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. (Trained service technician only) Microprocessor
b. (Trained service technician only) System board
001100AMicrocode update failed
1. Update the system firmware (see “Firmware updates” on
page 213).
2. (Trained service technician only) Replace the
microprocessor.
0050001DIMM disabledNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Make sure the DIMM is installed correctly (see “Installing
a memory module” on page 164).
2. If the DIMM was disabled because of a memory fault,
follow the suggested actions for that error event and
restart the server.
3. Check the IBM support website for an applicable retain tip
or firmware update that applies to this memory event. If
no memory fault is recorded in the logs and no DIMM
connector error LED is lit, you can re-enable the DIMM
through the Setup utility or the Advanced Settings Utility
(ASU).
Chapter 3. Diagnostics17
Page 34
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0051003Uncorrectable DIMM errorNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Check the IBM support website for an applicable retain tip
or firmware update that applies to this memory error.
2. Manually re-enable all affected DIMMs if the server
firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and
reconnect the server to the power source and restart the
server.
3. If the problem remains, replace the failing DIMM (see
“Removing a memory module” on page 163 and
“Installing a memory module” on page 164).
4. (Trained service technician only) If the problem occurs on
the same DIMM connector, check the DIMM connector. If
the connector contains any foreign material or is
damaged, replace the system-board tray (see “Removing
the system-board tray” on page 208 and “Installing the
system-board tray” on page 210).
5. (Trained service technician only) Remove the affected
microprocessor and check the microprocessor socket pins
for any damaged pins. If a damage is found, replace the
system-board tray (see “Removing the system-board tray”
on page 208 and “Installing the system-board tray” on
page 210).
6. (Trained Service technician only) Replace the affected
microprocessor (see “Removing a microprocessor and
heat sink” on page 197 and “Installing a microprocessor
and heat sink” on page 199).
0051006DIMM mismatch detectedNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
Make sure that the DIMMs match and are installed in the
correct sequence (see “Installing a memory module” on page
164).
18System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 35
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0051009No memory detectedNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Make sure one or more DIMMs are installed in the server.
2. Reseat the DIMMs and restart the server (see “Removing
a memory module” on page 163 and “Installing a memory
module” on page 164).
3. Make sure that the DIMMs match and are installed in the
correct sequence (see “Installing a memory module” on
page 164).
4. (Trained service technician only) Replace the
microprocessor that controls the failing DIMMs (see
“Removing a microprocessor and heat sink” on page 197
and “Installing a microprocessor and heat sink” on page
199).
5. (Trained service technician only) Replace the
system-board tray (see “Removing the system-board tray”
on page 208 and “Installing the system-board tray” on
page 210).
005100ANo usable memory detectedNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Make sure one or more DIMMs are installed in the server.
2. Reseat the DIMMs and restart the server (see “Removing
a memory module” on page 163 and “Installing a memory
module” on page 164).
3. Make sure that the DIMMs match and are installed in the
correct sequence (see “Installing a memory module” on
page 164).
4. Clear CMOS memory to ensure that all DIMM connectors
are enabled (see “Removing the battery” on page 137
and “Installing the battery” on page 138). Note that all
firmware settings will be reset to the default settings.
Chapter 3. Diagnostics19
Page 36
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0058001PFA threshold exceededNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Check the IBM support website for an applicable retain tip
or firmware update that applies to this memory error.
2. Swap the affected DIMMs (as indicated by the error LEDs
on the system board or the event logs) to a different
memory channel or microprocessor (see “Installing a
memory module” on page 164).
3. If the error still occurs on the same DIMM, replace the
affected DIMM.
4. (Trained service technician only) If the problem occurs on
the same DIMM connector, check the DIMM connector. If
the connector contains any foreign material or is
damaged, replace the system-board tray (see “Removing
the system-board tray” on page 208 and “Installing the
system-board tray” on page 210).
5. (Trained service technician only) Remove the affected
microprocessor and check the microprocessor socket pins
for any damaged pins. If a damage is found, replace the
system-board tray (see “Removing the system-board tray”
on page 208 and “Installing the system-board tray” on
page 210).
6. (Trained Service technician only) Replace the affected
microprocessor (see “Removing a microprocessor and
heat sink” on page 197 and “Installing a microprocessor
and heat sink” on page 199).
0058007DIMM population is unsupportedNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Reseat the DIMMs and restart the server (see “Removing
a memory module” on page 163 and “Installing a memory
module” on page 164).
2. Make sure that the DIMMs are installed in the proper
sequence (see “Installing a memory module” on page
164).
20System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 37
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
0058008DIMM failed memory testNote: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. Check the IBM support website for an applicable retain tip
or firmware update that applies to this memory error.
2. Manually re-enable all affected DIMMs if the server
firmware version is older than UEFI v1.10. If the server
firmware version is UEFI v1.10 or newer, disconnect and
reconnect the server to the power source and restart the
server.
3. Swap the affected DIMMs (as indicated by the error LEDs
on the system board or the event logs) to a different
memory channel or microprocessor (see “Installing a
memory module” on page 164 for memory population).
4. If the problem is related to a DIMM, replace the failing
DIMM (see “Removing a memory module” on page 163
and “Installing a memory module” on page 164).
5. (Trained service technician only) If the problem occurs on
the same DIMM connector, check the DIMM connector. If
the connector contains any foreign material or is
damaged, replace the system-board tray (see “Removing
the system-board tray” on page 208 and “Installing the
system-board tray” on page 210).
6. (Trained service technician only) Remove the affected
microprocessor and check the microprocessor socket pins
for any damaged pins. If a damage is found, replace the
system-board tray (see “Removing the system-board tray”
on page 208 and “Installing the system-board tray” on
page 210).
7. (Trained service technician only) If the problem is related
to microprocessor socket pins, replace the system-board
tray (see “Removing the system-board tray” on page 208
and “Installing the system-board tray” on page 210).
8. (Trained Service technician only) Replace the affected
microprocessor (see “Removing a microprocessor and
heat sink” on page 197 and “Installing a microprocessor
and heat sink” on page 199).
00580A1Invalid DIMM population for mirroring
mode
Note: Each time you install or remove a DIMM, you must
disconnect the server from the power source; then, wait 10
seconds before restarting the server.
1. If a fault LED is lit, resolve the failure.
2. Install the DIMMs in the correct sequence (see “Installing
a memory module” on page 164).
00580A4Memory population changedInformation only. Memory has been added, moved, or
changed.
Chapter 3. Diagnostics21
Page 38
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
00580A5Mirror failover completeInformation only. Memory redundancy has been lost. Check
the event log for uncorrected DIMM failure events (See
“Event logs” on page 25 for more information).
0068002CMOS battery cleared
2011000PCI-X PERR
2011001PCI-X SERR
2018001PCI Express uncorrected or
uncorrected error
1. Reseat the battery.
2. Clear the CMOS memory (see “Clearing CMOS memory”
on page 77).
3. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Battery
b. (Trained service technician only) System board
1. Check the riser-card LEDs.
2. Reseat all affected adapters and riser cards.
3. Update the PCI device firmware.
4. Remove both adapters from the riser card.
5. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Riser card
b. (Trained service technician only) System board
1. Check the riser-card LEDs.
2. Reseat all affected adapters and riser cards.
3. Update the PCI device firmware.
4. Remove both adapters from the riser card.
5. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Riser card
b. (Trained service technician only) System board
1. Check the riser-card LEDs.
2. Reseat all affected adapters and riser cards.
3. Update the PCI device firmware.
4. Remove both adapters from the riser card.
5. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Riser card
b. (Trained service technician only) System board
22System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 39
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
2018002Option ROM resource allocation
failure
Informational message that some devices might not be
initialized.
1. If possible, rearrange the order of the adapters in the PCI
slots to change the load order of the optional-device ROM
code.
2. Run the Setup utility, select Start Options, and change
the boot priority to change the load order of the
optional-device ROM code.
3. Run the Setup utility and disable some other resources, if
their functions are not being used, to make more space
available:
v Select Start Options and Planar Ethernet
(PXE/DHCP) to disable the integrated Ethernet
controller ROM.
v Select Advanced Functions, then PCI Bus Control,
then PCI ROM Control Execution to disable the ROM
of adapters in the PCI slots.
v Select Devices and I/O Ports to disable any of the
integrated devices.
4. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Each adapter
b. (Trained service technician only) System board
3xx0007 (xx
can be 00 -
19)
Firmware fault detected, system
halted
1. Recover the server firmware to the latest level.
2. Undo any recent configuration changes, or clear CMOS
memory to restore the settings to the default values.
3. Remove any recently installed hardware.
3038003Firmware corrupted
1. Run the Setup utility, select Load Default Settings, and
save the settings to recover the server firmware.
2. (Trained service technician only) Replace the system
board.
3048005Booted secondary (backup) UEFI
image
3048006Booted secondary (backup) UEFI
image because of ABR
Information only. The backup switch was used to boot the
secondary bank.
1. Run the Setup utility, select Load Default Settings, and
save the settings to recover the primary UEFI settings.
2. Turn off the system-board tray and remove it from the
power source.
3. Reconnect the system-board tray to the power source,
and then turn on the system-board tray.
Chapter 3. Diagnostics23
Page 40
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
305000ARTC date/time is incorrect
3058001System configuration invalid
3058004Three boot failures
3108007System configuration restored to
default settings
3138002Boot configuration error
3808000IMM communication failure
1. Adjust the date and time settings in the Setup utility, and
then restart the system-board tray.
2. Reseat the battery.
3. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Battery
b. (Trained service technician only) System board
1. Run the Setup utility, and select Save Settings.
2. Run the Setup utility, select Load Default Settings, and
save the settings.
3. Reseat the following components one at a time in the
order shown, restarting the system-board tray each time:
a. Battery
b. Failing device (if the device is a FRU, then it must be
reseated by a trained service technician only)
4. Replace the following components one at a time, in the
order shown, restarting the system-board tray each time:
a. Battery
b. Failing device (if the device is a FRU, then it must be
replaced by a trained service technician only)
c. (Trained service technician only) System board
1. Undo any recent system changes, such as new settings
or newly installed devices.
2. Make sure that the system-board tray is attached to a
reliable power source.
3. Make sure that the operating system is not corrupted.
4. Run the Setup utility, save the configuration, and then
restart the system-board tray.
5. See “Problem determination tips” on page 108.
Information only. This is message is usually associated with
the CMOS battery clear event.
1. Remove any recent configuration changes that you made
in the Setup utility.
2. Run the Setup utility, select Load Default Settings, and
save the settings.
1. Remove power from the system-board tray for 30
seconds, and then reconnect the system-board tray to
power and restart it.
2. Update the IMM firmware.
3. Make sure that the IMM key is seated and not damaged.
4. (Trained service technician only) Replace the system
board.
24System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 41
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Error codeDescriptionAction
3808002Error updating system configuration
to IMM
3808003Error retrieving system configuration
from IMM
3808004IMM system event log full
3828004AEM power capping disabled
1. Remove power from the system-board tray, and then
reconnect the system-board tray to power and restart it.
2. Run the Setup utility and select Save Settings.
3. Update the firmware.
1. Remove power from the system-board tray, and then
reconnect the system-board tray to power and restart it.
2. Run the Setup utility and select Save Settings.
3. Update the IMM firmware.
v When out-of-band, use the IMM Web interface or IPMItool
to clear the logs from the operating system.
v When using the local console:
1. Run the Setup utility.
2. Select System Event Log.
3. Select Clear System Event Log.
4. Restart the system-board tray.
1. Check the settings and the event logs.
2. Make sure that the Active Energy Manager feature is
enabled in the Setup utility. Select System Settings,
Power, Active Energy, and Capping Enabled.
3. Update the system-board tray firmware.
4. Update the IMM firmware.
Event logs
Error codes and messages are displayed in the following types of event logs:
v POST event log: This log contains the three most recent error codes and
messages that were generated during POST. You can view the POST event log
through the Setup utility.
v System-event log: This log contains POST and system management interrupt
(SMI) events and all events that are generated by the BMC that is embedded in
the IMM. You can view the system-event log through the Setup utility and through
the Dynamic System Analysis (DSA) program (as the IPMI event log).
The system-event log is limited in size. When it is full, new entries will not
overwrite existing entries; therefore, you must periodically save and then clear
the system-event log through the Setup utility. When you are troubleshooting, you
might have to save and then clear the system-event log to make the most recent
events available for analysis.
Messages are listed on the left side of the screen, and details about the selected
message are displayed on the right side of the screen. To move from one entry
to the next, use the Up Arrow (↑) and Down Arrow (↓) keys.
Chapter 3. Diagnostics25
Page 42
Some IMM sensors cause assertion events to be logged when their setpoints are
reached. When a setpoint condition no longer exists, a corresponding
deassertion event is logged. However, not all events are assertion-type events.
v Integrated management module (IMM) event log: This log contains a filtered
subset of all IMM, POST, and system management interrupt (SMI) events. You
can view the IMM event log through the IMM Web interface and through the
Dynamic System Analysis (DSA) program (as the ASM event log).
v DSA log: This log is generated by the Dynamic System Analysis (DSA) program,
and it is a chronologically ordered merge of the system-event log (as the IPMI
event log), the IMM chassis-event log (as the ASM event log), and the
operating-system event logs. You can view the DSA log through the DSA
program.
Viewing event logs through the Setup utility
To view the POST event log or system-event log, complete the following steps:
1. Turn on the server.
2. When the prompt <F1> Setup is displayed, press F1. If you have set both a
power-on password and an administrator password, you must type the
administrator password to view the event logs.
3. Select System Event Logs and use one of the following procedures:
v To view the POST event log, select POST Event Viewer.
v To view the system-event log, select System Event Log.
Viewing event logs without restarting the server
If the server is not hung, methods are available for you to view one or more event
logs without having to restart the server.
If you have installed Portable or Installable Dynamic System Analysis (DSA), you
can use it to view the system-event log (as the IPMI event log), the IMM event log
(as the ASM event log), the operating-system event logs, or the merged DSA log.
You can also use DSA Preboot to view these logs, although you must restart the
server to use DSA Preboot. To install Portable DSA, Installable DSA, or DSA
Preboot or to download a DSA Preboot CD image, go to http://www.ibm.com/
systems/support/supportsite.wss/docdisplay?lndocid=SERV-DSA
&brandind=5000008 or complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual procedure
might vary slightly from what is described in this document.
1. Go to http://www.ibm.com/systems/support/.
2. Under Product support, click System x.
3. Under Popular links, click Software and device drivers.
4. Under Related downloads, click Dynamic System Analysis (DSA) to display
the matrix of downloadable DSA files.
If IPMItool is installed in the server, you can use it to view the system-event log.
Most recent versions of the Linux operating system come with a current version of
IPMItool. For information about IPMItool, see http://publib.boulder.ibm.com/
infocenter/toolsctr/v1r0/index.jsp?topic=/com.ibm.xseries.tools.doc/
config_tools_ipmitool.html or complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual procedure
might vary slightly from what is described in this document.
1. Go to http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/index.jsp.
26System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 43
2. In the navigation pane, click IBM System x and BladeCenter Tools Center.
For an overview of IPMI, go to http://publib.boulder.ibm.com/infocenter/systems/
index.jsp?topic=/liaai/ipmi/liaaiipmi.htm or complete the following steps:
1. Go to http://publib.boulder.ibm.com/infocenter/systems/index.jsp.
2. In the navigation pane, click IBM Systems Information Center.
3. Expand Operating systems, expand Linux information, expand Blueprints
for Linux on IBM systems, and click Using Intelligent Platform Management
Interface (IPMI) on IBM Linux platforms.
You can view the IMM event log through the Event Log link in the IMM Web
interface.
The following table describes the methods that you can use to view the event logs,
depending on the condition of the server. The first two conditions generally do not
require that you restart the server.
Table 1. Methods for viewing event logs
ConditionAction
The server is not hung and is connected to a
network.
The server is not hung and is not connected
to a network.
The server is hung.
Use any of the following methods:
v Run Portable or Installable DSA to view
the event logs or create an output file that
you can send to IBM service and support.
v In a Web browser, type the IP address of
the IMM and go to the Event Log page.
v Use IPMItool to view the system-event log.
Use IPMItool locally to view the system-event
log.
v If DSA Preboot is installed, restart the
server and press F2 to start DSA Preboot
and view the event logs.
v If DSA Preboot is not installed, insert the
DSA Preboot CD and restart the server to
start DSA Preboot and view the event
logs.
v Alternatively, you can restart the server
and press F1 to start the Setup utility and
view the POST event log or system-event
log. For more information, see “Viewing
event logs through the Setup utility” on
page 26.
Checkout procedures
The checkout procedures are the sequence of tasks that you should follow to
diagnose a problem. The basic checkout procedure is designed for anyone to use.
The advanced checkout procedure is intended for trained service technicians only.
About the checkout procedures
Before you perform either the basic checkout procedure or the advanced checkout
procedure for diagnosing hardware problems, review the following information:
Chapter 3. Diagnostics27
Page 44
v Read the safety information that begins on page vii.
v The diagnostic programs provide the primary methods of testing the major
components. If you are not sure whether a problem is caused by the hardware or
by the software, you can use the diagnostic programs to confirm that the
hardware is working correctly.
v When you run the diagnostic programs, a single problem might cause more than
one error message. When this happens, correct the cause of the first error
message. The other error messages usually will not occur the next time you run
the diagnostic programs.
Exception: If multiple error codes indicate a microprocessor error, the error
might be in a microprocessor or in a microprocessor socket. See
“Microprocessor problems” on page 35 for information about
diagnosing microprocessor problems.
v Before you run the diagnostic programs, you must determine whether the failing
system-board tray is part of a shared hard disk drive cluster (two or more
system-board trays that share external storage devices). If it is part of a cluster,
you can run all diagnostic programs except the ones that test the storage unit
(that is, a hard disk drive in the storage unit) or the storage adapter that is
attached to the storage unit. The failing system-board tray might be part of a
cluster if any of the following conditions are true:
– You have identified the failing system-board tray as part of a cluster (two or
more system-board trays that share external storage devices).
– One or more external storage units are attached to the failing system-board
tray and at least one of the attached storage units is also attached to another
server or unidentifiable device.
Important: If the system-board tray is part of a shared hard disk drive cluster,
run one test at a time. Do not run any suite of tests, such as “quick”
or “normal” tests, because this might enable the hard disk drive
diagnostic tests.
v If the system-board tray is halted and a POST error code is displayed, see
“POST error messages” on page 16. If the system-board tray is halted and no
error message is displayed, see “Troubleshooting tables” on page 31 and
“Solving undetermined problems” on page 106.
v For information about power-supply problems, see “Power problems” on page 37.
v For intermittent problems, check the event log; see “Event logs” on page 25 and
“Diagnostic programs, messages, and error codes” on page 39.
Performing the basic checkout procedure
To perform the basic checkout procedure, complete the following steps:
1. Is the system-board tray part of a cluster?
v Yes: Shut down all failing system-board trays that are related to the cluster.
Go to step 2.
v No: Go to step 2.
2. Complete the following steps:
a. If the system-board tray is running, turn off the system-board tray.
b. Check all installed devices for compatibility.
c. Turn on the system-board tray. If the system-board tray does not start, see
“Troubleshooting tables” on page 31.
28System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 45
d. Record any POST error messages that are displayed on the monitor. If an
error is displayed, look up the first error in “POST error messages” on page
16.
e. Check the system-error LED on the system-board tray operator panel. If it is
lit, check the system-event log.
Important: If the system-error LED on the front of the system-board tray is
lit but there are no error indications, clear the system-event log.
This log does not clear itself, and if it begins to fill up, the
system-error LED will be lit. Also, after you complete a repair or
correct all conditions in the system-event log, clear the
system-event log to turn off the system-error LED.
f. Check for the successful completion of startup, indicated by a readable
display of the operating-system desktop.
3. Are there readable instructions on the main menu?
v Yes: Run the diagnostic programs (see “Running the diagnostic programs” on
page 40).
– If you receive an error, see “Diagnostic error codes” on page 41.
– If the diagnostic programs were completed successfully and you still
suspect a problem, see “Solving undetermined problems” on page 106.
v No: Find the failure symptom in “Troubleshooting tables” on page 31; if
necessary, see “Solving undetermined problems” on page 106.
Important: Clear the system-event log and the POST event log after you correct all
conditions. This will turn off the system-error LED, if all conditions are
corrected.
Performing the advanced checkout procedure
This section contains information for trained service technicians.
The no-POST no-video environment occurs when the server does not complete
POST and there is no output to the monitor during boot. To perform the no-POST
no-video troubleshooting procedure, complete the following steps:
1. Search the Retain tips for a known solution that will correct the problem. Did a
Retain tip correct the issue?
v Yes: The problem is solved.
v No: Go to step 2.
2. Check the standby power. Are any system LEDs lit or flashing?
v Yes: See “System-board LEDs and controls” on page 13 to locate the
system LEDs and to continue troubleshooting.
v No: Go to step 3.
3. Verify that the power supply is receiving power. Is the power properly turned
on and are the power-supply fans working?
v Yes: Go to step 4.
v No: Go to step 5 on page 30.
4. Remove the system-board tray from the chassis and apply power to the
system. Is the fan on the power supply working?
v Yes: (Trained service technician only) Replace the system-board tray.
v No: Replace the power supply.
Chapter 3. Diagnostics29
Page 46
5. Determine whether power is being applied to the system-board tray. Press the
power-control button to turn on the system. Are the system fans working?
v Yes: Go to step 7.
v No: Complete the following tasks:
a. Remove the chassis.
b. Remove the chassis top cover.
c. Reseat the fan packs on the power supply.
d. Reseat the chassis in the rack.
e. Go to step 6.
6. Is the amber LED on the power supply lit?
v Yes: Replace the power supply.
v No: (Trained service technician only) If the amber LED on the power supply
is not lit, reseat the system-board tray.
7. Reseat all of the system board components, including the following
components:
v Cables
v DIMMs
v Optional adapters
v Video adapter
Go to step 8.
8. Turn the system on. Does the system boot and display output to the monitor?
v Yes: One of the components was loose. The problem is solved.
v No: Go to step 9.
9. Configure the system to the minimum hardware requirements as listed in
“Solving undetermined problems” on page 106; then, turn on the system. Does
the system boot and display output to the monitor?
v Yes: The problem was caused by one or more of the components that were
removed. Reinstall each device one at a time to isolate the failing
component; then, replace the component.
v No: Go to step 10.
10. Test POST by completing the following steps:
a. Clear CMOS memory by using the procedure listed in “Clearing CMOS
memory” on page 77.
b. Turn on the system.
c. Does the system boot and display output to the monitor?
v Yes: Go to step 11.
v No: See the “Solving undetermined problems” on page 106 to continue
troubleshooting.
11. Recover the server firmware:
a. Use the server firmware recovery procedure listed in “Starting the backup
server firmware” on page 219.
b. Turn on the system.
c. Does the system boot and display output to the monitor?
v Yes: The symptom has changed, see “Solving undetermined problems”
on page 106 to continue troubleshooting.
v No: Go to step 12.
12. (Trained service technician only) Replace the system-board tray.
30System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 47
Troubleshooting tables
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
If you cannot find a problem in these tables, see “Running the diagnostic programs”
on page 40 for information about testing the system-board tray.
If you have just added new software or a new optional device and the system-board
tray is not working, complete the following steps before you use the troubleshooting
tables:
1. Remove the software or device that you just added.
2. Run the diagnostic tests to determine whether the system-board tray is running
correctly.
3. Reinstall the new software or new device.
General problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
A cover lock is broken, an LED
is not working, or a similar
problem has occurred.
If the part is a CRU, replace it. If the part is a FRU, the part must be replaced by a
trained service technician.
Hard disk drive problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
A hard disk drive has failed, and
the associated amber hard disk
drive status LED is lit.
Replace the failed hard disk drive (see “Removing and installing a hard disk drive”
on page 139).
Chapter 3. Diagnostics31
Page 48
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
A newly installed hard disk drive
is not recognized.
Multiple hard disk drives fail.Make sure that the hard disk drive, SAS RAID controller, and system-board tray
1. Observe the associated amber hard disk drive status LED. If the LED is lit, it
indicates a drive fault.
2. If the LED is lit, remove the drive from the bay, wait 45 seconds, and reinsert
the drive, making sure that the drive assembly connects to the hard disk drive
backplane.
3. Observe the associated green hard disk drive activity LED and the amber
status LED:
v If the green activity LED is flashing and the amber status LED is not lit, the
drive is recognized by the controller and is working correctly. Run the DSA
hard disk drive test to determine whether the drive is detected.
v If the green activity LED is flashing and the amber status LED is flashing
slowly, the drive is recognized by the controller and is rebuilding.
v If neither LED is lit or flashing, check the hard disk drive backplane (go to
step 4).
v If the green activity LED is flashing and the amber status LED is lit, replace
the drive. If the activity of the LEDs remains the same, go to step 4. If the
activity of the LEDs changes, return to step 1.
4. Make sure that the hard disk drive backplane is correctly seated. When it is
correctly seated, the drive assemblies correctly connect to the backplane
without bowing or causing movement of the backplane.
5. Reseat the backplane power cable and repeat steps 1 through 3.
6. Reseat the backplane signal cable and repeat steps 1 through 3.
7. Suspect the backplane signal cable or the backplane:
v If the configuration has eight hot-swap bays:
a. Replace the affected backplane signal cable.
b. Replace the affected backplane.
v If the configuration has 12 hot-swap bays:
a. Replace the backplane signal cable.
b. Replace the backplane.
c. Replace the SAS expander card.
8. Run the DSA tests for the SAS controller and hard disk drives:
v If the controller passes the test but the drives are not recognized, replace the
backplane signal cable and run the tests again.
v Replace the backplane.
v If the controller fails the test, disconnect the backplane signal cable from the
controller and run the tests again.
v If the controller fails the test, replace the controller.
9. See “Problem determination tips” on page 108.
device drivers and firmware are at the latest level.
Important: Some cluster solutions require specific code levels or coordinated code
updates. If the device is part of a cluster solution, verify that the latest level of code
is supported for the cluster solution before you update the code.
32System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 49
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
Multiple hard disk drives are
offline.
A replacement hard disk drive
does not rebuild.
A green hard disk drive activity
LED does not accurately
represent the actual state of the
associated drive.
An amber hard disk drive status
LED does not accurately
represent the actual state of the
associated drive.
1. Review the storage subsystem logs for indications of problems within the
storage subsystem, such as backplane or cable problems.
2. See “Problem determination tips” on page 108.
1. Make sure that the hard disk drive is recognized by the controller (the green
hard disk drive activity LED is flashing).
2. Review the SAS RAID controller documentation to determine the correct
configuration parameters and settings.
1. If the green hard disk drive activity LED does not flash when the drive is in use,
run the DSA disk drive test.
2. Use one of the following procedures:
v If the drive passes the test, replace the backplane.
v If the drive fails the test, replace the drive.
1. If the amber hard disk drive LED and the RAID controller software do not
indicate the same status for the drive, complete the following steps:
a. Turn off the system-board tray.
b. Reseat the SAS controller.
c. Reseat the backplane signal cable, backplane power cable, and SAS
expander card (if the server has 12 drive bays).
d. Reseat the hard disk drive.
e. Turn on the system-board tray and observe the activity of the hard disk
drive LEDs.
2. See “Problem determination tips” on page 108.
Intermittent problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
A problem occurs only
occasionally and is difficult to
diagnose.
1. Make sure that:
v All cables are connected securely to the front of the system-board tray and
the power cord is connected securely to the rear of the chassis.
v When the system-board tray is turned on, air is flowing from the rear of the
chassis. If there is no airflow, the fan assembly is not working. This causes
the system-board tray to overheat and shut down.
2. Check the system-event log (see “Event logs” on page 25).
3. See “Solving undetermined problems” on page 106.
Chapter 3. Diagnostics33
Page 50
Keyboard or mouse problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
All keyboard and mouse
problems.
1. Make sure that the keyboard and mouse cables are securely connected.
2. If you are using a USB keyboard and mouse and they are connected to a USB
hub, disconnect the devices from the hub and connect them directly to the
system-board tray.
3. Replace the following components one at a time, in the order shown, restarting
the system-board tray each time:
a. Keyboard or mouse
b. (Trained service technician only) System-board tray
34System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 51
Memory problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
The amount of system memory
that is displayed is less than the
amount of installed physical
memory.
1. Make sure that:
v Memory mirroring does not account for the discrepancy.
v The memory modules are seated correctly.
v You have installed the correct type of memory.
v If you changed the memory, you updated the memory configuration in the
Setup utility.
v All banks of memory are enabled. The software might have automatically
disabled a memory bank when it detected a problem, or a memory bank
might have been manually disabled.
2. Check the POST event log for a memory error message.
v If a DIMM was disabled by a systems-management interrupt (SMI), replace
the DIMM.
v If a DIMM was disabled by the user or by POST, run the Setup utility and
enable the DIMM.
3. Run memory diagnostics (see “Running the diagnostic programs” on page 40).
4. Make sure that there is no memory mismatch when the system-board tray is at
the minimum memory configuration (see “Solving undetermined problems” on
page 106 for information about the minimum required configuration).
5. Add one pair of DIMMs at a time, making sure that the DIMMs in each pair
match.
6. Reseat the DIMMs.
7. Replace the following components one at a time, in the order shown, restarting
the system-board tray each time:
a. DIMMs
b. (Trained service technician only) System-board tray
Microprocessor problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
Multiple error codes indicate a
microprocessor error.
1. (Trained service technician only) Reseat the microprocessor and restart the
system-board tray.
2. Run the DSA Preboot diagnostic program. See “Running the diagnostic
programs” on page 40.
3. (Trained service technician only) Replace the microprocessor.
Chapter 3. Diagnostics35
Page 52
Optional-device problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
An IBM optional device that was
just installed does not work.
An IBM optional device that
used to work does not work
now.
1. Make sure that:
v The device is designed for the system-board tray.
v You followed the installation instructions that came with the device and the
device is installed correctly.
v You have not loosened any other installed devices or cables.
v You updated the configuration information in the Setup utility. Whenever
memory or any other device is changed, you must update the configuration.
2. If the device comes with its own test instructions, use those instructions to test
the device.
3. Reseat the device that you just installed.
4. Replace the device that you just installed.
1. Make sure that all of the cable connections for the device are secure.
2. If the device comes with test instructions, use those instructions to test the
device.
3. Reseat the failing device.
4. Replace the failing device.
36System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 53
Power problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
The power-control button does
not work (the system-board tray
does not start).
The system-board tray does not
turn off.
The system-board tray
unexpectedly shuts down, and
the LEDs on the operator panel
are not lit.
1. Make sure that the operator panel power-control button is working correctly:
a. Disconnect the chassis power cord.
b. Reconnect the power cord.
c. Press the power-control button.
2. Make sure that:
v The power cord is fully seated in the power-supply inlet and connected to a
working electrical outlet and that the power-supply fan is working.
v The system-board tray contains the correct type of DIMMs.
v The DIMMs are correctly seated.
v The microprocessor is correctly installed.
3. Reseat the following components:
a. DIMMs
b. Power-supply cables to all internal components
c. Power supply
4. Replace the following components one at a time, in the order shown, restarting
the system-board tray each time:
a. DIMMs
b. Power supply
5. If you just installed an optional device, remove it, and restart the system-board
tray. If the system-board tray now starts, you might have installed more devices
than the power supply supports.
6. See “Solving undetermined problems” on page 106.
1. Determine whether you are using an Advanced Configuration and Power
Interface (ACPI) or a non-ACPI operating system. If you are using a non-ACPI
operating system, complete the following steps:
a. Press Ctrl+Alt+Delete.
b. Turn off the system-board tray by holding the power-control button for 5
seconds.
c. Restart the system-board tray.
d. If the system-board tray fails POST and the power-control button does not
work, disconnect the ac power cord for 20 seconds; then, reconnect the ac
power cord and restart the system-board tray.
2. (Trained service technician only) If the problem remains or if you are using an
ACPI-aware operating system, suspect the system board.
See “Solving undetermined problems” on page 106.
Chapter 3. Diagnostics37
Page 54
Serial-device problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
The number of serial ports that
are identified by the operating
system is less than the number
of installed serial ports.
A serial device does not work.
1. Make sure that each port is assigned a unique address in the Setup utility and
none of the serial ports is disabled.
Note: One external serial port is available. A second port (COM2) is reserved
for the IMM Serial over LAN (SOL) function.
2. Reseat the serial port adapter, if one is installed.
3. Replace the serial port adapter, if one is installed.
1. Make sure that:
v The device is compatible with the system-board tray.
v The serial port is enabled and is assigned a unique address.
v The device is connected to the correct connector (see “Operator panel
controls, connectors, and LEDs” on page 8).
2. Reseat the following components:
a. Failing serial device
b. Serial cable
3. Replace the following components one at a time, in the order shown, restarting
the system-board tray each time:
a. Failing serial device
b. Serial cable
c. (Trained service technician only) System-board tray
Software problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
You suspect a software
problem.
38System x iDataPlex dx360 M2: Problem Determination and Service Guide
1. To determine whether the problem is caused by the software, make sure that:
v The system-board tray has the minimum memory that is needed to use the
software. For memory requirements, see the information that comes with the
software.
Note: If you have just installed an adapter or memory, the system-board tray
might have a memory-address conflict.
v The software is designed to operate on the system-board tray.
v Other software works on the system-board tray.
v The software works on another system-board tray.
2. If you receive any error messages while you use the software, see the
information that comes with the software for a description of the messages and
suggested solutions to the problem.
3. Contact your place of purchase of the software.
Page 55
Universal Serial Bus (USB) port problems
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
SymptomAction
A USB device does not work.Important: To avoid potential problems during startup, disconnect any USB flash
drives from the system that contain the Smart Launch Utility before you turn on the
system-board tray.
1. Make sure that:
v The operating system supports USB devices.
v The correct USB device driver is installed.
2. Make sure that the USB configuration options are set correctly in the Setup
utility.
3. If you are using a USB hub, disconnect the USB device from the hub and
connect it directly to the system-board tray.
4. (Trained service technician only) Replace the system-board tray.
Diagnostic programs, messages, and error codes
The IBM Dynamic System Analysis (DSA) Preboot diagnostic programs are the
primary method of testing the major components of the system-board tray. DSA is a
system information collection and analysis tool that you can use to provide
information to IBM service and support to aid in the diagnosis of the system
problems.
To download the latest version of DSA, go to http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA or complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual procedure
might vary slightly from what is described in this document.
1. Go to http://www.ibm.com/systems/support/.
2. Under Product support, click System x.
3. Under Popular links, click Software and device drivers.
4. Click Dynamic System Analysis (DSA).
As you run the diagnostic programs, text messages are displayed on the screen
and are saved in the test log. A diagnostic text message indicates that a problem
has been detected and indicates what action you should take as a result of the text
message.
The DSA diagnostic programs collect information about the following aspects of the
system:
v System configuration
v Network interfaces and settings
v Hardware inventory, including PCIe and USB information
v Service processor status and configuration
v Vital product data, firmware, and server firmware
Chapter 3. Diagnostics39
Page 56
v Drive health information
v LSI RAID and adapter configuration
v Event logs for RAID controllers and service processors
The DSA diagnostic programs can also provide diagnostics for the following system
components, if they are installed in the system:
v Hard disk drives
v Memory
v Microprocessor
v Network devices
v IMM I2C bus test
The diagnostic programs create a service data record with information about the
server and results from the diagnostics tests you performed. You can output all of
the collected information as a compressed XML file that you can send to IBM
service and support, view the information locally through a generated text report file,
or copy the log to a removable media and view the log from a Web browser. See
“Running the diagnostic programs” for more information.
Running the diagnostic programs
Important: The DSA diagnostic programs do not support USB CD-ROM drives. If
you run the DSA diagnostic programs while any USB CD-ROM drives are attached,
ignore any optical drive test results that are returned for USB CD-ROM drives. You
also can remove USB CD-ROM drives before you run the DSA diagnostic programs
to get accurate optical drive test results.
To run the DSA Preboot diagnostic programs, complete the following steps:
1. If the system-board tray is running, turn off the system-board tray and all
attached devices.
2. Turn on all attached devices; then, turn on the system-board tray.
3. When the prompt Press F2 for Dynamic System Analysis (DSA) is displayed,
press F2.
Note: The DSA Preboot diagnostic program might appear to be unresponsive
for an unusual length of time when you start the program. This is normal
operation while the program loads.
4. Optionally, select Exit to DSA to exit from the stand-alone memory diagnostic
program.
Note: After you exit from the stand-alone memory diagnostic environment, you
must restart the server to access the stand-alone memory diagnostic
environment again.
5. Select gui to display the graphical user interface, or select cmd to display the
DSA interactive menu.
6. Follow the instructions on the screen to select the diagnostic test to run.
Follow the actions in the “Diagnostic error codes” on page 41 to solve the problem.
If the diagnostic programs do not detect any hardware errors but the problem
remains during normal operations, a software error might be the cause. If you
suspect a software problem, see the information that comes with your software.
40System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 57
A single problem might cause more than one error message. When this happens,
correct the cause of the first error message. The other error messages usually will
not occur the next time you run the diagnostic programs.
Exception: Reseat all hard disk drives and cables; then, run the hard disk drive
diagnostic tests again. See “Microprocessor problems” on page 35 for
information about diagnosing microprocessor problems.
If the system-board tray stops during testing and you cannot continue, restart the
system-board tray and try running the diagnostic programs again. If the problem
remains, replace the component that was being tested when the system-board tray
stopped.
Diagnostic text messages
Diagnostic text messages are displayed while the tests are running. A diagnostic
text message contains one of the following results:
Passed: The test was completed without any errors.
Failed: The test detected an error.
Aborted: The test could not proceed because of the server configuration.
Viewing the test log
You can use one of the following methods to access the test log when the tests are
completed:
v From the DSA command line, issue the DSA CLI view command or select
Diagnostic Event Log from the DSA graphical user interface (GUI).
v From the DSA interactive menu, select getextendedresults.
v From the DSA interactive menu, select view to view all of the collected results
and event log data.
v In the DSA GUI, select DSA error log from the System Information page.
You can send the DSA event log file to IBM service and support to aid in diagnosing
the server problems or you can use the DSA CLI copy command to copy the log to
an external USB device.
Diagnostic error codes
The following table describes the messages that the diagnostic programs might
generate and suggested actions to correct the detected problems. Follow the
suggested actions in the order in which they are listed in the action column.
Important: The DSA diagnostic programs do not support USB CD-ROM drives. If
you run the DSA diagnostic programs while any USB CD-ROM drives are attached,
ignore any optical drive test results that are returned for USB CD-ROM drives.
Chapter 3. Diagnostics41
Page 58
Table 2. DSA Preboot messages
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
089-801-xxxCPUCPU Stress
Test
AbortedInternal
program error.
1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Run the test again.
4. Make sure that the system firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
5. Run the test again.
6. Turn off and restart the system if necessary to
recover from a hung state.
7. Run the test again.
8. Replace the following components one at a time,
in the order shown, and run this test again to
determine whether the problem has been solved:
a. (Trained service technician only)
Microprocessor board
b. (Trained service technician only)
Microprocessor
9. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
42System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 59
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
089-802-xxxCPUCPU Stress
Test
AbortedSystem
resource
availability error.
1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Run the test again.
4. Make sure that the system firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
5. Run the test again.
6. Turn off and restart the system if necessary to
recover from a hung state.
7. Run the test again.
8. Make sure that the system firmware is at the
latest level. The installed firmware level is
shown in the DSA event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
9. Run the test again.
10. Replace the following components one at a
time, in the order shown, and run this test
again to determine whether the problem has
been solved:
a. (Trained service technician only)
Microprocessor board
b. (Trained service technician only)
Microprocessor
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
43
Page 60
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
089-901-xxxCPUCPU Stress
Test
FailedTest failure.
1. Turn off and restart the system if necessary to
recover from a hung state.
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Run the test again.
4. Make sure that the system firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
5. Run the test again.
6. Turn off and restart the system if necessary to
recover from a hung state.
7. Run the test again.
8. Replace the following components one at a time,
in the order shown, and run this test again to
determine whether the problem has been solved:
a. (Trained service technician only)
Microprocessor board
b. (Trained service technician only)
Microprocessor
9. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
44System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 61
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-801-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: the
IMM returned
an incorrect
response
length.
166-802-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: the
test cannot be
completed for
an unknown
reason.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
45
Page 62
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-803-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: the
node is busy;
try later.
166-804-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: invalid
command.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
46System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 63
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-805-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: invalid
command for
the given LUN.
166-806-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
timeout while
processing the
command.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
47
Page 64
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-807-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: out of
space.
166-808-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
reservation
canceled or
invalid
reservation ID.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
48System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 65
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-809-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
request data
was truncated.
166-810-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
request data
length is invalid.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
49
Page 66
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-811-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
request data
field length limit
is exceeded.
166-812-xxxIMMIMM I2C Test AbortedIMM I2C Test
stopped a
parameter is
out of range.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
50System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 67
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-813-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: cannot
return the
number of
requested data
bytes.
166-814-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped:
requested
sensor, data, or
record is not
present.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
51
Page 68
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-815-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: invalid
data field in the
request.
166-816-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: the
command is
illegal for the
specified sensor
or record type.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
52System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 69
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-817-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: a
command
response could
not be provided.
166-818-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: cannot
execute a
duplicated
request.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
53
Page 70
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-819-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: a
command
response could
not be provided;
the SDR
repository is in
update mode.
166-820-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: a
command
response could
not be provided;
the device is in
firmware update
mode.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code and IMM firmware
are at the latest level.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
54System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 71
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-821-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: a
command
response could
not be provided;
IMM
initialization is
in progress.
166-822-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: the
destination is
unavailable.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
55
Page 72
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-823-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: cannot
execute the
command;
insufficient
privilege level.
166-824-xxxIMMIMM I2C Test AbortedIMM I2C test
stopped: cannot
execute the
command.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the latest
level. The installed firmware level is shown in
the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
56System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 73
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-901-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the I/O
controller hub.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Remove power from the system.
8. (Trained service technician only) Replace the
system board.
9. Reconnect the system to power and turn on the
system.
10. Run the test again.
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
57
Page 74
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-902-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the
SIO bus.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Turn off the system and disconnect it from the
power source.
8. (Trained service technician only) Replace the
system board.
9. Reconnect the system to the power source and
turn on the system.
10. Run the test again.
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
58System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 75
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-903-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the
LAN bus.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Make sure that the Ethernet device firmware is
at the latest level. The installed firmware level
is shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
7. Run the test again.
8. Turn off the system and disconnect it from the
power source.
9. (Trained service technician only) Replace the
system board.
10. Reconnect the system to the power source and
turn on the system.
11. Run the test again.
12. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
59
Page 76
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-904-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the
LED or CPU
temperature
bus.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Turn off the system and disconnect it from the
power source.
8. (Trained service technician only) Replace the
system board.
9. Reconnect the system to the power source and
turn on the system.
10. Run the test again.
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
60System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 77
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-905-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the
VRD bus.
Note: Ignore the error if the hard disk drive
backplane is not installed.
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Turn off the system and disconnect it from the
power source.
8. (Trained service technician only) Reseat the
microprocessors.
9. (Trained service technician only) Replace the
system board.
10. Reconnect the system to the power source and
turn on the system.
11. Run the test again.
12. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
61
Page 78
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
166-906-xxxIMMIMM I2C Test FailedThe IMM
indicates a
failure in the
VPD Power
PSOC.
201-801-xxxMemoryMemory TestAbortedTest canceled:
the server
firmware
programmed
the memory
controller with
an invalid
CBAR address
1. Turn off the system and disconnect it from the
power source. You must disconnect the system
from ac power to reset the IMM.
2. After 45 seconds, reconnect the system to the
power source and turn on the system.
3. Run the test again.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the IMM firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Turn off the system and disconnect it from the
power source.
8. (Trained service technician only) Replace the
system board.
9. Reconnect the system to the power source and
turn on the system.
10. Run the test again.
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
62System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 79
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
201-802-xxxMemoryMemory TestAbortedTest canceled:
the end address
in the E820
function is less
than 16 MB.
201-803-xxxMemoryMemory TestAbortedTest canceled:
could not
enable the
processor
cache.
201-804-xxxMemoryMemory TestAbortedTest canceled:
the memory
controller buffer
request failed.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that all DIMMs are enabled in the
Setup utility.
4. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
5. Run the test again.
6. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
63
Page 80
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
201-805-xxxMemoryMemory TestAbortedTest canceled:
the memory
controller
display/alter
write operation
was not
completed.
201-806-xxxMemoryMemory TestAbortedTest canceled:
the memory
controller fast
scrub operation
was not
completed.
201-807-xxxMemoryMemory TestAbortedTest canceled:
the memory
controller buffer
free request
failed.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
64System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 81
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
unknown error
code xxx
received in
COMMONEXIT
procedure.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
4. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
5. Run the test again.
6. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Run the test again.
3. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
4. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
5. Run the test again.
6. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
65
Page 82
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
201-901-xxxMemoryMemory TestFailedTest failure:
single-bit error,
failing DIMM z.
1. Turn off the system and disconnect it from the
power source.
2. Reseat DIMM z.
3. Reconnect the system to power and turn on the
system.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the server firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Replace the failing DIMMs.
8. Re-enable all memory in the Setup utility (see
“Using the Setup utility” on page 214).
9. Run the test again.
10. Replace the failing DIMM.
11. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
66System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 83
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
201-902-xxxMemoryMemory TestFailedTest failure:
202-801-xxxMemoryMemory
Stress Test
AbortedInternal
single-bit and
multi-bit error,
failing DIMM z
program error.
1. Turn off the system and disconnect it from the
power source.
2. Reseat DIMM z.
3. Reconnect the system to power and turn on the
system.
4. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
5. Make sure that the server firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
6. Run the test again.
7. Replace the failing DIMMs.
8. Re-enable all memory in the Setup utility see
“Using the Setup utility” on page 214).
9. Run the test again.
10. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Turn off and restart the system.
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Make sure that the server firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
4. Run the test again.
5. Turn off and restart the system if necessary to
recover from a hung state.
6. Run the memory diagnostics to identify the
specific failing DIMM.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
67
Page 84
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
202-802-xxxMemoryMemory
Stress Test
202-901-xxxMemoryMemory
Stress Test
FailedGeneral error:
memory size is
insufficient to
run the test.
FailedTest failure.
1. Make sure that all memory is enabled by
checking the Available System Memory in the
Resource Utilization section of the DSA event
log. If necessary, enable all memory in the Setup
utility (see “Using the Setup utility” on page 214).
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Run the test again.
4. Run the standard memory test to validate all
memory.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Run the standard memory test to validate all
memory.
2. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
3. Turn off the system and disconnect it from
power.
4. Reseat the DIMMs.
5. Reconnect the system to power and turn on the
system.
6. Run the test again.
7. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
68System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 85
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
215-801-xxxOptical Drive
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
AbortedUnable to
communicate
with the device
driver.
1. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
2. Run the test again.
3. Check the drive cabling at both ends for loose
or broken connections or damage to the cable.
Replace the cable if it is damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
http://www.ibm.com/support/
docview.wss?uid=psg1MIGR-41559.
6. Run the test again.
7. Make sure that the system firmware is at the
latest level. The installed firmware level is
shown in the diagnostic event log in the
Firmware/VPD section for this component. For
more information, see “Firmware updates” on
page 213.
8. Run the test again.
9. Replace the CD/DVD drive.
10. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
69
Page 86
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
215-802-xxxOptical Drive
215-803-xxxOptical Drive
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
AbortedThe media tray
is open.
FailedThe disc might
be in use by the
system.
1. Close the media tray and wait 15 seconds.
2. Run the test again.
3. Insert a new CD/DVD into the drive and wait
for 15 seconds for the media to be recognized.
4. Run the test again.
5. Check the drive cabling at both ends for loose
or broken connections or damage to the cable.
Replace the cable if it is damaged.
6. Run the test again.
7. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
8. Run the test again.
9. For additional troubleshooting information, go to
http://www.ibm.com/support/
docview.wss?uid=psg1MIGR-41559.
10. Run the test again.
11. Replace the CD/DVD drive.
12. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Wait for the system activity to stop.
2. Run the test again
3. Turn off and restart the system.
4. Run the test again.
5. Replace the CD/DVD drive.
6. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
70System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 87
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
215-901-xxxOptical Drive
215-902-xxxOptical Drive
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
AbortedDrive media is
not detected.
FailedRead
miscompare.
1. Insert a CD/DVD into the drive or try a new
media, and wait for 15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or
broken connections or damage to the cable.
Replace the cable if it is damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
http://www.ibm.com/support/
docview.wss?uid=psg1MIGR-41559.
6. Run the test again.
7. Replace the CD/DVD drive.
8. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Insert a CD/DVD into the drive or try a new
media, and wait for 15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or
broken connections or damage to the cable.
Replace the cable if it is damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
http://www.ibm.com/support/
docview.wss?uid=psg1MIGR-41559.
6. Run the test again.
7. Replace the CD/DVD drive.
8. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
71
Page 88
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
215-903-xxxOptical Drive
215-904-xxxOptical Drive
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
v Verify
Media
Installed
v Read/ Write
Test
v Self-Test
Messages
and actions
apply to all
three tests.
AbortedCould not
access the
drive.
FailedA read error
occurred.
1. Insert a CD/DVD into the drive or try a new
media, and wait for 15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose
or broken connections or damage to the cable.
Replace the cable if it is damaged.
4. Run the test again.
5. Make sure that the DSA code is at the latest
level. For the latest level of DSA code, go to
http://www.ibm.com/support/
docview.wss?uid=psg1SERV-DSA.
6. Run the test again.
7. For additional troubleshooting information, go to
http://www.ibm.com/support/
docview.wss?uid=psg1MIGR-41559.
8. Run the test again.
9. Replace the CD/DVD drive.
10. If the failure remains, go to the IBM Web site
for more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Insert a CD/DVD into the drive or try a new
media, and wait for 15 seconds.
2. Run the test again.
3. Check the drive cabling at both ends for loose or
broken connections or damage to the cable.
Replace the cable if it is damaged.
4. Run the test again.
5. For additional troubleshooting information, go to
8. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
72System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 89
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
217-900-xxxHard DriveDisk Drive
405-901-xxxBroadcom
Ethernet
Device
405-901-xxxBroadcom
Ethernet
Device
Self Test
Test Control
Registers
Test MII
Registers
Failed
Failed
Failed
1. Reseat all hard disk drive backplane connections
at both ends.
2. Reseat the all drives.
3. Run the test again.
4. Make sure that the firmware is at the latest level.
5. Run the test again.
6. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
73
Page 90
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
405-903-xxxBroadcom
Ethernet
Device
405-904-xxxBroadcom
Ethernet
Device
Test EEPROM Failed
FIFOFailed
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
74System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 91
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
405-905-xxxBroadcom
Ethernet
Device
405-906-xxxBroadcom
Ethernet
Device
Test InterruptFailed
Test Loop
back at
Physical
Layer
Failed
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Check the interrupt assignments in the PCI
Hardware section of the DSA event log. If the
Ethernet device is sharing interrupts, if possible,
use the Setup utility see “Using the Setup utility”
on page 214) to assign a unique interrupt to the
device.
4. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Check the Ethernet cable for damage and make
sure that the cable type and connection are
correct.
2. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
3. Run the test again.
4. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
5. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
Chapter 3. Diagnostics
75
Page 92
Table 2. DSA Preboot messages (continued)
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable units (CRU) and
which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a trained
service technician.
Message
numberComponentTestStateDescriptionAction
405-907-xxxBroadcom
Ethernet
Device
405-908-xxxBroadcom
Ethernet
Device
Test Loop
back at
MAC-Layer
Test LEDsFailed
Failed
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
1. Make sure that the component firmware is at the
latest level. The installed firmware level is shown
in the diagnostic event log in the Firmware/VPD
section for this component. For more
information, see “Firmware updates” on page
213.
2. Run the test again.
3. Replace the component that is causing the error.
If the error is caused by an adapter, replace the
adapter. Check the PCI Information and Network
Settings information in the DSA event log to
determine the physical location of the failing
component.
4. If the failure remains, go to the IBM Web site for
more troubleshooting information at
http://www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008
&lndocid=SERV-CALL.
76System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 93
Clearing CMOS memory
To clear the CMOS memory, complete the following steps:
1. Read the safety information that begins on page vii and “Installation guidelines”
on page 123.
2. Turn off the system-board tray and all attached devices; then, disconnect the
chassis power cord and external cables.
3. If the system-board tray is installed in a chassis, remove it (see “Removing the
system-board tray from a 2U chassis” on page 126 or “Removing the
system-board tray from a 3U chassis” on page 128).
4. If an expansion enclosure is installed, remove it (see “Removing an expansion
enclosure from a system-board tray” on page 131); otherwise, remove the
system-board tray cover (see “Removing the system-board tray cover” on page
125).
5. Remove the battery (see “Removing the battery” on page 137).
6. Locate the Clear CMOS jumper (JP1) (see “System-board jumpers” on page
12).
7. Move the jumper from pins 1 and 2 to pins 2 and 3.
8. Wait approximately 10 seconds; then, move the jumper back to pins 1 and 2.
9. Install the battery (see “Installing the battery” on page 138).
10. Install the expansion enclosure, if you removed one (see “Installing an
expansion enclosure on a system-board tray” on page 132); otherwise, install
the system-board tray cover (see “Installing the system-board tray cover” on
page 125).
11. Install the system-board tray in the chassis (see “Installing the system-board
tray in a 2U chassis” on page 127 or “Installing the system-board tray in a 3U
chassis” on page 129).
12. Reconnect the external cables and power cords; then, turn on the attached
devices and turn on the system-board tray.
13. Run the Setup utility and set configuration parameters as necessary (see
“Using the Setup utility” on page 214 for information).
Updating (flash-updating) the server firmware
Periodically, IBM makes new levels of server firmware available on the Web. Always
check http://www.ibm.com/systems/support/ for the latest level of server firmware,
device drivers, documentation, and hints and tips. You can use one of the following
methods to update (flash-update) the server firmware on the system-board tray:
v Download the server firmware update file directly to the hard disk drive.
v Download the server firmware update file to an external USB device, such as a
USB flash drive; then, start the system-board tray with the external USB device
attached to the system-board tray to update the server firmware.
v Download the server firmware update file to a CD or DVD (you must attach an
optional external USB portable CD or DVD drive to the system-board tray); then,
start the system-board tray with the CD or DVD in the CD or DVD drive to
update the server firmware.
One file type is available for each of these methods. The description next to each
file indicates the type of medium to which you can download the file. A readme file
is also available with instructions for installing the server firmware update.
Chapter 3. Diagnostics77
Page 94
Important: Some cluster solutions require specific code levels or coordinated code
updates. If the device is part of a cluster solution, verify that the latest
level of code is supported for the cluster solution before you update the
code.
To download the UEFI (flash) update files, complete the following steps.
Note: Changes are made periodically to the IBM Web site. The actual procedure
might vary slightly from what is described in this document.
1. Go to http://www.ibm.com/systems/support/.
2. Under Product support, click System x.
3. Under Popular links, click Software and device drivers.
4. Click System x iDataPlex dx360 M2 server to display the matrix of
downloadable files.
5. Select the applicable file for your operating system and the file type for the
medium that you want to use; then, download the flash UEFI update.
6. Update the server firmware and follow the instructions in the readme file that
comes with the update file.
Note: Always reset the Setup utility to the default values after you update the
server firmware.
7. Restart the system-board tray.
System-event log
The system-event log contains messages of three types:
InformationInformation messages do not require action; they record significant
WarningWarning messages do not require immediate action; they indicate
ErrorError messages might require action; they indicate system errors,
system-level events, such as when the server is started.
possible problems, such as when the recommended maximum
ambient temperature is exceeded.
such as when a fan is not detected.
78System x iDataPlex dx360 M2: Problem Determination and Service Guide
Page 95
Integrated management module error messages
The following table describes the possible integrated management module error
messages and suggested actions to correct the detected problems.
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
MessageSeverityDescriptionAction
A Uncorrectable Bus Error
has occurred on system %1.
(%1 =
CIM_ComputerSystem.
ElementName)
An Over-Temperature
Condition has been detected
on the Processor CPU
n Status.
(n = microprocessor number)
ErrorA bus uncorrectable error has
occurred.
(Sensor = Critical Int CPU)
ErrorAn overtemperature condition has
occurred for microprocessor n.
(n = microprocessor number)
1. Check the system-event log.
2. Check the microprocessor error
LEDs.
3. Remove the failing
microprocessor from the system
board.
4. Check for a UEFI firmware
update.
Important: Some cluster
solutions require specific code
levels or coordinated code
updates. If the device is part of
a cluster solution, verify that the
latest level of code is supported
for the cluster solution before
you update the code.
5. Make sure that the two
microprocessors are matching
(see “Installing a
microprocessor and heat sink”
on page 199 for information
about microprocessor
requirements).
6. (Trained service technician only)
Replace the system board.
1. Make sure that the fans are
operating, that there are no
obstructions to the airflow, that
the air baffles are in place and
correctly installed, and that the
server cover is installed and
completely closed.
2. Make sure that the heat sink for
microprocessor n is installed
correctly.
3. (Trained service technician only)
Replace microprocessor n.
(n = microprocessor number)
80System x iDataPlex dx360 M2: Problem Determination and Service Guide
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
MessageSeverityDescriptionAction
An SM BIOS Uncorrectable
CPU complex error for
Processor CPU n Status
has asserted.
(n = microprocessor number)
ErrorAn SMBIOS uncorrectable CPU
complex error has asserted.
1. Check for a UEFI firmware
update.
Important: Some cluster
solutions require specific code
levels or coordinated code
updates. If the device is part of
a cluster solution, verify that the
latest level of code is supported
for the cluster solution before
you update the code.
2. Make sure that the installed
microprocessors are compatible
with each other (see “Installing
a microprocessor and heat sink”
on page 199 for information
about microprocessor
requirements).
3. (Trained service technician only)
Reseat microprocessor n.
4. (Trained service technician only)
Replace microprocessor n.
(n = microprocessor number)
Attempting to %1 server %2
by user %3.
(%1 = Power Up, Power
InfoA user has used the IMM to
perform a power function on the
server.
No action; information only.
Down, Power Cycle, or
Reset;
%2 = IBM_ComputerSystem.
ElementName; %3 = user
ID)
Certificate Authority %1 has
detected a %2 Certificate
Error. (%1 = IBM_Certificate
Authority.CADistinguished
Name; %2 =
CIM_PublicKeyCertificate.
ElementName)
ErrorA problem has occurred with the
SSL Server, SSL Client, or SSL
Trusted CA certificate that has been
imported into the IMM. The
imported certificate must contain a
public key that corresponds to the
key pair that was previously
1. Make sure that the certificate
that you are importing is
correct.
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 4, “Parts listing,” on page 109 to determine which components are customer replaceable
units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
MessageSeverityDescriptionAction
Failure Predicted on drive n
for array %1.
(n = hard disk drive number,
%1 = CIM_ComputerSystem.
ElementName)
Fault in slot System board
on system %1. (%1 =
CIM_ComputerSystem.
ElementName)
Flash of %1 from %2 failed
for user %3. (%1 =
CIM_ManagedElement.
ElementName;
%2 = Web or LegacyCLI;
%3 = user ID)
WarningPredicted failure on a drive.
ErrorA PCI slot error has occurred.
InfoAn attempt to update a firmware
component from the interface and
IP address has failed.
1. Run the hard disk drive
diagnostic test on drive n.
2. Reseat the following
components:
a. Hard disk drive
b. Cable from the system
board to the backplane
3. Replace the following
components one at a time, in
the order shown, restarting the
server each time:
a. Hard disk drive
b. Cable from the system
board to the backplane
c. Hard disk drive backplane
1. Check the riser-card LEDs.
2. Reseat the affected adapters
and riser card.
3. Update the server and adapter
firmware (UEFI and IMM).
Important: Some cluster
solutions require specific code
levels or coordinated code
updates. If the device is part of
a cluster solution, verify that the
latest level of code is supported
for the cluster solution before
you update the code.
4. Remove both adapters.
5. Replace the PCIe adapter.
6. Replace the riser card.
7. (Trained service technician only)
Replace the system board.
Try to update the firmware again.
84System x iDataPlex dx360 M2: Problem Determination and Service Guide
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.