X 3530 M 4 Ibm

System x3530 M4
Type 7160
Installation and Service Guide

System x3530 M4
Type 7160
Installation and Service Guide
Note
Before using this information and the product it supports, read the general information in
Notices on page 673 and the IBM Safety Information, and IBM Environmental Notices and User's
Guide on the IBM Documentation CD, and the IBM Warranty Information document that comes with
the server.
Seventh Edition (April 2014)

Copyright IBM Corporation 2014.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Safety . . . . . . . . . . . . . . . vii
Guidelines for trained service technicians . . . . ix
Inspecting for unsafe conditions . . . . . . ix
Guidelines for servicing electrical equipment . . x
Safety statements . . . . . . . . . . . . xi
Chapter 1. The IBM System x3530 M4

7160 server . . . . . . . . . . . . . 1
The IBM Documentation CD . . . . .
Hardware and software requirements .
Using the Documentation Browser . .
Related documentation . . . . . . .
Notices and statements in this document .
Server features and specifications . . .
What your server offers. . . . . . .
Reliability, availability, and serviceability
IBM Systems Director . . . . . . .
Server controls, LEDs, and power . . .
Front view. . . . . . . . . .
Operator information panel . . . .
Light path diagnostics panel . . . .
Rear view . . . . . . . . . .
Server power features . . . . . .
Turning on the server . . . . .
Turning off the server . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 3
. 4
. 4
. 5
. 6
. 6
. 9
. 13
. 14
. 15
. 15
. 16
. 18
. 19
. 23
. 23
. 23
Chapter 2. Installing optional devices

Installing optional hardware devices in the server
Instructions for IBM Business Partners . . . .
Sending DSA data to IBM . . . . . . . .
Server components . . . . . . . . . . .
Server internal LEDs, connectors, and jumpers
System-board internal connectors . . . . .
System-board external connectors . . . . .
System-board jumpers . . . . . . . . .
System-board LEDs. . . . . . . . . .
System-board optional device connectors . .
PCI riser cards . . . . . . . . . . . .
Installation guidelines . . . . . . . . . .
System reliability guidelines . . . . . . .
Handling static-sensitive devices . . . . .
Removing the server top cover . . . . . . .
Removing the air baffle . . . . . . . . .
Installing a memory module. . . . . . . .
Installing drives . . . . . . . . . . . .
Installing hot-swap drives . . . . . . .
IDs for hot-swap drives . . . . . . . .
Installing simple-swap drives . . . . . .
Installing an optional optical drive . . . .
Installing a PCI riser-card assembly . . . . .
Installing an adapter . . . . . . . . . .
Installing an optional IBM ServeRAID SAS/SATA
Controller . . . . . . . . . . . . . .
Installing an additional microprocessor and heat
sink . . . . . . . . . . . . . . . .
Copyright IBM Corp. 2014
25
26
26
26
27
28
28
28
29
30
31
32
34
35
36
36
37
38
43
44
45
46
47
50
51
54
55
Thermal grease . . . . . . . . . . .
Installing a hot-swap ac power supply . . . .
Installing a hot-swap dc power supply . . . .
Installing a USB embedded hypervisor flash
device . . . . . . . . . . . . . . .
Installing a RAID adapter battery remotely in the
server . . . . . . . . . . . . . . .
Installing an optional 4x2.5-inch hot-swap drive
backplane . . . . . . . . . . . . . .
Completing the installation . . . . . . . .
Replacing the air baffle . . . . . . . .
Replacing a PCI riser-card assembly . . . .
Replacing the server top cover . . . . . .
Connecting the cables . . . . . . . . .
Updating the server configuration . . . . .
60
61
64
70
71
74
77
78
79
80
81
82
Chapter 3. Configuration information

and instructions. . . . . . . . . . . 83
Updating the firmware . . . . . . . . . . 83
Configuring UEFI compatible devices . . . . . 84
Configuring the server. . . . . . . . . . . 84
Using the ServerGuide Setup and Installation CD 86
ServerGuide features . . . . . . . . . 86
Setup and configuration overview . . . . . 87
Typical operating-system installation . . . . 87
Installing your operating system without
using ServerGuide . . . . . . . . . . 87
Using the Setup utility. . . . . . . . . . 88
Starting the Setup utility . . . . . . . . 88
Setup utility menu choices . . . . . . . 88
Passwords . . . . . . . . . . . . . 93
Using the Boot Manager program . . . . . . 94
Starting the backup server firmware . . . . . 95
The UpdateXpress System Pack Installer . . . . 95
Using the integrated management module II . . 95
Using the embedded hypervisor . . . . . . 97
Using the remote presence and blue-screen
capture features . . . . . . . . . . . . 98
Obtaining the IP address for the IMM . . . 99
Logging on to the Web interface . . . . . 99
Enabling the Intel Gigabit Ethernet Utility
program . . . . . . . . . . . . . . 100
Configuring the Gigabit Ethernet controller . . 100
Configuring RAID arrays . . . . . . . . 101
Starting the LSI Configuration Utility
program . . . . . . . . . . . . . 102
Starting the Human Interface Infrastructure
(HII) Configuration Application . . . . . 102
Creating RAID of hard disk drives
(ServeRAID-C105 only) . . . . . . . . 102
IBM Advanced Settings Utility program . . . 104
Updating IBM Systems Director . . . . . . 104
Updating the Universal Unique Identifier
(UUID) . . . . . . . . . . . . . . 105
Updating the DMI/SMBIOS data . . . . . . 108
iii
Chapter 4. Troubleshooting . . . . . 113

Start here . . . . . . . . . . . . . . .
Diagnosing a problem . . . . . . . . .
Undocumented problems . . . . . . . .
Service bulletins . . . . . . . . . . . .
Checkout procedure . . . . . . . . . . .
About the checkout procedure . . . . . . .
Performing the checkout procedure . . . . .
Diagnostic tools . . . . . . . . . . . .
Light path diagnostics . . . . . . . . .
Light path diagnostics panel . . . . . .
Light path diagnostics LEDs . . . . . .
Power-supply LEDs . . . . . . . . . .
Event logs . . . . . . . . . . . . .
Viewing event logs through the Setup utility
Viewing event logs without restarting the
server . . . . . . . . . . . . . .
Clearing the error logs . . . . . . . .
POST . . . . . . . . . . . . . . .
IBM Dynamic System Analysis . . . . . .
DSA editions . . . . . . . . . . .
Running the DSA Preboot diagnostic
programs . . . . . . . . . . . . .
Diagnostic text messages . . . . . . .
Viewing the test log results . . . . . . .
Call home (automated service request) . . . . .
Service advisor . . . . . . . . . . . .
IBM Electronic Service Agent . . . . . . .
Error messages . . . . . . . . . . . . .
Troubleshooting by symptom . . . . . . . .
CD/DVD drive problems . . . . . . . .
Hypervisor problems . . . . . . . . . .
General problems . . . . . . . . . . .
Hard disk drive problems . . . . . . . .
Intermittent problems . . . . . . . . .
Keyboard, mouse, or pointing-device problems
Memory problems . . . . . . . . . . .
Microprocessor problems . . . . . . . .
Monitor and video problems . . . . . . .
Network connection problems . . . . . . .
Optional-device problems . . . . . . . .
Power problems . . . . . . . . . . .
Serial-device problems . . . . . . . . .
ServerGuide problems . . . . . . . . .
Software problems. . . . . . . . . . .
Universal Serial Bus (USB) port problems . . .
Video problems. . . . . . . . . . . .
Solving power problems. . . . . . . . . .
Solving Ethernet controller problems . . . . .
Solving undetermined problems . . . . . . .
Problem determination tips. . . . . . . . .
Recovering the server firmware (UEFI update
failure) . . . . . . . . . . . . . . .
Automated boot recovery (ABR) . . . . . . .
Nx boot failure . . . . . . . . . . . . .
113
113
115
116
116
116
117
118
120
122
123
129
130
131
131
133
133
134
134
135
136
136
136
136
137
137
137
138
139
139
140
142
143
145
146
146
149
150
151
152
153
154
154
155
155
155
156
157
158
160
160
Chapter 5. Parts listing, IBM System

x3530 M4 Type 7160 . . . . . . . . 161
Replaceable server components .
Consumable parts . . . . .
iv
.
.
.
.
.
.
.
.
.
.
. 161
. 169
System x3530 M4 Type 7160: Installation and Service Guide
Structural parts .
Power cords . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 170
. 171
Chapter 6. Removing and replacing

components . . . . . . . . . . . . 173
Returning a device or component . . . . .
Internal cable routing. . . . . . . . . .
General . . . . . . . . . . . . .
2.5-inch hard disk drive cable connection . .
4-drive-capable model . . . . . . .
8-drive-capable model . . . . . . .
3.5-inch hard disk drive cable connection . .
3.5-inch hot-swap model . . . . . .
3.5-inch simple-swap model . . . . .
Removing and replacing components . . . .
Removing the server top cover . . . . .
Replacing the server top cover . . . . .
Removing the bezel . . . . . . . . .
Replacing the bezel . . . . . . . . .
Removing the air baffle . . . . . . . .
Replacing the air baffle . . . . . . . .
Removing and replacing Tier 1 CRUs . . . .
Removing an adapter. . . . . . . . .
Replacing an adapter . . . . . . . . .
Removing hot-swap drives . . . . . . .
Installing hot-swap drives . . . . . . .
IDs for hot-swap drives . . . . . . .
Removing a simple-swap SATA drive . . .
Replacing a simple-swap SATA drive . . .
Removing a CD/DVD drive . . . . . .
Installing an optional CD/DVD drive . . .
Removing the CD/DVD cable . . . . . .
Replacing the CD/DVD cable . . . . . .
Removing a fan . . . . . . . . . .
Replacing a fan. . . . . . . . . . .
Removing a memory module . . . . . .
Replacing a memory module . . . . . .
Removing an IBM ServeRAID Controller . .
Replacing an optional IBM ServeRAID
Controller . . . . . . . . . . . .
Removing a remotely installed RAID adapter
battery . . . . . . . . . . . . .
Replacing a RAID adapter battery remotely in
the server . . . . . . . . . . . .
Removing a USB embedded hypervisor flash
device . . . . . . . . . . . . . .
Replacing a USB embedded hypervisor flash
device . . . . . . . . . . . . . .
Removing a hot-swap power supply . . .
Replacing a hot-swap power supply . . . .
Removing a hot-swap dc power supply . .
Replacing a hot-swap dc power supply. . .
Removing the fixed power supply . . . .
Replacing the fixed power supply . . . .
Removing a PCI riser-card assembly. . . .
Replacing a PCI riser-card assembly . . . .
Removing the operator information panel
assembly . . . . . . . . . . . . .
Replacing the operator information panel
assembly . . . . . . . . . . . . .
Removing the system battery . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
173
174
174
179
179
183
192
192
197
201
202
203
204
205
205
206
207
207
209
210
211
212
213
214
215
216
219
220
221
222
223
224
225
. 226
. 227
. 228
. 229
.
.
.
.
.
.
.
.
.
231
232
234
236
240
245
247
251
252
. 253
. 254
. 255
Replacing the system battery . . . . . .

Removing the front USB connector board . .
Replacing the front USB connector board . .
Removing the front video connector . . . .
Replacing the front video connector . . . .
Removing the power interposer card assembly
Replacing the power interposer card assembly
Removing the hot-swap drive backplane . .
Replacing the hot-swap drive backplane . .
Removing the simple-swap SATA drive
backplate assembly . . . . . . . . .
Replacing the simple-swap SATA drive
backplate assembly . . . . . . . . .
Removing and replacing Tier 2 CRUs . . . .
Removing a microprocessor and heat sink . .
Replacing a microprocessor and heat sink . .
Thermal grease . . . . . . . . . .
Removing the system board . . . . . .
Replacing the system board . . . . . .
.
.
.
.
.
257
259
261
262
263
265
267
. 269
. 269
. 270
.
.
.
.
.
.
.
271
272
273
275
280
281
286
Appendix A. Integrated Management

Module II (IMM2) error messages . . . 291
Appendix B. UEFI (POST) error codes
525
Appendix C. DSA diagnostic test

results . . . . . . . . . . . . . . 549
DSA Broadcom network test results .
DSA Brocade test results. . . . .
DSA checkpoint panel test results .
DSA CPU stress test results. . . .
DSA Emulex adapter test results . .
DSA EXA port ping test results . .
DSA hard drive test results . . . .
DSA Intel network test results . . .
DSA LSI hard drive test results . .
DSA Mellanox adapter test results .
DSA memory isolation test results .
DSA memory stress test results . .
DSA Nvidia GPU test results . . .
DSA optical drive test results . . .
DSA system management test results
DSA tape drive test results . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
549
556
562
563
566
568
569
570
573
576
579
647
648
652
654
664
Appendix D. Getting help and

technical assistance . . . . . . . . 669
Before you call . . . . . . . . . . . . .
Using the documentation . . . . . . . . .
Getting help and information from the World Wide
Web . . . . . . . . . . . . . . . .
How to send DSA data to IBM . . . . . . .
Creating a personalized support web page . . .
Software service and support . . . . . . . .
Hardware service and support . . . . . . .
IBM Taiwan product service . . . . . . . .
669
670
670
670
671
671
671
671
Notices . . . . . . . . . . . . . . 673
Trademarks . . . . . . . . . . . . . .
Important notes . . . . . . . . . . . .
Particulate contamination . . . . . . . . .
Documentation format . . . . . . . . . .
Telecommunication regulatory statement . . . .
Electronic emission notices . . . . . . . . .
Federal Communications Commission (FCC)
statement. . . . . . . . . . . . . .
Industry Canada Class A emission compliance
statement. . . . . . . . . . . . . .
Avis de conformit la rglementation
d'Industrie Canada . . . . . . . . . .
Australia and New Zealand Class A statement
European Union EMC Directive conformance
statement. . . . . . . . . . . . . .
Germany Class A statement . . . . . . .
Japan VCCI Class A statement. . . . . . .
Japan Electronics and Information Technology
Industries Association (JEITA) statement . . .
Korea Communications Commission (KCC)
statement. . . . . . . . . . . . . .
Russia Electromagnetic Interference (EMI) Class
A statement . . . . . . . . . . . . .
People's Republic of China Class A electronic
emission statement . . . . . . . . . .
Taiwan Class A compliance statement . . . .
674
674
675
676
677
677
677
677
677
678
678
678
679
680
680
680
680
681
Index . . . . . . . . . . . . . . . 683
Contents
vi
Safety
Before installing this product, read the Safety Information.
Antes de instalar este produto, leia as Informaes de Segurana.
Ls sikkerhedsforskrifterne, fr du installerer dette produkt.

Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.
Ennen kuin asennat tmn tuotteen, lue turvaohjeet kohdasta Safety Information.
Avant d'installer ce produit, lisez les consignes de scurit.
Vor der Installation dieses Produkts die Sicherheitshinweise lesen.
Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.
vii
Les sikkerhetsinformasjonen (Safety Information) fr du installerer dette produktet.
Antes de instalar este produto, leia as Informaes sobre Segurana.
Antes de instalar este producto, lea la informacin de seguridad.

Ls skerhetsinformationen innan du installerar den hr produkten.
Bu rn kurmadan nce gvenlik bilgilerini okuyun.
viii
Guidelines for trained service technicians

This section contains information for trained service technicians.
Inspecting for unsafe conditions

Use this information to help you identify potential unsafe conditions in an IBM
product that you are working on.
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 cords are disconnected.
2. Make sure that the exterior cover is not damaged, loose, or broken, and observe
any sharp edges.
3. Check the power cords:
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 cords are the correct type.
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 system 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.
Safety
ix
Guidelines for servicing electrical equipment

Observe these 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.
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
These statements provide the caution and danger information that is used in this
documentation.
Important:
Each caution and danger statement in this documentation 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 documentation before you
perform the procedures. Read any additional safety information that comes with
your system or optional device before you install the device.
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.
1. Turn everything OFF.
2. First, attach all cables to devices.
2. First, remove power cords from outlet.
3. Attach signal cables to connectors.
3. Remove signal cables from connectors.
4. Attach power cords to outlet.
4. Remove all cables from devices.
5. Turn device ON.

Safety
xi
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 100C (212F)
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.
xii
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.
Class 1 Laser Product

Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
Appareil A` Laser de Classe 1
Statement 4
CAUTION:
Use safe practices when lifting.
18 kg (39.7 lb)
32 kg (70.5 lb)
55 kg (121.2 lb)
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.
2
1
Safety
xiii
Statement 6
CAUTION:
If you install a strain-relief bracket option over the end of the power cord that is
connected to the device, you must connect the other end of the power cord to an
easily accessible power source.
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 12
CAUTION:
The following label indicates a hot surface nearby.
Statement 26
xiv
CAUTION:
Do not place any object on top of rack-mounted devices.
Statement 27
CAUTION:
Hazardous moving parts are nearby.
Rack Safety Information, Statement 2
DANGER
v Always lower the leveling pads on the rack cabinet.
v Always install stabilizer brackets on the rack cabinet.
v Always install servers and optional devices starting from the bottom of the
rack cabinet.
v Always install the heaviest devices in the bottom of the rack cabinet.
Safety
xv
xvi
Chapter 1. The IBM System x3530 M4 7160 server

This Installation and Service Guide contains information and instructions for setting
up yourIBM System x3530 M4 Type 7160 server, instructions for installing some
optional devices, cabling and configuring the server, removing and replacing
devices, and diagnostics and troubleshooting information.
In addition to the instructions in Chapter 2, Installing optional devices, on page
25 for installing optional hardware devices, updating firmware and device drivers,
and completing the installation, IBM Business Partners must also complete the
steps in Instructions for IBM Business Partners on page 26.
The IBM System x3530 M4 7160 is a 1-U-high rack model, two-socket server for
virtualization, database, and computational intensive computing. It is the next
generation enterprise server based on Intel's Romley-EN technology. This
high-performance, scalable server is ideally suited for enterprise environments that
require superior input/output (I/O) flexibility, scalability, and high manageability.
Performance, ease of use, reliability, and expansion capabilities were key
considerations in the design of the server. These design features make it possible
for you to customize the system hardware to meet your needs today and provide
flexible expansion capabilities for the future.
The server comes with a limited warranty. For information about the terms of the
warranty and getting service and assistance, see the IBM Warranty Information
document that comes with the server.
The server contains IBM next generation technologies, which help increase
performance and reliability. For more information, see What your server offers
on page 9 and Reliability, availability, and serviceability on page 13.
You can obtain up-to-date information about the server and other IBM server
products at http://www.ibm.com/systems/x/. At http://www.ibm.com/support/
mysupport/, you can create a personalized support page by identifying IBM
products that are of interest to you. From this personalized page, you can subscribe
to weekly e-mail notifications about new technical documents, search for
information and downloads, and access various administrative services.
If you participate in the IBM client reference program, you can share information
about your use of technology, best practices, and innovative solutions; build a
professional network; and gain visibility for your business. For more information
about the IBM client reference program, see http://www.ibm.com/ibm/
clientreference/.
The server supports up to eight 2.5-inch simple-swap or hot-swap drives, or four
3.5-inch simple-swap or hot-swap drives, using the supported drive backplane
configurations. It supports 2.5-inch hot-swap Serial Attached SCSI (SAS) or SATA
hard disk drives, 2.5-inch simple-swap SATA or solid-state hard disk drives,
3.5-inch hot-swap SAS or SATA hard disk drives, or 3.5-inch simple-swap SATA
hard disk drives. The illustrations in this document might differ slightly from your
hardware.
Note: The simple-swap models do not support hard disk drive status reporting
with system management features. Hard disk drive status reporting can be
managed by ServeRAID software. See the RAID documentation in the IBM
ServeRAID Support CD for information about RAID controllers.
The following illustration shows the front of the server model with eight 2.5-inch
hot-swap hard disk drive bays.
Operator
information panel
Rack release
USB 1
USB 2
Video
Drive bay 0 Drive bay 2 Drive bay 4 Drive bay 6
latch
connector connector connector
Rack release latch

Drive activity LED
(green)
Drive status LED

(yellow)
Power control
button
and
power - on
LED
Optional optical
drive eject button
Optional
optical drive
activity LED
Figure 1. Front view: 2.5-inch model
The following illustration shows the front of the server model with four 3.5-inch
hot-swap hard disk drive bays.
Rack release
latch
Operator
USB 1
USB 2
information panel connector connector
Video connector (optional)
Rack release latch
Drive bay 0
Drive bay 1
Drive bay 2
Drive bay 3
Figure 2. Front view: 3.5-inch model
If firmware and documentation updates are available, you can download them
from the IBM website. The server might have features that are not described in the
documentation that comes with the server, and the documentation might be
updated occasionally to include information about those features, or technical
updates might be available to provide additional information that is not included
in the server documentation. To check for updates, go to http://www.ibm.com/
supportportal/.
Record information about the server in the following table.
Product name
Machine type
Model number
Serial number
IBM System x3530 M4

7160
_____________________________________________
_____________________________________________
The model number and serial number are on the ID label on the front of the
server. The location of the ID label differs depending on your service model, as
shown in the following illustrations.
Note: The illustrations in this document might differ slightly from your hardware.
ID label
Figure 3. ID label
In addition, the system service label, which is on the cover of the server, provides a
QR code for mobile access to service information. You can scan the QR code using
a QR code reader and scanner with a mobile device and get quick access to the
IBM Service Information website. The IBM Service Information website provides
additional information for parts installation and replacement videos, and error
codes for server support.
The following illustration shows the QR code (ibm.co/18TTiiG):
Figure 4. QR code
You can download an IBM ServerGuide Setup and Installation CD to help you
configure the hardware, install device drivers, and install the operating system.
For a list of supported optional devices for the server, see http://www.ibm.com/
systems/info/x86servers/serverproven/compat/us/.
See the Rack Installation Instructions document on the IBM Documentation CD for
complete rack installation and removal instructions.
The IBM Documentation CD

The IBM Documentation CD contains documentation for the server in Portable
Document Format (PDF) and includes the IBM Documentation Browser to help
you find information quickly.
Hardware and software requirements

The hardware and software requirements of the IBM Documentation CD.
v Microsoft Windows XP, Windows 2000, or Red Hat Linux
v 100 MHz microprocessor
v 32 MB of RAM
v Adobe Acrobat Reader 3.0 (or later) or xpdf, which comes with Linux operating
systems
Using the Documentation Browser

Use the Documentation Browser to browse the contents of the CD, read brief
descriptions of the documents, and view documents, using Adobe Acrobat Reader
or xpdf.
The Documentation Browser automatically detects the regional settings in use in
your server and displays the documents in the language for that region (if
available). If a document is not available in the language for that region, the
English-language version is displayed.
Use one of the following procedures to start the Documentation Browser:
v If Autostart is enabled, insert the CD into the CD or DVD drive. The
Documentation Browser starts automatically.
v If Autostart is disabled or is not enabled for all users, use one of the following
procedures:
If you are using a Windows operating system, insert the CD into the CD or
DVD drive and click Start -> Run. In the Open field, type
e:\win32.bat
where e is the drive letter of the CD or DVD drive, and click OK.
If you are using Red Hat Linux, insert the CD into the CD or DVD drive;
then, run the following command from the /mnt/cdrom directory:
sh runlinux.sh
Select the server from the Product menu. The Available Topics list displays all the
documents for the server. Some documents might be in folders. A plus sign (+)
indicates each folder or document that has additional documents under it. Click
the plus sign to display the additional documents.
When you select a document, a description of the document is displayed under
Topic Description. To select more than one document, press and hold the Ctrl key
while you select the documents. Click View Book to view the selected document
or documents in Acrobat Reader or xpdf. If you selected more than one document,
all the selected documents are opened in Acrobat Reader or xpdf.
To search all the documents, type a word or word string in the Search field and
click Search. The documents in which the word or word string appears are listed
in order of the most occurrences. Click a document to view it, and press Crtl+F to
use the Acrobat search function, or press Alt+F to use the xpdf search function
within the document.
Click Help for detailed information about using the Documentation Browser.
Related documentation
This Installation and Service Guide contains general information about the server
including how to set up and cable the server, how to install supported optional
devices, how to configure the server, and information to help you solve problems
yourself and information for service technicians.
The following documentation also comes with the server:
v Warranty Information:
This document is in printed format and comes with the server. It contains
warranty terms and a pointer to the IBM Statement of Limited Warranty on the
IBM website.
v Important Notices:
This document is in printed format and comes with the server. It contains
information about the safety, environmental, and electronic emission notices for
your IBM product.
v Environmental Notices and User Guide:
This document is in PDF format on the IBM Documentation CD. It contains
translated environmental notices.
v IBM License Agreement for Machine Code:
This document is in PDF on the IBM Documentation CD. It provides translated
versions of the IBM License Agreement for Machine Code for your product.
v Licenses and Attributions Document:
This document is in PDF on the IBM Documentation CD. It provides the open
source notices.
v Safety Information
This document is in PDF on the IBM Documentation CD. It 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 Safety Information document.
v Rack Installation Instructions
This printed document contains instructions for installing the server in a rack.
Depending on the server model, additional documentation might be included on
the IBM Documentation CD.
The ToolsCenter for System x and BladeCenter is an online information center that
contains information about tools for updating, managing, and deploying firmware,
device drivers, and operating systems. The ToolsCenter for System x and
BladeCenter is at http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/
index.jsp.
The server might have features that are not described in the documentation that
you received with the server. The documentation might be updated occasionally to
include information about those features, or technical updates might be available
to provide additional information that is not included in the server documentation.
These updates are available from the IBM website. To check for updates, go to
http://www.ibm.com/supportportal/.
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.
Server features and specifications

The following information is a summary of the features and specifications of the
server. Depending on the model, some features might not be available, or some
specifications might not apply.
Table 1. Server features and specifications
Microprocessor (depending on the
model):
v Supports one Intel Pentium 1400
series microprocessor or up to two
Intel Xeon EN E5-2400 series
microprocessors
v Up to 20 MB Level-3 cache
v One QuickPath Interconnect (QPI)
link speed up to 8 Giga Transfers
(GT) per second
v Scalable up to eight cores
v Three memory channels per
microprocessor on the system
board that supports two DIMMs
per channel
Memory (depending on the model):

v Slots: 12 dual inline memory
module connectors
v Minimum: 2 GB
v Maximum: up to 192 GB
v Type: DDR3-1066 (PC3-8500),
DDR3-1333 (PC3-10600), or
DDR3-1600 (PC3-12800), ECC,
single-rank or dual-rank, DDR3
registered or unbuffered SDRAM
DIMMs
v Supports:
UDIMM: 4 GB
RDIMM: 2 GB, 4 GB, 8 GB, 16
GB, or 32 GB (when available)
Note: For a list of supported

microprocessors, see
http://www.ibm.com/systems/info/
x86servers/serverproven/compat/
us/.
Drive expansion bays (depending

on the model):
v The server can support up to eight
2.5-inch drives or up to four
3.5-inch drives. The following
drives are supported:
v 2.5-inch hot-swap SAS/SATA hard
disk drive
v 2.5-inch simple-swap SATA or
solid-state hard disk drive
v 3.5-inch hot-swap SAS/SATA hard
disk drive
v 3.5-inch simple-swap SATA hard
disk drive
Note: For specific models that may
be shipped initially with four hard
disk drives, configuration may be
able to expand to eight hard disk
drives via Features on Demand
(FoD).
Table 1. Server features and specifications (continued)

Optional SATA optical drives
(depending on your model):
v DVD-ROM
v Multi-burner
Fans:
v The server comes standard with
four speed-controlled fans for
one-microprocessor configuration
v Supports up to six fans with two
microprocessors installed
PCI expansion slots (depending on
your model):
v Two x8 low-profile, PCIE 3.0
adapter slots on the system board
v One x16 (x16 mechanically) PCIE
3.0 adapter slot
v One x4 (x8 mechanically) PCIE 3.0
adapter slot on the optional PCI
riser-card for an optional RAID
adapter
Integrated functions:
v Integrated Management Module II
(IMM2), which provides service
processor control and monitoring
functions, video controller, and
remote keyboard, video, mouse,
and remote hard disk drive
capabilities
v Onboard Intel Powerville 4-port
Gigabit Ethernet controller with
Wake on LAN support (by default
Ethernet 1 and 2 are enabled, to
enable Ethernet 3 and 4, it is done
through the Features on Demand
(FoD))
v Onboard PCH with LSI software
RAID with support for RAID
levels 0, 1 and 10
v Light path diagnostics
v Seven Universal Serial Bus (USB)
2.0 ports:
Two on the front of the chassis
Four on the rear of the chassis
One internal
v One serial port
Note: In messages and
documentation, the term service
processor refers to the integrated
management module II (IMM2).
Power supply (depending on your

model):
v One fixed 460-watt ac power
supply
v Up to two 460-watt or 675-watt ac
hot-swap power supplies for 1+1
redundancy support
v Up to two 675-watt dc
Video controller (integrated into
IMM, depending on your model):
v Matrox G200eR2 (two analog ports
- one optional on front and one
rear that can be connected at the
same time)
Note: The maximum video
resolution is 1600 x 1200 at 60 or
75 Hz.
SVGA compatible video
controller
DDR2 250 MHz SDRAM video
memory controller
Avocent Digital Video
Compression
Video memory is not
expandable
Table 1. Server features and specifications (continued)

Environment:
v Air temperature:
The following RAID options are
Server on: 5C to 40C (41F to
available for the server:
104F); altitude: 0 to 915 m (3000
ft)
v ServeRAID H1110 SAS/SATA
Controller for System x
89.6F); altitude: 915 m (3000 ft)
v ServeRAID M1115 SAS/SATA
to 2134 m (7000 ft)
Controller for System x
82.4F); altitude: 2134 m (7000
Controller for IBM System x
ft) to 3050 m (10000 ft)
Server off: 5C to 45C (41 to
Controller for IBM System x
113F)
Shipment: -40C to +60C (-40F

v ServeRAID M5100 Series Battery
to 140F)
Kit for IBM System x
v Humidity:
v ServeRAID M5100 Series 512MB
Server on: 8% to 85%; maximum
Cache/RAID 5 Upgrade for IBM
dew point: 24C (75.2F);
System x
maximum rate of change 5
v ServeRAID M5100 Series 512MB
C/hr
Flash/RAID 5 Upgrade for IBM
Server off: 8% to 80%; maximum
System x
dew point: 27C (80F)
v ServeRAID M5100 Series Zero
Shipment: 5% to 100%
Cache/RAID 5 Upgrade for IBM
v Design to ASHRAE Class A3:
System x
Ambient of 35C to 40C (95F
to 104F), with relaxed support
v ServeRAID M5100 Series 1GB
Support cloud like workload

Flash/RAID Upgrade for IBM
with no performance
System x
degradation acceptable
v ServeRAID C105 for IBM System X
(Turbo-Off)
Under no circumstance, can any
Size:
combination of worst case
v Height: 43 mm ( 1.7 inches, 1U)
workload and configuration
v Depth: 673.1 mm (26.5 inches)
result in system shutdown or
v Width: 447 mm (17.6 inches)
design exposure at 40C (104F)
v Maximum weight: 15.8 kg (33.8 lb)
v Particulate contamination:
when fully configured
Attention: Airborne particulates
Acoustical noise emissions:
and reactive gases acting alone or
v Sound power, idling: 6.5 bels
in combination with other
v Sound power, operating: 6.5 bels
environmental factors such as
humidity or temperature might
pose a risk to the server. For
information about the limits for
particulates and gases, see
Particulate contamination on
page 675.
RAID controllers:
Heat output:
Approximate heat output:
v Minimum configuration: 406 Btu
per hour (119 watts)
v Maximum configuration: 2627.3
Btu per hour (770 watts)
Electrical input:
v Sine-wave input (50 - 60 Hz)
required
v Input voltage automatically
selected
v Input voltage low range:
Minimum: 100 V ac
Maximum: 127 V ac
v Input voltage high range:
Minimum: 200 V ac
Maximum: 240 V ac
v Input kilovolt-amperes (kVA),
approximately:
Minimum: 0.12 kVA
Maximum: 0.78 kVA
Notes:
1. Power consumption and heat
output vary depending on the
number and type of optional
features installed and the
power-management optional
features in use.
2. The noise emission level stated is
the declared (upper limit) sound
power level, in bels, for a random
sample of machines. All
measurements are made in
accordance with ISO 7779 and
reported in conformance with ISO
9296.
What your server offers

The server uses the following features and technologies.
v Active Energy Manager
The IBM Active Energy Manager solution is an IBM Systems Director extension
that measures and reports server power consumption as it occurs. This enables
you to monitor power consumption in correlation to specific software
application programs and hardware configurations. You can obtain the
measurement values through the systems-management interface and view them,
using IBM Systems Director. For more information, including the required levels
of IBM Systems Director and Active Energy Manager, see the IBM Systems
Director documentation on the IBM Systems Director DVD, or see
http://www.ibm.com/servers/systems/management/director/extensions/
actengmgr.html/.
v Dynamic System Analysis (DSA) Preboot
The server comes with the IBM Dynamic System Analysis (DSA) Preboot
diagnostic program stored in the integrated USB memory on the server. DSA
Preboot collects and analyzes system information to aid in diagnosing server
problems, as well as offering a rich set of diagnostic tests of the major
components of the server. DSA Preboot collects the following information about
the server:
Drive health information
Event logs for ServeRAID controllers and service processors
Hardware inventory, including PCI and USB information

Light path diagnostics status
Microprocessor, input/out hub, and UEFI error logs
Network interfaces and settings
RAID controller configuration

Service processor (integrated management module) status and configuration
System configuration
Vital product data, firmware, and UEFI configuration
DSA Preboot also provides diagnostics for the following system components
(when they are installed):
Intel network adapter
IMM I2C bus
Light path diagnostics panel
Memory modules
Microprocessors
Optical devices (CD or DVD)
SAS or SATA drives
For information about both editions (DSA Preboot and Portable) of the Dynamic
System Analysis (DSA) diagnostic programs, see DSA editions on page 134.
v IBM ServerGuide Setup and Installation CD
The ServerGuide Setup and Installation CD, which you can download from the
Web, provides programs to help you set up the server and install a Windows
operating system. The ServerGuide program detects installed optional hardware
devices and provides the correct configuration programs and device drivers. For
more information about the ServerGuide Setup and Installation CD, see Using the
ServerGuide Setup and Installation CD on page 86.
v IBM Systems Director DVD

IBM Systems Director is a platform-management foundation that streamlines the
way you manage physical and virtual systems in a heterogeneous environment.
By using industry standards, IBM Systems Director supports multiple operating
systems and virtualization technologies for IBM and non-IBM x86 platforms. For
more information, see the IBM Systems Director documentation on the IBM
Systems Director DVD and IBM Systems Director on page 14.
v Integrated Management Module II (IMM2)
The Integrated Management module II (IMM2) combines service processor
functions, video controller, and remote presence and blue-screen capture features
in a single chip. The IMM2 provides advanced service-processor control,
monitoring, and alerting function. If an environmental condition exceeds a
threshold or if a system component fails, the IMM lights LEDs to help you
diagnose the problem, records the error in the IMM2 event log, and alerts you to
the problem. Optionally, the IMM2 also provides a virtual presence capability for
remote server management capabilities. The IMM2 provides remote server
management through the following industry-standard interfaces:
Intelligent Platform Management Interface (IPMI) version 2.0
Simple Network Management Protocol (SNMP) version 3.0
Common Information Model (CIM)
Web browser
For additional information, see Using the integrated management module II
on page 95 and the Integrated Management Module II Users Guide at the
http://www.ibm.com/supportportal.
v Integrated network support
The server comes with an integrated 4-port (2 ports by default, 2 ports by
upsell) Gigabit Ethernet controller, which supports connection to a 10 Mbps, 100
Mbps, or 1000 Mbps network. For more information, see Configuring the
Gigabit Ethernet controller on page 100.
v Integrated Trusted Platform Module (TPM)
This integrated security chip performs cryptographic functions and stores
private and public secure keys. It provides the hardware support for the Trusted
Computing Group (TCG) specification. You can download the software to
support the TCG specification, when the software is available. See
http://www.ibm.com/servers/eserver/xseries/scalable_family.html for details
about the TPM implementation. You can enable TPM support through the Setup
utility under the System Security menu choice (seeUsing the Setup utility on
page 88).
v Large data-storage capacity and hot-swap capability
The server can support a maximum of eight 2.5-inch drives or four 3.5-inch
drives. The server supports 2.5-inch hot-swap SAS/SATA hard disk drives, or
3.5-inch simple-swap SATA or hot-swap SAS/SATA hard disk drives.
With the hot-swap feature, you can add, remove, or replace hard disk drives
without turning off the server.
v Large system-memory capacity
The server system board provides 12 DIMM connectors for up to 192 GB of
memory.
The server memory controller supports error correcting code (ECC) for up to 12
industry-standard DDR3-1066 (PC3-8500), DDR3-1333 (PC3-10600), DDR3-1600
(PC3-12800) (single-rank or dual-rank), DDR3 (third-generation
10
double-data-rate), registered or unbuffered, synchronous dynamic random access

memory (SDRAM) dual inline memory modules (DIMMs).
Light path diagnostics provides LEDs to help you diagnose problems. For more
information about the light path diagnostics and the LEDs, see Light path
diagnostics panel on page 18 and Light path diagnostics LEDs on page 123.
v Mobile access to IBM Service Information website
The server provides a QR code on the system service label, which is on the
cover of the server, that you can scan using a QR code reader and scanner with
a mobile device to get quick access to the IBM Service Information website. The
IBM Service Information website provides additional information for parts
installation and replacement videos, and error codes for server support. For the
QR code, see Chapter 1, The IBM System x3530 M4 7160 server, on page 1.
v Multi-core processors
Depending on your server model, the server supports one Intel Pentium 1400
series microprocessor or up to two Intel Xeon EN E5-2400 series
microprocessors.
v PCI Express adapter capabilities
The system board provides up to three PCIe connectors for two PCI riser-card
assemblies. See Installing an adapter on page 51 for detailed information.
v Redundant connection
The Intel Gigabit Ethernet controller provides failover capability to a redundant
Ethernet connection with the applicable application installed. If a problem occurs
with the primary Ethernet connection and the optional Ethernet adapter is
installed in the server, all Ethernet traffic that is associated with the primary
connection is automatically switched to an optional Ethernet connection. If the
applicable device drivers are installed, this switching occurs without data loss
and without user intervention.
A feature upgrade key is required to enable ports 3 and 4 on the Gigatbit
Ethernet controller. See /http://www.ibm.com/systems/x/fod/ for detailed
information on product feature activation.
v Cooling and optional power capabilities
The server supports up to six speed-controlled simple-swap fans for a full
configuration.
The server comes with one fixed 460-watt, or one hot-swap 460-watt or 675-watt
power supply installed. The server supports a maximum of two 460-watt or two
675-watt hot-swap power supplies.
For redundancy support on hot-swap models, two power-supplies must be
installed in the server. Two power supplies enables continued operation if one of
the power supplies fails.
v Remote presence and blue-screen capture features
The blue-screen capture feature is an integrated function of the integrated
management module (IMM).
The blue-screen capture feature captures the video display contents before the
IMM restarts the server when the IMM detects an operating-system hang
condition. A system administrator can use the blue-screen capture feature to
assist in determining the cause of the hang condition.
You can activate the optional remote presence feature in the IMM Premium only
to use the following functions: .
Remotely viewing video with graphics resolutions up to 1600 x 1200 at 60 or
75 Hz, regardless of the system state
11
Remotely accessing the server, using the keyboard and mouse from a remote
client
Mapping the CD or DVD drive, diskette drive, and USB flash drive on a
remote client, and mapping ISO and diskette image files as virtual drives that
are available for use by the server
Uploading a diskette image to the IMM memory and mapping it to the server
as a virtual drive
For information on product feature activation, see /http://www.ibm.com/
systems/x/fod/
See Using the remote presence and blue-screen capture features on page 98 for
additional information.
v ServeRAID support
A ServeRAID adapter provides hardware redundant array of independent disks
(RAID) support to create configurations. The server comes with an onboard
RAID controller which provides RAID levels 0 and 1. Additional optional RAID
adapters are available for purchase that provide RAID level 5.
v Service Advisor
The server comes with the Service Advisor feature that can collect data about the
system when a the system detects a fault and sends that data to IBM Service for
problem determination. It also includes the call home feature that automatically
calls IBM Service when a problem occurs. The Service Advisor feature is
integrated into the Integrated Management Module (IMM). You will need to
setup and configure the Service Advisor feature before you can use it. For more
information about how to setup and configure the Service Advisor feature, see
the Integrated Management Module User's Guide at http://www.ibm.com/
supportportal.
v Systems-management capabilities
The server comes with an integrated management module (IMM). When the
IMM is used with the systems-management software that comes with the server,
you can manage the functions of the server locally and remotely. The IMM also
provides system monitoring, event recording, and network alert capability. The
systems-management connector on the rear of the server is dedicated to the
IMM. The dedicated systems-management connector provides additional
security by physically separating the management network traffic from the
production network. You can use the Setup utility to configure the server to use
a dedicated systems-management network or a shared network.
v UEFI-compliant server firmware
The UEFI firmware offers several features, including Unified Extensible
Firmware Interface (UEFI) version 2.1 compliance, Active Energy Management
(AEM) technology, enhanced reliability, availability, and serviceability (RAS)
capabilities, and basic input/output system (BIOS) compatibility support. UEFI
replaces the BIOS and defines a standard interface between the operating
system, platform firmware, and external devices. The server is capable of
booting UEFI-compliant operating systems, BIOS-based operating systems, and
BIOS-based adapters as well as UEFI-compliant adapters. For more information
about UEFI-compliant firmware, go to http://www.ibm.com/support/entry/
portal/docdisplay?lndocid=MIGR-5083207.
Note: The server does not support DOS.
v VMware ESXi embedded hypervisor
An optional USB flash device with VMware ESXi embedded hypervisor software
is available for purchase. Hypervisor is virtualization software that enables
12
multiple operating systems to run on a host system at the same time. See Using
the embedded hypervisor on page 97 for additional information.
Reliability, availability, and serviceability

Three important computer design features are reliability, availability, and
serviceability (RAS). The RAS features help to ensure the integrity of the data that
is stored in the server, the availability of the server when you need it, and the ease
with which you can diagnose and correct problems.
Your server has the following RAS features:
v 3-year parts and 3-year labor limited warranty (Machine Type 7160)
v 24-hour support center
v Automatic error retry and recovery
v Automatic restart on nonmaskable interrupt (NMI)
v Automatic restart after a power failure
v Backup basic input/output system switching under the control of the integrated
management module (IMM)
v Built-in monitoring for fan, power, temperature, voltage, and power-supply
redundancy
v Cable-presence detection on most connectors
v Chipkill memory protection
v Diagnostic support for ServeRAID and Ethernet adapters
v Error codes and messages
v Error correcting code (ECC) L3 cache and system memory
v Full Array Memory Mirroring (FAMM) redundancy
v Hot-swap hard disk drives
v Operator information and light path diagnostics LED panels
v Integrated Management Module (IMM)
v Light path diagnostics LEDs for memory DIMMs, microprocessors, hard disk
drives, power supplies, and fans
v Memory mirroring and memory sparing support
v Memory error correcting code and parity test
v Memory down sizing (non-mirrored memory). After a restart of the server after
the memory controller detected a non-mirrored uncorrectable error and the
memory controller cannot recover operationally, the IMM logs the uncorrectable
error and informs POST. POST logically maps out the memory with the
uncorrectable error, and the server restarts with the remaining installed memory.
v Menu-driven setup, system configuration, and redundant array of independent
disks (RAID) configuration programs
v Microprocessor built-in self-test (BIST), internal error signal monitoring, internal
thermal trip signal monitoring, configuration checking, and microprocessor and
voltage regulator module failure identification through light path diagnostics
v Nonmaskable interrupt (NMI) button
v Parity checking on the small computer system interface (SCSI) bus and PCI-E
buses
v Power management: Compliance with Advanced Configuration and Power
Interface (ACPI)
v Power-on self-test (POST)
v Predictive Failure Analysis (PFA) alerts on memory, microprocessors, SAS/SATA
hard disk drives or solid state drives, fans, power supplies, and VRM
v Redundant Ethernet capabilities with failover support
v Redundant hot-swap power supplies
v Redundant network interface card (NIC) support
v Remind button to temporarily turn off the system-error LED on the optional
advanced operator information panel
13
v ROM-based diagnostics
v ROM checksums
v Serial Presence Detection (SPD) on memory, VPD on system board, power
supply, and hard disk drive or solid state drive backplanes, microprocessor and
memory expansion tray, and Ethernet cards
v Single-DIMM isolation of excessive correctable error or multi-bit error by the
Unified Extensible Firmware Interface (UEFI)
v Standby voltage for system-management features and monitoring
v Startup (boot) from LAN through remote initial program load (RIPL) or dynamic
host configuration protocol/boot protocol (DHCP/BOOTP)
v System auto-configuring from the configuration menu
v System-error logging (POST and IMM)
v Systems-management monitoring through the Inter-Integrated Circuit (I2C)
protocol bus
v Uncorrectable error (UE) detection
v Upgradeable POST, Unified Extensible Firmware Interface (UEFI), diagnostics,
IMM firmware, and read-only memory (ROM) resident code, locally or over the
LAN
v Vital product data (VPD) on microprocessors, system board, power supplies, and
SAS/SATA (hot-swap hard disk drive) backplane
v Wake on LAN capability
IBM Systems Director

IBM Systems Director is a platform-management foundation that streamlines the
way you manage physical and virtual systems in a heterogeneous environment. By
using industry standards, IBM Systems Director supports multiple operating
systems and virtualization technologies in IBM and non-IBM x86 platforms.
Through a single user interface, IBM Systems Director provides consistent views
for viewing managed systems, determining how these systems relate to one other,
and identifying their statuses, helping to correlate technical resources with business
needs. A set of common tasks that are included with IBM Systems Director
provides many of the core capabilities that are required for basic management,
which means instant out-of-the-box business value. The common tasks include the
following:
v Discovery
v Inventory
v Configuration
v System health
v Monitoring
v Updates
v Event notification
v Automation for managed systems
The IBM Systems Director Web and command-line interfaces provide a consistent
interface that is focused on driving these common tasks and capabilities:
v Discovering, navigating, and visualizing systems on the network with the
detailed inventory and relationships to the other network resources
v Notifying users of problems that occur on systems and the ability to isolate the
sources of the problems
v Notifying users when systems need updates and distributing and installing
updates on a schedule
14
v Analyzing real-time data for systems and setting critical thresholds that notify
the administrator of emerging problems
v Configuring settings of a single system and creating a configuration plan that
can apply those settings to multiple systems
v Updating installed plug-ins to add new features and functions to the base
capabilities
v Managing the life cycles of virtual resources
For more information about IBM Systems Director, see the IBM Systems Director
Information Center at http://pic.dhe.ibm.com/infocenter/director/pubs/
index.jsp?topic=%2Fcom.ibm.director.main.helps.doc%2Ffqm0_main.html, and the
Systems Management web page at http://www.ibm.com/systems/management,
which presents an overview of IBM Systems Management and IBM Systems
Director.
Server controls, LEDs, and power

This section describes the controls and light-emitting diodes (LEDs) and how to
turn the server on and off.
For the locations of other LEDs on the system board, see System-board LEDs on
page 30.
Front view
The following illustration shows the controls, LEDs, and connectors on the front of
the hot-swap server model.
The following illustration shows the controls, LEDs, and connectors on the front of
the hot-swap server model.
Operator
information panel
Rack release
USB 1
USB 2
Video
latch
Rack release latch

Drive activity LED
(green)
Drive status LED

(yellow)
Power control
button
and
power - on
LED
Optional optical
drive eject button
Optional
optical drive
activity LED
Figure 5. Front view of server
v Rack release latches: Press the latches on each front side of the server to slide it
out of the rack.
v Hard disk drive status LEDs: These LEDs are used on hot-swap SAS or SATA
hard disk drives. When one of these LED are lit, it indicates that the drive has
failed. If an optional IBM ServeRAID controller is installed in the server, when
this LED is flashing slowly (one flash per second), it indicates that the drive is
being rebuilt. When the LED is flashing rapidly (three flashes per second), it
indicates that the controller is identifying the drive.
v Hard disk drive activity LEDs: These LEDs are used on SAS or SATA hard disk
drives. Each hot-swap drive has an activity LED, and when this LED is flashing,
it indicates that the drive is in use.
15
v CD-RW/DVD eject button (Optional): Press this button to release a DVD or CD

from the CD/DVD drive.
v CD-RW/DVD drive activity LED (Optional): When this LED is lit, it indicates
that the CD-RW/DVD drive is in use.
v Operator information panel: This panel contains controls and LEDs that provide
information about the status of the server. For information about the controls
and LEDs on the operator information panel, see Operator information panel.
v Operator information panel release button (Optional): This release button is on
the advanced operator information panel. Push the blue release button and pull
out the light path diagnostics panel to view the light path diagnostics LEDs and
buttons. See Operator information panel, Light path diagnostics on page
120, and Light path diagnostics LEDs on page 123 for more information about
light path diagnostics.
v Video connector: Connect a monitor to this connector. The video connectors on
the front and rear of the server can be used simultaneously.
Note: The maximum video resolution is 1600 x 1200 at 75 Hz.
v USB connectors: Connect a USB device, such as a USB mouse, keyboard, or
other device, to any of these connectors.
Operator information panel

The following illustrations show the location of the operator information panel and
the LEDs on the operator information panel respectively.
Figure 6. Operator information panel
16
v Power-control button and power-on LED: Press this button to turn the server
on and off manually or to wake the server from a reduced-power state. The
states of the power-on LED are as follows:
Off: AC power is not present, or the power supply or the LED itself has
failed.
Flashing rapidly (4 times per second): The server is turned off and is not
ready to be turned on. The power-control button is disabled. This lasts
approximately 1 to 3 minutes.
Flashing slowly (once per second): The server is turned off and is ready to
be turned on. You can press the power-control button to turn on the server.
Lit: The server is turned on.
Fading on and off: The server is in a reduced-power state. To wake the
server, press the power-control button or use the IMM web interface. See
Logging on to the Web interface on page 99 for information on logging on
to the IMM web interface.
v Ethernet activity LEDs: When any of these LEDs is flashing or flickering, it
indicates that the server is transmitting to or receiving signals from the Ethernet
LAN that is connected to the Ethernet port that corresponds to that LED.
v Locator button/LED: Use this blue LED to visually locate the server among
other servers. This LED is also used as a presence detection button. You can use
IBM Systems Director to light this LED remotely. This LED is controlled by the
IMM. When you press the locator button, the LED will be lit and it will continue
to be lit until you press it again to turn it off. Press the locator button to visually
locate the server among the others servers. It is also used as the physical
presence for the Trusted Platform Module (TPM).
v Log LED: When this yellow LED is lit, it indicates that a noncritical event has
occurred. Check the system-event log for additional information. See Error
messages on page 137 for more information about event logs.
v System-error LED: When this yellow LED is lit, it indicates that a system error
has occurred. A system-error LED is also on the rear of the server. An LED on
the light path diagnostics panel on the operator information panel is also lit to
help isolate the error. This LED is controlled by the IMM.
v Reset button: Press this button to reset the server and run the power-on self-test
(POST). You might have to use a pen or the end of a straightened paper clip to
press the button.
Note: All the operator information is on the operator information panel already.
You do not need to pull the panel out for obtaining more information.
17

The following illustration shows the optional advanced light path diagnostics
panel.
The light path diagnostics panel is available on the top of the advanced operator
information panel. For additional information about the light path diagnostics and
LEDs on the light path diagnostics panel, see Light path diagnostics on page 120
and Light path diagnostics LEDs on page 123.
Power-control button/
power-on LED
System locator
LED
Ethernet activities
LEDs
System-error
LED
Check log
LED
Operator information
panel
Light path
diagnostics LEDs
Release button
Figure 7. Light path diagnostics panel
To access the optional advanced light path diagnostics panel, push the blue release
button on the advanced operator information panel. Pull forward on the unit until
the hinge of the operator panel is free of the server chassis. Then pull down on the
unit, so that you can view the light path diagnostics panel information.
Note: When you slide the optional advanced light path diagnostics panel out of
the server to check the LEDs, do not run the server continuously with light path
diagnostics panel outside of the server. The panel should only be outside of the
server a short time. The optional advanced light path diagnostics panel must
remain in the server when the server is running to ensure proper cooling.
The following illustration shows the LEDs and controls on the light path
diagnostics panel.
18
Figure 8. LEDs and controls on the light path diagnostics panel
v Remind button: This button places the system-error/Check Log LED on the
front panel into Remind mode. In Remind mode, the system-error LED flashes
once every 2 seconds until the problem is corrected, the server is restarted, or a
new problem occurs.
By placing the system-error LED indicator in Remind mode, you acknowledge
that you are aware of the last failure but will not take immediate action to
correct the problem.
press the button.
Rear view
The following illustrations show the connectors and LEDs on the rear of the server.
The following illustrations show the connectors on the rear of the server.
19
Figure 9. Rear view of server
20
The following illustrations show the locations of the power-supply LEDs for fixed
and redundant models respectively on the rear of the server.
AC LED (green)
DC LED (green)
Power - supply
error LED (yellow)
AC LED (green)
DC LED (green)
Power - supply
error LED (yellow)
Ethernet link
LED
Ethernet
activity LED
Figure 10. The LEDs on the rear of the server
v PCI riser slot 1: Insert a full-height, half-length PCI Express adapter into this
slot. See Installing an adapter on page 51 for the supported adapters for these
riser-cards.
v PCI riser slot 2: Insert a low-profile PCI Express adapter into this slot. See
Installing an adapter on page 51 for information about adapters that this riser
card support.
v Power connector: Connect the power cord to this connector.
v AC power LED: Each power supply has an ac power LED and a dc power LED.
When the ac power LED is lit, it indicates that sufficient power is being supplied
to the power supply through the power cord. During normal operation, both the
ac and dc power LEDs are lit. For any other combination of LEDs, see
Power-supply LEDs on page 129.
v DC power LED: Each power supply has a dc power LED and an ac power LED.
When the dc power LED is lit, it indicates that the power supply is supplying
adequate dc power to the system. During normal operation, both the ac and dc
power LEDs are lit. For any other combination of LEDs, see Power-supply
LEDs on page 129.
v Power-supply error LED: Each power supply has an ac power LED and a dc
power LED. When the power-supply error LED is lit, it indicates that the power
supply has failed.
v Video connector: Connect a monitor to this connector. The video connectors on
the front and rear of the server can be used simultaneously.
Note: The maximum video resolution is 1600 x 1200 at 75 Hz.
v Serial connector: Connect a 9-pin serial device to this connector. The serial port
is shared with the integrated management moduleII (IMM2). The IMM2 can take
control of the shared serial port to redirect serial traffic, using Serial over LAN
(SOL).
v USB connectors: Connect a USB device to any of these connectors.
21
v Ethernet activity LEDs: When these LEDs are lit, they indicate that the server is
transmitting to or receiving signals from the Ethernet LAN that is connected to
the Ethernet port.
v Ethernet link LEDs: When these LEDs are lit, they indicate that there is an
active link connection on the 10BASE-T, 100BASE-TX, or 1000BASE-TX interface
for the Ethernet port.
v Ethernet and system-management connectors:
IMM2 dedicated mode (default): In this mode, which is the default setting for
the server, the Ethernet 2 connector connects to a network for full
systems-management information control. A dedicated management network
provides additional security by physically separating the management
network traffic from the production network. Meanwhile, the Ethernet 1,
Ethernet 3 and Ethernet 4 connectors are used to connect to the production
network. See Using the Setup utility on page 88for more information.
IMM2 shared mode : In this mode, the Ethernet 1 connector is used to
connect to a network for full systems-management information control and
production network. See Using the Setup utility on page 88 for more
information.
Note: The IMM2 network must operate at 100 Mbps full duplex. The IMM2
network connection does not support Gigabit Ethernet. However, in shared
mode the production Ethernet network still operates at Gigabit speeds.
Table 2. UEFI settings for remote access to the IMM
UEFI mode
Ethernet Port 1
Ethernet Port 2
Ethernet Port 3
(optional)
Ethernet Port 4
(optional)
IMM network
interface port
dedicated
(default)
Production
Ethernet
IMM2 dedicated
(please see note)
Production
Ethernet
Production
Ethernet
IMM network
interface port
shared
Shared Production Gb
Ethernet and
IMM2 (please
see note)
Production
Ethernet
Production
Ethernet
Production
Ethernet
Note:
v The IMM network is limited to 100 Mbps full duplex.
22
Server power features

When the server is connected to a suitable input source but is not turned on, the
operating system does not run, and all core logic except for the service processor
(the integrated management module) is shut down.
However, the server can respond to requests to the service processor, such as a
remote request to turn on the server. The power-on LED flashes to indicate that the
server is connected to ac power but is not turned on.
Turning on the server

Use this information to turn on the server.
Approximately 5 seconds after the server is connected to ac power, one or more
fans might start running to provide cooling while the server is connected to power
and the power-on button LED will blink quickly. Approximately 1 to 3 minutes
after the server is connected to ac power, the power-control button becomes active
(the power-on LED will blink slowly), and one or more fans might start running to
provide cooling while the server is connected to power. You can turn on the server
by pressing the power-control button.
The server can also be turned on in any of the following ways:
v If a power failure occurs while the server is turned on, the server will restart
automatically when power is restored.
v If your operating system supports the Wake on LAN feature, the Wake on LAN
feature can turn on the server.
Note: When 4 GB or more of memory (physical or logical) is installed, some
memory is reserved for various system resources and is unavailable to the
operating system. The amount of memory that is reserved for system resources
depends on the operating system, the configuration of the server, and the
configured PCI options.
Turning off the server

Use this information to turn off the server.
When you turn off the server and leave it connected to ac power, the server can
respond to requests to the service processor, such as a remote request to turn on
the server. While the server remains connected to ac power, one or more fans
might continue to run. To remove all power from the server, you must disconnect
it from the power source.
Some operating systems require an orderly shutdown before you turn off the
server. See your operating-system documentation for information about shutting
down the operating system.
Statement 5
23
CAUTION:
2
1
The server can be turned off in any of the following ways:
v You can turn off the server from the operating system, if your operating system
supports this feature. After an orderly shutdown of the operating system, the
server will turn off automatically.
v You can press the power-control button to start an orderly shutdown of the
operating system and turn off the server, if your operating system supports this
feature.
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 server.
v The integrated management module (IMM) can turn off the server as an
automatic response to a critical system failure.
24

This chapter provides detailed instructions for installing optional hardware devices
in the server.
This chapter provides detailed instructions for installing optional hardware devices
in the server.
In addition to the instructions in this chapter for installing optional hardware
devices, updating the firmware and device drivers, and completing the installation,
IBM Business Partners must also complete the steps in Instructions for IBM
Business Partners on page 26.
Important: To help ensure that the devices that you install work correctly and do
not introduce problems, observe the following precautions:
1. Make sure that the server and the installed firmware levels support the devices
that you are installing. If necessary, update the UEFI and IMM firmware and
any other firmware that is stored on the system board. For information about
where firmware is stored in the server, seeUpdating the firmware on page 83.
For a list of supported optional devices for the server, go to
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us.
2. Before you install optional hardware devices, make sure that the server is
working correctly. Start the server and make sure that the operating system
starts, if an operating system is installed, or that a 19990305 error code is
displayed, indicating that an operating system was not found but the server is
otherwise working correctly. If the server is not working correctly, see
Running the DSA Preboot diagnostic programs on page 135 for information
about how to run diagnostics.
3. Follow the installation procedures in this chapter and use the correct tools.
Incorrectly installed device can cause system failure because of damaged pins
in sockets or connectors, loose cabling, or loose components.
4. Use the best practices to apply current firmware and device-driver updates for
the server and optional devices. To download the IBM System x Firmware Update
Best Practices document, go to www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5082923&brandind=5000008. Additional hints and
tips are available from the following sites:
v IBM support: http://www.ibm.com/supportportal/
v System x configuration tools: http://www.ibm.com/systems/x/hardware/
configtools.html
25
Installing optional hardware devices in the server

This following sections provide detailed instructions for installing optional
hardware devices in the server.
Instructions for IBM Business Partners

Instructions for IBM Business Partners on verifying the newly installed devices by
running the Dynamic System Analysis (DSA) stress test.
In addition to the instructions in this chapter for installing optional hardware
devices, updating firmware and device drivers, and completing the installation,
IBM Business Partners must also complete the following steps:
1. After you have confirmed that the server starts correctly and recognizes the
newly installed devices and that no error LEDs are lit, run the Dynamic System
Analysis (DSA) stress test. For information about using DSA, see IBM
Dynamic System Analysis on page 134.
2. Shut down and restart the server multiple times to ensure that the server is
correctly configured and functions correctly with the newly installed devices.
3. Save the DSA log as a file and send it to IBM. For information about
transferring data and logs, see How to send DSA data to IBM on page 670.
4. To ship the server, repackage it in the original undamaged packing material
and observe IBM procedures for shipping.
Support information for IBM Business Partners is available at http://
www.ibm.com/partnerworld.
Sending DSA data to IBM

You can send DSA data to IBM with standard upload, standard upload with the
system serial number, secure upload, and secure upload with the system serial
number.
Before you send diagnostic data to IBM, read the terms of use at
http://www.ibm.com/de/support/ecurep/terms.html.
You can use any of the following methods to send diagnostic data to IBM:
v
v
v
v
26
Standard upload:
Standard upload with the system serial number:
Secure upload:
Secure upload with the system serial number:
Server components
The following illustration shows the major components in the server.
The illustrations in this document might differ slightly from your hardware.
Figure 11. Server components
Blue on a component indicates touch points, where you can grip the component to
remove it from or install it in the server, open or close a latch, and so on.
Orange on a component or an orange label on or near a component indicates that
the component can be hot-swapped, which means that if the server and operating
system support hot-swap capability, you can remove or install the component
while the server is running. (Orange can also indicate touch points on hot-swap
components.) See the instructions for removing or installing a specific hot-swap
component for any additional procedures that you might have to perform before
you remove or install the component.
27
Server internal LEDs, connectors, and jumpers

The illustrations in this section show the connectors, LEDs, and jumpers on the
internal boards.
The illustrations might differ slightly from your hardware.
System-board internal connectors

The following illustrations show the internal connectors on the system board.
PCI riser card

Battery
connector 1
USB hypervisor
connector
PCI riser card

connector 2
SAS signal cable

connector 1
Front video
connector (Optional)
SAS signal cable

connector 0
Backplane configuration
connector
Power-supply
connector
DIMM
connectors 1-6
DIMM connectors 7-12

Front USB connector
Microprocessor 1
Microprocessor 2
Operator
information panel
connector 2
Operator
information panel
connector 1
Fan
connector 1B
Fan
connector 1A
Fan
Fan
connector 2B connector 3B
Fan
connector 2A
Fan
connector 3A
Power-supply
signal connector
Optical drive
connector
(optional)
Figure 12. Internal connectors on system board
System-board external connectors

The following illustration shows the external connectors on the system board.
28
Figure 13. External connectors on system board
System-board jumpers
The following illustration shows the location and description of the switches and
jumpers.
Figure 14. Location and description of switches and jumpers
The following table describes the jumper on the system board.
29
Table 3. System board jumpers

Jumper number
Jumper name
Jumper setting
CN14
Clear CMOS jumper
v Pins 1 and 2: Normal

(default) This keeps the
CMOS data.
v Pins 2 and 3: This clears
the CMOS data such as
power-on password and
loads the default UEFI
settings.
J2
UEFI boot recovery jumper
v Pins 1 and 2: Normal

(default) Loads the
primary server firmware
ROM page.
v Pins 2 and 3: Loads the
secondary (backup) server
firmware ROM page.
Note:
1. If no jumper is present, the server responds as if the pins are set to 1 and 2.
2. Changing the position of the UEFI boot recovery jumper from pins 1 and 2 to pins 2
and 3 before the server is turned on alters which flash ROM page is loaded. Do not
change the jumper pin position after the server is turned on. This can cause an
unpredictable problem.
Important:
1. Before you change any switch settings or move any jumpers, turn off the
server; then, disconnect all power cords and external cables. Review the
information in Safety on page vii, Installation guidelines on page 34,
Handling static-sensitive devices on page 36, and Turning off the server on
page 23.
2. Any system-board switch or jumper blocks that are not shown in the
illustrations in this document are reserved.
System-board LEDs
The following illustration shows the light-emitting diodes (LEDs) on the system
board.
30
System error LED
Light path LED
Locator LED
Battery error LED

System board
error LED
PCI riser 2
missing LED
Microprocessor
mismatch LED
DIMM error
LEDs 7-12
Microprocessor 2
error LED
DIMM error
LEDs 1-6
Microprocessor 1
error LED
PCI riser 1
missing LED
Fan 1B
error LED
Fan 1A
error LED
Fan 2B
error LED
Fan 2A
error LED
Fan 3B
error LED
Fan 3A
error LED
Figure 15. LEDs and controls on system board
System-board optional device connectors

The following illustration shows the connectors on the system board for
user-installable optional devices.
31
PCI riser card

Battery
connector 1
USB hypervisor
connector
PCI riser card

connector 2
SAS signal cable

connector 1
Front video
connector (Optional)
SAS signal cable

connector 0
Backplane configuration
connector
Power-supply
connector
DIMM
connectors 1-6
DIMM connectors 7-12

Front USB connector
Microprocessor 1
Microprocessor 2
Operator
information panel
connector 2
Operator
information panel
connector 1
Fan
connector 1B
Fan
connector 1A
Fan
Fan
connector 2B connector 3B
Fan
connector 2A
Fan
connector 3A
Power-supply
signal connector
Optical drive
connector
(optional)
Figure 16. LEDs and controls on system board
PCI riser cards

The following illustrations show the connectors on the PCI riser cards in the
riser-card assemblies.
The server comes with one PCI riser-card assembly installed in PCI riser connector
1. The riser-card assembly provides either one or two PCI slots, depending on the
server model. The following illustrations shows the connectors on PCI riser-card
assembly 1.
32
Slot 1, PCI Express 3.0

x16 (8,4,1),
full-height, half-length

x16 (8,4,1),
low-profile
PCI riser-card
Slot 1, PCI Express 3.0 x16,
full-height, half-length
PCI riser-card
Figure 17. Connectors on PCI riser-card assembly 1
The optional PCI riser-card assembly 2 is dedicated for an internal ServeRAID

adapter. If your server does not come with PCI riser-card assembly 2, you may
order it for hardware RAID upgrade or for installing additional hard disk drives.

x8 (4,1), low-profile
PCI riser-card
Figure 18. Connectors on PCI riser-card assembly 2
33
Installation guidelines
Use the installation guidelines to install the IBM System x3530 M4 Type 7160.
Attention: Static electricity that is released to internal server components when
the server is powered-on might cause the system to halt, which might result in the
loss of data. To avoid this potential problem, always use an electrostatic-discharge
wrist strap or other grounding system when removing or installing a hot-swap
devices.
Before you install optional devices, read the following information:
v Read the safety information that begins on page Safety on page vii and the
guidelines in Handling static-sensitive devices on page 36. This information
will help you work safely.
v Make sure that the devices that you are installing are supported.
v Make sure that the devices that you are installing are supported. For a list of
supported optional devices for the server, go to http://www.ibm.com/systems/
info/x86servers/serverproven/compat/us.
v When you install your new server, take the opportunity to download and apply
the most recent firmware updates. This step will help to ensure that any known
issues are addressed and that your server is ready to function at maximum
levels of performance. To download firmware updates for your server, go to
http://www.ibm.com/support/fixcentral.
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.
For additional information about tools for updating, managing, and deploying
firmware, see the ToolsCenter for System x and BladeCenter at
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=TOOLCENTER.
v Before you install optional hardware, make sure that the server is working
correctly. Start the server, and make sure that the operating system starts, if an
operating system is installed, or that a 19990305 error code is displayed,
indicating that an operating system was not found but the server is otherwise
working correctly. If the server is not working correctly, see Running the DSA
Preboot diagnostic programs on page 135 for information about how to run
diagnostics.
v Observe good housekeeping in the area where you are working. Place removed
covers and other parts in a safe place.
v Do not attempt to lift an object that you think is too heavy for you. If you have
to lift a heavy object, observe the following precautions:
Make sure that you can stand safely without slipping.
Distribute the weight of the object equally between your feet.
Use a slow lifting force. Never move suddenly or twist when you lift a heavy
object.
To avoid straining the muscles in your back, lift by standing or by pushing
up with your leg muscles.
v Make sure that you have an adequate number of properly grounded electrical
outlets for the server, monitor, and other devices.
v Back up all important data before you make changes to disk drives.
v Have a small flat-blade screwdriver available.
34
v To view the error LEDs on the system board and internal components, leave the
server connected to power.
v You do not have to turn off the server to install or replace hot-swap power
supplies, hot-swap fans, or hot-plug Universal Serial Bus (USB) devices.
However, you must turn off the server before you perform any steps that
involve removing or installing adapter cables and you must disconnect the
power source from the server before you perform any steps that involve
removing or installing a riser card.
v Blue on a component indicates touch points, where you can grip the component
to remove it from or install it in the server, open or close a latch, and so on.
v Orange on a component or an orange label on or near a component indicates
that the component can be hot-swapped, which means that if the server and
operating system support hot-swap capability, you can remove or install the
component while the server is running. (Orange can also indicate touch points
on hot-swap components.) See the instructions for removing or installing a
specific hot-swap component for any additional procedures that you might have
to perform before you remove or install the component.
v When you are finished working on the server, reinstall all safety shields, guards,
labels, and ground wires.
System reliability guidelines

The system reliability guidelines to ensure proper system cooling.
To help ensure proper system cooling and system reliability, make sure that the
following requirements are met:
v Each of the drive bays has a drive or a filler panel and electromagnetic
compatibility (EMC) shield installed in it.
v If the server has redundant power, each of the power-supply bays has a power
supply installed in it.
v There is adequate space around the server to allow the server cooling system to
work properly. Leave approximately 50 mm (2.0 in.) of open space around the
front and rear of the server. Do not place objects in front of the fans. For proper
cooling and airflow, replace the server cover before you turn on the server.
v You have followed the cabling instructions that come with optional adapters.
v You have replaced a failed fan within 48 hours.
v You have replaced a hot-swap drive within 2 minutes of removal.
v You do not operate the server without the air baffles installed. Operating the
server without the air baffles might cause the microprocessor to overheat.
35
Handling static-sensitive devices

Use this information to handle static-sensitive devices.
Attention: Static electricity can damage the server and other electronic devices. To
avoid damage, keep static-sensitive devices in their static-protective packages until
you are ready to install them.
To reduce the possibility of damage from electrostatic discharge, observe the
following precautions:
v Limit your movement. Movement can cause static electricity to build up around
you.
v Handle the device carefully, holding it by its edges or its frame.
v Do not touch solder joints, pins, or exposed circuitry.
v Do not leave the device where others can handle and damage it.
v While the device is still in its static-protective package, touch it to an unpainted
metal surface on the outside of the server for at least 2 seconds. This drains
static electricity from the package and from your body.
v Remove the device from its package and install it directly into the server
without setting down the device. If it is necessary to set down the device, put it
back into its static-protective package. Do not place the device on the server
cover or on a metal surface.
v Take additional care when handling devices during cold weather. Heating
reduces indoor humidity and increases static electricity.
Removing the server top cover

Use this information to remove the cover.
To remove the server top cover, complete the following steps:
1. Read the safety information that begins on page Safety on page vii and
Installation guidelines on page 34.
2. Turn off the server (see Turning off the server on page 23) and all attached
peripheral devices. Disconnect all power cords; then, disconnect all external
cables as necessary to replace the device.
3. If the server has been installed in a rack, press the two release latches on the
front of the server and remove the server out of the rack enclosure.
Attention: Two or more people are required to remove the system from a rack
cabinet.
4. Loosen the two thumbscrews that secure the cover to the rear of the server.
5. Press on the two blue grip points and slide the cover toward the rear; then, lift
the cover off the server and set it aside.
36
Thumbscrew
Top cover
Figure 19. Cover removal
If you have other devices to install or remove, do so now. Otherwise, go to

Completing the installation on page 77.
Removing the air baffle

Use this information to remove the air baffle.
To remove the air baffle, complete the following steps:
cables from the server.
3. Remove the top cover (see Removing the server top cover on page 36).
4. Lift the air baffle from the server and set it aside.
Attention: For proper cooling and airflow, replace the air baffle before you
turn on the server. Operating the server with the air baffle removed might
damage server components.
37
Air baffle
Alignment hook
Figure 20. Air baffle removal

Installing a memory module

The following notes describe the types of DIMMs that the server supports and
other information that you must consider when you install DIMMs.
v Confirm that the server supports the DIMM that you are installing, see
v The server supports only industry-standard double-data-rate 3 (DDR3), 1066
MHz PC3-8500, 1333 MHz PC3-10600, or 1600 MHz PC3-12800, (single-rank,
dual-rank, or quad-rank in specified models), registered or unbuffered,
synchronous dynamic random-access memory (SDRAM) dual inline memory
modules (DIMMs) with error correcting code (ECC).
The specifications of a DDR3 DIMM are on a label on the DIMM, in the
following format.
ggggg eRxff-PC3v-wwwwwm-aa-bb-ccd
where:
- ggggg is the total capacity of the DIMM (for example, 1GB, 2GB, or 4GB)
- eR is the number of ranks
1R = single-rank
2R = dual-rank
4R = quad-rank
- x ff is the device organization or bit width (for example, x4, x8, or x16)
4 = x4 organization (4 DQ lines per SDRAM)
8 = x8 organization
16 = x16 organization
- wwwww is the DIMM bandwidth, in MBps
8500 = 8.53 GBps (DDR3-1066 SDRAMs, 8-byte primary data bus)
38
14900 = 14.93 GBps (DDR3-1866 SDRAMs, 8 byte primary data bus)

17000 = 17.06 GBps (DDR3-2133 SDRAMs, 8 byte primary data bus)
- m is the DIMM type
E = Unbuffered DIMM (UDIMM) with ECC (x72-bit module data bus)
R = Registered DIMM (RDIMM)
U = Unbuffered DIMM with no ECC (x64-bit primary data bus)
- aa is the DDR3 SDRAM CAS latency, in clocks at maximum operating
frequency
- bb is the JEDEC SPD Revision Encoding and Additions level
- cc is the reference design file for the design of the DIMM
- d is the revision number of the reference design of the DIMM
v
v
v
Note: To determine the type of a DIMM, see the label on the DIMM. The
information on the label is in the format xxxxx nRxxx PC3-xxxxx-xx-xx-xxx. The
numeral in the sixth numerical position indicates whether the DIMM is
single-rank (n=1) or dual-rank (n=2).
Do not install registered and unbuffered DIMMs in the same server.
The server supports 1.35-volt (low-voltage) and 1.5-volt DIMMs. Do not install a
1.35-volt and 1.5-volt DIMM in the same server.
The server supports a maximum of 12 DIMMs (single-rank, dual-rank, or
quad-rank) on the system board. If you mix single-rank, dual-rank, or quad-rank
DIMMs in the server, quad-rank DIMMs must be installed first. When one
quad-rank DIMM is installed, it must be installed in DIMM slot 1.
The DIMM options that are available for the server are 2 GB, 4 GB, 8 GB, 16 GB,
and 32 GB (when available).
v The server system board supports a minimum of 2 GB and a maximum of 96 GB

of system memory.
Note: The amount of usable memory is reduced depending on the system
configuration. A certain amount of memory must be reserved for system
resources. To view the total amount of installed memory and the amount of
configured memory, run the Setup utility. For additional information, see
Configuring the server on page 84.
v The server system board provides three memory channels for each
microprocessor and each memory channel supports up to two DIMMs. The
following table lists the DIMM connectors on each memory channel:
Table 4. DIMM connectors on each memory channel
Microprocessor
Channel 0
Channel 1
Channel 2
Microprocessor 1
DIMM connectors 1
and 2
DIMM connectors 3
and 4
DIMM connectors 5
and 6
Microprocessor 2
DIMM connectors 7
and 8
DIMM connectors 9
and 10
DIMM connectors 11
and 12
v The following table shows the DIMM connectors that are associated with each
microprocessor:
Table 5. DIMM connectors associated with each microprocessor
Microprocessor
DIMM connectors associated with the

microprocessor
Microprocessor 1
1 through 6
39
Table 5. DIMM connectors associated with each microprocessor (continued)

Microprocessor
DIMM connectors associated with the

microprocessor
Microprocessor 2
7 through 12
v The maximum operating speed of the server is determined by the slowest

DIMM installed in the server.
v A minimum of one DIMM must be installed for each microprocessor. For
example, you must install a minimum of two DIMMs if the server has two
microprocessors installed. That is, one for microprocessor 1 and one for
microprocessor 2.
v The server comes with a minimum of one DIMM installed in slot 1. When you
install additional DIMMs, install them in the order shown in the information in
the following tables to optimize system performance.
v The server supports independent mode, spare channel mode, and mirroring
mode.
v Independent mode: When you use the independent mode, install DIMMs as
indicated in the following tables.
The following table lists the DIMM installation sequence for non-mirroring
mode when one or two microprocessors is installed in the server:
Table 6. DIMM population sequence (independent mode)
Number of installed
microprocessors
DIMM connector population sequence
1, 3, 5, 2, 4, 6
1, 7, 3, 9, 5, 11, 2, 8, 4, 10, 6, 12
v Spare channel mode: When you use the memory mirroring feature, consider the
following information:
In spare channel mode, one rank is a spare of the other ranks on the same
channel. The spare rank is held in reserve and is not available as system
memory. The spare rank must have identical or larger memory capacity than
all the other ranks (sparing source ranks) on the same channel. After sparing,
the sparing source rank will be lost.
DIMMs must be installed in sets of three. The DIMMs in each set must be the
same size and type.
The following table lists the DIMM installation sequence for rank sparing
mode when one or two microprocessors is installed in the server:
Table 7. DIMM population sequence (rank sparing mode)
Number of installed
microprocessors
1, 3, 5
2, 4, 6
1, 3, 5
7, 9, 11
2, 4, 6
8, 10, 12
40
v Memory-mirroring mode: When you use the memory mirroring feature,

consider the following information:
Memory-mirroring mode replicates and stores data on two pairs of DIMMs
simultaneously. If a failure occurs, the memory controller switches from the
primary pair of memory DIMMs to the backup pair of DIMMs. This
mirroring provides redundancy in memory but reduces the total memory
capacity to one third. Channel 1 DIMM connectors 3, 4, 9, and 10 are not used
in memory-mirroring mode. To enable memory mirroring through the Setup
utility, select System Settings Memory. For more information, see Using
the Setup utility on page 88.
DIMMs must be installed in pairs. The DIMMs in each pair must be the same
size and type.
The maximum available memory is reduced to one third of the installed
memory when memory mirroring is enabled. For example, if you install 96
GB of memory, only 32 GB of addressable memory is available when you use
memory mirroring.
The following table lists the DIMM installation sequence for
memory-mirroring mode when one or two microprocessors is installed in the
server:
Table 8. DIMM population sequence (memory-mirroring mode)
Number of installed
microprocessors
3, 5
4, 6
3, 5
9, 11
4, 6
10, 12
v When you install or remove DIMMs, the server configuration information

changes. When you restart the server, the system displays a message that
indicates that the memory configuration has changed.
The following illustration shows the location of the DIMM connectors on the
system board.
41
Figure 21. DIMM connectors location
To install a DIMM, complete the following steps:

4. Open the retaining clip on each end of the DIMM connector.
Attention: To avoid breaking the retaining clips or damaging the DIMM
connectors, open and close the clips gently.
42
Figure 22. DIMM installation
5. Touch the static-protective package that contains the DIMM to any unpainted
metal surface on the outside of the server. Then, remove the DIMM from the
package.
6. Turn the DIMM so that the DIMM keys align correctly with the connector.
7. Insert the DIMM into the connector by aligning the edges of the DIMM with
the slots at the ends of the DIMM connector (see System-board optional device
connectors on page 31 for the locations of the DIMM connectors).
8. Firmly press the DIMM straight down into the connector by applying pressure
on both ends of the DIMM simultaneously. The retaining clips snap into the
locked position when the DIMM is firmly seated in the connector.
Note: If there is a gap between the DIMM and the retaining clips, the DIMM
has not been correctly inserted; open the retaining clips, remove the DIMM,
and then reinsert it.
Installing drives
The following notes describe the type of hard disk drives that the server supports
and other information that you must consider when you install a hard disk drive.
To confirm that the server supports the drive that you are installing, see
v Locate the documentation that comes with the drive and follow those
instructions in addition to the instructions in this chapter.
v Make sure that you have all the cables and other equipment that are specified in
the documentation that comes with the drive.
v Select the bay in which you want to install the drive.
v The server supports one optional ultra-slim SATA CD-RW/DVD-ROM optical
drive.
43
v The server can support up to eight 2.5 inch hot-swap SAS/SATA drives, four
3.5-inch hot-swap SAS/SATA drives, or four 3.5-inch simple-swap SATA drives.
(see Supported SAS/SATA drive backplane configurations for the supported
configurations).
v You can mix hot-swap SAS and SATA hard disk drives in the same server as
long as you do not mix drives on the same array.
v The electromagnetic interference (EMI) integrity and cooling of the server are
protected by having all bays and PCI Express slots covered or occupied. When
you install a drive, save the EMC shield and filler panel from the bay in the
event that you later remove the device.
Installing hot-swap drives

Use this information to install a hot-swap hard disk drive.
To install a hot-swap SAS or SATA drive, complete the following steps.
Note: If you install only one drive, you must install it in drive bay 0.
2. Touch the static-protective package that contains the drive to any unpainted
metal surface on the server; then, remove the drive from the package and place
it on a static-protective surface.
3. Install a 3.5-inch hot-swap drive:
a. Remove the filler panel from the empty drive bay.
b. Make sure that the drive-tray handle is in the open (unlocked) position.
c. Align the drive assembly with the guide rails in the bay.
Figure 23. 3.5-inch hot-swap hard disk drives installation
d. Gently push the drive assembly into the drive bay until the drive stops.
e. Rotate the drive-tray handle to the closed (locked) position.
f. Skip to step 5.
4. Install a 2.5-inch hot-swap drive:
b. Make sure that the drive-tray handle is in the open (unlocked) position.
c. Align the drive assembly with the guide rails in the bay.
44
Figure 24. 2.5-inch hot-swap hard disk drives installation
d. Gently push the drive assembly into the drive bay until the drive stops.
e. Rotate the drive-tray handle to the closed (locked) position.
5. Check the drive status LED to verify that the drive is operating correctly. If the
yellow drive status LED for a drive is lit continuously, that drive is faulty and
must be replaced. If the green drive activity LED is flashing, the drive is being
accessed.
Note: If the server is configured for RAID operation using a ServeRAID
adapter, you might have to reconfigure your disk arrays after you install drives.
See the ServeRAID adapter documentation for additional information about
RAID operation and complete instructions for using the ServeRAID adapter.
6. If you are installing additional hot-swap drives, do so now.
7. Restart the server. Confirm that it starts correctly and recognizes the newly
installed devices, and make sure that no error LEDs are lit.
8. Complete the additional steps in Instructions for IBM Business Partners on
page 26.
IDs for hot-swap drives

The drive ID that is assigned to each drive is printed on the front of the server.
The following illustrations show the locations of the IDs of the drives. The ID
numbers and the drive bay numbers are the same.
The following illustration shows the drive bay IDs on a 3.5-inch drive server
model.
Figure 25. 3.5-inch hot-swap hard disk drive IDs
model.
45
Installing simple-swap drives

Use this information to install simple-swap hard disk drives.
To install a simple-swap SATA drive, complete the following steps.
4. Install the hard disk drive in the drive bay
b. Align the drive assembly with the guide rails in the bay.
Figure 27. 3.5-inch simple-swap hard disk drive installation
46
c. Gently slide the drive assembly into the drive bay until it clicks into place.
d. Install the filler panel.
5. If you are installing additional simple-swap drives, do so now.
Installing an optional optical drive

Use this information to install an optional optical drive.
To install an optional optical drive, complete the following steps:
4. Locate the blue release tab on the rear of the drive bay; then, while you press
the tab, push the optical drive filler toward the front of the server.
47
Figure 29. DVD drive filler panel removal
5. Pull the optical drive filler out of the front of the server.
6. Remove the retention clip from the side of the drive filler.
Figure 30. retention clip removal
Note: If you are installing a drive that contains a laser, observe the following
safety precaution.
Statement 3
48
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
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.

Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
7. Touch the static-protective package that contains the new optical drive to any
unpainted metal surface on the server; then, remove the optical drive from the
package and place it on a static-protective surface.
8. Attach the drive retention clip that you removed from the previous drive to the
side of the new drive.
9. Align the drive in the drive bay and slide the drive into the optical drive bay
until the drive clicks into place.
49
Installing a PCI riser-card assembly

Use this information to install a PCI riser-card assembly.
To install a PCI riser-card assembly, complete the following steps:
4. Install the adapter in the PCI riser-card assembly (see Installing an adapter
on page 51).
5. Align the PCI riser-card assembly with the PCI slot connector on the system
board and align nailheads with the slots on the chassis; then, press down firmly
until the riser-card assembly is seated correctly in the connector on the system
board.
PCI riser-card
assembly 2 (one
internal RAID
adapter)
PCI riser-card
assembly 1 (fullheight, half - length, or
low-profile adapters)
PCI riser 1
PCI riser 2
Figure 31. PCI riser-card assembly installation

50
Installing an adapter
Use this information to install an adapter.
The following notes describe the types of adapters that the server supports and
other information that you must consider when you install an adapter:
v To confirm that the server supports the adapter that you are installing, see
v Locate the documentation that comes with the adapter and follow those
instructions in addition to the instructions in this section.
v Do not set the maximum digital video adapter resolution above 1280 x 1024 at
75 Hz for an LCD monitor. This is the highest resolution that is supported for
any add-on video adapter that you install in the server.
v Any high-definition video-out connector or stereo connector on any add-on
video adapter is not supported.
v The server provides two PCI riser slots on the system board. The riser cards
provide up to three PCIE 3 adapter slots (see PCI riser cards on page 32 for
the location of the PCI-e slots on the riser cards). The following table lists the
PCI-e slots on the riser-card and the system board, the microprocessor to which
each slot is connected, and the supported adapters that you can install in each
slot:
Table 9. PCI riser slots supported configurations
Microprocessor
to which the
slot is connected Configuration 1
PCI riser-card
assembly
PCI-e slot
number
Microprocessor 1 PCIE 3.0 x16

(x16
mechanically)
full-height,
half-length
adapter
PCIE 3.0 x8 (x16

mechanically)
full-height,
half-length
adapter
Microprocessor 1 N/A
PCIE 3.0 x8 (x16

mechanically)
low-profile
adapter
Microprocessor 1 PCIE 3.0 x4

low-profile,
internal RAID
adapter
PCIE 3.0 x4
low-profile,
internal RAID
adapter
Configuration 2
Note: PCI-e slot 3 on PCI riser-card assembly 2 is reserved for an optional internal RAID
adapter. Do not install any internal RAID adapter in PCI riser-card assembly 1.
v Depending on your server model, the server comes with an onboard RAID
controller which provides basic RAID levels 0 and 1 functionality. The server
supports the following optional RAID adapters that you can purchase for
additional RAID support. For configuration information, see the documentation
that comes with the adapter or the ServeRAID documentation at
Attention: 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.
ServeRAID controllers:
- ServeRAID H1110 SAS/SATA Controller for System x
51
- ServeRAID M1115 SAS/SATA Controller for System x

- ServeRAID M5120 SAS/SATA Controller for IBM System x
- ServeRAID M5110 SAS/SATA Controller for IBM System x
ServeRAID controller upgrade options:
- ServeRAID M5100 Series 512 MB Cache/RAID 5 Upgrade for IBM System
x
- ServeRAID M5100 Series 512 MB Flash/RAID 5 Upgrade for IBM System x
- ServeRAID M5100 Series 1 GB Flash/RAID 5 Upgrade for IBM System x
- ServeRAID M5100 Series RAID 6 Upgrade for IBM System x
- ServeRAID M5100 Series Performance Key
Notes:
v The instructions in this section apply to any supported adapter (for example,
video graphics adapters or network adapters).
v You must install an internal ServeRAID adapter in PCI riser-card assembly 2.
v When you install an adapter, make sure that the adapter is correctly seated in
the riser-card assembly and that the riser-card assembly is securely seated in the
riser-card connector on the system board before you turn on the server. An
incorrectly seated adapter might cause damage to the system board, the
riser-card assembly, or the adapter.
video adapter is not supported
v
To install an adapter, complete the following steps:
4. Follow the cabling instructions, if any come with the adapter. Route the adapter
cables before you install the adapter.
5. Installing an adapter in PCI riser-card assembly 1:
Insert the adapter into the PCI riser-card assembly, aligning the edge connector
on the adapter with the connector on the PCI riser-card assembly. Press the
edge of the connector firmly into the PCI riser-card assembly. Make sure that
the adapter snaps into the PCI riser-card assembly securely.
52
PCI bracket
Adapter
PCI slot 1
PCI slot 2
PCI bracket
Riser-card
assembly 1
Adapter
Figure 32. Adapter installation in PCI riser-card assembly 1
6. Installing a ServeRAID adapter in PCI riser-card assembly 2:

a. Pull the release pin to unlock the release latch.
b. Rotate the retention latch to the open position.
c. Insert the adapter into the PCI riser-card assembly, aligning the edge
connector on the adapter with the connector on the PCI riser-card assembly.
Press the edge of the connector firmly into the PCI riser-card assembly. Make
sure that the adapter snaps into the PCI riser-card assembly securely.
d. Rotate the retention latch to the close position. Make sure the retention latch
engages the adapter securely; then, push in the release pin to lock the
retention latch.
PCI slot 3
Riser-card
assembly 2
Adapter
Figure 33. Adapter installation in PCI riser-card assembly 2
7. Install the PCI riser-card assembly in the server (see Installing a PCI riser-card
assembly on page 50).
8. Perform any configuration tasks that are required for the adapter.
53
Installing an optional IBM ServeRAID SAS/SATA Controller

Use this information to install a ServeRAID SAS/SATA controller.
Port 1
(ports 7-4)
Port 0
(ports 0-3)
Figure 34. ServeRAID adapter installation
You can purchase an optional IBM ServeRAID SAS/SATA controller. You must
install the optional ServeRAID adapter in PCI slot 3 on PCI riser-card assembly 2.
If the server does not already come with PCI riser-card assembly 2, you must
purchase the PCI riser-card assembly option. For configuration information, see the
ServeRAID documentation at http://www.ibm.com/support/mysupport/.
Attention: 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.
Note:
1. Follow the general rule for connecting the SAS signal cables to the adapter and
drive backplane, port 0 on the adapter to port 0 on the drive backplane; then
port 1 on the adapter to port 1 on the drive backplane (depending on the drive
backplane you install in the server).
2. When you install an IBM ServeRAID SAS/SATA adapter that has a battery, you
must install the ServeRAID battery remotely on the remote battery holder in
the server (see Installing a RAID adapter battery remotely in the server on
page 71).
To install an IBM ServeRAID adapter, complete the following steps:
4. Carefully grasp PCI riser-card assembly 2 by the blue touch points and pull it
until the PCI riser-card assembly disengages from the connector on the system
board.
5. Pull the release pin on the rear of the PCI riser-card assembly to unlock the
retention latch; then rotate the retention latch to the open position.
6. Touch the static-protective package that contains the ServeRAID adapter to
any unpainted surface on the outside of the server; then, grasp the adapter by
the top edge or upper corners of the adapter and remove it from the package.
54
7. Align the ServeRAID adapter so that the keys align correctly with the
connector on the PCI riser-card assembly.
8. Insert the ServeRAID adapter into the connector on the riser-card until it is
firmly seated.
Attention: Incomplete insertion might cause damage to the server or the
adapter.
9. Rotate the retention latch to the closed position, making sure the retention
latch engages the ServeRAID adapter. Then, push in the release pin to lock the
retention latch in place.
10. Connect the power/configuration cable to the drive backplane and the system
board.
11. Connect the signal cable to the drive backplane and to the adapter. Be sure to
route the signal cables as shown in the following illustration. Secure the cables
with any cable clips on the system board so that they do not get in the way or
get damaged.
12. Reinstall PCI riser-card assembly 2 onto the system board.
Installing an additional microprocessor and heat sink

The following notes describe the type of microprocessor that the server supports
and other information that you must consider when you install a microprocessor
and heat sink.
Note: If your server comes with one Intel Pentium 1400 series microprocessor, the
second microprocessor socket is not used. The server supports only one Intel
Pentium microprocessor. If you plan to install two Intel Xeon microprocessors in
the server, you must first remove the Intel Pentium microprocessor that came with
the server.
v A microprocessor must be replaced or serviced by a trained technician.
v Be extremely careful, the pins on the socket are fragile. Any damage to the pins
may require replacing the system board.
v The microprocessor tool assembly comes with the microprocessor and
microprocessor cover attached to the tool. The microprocessor comes protected
between the tool and the microprocessor cover. Store the microprocessor tool in
a safe location for future use.
v Use the microprocessor tool to install or remove a microprocessor in the server.
Failure to use the microprocessor tool may cause damage to the pins in the
socket. Any damage to the pins may require replacing the system board.
v The server supports one Intel Pentium 1400 series microprocessor or up to two
Intel Xeon four-core, six-core, or eight-core microprocessors (depending on your
model). To confirm that the server supports the microprocessor, see
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us for a
list of supported microprocessors.
v Do not mix four-core, six-core, and eight-core microprocessors in the same
server.
v The microprocessor options that IBM supports are limited by the capacity and
capability of the server. Any microprocessor options that you install must have
the same specifications as the microprocessor(s) that came with the server.
v The first microprocessor must always be installed in microprocessor socket 1 on
the system board.
55
v Do not remove the first microprocessor from the system board when you install
the second microprocessor.
v When you install the second microprocessor, you must also install additional
memory and the fourth and sixth fans. See Installing a memory module on
page 38 for details about the memory installation sequence.
v To ensure proper server operation when you install an additional
microprocessor, use microprocessors that have the same QuickPath Interconnect
(QPI) link speed, integrated memory controller frequency, core frequency, power
segment, internal cache size, and type.
v Mixing microprocessors of different stepping levels within the same server
model is supported.
v When mixing microprocessors with different stepping levels within the same
server model, you do not have to install the microprocessor with lowest
stepping level and features in microprocessor socket 1.
v Both microprocessor voltage regulator modules are integrated on the system
board.
v Read the documentation that comes with the microprocessor, so that you can
determine whether you have to update the server firmware. To download the
latest level of the server firmware and other code updates for your server, go to
v If the thermal-grease protective cover (for example, a plastic cap or tape liner) is
removed from the heat sink, do not touch the thermal grease on the bottom of
the heat sink or set down the heat sink. For details, see Thermal grease.
Note: Removing the heat sink from the microprocessor destroys the even
distribution of the thermal grease and requires replacing the thermal grease.
v To order an additional optional microprocessor, contact your IBM marketing
representative or authorized reseller.
v The following table shows the DIMM connectors on the system board and the
DIMM connectors that are associated with each microprocessor:
Table 10. DIMM connectors associated with each microprocessor
Microprocessor
DIMM connectors
Microprocessor socket 1
1 through 6
Microprocessor socket 2
7 through 12
To install an additional microprocessor and heat sink, complete the following steps:
Attention: When you handle static-sensitive devices, take precautions to
avoid damage from static electricity. For details about handling these devices,
see Handling static-sensitive devices on page 36.
4. Remove the air baffle (see Removing the air baffle on page 37).
5. Locate microprocessor socket 2 on the system board.
6. Remove the heat-sink filler, if one is present.
7. Open the microprocessor socket release lever and retainer.
56
a. Press down and out on the release lever on microprocessor socket 2 and
lift up the microprocessor release lever until it stops in the fully open
position.
b. Lift the hinged microprocessor bracket frame into an open position.
Attention: When you handle static-sensitive devices, take precautions to
avoid damage from static electricity. For details about handling these
devices, see Handling static-sensitive devices on page 36.
Figure 35. Lift the bracket frame into an open position
8. Install the microprocessor:

a. Remove the socket cover from the microprocessor socket.
Figure 36. Microprocessor Installation
b. Touch the static-protective package that contains the new microprocessor

to any unpainted metal surface on the server.
c. Remove the microprocessor installation tool assembly from the package.
The microprocessor installation tool assembly comes with the
microprocessor and microprocessor cover attached to the tool. The
microprocessor comes protected between the tool and the microprocessor
cover.
57
Attention:
v Do not rotate the handle on the tool until you are ready to install the
microprocessor into the microprocessor socket.
v Do not touch the microprocessor contacts; handle the microprocessor by
the edges only. Contaminants on the microprocessor contacts, such as oil
from your skin, can cause connection failures between the contacts and
the socket.
v Handle the microprocessor carefully. Dropping the microprocessor
during installation or removal can damage the contacts.
d. Remove the cover from the bottom of the microprocessor installation tool.
Press both microprocessor cover release tabs outward (in opposite
directions as shown in the illustration) and remove the microprocessor
installation tool with the microprocessor attached.
Installation tool
Microprocessor
Microprocessor
cover release
tabs
Microprocessor
cover
Figure 37. Microprocessor removal with microprocessor installation tool
e. Carefully align the microprocessor installation tool over the microprocessor

socket. .
Note: The microprocessor fits only one way in the socket.
Installation tool
Microprocessor
Alignment pins
Figure 38. Microprocessor installation alignment
f. Twist the handle on the microprocessor tool counterclockwise to insert the

microprocessor into the socket.
58
Handle
Installation tool
Figure 39. Microprocessor insertion
g. Take off the microprocessor installation tool from the microprocessor

socket and close the microprocessor bracket frame.
h. Carefully close the microprocessor release lever to the closed position to
secure the microprocessor in the socket.
9. Install the heat sink that came with the microprocessor:
a. Remove the plastic protective cover from the bottom of the heat sink.
Attention: Do not touch the thermal grease on the bottom of the heat
sink after you remove the plastic cover. Touching the thermal grease will
contaminate it. See Thermal grease for more information.
b.
Align the screws on the heat sink with the screw holes on the system
board; then, place the heat sink on the microprocessor with the
thermal-grease side down.
Figure 40. Heat sink placement
c. Press firmly on the captive screws and tighten them with a screwdriver.
The follow illustration shows the sequence in tightening the screws, which
is also shown on top of the heat sink. Begin with the screw labeled as "1",
then "2", "3" and finally "4". If possible, each screw should be rotated two
full rotations at a time. Repeat until the screws are tight. Do not
overtighten the screws by using excessive force. If you are using a torque
wrench, tighten the screws to 8.5 Newton-meters (Nm) to 13 Nm (6.3
foot-pounds to 9.6 foot-pounds).
59
REPEAT SEQUENCE
UNTIL TIGHT.
Figure 41. Sequence in tightening the screws
10. If you installed the second microprocessor, install the two fans on Fan
connector 4 and Fan connector 6 of the system board respectively (see
Replacing a hot-swap fan assembly).
11. Reinstall the air baffle, (see Replacing the microprocessor air baffle).
12. Reconnect any cables that you have disconnected from the adapters or system
board.
Thermal grease
The thermal grease must be replaced whenever the heat sink has been removed
from the top of the microprocessor and is going to be reused or when debris is
found in the grease.
When you are installing the heat sink on the same microprocessor that is was
removed from, make sure that the following requirements are met:
v The thermal grease on the heat sink and microprocessor is not contaminated.
v Additional thermal grease is not added to the existing thermal grease on the
heat sink and microprocessor.
Note:
v Read the Safety information on page Safety on page vii.
v Read the Installation guidelines on page 34.
v Read Handling static-sensitive devices on page 36.
To replace damaged or contaminated thermal grease on the microprocessor and
heat sink, complete the following steps:
1. Place the heat sink on a clean work surface.
2. Remove the cleaning pad from its package and unfold it completely.
3. Use the cleaning pad to wipe the thermal grease from the bottom of the heat
sink.
Note: Make sure that all of the thermal grease is removed.
4. Use a clean area of the cleaning pad to wipe the thermal grease from the
microprocessor; then, dispose of the cleaning pad after all of the thermal grease
60
is removed.
0.02 mL of thermal
grease
Microprocessor
Figure 42. Thermal grease distribution
5. Use the thermal-grease syringe to place 9 uniformly spaced dots of 0.02 mL

each on the top of the microprocessor. The outermost dots must be within
approximately 5 mm of the edge of the microprocessor; this is to ensure
uniform distribution of the grease.
Figure 43. Syringe
Note: If the grease is properly applied, approximately half of the grease will
remain in the syringe.
6. Install the heat sink onto the microprocessor as described in Installing an
additional microprocessor and heat sink on page 55.
Installing a hot-swap ac power supply

Use this information to install a hot-swap ac power supply.
The following notes describe the type of power supply that the server supports
and other information that you must consider when you install a power supply:
v To confirm that the server supports the power supply that you are installing, see
v Before you install an additional power supply or replace a power supply with
one of a different wattage, you may use the IBM Power Configurator utility to
determine current system power consumption. For more information and to
download the utility, go to http://www.ibm.com/systems/bladecenter/
resources/powerconfig.html.
v The server comes standard with one of the following power supplies that
connects to power supply bay 1. The input voltage is 100-127 V ac or 200-240 V
ac auto-sensing.
460-watt fixed power supply
460-watt hot-swap power supply
675-watt high-efficiency, hot-swap power supply
Note: You cannot mix 110 V ac and 220 V ac, or 460-watt and 675-watt power
supplies in the server, it is not supported.
61
v Power supply 1 is the default/primary power supply. If power supply 1 fails,

you must replace the power supply with the same wattage immediately.
v The server supports a maximum of two hot-swap power supplies. These power
supplies are designed for parallel operation. In the event of a power-supply
failure, the redundant power supply continues to power the system.
v The server can run fully configured with one power supply. For redundancy
support, you must install the second hot-swap power supply.
Statement 5
CAUTION:
2
1
Statement 8
CAUTION:
label attached.
components. If you suspect a with one of these parts, contact a service
technician.
To install a hot-swap power supply, complete the following steps:
2. Touch the static-protective package that contains the hot-swap power supply
to any unpainted metal surface on the server; then, remove the power supply
from the package and place it on a static-protective surface.
62
3. If you are installing a hot-swap power supply into an empty bay, remove the
power-supply filler panel from the power-supply bay.
Figure 44. Power supply installation
4. Grasp the handle on the rear of the power supply with the gold contact ; then,
slide the power supply forward into the power-supply bay until it clicks.
Make sure that the power supply connects firmly into the power-supply
connector.
5. Route the power cord through the cable retainer clip on the rear of the server
so that it does not accidentally become unplugged.
6. Connect the power cord for the new power supply to the power-cord
connector on the power supply.
7. Connect the other end of the power cord to a properly grounded electrical
outlet.
8. Make sure that the ac power LED and the dc power LED on the power
supply are lit, indicating that the power supply is operating correctly. The two
green LEDs are to the right of the power-cord connector.
9. If you are replacing a power supply with one of a different wattage in the
server, apply the new power information label provided over the existing
power information label on the server. Power supplies in the server must be
with the same power rating or wattage to ensure that the server will operate
correctly.
xxx-xxx/xxx-xxx
x,x/x,x
xx/xx Hz

Product certified in Shenzhen, China

Made in China
V
xxx-xxx/xxx-xxx
x,x/x,x
xx/xx Hz

Manufacturer: IBM Corporation
Copyright Code and Parts Contained Herein.

Copyright IBM Corp. 2012 All Rights Reserved.
Canada ICES/NMB-003 Class/Classe A
XXXX
xxx
KCC-REM-IBC-7915
Figure 45. Power information label
10. If you are adding a power supply to the server, attach the redundant power
information label that comes with this option on the server cover near the
63
power supplies.
XXXW ~ AC
1
xxx-xxx/
xxx-xxxV~
XXXW ~ AC
2
xxx-xxx/
xxx-xxxV~
x,x/x,x A
x,x/x,x A
xx/xx Hz
xx/xx Hz
Power supplies
Figure 46. Redundant power information label
installed device, and make sure that no error LEDs are lit.
Installing a hot-swap dc power supply

Observe the following precautions when you install a hot-swap dc power supply.
v The server comes with one hot-swap 12-volt output power supply that connects
to power supply bay 1. The input voltage is -48 V dc or -60 V dc auto-sensing.
v Before you install a dc power supply in the server, you must remove all ac
power supplies. Do not use both ac and dc power supplies in the same server.
Install up to two dc power supplies or up to two ac power supplies, but not a
combination.
v You can order an optional power supply for redundancy.
v These power supplies are designed for parallel operation. In the event of a
power-supply failure, the redundant power supply continues to power the
system. The server supports a maximum of two power supplies.
v It is the customer's responsibility to supply the necessary power cable.
To reduce the risk of electric shock or energy hazards:
Use a circuit breaker that is rated at 25 amps.
Use 2.5 mm2 (12 AWG) at 90 C copper wire.
64
Torque the wiring-terminal screws to 0.50 ~ 0.60 newton-meters (4.43 ~ 5.31

inch-pounds).
For more information, see Statement 34.
v If the power source requires ring terminals, you must use a crimping tool to
install the ring terminals to the power cord wires. The ring terminals must be
UL approved and must accommodate the wire that is described in the
above-mentioned note .
Statement 29:
CAUTION:
This equipment is designed to permit the connection of the earthed conductor of
the dc supply circuit to the earthing conductor at the equipment.
the dc supply circuit to the earthing conductor at the equipment. If this connection
is made, all of the following conditions must be met:
v This equipment shall be connected directly to the dc supply system earthing
electrode conductor or to a bonding jumper from an earthing terminal bar or
bus to which the dc supply system earthing electrode conductor is connected.
v This equipment shall be located in the same immediate area (such as, adjacent
cabinets) as any other equipment that has a connection between the earthed
conductor of the same dc supply circuit and the earthing conductor, and also the
point of earthing of the dc system. The dc system shall not be earthed elsewhere.
v The dc supply source shall be located within the same premises as this
equipment.
v Switching or disconnecting devices shall not be in the earthed circuit conductor
between the dc source and the point of connection of the earthing electrode
conductor.
Statement 31
65
DANGER
hazardous.
v Connect all power cords to a properly wired and grounded power source.
v Connect to properly wired power sources any equipment that will be
attached to this product.
structural damage.
v Disconnect the attached ac power cords, dc power sources, network
connections, telecommunications systems, and serial cables before you
open the device covers, unless you are instructed otherwise in the
installation and configuration procedures.
you install, move, or open covers on this product or attached devices.
To Connect:
To Disconnect:
1. Turn OFF all power sources and

equipment that is to be attached to this
product.

product.
2. Attach signal cables to the product.

3. Attach power cords to the product.
v For ac systems, use appliance inlets.
v For dc systems, ensure correct polarity
of -48 V dc connections: RTN is + and
-48 V dc is -. Earth ground should use
a two-hole lug for safety.
4. Attach signal cables to other devices.
v For ac systems, remove all power

cords from the chassis power
receptacles or interrupt power at the
ac power distribution unit.
v For dc systems, disconnect dc power
sources at the breaker panel or by
turning off the power source. Then,
remove the dc cables.
5. Connect power cords to their sources.
2. Remove the signal cables from the

connectors.
6. Turn ON all the power sources.
3. Remove all cables from the devices.
Statement 33
CAUTION:
This product does not provide a power-control button. Turning off blades or
removing power modules and I/O modules does not turn off electrical current to
the product. The product also might have more than one power cord. To remove
all electrical current from the product, make sure that all power cords are
disconnected from the power source.
66
OFF
Statement 34
CAUTION:
v This equipment must be installed by trained service personnel in a
restricted-access location, as defined by the NEC and IEC 60950-1, First
Edition, The Standard for Safety of Information Technology Equipment.
v Connect the equipment to a properly grounded safety extra low voltage
(SELV) source. A SELV source is a secondary circuit that is designed so that
normal and single fault conditions do not cause the voltages to exceed a safe
level (60 V direct current).
v Incorporate a readily available approved and rated disconnect device in the
field wiring.
v See the specifications in the product documentation for the required
circuit-breaker rating for branch circuit overcurrent protection.
v Use copper wire conductors only. See the specifications in the product
documentation for the required wire size.
v See the specifications in the product documentation for the required torque
values for the wiring-terminal screws.
Important: Be sure to read the multilingual safety instructions on the CD that comes with
the server before you use the product.
To install a hot-swap dc power supply, complete the following steps:

Attention: Only trained service personnel other than IBM service technicians are
authorized to install and remove the -48 volt dc power supply, and make the
connections to and disconnections from the -48 volt dc power source. IBM service
technicians are not certified or authorized to install or remove the -48 volt power
cable. The customer is responsible for ensuring that only trained service personnel
install or remove the -48 volt power cable.
67
to any unpainted metal surface on the server; then, remove the power supply
3. Turn off the circuit breaker for the dc power source to which the new power
supply will be connected. Disconnect the power cord from the dc power
source.
4. Attach the dc power cable to the new power supply. Make sure the wires are
connected securely to the -48V, ground, and -48V return terminals.
Power input LED
Power output LED
Power error LED
-48V return
Ground
-48V
Figure 47. DC power supply rear view
power-supply filler from the power-supply bay.
6. Grasp the handle on the rear of the power supply and slide the power supply
forward into the power-supply bay until it clicks. Make sure that the power
supply connects firmly into the power-supply connector.
7. Route the power cord through the handle and cable tie if any, so that it does
not accidentally become unplugged.
8. Connect the other ends of the dc power cable to the dc power source. Cut the
wires to the correct length, but do not cut them shorter than 150 mm (6 inch).
If the power source requires ring terminals, you must use a crimping tool to
UL approved and must accommodate the wires that are described in the note.
The minimum nominal thread diameter of a pillar or stud type of terminal
must be 4 mm; for a screw type of terminal the diameter must be 5.0 mm.
68
9. Turn on the circuit breaker for the dc power source to which the new power
supply is connected.
10. Make sure that the green power LEDs on the power supply are lit, indicating
that the power supply is operating correctly.
correctly.
power supplies.
69
Installing a USB embedded hypervisor flash device

Use this information to install a USB embedded hypervisor flash device.
To install a hypervisor flash device, complete the following steps:
4. Remove PCIe riser-card assembly 1 (see Removing a PCI riser-card assembly
on page 251).
5. Locate the embedded hypervisor USB flash device connector on the system
board as shown in the following illustration:
Figure 51. Location of the embedded hypervisor USB flash device
6. Slide the lockbar toward the riser-card assembly to the locked position until it
is seated firmly.
70
Lockbar
USB Hypervisor
key
Figure 52. Embedded hypervisor USB flash device installation

Installing a RAID adapter battery remotely in the server

Use this information to install a RAID adapter battery remotely in the server.
When you install a RAID adapter in the server that come with a battery or a
power module (Supercap pack), the RAID battery or power module must be
installed remotely to prevent it from overheating. The battery or power module
must be installed in the RAID battery tray on top of the power interposer card.
To install a RAID adapter battery or power module remotely in the server,
complete the following steps:
3. If the RAID adapter was shipped with a battery and battery carrier attached,
disconnect the battery carrier cable from the battery and remove the three
screws that secure the battery carrier to the adapter. Set the battery and
battery carrier aside.
71
Figure 53. Screws removal from the battery carrier
4. Install the interposer card in the interposer card connector on the RAID
adapter:
a. Remove the interposer card and the screw from the bag.
b. Rotate the plastic standoff on the interposer card so that it aligns with the
hole on the RAID adapter; then, align the connector on interposer card
with the interposer card connector on the RAID adapter.
Figure 54. Interposer card and interposer card connector alignment
c. Press the interposer card down onto the interposer card connector on the
RAID adapter until it is firmly seated.
d. From underneath the RAID adapter, insert the screw that you took from
the bag and tighten the screw to secure the interposer card to the RAID
adapter.
5. Connect one end of the remote battery cable to the interposer card.
Attention: To avoid damage to the hardware, make sure that the black dot
on the remote battery cable connector faces away from the interposer card on
the adapter. Do not force the remote battery cable into the connector.
72
Figure 55. Interposer card connection
6. Install the RAID adapter on the riser card and install the PCI riser-card
assembly in the server (see Installing a PCI riser-card assembly on page 50).
7. Connect the other end of the remote battery cable to the remote battery cable
connector on the battery carrier.
Attention: To avoid damage to the hardware, make sure that the black dot
on the remote battery cable connector faces away from the interposer card on
the adapter. Do not force the remote battery cable into the connector.
8. Route the remote battery cable in server as shown in the following illustration.
Attention: Make sure that the cable is not pinched and does not cover any
connectors or obstruct any components on the system board.
9. Install the battery on the safety cover:
a. Orient the battery as shown in the following illustration; then, lower the
battery onto the safety cover. If the battery comes with a battery carrier,
ensure that battery carrier posts align with the rings on the battery
mounting slot so that the battery carrier is secure in the slot.
Note: The positioning of the remote battery depends on the type of remote
battery that you install.
b. Rotate the retention clip to the close position and press down on the
retention clip until it snaps in place to hold the battery in place.
10. Connect the remote battery cable to the remote battery cable connector to the
ServeRAID adapter. Route the remote battery cable in the server as shown in
the following illustration.
73
Installing an optional 4x2.5-inch hot-swap drive backplane

You can install a IBM System x3530 M4 4x2.5-inch hot-swap drive backplane
option in the server.
To install an optional 4x2.5-inch hot-swap drive backplane, complete the following
steps:
4. Connect the configuration, signal, and power cables to the connectors on the
backplane, if they are not already connected.
5. Slide the backplane into the guide channels, making sure that any nearby wires
or cables are not trapped or pinched.
Figure 56. Backplane installation
6. Connect the cables:

a. Connect the other end of the power cable to the power connector to the
power supply.
1) The redundant power model:
74
Power cable
Figure 57. Power cable installation for redundant power model
2) The fixed power model:
75
Power cable
Figure 58. Power cable installation for fixed power model
b. Connect the other end of the signal cable to the Port 1 connector on the
RAID adapter or the connector on the system board. Be sure to route the
signal cable through the cage hole next to the power distribution board.
76
Figure 59. Signal cable installation
c. Use the cable clips on the chassis to secure the cables so that they do not get
in the way or get damaged.
Completing the installation.
Completing the installation

Use this information to complete the installation.
To complete the installation, complete the following steps:
1. If you removed the air baffle, reinstall it (see Replacing the air baffle on page
78).
2. If you removed a PCIe riser-card assembly, reinstall it (see Replacing a PCI
riser-card assembly on page 79).
3. If you removed the server cover, replace it (see Replacing the server top
cover on page 80).
4. Install the server in the rack cabinet (see the Rack Installation Instructions that
come with the server for instructions).
5. Reconnect the cables and power cords (see Connecting the cables on page
81).
6. Start the server. Confirm that is starts correctly and recognizes the newly
7. Update the server configuration (see Updating the server configuration on
page 82).
77

page 26.
Replacing the air baffle

Use this information to replace the air baffle.
To install the air baffle, complete the following steps:
2. Align the tabs on the sides of the air baffle with the slots on the fan cage and
lower the air baffle into the server.
Note: Make sure that no cable is pinched.
Air baffle
Alignment hook
Alignment pin
Figure 60. Air baffle installation
78
Replacing a PCI riser-card assembly

Use this information to replace the PCI riser-card assembly.
To replace a PCI riser-card assembly, complete the following steps:
2. Install the adapter in the PCI riser-card assembly (see Installing an adapter
on page 51).
3. Align the PCI riser-card assembly with the PCIe slot connector on the system
board and align nailheads with the slots on the chassis; then, press down firmly
until the riser-card assembly is seated correctly in the connector on the system
board.
PCI riser-card
assembly 2 (one
internal RAID
adapter)
PCI riser-card
PCI riser 1
PCI riser 2
79
Replacing the server top cover

Use this information to replace the cover.
To replace the server cover, complete the following steps:
1. Make sure that all cables, adapters, and other components are installed and
seated correctly and that you have not left loose tools or parts inside the server.
Also, make sure that all internal cables are correctly routed.
2. Align the cover over the server (toward the rear of the server) until the cover
edges slip into position over the chassis.
Important: Before you slide the cover forward, make sure that all the tabs on
the cover engage the chassis correctly. If all the tabs do not engage the chassis
correctly, it will be hard to remove the cover later.
Thumbscrew
Top cover
Figure 62. Cover installation
3. Slightly slide the cover toward the front of the server until the inset tabs start
to engage on the server; then, tighten the thumbscrews to secure the cover to
the chassis.
4. Install the server into the rack enclosure and push the server into the rack until
it clicks into place.
80
Connecting the cables

The following illustrations show the locations of the input and output connectors
of the server.
The following illustration shows the locations of the input and output connectors
on the front of the server.
Operator
information panel
Rack release
USB 1
USB 2
Video
latch
Rack release latch
Power control
button
and
power - on
LED

Drive activity LED
(green)
Drive status LED

(yellow)
Optional optical
drive eject button
Optional
optical drive
activity LED
Figure 63. Front of server
The following illustration shows the locations of the input and output connectors
for both non-hot-swap and hot-swap power supplies respectively on the rear of the
server.
Ethernet 2
Power supply
Power supply Ethernet 1
PCI slot 3
connector
PCI slot 2
USB 4
Ethernet 4
Ethernet 3
USB 3
PCI slot 1
USB 6 Serial Video NMI

button
connector
USB 5
Figure 64. Rear of server for non-hot-swap power supplies
Power
supply 1
Power
supply 2
Power supply
connectors
Ethernet 2
PCI slot 3
Ethernet 1
Ethernet 4
Ethernet 3
PCI slot 2
USB 4
USB 3
PCI slot 1
USB 6 Serial Video NMI

button
connector
USB 5
Figure 65. Rear of server for hot-swap power supplies
You must turn off the server before you connect or disconnect cables.
See the documentation that comes with any external devices for additional cabling
instructions. It might be easier for you to route cables before you connect the
devices to the server.
81
Updating the server configuration

Use this information to update the server configuration.
When you start the server for the first time after you add or remove a device, you
might receive a message that the configuration has changed. The Setup utility
starts automatically so that you can save the new configuration settings.
Some optional devices have device drivers that you must install. For information
about installing device drivers, see the documentation that comes with each device.
If the server has an optional RAID adapter and you have installed or removed a
hard disk drive, see the documentation that comes with the RAID adapter for
information about reconfiguring the disk arrays.
The server comes with at least one microprocessor. If more that one microprocessor
is installed, the server can operate as a symmetric multiprocessing (SMP) server.
You might have to upgrade the operating system to support SMP. For more
information, see Typical operating-system installation on page 87 and the
operating-system documentation.
For information about configuring the integrated Gigabit Ethernet controller, see
Configuring the Gigabit Ethernet controller on page 100.
82
Chapter 3. Configuration information and instructions

This chapter provides information about updating the firmware and using the
configuration utilities.
Updating the firmware

Use this information to update the system firmware.
Important:: Some cluster solutions require specific code levels or coordinated code
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. Use UpdateXpress System Pack Installer to acquire and apply UpdateXpress
System Packs and individual firmware and device-driver updates. For additional
information and to download the UpdateXpress System Pack Installer, go to the
ToolsCenter for System x and BladeCenter at http://www.ibm.com/support/
entry/portal/docdisplay?lndocid=TOOL-CENTER and click UpdateXpress System
Pack Installer.
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.
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.
The firmware for the server is periodically updated and is available for download
on the IBM wb site. To check for the latest level of firmware, such as the UEFI
firmware, vital product data (VPD) code, device drivers, and integrated
management module (IMM) firmware, go to http://www.ibm.com/support/
fixcentral.
Note: Before you update the firmware, be sure to back up any data that is stored
in the Trusted Platform Module (TPM), in case any of the TPM characteristics are
changed by the new firmware. For instructions, see your encryption software
documentation.
Download the latest firmware for the server; then, install the firmware, using the
instructions that are included with the downloaded files.
When you replace a device in the server, you might have to either update the
firmware that is stored in memory on the device or restore the pre-existing
firmware from a diskette or CD image.
The following list indicates where the firmware is stored:
v UEFI firmware is stored in ROM on the system board.
v IMM firmware is stored in ROM on the system board.
83
v Ethernet firmware is stored in ROM on the Ethernet controller.

v ServeRAID firmware is stored in ROM on the ServeRAID adapter.
v SAS/SATA firmware is stored in ROM on the SAS/SATA controller on the
system board.
Configuring UEFI compatible devices

Use this information to configure UEFI compatible devices.
UEFI compatible expansion cards can be configured through the Setup utility. To
configure a UEFI compatible expansion card, complete the following steps:
Note: Before configuring a UEFI compatible device, it is recommended to update
the firmware for your server. See Updating the firmware on page 83 for
information on how to update the firmware for your server.
1. Run the Setup utility (see Using the Setup utility on page 88).
2. Select System Settings Network or Storage depending on the type of your
adapters.
Note: Select System Settings Adapters and UEFI drivers for UEFI 2.0 (and
prior) compliant adapters and drivers installed in the server.
3. Select Please refresh this page first and press Enter.
4. Select the device driver that you want to configure and press Enter.
5. When you have finished changing settings, press Esc to exit from the program;
select Save to save the settings that you have changed.
Configuring the server

The following configuration programs come with the server:
v Setup utility
The UEFI Setup Utility program is part of the basic input/output system
firmware. Use it to change interrupt request (IRQ) settings, change the
startup-device sequence, set the date and time, and set passwords. For
information about using this program, see Using the Setup utility on page 88.
v Boot Manager program
The Boot Manager program is part of the server firmware. Use it to override the
startup sequence that is set in the Setup utility and temporarily assign a device
to be first in the startup sequence. For more information about using this
program, see Using the Boot Manager program on page 94.
v IBM ServerGuide Setup and Installation CD
The ServerGuide program provides software-setup tools and installation tools
that are designed for the server. Use this CD during the installation of the server
to configure basic hardware features, such as an integrated SAS/SATA controller
with RAID capabilities, and to simplify the installation of your operating system.
For information about using this CD, see Using the ServerGuide Setup and
Installation CD on page 86.
v IBM FastSetup
IBM FastSetup is a no-cost software tool that helps simplify the maintenance and
deployment of selected IBM BladeCenter chassis, servers, and components. The
intuitive graphical interface initializes all phases of server setup, including
discovery, update, and configuration. Features include templates that enable
replication of settings to many servers and automation that reduces hands-on
84
time and user errors. Wizards and other default settings enable customization
capabilities. The low-touch, set-once and walk-away feature reduces the
hands-on server setup time from days to minutes, particularly for larger
deployments. For information about this tool, see http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=TOOL-FASTSET.
v Integrated Management Module
Use the integrated management module II (IMM2) for configuration, to update
the firmware and sensor data record/field replaceable unit (SDR/FRU) data, and
to remotely manage a network. For information about using the IMM, see
Using the integrated management module II on page 95 and the Integrated
Management Module User's Guide at www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5089484&brandind=5000008.
v VMware ESXi embedded hypervisor
An optional USB flash device with VMware ESXi embedded hypervisor software
is available for purchase. Hypervisor is virtualization software that enables
multiple operating systems to run on a host system at the same time. The USB
embedded hypervisor flash device installs in the USB connector on the system
board. For more information about using the embedded hypervisor, see Using
the embedded hypervisor on page 97.
v Remote presence capability and blue-screen capture
The remote presence and blue-screen capture features are integrated functions of
the Integrated Management Module II (IMM2). The remote presence feature
provides the following functions:
Remotely viewing video with graphics resolutions up to 1600 x 1200 at 75 Hz,
regardless of the system state
Remotely accessing the server, using the keyboard and mouse from a remote
client
Mapping the CD or DVD drive, diskette drive, and USB flash drive on a
remote client, and mapping ISO and diskette image files as virtual drives that
are available for use by the server
Uploading a diskette image to the IMM memory and mapping it to the server
as a virtual drive
The blue-screen capture feature captures the video display contents before the
IMM restarts the server when the IMM detects an operating-system hang
condition. A system administrator can use the blue-screen capture feature to
assist in determining the cause of the hang condition.
v Ethernet controller configuration
For information about configuring the Ethernet controller, see Configuring the
Gigabit Ethernet controller on page 100.
v Configuring RAID arrays
For information about configuring RAID arrays, see Configuring RAID arrays.
v IBM Advanced Settings Utility (ASU) program
Use this program as an alternative to the Setup utility for modifying UEFI
settings and IMM settings. Use the ASU program online or out of band to
modify UEFI settings from the command line without the need to restart the
server to access the Setup utility. For more information about using this
program, see IBM Advanced Settings Utility program on page 104.
85
Using the ServerGuide Setup and Installation CD

Use this information as an overview for using the ServerGuide Setup and
Installation CD.
The ServerGuide Setup and Installation CD provides software setup tools and
installation tools that are designed for your server. The ServerGuide program
detects the server model and optional hardware devices that are installed and uses
that information during setup to configure the hardware. The ServerGuide
simplifies the operating-system installations by providing updated device drivers
and, in some cases, installing them automatically.
You can download a free image of the ServerGuide Setup and Installation CD or
purchase the CD from the ServerGuide fulfillment Web site at
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-GUIDE. To
download the free image. click IBM Service and Support Site.
Note: Changes are made periodically to the IBM web site. The actual procedure
might vary slightly from what is described in this document.
The ServerGuide program requires a supported IBM server with an enabled
startable (bootable) CD drive. In addition to the ServerGuide Setup and Installation
CD, you must have your operating-system CD to install the operating system.
To start the ServerGuide Setup and Installation CD, complete the following steps:
1. Insert the CD, and restart the server. If the CD does not start, see ServerGuide
problems on page 153.
2. Follow the instructions on the screen to complete the following steps:
a. Select your language.
b. Select your keyboard layout and country.
c. View the overview to learn about ServerGuide features.
d. View the readme file to review installation tips for your operating system
and adapter.
e. Start the operating-system installation. You will need your operating-system
CD.
ServerGuide features
This information provides an overview of the ServerGuide features.
Features and functions can vary slightly with different versions of the ServerGuide
program. To learn more about the version that you have, start the ServerGuide Setup
and Installation CD and view the online overview. Not all features are supported on
all server models.
The ServerGuide program performs the following tasks:
v Sets system date and time
v Detects the RAID adapter or controller and runs the SAS/SATA RAID
configuration program
v Checks the microcode (firmware) levels of a ServeRAID adapter and determines
whether a later level is available from the CD
v Detects installed hardware options and provides updated device drivers for
most adapters and devices
v Provides diskette-free installation for supported Windows operating systems
v Includes an online readme file with links to tips for your hardware and
operating-system installation
86
Setup and configuration overview

Use this information for the ServerGuide setup and configuration.
When you use the ServerGuide Setup and Installation CD, you do not need setup
diskettes. You can use the CD to configure any supported IBM server model. The
setup program provides a list of tasks that are required to set up your server
model. On a server with a ServeRAID adapter or SAS/SATA controller with RAID
capabilities, you can run the SAS/SATA RAID configuration program to create
logical drives.
Note: Features and functions can vary slightly with different versions of the
ServerGuide program.
Typical operating-system installation

This section details the ServerGuide typical operating-system installation.
The ServerGuide program can reduce the time it takes to install an operating
system. It provides the device drivers that are required for your hardware and for
the operating system that you are installing. This section describes a typical
ServerGuide operating-system installation.
Note: Features and functions can vary slightly with different versions of the
ServerGuide program.
1. After you have completed the setup process, the operating-system installation
program starts. (You will need your operating-system CD to complete the
installation.)
2. The ServerGuide program stores information about the server model, service
processor, hard disk drive controllers, and network adapters. Then, the
program checks the CD for newer device drivers. This information is stored
and then passed to the operating-system installation program.
3. The ServerGuide program presents operating-system partition options that are
based on your operating-system selection and the installed hard disk drives.
4. The ServerGuide program prompts you to insert your operating-system CD
and restart the server. At this point, the installation program for the operating
system takes control to complete the installation.
Installing your operating system without using ServerGuide

Use this information to install the operating system on the server without using
ServerGuide.
If you have already configured the server hardware and you are not using the
ServerGuide program to install your operating system, you can download
operating-system installation instructions for the server from http://
www.ibm.com/supportportal/.
87
Using the Setup utility

Use these instructions to start the Setup utility.
Use the Unified Extensible Firmware Interface (UEFI) Setup Utility program to
perform the following tasks:
v View configuration information
v View and change assignments for devices and I/O ports
v
v
v
v
v
v
v
Set the date and time

Set and change passwords
Set the startup characteristics of the server and the order of startup devices
Set and change settings for advanced hardware features
View, set, and change settings for power-management features
View and clear error logs
Change interrupt request (IRQ) settings
v Resolve configuration conflicts
Starting the Setup utility

Use this information to start up the Setup utility.
To start the Setup utility, complete the following steps:
1. Turn on the server.
Note: Approximately 1 to 3 minutes after the server is connected to ac power,
the power-control button becomes active.
2. When the prompt <F1> Setup is displayed, press F1. If you have set an
administrator password, you must type the administrator password to access
the full Setup utility menu. If you do not type the administrator password, a
limited Setup utility menu is available.
3. Select settings to view or change.
Setup utility menu choices

Use the Setup utility main menu to view and configure server configuration data
and settings.
The following choices are on the Setup utility main menu for the UEFI. Depending
on the version of the firmware, some menu choices might differ slightly from these
descriptions.
v System Information
Select this choice to view information about the server. When you make changes
through other choices in the Setup utility, some of those changes are reflected in
the system information; you cannot change settings directly in the system
information. This choice is on the full Setup utility menu only.
System Summary
Select this choice to view configuration information, including the ID, speed,
and cache size of the microprocessors, machine type and model of the server,
the serial number, the system UUID, and the amount of installed memory.
When you make configuration changes through other options in the Setup
utility, the changes are reflected in the system summary; you cannot change
settings directly in the system summary.
Product Data
88
Select this choice to view the system-board identifier, the revision level or
issue date of the firmware, the integrated management module and
diagnostics code, and the version and date.
This choice is on the full Setup utility menu only.
v System Settings
Select this choice to view or change the server component settings.
Adapters and UEFI Drivers
Select this choice to view information about the adapters and device drivers
installed in the server that are compliant with UEFI 1.10 and UEFI 2.0.
Processors
Select this choice to view or change the processor settings.
Memory
Select this choice to view or change the memory settings. To configure
memory mirroring, select System Settings Memory Memory Mode
Mirrored.
Devices and I/O Ports
Select this choice to view or change assignments for devices and
input/output (I/O) ports. You can configure the serial ports; configure remote
console redirection; enable or disable integrated Ethernet controllers, the
SAS/SATA adapter, SATA optical drive channels, and PCI slots; and view the
system Ethernet MAC addresses. If you disable a device, it cannot be
configured, and the operating system will not be able to detect it (this is
equivalent to disconnecting the device).
Power
Select this choice to view or change power capping to control consumption,
processors, and performance states.
- Active Energy Manager
Select this choice to enable or disable power capping. If you enable power
capping, the Active Energy Manager program will limit the maximum
power that is consumed by the server.
Note: It is available only when System Settings Processors Processor
Performance States is enabled.
- Power/Performance Bias
Select this choice to determine how the power management of the
microprocessor is controlled. You can choose either Platform Controlled
(system) or OS Controlled (operating system) to control the setting. Not all
operating systems support this feature.
- Platform Controlled Type
Select this choice to determine how to balance between performance and
power consumption. Choosing Maximum Performance will disable power
management functions and allow the most aggressive use of turbo.
Choosing Minimal Power will maximizes the use of power management
features for least power consumption and disable turbo.
Note: It is available only when System Settings Power
Power/Performance Bias Platform Controlled is enabled.
- Workload Configuration
Select this choice to determine how to balance between I/O bandwidth and
balanced workload. Choosing I/O sensitive will get higher I/O bandwidth
89
while expansion cards are used. Choosing Balanced will allow enough
frequency for workload while the microprocessor cores are idle.
Operating Modes
Select this choice to view or change the operating profile (performance and
power utilization). This choice specify a preset operating mode to configure
the server for maximum power savings, maximum efficiency, and maximum
performance.
- Choose Operating Mode
Select the operating mode based on your preference. Power savings and
performance are also highly dependent on hardware and software running
on the system. When a present mode is selected, the low-level settings are
not changeable and will be grayed out.
- Memory Speed
Select the desired memory speed. Maximum performance mode maximizes
performance. Balanced mode offers a balance between performance and
power. Minimal power mode maximizes power savings.
- Memory Power Management
Select this choice to enable or disable power management on memory. If
you choose Disabled, it will provide maximum performance but minimum
power savings. If you choose Automatic, it is suitable for most applications.
- Proc Performance States
Select this choice to enable or disable processor performance states.
Enabling processor performance states (Intel Speedstep Technology) saves
power by reducing speed and voltage as the microprocessor utilized is
reduced.
Note: Some operating systems must have the correct power profile selected
to take advantage of this feature.
- C1 Enhance Mode
Select this choice to enable or disable C1E (C1 Enhanced) state. Enabling
C1E (C1 Enhanced) state can save power by halting CPU cores that are
idle.
Note: An operating system that supports C1E state must be installed to
take advantage of this feature. Changing this setting will be effective after
the next system reboot.
- QPI Link Frequency
Select this choice to determine the desired microprocessor QPI link
frequency. Maximum performance mode maximizes performance. Balanced
mode offers a balance between performance and power. Minimal power
maximizes power savings.
- Turbo Mode
Select this choice to enable or disable turbo mode. Enabling turbo mode
can boost the overall microprocessor performance when all microprocessor
cores are not fully utilized. A microprocessor core can run above its rated
frequency for a short period of time when it is in turbo mode.
- CPU C-States
Select this choice to enable or disable ACPI C2 Processor Power states. It
will be effective after the next system reboot.
- Package ACPI CState Limit
90
Select this choice to determine the level of C-state. Selecting a higher

C-state limit allows the microprocessors to consume less power when they
are idle. If you experience problems with legacy operating systems, set the
ACPI Cstate limit to C2.
- Power/Performance Bias
Select this choice to determine how the power management of the
microprocessor is controlled. You can choose either Platform Controlled
(system) or OS Controlled (operating system) to control the setting. Not all
operating systems support this feature.
- Platform Controlled Type
Select this choice to determine how to balance between performance and
power consumption. Choosing Maximum Performance will disable power
management functions and allow the most aggressive use of turbo.
Choosing Minimal Power will maximizes the use of power management
features for least power consumption and disable turbo.
Legacy Support
Select this choice to view or set legacy support.
- Force Legacy Video on Boot
Select this choice to force INT video support, if the operating system does
not support UEFI video output standards.
- Rehook INT 19h
Select this choice to enable or disable devices from taking control of the
boot process. The default is Disable.
- Legacy Thunk Support
Select this choice to enable or disable UEFI to interact with PCI mass
storage devices that are non-UEFI compliant.
- Infinite Boot Retry
Select this choice to enable or disable Infinitely retry the Legacy Boot order.
- BBS Boot
Select this choice to enable or disable legacy boot in BBS manner.
System Security
Select this choice to view or configure Trusted Platform Module (TPM)
support.
Integrated Management Module
Select this choice to view or change the settings for the integrated
management module.
- Power Restore Policy
Select this choice to view or enable the POST watchdog timer.
- Commands on USB Interface Preference
Select this choice to enable or disable the Ethernet over USB interface on
IMM.
- Network Configuration
Select this choice to view the system management network interface port,
the IMM MAC address, the current IMM IP address, and the host name;
define the static IMM IP address, subnet mask, and gateway address;
specify whether to use the static IP address or have DHCP assign the IMM
IP address; save the network changes; and reset the IMM.
- Reset IMM to Defaults
Select this choice to view or reset IMM to the default settings.
91
- Reset IMM
Select this choice to reset the IMM settings.
Recovery
Select this option to configure recovery settings.
Storage
Select this option to see all the storage device settings.
Network
Select this choice to view or configure the network device options, such as
iSCSI, PXE, and network devices. There might be additional configuration
choices for optional network devices that are compliant with UEFI 2.1 and
later.
Driver Health
Select this option to view the status of the controllers in the system as
reported by their corresponding drivers.
v Date and Time
Select this choice to set the date and time in the server, in 24-hour format
(hour:minute:second).
v Start Options
Select this choice to view or change the start options, including the startup
sequence, keyboard NumLock state, PXE boot option, and PCI device boot
priority. Changes in the startup options take effect when you start the server.
The startup sequence specifies the order in which the server checks devices to
find a boot record. The server starts from the first boot record that it finds. If the
server has Wake on LAN hardware and software and the operating system
supports Wake on LAN functions, you can specify a startup sequence for the
Wake on LAN functions. For example, you can define a startup sequence that
checks for a disc in the CD-RW/DVD drive, then checks the hard disk drive,
and then checks a network adapter.
v Boot Manager
Select this choice to view, add, delete, or change the device boot priority, boot
from a file, select a one-time boot, or reset the boot order to the default setting.
v System Event Logs
Select this choice to enter the System Event Manager, where you can view the
POST event log and the system-event log. You can use the arrow keys to move
between pages in the error log.
The POST event log contains the three most recent error codes and messages
that were generated during POST.
The system-event log contains POST and system management interrupt (SMI)
events and all events that are generated by the baseboard management
controller that is embedded in the integrated management module (IMM).
Important: If the system-error LED on the front of the server is lit but there are
no other error indications, clear the system-event log. Also, after you complete a
repair or correct an error, clear the system-event log to turn off the system-error
LED on the front of the server.
POST Event Viewer
Select this choice to enter the POST event viewer to view the POST event log.
System Event Log
92
Select this choice to view the system event log.

Clear System Event Log
Select this choice to clear the system event log.
v User Security
Select this choice to set, change, or clear passwords. See Passwords for more
information.
This choice is on the full and limited Setup utility menu.
Power-on Password
Select this choice to set or change a power-on password. See Power-on
password on page 94 for more information.
Administrator Password
v
v
Select this choice to set or change an administrator password. An

administrator password is intended to be used by a system administrator; it
limits access to the full Setup utility menu. If an administrator password is
set, the full Setup utility menu is available only if you type the administrator
password at the password prompt. For more information, see Administrator
password on page 94.
Save Settings
Select this choice to save the changes that you have made in the settings.
Restore Settings
Select this choice to cancel the changes that you have made in the settings and
restore the previous settings.
Load Default Settings
Select this choice to cancel the changes that you have made in the settings and
restore the factory settings.
Exit Setup
Select this choice to exit from the Setup utility. If you have not saved the
changes that you have made in the settings, you are asked whether you want to
save the changes or exit without saving them.
Passwords
From the User Security menu choice, you can set, change, and delete a power-on
password and an administrator password.
The User Security choice is on the full Setup utility menu only.
If you set only a power-on password, you must type the power-on password to
complete the system startup and to have access to the full Setup utility menu.
An administrator password is intended to be used by a system administrator; it
limits access to the full Setup utility menu. If you set only an administrator
password, you do not have to type a password to complete the system startup, but
you must type the administrator password to access the Setup utility menu.
If you set a power-on password for a user and an administrator password for a
system administrator, you can type either password to complete the system
startup. A system administrator who types the administrator password has access
to the full Setup utility menu; the system administrator can give the user authority
to set, change, and delete the power-on password. A user who types the power-on
password has access to only the limited Setup utility menu; the user can set,
change, and delete the power-on password, if the system administrator has given
the user that authority.
93
Power-on password:
If a power-on password is set, when you turn on the server, you must type the
power-on password to complete the system startup. You can use any combination
of 6 - 20 printable ASCII characters for the password.
When a power-on password is set, you can enable the Unattended Start mode, in
which the keyboard and mouse remain locked but the operating system can start.
You can unlock the keyboard and mouse by typing the power-on password.
If you forget the power-on password, you can regain access to the server in any of
the following ways:
v If an administrator password is set, type the administrator password at the
password prompt. Start the Setup utility and reset the power-on password.
v Remove the battery from the server and then reinstall it. See Removing the
system battery on page 255 for instructions for removing the battery.
v Clear CMOS data by using the clear CMOS jumper (see System-board jumpers
on page 29 for more information).
Attention: Before you change any switch settings or move any jumpers, turn
off the server; then, disconnect all power cords and external cables. See the
safety information that begins on page Safety on page vii. Do not change
settings or move jumpers on any system-board switch or jumper blocks that are
not shown in this document.
Clearing CMOS data does not affect the administrator password.
Administrator password:
If an administrator password is set, you must type the administrator password for
access to the full Setup utility menu. You can use any combination of 6 to 20
printable ASCII characters for the password.
Attention: If you set an administrator password and then forget it, there is no
way to change, override, or remove it. You must replace the system board.
Using the Boot Manager program

Use this information for the Boot Manager.
The Boot Manager program is a built-in, menu-driven configuration utility
program that you can use to temporarily redefine the first startup device without
changing settings in the Setup utility.
To use the Boot Manager program, complete the following steps:
1. Turn off the server.
2. Restart the server.
3. When the prompt <F12> Select Boot Device is displayed, press F12. If a
bootable USB mass storage device is installed, a submenu item (USB Key/Disk)
is displayed.
4. Use the Up arrow and Down arrow keys to select an item from the Boot
Selection Menu and press Enter.
The next time the server starts, it returns to the startup sequence that is set in the
Setup utility.
94
Starting the backup server firmware

Use this information to start the backup server firmware.
The system board contains a backup copy area for the server firmware. This is a
secondary copy of the server firmware that you update only during the process of
updating the server firmware. If the primary copy of the server firmware becomes
damaged, use this backup copy.
To force the server to start from the backup copy, turn off the server; then, place
the J2 jumper in the backup position (pins 2 and 3).
Use the backup copy of the server firmware until the primary copy is restored.
After the primary copy is restored, turn off the server; then, move the J2 jumper
back to the primary position (pins 1 and 2).
The UpdateXpress System Pack Installer

The UpdateXpress System Pack Installer detects supported and installed device
drivers and firmware in the server and installs available updates.
For additional information and to download the UpdateXpress System Pack
Installer, go to the ToolsCenter for System x and BladeCenter at
http://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/ and click UpdateXpress
System Pack Installer.
Using the integrated management module II

The integrated management module (IMM) is a second generation of the functions
that were formerly provided by the baseboard management controller hardware. It
combines service processor functions, video controller, and remote presence
function in a single chip.
The IMM supports the following basic systems-management features:
v Active Energy Manager.
v Alerts (in-band and out-of-band alerting, PET traps - IPMI style, SNMP, e-mail).
v Auto Boot Failure Recovery (ABR).
v Automatic microprocessor disable on failure and restart in a two-microprocessor
configuration when one microprocessor signals an internal error. When one of
the microprocessors fail, the server will disable the failing microprocessor and
restart with the other microprocessor.
v Automatic Server Restart (ASR) when POST is not complete or the operating
system hangs and the operating system watchdog timer times-out. The IMM
might be configured to watch for the operating system watchdog timer and
reboot the system after a timeout, if the ASR feature is enabled. Otherwise, the
IMM allows the administrator to generate a nonmaskable interrupt (NMI) by
pressing an NMI button on the light path diagnostics panel for an
operating-system memory dump. ASR is supported by IPMI.
v A virtual media key, which enables remote presence support (remote video,
remote keyboard/mouse, and remote storage).
v Boot sequence manipulation.
v Command-line interface.
v Configuration save and restore.
95
v DIMM error assistance. The Unified Extensible Firmware Interface (UEFI)

disables a failing DIMM that is detected during POST, and the IMM lights the
associated system error LED and the failing DIMM error LED.
v Environmental monitor with fan speed control for temperature, voltages, fan
failure, power supply failure, and power backplane failure.
v Intelligent Platform Management Interface (IPMI) Specification V2.0 and
Intelligent Platform Management Bus (IPMB) support.
v Invalid system configuration (CNFG) LED support.
v Light path diagnostics LEDs indicators to report errors that occur with fans,
power supplies, microprocessor, hard disk drives, and system errors.
v Local firmware code flash update
v Nonmaskable interrupt (NMI) detection and reporting.
v Operating-system failure blue screen capture.
v PCI configuration data.
v PECI 3 support.
v Power/reset control (power-on, hard and soft shutdown, hard and soft reset,
schedule power control).
v
v
v
v
v
Query power-supply input power.

ROM-based IMM firmware flash updates.
Serial over LAN (SOL).
Serial port redirection over telnet or ssh.
SMI handling
v System event log (SEL) - user readable event log.

The IMM also provides the following remote server management capabilities
through the OSA SMBridge management utility program:
v Command-line interface (IPMI Shell)
The command-line interface provides direct access to server management
functions through the IPMI 2.0 protocol. Use the command-line interface to issue
commands to control the server power, view system information, and identify
the server. You can also save one or more commands as a text file and run the
file as a script.
v Serial over LAN
Establish a Serial over LAN (SOL) connection to manage servers from a remote
location. You can remotely view and change the UEFI settings, restart the server,
identify the server, and perform other management functions. Any standard
Telnet client application can access the SOL connection.
For more information about IMM, see the Integrated Management Module User's
Guide at www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5089484
&brandind=5000008.
96
Using the embedded hypervisor

The VMware ESXi embedded hypervisor software is available on the optional IBM
USB flash device with embedded hypervisor.
The USB flash device can be installed in the USB connector near PCI riser slot 1 on
the system board. Hypervisor is virtualization software that enables multiple
operating systems to run on a host system at the same time. The USB flash device
is required to activate the hypervisor functions.
Figure 66. Location of the embedded hypervisor USB flash device
To start using the embedded hypervisor functions, you must add the USB flash
device to the startup sequence in the Setup utility.
To add the USB flash device to the startup sequence, complete the following steps:
2. When the prompt <F1> Setup is displayed, press F1.
3. From the Setup utility main menu, select Boot Manager.
4. Select Add Boot Option; then, select USB Storage. Press Enter, and then select
Esc.
5. Select Change Boot Order and then select Commit Changes; then, press Enter.
6. Select Save Settings and then select Exit Setup.
97
If the embedded hypervisor flash device image becomes corrupt, you can use the
VMware Recovery CD that comes with the system to recover the flash device image.
To recover the flash device image, complete the following steps:
2. Insert the VMware Recovery CD into the CD or DVD drive.
3. Follow the instructions on the screen.
For additional information and instructions, see the VMware ESXi Server 31
Embedded Setup Guide a http://www-03.ibm.com/systems/x/os/vmware/esxi/
Using the remote presence and blue-screen capture features

The remote presence and blue-screen capture features are integrated functions of
the integrated management module II (IMM2).
The remote presence feature provides the following functions:
v Remotely viewing video with graphics resolutions up to 1600 x 1200 at 75 Hz,
regardless of the system state
v Remotely accessing the server, using the keyboard and mouse from a remote
client
v Mapping the CD or DVD drive, diskette drive, and USB flash drive on a remote
client, and mapping ISO and diskette image files as virtual drives that are
available for use by the server
v Uploading a diskette image to the IMM memory and mapping it to the server as
a virtual drive
The blue-screen capture feature captures the video display contents before the IMM
restarts the server when the IMM detects an operating-system hang condition. A
system administrator can use the blue-screen capture to assist in determining the
cause of the hang condition.
For more information on Features on Demand (FoD), including instructions for
automating the activation and installation of the activation key by using IBM
ToolsCenter or IBM Director, see the IBM System x Features on Demand User's
Guide at/http://www.ibm.com/systems/x/fod/under the Help section.
Note: The server may need to be restarted to activate the feature.
98
Obtaining the IP address for the IMM

Use this information to obtain the IP address for the IMM.
If you are logging on to the IMM for the first time after installation, the IMM
defaults to DHCP. If a DHCP server is not available, the IMM uses a static IP
address of 192.168.70.125. The default IPv4 host name is IMM- (plus the last 12
characters on the IMM MAC address). The default host name also comes on the
IMM network access tag that comes attached to the power supply on the rear of
the server. The IMM network access tag provides the default host name of the
IMM and does not require you to start the server.
The IPv6 link-local address (LLA) is derived from the IMM default host name. The
IMM LLA is on the IMM network access tag is on the power supply on the rear of
the server. To derive the link-local address, complete the following steps:
Note: IPv6 address will not immediately show on host address when we change
the values and have to exit and re-visit the driver to get the actual value.
1. Take the last 12 characters on the IMM MAC address (for example,
5CF3FC5EAAD0).
2. Separate the number into pairs of hexadecimal characters (for example,
5C:F3:FC:5E:AA:D0).
3. Separate the first six and last six hexadecimal characters.
4. Add FF and FE in the middle of the 12 characters (for example, 5C F3 FC
FF FE 5E AA D0).
5. Convert the first pair of hexadecimal characters to binary (for example, 5=0101,
C=1100, which results in 01011100 F3 FC FF FE 5E AA D0).
6. Flip the 7th binary character from left (0 to 1 or 1 to 0), which results in
01011110 F3 FF FE 5E AA D0.
7. Convert the binary back to hexadecimal (for example, 5E F3FCFFFE5EAAD0).
Logging on to the Web interface

Use this information to log on to the web interface.
To log on to the IMM Web interface, complete the following steps:
1. Open a Web browser on a computer that connects to the server and in the
Address or URL field, type the IP address or host name of the IMM to which
you want to connect.
Note: If you are logging on to the IMM for the first time after installation, the
IMM defaults to DHCP. If a DHCP host is not available, the IMM assigns a
static IP address of 192.168.70.125. The MAC address tag provides the default
hostname of the IMM and does not require you to start the server.
2. On the Login page, type the user name and password. If you are using the
IMM for the first time, you can obtain the user name and password from your
system administrator. All login attempts are documented in the event log.
Note: The IMM is set initially with a user name of USERID and password of
PASSW0RD (passw0rd with a zero, not a the letter O). You have read/write
access. You must change the default password the first time you log on.
3. On the Welcome page, type a timeout value (in minutes) in the field that is
provided. The IMM will log you off of the Web interface if your browser is
inactive for the number of minutes that you entered for the timeout value.
99
4. Click Continue to start the session. The System Health page provides a quick
view of the system status.
Enabling the Intel Gigabit Ethernet Utility program

Use this information to Enabling the Intel Gigabit Ethernet Utility program.
The Intel Gigabit Ethernet Utility program is part of the server firmware. You can
use it to configure the network as a startable device, and you can customize where
the network startup option appears in the startup sequence. Enable and disable the
Intel Gigabit Ethernet Utility program from the Setup utility.
Configuring the Gigabit Ethernet controller

Use this information to configure the Gigabit Ethernet controller.
The Ethernet controllers are integrated on the system board. They provide an
interface for connecting to a 10 Mbps, 100 Mbps, or 1 Gbps network and provide
full-duplex (FDX) capability, which enables simultaneous transmission and
reception of data on the network. If the Ethernet ports in the server support
auto-negotiation, the controllers detect the data-transfer rate (10BASE-T,
100BASE-TX, or 1000BASE-T) and duplex mode (full-duplex or half-duplex) of the
network and automatically operate at that rate and mode.
By default the server has enabled Ethernet 1 and Ethernet 2. Ethernet 3 and
Ethernet 4 can be enabled by the Features on Demand (FoD). Please note that the
server may need to be restarted to activate the feature. Meanwhile, when switching
from dedicated mode (Ethernet 2) to shared mode (Ethernet 1), followed by the
activation of Ethernet 3 and Ethernet 4 via the Features on Demand (FoD) or vice
versa, remember to first unplug and subsequently plug back the power cable or
cables to the server (power cycle). For more information on Features on Demand
(FoD), including instructions for automating the activation and installation of the
activation key by using IBM ToolsCenter or IBM Director, see the IBM System x
Features on Demand User's Guide at /http://www.ibm.com/systems/x/fod/
under the Help section.
You do not have to set any jumpers or configure the controllers. However, you
must install a device driver to enable the operating system to address the
controllers. For device drivers and information about configuring the Ethernet
controllers or to find updated information about configuring the controllers, see
100
Configuring RAID arrays

Use the configuration utility programs to configure and manage redundant array
of independent disks (RAID) arrays.
Be sure to use this program as described in this document.
The following table lists the different server configurations and the applications
that are available for configuring and managing RAID arrays.
Table 11. Server configuration and applications for configuring and managing RAID arrays
RAID array configuration
(before operating system is
installed)
RAID array management

(after operating system is
installed)
ServeRAID-H1110 adapter
LSI Utility (Setup utility,

press Ctrl+C), ServerGuide,
Human Interface
Infrastructure (HII)
MegaRAID Storage Manager

(MSM), SAS2IRCU
(Command Line) Utility for
Storage Management
ServeRAID-M1115 adapter
MegaRAID BIOS
Configuration Utility (press
Ctrl+H to start), pre-boot CLI
(press Ctrl+P to start),
ServerGuide, HII

(MSM), MegaCLI (Command
Line Interface), and IBM
Director
ServeRAID-M5110,
ServeRAID-M5120 adapters

MegaRAID BIOS
(MSM), MegaCLI, and IBM
Configuration Utility (press
Ctrl+H to start), pre-boot CLI Director
(press Ctrl+P to start),
ServerGuide, HII
ServeRAID-C105
HII
Server configuration

(MSM), MegaCLI, and IBM
Director
Note:
1. For more information about Problem Determination and Service Guide for
ServeRAID M controllers, see .
2. For more information about Configuration and Options Guide (COG), see .
3. For further details on creating a software RAID array of hard disk drives,
please see the ServeRAID C105 documentation at .
4. When the ServeRAID adapter is removed, software RAID will not be
supported. This system does not support downgrade software RAID function
from hardware RAID configuration.
101
Starting the LSI Configuration Utility program

Use these instructions to start the LSI Configuration Utility program.
To start the LSI Configuration Utility program, complete the following steps:
1. Turn on the server, and make sure that the server is the owner of the keyboard,
video, and mouse.
2. When the prompt message is displayed, you may perform either of the
following:
a. ServeRAID-H1110: press Ctrl+C.
b. ServeRAID-M5110, ServeRAID-M5120, or ServeRAID-M1115: press
Ctrl+H.
When you have finished changing settings, press Esc to exit from the program;
Starting the Human Interface Infrastructure (HII) Configuration

Application
Use these instructions to start the Human Interface Infrastructure (HII)
configuration utility program.
To start the Human Interface Infrastructure (HII) configuration utility program,
the power-control button becomes active after the power-on LED flashes slowly.
2. When prompted, <F1 Setup> is displayed, press F1. If you have set an
administrator password, you are prompted to type the password.
3. Under System Settings, select Storage.
When you have finished changing settings, press Esc to exit from the program;
Creating RAID of hard disk drives (ServeRAID-C105 only)

Use these instructions to create the RAID of hard disk drives (ServeRAID-C105
only).
Note:
1. If there is a ServeRAID adapter in slot 3, ServeRAID-C105 will not work.
2. ServeRAID-C105 uses HII only for configuration and there is no legacy
configuration utility.
To create RAID of hard disk drives (ServeRAID-C105 only), complete the following
steps:
the power-control button becomes active after the power-on LED flashes
slowly.
3. Under System Settings, select Storage.
4. Under Storage, select ServeRAID C105.
102
5. Under Configuration Options, select Virtual Drive Management Create

Configuration.
6. Select the type of array that you want to create.
7. Select Select Drives and use space key to select all the drives for your array.
8. Select Apply Changes to create the array.
9. When the prompt Success is displayed, select OK to continue.
10. After the system auto skip to the next screen, select Save Configuration.
11. When the prompt Creating Virtual Drives will cause the data lost on
the associated Drives to be permanently deleted. is displayed, use space
key to select Yes to continue.
12. Select OK to continue.
13. To initialize virtual disk, select ServeRAID C105 Virtual Drive Management
Select Virtual Drive Operations.
14. Under Virtual Drive Operation, choose Select Operation. Select the type of
initialization you want to initialize.
15. Select Start Operation.
16. Select Yes to confirm.
17. Select OK to continue.
18. When the prompt Success is displayed, select OK.
Note:
1. For further details on creating a software RAID array of hard disk drives,
please see the ServeRAID C105 documentation at .
2. Some specific models may be shipped initially with four hard disk drives.
Configuration may be able to expand to eight hard disk drives via Features on
Demand (FoD). Please note that the server may need to be restarted to activate
the feature. For more information on Features on Demand (FoD), including
instructions for automating the activation and installation of the activation key
by using IBM ToolsCenter or IBM Systems Director, see the IBM Features on
Demand User's Guide at /http://www.ibm.com/systems/x/fod/ under the
Help section.
3. Software RAID does not support VMware 5 and VMware 4.1.
4. Software RAID does not support legacy configuration.
5. In order to install the legacy OS in the software RAID, you have to set the SCU
Controller as the first device in the option ROM execution order.
6. ServeRAID-C105 does not support both hot-swap and solid-state drives.
103
IBM Advanced Settings Utility program

The IBM Advanced Settings Utility (ASU) program is an alternative to the Setup
utility for modifying UEFI settings.
Use the ASU program online or out of band to modify UEFI settings from the
command line without the need to restart the system to access the Setup utility.
You can also use the ASU program to configure the optional remote presence
features or other IMM settings. The remote presence features provide enhanced
systems-management capabilities.
In addition, the ASU program provides limited settings for configuring the IPMI
function in the IMM through the command-line interface.
Use the command-line interface to issue setup commands. You can save any of the
settings as a file and run the file as a script. The ASU program supports scripting
environments through a batch-processing mode.
For more information and to download the ASU program, go to
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=TOOL-ASU.
Updating IBM Systems Director

Use this information to update the IBM Systems Director.
If you plan to use IBM Systems Director to manage the server, you must check for
the latest applicable IBM Systems Director updates and interim fixes.
Note: Changes are made periodically to the IBM Web site. The actual procedure
To locate and install a newer version of IBM Systems Director, complete the
following steps:
1. Check for the latest version of IBM Systems Director:
a. Go to .
b. If a newer version of IBM Systems Director than what comes with the
server is shown in the drop-down list, follow the instructions on the Web
page to download the latest version.
2. Install the IBM Systems Director program.
If your management server is connected to the Internet, to locate and install
updates and interim fixes, complete the following steps:
1. Make sure that you have run the Discovery and Inventory collection tasks.
2. On the Welcome page of the IBM Systems Director Web interface, click View
updates.
3. Click Check for updates. The available updates are displayed in a table.
4. Select the updates that you want to install, and click Install to start the
installation wizard.
If your management server is not connected to the Internet, to locate and install
updates and interim fixes, complete the following steps:
1. Make sure that you have run the Discovery and Inventory collection tasks.
104
2. On a system that is connected to the Internet, go to http://www.ibm.com/

support/fixcentral.
3. From the Product family list, select IBM Systems Director.
4. From the Product list, select IBM Systems Director.
5. From the Installed version list, select the latest version, and click Continue.
6. Download the available updates.
7. Copy the downloaded files to the management server.
8. On the management server, on the Welcome page of the IBM Systems Director
Web interface, click the Manage tab, and click Update Manager.
9. Click Import updates and specify the location of the downloaded files that
you copied to the management server.
10. Return to the Welcome page of the Web interface, and click View updates.
11. Select the updates that you want to install, and click Install to start the
installation wizard.
Updating the Universal Unique Identifier (UUID)

The Universal Unique Identifier (UUID) must be updated when the system board
is replaced. Use the Advanced Settings Utility to update the UUID in the
UEFI-based server.
The ASU is an online tool that supports several operating systems. Make sure that
you download the version for your operating system. You can download the ASU
from the IBM Web site. To download the ASU and update the UUID, complete the
following steps.
1. Download the Advanced Settings Utility (ASU):
a. Go to http://www.ibm.com/supportportal/.
b. Click on the Downloads tab at the top of the panel.
c. Under ToolsCenter, select View ToolsCenter downloads.
d. Select Advanced Settings Utility (ASU).
e. Scroll down and click on the link and download the ASU version for your
operating system.
2. ASU sets the UUID in the Integrated Management Module (IMM). Select one of
the following methods to access the Integrated Management Module (IMM) to
set the UUID:
v Online from the target system (LAN or keyboard console style (KCS) access)
v Remote access to the target system (LAN based)
v Bootable media containing ASU (LAN or KCS, depending upon the bootable
media)
Note: IBM provides a method for building a bootable media. You can create
a bootable media using the Bootable Media Creator (BoMC) application from
the Tools Center Web site. In addition, the Windows and Linux based tool
kits are also available to build a bootable media. These tool kits provide an
alternate method to creating a Windows Professional Edition or Master
Control Program (MCP) based bootable media, which will include the ASU
application.
105
3. Copy and unpack the ASU package, which also includes other required files, to
the server. Make sure that you unpack the ASU and the required files to the
same directory. In addition to the application executable (asu or asu64), the
following files are required:
v For Windows based operating systems:
ibm_rndis_server_os.inf
device.cat
v For Linux based operating systems:
cdc_interface.sh
4. After you install ASU, use the following command syntax to set the UUID:
asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value> [access_method]
Where:
<uuid_value>
Up to 16-byte hexadecimal value assigned by you.
[access_method]
The access method that you selected to use from the following
methods:
v Online authenticated LAN access, type the command:
[host <imm_internal_ip>] [user <imm_user_id>][password <imm_password>]
Where:
imm_internal_ip
The IMM internal LAN/USB IP address. The default value is
169.254.95.118.
imm_user_id
The IMM account (1 of 12 accounts). The default value is USERID.
imm_password
The IMM account password (1 of 12 accounts). The default value is
PASSW0RD (with a zero 0 not an O).
Note: If you do not specify any of these parameters, ASU will use the
default values. When the default values are used and ASU is unable to access
the IMM using the online authenticated LAN access method, ASU will
automatically use the unauthenticated KCS access method.
The following commands are examples of using the userid and password
default values and not using the default values:
Example that does not use the userid and password default values:
asu set SYSTEM_PROD_DATA.SYsInfoUUID <uuid_value> --user <user_id>
--password <password>
Example that does use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value>
v Online KCS access (unauthenticated and user restricted):
You do not need to specify a value for access_method when you use this
access method.
Example:
asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value>
The KCS access method uses the IPMI/KCS interface. This method requires
that the IPMI driver be installed. Some operating systems have the IPMI
106
driver installed by default. ASU provides the corresponding mapping layer.

See the Advanced Settings Utility Users Guide for more details. You can access
the ASU Users Guide from the IBM Web site.
Note: Changes are made periodically to the IBM Web site. The actual
procedure might vary slightly from what is described in this document.
Go to http://www.ibm.com/supportportal/.
Click on the Downloads tab at the top of the panel.
Under ToolsCenter, select View ToolsCenter downloads.
Select Advanced Settings Utility (ASU).
Scroll down and click on the link and download the ASU version for
your operating system. Scroll down and look under Online Help to
download the Advanced Settings Utility Users Guide.
v Remote LAN access, type the command:
a.
b.
c.
d.
e.
Note: When using the remote LAN access method to access IMM using the
LAN from a client, the host and the imm_external_ip address are required
parameters.
host <imm_external_ip> [user <imm_user_id>][password <imm_password>]
Where:
imm_external_ip
The external IMM LAN IP address. There is no default value. This
parameter is required.
imm_user_id
imm_password
Example that does not use the userid and password default values:
asu set SYSTEM_PROD_DATA.SYsInfoUUID <uuid_value> --host <imm_ip>
--user <user_id> --password <password>
Example that does use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoUUID <uuid_value> --host <imm_ip>
v Bootable media:
You can also build a bootable media using the applications available through
the Tools Center Web site at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=TOOL-CENTER. From the IBM Tools Center page, scroll
down for the available tools.
107
Updating the DMI/SMBIOS data

Use this information to update the DMI/SMBIOS data.
The Desktop Management Interface (DMI) must be updated when the system
board is replaced. Use the Advanced Settings Utility (ASU) to update the DMI in
the UEFI-based server. The ASU is an online tool that supports several operating
systems. Make sure that you download the version for your operating system. You
can download the ASU from the IBM Web site. To download the ASU and update
the DMI, complete the following steps.
1. Download the Advanced Settings Utility (ASU):
a. Go to http://www.ibm.com/supportportal/.
e. Scroll down and click on the link and download the ASU version for your
operating system.
2. ASU sets the DMI in the Integrated Management Module (IMM). Select one of
the following methods to access the Integrated Management Module (IMM) to
set the DMI:
v Online from the target system (LAN or keyboard console style (KCS) access)
v Remote access to the target system (LAN based)
v Bootable media containing ASU (LAN or KCS, depending upon the bootable
media)
Note: IBM provides a method for building a bootable media. You can create
a bootable media using the Bootable Media Creator (BoMC) application from
the Tools Center Web site. In addition, the Windows and Linux based tool
kits are also available to build a bootable media. These tool kits provide an
alternate method to creating a Windows Professional Edition or Master
Control Program (MCP) based bootable media, which will include the ASU
application.
3. Copy and unpack the ASU package, which also includes other required files, to
the server. Make sure that you unpack the ASU and the required files to the
same directory. In addition to the application executable (asu or asu64), the
following files are required:
v For Windows based operating systems:
ibm_rndis_server_os.inf
device.cat
v For Linux based operating systems:
cdc_interface.sh
4. After you install ASU, Type the following commands to set the DMI:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> [access_method]
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> [access_method]
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> [access_method]
Where:
108
<m/t_model>
The server machine type and model number. Type mtm xxxxyyy, where
xxxx is the machine type and yyy is the server model number.
<s/n>
The serial number on the server. Type sn zzzzzzz, where zzzzzzz is the
serial number.
<asset_method>
The server asset tag number. Type asset
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, where
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa is the asset tag number.
[access_method]
The access method that you select to use from the following methods:
v Online authenticated LAN access, type the command:
[host <imm_internal_ip>] [user <imm_user_id>][password <imm_password>]
Where:
imm_internal_ip
The IMM internal LAN/USB IP address. The default value is
169.254.95.118.
imm_user_id
imm_password
Note: If you do not specify any of these parameters, ASU will use the
default values. When the default values are used and ASU is unable to access
the IMM using the online authenticated LAN access method, ASU will
automatically use the following unauthenticated KCS access method.
Examples that do not use the userid and password default values:
asu set SYSTEM_PROD_DATA.SYsInfoProdName <m/t_model>
--user <imm_user_id> --password <imm_password>
asu set SYSTEM_PROD_DATA.SYsInfoSerialNum <s/n> --user <imm_user_id>
--password <imm_password>
asu set SYSTEM_PROD_DATA.SYsEncloseAssetTag <asset_tag>
Examples that do use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>
v Online KCS access (unauthenticated and user restricted):
You do not need to specify a value for access_method when you use this
access method.
The KCS access method uses the IPMI/KCS interface. This method requires
that the IPMI driver be installed. Some operating systems have the IPMI
driver installed by default. ASU provides the corresponding mapping layer.
You can download the ASU from the IBM Web site. To download the
Advanced Settings Utility Users Guide, complete the following steps.
109
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 tohttp://www.ibm.com/supportportal/.
e. Scroll down and click on the link and download the ASU version for
your operating system. Scroll down and look under Online Help to
download the Advanced Settings Utility Users Guide.
asu set SYSTEM_PROD_DATA.SYsInfoProdName <m/t_model>
asu set SYSTEM_PROD_DATA.SYsInfoSerialNum <s/n>
v Remote LAN access, type the command:
Note: When using the remote LAN access method to access IMM using the
LAN from a client, the host and the imm_external_ip address are required
parameters.
host <imm_external_ip> [user <imm_user_id>][password <imm_password>]
Where:
imm_external_ip
The external IMM LAN IP address. There is no default value. This
parameter is required.
imm_user_id
imm_password
asu set SYSTEM_PROD_DATA.SYsInfoProdName <m/t_model> --host <imm_ip>
asu set SYSTEM_PROD_DATA.SYsInfoSerialNum <s/n> --host <imm_ip>
--host <imm_ip> --user <imm_user_id> --password <imm_password>
Examples that do use the userid and password default values:
asu set SYSTEM_PROD_DATA.SysInfoProdName <m/t_model> --host <imm_ip>
asu set SYSTEM_PROD_DATA.SysInfoSerialNum <s/n> --host <imm_ip>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag>
--host <imm_ip>
v Bootable media:
110
You can also build a bootable media using the applications available through
the ToolsCenter Web site at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=TOOL-CENTER. From the IBM ToolsCenter page, scroll
down for the available tools
111
112
Chapter 4. Troubleshooting
This chapter describes the diagnostic tools and troubleshooting information that
are available to help you solve problems that might occur in the server.
If you cannot diagnose and correct a problem by using the information in this
chapter, see Appendix D, Getting help and technical assistance, on page 669 for
more information.
Start here
You can solve many problems without outside assistance by following the
troubleshooting procedures in this documentation and on the World Wide Web.
This document describes the diagnostic tests that you can 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. Return the server to the condition it was in before the problem occurred. If
any hardware, software, or firmware was changed before the problem occurred,
if possible, reverse those changes. This might include any of the following
items:
v
v
v
v
v
Hardware components
Device drivers and firmware
System software
UEFI firmware
System input power or network connections
2. View the light path diagnostics LEDs and event logs. The server is designed
for ease of diagnosis of hardware and software problems.
v Light path diagnostics LEDs: See Light path diagnostics LEDs on page 123
for information about using light path diagnostics LEDs.
v Event logs: See Event logs on page 130 for information about notification
events and diagnosis.
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 website for documentation.
3. Run IBM Dynamic System Analysis (DSA) and 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. For
instructions for running DSA, see the Dynamic System Analysis Installation and
User's Guide.
113
To download the latest version of DSA code and the Dynamic System Analysis
Installation and User's Guide, go to http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=SERV-DSA.
4. Check for and apply code updates. Fixes or workarounds for many problems
might be available in updated UEFI firmware, device firmware, or device
drivers. To display a list of available updates for the server, go to
Attention: Installing the wrong firmware or device-driver update might cause
the server to malfunction. Before you install a firmware or device-driver
update, read any readme and change history files that are provided with the
downloaded update. These files contain important information about the
update and the procedure for installing the update, including any special
procedure for updating from an early firmware or device-driver version to the
latest version.
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.
a. Install UpdateXpress system updates. 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. In addition, you can
use IBM ToolsCenter Bootable Media Creator to create bootable media that
is suitable for applying firmware updates and running preboot diagnostics.
For more information about UpdateXpress System Packs, see
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERVXPRESS and Updating the firmware on page 83. For more information
about the Bootable Media Creator, see http://www.ibm.com/support/
entry/portal/docdisplay?lndocid=TOOL-BOMC.
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 (see step 4b).
b. Install manual system updates.
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.
To display a list of available updates for the server, go to
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.
5. 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.
a. Make sure that all installed hardware and software are supported. See
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us
to verify that the server supports the installed operating system, optional
devices, and software levels. If any hardware or software component is not
supported, uninstall it to determine whether it is causing the problem. You
114
must remove nonsupported hardware before you contact IBM or an

approved warranty service provider for support.
b. 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. For information about performing
the checkout procedure, see About the checkout procedure on page 116.
For information about configuring the server, see Chapter 3, Configuration
information and instructions, on page 83.
6. See controller and management software documentation. 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, go to
7. 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, go to
8. Use the troubleshooting tables. See Troubleshooting by symptom on page
137 to find a solution to a problem that has identifiable symptoms.
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/entry/portal/Open_service_request. 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 light path 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/entry/
portal/Open_service_request. Be prepared to provide information about any error
codes and collected data and the problem determination procedures that you have
used.
115
Service bulletins
IBM continually updates the support website with the latest tips and techniques
that you can use to solve problem that you might have with the IBM System x3530
M4 server.
To find service bulletins that are available for the IBM System x3530 M4 server, go
to http://www.ibm.com/supportportal/ and search for 7160 and retain.
Checkout procedure
The checkout procedure is the sequence of tasks that you should follow to
diagnose a problem in the server.
About the checkout procedure

Before you perform the checkout procedure for diagnosing hardware problems,
review the following information.
v Read the safety information that begins on page Safety on page vii.
v IBM Dynamic System Analysis (DSA) provides the primary methods of testing
the major components of the server, such as the system board, Ethernet
controller, keyboard, mouse (pointing device), serial ports, and hard disk drives.
You can also use them to test some external devices. 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 DSA, 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 DSA.
Exception: If multiple error codes or light path diagnostics LEDs indicate a
microprocessor error, the error might be in the microprocessor or in the
microprocessor socket. See Microprocessor problems on page 146 for
information about diagnosing microprocessor problems.
v Before you run diagnostic programs, you must determine whether the failing
server is part of a shared hard disk drive cluster (two or more servers sharing
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 server might be part of a cluster if any of the following conditions is true:
You have identified the failing server as part of a cluster (two or more servers
sharing external storage devices).
One or more external storage units are attached to the failing server and at
least one of the attached storage units is also attached to another server or
unidentifiable device.
One or more servers are located near the failing server.
Important: If the server 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 server is halted and a POST error code is displayed, see Appendix B,
UEFI (POST) error codes, on page 525. If the server is halted and no error
message is displayed, see Troubleshooting by symptom on page 137 and
Solving undetermined problems on page 156.
116
v For information about power-supply problems, see Solving power problems

on page 155 and Power-supply LEDs on page 129.
v For intermittent problems, check the event log; see Event logs on page 130 and
Appendix C, DSA diagnostic test results, on page 549.
Performing the checkout procedure

Use this information to perform the checkout procedure.
To perform the checkout procedure, complete the following steps:
1. Is the server part of a cluster?
v No: Go to step 2.
v Yes: Shut down all failing servers that are related to the cluster. Go to step 2.
2. Complete the following steps:
a. Check the power supply LEDs (see Power-supply LEDs on page 129).
b. Turn off the server and all external devices.
c. Check all internal and external devices for compatibility at
d. Check all cables and power cords.
e. Set all display controls to the middle positions.
f. Turn on all external devices.
g. Turn on the server. If the server does not start, see Troubleshooting by
symptom on page 137.
h. Check the system-error LED on the operator information panel. If it is
flashing, check the light path diagnostics LEDs (see Light path diagnostics
on page 120).
Note: When you slide the light path diagnostics panel out of the server to
check the LEDs or checkpoint codes, do not run the server continuously
with light path diagnostics panel outside of the server. The panel should
only be outside of the server a short time. The light path diagnostics panel
must remain in the server when the server is running to ensure proper
cooling.
i. Check for the following results:
v Successful completion of POST (see POST on page 133 for more
information)
v Successful completion of startup, which is indicated by a readable display
of the operating-system desktop
3. Is there a readable image on the monitor screen?
v No: Find the failure symptom in Troubleshooting by symptom on page
137; if necessary, see Solving undetermined problems on page 156.
v Yes: Run DSA (see Running the DSA Preboot diagnostic programs on page
135).
If DSA reports an error, follow the instructions in Appendix C, DSA
diagnostic test results, on page 549.
If DSA does not report an error but you still suspect a problem, see
Solving undetermined problems on page 156.
117
Diagnostic tools
The following tools are available to help you diagnose and solve hardware-related
problems.
Use light path diagnostics to diagnose system errors quickly. See Light path
diagnostics on page 120 for more information.
v Event logs
The event logs list the error codes and messages that are generated when an
error is detected for the subsystems IMM2, POST, DSA, and the server
baseboard management controller. See Event logs on page 130 for more
information.
v Integrated Management Module (IMM)
The Integrated Management Module (IMM) combines service processor
functions, video controller, and remote presence and blue-screen capture features
in a single chip. The IMM provides advanced service-processor control,
monitoring, and alerting function. If an environmental condition exceeds a
threshold or if a system component fails, the IMM lights LEDs to help you
diagnose the problem, records the error in the IMM event log, and alerts you to
the problem. Optionally, the IMM also provides a virtual presence capability for
remote server management capabilities. The IMM provides remote server
management through the following industry-standard interfaces:
Intelligent Platform Management Protocol (IPMI) version 2.0
Simple Network Management Protocol (SNMP) version 3
Common Information Model (CIM)
Web browser
For more information about the Integrated Management Module (IMM), see
Using the integrated management module II on page 95, Appendix A,
Integrated Management Module II (IMM2) error messages, on page 291, and
the Integrated Management Module User's Guide at www.ibm.com/support/entry/
portal/docdisplay?lndocid=MIGR-5089484&brandind=5000008.
v IBM Dynamic System Analysis
Two editions of IBM Dynamic System Analysis (DSA) are available for
diagnosing problems, DSA Portable and DSA Preboot:
DSA Portable
DSA Portable collect and analyze system information to aid in diagnosing
server problems. DSA Portable runs on the server's operating system and
collect the following information about the server:
- Drive health information
-
Event logs for ServeRAID controllers and service processors

Installed hardware, including PCI and USB information
Installed applications and hot fixes
Kernel modules
- RAID controller configuration

- Service processor (integrated management module) status and
configuration
118
- System configuration
- Vital product data, firmware, and UEFI configuration
DSA Portable create a DSA log, which is a chronologically ordered merge of
the system-event log (as the IPMI event log), the integrated management
module (IMM) chassis-event log (as the ASM event log), and the
operating-system event logs. You can send the DSA log as a file to IBM
service (when requested by service) or view the information as a text file or
HTML file.
Note: Use the latest available version of DSA to make sure you are using the
most recent configuration data. For documentation and download information
for DSA, see http://www.ibm.com/systems/management.
For additional information, see IBM Dynamic System Analysis on page 134
and Appendix C, DSA diagnostic test results, on page 549.
DSA Preboot
DSA Preboot diagnostic program is stored in the integrated USB memory on
the server. DSA Preboot collects and analyzes system information to aid in
diagnosing server problems, as well as offering a rich set of diagnostic tests of
the major components of the server. DSA Preboot collects the following
information about the server:
- Drive health information
- Event logs for ServeRAID controllers and service processors
- Installed hardware, including PCI and USB information
-

RAID controller configuration
- Service processor (integrated management module) status and

configuration
- System configuration
- Vital product data, firmware, and UEFI configuration
DSA Preboot also provides diagnostics for the following system components
(when they are installed):
1. Network adapter
2. IMM 12C bus
3. Lightpath diagnostics panel
4. Memory modules
5. Microprocessors
6. Optical devices (CD or DVD)
7. SAS or SATA drives
8. Tape drives (SCSI)
See Running the DSA Preboot diagnostic programs on page 135 for more
information on running the DSA Preboot program on the server.
v Troubleshooting by symptom
These tables list problem symptoms and actions to correct the problems. See
Troubleshooting by symptom on page 137 for more information.
119
Light path diagnostics

Light path diagnostics is a system of LEDs on various external and internal
components of the server that leads you to the failed component. When an error
occurs, LEDs are lit along the path of the front panel, the light path diagnostics
panel, then on the failed component. By viewing the LEDs in a particular order,
you can often identify the source of the error.
When LEDs are lit to indicate an error, they remain lit when the server is turned
off, provided that the server is still connected to power and the power supply is
operating correctly and the top cover is closed and latched correctly.
Before you work inside the server to view light path diagnostics LEDs, read the
safety information that begins on page Safety and Handling static-sensitive
devices on page 36.
If an error occurs, view the light path diagnostics LEDs in the following order:
1. Look at the operator information panel on the front of the server.
v If the Log LED is lit, it indicates that information about a suboptimal
condition in the server is available in the IMM system-event log or in the
system-event log.
v If the system-error LED is lit, it indicates that an error has occurred; go to
step 2.
The following illustration shows the operator information panel:
Figure 67. Operator information panel
120
2. To view the advanced operator information panel, press the blue latch on the
right of the operator panel. Lit LEDs on this panel indicate the type of error
that has occurred.
Look at the system service label inside the server cover, which gives an
overview of internal components that correspond to the LEDs on the light path
diagnostics panel. This information and the information in Light path
diagnostics LEDs on page 123 can often provide enough information to
diagnose the error.
3. Remove the server cover and look inside the server for lit LEDs. Certain
components inside the server have LEDs that are lit to indicate the location of a
problem.
The following illustration shows the LEDs on the system board.
System error LED
Light path LED
Locator LED
Battery error LED

System board
error LED
PCI riser 2
missing LED
Microprocessor
mismatch LED
DIMM error
LEDs 7-12
Microprocessor 2
error LED
DIMM error
LEDs 1-6
Microprocessor 1
error LED
PCI riser 1
missing LED
Fan 1B
error LED
Fan 1A
error LED
Fan 2B
error LED
Fan 2A
error LED
Fan 3B
error LED
Fan 3A
error LED
Figure 68. LEDs on the system board
121

The following illustration shows the optional advanced light path diagnostics
panel.
The light path diagnostics panel is available on the top of the advanced operator
information panel. For additional information about the light path diagnostics and
LEDs on the light path diagnostics panel, see Light path diagnostics on page 120
and Light path diagnostics LEDs on page 123.
Power-control button/
power-on LED
System locator
LED
Ethernet activities
LEDs
System-error
LED
Check log
LED
panel
Light path
diagnostics LEDs
Release button
Figure 69. Light path diagnostics panel
To access the optional advanced light path diagnostics panel, push the blue release
button on the advanced operator information panel. Pull forward on the unit until
the hinge of the operator panel is free of the server chassis. Then pull down on the
unit, so that you can view the light path diagnostics panel information.
Note: When you slide the optional advanced light path diagnostics panel out of
the server to check the LEDs, do not run the server continuously with light path
diagnostics panel outside of the server. The panel should only be outside of the
server a short time. The optional advanced light path diagnostics panel must
remain in the server when the server is running to ensure proper cooling.
The following illustration shows the LEDs and controls on the light path
diagnostics panel.
122
Figure 70. LEDs and controls on the light path diagnostics panel
v Remind button: This button places the system-error/Check Log LED on the
front panel into Remind mode. In Remind mode, the system-error LED flashes
once every 2 seconds until the problem is corrected, the server is restarted, or a
new problem occurs.
By placing the system-error LED indicator in Remind mode, you acknowledge
that you are aware of the last failure but will not take immediate action to
correct the problem.
press the button.
Light path diagnostics LEDs

The following table describes the LEDs on the light path diagnostics panel and
suggested actions to correct the detected problems.
For additional information, see Server controls, LEDs, and power on page 15 and
the System-board LEDs on page 30 for the location of the system board LEDs.
Note: Check the IMM system-event log or system event log for additional
information before replacing a FRU.
Table 12. Light path diagnostics panel LEDs
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v If a action step is preceded by "(Trained technician only)," that step must be performed only by a trained
technician.
LED
Description
Action
None, but the

Check Log LED
is lit.
An error has occurred and cannot 1. Check the IMM2 system even log and the system-error
be isolated. The error is not
log for information about the error.
represented by a path.
2. Save the log if necessary and clear the log afterwards.
123
Table 12. Light path diagnostics panel LEDs (continued)

solved.
technician.
LED
Description
Action
System Error
LED
An error occurred.
1. Check the light path LEDs and follow the listed

instruction.
2. Check the IMM2 system even log and the system-error
log for information about the error.
3. Save the log if necessary and clear the log afterwards.
OVER SPEC
The power supplies are using

more power than their maximum
rating. The system is drawing
power incoherent to power
supply specified ratings.
If the OVER SPEC LED is lit, use one of the following

procedures:
1. Turn off the server, disconnect the power from the server.
2. Remove the optical drive, fans, hard disk drives, and hard
disk drive backplanes.
3. Restart the server to see whether the problem remains.
4. Reinstall each device that was removed in step 2 one at a
time, starting the server each time, to isolate the failing
device.
5. Replace any failing device.
6. (Trained technician only) Replace the system board.
LINK
Reserved.
PS
A power supply is not detected

or has failed.
1. Check the power-supply in the server that has an lit

yellow LED (see Power-supply LEDs on page 129).
2. Make sure that the power supplies are seated correctly.
3. Remove one of the power supplies to isolate the failed
power supply.
4. Replace the failed power supply.
PCI
An error has occurred on a PCI

card, a PCI bus or on the system
board. An additional LED is lit
on one of the riser cards.
1. Check the system-event log for information about the

error.
2. Check the LEDs on the PCI riser cards to identify the
component that caused the error.
3. If you cannot isolate the failing adapter by using the
LEDs and the information in the system-event log,
remove one adapter at a time from the failing PCI bus;
and restart the server after each adapter is removed.
4. Replace the following components, in the order shown,
restarting the server each time:
v PCI riser card
v (Trained technician only) Replace the system board.
FAN
A fan has failed, is operating too 1. Check the LEDs on the server.
slowly, or has been removed. The
2. Reseat the failing fan, which is indicated by a lit LED on
TEMP LED might also be lit.
the fan.
3. Replace the failing fan.
124

solved.
technician.
LED
Description
Action
TEMP
The system temperature has

exceeded a threshold level. A
failing fan can cause the TEMP
LED to be lit.
1. Make sure that the air vents are not blocked.

2. Determine whether a fan has failed. If it has, replace it.
3. Make sure that the heat sink is seated correctly.
4. Make sure that the room temperature is not too high. See
Server features and specifications on page 6 and
System reliability guidelines on page 35 for the server
temperature information.
MEM
An invalid memory configuration

(both the MEM LED and
CONFIG LED might be lit) or a
memory error has occurred .
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 the MEM LED and the CONFIG LED are lit, the system
issues an invalid memory configuration error. Complete
the following steps to correct the problem:
a. Check the system-event log in the Setup utility or
IMM error messages. Follow steps indicated in
Appendix B, UEFI (POST) error codes, on page 525
and Appendix A, Integrated Management Module II
(IMM2) error messages, on page 291.
2. If the CONFIG LED is not lit, the system has detected a
memory error. Complete the following steps to correct the
problem:
a. Update the firmware to the latest level (see Updating
the firmware on page 83).
b. Reseat or swap the DIMMs.
c. Check the system-event log in the Setup utility or
IMM error messages. Follow steps indicated in
Appendix B, UEFI (POST) error codes, on page 525
and Appendix A, Integrated Management Module II
(IMM2) error messages, on page 291.
NMI
A nonmaskable interrupt has

occurred, or the NMI button was
pressed.
Check the system-event log for information about the error.
125

solved.
technician.
LED
Description
Action
CONFIG
A hardware configuration error

has occurred.
1. If the CONFIG LED and the CPU LED are lit, complete
the following steps to correct the problem:
a. Check the microprocessors that were just installed to
make sure that they are compatible with each other
(see Replacing a microprocessor and heat sink on
page 275 for additional information about
microprocessor requirements).
b. (Trained technician only) Replace the incompatible
microprocessor.
c. Check the system-event logs for information about the
error. Replace any components that are identified in
the error log.
2. If the CONFIG LED and the MEM LED are both lit,
a. Make sure that the DIMM configuration is supported
(see Installing a memory module on page 38 for
DIMM requirements and installation sequence
information).
b. Replace the DIMMs with a supported configuration.
126

solved.
technician.
LED
Description
Action
CPU
An invalid microprocessor
1. If the CONFIG LED is lit, the system issues an invalid
configuration or a microprocessor
microprocessor configuration error. Complete the
has failed (both the CPU LED
following steps to correct the problem:
and the CONFIG LED might be
a. Check the microprocessors that were just installed to
lit).
make sure that they are compatible with each other
(see Replacing a microprocessor and heat sink on
page 275 for additional information about
microprocessor requirements) and use the Setup utility
and select System Information System Summary
Processor to verify the microprocessors information.
b. (Trained technician only) Replace the incompatible
microprocessor.
c. Check the system-event logs for information about the
error. Replace any components that are identified in
the error log.
2. If the CPU LED is lit and the CONFIG LED is not lit,
a. (Trained technician only) Make sure that the failing
microprocessor, which is indicated by a lit LED on the
system board, is installed correctly. See Replacing a
microprocessor and heat sink on page 275 for
information about installation and requirements.
When only the CPU LED is lit, a
microprocessor has failed.
If the CONFIG LED is not lit, a microprocessor failure occurs,

complete the following steps to correct the problem:
1. (Trained technician only) Make sure that the failing
microprocessor and its heat sink, which are indicated by a
lit LED on the system board, are installed correctly. See
Replacing a microprocessor and heat sink on page 275
for information about installation and requirements.
2. (Trained technician only) Replace the failing
microprocessor (see Removing a microprocessor and heat
sink on page 273 and Replacing a microprocessor and
heat sink on page 275).
3. For more information, go to .
127

solved.
technician.
LED
Description
Action
HDD
A hard disk drive has failed or is

missing.
1. Check the LEDs on the hard disk drives for the drive
with a lit status LED and reseat the hard disk drive.
2. Make sure that the cables are correctly connected to the
hard disk drive backplane.
3. For more information, see Hard disk drive problems on
page 140.
4. If the error remains, replace the following components in
the order listed, restarting the server after each:
a. Replace the hard disk drive.
b. Replace the hard disk drive backplane.
5. If the error remains, replace the following components
one at a time, in the order listed, restarting the server
after each:
a. Replace the hard disk drive.
b. Replace the hard disk drive backplane.
6. If the problem remains, go to .
BOARD
An error has occurred on the

system board.
1. Check the LEDs on the server.

2. Check the LEDs on the system board to identify the
component that caused the error. The BOARD LED can be
lit due to any of the following reasons:
v Battery
v Missing PCI riser-card assembly
v Failed firmware update
v Failed system board
3. Check the system-event log for information about the
error.
4. Replace any failed or missing replacement components,
such as the battery or PCI riser-card assembly.
5. (Trained technician only) replace the server system board.
128
Power-supply LEDs
This section describes the power-supply LEDs on the rear of the server and the
suggested actions to correct the detected problems.
The following minimum configuration is required for the DC LED on the power
supply to be lit:
v Power supply
v Power cord
The following minimum configuration is required for the server to start:
v One microprocessor in microprocessor socket 1
v One 2 GB DIMM (per microprocessor) on the system board
v One power supply
v Power cord
v Four cooling fans
The following illustrations show the locations of the power-supply LEDs for fixed
and redundant models respectively.
AC LED (green)
Figure 71. Power-supply LEDs locations

DC LED (green)
Power - supply
error LED (yellow)
AC LED (green)
DC LED (green)
Power - supply
error LED (yellow)
Ethernet link
LED
Ethernet
activity LED
The following table describes the problems that are indicated by various
combinations of the power-supply LEDs and the power-on LED on the operator
information panel and suggested actions to correct the detected problems.
Power-supply LEDs
AC
DC
Error
Description
Action
Notes
On
On
Off
Normal operation
Off
Off
Off
No ac power to the 1. Check the ac power to the

server or a problem
server.
with the ac power
2. Make sure that the power
source.
cord is connected to a
functioning power source.
This is a normal
condition when no ac
power is present.
3. Restart the server. If the error

remains, check the
power-supply LEDs.
4. Replace the power-supply.
129
Power-supply LEDs
AC
DC
Error
Description
Action
Off
Off
On
No ac power to the v Make sure that the power

server or a problem
cord is connected to a
with the ac power
functioning power source.
source and the
v Replace the power supply.
power-supply had
detected an
internal problem.
Off
On
Off
Faulty
power-supply
Replace the power supply.
Off
On
On
Faulty
power-supply
On
Off
Off
Power-supply not
fully seated, faulty
system board, or
faulty
power-supply
1. Make sure that the top cover

is closed and latched
correctly.
Notes
This happens only
when a second power
supply is providing
power to the server.
Typically indicates a
power-supply is not
fully seated.
2. Reseat the power supply.

3. Replace the failing power
supply.
On
Off
On
Faulty power
-supply
On
On
On
Power-supply is
faulty
Event logs
Error codes and messages are displayed in POST event log, system-event log,
integrated management module (IMM2) event log, and DSA event log.
v POST event log: This log contains the three most recent error codes and
messages that were generated during POST. You can view the contents of the
POST event log from the Setup utility (see Starting the Setup utility on page
88). For more information about POST error codes, see Appendix B, UEFI
(POST) error codes, on page 525.
v System-event log: This log contains POST and system management interrupt
(SMI) events and all events that are generated by the baseboard management
controller that is embedded in the integrated management module (IMM). You
can view the contents of the system-event log through the Setup utility and
through the Dynamic System Analysis (DSA) program (as 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 clear the
system-event log through the Setup utility. When you are troubleshooting an
error, you might have to save and then clear the system-event log to make the
most recent events available for analysis. For more information about the
system-event log, see Appendix A, Integrated Management Module II (IMM2)
error messages, on page 291.
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.
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.
130
v Integrated management module (IMM2) 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. For more
information, see Logging on to the Web interface on page 99. You can also
view the IMM event log through the Dynamic System Analysis (DSA) program
(as the ASM event log). For more information about IMM error messages, see
Appendix A, Integrated Management Module II (IMM2) error messages, on
page 291.
v DSA event 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 event log through the DSA
program (see Viewing event logs without restarting the server). For more
information about DSA and DSA messages, see Appendix C, DSA diagnostic
test results, on page 549 and IBM Dynamic System Analysis on page 134.
For more information about viewing the logs or clearing the logs, see Viewing
event logs through the Setup utility, Viewing event logs without restarting the
server, and Clearing the error logs on page 133.
Viewing event logs through the Setup utility

Use this information to view the event logs through the Setup utility.
To view the POST event log or system-event log, complete the following steps:
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

Use this information to view the event logs without restarting the server.
If the server is not hung and the IMM is connected to a network, methods are
available for you to view one or more event logs without having to restart the
server.
If you have installed Dynamic System Analysis (DSA) Portable, you can use it to
view the system-event log (as the IPMI event log), or 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. The server comes with DSA Preboot stored in integrated USB
memory. To install DSA Portable or check for and download a later version of DSA
Preboot CD image, go to http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=SERV-DSA.
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 an overview of IPMI, go to http://www.ibm.com/developerworks/
linux/blueprints/ and click Using Intelligent Platform Management Interface
(IPMI) on IBM Linux platforms.
131
You can view the IMM event log through the Event Log link in the integrated
management module (IMM) Web interface. For more information, see Logging on
to the Web interface on page 99.
The following table describes the methods that you can use to view the event logs,
depending on the condition of the server. The first three conditions generally do
not require that you restart the server.
Table 13. Methods for viewing event logs
Condition
Action
The server is not hung and is connected to a

Use any of the following methods:
network (using an operating system
controlled network ports).
v Run DSA Portable to view the diagnostic
event log (requires IPMI driver) or create
an output file that you can send to IBM
service and support (using ftp or local
copy).
v Use IPMItool to view the system-event log
(requires IPMI driver).
v Use the Web browser interface to the IMM
to view the system-event log locally
(requires RNDIS USB LAN driver).
The server is not hung and is not connected
to a network (using an operating system
controlled network ports).
Use any of the following methods:

v Run Portable DSA to view the diagnostic
event log (requires IPMI driver) or create
an output file that you can send to IBM
service and support (using a local copy).
v Use IPMItool to view the system-event log
(requires IPMI driver).
to view the system-event log locally
(requires RNDIS USB LAN driver). For
more information, see Obtaining the IP
address for the IMM on page 99 and
Logging on to the Web interface on
page 99.
The integrated management module (IMM)

is connected to a network and AC power is Use any of the following methods:
applied - the server state might be hung, not v Use IPMItool over the network to the
hung, or powered off.
IMM external IP address to view the
system-event log.
to view the system-event log. In the Web
browser, type the IP address for the IMM
and go to the Event Log page. For more
information, see Obtaining the IP address
for the IMM on page 99 and Logging
on to the Web interface on page 99.
132
Table 13. Methods for viewing event logs (continued)

Condition
The server is hung and no communication
can be made with the IMM.
Action
Restart the server and press F2 to start DSA
Preboot and view the diagnostic event log
(see Running the DSA Preboot diagnostic
programs on page 135 for more
information).
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 131.
Clearing the error logs

Use this information to clear the event logs.
To clear the event logs, complete the following steps.
Note: The POST event log is automatically cleared each time the server is
restarted.
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. Use one of the following procedures:
v To clear the IMM system-event log, select System Event Logs --> System
Event Log. Select Clear System Event Log; then, press Enter twice.
POST
When you turn on the server, it performs a series of tests to check the operation of
the server components and some optional devices in the server. This series of tests
is called the power-on self-test, or POST.
Note: This server does not use beep codes for server status.
If a power-on password is set, you must type the password and press Enter (when
you are prompted), for POST to run.
If POST detects a problem an error message is displayed. See Appendix B, UEFI
(POST) error codes, on page 525 for more information.
If POST detects a problem, an error message is sent to the POST event log, see
Event logs on page 130 for more information.
133
IBM Dynamic System Analysis

IBM Dynamic System Analysis (DSA) collects and analyzes system information to
aid in diagnosing server problems.
DSA collects the following information about the server:
v Drive health information
v Event logs for ServeRAID controllers and service processors
v
v
v
v
v
v
v
Hardware inventory, including PCI and USB information

Installed applications and hot fixes (available in DSA Portable only)
Kernel modules (available in DSA Portable only)
Performance data and details about processes that are running
RAID and controller configuration
v Service processor (integrated management module) status and configuration

v System configuration
v Vital product data and firmware information
For system-specific information about the action that you should take as a result of
a message that DSA generates, see Diagnostic text messages on page 136.
If you cannot find a problem by using DSA, see Solving undetermined problems
on page 156 for information about testing the server.
Note:
1. In a multi-node environment, each server has a unique DSA interface. You can
view server-specific information, such as event logs, from these unique DSA
interfaces.
2. DSA Preboot might appear to be unresponsive when you start the program.
This is normal operation while the program loads.
Make sure that the server has the latest version of the DSA code. To obtain DSA
code and the Dynamic System Analysis Installation and User's Guide, go to
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-DSA.
DSA editions
Two editions of Dynamic System Analysis are available.
v DSA Portable
DSA Portable Edition runs within the operating system; you do not have to
restart the server to run it. It is packaged as a self-extracting file that you
download from the Web. When you run the file, it self-extracts to a temporary
folder and performs comprehensive collection of hardware and operating-system
information. After it runs, it automatically deletes the temporary files and folder
and leaves the results of the data collection and diagnostics on the server.
If you are able to start the server, use DSA Portable.
v DSA Preboot
DSA Preboot runs outside of the operating system; you must restart the server to
run it. It is provided in the flash memory on the server, or you can create a
bootable media such as a CD, DVD, ISO, USB, or PXE using the IBM
ToolsCenter Bootable Media Creator (BoMC). For more details, see the BoMC
User Guide at http://www.ibm.com/support/entry/portal/
134
docdisplay?lndocid=TOOL-BOMC. In addition to the capabilities of the other

editions of DSA, DSA Preboot includes diagnostic routines that would be
disruptive to run within the operating-system environment (such as resetting
devices and causing loss of network connectivity). It has a graphical user
interface that you can use to specify which diagnostics to run and to view the
diagnostic and data collection results.
DSA Preboot provides diagnostics for the following system components, if they
are installed:
Broadcom network adapter
Optical devices (CD or DVD)

Tape drives (SCSI, SAS, or SATA)
Memory
Microprocessor
Checkpoint panel
I2C bus
SAS and SATA drives
If you are unable to restart the server or if you need comprehensive diagnostics,
use DSA Preboot.
The IBM System x3530 M4 server comes with DSA Preboot diagnostics code on
the integrated USB flash memory. Utilities are available to reset and update the
diagnostics code on the integrated USB flash device, if the diagnostic partition
becomes damaged and does not start the DSA Preboot diagnostic programs. For
more information and to download the utilities, go to http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=SERV-DSA.
Running the DSA Preboot diagnostic programs

Use this information to run the DSA Preboot diagnostic programs.
Note: The DSA memory test might take up to 30 minutes to run. If the problem is
not a memory problem, skip the memory test.
To run the DSA Preboot diagnostic programs that is stored in integrated flash
memory on the server, complete the following steps:
1. If the server is running, turn off the server and all attached devices.
2. Turn on all attached devices; then, turn on the server.
3. When the prompt <F2> Diagnostics 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 Quit 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.
If the server stops during testing and you cannot continue, restart the server and
try running the DSA Preboot diagnostic programs again. If the problem remains,
135
replace the component that was being tested when the server 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
Additional information concerning test failures is available in the extended
diagnostic results for each test.
Viewing the test log results

Use this information to view the test log results and transferring the DSA
collection.
To view the test log for the results when the tests are completed, click the Success
link in the Status column, if you are running the DSA graphical user interface, or
type :x to exit the Execute Tests menu, if you are running the DSA interactive
menu, or select Diagnostic Event Log in the graphical user interface. To transfer
DSA Preboot collections to an external USB device, type the copy command in the
DSA interactive menu.
v If you are running the DSA graphical user interface (GUI), click the Success link
in the Status column.
v If you are running the DSA interactive menu (CLI), type :x to exit the Execute
Tests menu; then, select the completed tests to view the results.
Call home (automated service request)

IBM provides tools that can automatically collect and send data or call IBM
Support when an error is detected.
These tools can help IBM service speed up the process of diagnosing problems.
The following sections provide information about the call home tools.
Service advisor
The server comes with the Service Advisor feature that can collect data about the
system when the system detects a fault and sends that data to IBM Service for
problem determination. It also includes the call home feature that automatically
calls IBM Service when a problem occurs. The Service Advisor feature is integrated
into the Integrated Management Module (IMM). You will need to setup and
configure the Service Advisor feature before you can use it. For more information
about how to setup and configure the Service Advisor feature, see the Integrated
Management Module User's Guide at www.ibm.com/support/entry/portal/
136
IBM Electronic Service Agent

IBM Electronic Service Agent monitors, tracks, and captures system hardware
errors and hardware and software inventory information, and reports serviceable
problems directly to IBM Support. You can also choose to collect data manually. It
uses minimal system resources, and can be downloaded from the IBM website.
For more information and to download IBM Electronic Service Agent, go to
http://www-01.ibm.com/support/esa/.
Error messages
This section provides the list of error codes and messages for UEFI/POST, IMM2,
and DSA that are generated when a problem is detected.
See Appendix B, UEFI (POST) error codes, on page 525, Appendix A, Integrated
Management Module II (IMM2) error messages, on page 291, and Appendix C,
DSA diagnostic test results, on page 549 for more information.
Troubleshooting by symptom
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
If you cannot find a solution to the problem in these tables, see Appendix C, DSA
diagnostic test results, on page 549 for information about testing the server and
Running the DSA Preboot diagnostic programs on page 135 for additional
information about running DSA Preboot program that is stored in integrated USB
memory on the server. For additional information to help you solve problems, see
Start here on page 113.
If you have just added new software or a new optional device and the server is
not working, complete the following steps before you use the troubleshooting
tables:
1. Check the system-error LED on the operator information panel; if it is lit, check
the light path diagnostics LEDs (see Light path diagnostics on page 120).
2. Remove the software or device that you just added.
3. Run IBM Dynamic System Analysis (DSA) to determine whether the server is
running correctly (for information about using DSA, see Appendix C, DSA
diagnostic test results, on page 549.
4. Reinstall the new software or new device.
137
CD/DVD drive problems

solved.
v See Chapter 5, Parts listing, IBM System x3530 M4 Type 7160, on page 161 to check if a component is a
consumable, structural, or FRU part.
v If an action step is preceded by (Trained technician only), that step must be performed only by a trained
technician.
Symptom
Action
The CD-ROM/DVD-ROM drive 1. Make sure that:

is not recognized.
v The SATA connector to which the CD or DVD drive is attached (primary or
secondary) is enabled in the Setup utility.
v All cables and jumpers are installed correctly.
v The correct device driver is installed for the CD or DVD drive.
2. Run the CD or DVD drive diagnostic programs.
3. Reseat the following components:
a. CD or DVD drive
b. CD or DVD drive cable
4. Replace the components listed in step 3 one at a time, in the order shown,
restarting the server each time.
5. (Trained service technician only) Replace the system board.
A CD or DVD is not working
correctly.
1. Clean the CD or DVD.

2. Replace the CD or DVD with new CD or DVD media.
3. Run the CD or DVD drive diagnostic programs (see Appendix C, DSA
diagnostic test results, on page 549).
4. Reseat the CD or DVD drive (see Removing a CD/DVD drive on page 215
and Installing an optional CD/DVD drive on page 216).
5. Replace the CD or DVD drive.
The CD or DVD drive tray is

not working.
1. Make sure that the server is turned on.

2. Insert the end of a straightened paper clip into the manual tray-release
opening.
3. Reseat the CD or DVD drive (see Removing a CD/DVD drive on page 215
and Installing an optional CD/DVD drive on page 216).
4. Replace the CD or DVD drive.
138
Hypervisor problems
solved.
technician.
Symptom
Action
If an optional embedded
hypervisor flash device is not
listed in the expected boot
order, does not appear in the
list of boot devices, or a similar
problem has occurred.
1. Make sure that the optional embedded hypervisor flash device is selected on
the boot manager (<F12> Select Boot Device) at startup.
2. Make sure that the embedded hypervisor flash device is seated in the
connector correctly (see Removing a USB embedded hypervisor flash device
on page 229 and Replacing a USB embedded hypervisor flash device on
page 231).
3. See the documentation that comes with the optional embedded hypervisor
flash device for setup and configuration information.
4. Make sure that other software works on the server.
General problems
solved.
v See Chapter 5, Parts listing, IBM System x3530 M4 Type 7160, on page 161 to check whether a component is
a consumable, structural, or FRU part.
technician.
Symptom
Action
A cover latch is broken, an LED If the part is a CRU, replace it. If the part is a FRU, the part must be replaced by a
is not working, or a similar
trained service technician (see Chapter 6, Removing and replacing components,
problem has occurred.
on page 173 to determine whether the part is a consumable, structural, or FRU
component).
The server cover was removed
while running and the server
shut off.
Replace the server cover and restart the server.
The server is hung while the

screen is on. Cannot start the
Setup utility by pressing F1.
1. See Nx boot failure on page 160 for more information.

2. See Recovering the server firmware (UEFI update failure) on page 158 for
more information.
139
Hard disk drive problems

solved.
technician.
Symptom
Action
Not all drives are recognized by Remove the drive that is indicated by DSA (see Removing hot-swap drives on
the DSA hard disk drive
page 210 or Removing a simple-swap SATA drive on page 213); then, run the
diagnostic test.
hard disk drive diagnostic test again (see Appendix C, DSA diagnostic test
results, on page 549). If the remaining drives are recognized, replace the drive
that you removed with a new one.
The server stops responding
during the hard disk drive
diagnostic test.
Remove the drive that is indicated by DSA (see Removing hot-swap drives on
page 210 or Removing a simple-swap SATA drive on page 213); then, run the
hard disk drive diagnostic test again (see Appendix C, DSA diagnostic test
results, on page 549). If the remaining drives are recognized, replace the drive
that you removed with a new one.
A hard disk drive has failed,

and the associated yellow hard
disk drive status LED is lit.
Replace the failed hard disk drive.
140
solved.
technician.
Symptom
Action
A newly installed hard disk

drive is not recognized.
1. Observe the associated yellow 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 yellow
status LED:
v If the green activity LED is flashing and the yellow 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 yellow 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 Hard disk drive problems on page 140).
v If the green activity LED is flashing and the yellow status LED is lit, replace
the drive. If the activity of the LEDs remains the same, go to step Hard
disk drive problems on page 140. 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:
a. Replace the affected backplane signal cable.
b. Replace the affected backplane.
8. Run the DSA tests for the SAS/SATA adapter and hard disk drives (see
Running the DSA Preboot diagnostic programs on page 135).
v If the adapter 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 adapter fails the test, disconnect the backplane signal cable from the
adapter and run the tests again.
v If the adapter fails the test, replace the adapter.
9. See Problem determination tips on page 157.
Multiple hard disk drives fail.
Make sure that the hard disk drive, SAS/SATA RAID adapter, and server device
drivers and firmware are at the latest level.
Important: Some cluster solutions require specific code levels or coordinated code
Multiple hard disk drives are

offline.
1. Review the storage subsystem logs for indications of problems within the
storage subsystem, such as backplane or cable problems.
141
solved.
technician.
Symptom
Action
A replacement hard disk drive

does not rebuild.
1. Make sure that the hard disk drive is recognized by the adapter (the green
hard disk drive activity LED is flashing).
2. Review the SAS/SATA RAID adapter documentation to determine the correct
configuration parameters and settings.
A green hard disk drive activity 1. If the green hard disk drive activity LED does not flash when the drive is in
LED does not accurately
use, run the DSA disk drive test (see Running the DSA Preboot diagnostic
represent the actual state of the
programs on page 135.
associated drive.
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.
A yellow hard disk drive status 1. If the yellow hard disk drive LED and the RAID adapter software do not
LED does not accurately
indicate the same status for the drive, complete the following steps:
represent the actual state of the
a. Turn off the server.
associated drive.
b. Reseat the SAS/SATA adapter.
c. Reseat the backplane signal cable and backplane power cable.
d. Reseat the hard disk drive.
e. Turn on the server and observe the activity of the hard disk drive LEDs.
Intermittent problems
solved.
technician.
Symptom
Action
A problem occurs only

occasionally and is difficult to
diagnose.
1. Make sure that:

v All cables and cords are connected securely to the rear of the server and
attached devices.
v When the server is turned on, air is flowing from the fan grille. If there is no
airflow, the fan is not working. This can cause the server to overheat and
shut down.
2. Check the event logs (see Event logs on page 130).
3. See Solving undetermined problems on page 156.
142
solved.
technician.
Symptom
Action
The server resets (restarts)

occasionally.
1. If the reset occurs during POST and the POST watchdog timer is enabled (click
System Settings --> Integrated Management Module --> POST Watchdog
Timer in the Setup utility to see the POST watchdog setting), make sure that
sufficient time is allowed in the watchdog timeout value (POST Watchdog
Timer). If the server continues to reset during POST, see Appendix B, UEFI
(POST) error codes, on page 525 and Appendix C, DSA diagnostic test
results, on page 549.
2. If the reset occurs after the operating system starts, disable any automatic
server restart (ASR) utilities, such as the IBM Automatic Server Restart IPMI
Application for Windows, or any ASR devices that are be installed.
Note: ASR utilities operate as operating-system utilities and are related to the
IPMI device driver. If the reset continues to occur after the operating system
starts, the operating system might have a problem; see Software problems on
page 154.
3. If neither condition applies, check the event logs (see Event logs on page
130).
Keyboard, mouse, or pointing-device problems

solved.
technician.
Symptom
Action
All or some keys on the

keyboard do not work.
1. Make sure that:

v The keyboard cable is securely connected.
v The server and the monitor are turned on.
2. If you are using a USB keyboard, run the Setup utility and enable keyboardless
operation.
3. See http://www.ibm.com/systems/info/x86servers/serverproven/compat/us
for information about keyboard compatibility.
4. If you are using a USB keyboard and it is connected to a USB hub, disconnect
the keyboard from the hub and connect it directly to the server.
5. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. Keyboard
b. (Trained service technician only) System board
143
solved.
technician.
Symptom
Action
The mouse or pointing device

does not work.
1. See http://www.ibm.com/systems/info/x86servers/serverproven/compat/us
for information about mouse compatibility.
2. Make sure that:
v The mouse or pointing-device cable is securely connected to the server.
v If you are using a pointing device, the keyboard and mouse or
pointing-device cables are not reversed.
v The mouse or pointing-device device drivers are installed correctly.
v The server and the monitor are turned on.
v The mouse option is enabled in the Setup utility.
3. If you are using a USB mouse or pointing device and it is connected to a USB
hub, disconnect the mouse or pointing device from the hub and connect it
directly to the server.
a. Mouse or pointing device
b. (Trained service technician only) System board
144
Memory problems
solved.
technician.
Symptom
Action
The amount of system memory Note: If you change memory, you must update the memory configuration in the
that is displayed is less than the Setup utility.
amount of installed physical
1. Make sure that:
memory.
v No error LEDs are lit on the operator information panel, on the memory
tray, or on the MAX5 memory expansion module.
v Memory mirroring does not account for the discrepancy.
v The memory modules are seated correctly (see Removing a memory
module on page 223 and Replacing a memory module on page 224).
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 server 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:
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 DSA Preboot diagnostic programs
on page 135).
4. Make sure that there is no memory mismatch when the server is at the
minimum memory configuration ( see Installing a memory module on page
38 for information about DIMM rules and population sequence).
5. Reseat the DIMM.
Multiple rows of DIMMs in a
branch are identified as failing.
1. Reseat the DIMMs; then, restart the server.

2. Remove the lowest-numbered DIMM pair of those that are identified and
replace it with an identical pair of known good DIMMs; then, restart the
server. Repeat as necessary. If the failures continue after all identified pairs are
replaced, go to step 4.
3. Return the removed DIMMs, one pair at a time, to their original connectors,
restarting the server after each pair, until a pair fails. Replace each DIMM in
the failed pair with an identical known good DIMM, restarting the server after
each DIMM. Replace the failed DIMM. Repeat step 3 until you have tested all
removed DIMMs.
4. Replace the lowest-numbered DIMM pair of those identified; then, restart the
server. Repeat as necessary.
145
Microprocessor problems
solved.
technician.
Symptom
Action
The server goes directly to the

POST Event Viewer when it is
turned on.
1. Correct any errors that are indicated by the light path diagnostics LEDs (see
Light path diagnostics LEDs on page 123).
2. Make sure that the server supports all the microprocessors and that the
microprocessors match in speed, type, and cache size. To view the
microprocessor information, run the Setup utility and select System
Information System Summary Processor.
3. (Trained technician only) Make sure that microprocessor 1 is seated correctly.
4. (Trained technician only) Remove microprocessor 2 and restart the server.
a. (Trained technician only) Microprocessor
b. (Trained technician only) System board
Monitor and video problems

Some IBM monitors have their own self-tests. If you suspect a problem with your
monitor, see the documentation that comes with the monitor for instructions for
testing and adjusting the monitor. If you cannot diagnose the problem, call for
service.
solved.
technician.
Symptom
Action
Testing the monitor.
1. Make sure that the monitor cables are firmly connected.

2. Try using a different monitor on the server, or try using the monitor that is
being tested on a different server.
3. Run the diagnostic programs. If the monitor passes the diagnostic programs,
the problem might be a video device driver.
146
solved.
technician.
Symptom
Action
The screen is blank.
1. If the server is attached to a KVM switch, bypass the KVM switch to eliminate
it as a possible cause of the problem: connect the monitor cable directly to the
correct connector on the rear of the server.
2. Make sure that:
v The server is turned on. If there is no power to the server, see Power
problems on page 151.
v The monitor cables are connected correctly.
v The monitor is turned on and the brightness and contrast controls are
adjusted correctly.
3. Make sure that the correct server is controlling the monitor, if applicable.
4. Make sure that damaged server firmware is not affecting the video; see
Updating the firmware on page 83.
5. Observe the checkpoint LEDs on the system board; if the codes are changing,
go to step 6.
a. Monitor
b. Video adapter (if one is installed)
c. (Trained technician only) System board.
The monitor works when you

turn on the server, but the
screen goes blank when you
start some application
programs.
1. Make sure that:

v The application program is not setting a display mode that is higher than
the capability of the monitor.
v You installed the necessary device drivers for the application.
2. Run video diagnostics (see Running the DSA Preboot diagnostic programs
on page 135).
v If the server passes the video diagnostics, the video is good; see Solving
undetermined problems on page 156.
v (Trained technician only) If the server fails the video diagnostics, replace the
system board.
147
solved.
technician.
Symptom
Action
The monitor has screen jitter, or 1. If the monitor self-tests show that the monitor is working correctly, consider
the screen image is wavy,
the location of the monitor. Magnetic fields around other devices (such as
unreadable, rolling, or
transformers, appliances, fluorescents, and other monitors) can cause screen
distorted.
jitter or wavy, unreadable, rolling, or distorted screen images. If this happens,
turn off the monitor.
Attention: Moving a color monitor while it is turned on might cause screen
discoloration.
Move the device and the monitor at least 305 mm (12 in.) apart, and turn on
the monitor.
Notes:
a. To prevent diskette drive read/write errors, make sure that the distance
between the monitor and any external diskette drive is at least 76 mm (3
in.).
b. Non-IBM monitor cables might cause unpredictable problems.
2. Reseat the monitor cable.
a. Monitor cable
c. Monitor
d. (Trained technician only) System board.
Wrong characters appear on the 1. If the wrong language is displayed, update the server firmware to the latest
screen.
level (see Updating the firmware on page 83) with the correct language.
2. Reseat the monitor cable.
a. Monitor cable
c. Monitor
d. (Trained technician only) System board.
148
Network connection problems

solved.
technician.
Symptom
Action
Unable to wake the server

using the Wake on LAN
feature.
1. If you are using the dual-port network adapter and the server is connected to
the network using Ethernet 5 connector, check the system-error log or IMM2
system event log (see Event logs on page 130), make sure:
a. The room temperature is not too high (see Server features and
specifications on page 6).
b. The air vents are not blocked.
c. The air baffle is installed securely.
2. Reseat the dual-port network adapter (see Removing an adapter on page 207
and Installing an adapter on page 51).
3. Turn off the server and disconnect it from the power source; then, wait 10
seconds before restarting the server.
4. If the problem still remains, replace the dual-port network adapter.
Wake on Lan feature is in

disable mode.

the power-control button becomes active after the power-on LED flashes
slowly.
3. Under System Configuration and Boot Management, select System Settings.
4. Under System Settings, select Network.
5. Under Network, select the port number.
6. Under the chosen port number, select Intel (R) I350 Gigabit Network
Connection.
7. Under Main Configuration Page, select NIC configuration.
8. Under NIC configuration, change the Wake on Lan function from Disabled
to Enabled.
9. Press ESC several times until the System Configuration and Boot
Management window is displayed.
10. Select Save Setting.
11. Turn off the server and disconnect it from the power source. You must
disconnect the system from ac power to enable the Wake on Lan function.
Log in failed by using LDAP

account with SSL enabled.
1. Make sure the license key is valid.

2. Generate a new license key and log in again.
149
Optional-device problems
solved.
technician.
Symptom
Action
An IBM optional device that

was just installed does not
work.
1. Make sure that:

v The device is designed for the server (see http://www.ibm.com/systems/
info/x86servers/serverproven/compat/us).
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. Reseat the device that you just installed.
3. Replace the device that you just installed.
An IBM optional device that

worked previously does not
work now.
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. If the failing device is a SCSI device, make sure that:
v The cables for all external SCSI devices are connected correctly.
v The last device in each SCSI chain, or the end of the SCSI cable, is
terminated correctly.
v Any external SCSI device is turned on. You must turn on an external SCSI
device before you turn on the server.
4. Reseat the failing device.
5. Replace the failing device.
150
Power problems
solved.
technician.
Symptom
The power-control button does
not work, and the reset button
does work (the server does not
start).
Note: The power-control button
will not function until
approximately 1 to 3 minutes
after the server has been
connected to ac power.
Action
1. Make sure that the top cover is closed and latched correctly.
2. Make sure that the top cover/power cut-off switch cable is seated correctly.
3. Make sure that the power-control button on the server is working correctly:
a. Disconnect the server power cords.
b. Reconnect the power cords.
c. Reseat the operator information panel cables, and then repeat steps 3a and
3b.
v If the server starts, reseat the operator information panel. If the problem
remains, replace the operator information panel.
4. Make sure that the reset button is working correctly:
a. Disconnect the server power cords.
b. Reconnect the power cords.
c. Reseat the operator information panel cable, and then repeat steps 3a and
3b.
v If the server starts, replace the operator information panel.
v If the server does not start, go to step 5.
5. Make sure that:
v The power cords are correctly connected to the server and to a working
electrical outlet.
v The type of memory that is installed is correct.
v The DIMMs are fully seated.
v The LEDs on the power supply do not indicate a problem.
v The microprocessors are installed in the correct sequence.
a. DIMMs
b. Power supplies
8. If you just installed an optional device, remove it, and restart the server. If the
server now starts, you might have installed more devices than the power
supply supports.
9. See Power-supply LEDs on page 129.
The server does not start.
1. Check the power LED on the system board. See System-board LEDs on page
30 for the LED location.
2. Reseat the power supply.
3. Replace the power supply.
The server does not start.

(Continued)
151
solved.
technician.
Symptom
Action
The server does not turn off.
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 server by pressing the power-control button and hold it down
for 5 seconds.
c. Restart the server.
d. If the server 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 server.
2. If the problem remains or if you are using an ACPI-aware operating system,
suspect the system board.
The server unexpectedly shuts

down, and the LEDs on the
operator information panel are
not lit.
See Solving undetermined problems on page 156.
Serial-device problems
solved.
technician.
Symptom
Action
The number of serial ports that

are identified by the operating
system is less than the number
of installed serial ports.
1. Make sure that:

v Each port is assigned a unique address in the Setup utility and none of the
serial ports is disabled.
v The serial-port adapter (if one is present) is seated correctly.
2. Reseat the serial port adapter.
3. Replace the serial port adapter.
A serial device does not work.
1. Make sure that:

v The device is compatible with the server.
v The serial port is enabled and is assigned a unique address.
v The device is connected to the correct connector (see Connecting the
cables on page 81).
a. Failing serial device
b. Serial cable
152
ServerGuide problems
solved.
technician.
Symptom
Action
The ServerGuide Setup and

Installation CD will not start.
1. Make sure that the server supports the ServerGuide program and has a
startable (bootable) CD or DVD drive. See the readme file that is part of the
ISO image at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=TOOL-CENTER.
2. Make sure that you burned the CD or DVD from an image (do not burn the
CD or DVD ISO file as a data disk)
3. Make sure that you burn the CD or DVD as disk at once (not track at once).
4. If the startup (boot) sequence settings have been changed, make sure that the
CD or DVD drive is first in the startup sequence.
5. If more than one CD or DVD drive is installed, make sure that only one drive
is set as the primary drive. Start the CD from the primary drive.
The MegaRAID Storage

Manager program cannot view
all installed drives, or the
operating system cannot be
installed.
1. Make sure that the hard disk drive is connected correctly.
The operating-system
installation program
continuously loops.
Make more space available on the hard disk.
The ServerGuide program will

not start the operating-system
CD.
Make sure that the operating-system CD is supported by the ServerGuide

program. For a list of supported operating-system versions, go to
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-GUIDE,
click IBM Service and Support Site, click the link for your ServerGuide version,
and scroll down to the list of supported Microsoft Windows operating systems.
2. Make sure that the SAS/SATA hard disk drive cables are securely connected.
The operating system cannot be Make sure that the server supports the operating system. If it does, either no
installed; the option is not
logical drive is defined (SCSI RAID servers), or the ServerGuide System Partition
is not present. Run the ServerGuide program and make sure that setup is
available.
complete.
153
Software problems
solved.
technician.
Symptom
Action
You suspect a software

problem.
1. To determine whether the problem is caused by the software, make sure that:
v The server has the minimum memory that is needed to use the software. For
memory requirements, see the information that comes with the software. If
you have just installed an adapter or memory, the server might have a
memory-address conflict.
v The software is designed to operate on the server.
v Other software works on the server.
v The software works on another server.
2. If you received any error messages when using the software, see the
information that comes with the software for a description of the messages and
suggested solutions to the problem.
3. Contact the software vendor.
Universal Serial Bus (USB) port problems

solved.
technician.
Symptom
Action
A USB device does not work.
1. Make sure that:

v The correct USB device driver is installed.
v The operating system supports USB devices.
2. Make sure that the USB configuration options are set correctly in the Setup
utility (see Using the Setup utility on page 88 for more information).
3. If you are using a USB hub, disconnect the USB device from the hub and
connect it directly to the server.
154
Video problems
See Monitor and video problems on page 146.
Solving power problems

Use this information to solve power problems.
Power problems can be difficult to solve. For example, a short circuit can exist
anywhere on any of the power distribution buses. Usually, a short circuit will
cause the power subsystem to shut down because of an overcurrent condition. To
diagnose a power problem, use the following general procedure:
1. Turn off the server and disconnect all ac power cords.
2. Check for loose cables in the power subsystem. Also check for short circuits, for
example, if a loose screw is causing a short circuit on a circuit board.
3. If the system-error LED on the system board is lit, complete the following
steps:
a. Check the IMM2 event log. To access the web interface, see Logging on to
the Web interface on page 99.
b. If a log indicates that there is a power rail failure, find the location of the
failed power rail on the system board.
c. Disconnect the cables and power cords to all internal and external devices
(see Internal cable routing on page 174). Leave the power-supply cords
connected.
d. Remove each component that is associated with the failed power
component, one at a time, restarting the server each time, until the cause of
the failure is identified.
e. Replace the identified component.
4. Reconnect all power cords and turn on the server. If the server starts
successfully, replace the adapters and devices one at a time until the problem is
isolated.
If the server does not start from the minimum configuration, see Power-supply
LEDs on page 129 to replace the components in the minimum configuration one
at a time until the problem is isolated.
Solving Ethernet controller problems

Use this information to solve the Ethernet controller problems.
The method that you use to test the Ethernet controller depends on which
operating system you are using. See the operating-system documentation for
information about Ethernet controllers, and see the Ethernet controller
device-driver readme file.
Try the following procedures:
v Make sure that the correct device drivers, which come with the server are
installed and that they are at the latest level.
v Make sure that the Ethernet cable is installed correctly.
The cable must be securely attached at all connections. If the cable is attached
but the problem remains, try a different cable.
If you set the Ethernet controller to operate at 100 Mbps, you must use
Category 5 cabling.
155
v
v
If you directly connect two servers (without a hub), or if you are not using a
hub with X ports, use a crossover cable. To determine whether a hub has an X
port, check the port label. If the label contains an X, the hub has an X port.
Determine whether the hub supports auto-negotiation. If it does not, try
configuring the integrated Ethernet controller manually to match the speed and
duplex mode of the hub.
Check the Ethernet controller LEDs on the rear panel of the server. These LEDs
indicate whether there is a problem with the connector, cable, or hub.
The Ethernet link status LED is lit when the Ethernet controller receives a link
pulse from the hub. If the LED is off, there might be a defective connector or
cable or a problem with the hub.
The Ethernet transmit/receive activity LED is lit when the Ethernet controller
sends or receives data over the Ethernet network. If the Ethernet
transmit/receive activity is off, make sure that the hub and network are
operating and that the correct device drivers are installed.
Check for operating-system-specific causes of the problem.
Make sure that the device drivers on the client and server are using the same
protocol.
If the Ethernet controller still cannot connect to the network but the hardware
appears to be working, the network administrator must investigate other possible
causes of the error.
Solving undetermined problems

If Dynamic System Analysis (DSA) cannot diagnose the failure or if the server is
inoperative, use the information in this section to solve the undetermined
problems.
If you suspect that a software problem is causing failures (continuous or
intermittent), see Power problems on page 151.
Corrupted data in CMOS memory or corrupted UEFI firmware can cause
undetermined problems. To reset the CMOS data, use the CMOS jumper to clear
the CMOS memory and override the power-on password; see System-board
jumpers on page 29. If you suspect that the UEFI firmware is corrupted, see
Recovering the server firmware (UEFI update failure) on page 158.
If the power supplies are working correctly, complete the following steps:
1. Turn off the server.
2. Make sure that the server cover is closed and latched correctly.
3. Make sure that the server top cover/power cut-off switch cable is connected
correctly.
4. Make sure that the server is cabled correctly.
5. Remove or disconnect the following devices, one at a time, until you find the
failure. Turn on the server and reconfigure it each time.
v Any external devices.
v Surge-suppressor device (on the server).
v Printer, mouse, and non-IBM devices.
v Each adapter.
v Hard disk drives.
v Memory modules. The minimum configuration requirement is 2 GB DIMM
in slot 1 when one microprocessor is installed in the server.
156
If the problem is solved when you remove an adapter from the server but the
problem recurs when you reinstall the same adapter, suspect the adapter; if the
problem recurs when you replace the adapter with a different one, suspect the riser
card.
If you suspect a networking problem and the server passes all the system tests,
suspect a network cabling problem that is external to the server.
Problem determination tips

Because of the variety of hardware and software combinations that can encounter,
use the following information to assist you in problem determination. If possible,
have this information available when requesting assistance from IBM.
The model number and serial number are located on the ID label on the front of
the server as shown in the following illustration.
Note: The illustrations in this document might differ slightly from your hardware.
ID label
Figure 72. ID label
v Machine type and model

v Microprocessor or hard disk drive upgrades
v Failure symptom
Does the server fail the Dynamic System Analysis diagnostic tests?
What occurs? When? Where?
Does the failure occur on a single server or on multiple servers?

Is the failure repeatable?
Has this configuration ever worked?
What changes, if any, were made before the configuration failed?
Is this the original reported failure?

v Diagnostic program type and version level
v Hardware configuration (print screen of the system summary)
v UEFI firmware level
v IMM firmware level
v Operating-system software
You can solve some problems by comparing the configuration and software setups
between working and nonworking servers. When you compare servers to each
other for diagnostic purposes, consider them identical only if all the following
factors are exactly the same in all the servers:
v Machine type and model
v UEFI firmware level
v IMM firmware level
v Adapters and attachments, in the same locations
v Address jumpers, terminators, and cabling
157
v
v
v
v
Software versions and levels

Diagnostic program type and version level
Setup utility settings
Operating-system control-file setup
See Appendix D, Getting help and technical assistance, on page 669 for
information about calling IBM for service.
Recovering the server firmware (UEFI update failure)

Use this information to recover the server firmware.
If the server firmware has become corrupted, such as from a power failure during
an update, you can recover the server firmware in either of two ways:
v In-band method: Recover server firmware, using either the boot block jumper
(Automated Boot Recovery) and a server Firmware Update Package Service
Pack.
v Out-of-band method: Use the IMM Web interface to update the firmware, using
the latest server firmware update package.
Note: You can obtain a server update package from one of the following sources:
v Download the server firmware update from the World Wide Web.
v Contact your IBM service representative.
To download the server firmware update package from the World Wide Web, go to
The flash memory of the server consists of a primary bank and a backup bank. You
must maintain a bootable IBM System x Server Firmware (server firmware) image
in the backup bank. If the server firmware in the primary bank becomes corrupted,
you can either manually boot the backup bank with the boot block jumper, or in
the case of image corruption, this will occur automatically with the Automated
Boot Recovery function.
In-band manual recovery method
To recover the server firmware and restore the server operation to the primary
bank, complete the following steps:
1. Turn off the server, and disconnect all power cords and external cables.
2. Remove the server cover. See Removing the server top cover on page 202
for more information.
3. Locate the UEFI boot recovery jumper (J2) on the system board.
158
Figure 73. UEFI boot recovery jumper locations
4. Move the jumper from pins 1 and 2 to pins 2 and 3 to enable the UEFI
recovery mode.
5. Reinstall the server cover; then, reconnect all power cords.
6. Restart the server. The power-on self-test (POST) starts.
7. Boot the server to an operating system that is supported by the IBM Flash
UEFI Update package that you downloaded.
8. Perform the firmware update by following the instructions that are in the
firmware update package readme file.
9. Copy the downloaded firmware update package into a directory.
10. From a command line, type filename-s, where filename is the name of the
executable file that you downloaded with the firmware update package.
11. Turn off the server and disconnect all power cords and external cables, and
then remove the server cover.
12. Move the UEFI boot recovery jumper back to the primary position (pins 1 and
2).
13. Reinstall the server cover, and then reconnect all the power cables.
In-band automated boot recovery method
Note: Use this method if the BOARD LED on the light path diagnostics panel is lit
and there is a log entry or Booting Backup Image is displayed on the firmware
splash screen; otherwise, use the in-band manual recovery method.
1. Boot the server to an operating system that is supported by the firmware
update package that you downloaded.
2. Perform the firmware update by following the instructions that are in the
firmware update package readme file.
4. At the firmware splash screen, press F3 when prompted to restore to the
primary bank. The server boots from the primary bank.
Out-of-band method: See the IMM documentation.
159
For more information about UEFI-compliant firmware, go to http://

www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5083207.
Automated boot recovery (ABR)

Use this information for Automated boot recovery (ABR).
While the server is starting, if the integrated management module detects problems
with the server firmware in the primary bank, the server automatically switches to
the backup firmware bank and gives you the opportunity to recover the firmware
in the primary bank. For instructions for recovering the UEFI firmware, see
Recovering the server firmware (UEFI update failure) on page 158. After you
have recovered the firmware in the primary bank, complete the following steps:
2. When the prompt press F3 to restore to primary is displayed, press F3 to
recover the primary bank. Pressing F3 will restart the server.
Nx boot failure
Use this information for Nx-boot failure.
Configuration changes, such as added devices or adapter firmware updates, and
firmware or application code problems can cause the server to fail POST (the
power-on self-test). If this occurs, the server responds in either of the following
ways:
v The server restarts automatically and attempts POST again.
v The server hangs, and you must manually restart the server for the server to
attempt POST again.
After a specified number of consecutive attempts (automatic or manual), the Nx
boot failure feature causes the server to revert to the default UEFI configuration
and start the Setup utility so that you can make the necessary corrections to the
configuration and restart the server. If the server is unable to successfully complete
POST with the default configuration, there might be a problem with the system
board.
To specify the number of consecutive restart attempts that will trigger the Nx boot
failure feature, perform the following steps:
1. In the Setup utility, click System Settings > Recovery > POST Attempts >
POST Attempts Limit.
2. The available options are 3, 6, 9, and 255 (disable Nx boot failure). Select your
option.
160
Chapter 5. Parts listing, IBM System x3530 M4 Type 7160

The parts listing of IBM System x3530 M4 Type 7160.
The following replaceable components are available for the IBM System x3530 M4
Type 7160 server, except as specified otherwise in Replaceable server
components. For an updated parts listing, go to http://www.ibm.com/
supportportal/.
Replaceable server components

The replaceable server components for IBM System x3530 M4 Type 7160.
Replaceable components consist of consumable parts, structural parts, and field
replaceable units (FRUs):
v Consumables: Purchase and replacement of consumables (components, such as
batteries and printer cartridges, that have depleting life) is your responsibility. If
IBM acquires or installs a consumable component at your request, you will be
charged for the service.
v Structural parts: Purchase and replacement of structural parts (components, such
as chassis assembly, top cover, and bezel) is your responsibility. If IBM acquires
or installs a structural component 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.
For information about the terms of the warranty and getting service and assistance,
see the Warranty Information document that comes with the server. For more
information about getting service and assistance, see Appendix D, Getting help
and technical assistance, on page 669.
The following illustration shows the major components in the server. The
illustrations in this document might differ slightly from your hardware.
161
Figure 74. Server components
The following table lists the part numbers for the server components.
162
Table 14. Parts listing, Type 7160

Index
CRU part
CRU part
number (Tier 1) number (Tier 2)
Description
PCI Express 3.0 riser card assembly, x16 full-height, half-length
00FK950
PCI Express 3.0 riser card assembly, x16 full-height, half-length
00D4427
PCI Express 3.0 riser card assembly, x8 two-slot
00FK948
PCI Express 3.0 riser card assembly, x8 two-slot
00D4428
PCI Express 3.0 riser card assembly, x4
00FK952
PCI Express 3.0 riser card assembly, x4
00D4426
Power supply, 460 Watt, fixed
94Y8085
Air baffle/filler for power supply unit
00W2051
Power supply, 675 Watt, dc
39Y7215
Power supply, 675 Watt HE, ac
39Y7218
Power supply, 460 Watt
39Y7229
69Y5876
69Y5907
69Y5933
69Y5939
69Y5901
69Y5903
69Y5905
69Y5943
Heat sink assembly (all models)
94Y7813
10
Microprocessor, Intel Xeon E5-2403 v2 1.8 GHz, 10 MB, 80 W (quad

core)
46W4281
10
Microprocessor, Intel Xeon E5-2407 v2 2.4 GHz, 10 MB, 80 W (quad

core)
46W4282
10
Microprocessor, Intel Xeon E5-2420 v2 2.2 GHz, 15 MB, 80 W (six

core)
46W4283
10
Microprocessor, Intel Xeon E5-2430 v2 2.5 GHz, 15 MB, 80 W (six

core)
46W4284
10
Microprocessor, Intel Xeon E5-2440 v2 1.9 GHz, 20 MB, 95 W (eight

core)
46W4285
10
Microprocessor, Intel Xeon E5-2450 v2 2.5 GHz, 20 MB, 95 W (eight

core)
46W4286
10
Microprocessor, Intel Xeon E5-2470 v2 2.4 GHz, 25 MB, 95 W (ten

core)
46W4287
10
Microprocessor, Intel Xeon E5-2430L v2 2.4 GHz, 15 MB, 60 W (six

core)
46W4288
10
Microprocessor, Intel Xeon E5-2450L v2 1.7 GHz, 25 MB, 60 W (ten

core)
46W4289
10
Microprocessor, Intel Pentium 1403 v2 2.6 GHz, 5 MB, 80 W (dual

core)
46W4290
10
Microprocessor, Intel Pentium 1410 v2 2.8 GHz, 10 MB, 80 W (quad

core)
46W4292
163
Table 14. Parts listing, Type 7160 (continued)

Index
Description
CRU part
CRU part
10
Microprocessor, Intel Xeon E5-2470 2.3 GHz, 20 MB, 95 W (dual

quad core)
90Y4736
10
Microprocessor, Intel Xeon E5-2450 2.1 GHz, 20 MB, 95 W (dual

quad core)
90Y4738
10
Microprocessor, Intel Xeon E5-2440 2.4 GHz 15 MB, 95 W (six core)
90Y4739
10
Microprocessor, Intel Xeon E5-2430 2.2 GHz, 15 MB, 95 W (six core)
90Y4740
10
Microprocessor, Intel Xeon E5-2420 1.9 GHz, 15 MB, 95 W (six core)
90Y4742
10
Microprocessor, Intel Xeon E5-2407 2.2 GHz, 10 MB, 80 W (quad

core)
90Y4743
10

core)
90Y4744
10
Microprocessor, Intel Xeon E5-1403 2.6 GHz, 5 MB, 80 W (dual core)
90Y4745
10
Microprocessor, Intel Xeon E5-1407 2.8 GHz, 5 MB, 80 W (dual core)
90Y4746
10
Microprocessor, Intel Xeon E5-2450L 1.8 GHz, 20 MB, 70 W (dual

quad core)
90Y4747
10
Microprocessor, Intel Xeon E5-2430L 2.0 GHz, 15 MB, 60 W (six core)
90Y4748
10
Microprocessor module, Intel Xeon E5-2428L (EMB) EN-1.8 GHz, 15

MB, 7.2GT/S-QPI, 60 W (six core)
00D8760
10
Microprocessor module, Intel Xeon E5-2448L (EMB) EN-1.8 GHz, 20

MB, 8.0GT/S-QPI, 70 W (eight core)
00D8761
10
Microprocessor, Intel Xeon E5-2418L 2.0 GHz 10 MB, 50 W (quad

core)
00D8762
10

core)
00D9038
10
Microprocessor, Intel Xeon E5-2418L v2 2.0 GHz, 15 MB, 45 W (six

core)
00Y8135
10
Microprocessor, Intel Xeon E5-2428L v2 2.4 GHz, 20 MB, 60 W (eight

core)
00Y8136
10
Microprocessor, Intel Xeon E5-2448L v2 2.0 GHz, 25 MB, 70 W (ten

core)
00Y8137
11
System board (base assembly type 1 for use with Intel Xeon
Processor E5-2600 series)
00FL492
Type 7160 - A1x, B1x, F2x, A2x, B2x, C2x, D2x, E1Y, E2Y, E3Y, E4Y,
EAY, EBY, ECY, G2x, H2x, J2x
11
System board (base assembly type 2 for use with Intel Xeon
Processor E5-2600 v2 series)
00Y7538
Type 7160 - A3x, A5x, A7x, B3x, B5x, B7x, C3x, F3x, G3x
164
14
Power paddle card
69Y5879
17
DVD-ROM drive
44W3254
17
DVD-RW drive
44W3256
18
Operator information panel
90Y5821
18
Operator information panel, advanced
00AM393
24
Hard disk drive, 3.5-inch SATA, simple-swap, 500 GB 7.2K
81Y9803

Index
CRU part
CRU part
Description
24
Hard disk drive, 3.5-inch Near-Line SATA, simple-swap, 1TB 7.2K
81Y9807
24
Hard disk drive, 3.5-inch SATA, simple-swap, 2TB 7.2K
81Y9811
24
Hard disk drive, 3.5-inch Near-Line SATA, simple-swap, 3TB 7.2K
81Y9815
25
Hard disk drive, 3.5-inch Near-Line SATA, hot-swap, 1TB 7.2K
81Y9791
25
Hard disk drive, 3.5-inch SATA, hot-swap, 7.2K 6 Gbps
81Y9795
25
Hard disk drive, 3.5-inch SATA, hot-swap, 3TB 7.2K
81Y9799
25
Hard disk drive, 3.5-inch Near-Line SATA, hot-swap, 500 GB 7.2K 6

Gbps
81Y9787
25
Hard disk drive, 3.5-inch Near-Line SAS, hot-swap, 1 TB, 7.2 K
90Y8568
25
Hard disk drive, 3.5-inch hot-swap, 2 TB, 7.2 K
90Y8573
25
Hard disk drive, 3.5-inch Near-Line SAS, hot-swap, 3 TB, 7.2 K
90Y8578
27
Hard disk drive, 2.5-inch hot-swap, 1.2 TB, 10 K, SAS
00AD076
27
Hard disk drive, 2.5-inch hot-swap SE, 1.2 TB, 10 K, SAS
00AD086
27
Solid state drive, 2.5-inch hot-swap, 600 GB 15K SAS 6 Gbps 512E
G2
00AJ301
27
Solid state drive, 2.5-inch hot-swap, 120 GB SATA
00AJ356
27
00AJ361
27
00AJ366
27
00AJ371
27
Hard disk drive, 2.5-inch hot-swap, 900 GB, 10 K
81Y9651
27
81Y9691
27
Hard disk drive, 2.5-inch hot-swap, 250 GB, 7.2 K
81Y9723
27
Hard disk drive, 2.5-inch hot-swap, 500 GB, 7.2 K
81Y9727
27
81Y9731
27
81Y9671
27
90Y8878
27
90Y8927
27
Hard disk drive, 2.5-inch hot-swap, 146 GB, 15 K, SED
90Y8945
28
Solid state drive, 2.5-inch simple-swap, SAS, 1.2 TB, 10 K
00AD081
28
Solid state drive, 2.5-inch simple-swap, 120 GB SATA
00AJ376
28
00AJ381
28
00AJ386
28
00AJ391
28
Solid state drive, 2.5-inch simple-swap, SATA, 200 GB
43W7745
28
Solid state drive, 2.5-inch simple-swap, SATA SFF slim 64 GB
49Y5840
28
Solid state drive, 2.5-inch simple-swap, SATA SFF slim 512 GB
49Y5845
28
Solid state drive, 2.5-inch simple-swap, SATA SFF 64 GB
49Y5850
28
Solid state drive, 2.5-inch simple-swap, SATA SFF 512 GB
49Y5855
28
90Y8664
28
90Y8669
165

Index
166
Description
CRU part
CRU part
28
Solid state drive, 2.5-inch hot-swap, SATA, 200 GB
43W7721
28
Hard disk drive, 2.5-inch simple-swap, 900 GB 10 K 6 Gbps SAS SFF
81Y9655
28
Hard disk drive, 2.5-inch simple-swap, 300 GB 15 K 6 Gbps SAS SFF
81Y9675
28
Hard disk drive, 2.5-inch simple-swap, 1TB 7.2 K 6 Gbps NL SATA

SFF
81Y9743
28
Hard disk drive, 2.5-inch simple-swap, 600 GB 10K 6 GB SFF SAS PI
90Y8891
28
Hard disk drive, 2.5-inch simple-swap, SAS 300 GB 10K 6 Gbps SFF
G2
90Y8896
28
Hard disk drive, 2.5-inch simple-swap, SAS 146 GB 15K 6 Gbps SFF
G2
90Y8936
29
3.5-inch hot-swap backplane bracket assembly
46W6624
30
3.5-inch simple-swap bracket
00D4434
32
Sprint backplane
94Y7587
34
Fan cage assembly (all models)
00D2567
35
Memory, 16 GB dual-rank 1.35 V, DDR3, 1600MHz, RDIMM
46W0674
35
Memory, 32 GB quad-rank 1.5 V, DDR3, 1866MHz, LRDIMM
46W0763
35
49Y1415
35
Memory, 8 GB quad-rank 1.35 V, DDR3, 1333MHz, RDIMM
49Y1417
35
Memory, 4 GB dual-rank 1.35 V, DDR3, 1333MHz, UDIMM
49Y1422
35
Memory, 2 GB single-rank 1.35 V, DDR3, 1333MHz, RDIMM
49Y1423
35
49Y1424
35
49Y1425
35
49Y1561
35
49Y1565
35
90Y3107
35
90Y3180
35
90Y3111
35
00D5014
35
00D5018
35
00D5026
35
Memory, 8 GB, single-rank 1.35 V, DDR3, 1600MHz, RDIMM
00D5038
35
Memory, 8 GB, dual-rank 1.35 V, DDR3, 1600MHz, RDIMM
00D5046
35
00D4970
Thermal grease kit
41Y9292
Alcohol wipes
59P4739
Battery, 3.0 volt
33F8354
Cable, DD module
94Y5951
Cable, iPass mini SAS
00D2597
Cable, iPass mini SAS
94Y5954
Cable, optical disk drive, combo. slim
81Y7318

Index
CRU part
CRU part
Description
Cable, 1 M
39R6530
Cable, 3 M
39R6532
Cable, 1.5 M KVM conversion
39M2911
Cable, 3.5-inch hot-swap power
81Y7308
Cable, 2.5-inch simple-swap power
81Y7312
Cable, 2.5-inch power
81Y7316
Cable, 3.5-inch signal
81Y7306
Cable, 2.5-inch signal
81Y7314
Cable, serial conversion
46M4027
Cable, virtual media Gen 2
46M4028
Cable, USB board
94Y5952
Cable, 3.5-inch VGA
94Y6368
Cable, 2.5-inch VGA
94Y5953
Cable, flash power module ServeRAID M5100 series 425 mm
90Y7310
Cord, 4 - 4.3 M line
39M5076
Cord, 1.5 M line
39M5375
Cord, 4.3 M line
39M5378
Cord, PDU jumper
30M5392
Cord, PDU C19 60A 3P with line
39Y8926
Cord, C13 PDU without line
00AK194
Drive, 5.25-inch, 36 GB, USB
99Y3868
Fiber optic
17P9211
Hypervisor, embedded USB flash device
42D0545
Keyboard
00AL883
Keyboard, USB US English 103P (RoHS)
00FL300
Keyboard, US English 103P (RoHS)
94Y6050
Keyboard
94Y6108
Label, chassis
00D4431
Label, FRU/CRU list
00W2170
Label, GBM
00D4430
Label, system service
00J6284
NetXtreme II 1000 express Ethernet adapter
39Y6070
NEMA PDU
39Y8913
PRO/1000 PF adapter
42C1752
QLogic 10Gb virtual fabric and SR optical transceiver
42C1816
Brocade 10Gb adapter
42C1822
Emulex 8Gb FC single-port host bus adapter
42D0491
Emulex 8Gb FC dual-port host bus adapter
42D0500
Video adapter, NVIDIA Quadro 600
43V5931
167

Index
168
Description
CRU part
CRU part
4Gb FC PCIe single-port adapter
43W7510
4Gb FC PCIe dual-port adapter
43W7512
ServeRAID M1115 SAS/SATA adapter
46C8928
ServeRAID M5100 series 512 MB flash (RAID 5 upgrade)
46C9027
ServeRAID M5100 series 1 GB flash (RAID 5 upgrade)
46C9029
ServeRAID M5100 series 2 GB flash (RAID 5 upgrade)
47C8671
ServeRAID M5120
00AE811
ServeRAID M5100 series 512 MB cache (RAID 5 upgrade)
81Y4485
ServeRAID H1110 SAS/SATA adapter
81Y4494
ServeRAID M5110
00AE807
RDX 160 GB cartridge
46C5393
46C5394
46C5395
RSPDU+ 24C13 30A
46W1562
RSPDU 24C13 3P
46W1568
RSPDU 24C13 1P
46W1570
Strip Switched & Monitored PDU 12 C19 & 12 C13 fixed 3M 50A or
60A 3
46W1574
Strip Strip PDU 12 C19 & 12 C13 60A 3 fixed 3M 50A or 60A 3
46W1578
RPDU+ 9C19/3C13 3P
46W1582
Acc Kit (1U)
46M5293
Half high LTO Gen 3 SAS tape drive
46X5663
Half high LTO Gen 5 SAS tape drive
46X5683
USB cage assembly
00D4449
USB optical wheel
39Y9875
USB/SATA dongle
44E8876
Dual-port 10 GbE adapter
81Y9993
Brocade 8Gb FC single-port host bus adapter
46M6061
Brocade 8Gb FC dual-port host bus adapter
46M6062
Intel I340-T2 Ethernet dual-port adapter
94Y5166
Intel I340-T4 Ethernet quad-port adapter
94Y5167
Broadcom NetXtreme II dual-port 10Gb adapter
49Y7912
Endeavor basic 10Gb BE3-R adapter
00D8543
NetXtreme II 1000 express Ethernet dual-port adapter
49Y7947
NetXtreme II 1000 express Ethernet quad-port adapter
49Y7949
Intel X520-DA2 dual-port 10Gb virtual fabric adapter
49Y7962
Brocade 4Gb FC single-port host bus adapter
59Y1992
Brocade 4Gb FC dual-port host bus adapter
59Y1998
IBM 6 Gb SAS HBA
46C8935

Index
CRU part
CRU part
Description
IBM 6 Gb performance optimized HBA
46C8937
Mellanox ConnectX-2 VPI dual-port QSFP QDR IB/10GbE PCI-E 2.0

HCA
81Y1537
Emulex 16Gb FC single-port HBA
81Y1658
Emulex 16Gb FC dual-port HBA
81Y1665
Brocade 16Gb FC single-port HBA
81Y1671
Brocade 16Gb FC dual-port HBA
81Y1678
Broadcom NetExtreme qp
90Y9355
Broadcom NetExtreme dp
90Y9373
Emulex 10 GbE
95Y3766
Washer spacer
00Y8219
Consumable parts
Consumable parts are not covered by the IBM Statement of Limited Warranty. You
can place an order on the structural parts from the IBM retail store.
The following consumable parts are available for purchase from the retail store.
Table 15. Consumable parts, Type 7160
Index
Description
Part number
12
ServeRAID M5110 series battery kit
81Y4491
To order a consumable part, complete the following steps:

Note: Changes are made periodically to the IBM website. The actual procedure
1. Go to http://www.ibm.com.
2. From the Products menu, select Upgrades, accessories & parts.
3. Click Obtain maintenance parts; then, follow the instructions to order the part
from the retail store.
If you need help with your order, call the toll-free number that is listed on the
retail parts page, or contact your local IBM representative for assistance.
169
Structural parts
Structural parts are not covered by the IBM Statement of Limited Warranty. You
can place an order on the structural parts from the IBM retail store.
Table 16. Structural parts, Type 7160
Index
Description
Part number
Top cover
00D4437
Power supply unit cage, redundant
00D4444
Power supply unit cage, fixed
00D4445
Filler, power supply 1U
49Y4821
13
Remote RAID battery tray
00W2199
15
Chassis assembly (3.5-inch, without front bezel)
00D4433
15
Chassis assembly (2.5-inch, without front bezel)
00D4440
16
Filler, optical drive
00D4436
19
Front bezel, 3.5-inch
00D4447
20
Front bezel, 2.5-inch
00D4448
21
Filler, 3.5-inch simple-swap
69Y5368
21
Filler, 3.5-inch hot-swap
69Y5364
26
Filler, blank EMC
44T2248
31
2.5-inch simple-swap bracket assembly
00J6283
33
Air baffle
00D4439
240 VA safety cover
00D4435
EIA kit
00D4438
2.5-inch mechanical shell assembly
00AL104
00J6281
00AL103
00W2198
Acc kit (1U)
46M5293
Cartridge, 160 GB
46C5393
Cartridge, 320 GB
46C5394
Cartridge, 500 GB
46C5395
Filler, DIMM
81Y4297
Filler, hard disk drive bay
59Y3925
Miscellaneous parts kit
00D4446
Static rail assembly
00Y8216
Static rail kit
94Y6790
USB cage assembly
00D4449
To order a structural part, Go to http://www.ibm.com.

If you need help with your order, call the toll-free number that is listed on the
retail parts page, or contact your local IBM representative for assistance.
170
Power cords
For your safety, a power cord with a grounded attachment plug is provided to use
with this product. To avoid electrical shock, always use the power cord and plug
with a properly grounded outlet.
power cords
Power cords for this product that are used in the United States and Canada are
listed by Underwriter's Laboratories (UL) and certified by the Canadian Standards
Association (CSA).
For units intended to be operated at 115 volts: Use a UL-listed and CSA-certified
cord set consisting of a minimum 18 AWG, Type SVT or SJT, three-conductor cord,
a maximum of 15 feet in length and a parallel blade, grounding-type attachment
plug rated 15 amperes, 125 volts.
For units intended to be operated at 230 volts (U.S. use): Use a UL-listed and
CSA-certified cord set consisting of a minimum 18 AWG, Type SVT or SJT,
three-conductor cord, a maximum of 15 feet in length and a tandem blade,
grounding-type attachment plug rated 15 amperes, 250 volts.
For units intended to be operated at 230 volts (outside the U.S.): Use a cord set
with a grounding-type attachment plug. The cord set should have the appropriate
safety approvals for the country in which the equipment will be installed.
Power cords for a specific country or region are usually available only in that
country or region.
Power cord part
number
Used in these countries and regions
39M5206
China
39M5102
Australia, Fiji, Kiribati, Nauru, New Zealand, Papua New Guinea
39M5123
Afghanistan, Albania, Algeria, Andorra, Angola, Armenia,

Austria, Azerbaijan, Belarus, Belgium, Benin, Bosnia and
Herzegovina, Bulgaria, Burkina Faso, Burundi, Cambodia,
Cameroon, Cape Verde, Central African Republic, Chad,
Comoros, Congo (Democratic Republic of), Congo (Republic of),
Cote D'Ivoire (Ivory Coast), Croatia (Republic of), Czech
Republic, Dahomey, Djibouti, Egypt, Equatorial Guinea, Eritrea,
Estonia, Ethiopia, Finland, France, French Guyana, French
Polynesia, Germany, Greece, Guadeloupe, Guinea, Guinea Bissau,
Hungary, Iceland, Indonesia, Iran, Kazakhstan, Kyrgyzstan, Laos
(People's Democratic Republic of), Latvia, Lebanon, Lithuania,
Luxembourg, Macedonia (former Yugoslav Republic of),
Madagascar, Mali, Martinique, Mauritania, Mauritius, Mayotte,
Moldova (Republic of), Monaco, Mongolia, Morocco,
Mozambique, Netherlands, New Caledonia, Niger, Norway,
Poland, Portugal, Reunion, Romania, Russian Federation,
Rwanda, Sao Tome and Principe, Saudi Arabia, Senegal, Serbia,
Slovakia, Slovenia (Republic of), Somalia, Spain, Suriname,
Sweden, Syrian Arab Republic, Tajikistan, Tahiti, Togo, Tunisia,
Turkey, Turkmenistan, Ukraine, Upper Volta, Uzbekistan,
Vanuatu, Vietnam, Wallis and Futuna, Yugoslavia (Federal
Republic of), Zaire
39M5130
Denmark
171
Power cord part

number
Used in these countries and regions
39M5144
Bangladesh, Lesotho, Macao, Maldives, Namibia, Nepal, Pakistan,

Samoa, South Africa, Sri Lanka, Swaziland, Uganda
39M5151
Abu Dhabi, Bahrain, Botswana, Brunei Darussalam, Channel

Islands, China (Hong Kong S.A.R.), Cyprus, Dominica, Gambia,
Ghana, Grenada, Iraq, Ireland, Jordan, Kenya, Kuwait, Liberia,
Malawi, Malaysia, Malta, Myanmar (Burma), Nigeria, Oman,
Polynesia, Qatar, Saint Kitts and Nevis, Saint Lucia, Saint Vincent
and the Grenadines, Seychelles, Sierra Leone, Singapore, Sudan,
Tanzania (United Republic of), Trinidad and Tobago, United Arab
Emirates (Dubai), United Kingdom, Yemen, Zambia, Zimbabwe
39M5158
Liechtenstein, Switzerland
39M5165
Chile, Italy, Libyan Arab Jamahiriya
39M5172
Israel
39M5095
220 - 240 V
Antigua and Barbuda, Aruba, Bahamas, Barbados, Belize,
Bermuda, Bolivia, Caicos Islands, Canada, Cayman Islands,
Colombia, Costa Rica, Cuba, Dominican Republic, Ecuador, El
Salvador, Guam, Guatemala, Haiti, Honduras, Jamaica, Mexico,
Micronesia (Federal States of), Netherlands Antilles, Nicaragua,
Panama, Peru, Philippines, Saudi Arabia, Thailand, Taiwan,
United States of America, Venezuela
39M5076
110 - 120 V
Antigua and Barbuda, Aruba, Bahamas, Barbados, Belize,
Bermuda, Bolivia, Caicos Islands, Canada, Cayman Islands,
Colombia, Costa Rica, Cuba, Dominican Republic, Ecuador, El
Salvador, Guam, Guatemala, Haiti, Honduras, Jamaica, Mexico,
Micronesia (Federal States of), Netherlands Antilles, Nicaragua,
Panama, Peru, Philippines, Saudi Arabia, Thailand, Taiwan,
United States of America, Venezuela
172
39M5219
Korea (Democratic People's Republic of), Korea (Republic of)
39M5199
Japan
39M5226
India
39M5240
Brazil
Chapter 6. Removing and replacing components

Use this information to remove and replace the server components.
service.
v Field replaceable unit (FRU): FRUs must be installed only by trained
technicians, unless they are classified as customer replaceable units (CRUs):
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.
Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or
See Chapter 5, Parts listing, IBM System x3530 M4 Type 7160, on page 161 to
determine whether a component is a consumable, structural, or FRU that must be
replaced only by a trained service technician.
For information about the terms of the warranty, see the Warranty Information
For more information about getting service and assistance, see Appendix D,
Getting help and technical assistance, on page 669.
Returning a device or component

If you are instructed to return a device or component, follow all packaging
instructions, and use any packaging materials for shipping that are supplied to
you.
173
Internal cable routing

This section provides information about routing the cables when you install some
components in the server.
For more information about the requirements for cables and connecting devices,
see the documentation that comes with these devices.
Attention: Failing to install or remove the cable with care may damage the
connectors on the system board. Any damage to the connectors may require
replacing the system board.
General
The following illustrations show the general cabling information.
The following illustrations show the cabling information for the optional optical
drive with different power supply models:
174
DVD drive
cable
Power cable
DVD drive
cable
Power cable
Figure 75. Cabling information for the optional optical drive with different power supply
models
175
Attention: Failing to disconnect the optical drive cable from the system board
properly may damage the connector on the system board. Any damage to the
connector may require replacing the system board.
The following illustrations show the cabling information for the power interposer
card assembly for fixed and redundant power supply models respectively:
176
Power cables
Power cables
Figure 76. Cabling information for the power interposer card assembly for fixed and
redundant power supply models
177
The following illustration shows the cabling information for installing the RAID
battery remotely in the server:
Figure 77. Cabling information for installing the RAID battery remotely
178
2.5-inch hard disk drive cable connection

The following illustration shows the 2.5-inch hard disk drive cable connection.
4-drive-capable model
The following illustrations show the cabling information for the model of
4x2.5-inch hot-swap drive bays.
The following illustration shows the cabling information for the configuration cable
in the server:
Figure 78. Cabling information for the configuration cable
The following illustration shows the cabling information for the power cable in the
server:
179
Power cable
Figure 79. Cabling information for the power cable (redundant power model)
180
Power cable
Figure 80. Cabling information for the power cable (fixed power model)
The following illustration shows the cabling information for the hardware RAID
cable in the server:
181
Figure 81. Cabling information for the hardware RAID cable
The following illustration shows the cabling information for the software RAID
182
Figure 82. Cabling information for the software RAID cable
8-drive-capable model
The following illustrations show the cabling information for the model of
8x2.5-inch drive bays
The following illustrations show the cabling information for the two 4x2.5-inch
hot-swap drives model:
in the server:
183
The following illustrations show the cabling information for the power cable in the
server:
184
Power cable
185
Power cable
186
187
The following illustrations show the cabling information for the two 4x2.5-inch
simple-swap drives model:
server:
188
189
190
191
3.5-inch hard disk drive cable connection

The following illustration shows the 3.5-inch hard disk drive cable connection.
3.5-inch hot-swap model

The following illustrations show the cabling information for the 4x3.5-inch
hot-swap SATA/SAS drive backplane assembly.
in the server:
192
server:
193
194
195
196
3.5-inch simple-swap model

The following illustration shows the cabling information for the 4x3.5-inch
simple-swap SATA drive backplate assembly:
server:
197
198
199
200
Removing and replacing components

Use this information to remove and replace the server components.
service.
v Field replaceable unit (FRU): FRUs must be installed only by trained
technicians, unless they are classified as customer replaceable units (CRUs):
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.
Tier 2 customer replaceable unit: You may install a Tier 2 CRU yourself or
201
See Chapter 5, Parts listing, IBM System x3530 M4 Type 7160, on page 161 to
determine whether a component is a consumable, structural, or FRU that must be
replaced only by a trained service technician.
For information about the terms of the warranty, see the Warranty Information
For more information about getting service and assistance, see Appendix D,
Getting help and technical assistance, on page 669.
Removing the server top cover

Use this information to remove the server top cover.
Attention: If you release the cover latch and remove the cover while the server is
running, the server will lose power and turn off automatically. After you reinstall
the cover, you can power-on the server again.
To remove the server top cover, complete the following steps:
cabinet.
4. Loosen the two thumbscrews that secure the cover to the rear of the server.
5. Press on the two blue grip points and slide the cover toward the rear; then, lift
the cover off the server and set it aside.
Thumbscrew
Figure 101. Server topTop

cover
removal
cover
6. If you are instructed to return the cover, follow all packaging instructions, and
use any packaging materials for shipping that are supplied to you.
202
Replacing the server top cover

Use this information to replace the cover.
To replace the server cover, complete the following steps:
1. Make sure that all cables, adapters, and other components are installed and
seated correctly and that you have not left loose tools or parts inside the server.
Also, make sure that all internal cables are correctly routed.
2. Align the cover over the server (toward the rear of the server) until the cover
edges slip into position over the chassis.
Important: Before you slide the cover forward, make sure that all the tabs on
the cover engage the chassis correctly. If all the tabs do not engage the chassis
correctly, it will be hard to remove the cover later.
Thumbscrew
Top cover
Figure 102. Cover installation
3. Slightly slide the cover toward the front of the server until the inset tabs start
to engage on the server; then, tighten the thumbscrews to secure the cover to
the chassis.
203
Removing the bezel

Use this information to remove the bezel.
To remove the bezel, complete the following steps:
cabinet.
4. Remove the drives and filler panels from the drive bays (see Removing
hot-swap drives on page 210 or Removing a simple-swap SATA drive on
page 213).
5. Remove the EIA quick latch first; then, remove the screws from the bezel.
Bezel
screws
Figure 103. Bezel removal
6. Pull the top of the bezel out slightly; then, rotate it downward until the tabs on
the bottom of the bezel disengages from the chassis and set it aside.
7. If you are instructed to return the front bezel, follow all packaging instructions,
and use any packaging materials for shipping that are supplied to you.
204
Replacing the bezel

Use this information to install the bezel.
To install the bezel, complete the following steps:
1. Insert the tabs on the bottom of the bezel into the holes on the chassis.
2. Rotate the bezel upward to the server and reinstall the bezel screws. Then,
install the EIA quick latch.
Bezel
screws
Figure 104. Bezel installation
4. Reinstall the hard disk drives and drive bay filler panels into the drive bays.
5. Reconnect the power cords and any cables that you removed.
6. Turn on the peripheral devices and the server.
Removing the air baffle

Use this information to remove the air baffle from the server.
To remove the air baffle, complete the following steps:
4. Lift the air baffle from the server and set it aside.
Attention: For proper cooling and airflow, replace the air baffle before you
turn on the server. Operating the server with the air baffle removed might
damage server components.
205
Air baffle
Alignment hook
Figure 105. Air baffle removal
5. If you are instructed to return the air baffle, follow all packaging instructions,
Replacing the air baffle

Use this information to replace the air baffle.
To install the air baffle, complete the following steps:
2. Align the tabs on the sides of the air baffle with the slots on the fan cage and
lower the air baffle into the server.
Note: Make sure that no cable is pinched.
206
Air baffle
Alignment hook
Alignment pin
Figure 106. Air baffle installation
Removing and replacing Tier 1 CRUs

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.
Removing an adapter
Use this information to remove an adapter.
To remove an adapter, complete the following steps:
3. Remove the server cover (see Removing the server top cover on page 202).
4. Remove the PCI riser-card assembly (see Removing a PCI riser-card assembly
on page 251).
5. Disconnect any cables from the adapter.
6. Removing an adapter from PCI riser-card assembly 1:
Carefully grasp the adapter by its top edge or upper corners, and pull the
adapter from the PCI riser-card assembly.
207
PCI bracket
Adapter
PCI slot 1
PCI slot 2
PCI bracket
Riser-card
assembly 1
Adapter
Figure 107. Adapter removal from PCI riser-card assembly 1
7. Removing a RAID adapter from PCI riser-card assembly 2:

a. Pull the release pin to unlock the release latch.
b. Rotate the retention latch to the open position.
c. Carefully grasp the adapter by its top edge or upper corners, and pull the
adapter from the PCI riser-card assembly.
Figure 108. Adapter removal from PCI riser-card assembly 2
8. Place the adapter on a flat, static-protective surface.

9. If you are instructed to return the adapter, follow all packaging instructions,
208
Replacing an adapter
The following notes describe the types of adapters that the server supports and
other information that you must consider when you install an adapter.
Notes:
v The instructions in this section apply to any supported adapter (for example,
video graphics adapters or network adapters).
v See Installing an adapter on page 51 for additional notes and information that
you must consider when you install an adapter in the server.
video adapter is not supported
To replace an adapter, complete the following steps:
Attention: When you install an adapter, make sure that the adapter is correctly
seated in the PCI riser-card assembly and that the PCI riser-card assembly is
securely seated in the riser-card connector on the system board before you turn on
the server. An incorrectly seated adapter might cause damage to the system board,
the PCI riser-card assembly, or the adapter.
2. Follow the cabling instructions, if any come with the adapter. Route the
adapter cables before you install the adapter.
3. Installing an adapter in PCI riser-card assembly 1:
Insert the adapter into the PCI riser-card assembly, aligning the edge
connector on the adapter with the connector on the PCI riser-card assembly.
Press the edge of the connector firmly into the PCI riser-card assembly. Make
sure that the adapter snaps into the riser-card assembly securely.
PCI bracket
Adapter
PCI slot 1
PCI slot 2
PCI bracket
Riser-card
assembly 1
Adapter
Figure 109. Adapter removal to PCI riser-card assembly 1
4. Installing a ServeRAID adapter in PCI riser-card assembly 2:

a. Insert the adapter into the riser-card assembly, aligning the edge connector
on the adapter with the connector on the riser-card assembly. Press the
edge of the connector firmly into the riser-card assembly. Make sure that
the adapter snaps into the riser-card assembly securely.
209
b. Rotate the retention latch to the close position. Make sure the retention
latch engages the adapter securely; then, push in the release pin to lock the
PCI slot 3
Riser-card
assembly 2
Adapter
Figure 110. Adapter installation to PCI riser-card assembly 2
5. Install the PCI riser-card assembly in the server (see Replacing a PCI
6. Perform any configuration tasks that are required for the adapter.
7. Install the cover (see Replacing the server top cover on page 80).
9. Reconnect the power cord and any cables that you removed.
Removing hot-swap drives

Use this information to remove a hot-swap hard disk drive.
Attention:
v To avoid damage to the drive connectors, make sure that the server cover is in
place and fully closed whenever you install or remove a drive.
v To make sure that there is adequate system cooling, do not operate the server for
more than 2 minutes without either a drive or a filler panel installed in each bay.
Figure 111. Hot-swap hard disk drive removal
210
To remove a hot-swap drive, complete the following steps:

2. Press the release latch (orange) to unlock the drive handle.
3. Grasp the handle and pull the drive assembly out of the drive bay.
4. If you are instructed to return the drive assembly, follow all packaging
you.
Installing hot-swap drives

Use this information to install a hot-swap hard disk drive.
To install a hot-swap SAS or SATA drive, complete the following steps:
3. Installing a 3.5-inch hot-swap drive:
Figure 112. Hot-swap hard disk drive installation (3.5-inch)
a.
b.
c.
d.
e.
f.
Remove the filler panel from the empty drive bay.

Make sure that the drive-tray handle is in the open (unlocked) position.
Align the drive assembly with the guide rails in the bay.
Gently push the drive assembly into the drive bay until the drive stops.
Rotate the drive-tray handle to the closed (locked) position.
Skip to step 5.
4. Installing a 2.5-inch hot-swap drive:
211
Figure 113. Hot-swap hard disk drive installation (2.5-inch)
a.
b.
c.
d.
e.
Remove the filler panel from the empty drive bay.

Make sure that the drive-tray handle is in the open (unlocked) position.
Align the drive assembly with the guide rails in the bay.
Gently push the drive assembly into the drive bay until the drive stops.
Rotate the drive-tray handle to the closed (locked) position.
5. Check the drive status LED to verify that the drive is operating correctly. If the
yellow drive status LED for a drive is lit continuously, that drive is faulty and
must be replaced. If the green drive activity LED is flashing, the drive is being
accessed.
6. If you are installing additional hot-swap drives, do so now.
page 26.
For information on the supported combination of drive backplane configurations,
see Supported SAS/SATA drive backplane configurations.
IDs for hot-swap drives

The drive ID that is assigned to each drive is printed on the front of the server.
The following illustrations show the locations of the IDs of the drives. The ID
numbers and the drive bay numbers are the same.
model.
model.
212
Removing a simple-swap SATA drive

Use this information to remove a simple-swap hard disk drive.
To remove a simple-swap SATA drive, complete the following steps:
3. Remove the filler panel from the front of the server.
4. Press the release latch and pull the drive out of the bay.
Figure 116. 3.5-inch simple-swap hard disk drive removal
Figure 117. 2.5-inch simple-swap hard disk drive removal
5. If you are instructed to return the drive, follow all packaging instructions, and
213
Replacing a simple-swap SATA drive

Use this information to Replacing a simple-swap hard disk drive.
Note: You must turn off the server before installing simple-swap drives in the
server.
To install a simple-swap SATA drive, complete the following steps:
2. Touch the static-protective package that contains the new drive to any
unpainted metal surface on the server; then, remove the drive from the package
and place it on a static-protective surface.
3. Gently push the drive assembly into the drive bay until the drive clicks into
place.
4. Reinstall the filler panel that you removed

214
Removing a CD/DVD drive

Use this information to remove a DVD drive.
To remove a CD/DVD drive, complete the following steps:
the tab, push the CD/DVD drive toward the front of the server.
Figure 120. DVD drive removal
5. Remove the CD/DVD drive out of the bay and slide the drive-retention clip
from the side of the drive. Save the clip to use when you install the
replacement drive.
215
Figure 121. DVD drive retention clip removal
6. If you are instructed to return the CD/DVD drive, follow all packaging
you.
Installing an optional CD/DVD drive

Use this information to install a DVD drive.
To install an optional CD/DVD drive, complete the following steps:
the tab, push the CD/DVD filler toward the front of the server.
216
Figure 122. DVD drive filler panel removal
Figure 123. DVD drive installation
5. Pull the CD/DVD drive filler out of the front of the server.
6. Remove the retention clip from the side of the drive filler.
217
Note: If you are installing a drive that contains a laser, observe the following
safety precaution.
Statement 3
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices,
or transmitters) are installed, note the following:
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.

Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
7. Touch the static-protective package that contains the new optical drive to any
unpainted metal surface on the server; then, remove the optical drive from the
package and place it on a static-protective surface.
8. Attach the drive retention clip that you removed from the previous drive to
the side of the new drive.
218
Figure 124. DVD drive retention clip installation
9. Align the drive in the drive bay and slide the drive into the CD/DVD drive
bay until the drive clicks into place.
Removing the CD/DVD cable

Use this information to remove a CD/DVD cable.
To remove the CD/DVD cable, complete the following steps:
5. Remove the CD/DVD drive (see Removing a CD/DVD drive on page 215).
6. From the front of the server, grasp the cable connector latch and pull it up
toward the rear of the server; then, slide the cable connector to the unlock
position.
Figure 125. CD/DVD drive cable removing
7. Remove the cable from the optical drive cage connector.

8. Disconnect the other end of the CD/DVD cable from the connector on the
system board.
219
9. Disengage the cable clips and remove the CD/DVD cable from the server.
10. If you are instructed to return the CD/DVD cable, follow all packaging
instructions, and use any packaging materials for shipping that are supplied
to you.
Replacing the CD/DVD cable

Use this information to install a CD/DVD cable.
To install the CD/DVD cable, complete the following cable:
2. Align the cable connector with the connector on the rear of the optical drive
cage and press the cable connector into the optical drive cage connector.
3. From the front of the server, grasp the cable connector latch and pull it up
toward the rear of the server; then, slide the cable connector to the lock
position.
DVD drive
cable
Cable connector latch
Figure 126. CD/DVD drive cable installation
4. Connect the other end of the CD/DVD drive cable to the connector on the
system board. Secure the cable with the cable clips on the chassis.
5. Reinstall the CD/DVD drive (see Installing an optional CD/DVD drive on
page 216).
6. Install the air baffle (see Replacing the DIMM air baffle).
7. Replace the cover (see Replacing the server top cover on page 80).
220
Removing a fan
Use this information to remove a fan in the server.
Attention:
seconds.
To ensure proper server operation, replace a failed fan within 30
To remove a fan, complete the following steps:

4. Reconnect the power cord; then, turn on the server.
Attention: Operating the server for extended periods of time (more than 30
minutes) with the top cover removed might damage server components.
5. Determine which fan to replace by checking the LEDs on the system board
(see System-board LEDs on page 30); a lit LED indicates the fan to replace.
6.
7.
8.
9.
Turn off the server; then, disconnect the power cord again.
Remove the air baffle (see Removing the air baffle on page 205).
Disconnect the fan power cable from the connector on the system board.
Grasp the top of the fan with your index finger and thumb and lift the fan out
of the server.
Figure 127. Fan removal
Attention: To ensure proper operation, replace a failed hot-swap fan within

30 seconds.
10. If you are instructed to return the fan, follow all of the packaging instructions,
221
Replacing a fan
Use this information to replace a fan in the server.
The server comes standard with four speed-controlled cooling fans. You must
install the fifth and sixth fan when you install the second microprocessor.
Attention:
To ensure proper operation, replace a failed fan within 30 seconds.
To install or replace a fan, complete the following steps:

3. Touch the static-protective package that contains the new fan to any
unpainted metal surface on the server. Then, remove the new fan from the
package.
4. Orient the fan so that the air-flow arrow points to the rear of the server.
Figure 128. Fan installing
5. Lower the fan into the fan slot in the server and ensure that is it seated
correctly.
6. Connect the fan power cable to the connector on the system board.
222
Removing a memory module

Use this information to remove a memory module.
To remove a dual inline memory module (DIMM), complete the following steps:
5. Carefully open the retaining clips on each end of the DIMM connector and
remove the DIMM.
Figure 129. DIMM removal
6. If you are instructed to return the DIMM, follow all packaging instructions, and
223
Replacing a memory module

The following notes describe the types of DIMMs that the server supports and
other information that you must consider when you install DIMMs.
Notes:
v See Installing a memory module on page 38 for notes and information that
you must consider when you install DIMMs.
v Confirm that the server supports the DIMM that you are installing, see
The following illustration shows the location of the DIMM connectors on the
system board.
Figure 130. DIMM connectors location
To install a DIMM, complete the following steps:

4. Touch the static-protective package that contains the DIMM to any unpainted
metal surface on the outside of the server. Then, remove the DIMM from the
package.
5. Open the retaining clip on each end of the DIMM connector.
224

Figure 131. DIMM installation
6. Turn the DIMM so that the DIMM keys align correctly with the connector.
7. Insert the DIMM into the connector by aligning the edges of the DIMM with
the slots at the ends of the DIMM connector (see System-board optional
device connectors on page 31 for the locations of the DIMM connectors).
8. Firmly press the DIMM straight down into the connector by applying pressure
on both ends of the DIMM simultaneously. The retaining clips snap into the
locked position when the DIMM is firmly seated in the connector.
Note: If there is a gap between the DIMM and the retaining clips, the DIMM
has not been correctly inserted; open the retaining clips, remove the DIMM,
and then reinsert it.
11. Replace the cover (see Replacing the server top cover).
Removing an IBM ServeRAID Controller

Use this information to remove an optional ServeRAID Controller.
To remove an IBM ServeRAID adapter, complete the following steps:
Note: When the ServeRAID adapter is removed, software RAID will not be
supported. This system does not support downgrade software RAID function from
hardware RAID configuration.
4. Remove PCI riser-card assembly 2 (see Removing a PCI riser-card assembly
on page 251).
5. Disconnect the cables to the ServeRAID adapter.
225
6. Pull the release pin to unlock the retention latch; then rotate the retention latch
to the open position.
7. Carefully grasp the ServeRAID adapter by the edge and pull it out of the PCI
riser-card assembly.
Figure 132. ServeRAID adapter removal
8. If you are instructed to return the adapter, follow all packaging instructions,
Replacing an optional IBM ServeRAID Controller

Use this information to Replace an optional ServeRAID Controller.
You can purchase an optional IBM ServeRAID SAS/SATA controller that provides
additional RAID feature support. For configuration information, see the ServeRAID
documentation at http://www.ibm.com/support/mysupport/.
Attention: Some cluster solutions require specific code levels or coordinated code
Notes:
v You must install a ServeRAID adapter on PCI riser-card assembly 2.
v When you install an IBM ServeRAID adapter that has a RAID adapter battery in
the server, you must install the battery remotely in the remote battery tray (see
Installing a RAID adapter battery remotely in the server on page 71).
To install an IBM ServeRAID adapter, complete the following steps:
2. Touch the static-protective package that contains the new ServeRAID adapter
to any unpainted surface on the outside of the server; then, grasp the adapter
by the top edge or upper corners of the adapter and remove it from the
package.
3. Align the ServeRAID adapter so that the keys align correctly with the
connector on the PCI riser-card assembly.
226
4. Insert the ServeRAID adapter into the connector on the riser-card until it is
firmly seated.
Attention: Incomplete insertion might cause damage to the server or the
adapter.
PCI slot 3
Riser-card
assembly 2
Adapter
Figure 133. ServeRAID adapter installation
5. Rotate the retention latch to the closed position, making sure the retention
latch engages the ServeRAID adapter. Then, push in the release pin to lock the
6. Reconnect cables to the adapter. Be sure to route the signal cables as shown in
the following illustration. Secure the cables with any cable clips on the system
board so that they do not get in the way or get damaged.
7. Reinstall the PCI riser-card assembly (see Replacing a PCI riser-card
assembly on page 79).
Removing a remotely installed RAID adapter battery

Use this information to remove a RAID adapter battery remotely in the server.
To remove the RAID adapter battery from the RAID battery tray, complete the
following steps:
on page 251).
5. From the top of safety cover, press the release latch to open the battery tray
cover and press the release tab to open the retention clip that holds the battery
in place.
227
Figure 134. RAID adapter battery removal
6. Lift the battery from the RAID battery tray.

7. Disconnect the remote battery cable from the remote battery cable connector to
the ServeRAID adapter.
If you are instructed to return the RAID adapter battery, follow all packaging
you.
Replacing a RAID adapter battery remotely in the server

Use this information to install a RAID adapter battery remotely in the server.
When you install any ServeRAID adapter in the server that come with a RAID
adapter battery, the battery must be installed remotely to prevent the battery from
overheating. The battery must be installed only in the RAID battery tray on top of
the power safety cover.
To install the RAID adapter battery in the RAID battery tray, complete the
following steps:
2. Install the battery in the RAID battery tray:
Note: You should always install the first RAID battery (marked as 1 in the
graphic) on the RAID battery tray.
228
Figure 135. RAID adapter battery installation
a. Orient the battery as shown in the following illustration; then, lower the
battery into the RAID battery tray. If the battery comes with a battery
carrier, ensure that battery carrier posts align with the rings on the battery
mounting slot so that the battery carrier is secure in the slot.
Note: The positioning of the remote battery depends on the type of remote
battery that you install.
b. Rotate the retention clip to the close position and press down on the battery
tray cover until it snaps in place to hold the battery in place.
3. Connect the remote battery cable to the remote battery cable connector to the
ServeRAID adapter. Route the remote battery cable in the server as shown in
the following illustration.
4.
5.
6.
7.
Reinstall the PCI riser-card assembly (see Replacing a PCI riser-card assembly
on page 79).
Replace the cover (see Replacing the server top cover on page 80).
Reconnect the power cord and any cables that you removed.
Turn on the peripheral devices and the server.
Removing a USB embedded hypervisor flash device

Use this information to remove a USB embedded hypervisor flash device.
To remove a hypervisor flash device, complete the following steps:
on page 251).
5. Locate the USB embedded hypervisor flash device connector on the system
board.
229
Figure 136. Location of USB hypervisor flash device connector
6. Slide the lockbar on the flash device connector to the unlocked position and
pull the USB flash device out of the connector.
230
Lockbar
USB Hypervisor
key
Figure 137. USB hypervisor flash device removal
7. If you are instructed to return the flash device, follow all packaging
you.
Replacing a USB embedded hypervisor flash device

Use this information to install a USB embedded hypervisor flash device.
To install a hypervisor flash device, complete the following steps:
2. Align the USB flash device with the connector on the system board and push it
into the connector until it is firmly seated.
3. Slide the lockbar toward the riser-card assembly to the locked position until it
is seated firmly.
231
Lockbar
USB Hypervisor
key
Figure 138. USB hypervisor flash device installation
5. Install PCI riser-card assembly 1 (see Replacing a PCI riser-card assembly on
page 252).
Removing a hot-swap power supply

Use this information to remove a hot-swap power supply.
When you remove or install a hot-swap power supply, observe the following
precautions.
Statement 5
CAUTION:
232
2
1
Statement 8
CAUTION:
label attached.
technician.
To remove a hot-swap power supply, complete the following steps:
2. If only one power supply is installed, turn off the server and peripheral devices
and disconnect all power cords.
3. If the server is in a rack, at the back of the server, pull back the cable
management arm to gain access to the rear of the server and the power supply.
4. Press and hold the orange release tab to the left. Grasp the handle and pull the
power supply out of the server.
233
Figure 139. Power supply removal
5. If you are instructed to return the power supply, follow all packaging
you.
Replacing a hot-swap power supply

Use this information to install a hot-swap power supply.
v To confirm that the server supports the power supply that you are installing, see
v The server comes standard with one of the following power supplies that
connects to power supply bay 1. The input voltage is 100-127 V ac or 200-240 V
ac auto-sensing.
460-watt non-hot-swap power supply
460-watt hot-swap power supply
675-watt high-efficiency, hot-swap power supply
Note: You cannot mix 110 V ac and 220 V ac, or 460-watt and 675-watt power
supplies in the server, it is not supported.
v The server supports a maximum of two hot-swap power supplies. These power
supplies are designed for parallel operation. In the event of a power-supply
failure, the redundant power supply continues to power the system.
v The server can run fully configured with one power supply. For redundancy
support, you must install the second hot-swap power supply.
234
Statement 5
CAUTION:
2
1
Statement 8
CAUTION:
label attached.
technician.
To install a hot-swap power supply, complete the following steps:
2. Touch the static-protective package that contains the hot-swap power supply to
any unpainted metal surface on the server; then, remove the power supply
power-supply filler panel from the power-supply bay.
235
4. Grasp the handle on the rear of the power supply and slide the power supply
forward into the power-supply bay until it clicks. Make sure that the power
supply connects firmly into the power-supply connector.
5. Route the power cord through the cable retainer clip so that it does not
accidentally become disconnected
6. Connect the power cord for the new power supply to the power-cord connector
on the power supply.
outlet.
8. Make sure that the ac power LED and the dc power LED on the power supply
are lit, indicating that the power supply is operating correctly. The two green
LEDs are to the right of the power-cord connector.
Removing a hot-swap dc power supply

Use this information to remove a hot-swap dc power supply.
When you remove or install a hot-swap dc power supply, observe the following
precautions.
Statement 29
CAUTION: This equipment is designed to permit the connection of the earthed

conductor of the dc supply circuit to the earthing conductor at the equipment.
236
equipment.
conductor.
Statement 31
DANGER
hazardous.
structural damage.
To Connect:
To Disconnect:

product.

product.



connectors.
Statement 33
237
CAUTION:
removing power modules and I/O modules does not turn off electrical current
to the product. The product also might have more than one power cord. To
remove all electrical current from the product, make sure that all power cords
are disconnected from the power source.
OFF
Statement 34
CAUTION:
field wiring.
238
To remove a hot-swap dc power supply, complete the following steps:

2. If only one power supply is installed, turn off the server and peripheral
devices and disconnect all power cords.
3. If the server is in a rack, at the back of the server, pull back the cable
management arm to gain access to the rear of the server and the power
supply.
4. Press and hold the release tab to the left. Grasp the handle and pull the
power supply out of the server.
Figure 141. Power supply removal
to you.
239
Replacing a hot-swap dc power supply

Use this information to install a hot-swap dc power supply.
v The server comes with one hot-swap 12-volt output power supply that connects
to power supply bay 1. The input voltage is -48 V dc or -60 V dc auto-sensing.
v Before you install a dc power supply in the server, you must remove all ac
power supplies. Do not use both ac and dc power supplies in the same server.
Install up to two dc power supplies or up to two ac power supplies, but not a
combination.
v You can order an optional power supply for redundancy.
v These power supplies are designed for parallel operation. In the event of a
power-supply failure, the redundant power supply continues to power the
system. The server supports a maximum of two power supplies.
v It is the customer's responsibility to supply the necessary power cable.
Use a circuit breaker that is rated at 25 amps.
Use 2.5 mm2 (12 AWG) at 90 C copper wire.
Torque the wiring-terminal screws to 0.50 ~ 0.60 newton-meters (4.43 ~ 5.31
inch-pounds).
For more information, see Statement 34.
v If the power source requires ring terminals, you must use a crimping tool to
UL approved and must accommodate the wire that is described in the
above-mentioned note .
Statement 29:
CAUTION:
the dc supply circuit to the earthing conductor at the equipment.
240
equipment.
conductor.
Statement 31
DANGER
hazardous.
structural damage.
To Connect:
To Disconnect:

product.

product.



connectors.
Statement 33
241
CAUTION:
removing power modules and I/O modules does not turn off electrical current
to the product. The product also might have more than one power cord. To
remove all electrical current from the product, make sure that all power cords
are disconnected from the power source.
OFF
Statement 34
CAUTION:
field wiring.
242
To install a hot-swap dc power supply, complete the following steps:

Attention: Only trained service personnel other than IBM service technicians are
authorized to install and remove the -48 volt dc power supply, and make the
connections to and disconnections from the -48 volt dc power source. IBM service
technicians are not certified or authorized to install or remove the -48 volt power
cable. The customer is responsible for ensuring that only trained service
personnel install or remove the -48 volt power cable.
to any unpainted metal surface on the server; then, remove the power
supply from the package and place it on a static-protective surface.
3. Turn off the circuit breaker for the dc power source to which the new power
supply will be connected. Disconnect the power cord from the dc power
source.
4. Attach the dc power cable to the new power supply. Make sure the wires are
connected securely to the -48V, ground, and -48V return terminals.
Power input LED
Power output LED
Power error LED
-48V return
Ground
-48V
Figure 142. DC power supply rear view
power-supply filler from the power-supply bay.
243
6. Grasp the handle on the rear of the power supply and slide the power
supply forward into the power-supply bay until it clicks. Make sure that the
power supply connects firmly into the power-supply connector.
7. Route the power cord through the handle and cable tie if any, so that it does
not accidentally become unplugged.
8. Connect the other ends of the dc power cable to the dc power source. Cut
the wires to the correct length, but do not cut them shorter than 150 mm (6
inch). If the power source requires ring terminals, you must use a crimping
tool to install the ring terminals to the power cord wires. The ring terminals
must be UL approved and must accommodate the wires that are described
in note. The minimum nominal thread diameter of a pillar or stud type of
terminal must be 4 mm; for a screw type of terminal the diameter must be
5.0 mm.
9. Turn on the circuit breaker for the dc power source to which the new power
supply is connected.
10. Make sure that the green power LEDs on the power supply are lit, indicating
that the power supply is operating correctly.
correctly.
244
power supplies.
Removing the fixed power supply

Use this information to remove the fixed power supply.
Note: You must turn off the server before removing or replacing the fixed power
supply.
When you remove or install a power supply, observe the following precautions.
Statement 5
CAUTION:
2
1
Statement 8
245
CAUTION:
label attached.
technician.
To remove the fixed power supply, complete the following steps:
4. Disconnect the power-supply cables from the connectors on the system board
and internal devices; then, disengage the cables from any cable clips.
Note: Note the routing of all power-supply cables; you will route the
power-supply cables the same way when you install the power supply.
5. Remove the screw that holds the power supply to the rear of the chassis; then,
slide the power supply slightly toward the front of the server and lift to
remove it from the server.
246
Figure 146. Fixed power supply removal
you.
Replacing the fixed power supply

Use this information to install the fixed power supply.
Note: You must turn off the server before removing or replacing the fixed power
supply.
Statement 5
CAUTION:
247
2
1
Statement 8
CAUTION:
label attached.
technician.
To install a fixed power supply, complete the following steps:
2. Touch the static-protective package that contains the power supply to any
unpainted metal surface on the server; then, remove the power supply from
the package and place it on a static-protective surface.
3. Orient the power supply as shown in the following illustration and align the
retention tabs on the side of the power supply with the slots on the chassis.
4. Install the rear bracket.
248
Figure 147. Rear bracket installation
5. Lower the power supply and slide the retention tabs into the slots. Make sure
all retention tabs are engaged in the slots.
Figure 148. Fixed power supply installation
6. Install the screw and the filler to secure the power supply in the chassis.
249
Figure 149. Screw and filler installation
7. Connect the power cables to the power supply.

9. Route the power cord through the cable retainer clip so that it does not
accidentally become disconnected.
10. Connect the power cord for the new power supply to the power-cord
connector on the power supply.
outlet.
12. Make sure that the ac power LED and the dc power LED on the power
supply are lit, indicating that the power supply is operating correctly.
250
Removing a PCI riser-card assembly

Use this information to remove a PCI riser-card assembly.
To remove a PCI riser-card assembly, complete the following steps:
4. If an adapter is installed in the PCI riser-card assembly, disconnect any cables
that are connected to the adapter.
5. Grasp the front and rear of the PCI riser-card assembly at the blue touch-points
and lift it out of the PCI riser connector on the system board.
PCI riser-card
assembly 2 (one
internal RAID
adapter)
PCI riser-card
PCI riser 1
PCI riser 2
Figure 150. PCI riser-card assembly removal
6. Remove the adapter, if necessary, from the PCI riser-card assembly (see
Removing an adapter on page 207).
7. Set the adapter and PCI riser-card assembly aside.
8. If you are instructed to return the PCI riser-card assembly, follow all packaging
you.
251
Replacing a PCI riser-card assembly

Use this information to install a PCI riser-card assembly.
To replace a PCI riser-card assembly, complete the following steps:
2. Install the adapter in the new PCI riser-card assembly (see Replacing an
adapter on page 209).
3. Set any jumpers or switches on the adapter as directed by the adapter
manufacturer.
4. Align the PCI riser-card assembly with the PCI riser connector on the system
board; then, press down firmly until the PCI riser-card assembly is seated
correctly in the connector on the system board.
PCI riser-card
assembly 2 (one
internal RAID
adapter)
PCI riser-card
PCI riser 1
PCI riser 2
6. Reconnect the external cables; then, reconnect the power cords and turn on the
peripheral devices and the server.
252
Removing the operator information panel assembly

Use the information to remove the operator information panel assembly.
To remove the operator information panel, complete the following steps.
4. Disconnect the cable from the back of the operator information panel assembly.
5. Push the blue points on the rear of the operator information panel to the front
of the server.
panel
Figure 152. Operator information panel assembly removal
6. From the front of the server, carefully pull the assembly out of the server.
7. If you are instructed to return the operator information panel assembly, follow
all packaging instructions, and use any packaging materials for shipping that
are supplied to you.
253
Replacing the operator information panel assembly

Use the information to replace the operator information panel assembly.
To install the operator information panel, complete the following steps.
2. From the front of the server, slide the operator information panel into the
server until it stops.
Figure 153. Operator information panel assembly installation
panel
3. Connect the signal cable to the rear of the operator information panel; then,
connect the other end of the signal cable to the connectors on the system board.
Route the signal cable as shown in the following illustration. Secure the cable
with any cable clips on the chassis.
Figure 154. Signal cable installation
254
5. Inside the server, connect the cable to the rear of the operator information panel
assembly.
6. Reinstall the air baffle (see Replacing the air baffle on page 78).
Removing the system battery

Use this information to remove the system battery.
The following notes describe information that you must consider when replacing
the battery:
v IBM has designed this product with your safety in mind. The lithium battery
must be handled correctly to avoid possible danger. If you replace the battery,
you must adhere to the following instructions.
Note: In the U. S., call 1-800-IBM-4333 for information about battery disposal.
v If you replace the original lithium battery with a heavy-metal battery or a
battery with heavy-metal components, be aware of the following environmental
consideration. Batteries and accumulators that contain heavy metals must not be
disposed of with normal domestic waste. They will be taken back free of charge
by the manufacturer, distributor, or representative, to be recycled or disposed of
in a proper manner.
v To order replacement batteries, call 1-800-IBM-SERV within the United States,
and 1-800-465-7999 or 1-800-465-6666 within Canada. Outside the U.S. and
Canada, call your support center or business partner.
Note: After you replace the battery, you must reconfigure the server and reset
the system date and time.
Statement 2
CAUTION:
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:
Throw or immerse into water
Heat to more than 100C (212F)
Repair or disassemble
To remove the system-board battery, complete the following steps:
255
Figure 155. Location of system battery
4. Remove PCI riser-card assembly 1 from the server. (see Removing a PCI
5. Remove the system-board battery:
a. Use one finger to push the battery horizontally out of its housing.
Figure 156. System battery removal
b. Use your thumb and index finger to lift the battery from the socket.
256
6. Dispose of the battery as required by local ordinances or regulations. See the

IBM Environmental Notices and User's Guide on the IBM Documentation CD for
more information.
Replacing the system battery

Use this information to install the system battery.
The following notes describe information that you must consider when replacing
the system-board battery in the server.
v When replacing the system-board battery, you must replace it with a lithium
battery of the same type from the same manufacturer.
v To order replacement batteries, call 1-800-426-7378 within the United States, and
1-800-465-7999 or 1-800-465-6666 within Canada. Outside the U.S. and Canada,
call your IBM marketing representative or authorized reseller.
v After you replace the system-board battery, you must reconfigure the server and
reset the system date and time.
v To avoid possible danger, read and follow the following safety statement.
Statement 2
CAUTION:
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 100C (212F)
v Repair or disassemble
To install the replacement system-board battery, complete the following steps:
257
Figure 157. Location of system battery
1. Follow any special handling and installation instructions that come with the
replacement battery.
2. Insert the new battery:
a. Position the battery so that the positive (+) symbol is facing you.
Figure 158. System battery installation
b. Place the battery into its socket, and press the battery press the battery
toward the housing until it clicks into place. Make sure that the battery clip
holds the battery securely.
3. Install PCI riser-card assembly 1 (see Replacing a PCI riser-card assembly on
page 252).
5. Reconnect the external cables; then, reconnect the power cords and turn on the
peripheral devices and the server.
258
Note: You must wait approximately 1 to 3 minutes after you connect the server
to a power source before the power-control button becomes active.
6. Start the Setup utility and reset the configuration.
v Set the system date and time.
v Set the power-on password.
v Reconfigure the server.
See Using the Setup utility on page 88 for details.
Removing the front USB connector board

Use this information to remove the front USB connector board.
To remove the front USB connector board, complete the following steps:
4. Disconnect the USB cable from the connector on the rear of the USB assembly.
5. (For 2.5-inch hard disk drive models) Press the release tab and push the USB
assembly toward the rear of the server.
Release tab
Front USB assembly
Figure 159. Front USB connector board removal (for 2.5-inch HDD models)
6. (For 3.5-inch hard disk drive models) Press the release tab and push the USB
assembly toward the front of the server.
259
Release tab
Front USB assembly
Figure 160. Front USB connector board removal (for 3.5-inch HDD models)
7. Remove the two screws from the USB assembly and rotate the front USB
connector board out of the USB assembly.
Front USB
connector board
Figure 161. USB assembly screws removal
8. If you are instructed to return the front USB connector board, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
260
Replacing the front USB connector board

Use this information to replace the front USB connector board.
To replace the front USB connector board, complete the following steps:
2. Orient the USB connector board as shown in the illustration; then, align the
screw holes on the USB connector board with the screw holes on the USB
assembly.
Front USB
connector board
Figure 162. USB assembly screws installation
3. Install the screws to secure the USB connector board to the USB assembly.
4. From the front of the server, slide the USB assembly into the USB slot until it
clicks into place.
261
Figure 163. USB assembly installation
5. Connect one end of the USB cable to the connector on the USB connector
board; then, connect the other end of the USB cable to the connector on the
system board. Route the USB cable as shown in the following illustration.
6. Align the front video connector (if available) with the slot on the server and
install the two screws to secure it to the server.
7. Connect the video/USB cable to the connector on the system board.
8. Secure the USB cable with any cable clips in the server.
Removing the front video connector

Use this information to remove the front video connector.
To remove the front video connector, complete the following steps:
4. On a 3.5-inch server model, remove the front bezel (see Removing the bezel
on page 204).
5. Loosen the screws that secure the video connector to the front of the chassis.
2.5-inch hard disk drive model
Figure 164. Loosen video connector screws
262
6. Disconnect the video cable from the connector on the system board and
disengage the video cable from any cable clips on the chassis.
7. Remove the video connector and cable from the server.
Figure 165. Front video connector removal
8. If you are instructed to return the video connector, follow all packaging
you.
Replacing the front video connector

Use this information to replace the front video connector.
To replace the front video connector board, complete the following steps:
2. Align the video connector with the slot on the server and install the two screws
to secure it to the server.
Note: Refer to the illustrations below for 2.5-inch and 3.5-inch hard disk drive
bays models respectively. Depending on your server model, align the video
263
connector from inside or outside the server.

Figure 166. Video connector alignment
Video cable
264
3. Connect the video cable to the connector on the system board. Route the cable
as shown in the following illustration. Secure the cable with any cable clips on
the chassis.
4. Reinstall the cover (see Replacing the server top cover on page 80).
Removing the power interposer card assembly

Use this information to remove the power interposer card assembly.
To remove the power interposer card assembly, complete the following steps:
5. If a ServeRAID adapter is installed in PCI riser-card assembly 2, remove PCI
riser-card assembly 2 (see Removing a PCI riser-card assembly on page 251).
6. Remove the redundant power supply slightly out of the server to disconnect it
from the power interposer card.
7. Disconnect all power cables from the connectors on the system board.
Disengage the power cables from any cable clips.
8. If a RAID adapter battery is installed on the safety cover, disconnect the
power cable from the ServeRAID adapter.
9. Loosen the screws and remove the safety cover from the top of the power
interposer card.
10. Remove the screws that secure the power interposer card to the chassis.
11. Disconnect the power cable from the power interposer card; then, remove the
power interposer card out of the server.
265
Figure 167. Power interposer card assembly removal
Figure 168. Power interposer card assembly removal (with advanced remote battery holder)
12. If you are instructed to return the power interposer card, follow all of the
packaging instructions, and use any packaging materials for shipping that are
supplied to you.
266
Replacing the power interposer card assembly

Use this information to replace the power interposer card assembly.
To install the power interposer card assembly, complete the following steps:
2. Reconnect the power cable to the power interposer card.
3. Align the screw holes on the power interposer card with the screw holes on
the chassis; then, install the screws to secure the power interposer card to the
chassis.
Figure 169. Power interposer card assembly installation
267
Figure 170. Power interposer card assembly installation (with advanced remote battery
holder)
4. Orient the safety cover as shown in the above illustration and align the screws
with the screw holes on the power interposer card. Tighten the screws to
secure the safety cover on the power interposer card.
5. Reconnect the power cables to the connectors on the system board and secure
the power cables with any cable clips on the chassis.
6. Reconnect the power cable from the RAID battery on the safety cover to the
ServeRAID adapter, if you have removed it.
7. Reinstall PCI riser-card assembly 2, if you removed it (see Replacing a PCI
268
Removing the hot-swap drive backplane

Use this information to remove the hot-swap drive backplane.
To remove the 2.5-inch hot-swap drive backplane, complete the following steps:
4. Pull the drives and filler panels out of the server slightly to disengage them
from the drive backplane.
5. Disconnect the configuration, power, and SAS signal cables from the backplane.
Note: You can also choose to disconnect the cables after removing the
backplane, if that is easier for you.
6. Lift the backplane up slightly and pull it out the server.
Figure 171. Hot-swap drive backplane removal
7. If you are instructed to return the drive backplane, follow all packaging
you.
Replacing the hot-swap drive backplane

Use this information to install the hot-swap drive backplane.
To install the replacement hot-swap drive backplane, complete the following steps:
2. Align the sides of the drive backplane with the guide rails and lower the drive
backplane into the server.
Note: You can reconnect the cables to the drive backplane before installing the
backplane onto the cage or you can connect the cables after you install the
backplane, if that is easier for you.
269
Guide channels
Figure 172. Hot-swap drive backplane installation
3. Reconnect the configuration, power, and SAS signal cables to the connectors on
the backplane. Route the cables as shown in the following illustration.
4. Reinstall the drives and filler panels.
Removing the simple-swap SATA drive backplate assembly

Use this information to remove the simple-swap drive SATA drive backplate
assembly.
To remove the simple-swap SATA drive backplate assembly, complete the
following steps:
4. Pull the drive and filler panels out of the server slightly to disengage them
from the backplate assembly.
5. Disconnect the cables. Note the routing
a. Disconnect the signal cable from the connector on the system board.
b. Disconnect the power cable from the power supply or the power interposer
card.
6. Pull the retention latch on top of the drive backplane cage and lift the
backplate assembly up slightly and pull it out; then, rotate it backward out of
the tabs at the bottom of the drive cage and remove the backplate assembly
from the server.
270
Retention latch
Lock
Unlock
Figure 173. Simple-swap SATA drive backplate assembly removal
7. If you are instructed to return the backplate assembly, follow all packaging
you.
Replacing the simple-swap SATA drive backplate assembly

Use this information to replace the simple-swap drive SATA drive backplate
assembly.
To install the replacement simple-swap SATA drive and backplate assembly,
Note: The simple-swap SATA drive and backplate assembly must be installed in
the backplane slot closest to the information panel and the SATA drive must be
installed in the drive-bay closest to the information panel. The backplate assembly
cable connects to the CD/DVD-ROM drive connector on the system board.
2. Align the tabs on the bottom of the drive backplate with the backplate slots on
the bottom of the backplane cage.
271
Retention latch
Unlock
Lock
Figure 174. Simple-swap SATA drive backplate assembly installation
3. Insert the drive backplate tabs into the slots on the bottom of the backplate
cage and push down the retention latch on top of the drive cage; then, rotate
the drive backplate assembly forward until the backplate is latched.
4. Reinstall the drive and filler panel and plastic drive-bay spacer.
5. Install the cover (see Replacing the server top cover).
Removing and replacing Tier 2 CRUs

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.
272
Removing a microprocessor and heat sink

Use this information to remove a microprocessor and heat sink.
Attention:
v Do not allow the thermal grease on the microprocessor and heat sink to come in
contact with anything.
v Removing the heat sink from the microprocessor destroys the even distribution
of the thermal grease and requires replacing the thermal grease.
v Do not touch the microprocessor contacts; handle the microprocessor by the
edges only. Contaminants on the microprocessor contacts, such as oil from your
skin, can cause connection failures between the contacts and the socket.
v Use the microprocessor installation tool that came with the new microprocessor
to remove and install the microprocessor. Failure to use the microprocessor tool
may cause damage to the pins on the socket. Any damage to the pins may
require replacing the system board.
To remove a microprocessor and heat sink, complete the following steps:
4. Disconnect any cables that impede access to the heat sink and microprocessor.
6. If you are removing microprocessor 1, remove the memory module from
DIMM connector 5. If you are removing microprocessor 2, remove the
memory module from DIMM connector 12. See Removing a memory
module on page 223 for instructions.
7. Loosen the screws on the heat sink with a screwdriver, alternating among the
screws until they are loose. If possible, each screw should be rotated two full
rotations at a time.
8. Gently pull the heat sink off the microprocessor. Lift the heat sink out of the
server. If the heat sink sticks to the microprocessor, slightly twist the heat sink
back and forth to break the seal. After removal, place the heat sink on its side
on a clean, flat surface.
Note: Removing the heat sink from the microprocessor destroys the even
distribution of the thermal grease and requires replacing the thermal grease.
273
Figure 175. Heat sink removal
9. Release the microprocessor retention latch by pressing down on the end,

moving it to the side, and releasing it to the open (up) position.
10. Open the microprocessor bracket frame by lifting up the tab on the top edge.
Keep the bracket frame in the open position.
Microprocessor
release lever
Microprocessor
bracket frame
Figure 176. Open the microprocessor bracket frame
11. Align the holes on the microprocessor installation tool with the screws on the
microprocessor bracket, then place the microprocessor installation tool down
over the microprocessor 1. Twist the handle clockwise 2 to attach the tool
to the microprocessor.
Note: You can pick up or release the microprocessor by twisting the
microprocessor installation tool handle.
Handle
Installation tool
Figure 177. Microprocessor tool attachment
12. Carefully lift the microprocessor straight up and out of the socket, and place it
on a static-protective surface. Remove the microprocessor from the installation
tool by twisting the handle counterclockwise.
Attention: Do not touch the pins on the socket. The pins are fragile. Any
damage to the pins may require replacing the system board.
274
Installation tool
Alignment pins
Microprocessor
Figure 178. Microprocessor removal
13. If you are instructed to return the microprocessor, follow all packaging
to you. Do not return the microprocessor installation tool.
Replacing a microprocessor and heat sink

Use this information to install a microprocessor and heat sink.
Attention: When you handle static-sensitive devices, take precautions to avoid
damage from static electricity. For details about handling these devices, see
Handling static-sensitive devices on page 36.
Notes:
v If your server comes with one Intel Pentium 1400 series microprocessor, the
second microprocessor socket is not used. The server supports only one Intel
Pentium microprocessor. If you plan to install two Intel Xeon microprocessors in
the server, you must first remove the Intel Pentium microprocessor that came
with the server.
v See Installing an additional microprocessor and heat sink on page 55 for notes
and other information that you must consider when you install a
microprocessor.
v Use the microprocessor installation tool that came with the new microprocessor
to remove the microprocessor from the server. Failure to use the microprocessor
tool may cause damage to the pins on the socket. Any damage to the pins may
require replacing the system board.
To install an additional microprocessor and heat sink, complete the following steps:
2. Remove the socket cover from the microprocessor socket, if it is installed.
275
Figure 179. Mmcroprocessor socket cover removal
3. If the microprocessor is preinstalled in the installation tool, release the sides of

the cover and remove the cover from the installation tool; then, continue to
step 5.
4. Install the microprocessor in the microprocessor installation tool:
a. Remove the static-protective bag, and the foam surrounding the bag, from
the box.
b. Touch the static-protective package that contains the new microprocessor
to any unpainted metal surface on the server; then, remove the
microprocessor from the package.
Attention:
v Do not touch the microprocessor contacts; handle the microprocessor by
the edges only. Contaminants on the microprocessor contacts, such as oil
from your skin, can cause connection failures between the contacts and
the socket.
v Handle the microprocessor carefully. Dropping the microprocessor
during installation or removal can damage the contacts.
v Do not use excessive force when you press the microprocessor into the
socket.
v Make sure that the microprocessor is oriented and aligned and
positioned in the socket before you try to close the lever.
c. If there is a plastic protective cover on the bottom of the microprocessor,
carefully remove it.
Protective
cover
Microprocessor
Figure 180. Plastic protective cover removal
276
d. Twist the handle of the microprocessor installation tool counterclockwise

so that it is in the open position.
e. Align the triangle alignment mark on the microprocessor with the triangle
alignment mark on the microprocessor installation tool, then place the
microprocessor on the bottom of the tool so that the tool can grasp the
microprocessor correctly onto the bottom of the installation tool.
f. Align the holes on the microprocessor installation tool with the screws on
the microprocessor bracket, then place the microprocessor installation tool
down over the microprocessor 1. Twist the handle clockwise 2 to attach
the tool to the microprocessor.
Microprocessor
Installation tool
Alignment
pin slots
Alignment
pins
Figure 181. Installation tool attachment
g. Twist the handle of the installation tool clockwise to secure the

microprocessor in the tool.
Note: You can pick up or release the microprocessor by twisting the
microprocessor installation tool handle clockwise.
5. Install the microprocessor:
a. Align the holes on the microprocessor installation tool with the screws on
the microprocessor bracket, then place the microprocessor installation tool
down over the microprocessor 1. Twist the handle clockwise 2 to
attach the tool to the microprocessor.
Note: The microprocessor fits only one way on the socket.
277
Installation tool
Microprocessor
Alignment pins
Figure 182. Installation tool alignment
b. Twist the handle on the microprocessor tool counterclockwise to insert the

microprocessor into the socket.
Handle
Installation tool
Figure 183. Microprocessor installation
Attention:
v Do not press the microprocessor into the socket.
v Do not touch exposed pins of the microprocessor socket. The pins on the
socket are fragile. Any damage to the pins may require replacing the
system board.
v Make sure that the microprocessor is oriented and aligned correctly in
the socket before you try to close the microprocessor retainer.
v Do not touch the thermal material on the bottom of the heat sink or on
top of the microprocessor. Touching the thermal material will
contaminate it and destroys its even distribution. If the thermal material
on the microprocessor or heat sink becomes contaminated, you must
replace the thermal grease.
Take off the microprocessor installation tool from the microprocessor
socket and close the microprocessor bracket frame.
d. Carefully close the microprocessor release lever to the closed position to
secure the microprocessor in the socket.
c.
6. Install the heat sink that comes with the microprocessor:
278
Attention:
v Do not set down the heat sink after you remove the plastic cover.
v Do not touch the thermal material on the bottom of the heat sink. Touching
the thermal material will contaminate it. If the thermal material on the
microprocessor or heat sink becomes contaminated, contact your service
technician.
a. Remove the plastic protective cover from the bottom of the heat sink.
Attention: Do not touch the thermal grease on the bottom of the heat
sink after you remove the plastic cover. Touching the thermal grease will
contaminate it. See Thermal grease for more information.
b. Align the screws on the heat sink with the screw holes on the system
board; then, place the heat sink on the microprocessor with the
thermal-grease side down.
Figure 184. Heat sink installation
c. Press firmly on the captive screws and tighten them with a screwdriver.
The follow illustration shows the sequence in tightening the screws, which
is also shown on top of the heat sink. Begin with the screw labeled as "1",
then "2", "3" and finally "4". If possible, each screw should be rotated two
full rotations at a time. Repeat until the screws are tight. Do not
overtighten the screws by using excessive force. If you are using a torque
wrench, tighten the screws to 8.5 Newton-meters (Nm) to 13 Nm (6.3
foot-pounds to 9.6 foot-pounds).
REPEAT SEQUENCE
UNTIL TIGHT.
Figure 185. Tighten the captive screws
279
7. If you installed the second microprocessor, install the two fans on Fan
connector 4 and Fan connector 6 of the system board respectively (see
Replacing a hot-swap fan assembly).
8. Reinstall the memory module that you have removed (see Replacing a
memory module on page 224).
10. Reconnect any cables that you have disconnected from the adapters or system
board.
Thermal grease
The thermal grease must be replaced whenever the heat sink has been removed
from the top of the microprocessor and is going to be reused or when debris is
found in the grease.
When you are installing the heat sink on the same microprocessor that is was
removed from, make sure that the following requirements are met:
v The thermal grease on the heat sink and microprocessor is not contaminated.
v Additional thermal grease is not added to the existing thermal grease on the
heat sink and microprocessor.
Note:
v Read the Safety information on page Safety on page vii.
v Read the Installation guidelines on page 34.
v Read Handling static-sensitive devices on page 36.
To replace damaged or contaminated thermal grease on the microprocessor and
heat sink, complete the following steps:
1. Place the heat sink on a clean work surface.
2. Remove the cleaning pad from its package and unfold it completely.
3. Use the cleaning pad to wipe the thermal grease from the bottom of the heat
sink.
Note: Make sure that all of the thermal grease is removed.
4. Use a clean area of the cleaning pad to wipe the thermal grease from the
microprocessor; then, dispose of the cleaning pad after all of the thermal grease
is removed.
0.02 mL of thermal
grease
Microprocessor
Figure 186. Thermal grease distribution
5. Use the thermal-grease syringe to place 9 uniformly spaced dots of 0.02 mL

each on the top of the microprocessor. The outermost dots must be within
approximately 5 mm of the edge of the microprocessor; this is to ensure
280
uniform distribution of the grease.
Figure 187. Syringe
Note: If the grease is properly applied, approximately half of the grease will
remain in the syringe.
6. Install the heat sink onto the microprocessor as described in Installing an
additional microprocessor and heat sink on page 55.
Removing the system board

Use this information to remove the system board.
Note:
1. Before you replace the system board, make sure that you backup any features
on demand (FoD) keys that were enabled. Remember to re-enable the features
on demand (FoD) keys after installing the new system board. For more
information on Features on Demand (FoD), including instructions for
ToolsCenter or IBM Systems Director, see the IBM Features on Demand User's
Guide at /http://www.ibm.com/systems/x/fod/ under the Help section.
2. When you replace the system board, you must either update the server with
the latest firmware or restore the pre-existing firmware from a diskette or CD
image. Make sure that you have the latest firmware or a copy of the
pre-existing firmware before you proceed.
Before you remove the system board from the server, take the following steps to
save data, firmware, and configuration data:
v Record all system configuration information, such as IMM IP addresses, vital
product data, and the machine type, model number, serial number, Universally
Unique Identifier, and asset tag of the server.
v Using the Advanced Settings Utility (ASU), save the system configuration to
external media.
v Save the system-event log to external media.
Note: When you replace the system board, you must either update the server
with the latest firmware or restore the pre-existing firmware that the customer
provides on a diskette or CD image. Make sure that you have the latest firmware
or a copy of the pre-existing firmware before you proceed.
To remove the system board, complete the following steps:
281
5. Remove all PCI riser-card assemblies with the adapters in them (see
Removing a PCI riser-card assembly on page 251).
6. Disconnect all cables from the system board. Make a list of each cable as you
disconnect it; you can then use this as a checklist when you install the new
system board.
Attention: Disengage all latches, release tabs or locks on cable connectors
when you disconnect all cables from the system board. Refer toInternal cable
routing on page 174). for more information. Failing to release them before
removing the cables will damage the cable sockets on the system board. The
cable sockets on the system board are fragile. Any damage to the cable sockets
7. Remove the DIMMs from the system board and set them aside on a
static-protective surface for reinstallation (see Removing a memory module
on page 223).
Note: Make a note of the location of each DIMM as you remove it, so that
you can later reinstall it in the same connector.
8. Remove all heat sinks and microprocessors, and set them aside on a
static-protective surface for reinstallation (see Removing a microprocessor
and heat sink on page 273).
Note:
a. Be sure to keep the heat sink and microprocessor from each
microprocessor socket of the old system board together so that you can
install them on the new system board together. For example, when you
remove the heat sink and microprocessor from microprocessor socket 1 of
the old system board , install them both on the same socket on the new
system board.
b. Use an alcohol wipe to remove any thermal grease from the tabs on the
microprocessor bracket frame on the old system board.
Tabs
Figure 188. Use an alcohol wipe to remove any thermal grease from the tabs
c. Always use microprocessor installation tool to remove a microprocessor.

Failing to use microprocessor installation tool may damage the
microprocessor sockets on the system board. Any damage to the
microprocessor sockets may require replacing the system board.
9. Remove the socket covers from the microprocessor sockets on the new system
board and place them on the microprocessor sockets of the old system board
that you are removing.
282
Figure 189. Socket cover removal
10. Loosen the nine screws that secure the system board to the chassis.
System board
(9 screws)
Figure 190. Loosen screws
11. Slightly lift the system board at the side that is near the CPU1_PWR to create
a small angle of elevation between the system board and chassis.
283
Figure 191. Tilt the system board
12. Gently push the external input/output connectors toward to the fan cage as
much as possible.
Figure 192. Push the system board toward to the fan cage
13. Grasp the system board on both the cable clip near the microprocessor 2 and
PCI riser card connector 1. Then, slightly lift the system board to create a
small angle of elevation by leaning the edge against the partition of the power
supply between the system board and chassis.
284
Riser 1 connector
Cable clip
Figure 193. Lift the system board slightly
14. Carefully lift up the system board by placing both hands diagonally and
remove it from the chassis. Be careful to avoid damage any surrounding
components or bend the pin inside the microprocessor socket.
Figure 194. System board removal
285
15. If you are instructed to return the system board, follow all packaging
to you.
Attention: Make sure to place the socket covers for the microprocessor
sockets on the system board before you return the old system board.
Replacing the system board

Use this information to install the system board.
Note:
1. Before you replace the system board, make sure that you backup any features
on demand (FoD) keys that were enabled. Remember to re-enable the features
on demand (FoD) keys after installing the new system board. For more
information on Features on Demand (FoD), including instructions for
ToolsCenter or IBM Systems Director, see the IBM Features on Demand User's
Guide at /http://www.ibm.com/systems/x/fod/ under the Help section.
2. When you reassemble the components in the server, be sure to route all cables
carefully so that they are not exposed to excessive pressure and so that they do
not get pinched when you reinstall the system board. In addition, make sure
the cables are inserted into the relevant cable clips.
3. When you replace the system board, you must either update the server with
the latest firmware or restore the pre-existing firmware that the customer
provides on a diskette or CD image. Make sure that you have the latest
firmware or a copy of the pre-existing firmware before you proceed. See
Updating the firmware on page 83, Updating the Universal Unique
Identifier (UUID) on page 105, and Updating the DMI/SMBIOS data on
page 108 for more information.
code is supported for the cluster solution before you update the code
To install the system board, complete the following steps:
2. Slide the system board into the chassis with a small angle toward to the hard
disk bays. Make sure the system board is seated into the chassis flat and the
no standoff is blocking the system board.
286
Standoffs
Figure 195. System board alignment
3. Push the edge of the external input/output connectors of the system board
away from the hard disk bays.
Figure 196. System board alignment
4. Make sure the eight standoffs are aligned with the corresponding captive
screw holes on the system board.
287
Standoffs
System board
Standoff
Figure 197. Standoffs and captive screw holes alignment
5. Align the screw holes on the system board with the screw holes on the chassis
and install the screws to secure the system board to the chassis.
System board
(9 screws)
Figure 198. System board installation
6. Reconnect the cables that you disconnected earlier to the system board.
7. Reinstall the DIMMs onto the system board (see Replacing a memory
module on page 224).
288
8. Reinstall the microprocessors and heat sinks (see Replacing a microprocessor

and heat sink on page 275).
9. Install the socket covers that you removed from the microprocessor sockets on
the new system board and place them on the microprocessor sockets of the
old system board, if you have not done so.
10. Reconnect the SAS signal cables and remote RAID battery cable to the
ServeRAID adapter, if you removed them earlier.
11. Reinstall the PCI riser-card assemblies with the adapters, if any were installed
(see Replacing a PCI riser-card assembly on page 79).
Important: Perform the following updates:
v Either update the server with the latest RAID firmware or restore the
pre-existing firmware from a diskette or CD image.
v Update the UUID (see Updating the Universal Unique Identifier (UUID) on
page 105).
v Update the DMI/SMBIOS (see Updating the DMI/SMBIOS data on page 108).
v If you purchased a Feature on Demand, make sure that you reactivate the
feature using the instructions in the Feature on Demand documentation.
289
290
Appendix A. Integrated Management Module II (IMM2) error

messages
This section details the Integrated Management Module II (IMM2) error messages.
When a hardware event is detected by the Integrated Management Module II
(IMM2) on the server, the Integrated Management Module II (IMM2) logs that
event in the system-event log in the server.
For each event code, the following fields are displayed:
Event identifier
A hexadecimal identifier that uniquely identifies an event or class of
events. In this documentation, the event identifiers are prefixed with 0x
and followed by eight characters.
Event description
The logged message string that appears for an event. When the event
string is displayed in the event log, information such as a specific
component is displayed. In this documentation, that additional information
appears as variables, such as [arg1] or [arg2].
Explanation
Provides additional information to explain why the event occurred.
Severity
An indication of the level of concern for the condition. In the system-event
log, severity is abbreviated to the first character. The following severities
can be displayed.
Info:
The event was recorded for audit purposes, usually a user action
or a change of states that is normal behavior.
Warning:
The event is not as severe as an error, but if possible, the condition
should be corrected before it becomes an error. It might also be a
condition that requires additional monitoring or maintenance.
Error:
The event is a failure or critical condition that impairs service or an

expected function.
Alert Category
Similar events are grouped together in categories. The alert category is in
the following format:
severity - device
severity is one of the following severity levels:
v Critical: A key component in the server is no longer functioning.
v Warning: The event might progress to a critical level.
v System: The event is the result of a system error or a configuration
change.
device is the specific device in the server that caused the event to be
generated.
Serviceable
Specifies whether user action is required to correct the problem.
291
40000001-00000000
CIM Information
Provides the prefix of the message ID and the sequence number that is
used by the CIM message registry.
SNMP Trap ID
The SNMP trap ID that is found in the SNMP alert management
information base (MIB).
Automatically contact Service
If this field is set to Yes, and you have enabled Electronic Service Agent
(ESA), IBM Support will be notified automatically if the event is generated.
While you wait for IBM Support to call, you can perform the
recommended actions for the event.
User response
Indicates what actions you should perform to solve the event.
Perform the steps listed in this section in the order shown until the
problem is solved. After you perform all of the actions that are described
in this field, if you cannot solve the problem, contact IBM Support.
Note: This list includes error codes and messages that might not apply to
this machine type and model.
The following is the list of Integrated Management Module II (IMM2) error
messages and suggested actions to correct the detected server problems. For more
information about Integrated Management Module II (IMM2), see the Integrated
Management Module II User's Guide at www.ibm.com/support/entry/portal/
40000001-00000000 Management Controller [arg1]
Network Initialization Complete.
Explanation: This message is for the use case where a
Management Controller network has completed
initialization.
Severity: Info
Alert Category: System - IMM Network event
Serviceable: No
CIM Information: Prefix: IMM and ID: 0001
SNMP Trap ID: 37
Automatically notify Support: No
User response: Information only; no action is
required.
292
40000002-00000000 40000004-00000000
40000002-00000000 Certificate Authority [arg1] has
detected a [arg2] Certificate Error.
Explanation: This message is for the use case when
there is an error with an SSL Server, SSL Client, or SSL
Trusted CA Certificate.
Severity: Error
Alert Category: System - SSL certification
Serviceable: No
SNMP Trap ID: 22
User response: Make sure that the certificate that you
are importing is correct and properly generated.
40000003-00000000 Ethernet Data Rate modified
from [arg1] to [arg2] by user [arg3].
user modifies the Ethernet Port data rate.
Severity: Info
Alert Category: none
Serviceable: No
SNMP Trap ID:
required.
40000004-00000000 Ethernet Duplex setting modified
Explanation: This message is for the use case where A
user modifies the Ethernet Port duplex setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
Appendix A. Integrated Management Module II (IMM2) error messages
293
40000005-00000000 40000007-00000000
40000005-00000000 Ethernet MTU setting modified
user modifies the Ethernet Port MTU setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000006-00000000 Ethernet locally administered
MAC address modified from [arg1] to
[arg2] by user [arg3].
user modifies the Ethernet Port MAC address setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000007-00000000 Ethernet interface [arg1] by user
[arg2].
user enables or disabled the ethernet interface.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
294
40000008-00000000 4000000a-00000000
40000008-00000000 Hostname set to [arg1] by user
[arg2].
Explanation: This message is for the use case where
user modifies the Hostname of a Management
Controller.
Severity: Info
Serviceable: No
SNMP Trap ID: 37
required.
40000009-00000000 IP address of network interface
modified from [arg1] to [arg2] by user
[arg3].
user modifies the IP address of a Management
Controller.
Severity: Info
Serviceable: No
SNMP Trap ID: 37
required.
4000000a-00000000 IP subnet mask of network
interface modified from [arg1] to [arg2]
by user [arg3].
user modifies the IP subnet mask of a Management
Controller.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
295
4000000b-00000000 4000000d-00000000
4000000b-00000000 IP address of default gateway
modified from [arg1] to [arg2] by user
[arg3].
user modifies the default gateway IP address of a
Management Controller.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000000c-00000000 OS Watchdog response [arg1] by
[arg2] .
an OS Watchdog has been enabled or disabled by a
user.
Severity: Warning
Serviceable: No
SNMP Trap ID:
required.
4000000d-00000000 DHCP[[arg1]] failure, no IP
address assigned.
DHCP server fails to assign an IP address to a
Management Controller.
Severity: Warning
Serviceable: No
SNMP Trap ID:
User response: Complete the following steps until the
problem is solved: Make sure that the IMM network
cable is connected. Make sure that there is a DHCP
server on the network that can assign an IP address to
the IMM.
296
4000000e-00000000 40000010-00000000
4000000e-00000000 Remote Login Successful. Login
ID: [arg1] from [arg2] at IP address
[arg3].
user successfully logs in to a Management Controller.
Severity: Info
Alert Category: System - Remote Login
Serviceable: No
SNMP Trap ID: 30
required.
4000000f-00000000 Attempting to [arg1] server [arg2]
by user [arg3].
user is using the Management Controller to perform a
power function on the system.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000010-00000000 Security: Userid: [arg1] had [arg2]
login failures from WEB client at IP
address [arg3].
user has failed to log in to a Management Controller
from a web browser.
Severity: Warning
Serviceable: No
SNMP Trap ID: 30
problem is solved: Make sure that the correct login ID
and password are being used. Have the system
administrator reset the login ID or password.
297
40000011-00000000 40000016-00000000
40000011-00000000 Security: Login ID: [arg1] had
[arg2] login failures from CLI at [arg3]..
from the Legacy CLI.
Severity: Warning
Serviceable: No
SNMP Trap ID: 30
40000012-00000000 Remote access attempt failed.
Invalid userid or password received.
Userid is [arg1] from WEB browser at IP
address [arg2].
and password are being used.

40000014-00000000 The [arg1] on system [arg2]
cleared by user [arg3].
Management Controller Event Log on a system is
cleared by a user.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
reset was initiated by user [arg2].
Management Controller reset is initiated by a user.

remote user has failed to establish a remote control
session from a Web browser session.
Severity: Info
Severity: Info
Serviceable: No
Serviceable: No
SNMP Trap ID:
SNMP Trap ID: 30

required.

User response: Make sure that the correct login ID
and password are being used.
40000013-00000000 Remote access attempt failed.
Invalid userid or password received.
Userid is [arg1] from TELNET client at
IP address [arg2].
from a telnet session.
Severity: Info
Serviceable: No
SNMP Trap ID: 30
User response: Make sure that the correct login ID
298
40000016-00000000 ENET[[arg1]] DHCPHSTN=[arg2], DN=[arg3], IP@=[arg4],

SN=[arg5], GW@=[arg6], DNS1@=[arg7] .
Management Controller IP address and configuration
has been assigned by the DHCP server.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000017-00000000 40000019-00000000
40000017-00000000 ENET[[arg1]] IPCfg:HstName=[arg2], IP@=[arg3]
,NetMsk=[arg4], GW@=[arg5] .
Management Controller IP address and configuration
has been assigned statically using user data.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000018-00000000 LAN: Ethernet[[arg1]] interface is
no longer active.
Management Controller ethernet interface is no longer
active.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000019-00000000 LAN: Ethernet[[arg1]] interface is
now active.
Management Controller ethernet interface is now
active.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
299
4000001a-00000000 4000001e-00000000
4000001a-00000000 DHCP setting changed to [arg1]
by user [arg2].
user changes the DHCP setting.
the integrity of the installed operating system.

4000001d-00000000 Watchdog [arg1] Failed to
Capture Screen.

an operating system error has occurred and the screen
capture failed.
Serviceable: No
Severity: Error
Alert Category: System - other
SNMP Trap ID:
Serviceable: No

required.
SNMP Trap ID: 22
Severity: Info
4000001b-00000000 Management Controller [arg1]:

Configuration restored from a file by
user [arg2].
user restores a Management Controller configuration
from a file.
Severity: Info
Serviceable: No

problem is solved: Reconfigure the watchdog timer to a
higher value. Make sure that the IMM Ethernet over
USB interface is enabled.Reinstall the RNDIS or
cdc_ether device driver for the operating system.
Disable the watchdog. Check the integrity of the
installed operating system. Update the IMM firmware.
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.

SNMP Trap ID:
4000001e-00000000 Running the backup

Management Controller [arg1] main
application.

required.

Management Controller has resorted to running the
backup main application.
4000001c-00000000 Watchdog [arg1] Screen Capture

Occurred .
Severity: Warning

an operating system error has occurred and the screen
was captured.
Serviceable: No
Severity: Info
SNMP Trap ID: 22
Serviceable: No
User response: Update the IMM firmware. 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.

SNMP Trap ID: 22
User response: If there was no operating-system error,
complete the following steps until the problem is
solved: Reconfigure the watchdog timer to a higher
value. Make sure that the IMM Ethernet-over-USB
interface is enabled. Reinstall the RNDIS or cdc_ether
device driver for the operating system. Disable the
watchdog. If there was an operating-system error, check
300
4000001f-00000000 40000020-00000000
4000001f-00000000 Please ensure that the
Management Controller [arg1] is flashed
with the correct firmware. The
Management Controller is unable to
match its firmware to the server.
Management Controller firmware version does not
match the server.
Severity: Error
Serviceable: No
SNMP Trap ID: 22
User response: Update the IMM firmware to a version
that the server supports. 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.
Reset was caused by restoring default
values.
Management Controller has been reset due to a user
restoring the configuration to default values.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
301
40000021-00000000 40000022-00000000
clock has been set from NTP server
[arg2].
Management Controller clock has been set from the
Network Time Protocol server.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000022-00000000 SSL data in the Management
Controller [arg1] configuruation data is
invalid. Clearing configuration data
region and disabling SSL.
Management Controller has detected invalid SSL data
in the configuration data and is clearing the
configuration data region and disabling the SSL.
Severity: Error
Serviceable: No
SNMP Trap ID: 22
problem is solved: Make sure that the certificate that
you are importing is correct. Try to import the
certificate again.
302
40000023-00000000 40000025-00000000
40000023-00000000 Flash of [arg1] from [arg2]
succeeded for user [arg3] .
user has successfully flashed the firmware component
(MC Main Application, MC Boot ROM, BIOS,
Diagnostics, System Power Backplane, Remote
Expansion Enclosure Power Backplane, Integrated
System Management Processor, or Remote Expansion
Enclosure Processor) from the interface and IP address (
%d.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000024-00000000 Flash of [arg1] from [arg2] failed
for user [arg3].
user has not flashed the firmware component from the
interface and IP address due to a failure.
Severity: Info
Serviceable: No
SNMP Trap ID: 22
required.
40000025-00000000 The [arg1] on system [arg2] is
75% full.
Management Controller Event Log on a system is 75%
full.
Severity: Info
Alert Category: System - Event Log 75% full
Serviceable: No
SNMP Trap ID: 35
required.
303
40000026-00000000 40000028-00000000
40000026-00000000 The [arg1] on system [arg2] is
100% full.
Management Controller Event Log on a system is 100%
full.
Severity: Info
Alert Category: System - Event Log 75% full
Serviceable: No
SNMP Trap ID: 35
User response: To avoid losing older log entries, save
the log as a text file and clear the log.
40000027-00000000 Platform Watchdog Timer expired
for [arg1].
Explanation: This message is for the use case when an
implementation has detected a Platform Watchdog
Timer Expired
Severity: Error
Alert Category: System - OS Timeout
Serviceable: No
SNMP Trap ID: 21
problem is solved: Reconfigure the watchdog timer to a
higher value. Make sure that the IMM
Ethernet-over-USB interface is enabled. Reinstall the
RNDIS or cdc_ether device driver for the operating
system. Disable the watchdog. Check the integrity of
the installed operating system.
40000028-00000000 Management Controller Test
Alert Generated by [arg1].
user has generated a Test Alert.
Severity: Info
Serviceable: No
SNMP Trap ID: 22
required.
304
40000029-00000000 4000002b-00000000
40000029-00000000 Security: Userid: [arg1] had [arg2]
login failures from an SSH client at IP
address [arg3].
from SSH.
Severity: Info
Serviceable: No
SNMP Trap ID: 30
4000002a-00000000 [arg1] firmware mismatch
internal to system [arg2]. Please attempt
to flash the [arg3] firmware.
specific type of firmware mismatch has been detected.
Severity: Error
Alert Category: System - Other
Serviceable: No
SNMP Trap ID: 22
User response: Reflash the IMM firmware to the latest
version.
4000002b-00000000
Domain name set to [arg1].
Explanation: Domain name set by user

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
305
4000002c-00000000 4000002e-00000000
4000002c-00000000 Domain Source changed to [arg1]
by user [arg2].
Explanation: Domain source changed by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000002d-00000000 DDNS setting changed to [arg1]
by user [arg2].
Explanation: DDNS setting changed by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000002e-00000000 DDNS registration successful.
The domain name is [arg1].
Explanation: DDNS registation and values
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
306
4000002f-00000000 40000031-00000000
4000002f-00000000
IPv6 enabled by user [arg1] .
Explanation: IPv6 protocol is enabled by user

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000030-00000000
IPv6 disabled by user [arg1] .
Explanation: IPv6 protocol is disabled by user

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000031-00000000 IPv6 static IP configuration
enabled by user [arg1].
Explanation: IPv6 static address assignment method is
enabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
307
40000032-00000000 40000034-00000000
40000032-00000000 IPv6 DHCP enabled by user
[arg1].
Explanation: IPv6 DHCP assignment method is
enabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000033-00000000 IPv6 stateless auto-configuration
enabled by user [arg1].
Explanation: IPv6 statless auto-assignment method is
enabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000034-00000000 IPv6 static IP configuration
disabled by user [arg1].
Explanation: IPv6 static assignment method is
disabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
308
40000035-00000000 40000037-00000000
40000035-00000000 IPv6 DHCP disabled by user
[arg1].
Explanation: IPv6 DHCP assignment method is
disabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000036-00000000 IPv6 stateless auto-configuration
disabled by user [arg1].
Explanation: IPv6 statless auto-assignment method is
disabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000037-00000000 ENET[[arg1]] IPv6LinkLocal:HstName=[arg2], IP@=[arg3]
,Pref=[arg4] .
Explanation: IPv6 Link Local address is active
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
309
40000038-00000000 4000003a-00000000
40000038-00000000 ENET[[arg1]] IPv6Static:HstName=[arg2], IP@=[arg3]
,Pref=[arg4], GW@=[arg5] .
Explanation: IPv6 Static address is active
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000039-00000000 ENET[[arg1]] DHCPv6HSTN=[arg2], DN=[arg3], IP@=[arg4],
Pref=[arg5].
Explanation: IPv6 DHCP-assigned address is active
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000003a-00000000 IPv6 static address of network
interface modified from [arg1] to [arg2]
by user [arg3].
Explanation: A user modifies the IPv6 static address
of a Management Controller
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
310
4000003b-00000000 4000003d-00000000
4000003b-00000000 DHCPv6 failure, no IP address
assigned.
Explanation: S DHCP6 server fails to assign an IP
address to a Management Controller.
Severity: Warning
Serviceable: No
SNMP Trap ID:
problem is solved: Make sure that the IMM network
cable is connected. Make sure that there is a DHCPv6
server on the network that can assign an IP address to
the IMM.
4000003c-00000000 Platform Watchdog Timer expired
for [arg1].
Explanation: An implementation has detected an OS
Loader Watchdog Timer Expired
Severity: Error
Alert Category: System - Loader timeout
Serviceable: No
SNMP Trap ID: 26
User response: Reconfigure the watchdog timer to a
higher value. Make sure that the IMM Ethernet over
USB interface is enabled. Reinstall the RNDIS or
cdc_ether device driver for the operating system.
Disable the watchdog. Check the integrity of the
installed operating system.
4000003d-00000000 Telnet port number changed from
[arg1] to [arg2] by user [arg3].
Explanation: A user has modified the telnet port
number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
311
4000003e-00000000 40000040-00000000
4000003e-00000000 SSH port number changed from
[arg1] to [arg2] by user [arg3].
Explanation: A user has modified the SSH port
number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000003f-00000000 Web-HTTP port number changed
Explanation: A user has modified the Web HTTP port
number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000040-00000000 Web-HTTPS port number
changed from [arg1] to [arg2] by user
[arg3].
Explanation: A user has modified the Web HTTPS
port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
312
40000041-00000000 40000043-00000000
40000041-00000000 CIM/XML HTTP port number
[arg3].
Explanation: A user has modified the CIM HTTP port
number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000042-00000000 CIM/XML HTTPS port number
[arg3].
Explanation: A user has modified the CIM HTTPS
port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000043-00000000 SNMP Agent port number
[arg3].
Explanation: A user has modified the SNMP Agent
port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
313
40000044-00000000 40000046-00000000
40000044-00000000 SNMP Traps port number
[arg3].
Explanation: A user has modified the SNMP Traps
port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000045-00000000 Syslog port number changed
Explanation: A user has modified the Syslog receiver
port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000046-00000000 Remote Presence port number
[arg3].
Explanation: A user has modified the Remote
Presence port number
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
314
40000047-00000000 40000049-00000000
40000047-00000000 LED [arg1] state changed to [arg2]
by [arg3].
Explanation: A user has modified the state of an LED
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000048-00000000 Inventory data changed for
device [arg1], new device data
hash=[arg2], new master data
hash=[arg3] .
Explanation: Something has caused the physical
inventory to change
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000049-00000000 SNMP [arg1] enabled by user
[arg2] .
Explanation: A user enabled SNMPv1 or SNMPv3 or
Traps
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
315
4000004a-00000000 4000004c-00000000
4000004a-00000000 SNMP [arg1] disabled by user
[arg2] .
Explanation: A user disabled SNMPv1 or SNMPv3 or
Traps
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000004b-00000000 SNMPv1 [arg1] set by user [arg2]:
Name=[arg3], AccessType=[arg4],
Address=[arg5], .
Explanation: A user changed the SNMP community
string
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000004c-00000000 LDAP Server configuration set by
user [arg1]: SelectionMethod=[arg2],
DomainName=[arg3], Server1=[arg4],
Server2=[arg5], Server3=[arg6],
Server4=[arg7].
Explanation: A user changed the LDAP server
configuration
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
316
4000004d-00000000 4000004f-00000000
4000004d-00000000 LDAP set by user [arg1]:
RootDN=[arg2],
UIDSearchAttribute=[arg3],
BindingMethod=[arg4],
EnhancedRBS=[arg5],
TargetName=[arg6], GroupFilter=[arg7],
GroupAttribute=[arg8],
LoginAttribute=[arg9].
Explanation: A user configured an LDAP
Miscellaneous setting
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000004e-00000000 Serial Redirection set by user
[arg1]: Mode=[arg2], BaudRate=[arg3],
StopBits=[arg4], Parity=[arg5],
SessionTerminateSequence=[arg6].
Explanation: A user configured the Serial Port mode
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000004f-00000000 Date and Time set by user [arg1]:
Date=[arg2], Time-[arg3], DST
Auto-adjust=[arg4], Timezone=[arg5].
Explanation: A user configured the Date and Time
settings
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
317
40000050-00000000 40000052-00000000
40000050-00000000 Server General Settings set by
user [arg1]: Name=[arg2], Contact=[arg3],
Location=[arg4], Room=[arg5],
RackID=[arg6], Rack U-position=[arg7].
Explanation: A user configured the Location setting
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000051-00000000 Server Power Off Delay set to
Explanation: A user configured the Server Power Off
Delay
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000052-00000000 Server [arg1] scheduled for [arg2]
at [arg3] by user [arg4].
Explanation: A user configured a Server Power action
at a specific time
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
318
40000053-00000000 40000055-00000000
40000053-00000000 Server [arg1] scheduled for every
[arg2] at [arg3] by user [arg4].
Explanation: A user configured a recurring Server
Power Action
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000054-00000000 Server [arg1] [arg2] cleared by
user [arg3].
Explanation: A user cleared a Server Power Action.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000055-00000000 Synchronize time setting by user
[arg1]: Mode=[arg2],
NTPServerHost=[arg3]:[arg4],NTPUpdateFrequency=[arg5].
Explanation: A user configured the Date and Time
synchronize settings
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
319
40000056-00000000 40000058-00000000
40000056-00000000 SMTP Server set by user [arg1] to
[arg2]:[arg3].
Explanation: A user configured the SMTP server
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000057-00000000
Telnet [arg1] by user [arg2].
Explanation: A user enables or disables Telnet services

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000058-00000000 DNS servers set by user [arg1]:
UseAdditionalServers=[arg2],
PreferredDNStype=[arg3],
IPv4Server1=[arg4], IPv4Server2=[arg5],
IPv4Server3=[arg6], IPv6Server1=[arg7],
IPv6Server2=[arg8], IPv6Server3=[arg9].
Explanation: A user configures the DNS servers
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
320
40000059-00000000 4000005b-00000000
40000059-00000000 LAN over USB [arg1] by user
[arg2].
Explanation: A user configured USB-LAN
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000005a-00000000 LAN over USB Port Forwarding
set by user [arg1]: ExternalPort=[arg2],
USB-LAN port=[arg3].
Explanation: A user configured USB-LAN port
forwarding
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000005b-00000000 Secure Web services (HTTPS)
Explanation: A user enables or disables Secure web
services
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
321
4000005c-00000000 4000005e-00000000
4000005c-00000000 Secure CIM/XML(HTTPS) [arg1]
by user [arg2].
Explanation: A user enables or disables Secure
CIM/XML services
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000005d-00000000 Secure LDAP [arg1] by user
[arg2].
Explanation: A user enables or disables Secure LDAP
services
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000005e-00000000
SSH [arg1] by user [arg2].
Explanation: A user enables or disables SSH services

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
322
4000005f-00000000 40000061-00000000
4000005f-00000000 Server timeouts set by user [arg1]:
EnableOSWatchdog=[arg2],
OSWatchdogTimout=[arg3],
EnableLoaderWatchdog=[arg4],
LoaderTimeout=[arg5].
Explanation: A user configures Server Timeouts
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000060-00000000 License key for [arg1] added by
user [arg2].
Explanation: A user installs License Key
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000061-00000000 License key for [arg1] removed
by user [arg2].
Explanation: A user removes a License Key
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
323
40000062-00000000 40000063-00000000
40000062-00000000 Global Login General Settings set
by user [arg1]:
AuthenticationMethod=[arg2],
LockoutPeriod=[arg3],
SessionTimeout=[arg4].
Explanation: A user changes the Global Login General
Settings
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000063-00000000 Global Login Account Security
set by user [arg1]:
PasswordRequired=[arg2],
PasswordExpirationPeriod=[arg3],
MinimumPasswordReuseCycle=[arg4],
MinimumPasswordLength=[arg5],
MinimumPasswordChangeInterval=[arg6],
MaxmumLoginFailures=[arg7],
LockoutAfterMaxFailures=[arg8],
MinimumDifferentCharacters=[arg9],
DefaultIDExpired=[arg10],
ChangePasswordFirstAccess=[arg11].
Explanation: A user changes the Global Login
Account Security Settings to Legacy
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
324
40000064-00000000 40000066-00000000
40000064-00000000
User [arg1] created..
Explanation: A user account was created

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000065-00000000
User [arg1] removed...
Explanation: A user account was deleted

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000066-00000000
User [arg1] password modified..
Explanation: A user account was changed

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
325
40000067-00000000 40000069-00000000
40000067-00000000
User [arg1] role set to [arg2].
Explanation: A user account role assigned

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000068-00000000 User [arg1] custom privileges set:
[arg2].
Explanation: User account priveleges assigned
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000069-00000000 User [arg1] for SNMPv3 set:
AuthenticationProtocol=[arg2],
PrivacyProtocol=[arg3],
AccessType=[arg4], HostforTraps=[arg5].
Explanation: User account SNMPv3 settings changed
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
326
4000006a-00000000 4000006c-00000000
4000006a-00000000 SSH Client key added for user
[arg1].
Explanation: User locally defined an SSH Client key
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000006b-00000000 SSH Client key imported for user
[arg1] from [arg2].
Explanation: User imported an SSH Client key
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000006c-00000000 SSH Client key removed from
user [arg1].
Explanation: User removed an SSH Client key
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
327
4000006d-00000000 4000006f-00000000
4000006d-00000000 Management Controller [arg1]:
Configuration saved to a file by user
[arg2].
Explanation: A user saves a Management Controller
configuration to a file.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000006e-00000000 Alert Configuration Global Event
Notification set by user [arg1]:
RetryLimit=[arg2], RetryInterval=[arg3],
EntryInterval=[arg4].
Explanation: A user changes the Global Event
Notification settings.
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000006f-00000000 Alert Recipient Number [arg1]
updated: Name=[arg2],
DeliveryMethod=[arg3], Address=[arg4],
IncludeLog=[arg5], Enabled=[arg6],
EnabledAlerts=[arg7],
AllowedFilters=[arg8].
Explanation: A user adds or updates an Alert
Recipient
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
328
40000070-00000000 40000072-00000000
40000070-00000000 SNMP Traps enabled by user
[arg1]: EnabledAlerts=[arg2],
AllowedFilters=[arg3] .
Explanation: A user enabled the SNMP Traps
configuration
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000071-00000000 The power cap value changed
from [arg1] watts to [arg2] watts by user
[arg3].
Explanation: Power Cap values changed by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000072-00000000 The minimum power cap value
changed from [arg1] watts to [arg2]
watts.
Explanation: Minimum Power Cap value changed
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
329
40000073-00000000 40000075-00000000
40000073-00000000 The maximum power cap value
changed from [arg1] watts to [arg2]
watts.
Explanation: Maximum Power Cap value changed
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000074-00000000 The soft minimum power cap
value changed from [arg1] watts to
[arg2] watts.
Explanation: Soft Minimum Power Cap value changed
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000075-00000000 The measured power value
exceeded the power cap value.
Explanation: Power exceeded cap
Severity: Warning
Alert Category: Warning - Power
Serviceable: No
SNMP Trap ID: 164
required.
330
40000076-00000000 40000078-00000000
40000076-00000000 The new minimum power cap
value exceeded the power cap value.
Explanation: Minimum Power Cap exceeds Power
Cap
Severity: Warning
Serviceable: No
SNMP Trap ID: 164
required.
40000077-00000000 Power capping was activated by
user [arg1].
Explanation: Power capping activated by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000078-00000000 Power capping was deactivated
by user [arg1].
Explanation: Power capping deactivated by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
331
40000079-00000000 4000007b-00000000
40000079-00000000 Static Power Savings mode has
been turned on by user [arg1].
Explanation: Static Power Savings mode turned on by
user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000007a-00000000 Static Power Savings mode has
been turned off by user [arg1].
Explanation: Static Power Savings mode turned off by
user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000007b-00000000 Dynamic Power Savings mode
has been turned on by user [arg1].
Explanation: Dynamic Power Savings mode turned on
by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
332
4000007c-00000000 4000007e-00000000
4000007c-00000000 Dynamic Power Savings mode
has been turned off by user [arg1].
Explanation: Dynamic Power Savings mode turned off
by user
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000007d-00000000 Power cap and external throttling
occurred.
Explanation: Power cap and external throttling
occurred
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
4000007e-00000000
External throttling occurred .
Explanation: External throttling occurred

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
333
4000007f-00000000 40000081-00000000
4000007f-00000000
Power cap throttling occurred.
Explanation: Power cap throttling occurrred

Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000080-00000000 Remote Control session started
by user [arg1] in [arg2] mode.
Explanation: Remote Control session started
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
40000081-00000000 PXE boot requested by user
[arg1].
Explanation: PXE boot requested
Severity: Info
Serviceable: No
SNMP Trap ID:
required.
334
40000082-00000000 40000084-00000000
40000082-00000000 The measured power value has
returned below the power cap value.
Explanation: Power exceeded cap recovered
Severity: Info
Serviceable: No
SNMP Trap ID: 164
required.
40000083-00000000 The new minimum power cap
value has returned below the power cap
value.
Explanation: Minimum Power Cap exceeds Power
Cap recovered
Severity: Info
Serviceable: No
SNMP Trap ID: 164
required.
40000084-00000000 IMM firmware mismatch
between nodes [arg1] and [arg2]. Please
attempt to flash the IMM firmware to
the same level on all nodes.
Explanation: A mismatch of IMM firmware has been
detected between nodes
Severity: Error
Serviceable: No
SNMP Trap ID: 22
User response: Attempt to flash the IMM firmware to
335
40000085-00000000 40000087-00000000
40000085-00000000 FPGA firmware mismatch
between nodes [arg1] and [arg2]. Please
attempt to flash the FPGA firmware to
Explanation: A mismatch of FPGA firmware has been
detected between nodes
Severity: Error
Serviceable: No
SNMP Trap ID: 22
User response: Attempt to flash the FPGA firmware to
40000086-00000000 Test Call Home Generated by
user [arg1].
Explanation: Test Call Home generated by user.
Severity: Info
Serviceable: No
SNMP Trap ID:
Automatically notify Support: Yes
required.
40000087-00000000 Manual Call Home by user
[arg1]: [arg2].
Explanation: Manual Call Home by user.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: IBM Support will address the problem.
336
40000088-00000000 80010202-0701xxxx
40000088-00000000 Management Controller [arg1]:
Configuration restoration from a file by
user [arg2] completed..
from a file and it completes.
Severity: Info
from the power source. You must disconnect the server

from ac power to reset the IMM. After 45 seconds,
reconnect the server to the power source and turn on
the server. Retry the operation
4000008b-00000000 One or more of the Storage
Management IP addresses has changed..

an IP address for the Storage Management has changed
Serviceable: No
Severity: Info
SNMP Trap ID:
Serviceable: No

required.
SNMP Trap ID: 37

40000089-00000000 Management Controller [arg1]:

user [arg2] failed to complete..
from a file and the restoration fails to complete.
Severity: Error

required.
80010002-0701xxxx Numeric sensor
[NumericSensorElementName] going
low (lower non-critical) has asserted.
(CMOS Battery)
implementation has detected a Lower Non-critical
sensor going low has asserted.

Serviceable: No
Severity: Warning
Alert Category: Warning - Voltage
SNMP Trap ID: 22
Serviceable: Yes

User response: Turn off the server and disconnect it
from the power source. You must disconnect the server
from ac power to reset the IMM. After 45 seconds,
reconnect the server to the power source and turn on
the server. Retry the operation.
4000008a-00000000 Management Controller [arg1]:
user [arg2] failed to start..
from a file and the restoration fails to start.
Severity: Error
CIM Information: Prefix: PLAT and ID: 0476

SNMP Trap ID: 13
User response: Replace the system battery.
low (lower critical) has asserted. (CMOS
Battery)
implementation has detected a Lower Critical sensor
going low has asserted.
Severity: Error
Alert Category: Critical - Voltage
Serviceable: No
Serviceable: Yes
SNMP Trap ID: 22
SNMP Trap ID: 1

User response: Turn off the server and disconnect it
337
80010204-1d01xxxx 80010204-1d02xxxx
User response: If the specified sensor is Planar 3.3V or
Planar 5V, (Trained technician only) replace the system
board. If the specified sensor is Planar 12V, complete
the following steps until the problem is solved: 1.
Check power supply n LED. 2. Remove the failing
power supply. 3. Follow actions for OVER SPEC LED
in Light path diagnostics LEDs. 4. (Trained technician
only) Replace the system board. (n = power supply
number)
80010204-1d01xxxx Numeric sensor
low (lower critical) has asserted. (Fan
1Aa Tach)
Severity: Error
Alert Category: Critical - Fan Failure
Serviceable: Yes
SNMP Trap ID: 11
User response: 1. Reseat the failing fan n, which is
indicated by a lit LED near the fan connector on the
system board. 2. Replace the failing fan. (n = fan
number)
1Ab Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
338
80010204-1d03xxxx 80010204-1d04xxxx
1Ba Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
1Bb Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
339
80010204-1d05xxxx 80010204-1d06xxxx
2Aa Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
2Ab Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
340
80010204-1d07xxxx 80010204-1d08xxxx
2Ba Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
2Bb Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
341
80010204-1d09xxxx 80010204-1d0axxxx
3Aa Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
80010204-1d0axxxx Numeric sensor
3Ab Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
342
80010204-1d0bxxxx 80010204-1d0cxxxx
80010204-1d0bxxxx Numeric sensor
3Ba Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
80010204-1d0cxxxx Numeric sensor
3Bb Tach)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
number)
343
80010701-0701xxxx 80010701-0c01xxxx
high (upper non-critical) has asserted.
(FHHL Temp)
implementation has detected an Upper Non-critical
sensor going high has asserted.
Severity: Warning
Alert Category: Warning - Temperature
Serviceable: Yes
SNMP Trap ID: 12
User response: 1. Reduce the temperature. 2. Check
the server airflow. Make sure that nothing is blocking
the air from coming into or preventing the air from
exiting the server. LowProfile Temp : Raid Temp :
80010701-0c01xxxx Numeric sensor
(Ambient Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
exiting the server.
344
80010701-1401xxxx 80010701-1402xxxx
(CPU1 VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
exiting the server.
(CPU2 VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
exiting the server.
345
80010701-2d01xxxx 80010901-0701xxxx
(PCH Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
exiting the server.
high (upper critical) has asserted. (FHHL
Temp)
implementation has detected an Upper Critical sensor
going high has asserted.
Severity: Error
Alert Category: Critical - Temperature
Serviceable: Yes
SNMP Trap ID: 0
User response: 1. Reduce the ambient temperature. 2.
Ensure the air baffle is installed correctly. 3. Check the
server airflow. Make sure that nothing is blocking the
air from coming into or preventing the air from exiting
the server. LowProfile Temp : Raid Temp :
346
80010901-0c01xxxx 80010901-1401xxxx
high (upper critical) has asserted.
(Ambient Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
the server.
high (upper critical) has asserted. (CPU1
VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
the server.
347
80010901-1402xxxx 80010901-2d01xxxx
high (upper critical) has asserted. (CPU2
VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
the server.
high (upper critical) has asserted. (PCH
Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
the server.
348
80010902-0701xxxx 80010b01-0701xxxx
high (upper critical) has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 1
User response: If the specified sensor is Planar 3.3V or
Planar 5V, (Trained technician only) replace the system
board. If the specified sensor is Planar 12V, complete
power supply. 3. (Trained technician only) Replace the
system board. (n = power supply number)
80010b01-0701xxxx Numeric sensor
high (upper non-recoverable) has
asserted. (FHHL Temp)
implementation has detected an Upper Non-recoverable
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response: Check the server airflow. Make sure
that nothing is blocking the air from coming into or
preventing the air from exiting the server. LowProfile
Temp : Raid Temp :
349
80010b01-0c01xxxx 80010b01-1401xxxx
80010b01-0c01xxxx Numeric sensor
asserted. (Ambient Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
preventing the air from exiting the server.
asserted. (CPU1 VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
350
80010b01-1402xxxx 80010b01-2d01xxxx
asserted. (CPU2 VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
80010b01-2d01xxxx Numeric sensor
asserted. (PCH Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
351
80030006-2101xxxx 80050108-0a01xxxx
80030006-2101xxxx Sensor [SensorElementName] has
deasserted. (Sig Verify Fail)
implementation has detected a Sensor has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only.
deasserted. (OS RealTime Mod)
implementation has detected a Sensor has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
80050108-0a01xxxx Sensor [SensorElementName] has
indicated limit exceeded. (PS 1 CS)
implementation has detected a Sensor limit was
exceeded.
Severity: Info
Serviceable: No
SNMP Trap ID:
352
80050108-0a02xxxx 80070201-0301xxxx
indicated limit exceeded. (PS 2 CS)
implementation has detected a Sensor limit was
exceeded.
to Automatic. 3. Replace the corrupt disk.

transitioned from normal to non-critical
state. (TPM Phy Pres Set)

implementation has detected a Sensor transitioned to
non-critical from normal.
Serviceable: No
Severity: Warning
Alert Category: Warning - Other
SNMP Trap ID:
Serviceable: Yes
SNMP Trap ID: 60
Severity: Info

8007010f-2201xxxx Sensor [SensorElementName] has
state. (GPT Status)
User response: 1. Complete the administrative tasks

that require the TPM physical presence switch to be in
the ON position. 2. Restore the physical presence
switch to the OFF position. 3. Reboot the system. 4.
(Trained technician only) If the error continues, replace
the planar.
Severity: Warning
transitioned to critical from a less severe
state. (CPU 1 OverTemp)

Serviceable: Yes
SNMP Trap ID: 60

critical from less severe.
Severity: Error
User response: 1. Check the IBM support site for

service bulletins or firmware updates that apply to this
GPT error. 2. Set the UEFI setting DISK GPT Recovery
to Automatic. 3. Replace the corrupt disk. TXT ACM
Module :
Serviceable: Yes
SNMP Trap ID: 0

state. (No PCI I/O Space)
Severity: Warning
Serviceable: Yes

User response: 1. Make sure that the fans are
operating, that there are no obstructions to the airflow
(front and rear of the server), that the air baffles are in
place and correctly installed, and that the server cover
is installed and completely closed. 2. Check the ambient
temperature. You must be operating within the
specifications (see Features and specifications for more
information). 3. Make sure that the heat sink for
microprocessor n is installed correctly. 4. (Trained
technician only) Replace microprocessor n. (n =
microprocessor number)
SNMP Trap ID: 60

User response: 1. Check the IBM support site for
service bulletins or firmware updates that apply to this
GPT error. 2. Set the UEFI setting DISK GPT Recovery
353
80070201-0302xxxx 80070202-0701xxxx
state. (CPU 2 OverTemp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
specifications (see Features and specifications for more
information). 3. Make sure that the heat sink for
state. (SysBrd Vol Fault)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 1
User response: 1. Check the system-event log. 2.
Check for an error LED on the system board. 3. Replace
any failing device. 4. Check for a server 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. (Trained technician only)
Replace the system board.
354
80070208-0a01xxxx 80070208-0a02xxxx
state. (PS 1 Fan Fault)
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
SNMP Trap ID: 4
User response: 1. Make sure that there are no
obstructions, such as bundled cables, to the airflow
from the power-supply fan. 2. Use the IBM Power
Configurator utility to ensure current system power
consumption is under limitation. For more information
and to download the utility, go to http://www03.ibm.com/systems/bladecenter/resources/
powerconfig.html. 3. Replace power supply n. (n =
power supply number) PS 1 OP Fault : PS 1 Therm
Fault :
state. (PS 2 Fan Fault)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response: 1. Make sure that there are no
obstructions, such as bundled cables, to the airflow
from the power-supply fan. 2. Use the IBM Power
Configurator utility to ensure current system power
consumption is under limitation. For more information
and to download the utility, go to http://www03.ibm.com/systems/bladecenter/resources/
powerconfig.html. 3. Replace power supply n. (n =
power supply number) PS 2 OP Fault : PS 2 Therm
Fault :
355
8007020f-2582xxxx 80070214-2201xxxx
state. (No PCI I/O Space)
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
SNMP Trap ID: 50
User response: Complete the following step to solve
PCI I/O resource errors: 1. Go to F1 Setup-> System
Settings-> Device and I/O ports-> PCI 64 bit Resource
and choose enable.
state. (TPM Lock)
Severity: Error
Serviceable: No
SNMP Trap ID:
User response: 1. Update the server firmware (see
Recovering the server firmware). 2. If the problem
persists, (trained technician only) replace the system
board (see Removing the system board and Installing
the system board).
356
80070219-0701xxxx 8007021b-0301xxxx
state. (SysBrd Fault)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Check for an error LED on the
system board. 2. Check the system-event log. 3. Check
for a server firmware update. Important: Some cluster
solutions require specific code levels or coordinated
code updates. If the device is part of a cluster solution,
cluster solution before you update the code. 4. Replace
any failing device which indicated from system event
log. 5. (Trained technician only) Replace the system
board.
8007021b-0301xxxx Sensor [SensorElementName] has
state. (CPU 1 QPILinkErr)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Check for a server firmware update.
2. Make sure that the installed microprocessors are
compatible. 3. (Trained technician only) Replace the
microprocessor if the problems still exist. 4. (Trained
technician only) Replace the system board if the
problems still exist.
357
8007021b-0302xxxx 80070301-0301xxxx
state. (CPU 2 QPILinkErr)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Check for a server firmware update.
2. Make sure that the installed microprocessors are
compatible. 3. (Trained technician only) Replace the
microprocessor if the problems still exist. 4. (Trained
technician only) Replace the system board if the
problems still exist.
transitioned to non-recoverable from a
less severe state. (CPU 1 OverTemp)
non-recoverable from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
(front and rear of the server), that the air baffle is in
specifications (see Server Features and specifications for
more information). 3. Make sure that the heat sink for
microprocessor n. 4. (Trained technician only) Replace
microprocessor n. (n = microprocessor number)
358
80070301-0302xxxx 80070608-0a02xxxx
transitioned to non-recoverable from a
less severe state. (CPU 2 OverTemp)
non-recoverable from less severe.

number) If the specified sensor is PS n 12Vaux Fault,
solved: 1. Check power supply n LED. 2. Replace
power supply n. (n = power supply number)
Severity: Error
transitioned to non-recoverable.

Serviceable: Yes

non-recoverable.

SNMP Trap ID: 0
Severity: Error

(front and rear of the server), that the air baffle is in
specifications (see Server Features and specifications for
more information). 3. Make sure that the heat sink for
microprocessor n. 4. (Trained technician only) Replace
microprocessor n. (n = microprocessor number)
transitioned to non-recoverable.
non-recoverable.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response: If the specified sensor is PS n 12V OC
Fault, complete the following steps until the problem is
solved: 1. Use the IBM Power Configurator utility to
determine current system power consumption. For
more information and to download the utility, go to
http://www-03.ibm.com/systems/bladecenter/
resources/powerconfig.html. 2. Check the OVER SPEC
LED in Light path diagnostics LEDs and Pwr Rail (A,
B, C, D, E, F, G, and H) error has been recorded in the
IMM2 event log. If the specified sensor is PS n 12V OV
solved: 1. Check power supply n LED. 2. Remove the
failing power supply. 3. (Trained technician only)
Replace the system board. (n = power supply number)
If the specified sensor is PS n 12V UV Fault, complete

Serviceable: Yes
SNMP Trap ID: 4
User response: If the specified sensor is PS n 12V OC
solved: 1. Use the IBM Power Configurator utility to
determine current system power consumption. For
more information and to download the utility, go to
http://www-03.ibm.com/systems/bladecenter/
resources/powerconfig.html. 2. Check the OVER SPEC
LED in Light path diagnostics LEDs and Pwr Rail (A,
B, C, D, E, F, G, and H) error has been recorded in the
IMM2 event log. If the specified sensor is PS n 12V OV
solved: 1. Check power supply n LED. 2. Remove the
failing power supply. 3. (Trained technician only)
Replace the system board. (n = power supply number)
If the specified sensor is PS n 12V UV Fault, complete
number) If the specified sensor is PS n 12Vaux Fault,
solved: 1. Check power supply n LED. 2. Replace
power supply n. (n = power supply number)
359
80070614-2201xxxx 80080128-2101xxxx
transitioned to non-recoverable. (TPM
Phy Pres Set)
non-recoverable.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Update the server firmware (see
Recovering the server firmware). 2. If the problem
persists, (trained technician only) replace the system
the system board).
8008010f-2101xxxx Device
[LogicalDeviceElementName] has been
added. (Phy Presence Jmp)
implementation has detected a Device was inserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
80080128-2101xxxx Device
[LogicalDeviceElementName] has been
added. (Low Security Jmp)
implementation has detected a Device was inserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
360
800b0008-1301xxxx 800b010a-1e81xxxx
800b0008-1301xxxx Redundancy
[RedundancySetElementName] has been
restored. (Power Unit)
implementation has detected Redundancy was
Restored.
Severity: Info
Alert Category: Warning - Redundant Power Supply
Serviceable: No
SNMP Trap ID: 10
800b0108-1301xxxx Redundancy Lost for
[RedundancySetElementName] has
asserted. (Power Unit)
Redundancy Lost has asserted.
Severity: Error
Alert Category: Critical - Redundant Power Supply
Serviceable: Yes
SNMP Trap ID: 9
User response: 1. Check the LEDs for both power
supplies. 2. Follow the actions in Power-supply LEDs.
800b010a-1e81xxxx Redundancy Lost for
asserted. (Cooling Zone 1)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response: 1. Make sure that the connectors on
fan n are not damaged. 2. Make sure that the fan n
connectors on the system board are not damaged. 3.
Make sure that the fans are correctly installed. 4. Reseat
the fans. 5. Replace the fans. (n = fan number)
361
800b010a-1e82xxxx 800b050a-1e82xxxx
Severity: Error
User response: 1. Check the system-event log for

DIMM failure events (uncorrectable or PFA) and correct
the failures. 2. Re-enable mirroring in the Setup utility.
800b050a-1e81xxxx Non-redundant:Insufficient
Resources for
Explanation: This message is for the use case when a

Redundancy Set has transitioned to
Non-redundant:Insufficient Resources.
SNMP Trap ID: 11
Severity: Error

Serviceable: Yes
Serviceable: Yes
800b010c-2581xxxx Redundancy Lost for

asserted. (Backup Memory)
Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes

SNMP Trap ID: 11
Resources for
SNMP Trap ID: 41

Severity: Error

Serviceable: Yes
800b030c-2581xxxx Non-redundant:Sufficient
Resources from Redundancy Degraded
or Fully Redundant for
Redundancy Set has transitioned from Redundancy
Degraded or Fully Redundant to Nonredundant:Sufficient.
Severity: Warning
Alert Category: Warning - Memory
Serviceable: Yes
SNMP Trap ID: 43
362
SNMP Trap ID: 11

800b050c-2581xxxx 806f0007-0301xxxx
800b050c-2581xxxx Non-redundant:Insufficient
Resources for
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f0007-0301xxxx [ProcessorElementName] has
Failed with IERR. (CPU 1)
implementation has detected a Processor Failed - IERR
Condition.
Severity: Error
Alert Category: Critical - CPU
Serviceable: Yes
SNMP Trap ID: 40
User response: 1. Make sure that the latest level of
firmware and device drivers are installed for all
adapters and standard devices, such as Ethernet, SCSI,
and SAS. Important: Some cluster solutions require
before you update the code. 2. Update the firmware
(UEFI and IMM) to the latest level (Updating the
firmware). 3. Run the DSA program. 4. Reseat the
adapter. 5. Replace the adapter. 6. (Trained technician
only) Replace microprocessor n. 7. (Trained technician
only) Replace the system board. (n = microprocessor
number)
363
806f0007-0302xxxx 806f0008-0a01xxxx
Failed with IERR. (CPU 2)
implementation has detected a Processor Failed - IERR
Condition.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response: 1. Make sure that the latest level of
number)
806f0008-0a01xxxx [PowerSupplyElementName] has
been added to container
[PhysicalPackageElementName]. (Power
Supply 1)
implementation has detected a Power Supply has been
added.
Severity: Info
Serviceable: No
SNMP Trap ID:
364
806f0008-0a02xxxx 806f000d-0400xxxx
been added to container
Supply 2)
added.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0009-1301xxxx [PowerSupplyElementName] has
been turned off. (Host Power)
implementation has detected a Power Unit that has
been Disabled.
Severity: Info
Alert Category: System - Power Off
Serviceable: No
SNMP Trap ID: 23
806f000d-0400xxxx The Drive
[StorageVolumeElementName] has been
added. (Drive 0)
implementation has detected a Drive has been Added.
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
SNMP Trap ID: 5
365
806f000d-0401xxxx 806f000d-0403xxxx
added. (Drive 1)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
added. (Drive 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
added. (Drive 3)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
366
806f000d-0404xxxx 806f000d-0406xxxx
added. (Drive 4)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
added. (Drive 5)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
added. (Drive 6)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
367
806f000d-0407xxxx 806f000f-220101xx
added. (Drive 7)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000f-220101xx The System
[ComputerSystemElementName] has
detected no memory in the system.
(ABR Status)
implementation has detected that memory was detected
in the system.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response: 1. Make sure the server meets the
minimum configuration to start (see Power-supply
LEDs). 2. Recover the server firmware from the backup
page: a. Restart the server. b. At the prompt, press F3 to
recover the firmware. 3. Update the server firmware on
the primary page. Important: Some cluster solutions
require specific code levels or coordinated code
updates. If the device is part of a cluster solution,
cluster solution before you update the code. 4. Remove
components one at a time, restarting the server each
time, to see if the problem goes away. 5. If the problem
remains, (trained technician only) replace the system
board. Firmware Error : Sys Boot Status :
368
806f000f-220102xx 806f000f-220103xx
806f000f-220102xx Subsystem
[MemoryElementName] has insufficient
memory for operation. (ABR Status)
implementation has detected that the usable Memory is
insufficient for operation.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
LEDs). 2. Update the server firmware on the primary
page. 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. 3. (Trained technician only) Replace
the system board. Firmware Error : Sys Boot Status :
[ComputerSystemElementName]
encountered firmware error unrecoverable boot device failure. (ABR
Status)
implementation has detected that System Firmware
Error Unrecoverable boot device failure has occurred.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response: This is a UEFI detected event. The
UEFI(POST) error code for this event can be found in
the logged IMM message text. Please refer to the
UEFI(POST) error code in the "UEFI(POST) error code"
section of the Information Center for the appropriate
user response. Firmware Error : Sys Boot Status :
369
806f000f-220104xx 806f000f-220107xx
[ComputerSystemElementName]has
encountered a motherboard failure.
(ABR Status)
implementation has detected that a fatal motherboard
failure in the system.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
UEFI diagnostic code for this event can be found in the
logged IMM message text. Please refer to the
section of the Info Center for the appropriate user
response. Firmware Error : Sys Boot Status :
encountered firmware error unrecoverable keyboard failure. (ABR
Status)
Error Unrecoverable Keyboard failure has occurred.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
370
806f000f-22010axx 806f000f-22010bxx
806f000f-22010axx The System
encountered firmware error - no video
device detected. (ABR Status)
Error No video device detected has occurred.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
UEFI(POST) error for this event can be found in the
logged IMM message text. Please refer to the
806f000f-22010bxx Firmware BIOS (ROM) corruption
was detected on system
[ComputerSystemElementName] during
POST. (ABR Status)
Explanation: Firmware BIOS (ROM) corruption was
detected on the system during POST.
Severity: Info
Serviceable: Yes
SNMP Trap ID: 40
page: a. Restart the server. b. At the prompt, press F3 to
recover the firmware. 3. Update the server firmware to
the latest level (see Updating the firmware). 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 components one at a time,
restarting the server each time, to see if the problem
goes away. 5. If the problem remains, (trained service
technician) replace the system board. Firmware Error :
Sys Boot Status :
371
806f000f-22010cxx 806f000f-2201ffff
806f000f-22010cxx CPU voltage mismatch detected
on [ProcessorElementName]. (ABR
Status)
implementation has detected a CPU voltage mismatch
with the socket voltage.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
section of the Info Center for the appropriate user
response. Firmware Error : Sys Boot Status :
806f000f-2201ffff The System
encountered a POST Error. (ABR Status)
implementation has detected a Post Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
372
806f0013-1701xxxx 806f0021-2201xxxx
806f0013-1701xxxx A diagnostic interrupt has
occurred on system
[ComputerSystemElementName]. (NMI
State)
implementation has detected a Front Panel NMI /
Diagnostic Interrupt.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: If the NMI button has not been
pressed, complete the following steps: 1. Make sure
that the NMI button is not pressed. 2. Replace the
operator information panel cable. 3. Replace the
operator information panel.
806f0021-2201xxxx Fault in slot
[PhysicalConnectorSystemElementName]
on system
[ComputerSystemElementName]. (No
Op ROM Space)
implementation has detected a Fault in a slot.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Check the PCI LED. 2. Reseat the
affected adapters and riser card. 3. Update the server
firmware (UEFI and IMM) and adapter firmware.
the code. 4. Remove both adapters. 5. Replace the riser
card. 6. (Trained service technicians only) Replace the
system board.
373
806f0021-2582xxxx 806f0021-3001xxxx
on system
[ComputerSystemElementName]. (All
PCI Error)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
system board. One of PCI Error :
on system
[ComputerSystemElementName]. (PCI 1)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
system board. PCI 2 : PCI 3 :
374
806f0023-2101xxxx 806f0108-0a01xxxx
806f0023-2101xxxx Watchdog Timer expired for
[WatchdogElementName]. (IPMI
Watchdog)
implementation has detected a Watchdog Timer
Expired.
Severity: Info
(front and rear of the server), the air baffles are in place
and correctly installed, and the server cover is installed
and completely closed. 2. Make sure that the heat sink
for microprocessor n is installed correctly. 3. (Trained
806f0107-0302xxxx An Over-Temperature Condition
has been detected on
[ProcessorElementName]. (CPU 2)

Serviceable: No

implementation has detected an Over-Temperature
Condition Detected for Processor.

SNMP Trap ID:
Severity: Error
Serviceable: Yes
806f0028-2101xxxx Sensor [SensorElementName] is
unavailable or degraded on management
system [ComputerSystemElementName].
(TPM Cmd Failures)

implementation has detected a Sensor is Unavailable or
degraded.

operating. There are no obstructions to the airflow
(front and rear of the server), the air baffles are in place
and correctly installed, and the server cover is installed
and completely closed. 2. Make sure that the heat sink
for microprocessor n is installed correctly. 3. (Trained
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 0


Failed. (Power Supply 1)
SNMP Trap ID: 60

User response: 1. Turn off the server and disconnect
the power cords. Reconnect the power cords and restart
the server. 2. If the problem remains, (trained technician
only) replace the system board.

implementation has detected a Power Supply has
failed.
Severity: Error

has been detected on
Serviceable: Yes

implementation has detected an Over-Temperature
Condition Detected for Processor.
SNMP Trap ID: 4

User response: 1. Reseat power supply n. 2. If the
power-on LED is not lit and the power-supply error
LED is lit, replace power supply n. 3. If both the
power-on LED and the power-supply error LED are not
lit, see Power problems for more information. (n =
power supply number)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
operating. There are no obstructions to the airflow
375
806f0108-0a02xxxx 806f010c-2002xxxx
Failed. (Power Supply 2)
implementation has detected a Power Supply has
failed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response: 1. Reseat power supply n. 2. If the
power-on LED is not lit and the power-supply error
LED is lit, replace power supply n. 3. If both the
power-on LED and the power-supply error LED are not
lit, see Power problems for more information. (n =
power supply number)
been Power Cycled. (Host Power)
been power cycled.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f010c-2001xxxx Uncorrectable error detected for
[PhysicalMemoryElementName] on
Subsystem [MemoryElementName].
(DIMM 1)
implementation has detected a Memory uncorrectable
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response: 1. Check the IBM support website for
an applicable retain tip or firmware update that applies
376
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. 3. If the problem follows the DIMM,
replace the failing DIMM. 4. (Trained 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. 5. (Trained 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. 6. (Trained technician only)
Replace the affected microprocessor. 7. 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. 8. (Trained Service technician only) Replace the
affected microprocessor.
(DIMM 2)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f010c-2003xxxx 806f010c-2005xxxx
(DIMM 3)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 4)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

(DIMM 5)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
377
806f010c-2006xxxx 806f010c-2008xxxx
(DIMM 6)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 7)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
378

(DIMM 8)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f010c-2009xxxx 806f010c-200bxxxx
(DIMM 9)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f010c-200axxxx Uncorrectable error detected for
(DIMM 10)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f010c-200bxxxx Uncorrectable error detected for
(DIMM 11)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
379
806f010c-200cxxxx 806f010d-0400xxxx
806f010c-200cxxxx Uncorrectable error detected for
(DIMM 12)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
Subsystem [MemoryElementName]. (All
DIMMS)
error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
380

affected microprocessor. One of the DIMMs :
disabled due to a detected fault. (Drive
0)
implementation has detected a Drive was Disabled due
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response: 1. Run the hard disk drive diagnostic
test on drive n. 2. Reseat the following components: a.
Hard disk drive (wait 1 minute or more before
reinstalling the 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 (n
= hard disk drive number)
806f010d-0401xxxx 806f010d-0402xxxx
1)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
2)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
381
806f010d-0403xxxx 806f010d-0404xxxx
3)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
4)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
382
806f010d-0405xxxx 806f010d-0406xxxx
5)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
6)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
383
806f010d-0407xxxx 806f010f-2201xxxx
7)
to fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
806f010f-2201xxxx The System
encountered a firmware hang. (Firmware
Error)
implementation has detected a System Firmware Hang.
Severity: Error
Alert Category: System - Boot failure
Serviceable: Yes
SNMP Trap ID: 25
LEDs). 2. Update the server firmware on the primary
page. 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. 3. (Trained technician only) Replace
the system board.
384
806f0113-0301xxxx 806f0125-0b01xxxx
806f0113-0301xxxx A bus timeout has occurred on
(CPU 1 PECI)
implementation has detected a Bus Timeout.
Severity: Error
reset the front video cable in the system board. If the

specified sensor is PwrPaddle cable, complete the
following steps until problem is solved: 1. Reseat the
power paddle cable on the system board. 2. Replace the
power paddle cable. 3. (Trained technician only)
Replace the supercap n. (n = supercap number) 4.
(Trained technician only) Replace the system board.
Front Video :

806f0123-2101xxxx Reboot of system
initiated by [WatchdogElementName].
(IPMI Watchdog)
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Reseat the microprocessor, and then
restart the server. 2. Replace microprocessor n. (n =

implementation has detected a Reboot by a Watchdog
occurred.
Severity: Info
806f0113-0302xxxx A bus timeout has occurred on

(CPU 2 PECI)
Serviceable: No

implementation has detected a Bus Timeout.
SNMP Trap ID:
Severity: Error


806f0125-0b01xxxx [ManagedElementName] detected
as absent. (PCI Riser 1)
Serviceable: Yes

implementation has detected a Managed Element is
Absent.
SNMP Trap ID: 50

Severity: Info
Serviceable: No
806f011b-0701xxxx The connector

[PhysicalConnectorElementName] has
encountered a configuration error. (Front
USB)

implementation has detected an Interconnect
Configuration Error.
SNMP Trap ID:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: If the specified sensor is front USB
connector, reset the front USB cable on the system
board. If the specified sensor is front video connector,
385
806f0125-0b02xxxx 806f0207-2584xxxx
as absent. (PCI Riser 2)
Absent.

number)
Severity: Info
Serviceable: No

Failed with FRB1/BIST condition. (CPU
2)
SNMP Trap ID:

implementation has detected a Processor Failed FRB1/BIST condition.
Severity: Error
806f0125-0c01xxxx [ManagedElementName] detected

as absent. (Front Panel)
Absent.
Severity: Info
Serviceable: No
SNMP Trap ID:
Failed with FRB1/BIST condition. (CPU
1)
Serviceable: Yes
SNMP Trap ID: 40
User response: 1. Make sure that the latest levels of
number)


Failed with FRB1/BIST condition. (All
CPUs)
Severity: Error

Serviceable: Yes
Severity: Error
SNMP Trap ID: 40
Serviceable: Yes

SNMP Trap ID: 40
386

806f020d-0400xxxx 806f020d-0403xxxx
number) One of The CPUs :
806f020d-0400xxxx Failure Predicted on drive
[StorageVolumeElementName] for array
[ComputerSystemElementName]. (Drive
0)
implementation has detected an Array Failure is
Predicted.
Severity: Warning
board to the backplane. c. Hard disk drive backplane.

(n = hard disk drive number)
2)
Predicted.
Severity: Warning
Alert Category: System - Predicted Failure
Serviceable: Yes
SNMP Trap ID: 27

Serviceable: Yes
SNMP Trap ID: 27
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
1)
Predicted.
Severity: Warning

3)
Predicted.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27

Serviceable: Yes
SNMP Trap ID: 27

387
806f020d-0404xxxx 806f020d-0405xxxx
4)
Predicted.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
5)
Predicted.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
388
806f020d-0406xxxx 806f020d-0407xxxx
6)
Predicted.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
7)
Predicted.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
389
806f0223-2101xxxx 806f0308-0a02xxxx
806f0223-2101xxxx Powering off system
initiated by [WatchdogElementName].
(IPMI Watchdog)
implementation has detected a Poweroff by Watchdog
has occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
lost input. (Power Supply 1)
implementation has detected a Power Supply that has
input that has been lost.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: 1. Reconnect the power cords. 2. Check
power supply n LED. 3. See Power-supply LEDs for
more information. (n = power supply number)
lost input. (Power Supply 2)
input that has been lost.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: 1. Reconnect the power cords. 2. Check
power supply n LED. 3. See Power-supply LEDs for
more information. (n = power supply number)
390
806f030c-2001xxxx 806f030c-2003xxxx
806f030c-2001xxxx Scrub Failure for
(DIMM 1)
implementation has detected a Memory Scrub failure.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response: 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. Check the IBM support website for an
applicable retain tip or firmware update that applies to
this memory error. 2. Make sure that the DIMMs are
firmly seated and no foreign material is found in the
DIMM connector. Then, retry with the same DIMM. 3.
If the problem is related to a DIMM, replace the failing
DIMM indicated by the error LEDs. 4. If the problem
occurs on the same DIMM connector, 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. 5. (Trained 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. 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. 7. (Trained service
technician only) If the problem is related to
microprocessor socket pins, replace the system board.
(DIMM 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

(DIMM 3)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
391
806f030c-2004xxxx 806f030c-2006xxxx
(DIMM 4)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 5)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
392

(DIMM 6)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f030c-2007xxxx 806f030c-2009xxxx
(DIMM 7)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 8)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

(DIMM 9)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
393
806f030c-200axxxx 806f030c-200cxxxx
806f030c-200axxxx Scrub Failure for
(DIMM 10)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f030c-200bxxxx Scrub Failure for
(DIMM 11)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
394

806f030c-200cxxxx Scrub Failure for
(DIMM 12)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f030c-2581xxxx 806f0313-1701xxxx
DIMMS)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
One of the DIMMs :
806f0313-1701xxxx A software NMI has occurred on
(NMI State)
implementation has detected a Software NMI.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: 1. Check the device driver. 2. Reinstall
the device driver. 3. Update all device drivers to the
latest level. 4. Update the firmware (UEFI and IMM).
395
806f0323-2101xxxx 806f040c-2001xxxx
806f0323-2101xxxx Power cycle of system
initiated by watchdog
[WatchdogElementName]. (IPMI
Watchdog)
implementation has detected a Power Cycle by
Watchdog occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f040c-2001xxxx [PhysicalMemoryElementName]
Disabled on Subsystem
[MemoryElementName]. (DIMM 1)
implementation has detected that Memory has been
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: 1. Make sure the DIMM is installed
correctly. 2. If the DIMM was disabled because of a
memory fault (memory uncorrectable error or memory
logging limit reached), 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).
396
806f040c-2002xxxx 806f040c-2003xxxx
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
397
806f040c-2004xxxx 806f040c-2005xxxx
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
398
806f040c-2006xxxx 806f040c-2007xxxx
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
399
806f040c-2008xxxx 806f040c-2009xxxx
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
400
806f040c-200axxxx 806f040c-200bxxxx
806f040c-200axxxx [PhysicalMemoryElementName]
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
806f040c-200bxxxx [PhysicalMemoryElementName]
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
401
806f040c-200cxxxx 806f040c-2581xxxx
806f040c-200cxxxx [PhysicalMemoryElementName]
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU).
[MemoryElementName]. (All DIMMS)
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Utility (ASU). One of the DIMMs :
402
806f0413-2582xxxx 806f0507-0301xxxx
806f0413-2582xxxx A PCI PERR has occurred on
(PCIs)
implementation has detected a PCI PERR.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
affected adapters and riser cards. 3. Update the server
the code. 4. Remove both adapters. 5. Replace the PCIe
adapters. 6. Replace the riser card.
806f0507-0301xxxx [ProcessorElementName] has a
Configuration Mismatch. (CPU 1)
implementation has detected a Processor Configuration
Mismatch has occurred.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response: 1. Check the CPU LED. See more
information about the CPU LED in Light path
diagnostics. 2. Check for a server firmware update.
the code. 3. Make sure that the installed
microprocessors are compatible with each other. 4.
(Trained technician only) Reseat microprocessor n. 5.
(Trained technician only) Replace microprocessor n. (n
= microprocessor number)
403
806f0507-0302xxxx 806f0507-2584xxxx
Configuration Mismatch. (CPU 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
= microprocessor number)
Configuration Mismatch. (All CPUs)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
= microprocessor number) One of The CPUs :
404
806f050c-2001xxxx 806f050c-2004xxxx
806f050c-2001xxxx Memory Logging Limit Reached
for [PhysicalMemoryElementName] on
(DIMM 1)
implementation has detected that the Memory Logging
Limit has been Reached.
Severity: Warning
Serviceable: Yes
connector contains any foreign material or is damaged,

Remove the affected microprocessor and check the
microprocessor socket pins for any damaged pins. If a
damage is found, replace the system board. 6. (Trained
technician only) Replace the affected microprocessor.
(DIMM 3)

SNMP Trap ID: 43
Severity: Warning

microprocessor. 3. If the error still occurs on the same
DIMM, replace the affected DIMM. 4. (Trained
technician only) If the problem occurs on the same
DIMM connector, check the DIMM connector. If the
(DIMM 2)
Severity: Warning
Serviceable: Yes

Serviceable: Yes
SNMP Trap ID: 43
(DIMM 4)

SNMP Trap ID: 43
Severity: Warning


Serviceable: Yes
SNMP Trap ID: 43
405
806f050c-2005xxxx
(DIMM 5)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
406
806f050c-2006xxxx 806f050c-2009xxxx
(DIMM 6)
Severity: Warning
Serviceable: Yes

(DIMM 8)

SNMP Trap ID: 43
Severity: Warning

(DIMM 7)
Severity: Warning
Serviceable: Yes

Serviceable: Yes
SNMP Trap ID: 43
(DIMM 9)

SNMP Trap ID: 43
Severity: Warning


Serviceable: Yes
SNMP Trap ID: 43
407
806f050c-200axxxx
806f050c-200axxxx Memory Logging Limit Reached
(DIMM 10)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
408
806f050c-200bxxxx 806f050d-0400xxxx
806f050c-200bxxxx Memory Logging Limit Reached
(DIMM 11)
Severity: Warning
Serviceable: Yes

DIMMS)

SNMP Trap ID: 43
Severity: Warning

806f050c-200cxxxx Memory Logging Limit Reached
(DIMM 12)
Severity: Warning

Serviceable: Yes
SNMP Trap ID: 43
One of the DIMMs :
806f050d-0400xxxx Array
[ComputerSystemElementName] is in
critical condition. (Drive 0)

Serviceable: Yes

implementation has detected that an Array is Critical.
SNMP Trap ID: 43
Severity: Error

Serviceable: Yes
SNMP Trap ID: 5
User response: 1. Make sure that the RAID adapter
firmware and hard disk drive firmware are at the latest
level. 2. Make sure that the SAS cable is connected
409
806f050d-0401xxxx 806f050d-0402xxxx
correctly. 3. Replace the SAS cable. 4. Check backplane
cable connection. 5. Replace the RAID adapter. 6.
Replace the hard disk drive that is indicated by a lit
status LED.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
410
806f050d-0403xxxx 806f050d-0404xxxx
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
411
806f050d-0405xxxx 806f050d-0406xxxx
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
412
806f050d-0407xxxx 806f0513-2582xxxx
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
status LED.
806f0513-2582xxxx A PCI SERR has occurred on
(PCIs)
implementation has detected a PCI SERR.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
the code. 4. Make sure that the adapter is supported.
For a list of supported optional devices, see
http://www.ibm.com/systems/info/x86servers/
serverproven/compat/us/. 5. Remove both adapters. 6.
Replace the PCIe adapters. 7. Replace the riser card.
413
806f052b-2201xxxx 806f0607-0301xxxx
806f052b-2201xxxx Invalid or Unsupported firmware
or software was detected on system
[ComputerSystemElementName]. (IMM2
FW Failover)
implementation has detected an Invalid/Unsupported
Firmware/Software Version.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
page by restarting the server. 3. Update the server
firmware to the latest level (see Updating the
firmware). Important: Some cluster solutions require
before you update the code. 4. Remove components
one at a time, restarting the server each time, to see if
the problem goes away. 5. If the problem remains,
(trained service technician) replace the system board.
806f0607-0301xxxx An SM BIOS Uncorrectable CPU
complex error for
[ProcessorElementName] has asserted.
(CPU 1)
SM BIOS Uncorrectable CPU complex error has
asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response: 1. Make sure that the installed
microprocessors are compatible with each other (see
Installing a microprocessor and heat sink for
information about microprocessor requirements). 2.
Update the server firmware to the latest level (see
Updating the firmware). 3. (Trained technician only)
Replace the incompatible microprocessor.
414
806f0607-0302xxxx 806f0607-2584xxxx
complex error for
(CPU 2)
asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
Replace the incompatible microprocessor.
complex error for
(All CPUs)
asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
Replace the incompatible microprocessor. One of The
CPUs :
415
806f0608-1301xxxx 806f060d-0400xxxx
a Configuration Mismatch. (PS
Configuration)
implementation has detected a Power Supply with a
Configuration Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response: 1. Make sure that the power supplies
installed are with the same rating or wattage. 2.
Reinstall the power supplies with the same rating or
wattage.
failed. (Drive 0)
implementation has detected that an Array Failed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
correctly. 3. Replace the SAS cable. 4. Replace the RAID
adapter. 5. Replace the hard disk drive that is indicated
by a lit status LED.
416
806f060d-0401xxxx 806f060d-0402xxxx
failed. (Drive 1)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
failed. (Drive 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
417
806f060d-0403xxxx 806f060d-0404xxxx
failed. (Drive 3)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
failed. (Drive 4)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
418
806f060d-0405xxxx 806f060d-0406xxxx
failed. (Drive 5)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
failed. (Drive 6)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
419
806f060d-0407xxxx 806f070c-2001xxxx
failed. (Drive 7)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
806f070c-2001xxxx Configuration Error for
(DIMM 1)
implementation has detected a Memory DIMM
configuration error has been corrected.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response: Make sure that DIMMs are installed in
the correct sequence and have the same size, type,
speed, and technology.
420
806f070c-2002xxxx 806f070c-2003xxxx
(DIMM 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 3)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
421
806f070c-2004xxxx 806f070c-2005xxxx
(DIMM 4)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 5)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
422
806f070c-2006xxxx 806f070c-2007xxxx
(DIMM 6)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 7)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
423
806f070c-2008xxxx 806f070c-2009xxxx
(DIMM 8)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
(DIMM 9)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
424
806f070c-200axxxx 806f070c-200bxxxx
806f070c-200axxxx Configuration Error for
(DIMM 10)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
806f070c-200bxxxx Configuration Error for
(DIMM 11)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
425
806f070c-200cxxxx 806f070c-2581xxxx
806f070c-200cxxxx Configuration Error for
(DIMM 12)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
DIMMS)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
speed, and technology. One of the DIMMs :
426
806f070d-0400xxxx 806f070d-0402xxxx
806f070d-0400xxxx Rebuild in progress for Array in
(Drive 0)
implementation has detected that an Array Rebuild is
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 1)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 2)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
427
806f070d-0403xxxx 806f070d-0405xxxx
(Drive 3)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 4)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 5)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
428
806f070d-0406xxxx 806f072b-2201xxxx
(Drive 6)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 7)
in Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f072b-2201xxxx A successful software or
firmware change was detected on
(Bkup Auto Update)
implementation has detected a Successful Software or
Firmware Change.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only. ROM
Recovery :
429
806f0807-0301xxxx 806f0807-2584xxxx
806f0807-0301xxxx [ProcessorElementName] has been
Disabled. (CPU 1)
implementation has detected a Processor has been
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Disabled. (CPU 2)
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Disabled. (All CPUs)
Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only. One of
The CPUs :
430
806f0813-2581xxxx 806f0813-2582xxxx
806f0813-2581xxxx A Uncorrectable Bus Error has
occurred on system
[ComputerSystemElementName].
(DIMMs)
implementation has detected a Bus Uncorrectable Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
(Trained technician only) Remove the failing
microprocessor from the system board (see Removing a
microprocessor and heat sink). 3. Check for a server
firmware update. Important: Some cluster solutions
cluster solution before you update the code. 4. Make
sure that the two microprocessors are matching. 5.
occurred on system
[ComputerSystemElementName]. (PCIs)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
431
806f0813-2584xxxx 806f0823-2101xxxx
occurred on system
[ComputerSystemElementName]. (CPUs)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
806f0823-2101xxxx Watchdog Timer interrupt
occurred for [WatchdogElementName].
(IPMI Watchdog)
implementation has detected a Watchdog Timer
interrupt occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
432
806f090c-2001xxxx 806f090c-2003xxxx
on Subsystem [MemoryElementName]
Throttled. (DIMM 1)
implementation has detected Memory has been
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response: 1. Reseat the DIMM, and then restart
the server. 2. Replace DIMM n. (n = DIMM number)
Throttled. (DIMM 2)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled. (DIMM 3)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
433
806f090c-2004xxxx 806f090c-2006xxxx
Throttled. (DIMM 4)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled. (DIMM 5)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled. (DIMM 6)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
434
806f090c-2007xxxx 806f090c-2009xxxx
Throttled. (DIMM 7)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled. (DIMM 8)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled. (DIMM 9)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
435
Throttled. (DIMM 10)
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
Throttled.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
436
806f0a07-0301xxxx 806f0a07-0302xxxx
806f0a07-0301xxxx [ProcessorElementName] is
operating in a Degraded State. (CPU 1)
implementation has detected a Processor is running in
the Degraded state.
Severity: Warning
Alert Category: Warning - CPU
Serviceable: Yes
SNMP Trap ID: 42
specifications. 3. Make sure that the heat sink for
806f0a07-0302xxxx [ProcessorElementName] is
implementation has detected a Processor is running in
the Degraded state.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 42
specifications. 3. Make sure that the heat sink for
437
806f0a0c-2001xxxx 806f0a0c-2002xxxx
806f0a0c-2001xxxx An Over-Temperature Condition
has been detected on the
(DIMM 1)
implementation has detected an Over Temperature
Condition for Memory that has been Detected.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
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 ambient temperature is within
the specifications. 3. If a fan has failed, complete the
action for a fan failure. 4. Replace DIMM n. (n = DIMM
number)
(DIMM 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
438
(DIMM 3)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
(DIMM 4)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
439
(DIMM 5)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
(DIMM 6)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
440
(DIMM 7)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
(DIMM 8)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
441
806f0a0c-2009xxxx 806f0a0c-200axxxx
(DIMM 9)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
806f0a0c-200axxxx An Over-Temperature Condition
(DIMM 10)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
442
806f0a0c-200bxxxx 806f0a0c-200cxxxx
806f0a0c-200bxxxx An Over-Temperature Condition
(DIMM 11)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
806f0a0c-200cxxxx An Over-Temperature Condition
(DIMM 12)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
number)
443
806f0a13-0301xxxx 81010002-0701xxxx
806f0a13-0301xxxx A Fatal Bus Error has occurred on
(CPU 1 PECI)
implementation has detected a Bus Fatal Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
806f0a13-0302xxxx A Fatal Bus Error has occurred on
(CPU 2 PECI)
implementation has detected a Bus Fatal Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
low (lower non-critical) has deasserted.
(CMOS Battery)
implementation has detected a Lower Non-critical
sensor going low has deasserted.
Severity: Info
Alert Category: Warning - Voltage
Serviceable: No
SNMP Trap ID: 13
444
81010202-0701xxxx 81010204-1d02xxxx
low (lower critical) has deasserted.
(CMOS Battery)
going low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 1
User response: No action; information only. SysBrd
12V : SysBrd 3.3V : SysBrd 5V :
low (lower critical) has deasserted. (Fan
1Aa Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
1Ab Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
445
81010204-1d03xxxx 81010204-1d05xxxx
1Ba Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
1Bb Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
2Aa Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
446
81010204-1d06xxxx 81010204-1d08xxxx
2Ab Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
2Ba Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
2Bb Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
447
81010204-1d09xxxx 81010204-1d0bxxxx
3Aa Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
81010204-1d0axxxx Numeric sensor
3Ab Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
81010204-1d0bxxxx Numeric sensor
3Ba Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
448
81010204-1d0cxxxx 81010701-0c01xxxx
81010204-1d0cxxxx Numeric sensor
3Bb Tach)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
high (upper non-critical) has deasserted.
(FHHL Temp)
sensor going high has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 12
LowProfile Temp : Raid Temp :
(Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
449
81010701-1401xxxx 81010701-2d01xxxx
(CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(PCH Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
450
81010901-0701xxxx 81010901-1401xxxx
high (upper critical) has deasserted.
(FHHL Temp)
going high has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
451
81010901-1402xxxx 81010902-0701xxxx
(CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(PCH Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(SysBrd 12V)
Severity: Info
Serviceable: No
SNMP Trap ID: 1
User response: No action; information only. SysBrd
3.3V : SysBrd 5V :
452
81010b01-0701xxxx 81010b01-1401xxxx
deasserted. (FHHL Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010b01-0c01xxxx Numeric sensor
deasserted. (Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
deasserted. (CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
453
81010b01-1402xxxx 81030006-2101xxxx
deasserted. (CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010b01-2d01xxxx Numeric sensor
deasserted. (PCH Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
asserted. (Sig Verify Fail)
implementation has detected a Sensor has asserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
454
81030012-2301xxxx 81050108-0a02xxxx
asserted. (OS RealTime Mod)
implementation has detected a Sensor has asserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
indicated limit no longer exceeded. (PS
1 CS)
implementation has detected a Sensor limit is no longer
exceeded.
Severity: Info
Serviceable: No
SNMP Trap ID:
indicated limit no longer exceeded. (PS
2 CS)
implementation has detected a Sensor limit is no longer
exceeded.
Severity: Info
Serviceable: No
SNMP Trap ID:
455
8107010f-2201xxxx 81070201-0301xxxx
deasserted the transition from normal to
non-critical state. (GPT Status)
implementation has detected that a Sensor has
deasserted a transition to non-critical from normal.
Severity: Info
Serviceable: No
SNMP Trap ID: 60
User response: No action; information only. TXT ACM
Module :
deasserted the transition from normal to
non-critical state. (No PCI I/O Space)
implementation has detected that a Sensor has
deasserted a transition to non-critical from normal.
Severity: Info
Serviceable: No
SNMP Trap ID: 60
transitioned to a less severe state from
critical. (CPU 1 OverTemp)
implementation has detected a Sensor transition to less
severe from critical.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
456
81070201-0302xxxx 81070208-0a01xxxx
critical. (CPU 2 OverTemp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
critical. (SysBrd Vol Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 1
critical. (PS 1 Fan Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: No action; information only. PS 1 OP
Fault : PS 1 Therm Fault :
457
81070208-0a02xxxx 81070214-2201xxxx
critical. (PS 2 Fan Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: No action; information only. PS 2 OP
Fault : PS 2 Therm Fault :
critical. (No PCI I/O Space)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
critical. (TPM Lock)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
458
81070219-0701xxxx 8107021b-0302xxxx
critical. (SysBrd Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
critical. (CPU 1 QPILinkErr)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
critical. (CPU 2 QPILinkErr)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
459
81070301-0301xxxx 81070608-0a01xxxx
deasserted the transition to
non-recoverable from a less severe state.
(CPU 1 OverTemp)
implementation has detected that the Sensor transition
to non-recoverable from less severe has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
non-recoverable from a less severe state.
(CPU 2 OverTemp)
to non-recoverable from less severe has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
non-recoverable. (PS 1 OC Fault)
to non-recoverable has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: No action; information only. PS 1 OV
Fault : PS 1 UV Fault : PS 1 VCO Fault :
460
81070608-0a02xxxx 810b010a-1e82xxxx
non-recoverable. (PS 2 OC Fault)
to non-recoverable has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: No action; information only. PS 2 OV
Fault : PS 2 UV Fault : PS 2 VCO Fault :
deasserted. (Cooling Zone 1)
Redundacy Lost has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11
Severity: Info
Serviceable: No
SNMP Trap ID: 11
461
810b010c-2581xxxx 810b050a-1e81xxxx
810b010c-2581xxxx Redundancy Lost for
deasserted. (Backup Memory)
Severity: Info
Serviceable: No
SNMP Trap ID: 41
810b030c-2581xxxx Non-redundant:Sufficient
Resources from Redundancy Degraded
or Fully Redundant for
Redundancy Set has transitioned from
Non-redundant:Sufficient Resources.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
Resources for
Severity: Info
Serviceable: No
SNMP Trap ID: 11
462
810b050a-1e82xxxx 816f0007-0301xxxx
Resources for
Severity: Info
Serviceable: No
SNMP Trap ID: 11
810b050c-2581xxxx Non-redundant:Insufficient
Resources for
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Recovered from IERR. (CPU 1)
implementation has detected a Processor Recovered IERR Condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
463
816f0007-0302xxxx 816f0008-0a02xxxx
Recovered from IERR. (CPU 2)
implementation has detected a Processor Recovered IERR Condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
been removed from container
Supply 1)
removed.
Severity: Info
Serviceable: No
SNMP Trap ID:
been removed from container
Supply 2)
removed.
Severity: Info
Serviceable: No
SNMP Trap ID:
464
816f0009-1301xxxx 816f000d-0403xxxx
been turned on. (Host Power)
been Enabled.
Severity: Info
User response: 1. Reseat hard disk drive n.(n = hard

disk drive number). Wait 1 minute or more before
reinstalling the drive. 2. Replace the hard disk drive. 3.
Make sure that the disk firmware and RAID controller
firmware are at the latest level. 4. Check the SAS cable.
removed from unit
[PhysicalPackageElementName]. (Drive
2)
Alert Category: System - Power On

Serviceable: No

implementation has detected a Drive has been
Removed.
Severity: Error
SNMP Trap ID: 24

removed from unit
0)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
Serviceable: Yes
removed from unit
3)

SNMP Trap ID: 5

Removed.
Severity: Error

removed from unit
1)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
Serviceable: Yes
SNMP Trap ID: 5
465
816f000d-0404xxxx 816f000d-0405xxxx
removed from unit
4)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
removed from unit
5)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
466
816f000d-0406xxxx 816f000d-0407xxxx
removed from unit
6)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
removed from unit
7)
Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
467
816f000f-2201ffff 816f0021-2201xxxx
816f000f-2201ffff The System
detected a POST Error deassertion.
(ABR Status)
implementation has detected that Post Error has
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. Firmware
Error : Sys Boot Status :
816f0013-1701xxxx System
recovered from a diagnostic interrupt.
(NMI State)
implementation has detected a recovery from a Front
Panel NMI / Diagnostic Interrupt
Severity: Info
Serviceable: No
SNMP Trap ID: 50
816f0021-2201xxxx Fault condition removed on slot
[PhysicalConnectorElementName] on
(No Op ROM Space)
implementation has detected a Fault condition in a slot
has been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
468
816f0021-2582xxxx 816f0028-2101xxxx
(All PCI Error)
has been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
PCI Error :
(PCI 1)
has been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. PCI 2 :
PCI 3 :
816f0028-2101xxxx Sensor [SensorElementName] has
returned to normal on management
(TPM Cmd Failures)
implementation has detected a Sensor returned from
degraded/unavailable/failure.
Severity: Info
Serviceable: No
SNMP Trap ID: 60
469
816f0107-0301xxxx 816f0108-0a01xxxx
has been removed on
implementation has detected a Over-Temperature
Condition has been Removed for Processor.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
has been removed on
implementation has detected a Over-Temperature
Condition has been Removed for Processor.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
returned to OK status. (Power Supply 1)
implementation has detected a Power Supply return to
normal operational status.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
470
816f0108-0a02xxxx 816f010c-2002xxxx
returned to OK status. (Power Supply 2)
implementation has detected a Power Supply return to
normal operational status.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
816f010c-2001xxxx Uncorrectable error recovery
detected for
(DIMM 1)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
detected for
(DIMM 2)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
471
816f010c-2003xxxx 816f010c-2008xxxx
detected for
(DIMM 3)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
detected for
(DIMM 4)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
detected for
(DIMM 5)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
472

detected for
(DIMM 6)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
detected for
(DIMM 7)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
detected for
(DIMM 8)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-2009xxxx 816f010c-200axxxx
detected for
(DIMM 9)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-200axxxx Uncorrectable error recovery
detected for
(DIMM 10)
error recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
473
816f010c-200bxxxx 816f010d-0402xxxx
816f010c-200bxxxx Uncorrectable error recovery
detected for
(DIMM 11)
error recovery.

the DIMMs :
enabled. (Drive 0)
implementation has detected a Drive was Enabled.
Severity: Info
Severity: Info
Serviceable: No
Serviceable: No
SNMP Trap ID: 41
SNMP Trap ID: 5
816f010c-200cxxxx Uncorrectable error recovery

detected for
(DIMM 12)

enabled. (Drive 1)

error recovery.
Severity: Info
Severity: Info
Serviceable: No
Serviceable: No
SNMP Trap ID: 5
SNMP Trap ID: 41

detected for
DIMMS)
error recovery.

enabled. (Drive 2)
Severity: Info
Serviceable: No
Severity: Info
SNMP Trap ID: 5
Serviceable: No

SNMP Trap ID: 41
474
816f010d-0403xxxx 816f010d-0405xxxx
enabled. (Drive 3)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
enabled. (Drive 4)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
enabled. (Drive 5)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
475
816f010d-0406xxxx 816f010f-2201xxxx
enabled. (Drive 6)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
enabled. (Drive 7)
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010f-2201xxxx The System
recovered from a firmware hang.
(Firmware Error)
implementation has recovered from a System Firmware
Hang.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
476
816f0113-0301xxxx 816f0113-0302xxxx
recovered from a bus timeout. (CPU 1
PECI)
implemenation has detected that a system has
recovered from a Bus Timeout.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: 1. (Trained technician only) Replace
microprocessor n (see Removing a microprocessor and
heat sink and Replacing a microprocessor and heat
sink). 2. If the problem persists and there is no other
CPU with the same error indication, replace the system
board. 3. (Trained technician only) Replace the system
the system board). (n = microprocessor number)
recovered from a bus timeout. (CPU 2
PECI)
implemenation has detected that a system has
recovered from a Bus Timeout.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
477
816f011b-0701xxxx 816f0125-0b02xxxx
816f011b-0701xxxx The connector
[PhysicalConnectorElementName]
configuration error has been repaired.
(Front USB)
implementation has detected an Interconnect
Configuration was Repaired.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. Front
Video :
as present. (PCI Riser 1)
now Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
as present. (PCI Riser 2)
now Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
478
816f0125-0c01xxxx 816f0207-0302xxxx
816f0125-0c01xxxx [ManagedElementName] detected
as present. (Front Panel)
now Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
Recovered from FRB1/BIST condition.
(CPU 1)
implementation has detected a Processor Recovered FRB1/BIST condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
(CPU 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 40
479
816f0207-2584xxxx 816f020d-0401xxxx
(All CPUs)
Severity: Info
Serviceable: No
SNMP Trap ID: 40
The CPUs :
816f020d-0400xxxx Failure no longer Predicted on
drive [StorageVolumeElementName] for
array [ComputerSystemElementName].
(Drive 0)
implementation has detected an Array Failure is no
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
(Drive 1)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
480
816f020d-0402xxxx 816f020d-0404xxxx
(Drive 2)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
(Drive 3)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
(Drive 4)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
481
816f020d-0405xxxx 816f020d-0407xxxx
(Drive 5)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
(Drive 6)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
(Drive 7)
longer Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
482
816f0308-0a01xxxx 816f030c-2001xxxx
returned to a Normal Input State.
(Power Supply 1)
input that has returned to normal.
Severity: Info
Serviceable: No
SNMP Trap ID:
returned to a Normal Input State.
(Power Supply 2)
input that has returned to normal.
Severity: Info
Serviceable: No
SNMP Trap ID:
Subsystem [MemoryElementName]has
recovered. (DIMM 1)
implementation has detected a Memory Scrub failure
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
483
816f030c-2002xxxx 816f030c-2004xxxx
recovered. (DIMM 2)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (DIMM 3)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (DIMM 4)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
484
816f030c-2005xxxx 816f030c-2007xxxx
recovered. (DIMM 5)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (DIMM 6)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (DIMM 7)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
485
816f030c-2008xxxx 816f030c-200axxxx
recovered. (DIMM 8)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (DIMM 9)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200axxxx Scrub Failure for
recovered. (DIMM 10)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
486
816f030c-200bxxxx 816f030c-2581xxxx
816f030c-200bxxxx Scrub Failure for
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200cxxxx Scrub Failure for
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
recovered. (All DIMMS)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
the DIMMs :
487
816f0313-1701xxxx 816f040c-2002xxxx
recovered from an NMI. (NMI State)
implementation has detected a Software NMI has been
Recovered from.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
Enabled on Subsystem
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
488
816f040c-2003xxxx 816f040c-2005xxxx
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
489
816f040c-2006xxxx 816f040c-2008xxxx
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
490
816f040c-2009xxxx 816f040c-200bxxxx
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
491
816f040c-200cxxxx 816f0413-2582xxxx
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
[MemoryElementName]. (All DIMMS)
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
the DIMMs :
816f0413-2582xxxx A PCI PERR recovery has
occurred on system
[ComputerSystemElementName]. (PCIs)
implementation has detected a PCI PERR recovered.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
492
816f0507-0301xxxx 816f0507-2584xxxx
Recovered from a Configuration
Mismatch. (CPU 1)
implementation has Recovered from a Processor
Configuration Mismatch.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
Mismatch. (CPU 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 40
Mismatch. (All CPUs)
Severity: Info
Serviceable: No
SNMP Trap ID: 40
The CPUs :
493
816f050c-2001xxxx 816f050c-2003xxxx
816f050c-2001xxxx Memory Logging Limit Removed
(DIMM 1)
Limit has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 3)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
494
816f050c-2004xxxx 816f050c-2006xxxx
(DIMM 4)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 5)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 6)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
495
816f050c-2007xxxx 816f050c-2009xxxx
(DIMM 7)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 8)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
(DIMM 9)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
496
816f050c-200axxxx Memory Logging Limit Removed
(DIMM 10)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200bxxxx Memory Logging Limit Removed
(DIMM 11)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200cxxxx Memory Logging Limit Removed
(DIMM 12)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
497
816f050c-2581xxxx 816f050d-0401xxxx
DIMMS)
Severity: Info
Serviceable: No
SNMP Trap ID: 43
the DIMMs :
816f050d-0400xxxx Critical Array
deasserted. (Drive 0)
implementation has detected that an Critiacal Array has
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
498
816f050d-0402xxxx 816f050d-0404xxxx
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
499
816f050d-0405xxxx 816f050d-0407xxxx
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
500
816f0607-0301xxxx 816f0607-2584xxxx
complex error for
[ProcessorElementName] has deasserted.
(CPU 1)
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
complex error for
(CPU 2)
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
complex error for
(All CPUs)
deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
The CPUs :
501
816f0608-1301xxxx 816f060d-0401xxxx
816f0608-1301xxxx [PowerSupplyElementName]
Configuration is OK. (PS Configuration)
implementation when a Power Supply configuration is
OK.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
816f060d-0400xxxx Array in system
been restored. (Drive 0)
implementation has detected that a Failed Array has
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
502
816f060d-0402xxxx 816f060d-0404xxxx
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
503
816f060d-0405xxxx 816f060d-0407xxxx
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
been Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
504
816f070c-2001xxxx 816f070c-2003xxxx
816f070c-2001xxxx Configuration error for
deasserted. (DIMM 1)
configuration error has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
505
816f070c-2004xxxx 816f070c-2006xxxx
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
506
816f070c-2007xxxx 816f070c-2009xxxx
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
Severity: Info
Serviceable: No
SNMP Trap ID: 41
507
816f070c-200axxxx Configuration error for
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200bxxxx Configuration error for
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200cxxxx Configuration error for
Severity: Info
Serviceable: No
SNMP Trap ID: 41
508
816f070c-2581xxxx 816f070d-0401xxxx
deasserted. (All DIMMS)
Severity: Info
Serviceable: No
SNMP Trap ID: 41
the DIMMs :
816f070d-0400xxxx Rebuild completed for Array in
(Drive 0)
implementation has detected that an Array Rebuild has
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 1)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
509
816f070d-0402xxxx 816f070d-0404xxxx
(Drive 2)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 3)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 4)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
510
816f070d-0405xxxx 816f070d-0407xxxx
(Drive 5)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 6)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
(Drive 7)
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
511
816f0807-0301xxxx 816f0807-2584xxxx
Enabled. (CPU 1)
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled. (CPU 2)
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Enabled. (All CPUs)
Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
The CPUs :
512
816f0813-2581xxxx 816f0813-2584xxxx
recovered from an Uncorrectable Bus
Error. (DIMMs)
implementation has detected a that a system has
recovered from a Bus Uncorrectable Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
Error. (PCIs)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
Error. (CPUs)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
513
816f090c-2001xxxx 816f090c-2003xxxx
on Subsystem [MemoryElementName] is
no longer Throttled. (DIMM 1)
implementation has detected Memory is no longer
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
514
816f090c-2004xxxx 816f090c-2006xxxx
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
515
816f090c-2007xxxx 816f090c-2009xxxx
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
516
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:
517
816f0a07-0301xxxx 816f0a0c-2001xxxx
816f0a07-0301xxxx The Processor
[ProcessorElementName] is no longer
implementation has detected a Processor is no longer
running in the Degraded state.
Severity: Info
Serviceable: No
SNMP Trap ID: 42
816f0a07-0302xxxx The Processor
[ProcessorElementName] is no longer
implementation has detected a Processor is no longer
running in the Degraded state.
Severity: Info
Serviceable: No
SNMP Trap ID: 42
has been removed on the
(DIMM 1)
Condition for Memory that has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
518
(DIMM 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
SNMP Trap ID: 0

(DIMM 3)
Severity: Info
SNMP Trap ID: 0

(DIMM 4)

Serviceable: No
SNMP Trap ID: 0
SNMP Trap ID: 0

(DIMM 6)
Severity: Info
Serviceable: No
Serviceable: No


(DIMM 5)
Severity: Info
Serviceable: No
Severity: Info

(DIMM 7)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
519
(DIMM 8)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(DIMM 9)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
520
816f0a0c-200axxxx 816f0a0c-200bxxxx
816f0a0c-200axxxx An Over-Temperature Condition
(DIMM 10)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a0c-200bxxxx An Over-Temperature Condition
(DIMM 11)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
521
816f0a0c-200cxxxx 816f0a13-0301xxxx
816f0a0c-200cxxxx An Over-Temperature Condition
(DIMM 12)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a13-0301xxxx System
recovered from a Fatal Bus Error. (CPU 1
PECI)
implementation has detected that a system has
recovered from a Bus Fatal Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
522
816f0a13-0302xxxx
816f0a13-0302xxxx System
recovered from a Fatal Bus Error. (CPU 2
PECI)
implementation has detected that a system has
recovered from a Bus Fatal Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
523
524

This section details the UEFI (POST) error codes.
UEFI (POST) diagnostic error codes can be generated when the server starts up or
while the server is running. UEFI (POST) codes are logged in the Integrated
Management Module II (IMM2) event log in the server.
For each event code, the following fields are displayed:
Event identifier
An identifier that uniquely identifies an event.
Event description
The logged message string that appears for an event.
Explanation
Additional information to explain why the event occurred.
Severity
An indication of the level of concern for the condition. The severity is
abbreviated in the event log to the first character. The following severities
can be displayed:
Table 17. Event severity levels
Severity
Description
Informational
An informational message is something that was recorded for

audit purposes, usually a user action or a change of states that is
normal behavior.
Warning
A warning is not as severe as an error, but if possible, the

condition should be corrected before it becomes an error. It
might also be a condition that requires additional monitoring or
maintenance.
Error
An error typically indicates a failure or critical condition that

impairs service or an expected function.
User response
Indicate the actions that you should take to resolve the event.
Perform the steps listed in this section in the order shown until the
problem is solved. After you perform all of the actions that are described
in this field, if you cannot solve the problem, contact IBM support.
The following is the list of the UEFI (POST) error codes and suggested actions to
correct the detected problems.
525
I.11002 I.18005
I.11002
[I.11002] A processor mismatch has been

detected between one or more
processors in the system.
Explanation: One or More Mismatched Processors

Detected
Severity: Error
User response: Complete the following steps:
1.
This message could occur with messages about

other Processor configuration problems. Resolve
those messages first.
2.
If the problem persists, ensure that matching

processors are installed (i.e., matching option part
numbers, etc)
3.
Verify that the Processors are installed in the

correct sockets according to the service information
for this product. If not, correct that problem.
4.
Check IBM support site for an applicable service

bulletin or firmware update that applies to this
Processor error.
5.
(Trained Service technician only) Replace

mismatching processor. Inspect Processor socket and
replace the system board first if socket is damaged.
I.18005
[I.18005] A discrepancy has been

detected in the number of cores reported
by one or more processor packages
within the system.
Explanation: Processors have mismatched number of

cores
Severity: Error
1.
If this is a newly installed option, ensure that

matching Processors are installed in the correct
Processor sockets according to the service
information for this product.
2.

bulletin that applies to this Processor error.
3.
(Trained Service technician only) Replace Processor.

Inspect Processor socket and replace the system
board first if socket is damaged.
526
I.18006 I.18008
I.18006
[I.18006] A mismatch between the

maximum allowed QPI link speed has
been detected for one or more processor
packages.
Explanation: Processors have mismatched QPI Speed

Severity: Error
1.
If this is a newly installed option, ensure that

matching Processor CPUs are installed in the correct
ProcessorCPU sockets according to the service
information for this product
2.
Check IBM support site for an applicable retain

tipservice bulletin or firmware update that applies
to this Processor error.
3.

I.18007
[I.18007] A power segment mismatch has

packages.
Explanation: Processors have mismatched Power

Segments
Severity: Error
1.
Processors installed do not have the same power

requirements
2.
Ensure that all Processors have matching power

requirements (such as 65, 95, or 130 Watts)
3.
If power requirements match, check IBM support

site for an applicable service bulletin or firmware
update that applies to this Processor error.
4.

board first if socket is damaged
I.18008
[I.18008] A mismatch has been detected

between Processors frequency and
DDR3 DIMMs frequency.
Explanation: Processors have mismatched Internal

DDR3 Frequency
Severity: Error
1.
Verify that matching DIMMs are installed in the

correct population sequence, according to the
service information for this product. {Add link to
Memory chart.} Correct any configuration issues
found.
2.
(Trained Service technician only) Replace associated

Processor. Inspect Processor socket and replace the
system board first if socket is damaged
527
I.18009 I.1800A
I.18009
[I.18009] A core speed mismatch has

packages.
Explanation: Processors have mismatched Core Speed

Severity: Error
1.
Verify that matching processors are installed in the

correct processor sockets according to the service
information for this product. Correct any mismatch
issues found.
2.

Processor error.
3.

I.1800A
[I.1800A] A mismatch has been detected

between the speed at which a QPI link
has trained between two or more
processor packages.
Explanation: Processors have mismatched Bus Speed

Severity: Error
1.
Verify that the Processor is a valid option that is

listed as a Server Proven device for this system. If
not, remove the Processor and install a Server
Proven one.
2.
Verify that matching Processors are installed in the

correct Processor sockets according to the service
found.
3.

processor error.
4.
(Trained Service technician only) Replace the

Processor. Inspect Processor socket and replace the
system board first if socket is damaged
528
I.1800B I.1800D
I.1800B
[I.1800B] A cache size mismatch has

packages.
Explanation: Processors have one or more cache levels

with mismatched size
Severity: Error
1.
Verify that matching processors are installed in the

correct processor sockets according to the service
found.
2.

Processor error.
3.

system board.
I.1800C
[I.1800C] A cache type mismatch has

packages.

with mismatched type
Severity: Error
1.

2.

Processor error.
3.

system board.
I.1800D
[I.1800D] A cache associativity mismatch

has been detected for one or more
processor packages.

with mismatched associativity
Severity: Error
1.

2.

Processor error.
3.

system board.
529
I.1800E I.18010
I.1800E
[I.1800E] A processor model mismatch

processor packages.
Explanation: Processors have mismatched Model

Number
Severity: Error
1.

2.

Processor error.
3.

system board.
I.1800F
[I.1800F] A processor family mismatch

processor packages.
Explanation: Processors have mismatched Family

Severity: Error
1.

information for this product
2.

Processor error.
3.

system board.
I.18010
[I.18010] A processor stepping mismatch

processor packages.
Explanation: Processors of the same model have

mismatched Stepping ID
Severity: Error
1.

2.

Processor error.
3.

system board.
530
I.2018002 I.2018003
I.2018002
[I.2018002] The device found at Bus %

Device % Function % could not be
configured due to resource constraints.
The Vendor ID for the device is % and
the Device ID is %.
Explanation: OUT_OF_RESOURCES (PCI Option

ROM)
Severity: Info
1.
If this PCIe device and/or any attached cables

were recently installed, moved, serviced or
upgraded, reseat adapter and any attached cables.
2.
Check IBM support site for any applicable service

bulletin or UEFI or adapter firmware update that
applies to this error. NOTE: It may be necessary to
disable unused option ROMs from UEFI F1 setup or
ASU or using adapter manufacturer utilities so that
adapter firmware can be updated.
3.
Move card to a different slot. If slot not available or

error re-occurs, replace adapter.
4.
(Trained Service technician only) If adapter was

moved to a different slot and error did not re-occur,
verify that this is not a system limitation and then
replace the system board. Also, if this is not the
initial installation and the error persists after
adapter replacement, replace system board.
I.2018003
[I.2018003] A bad option ROM

checksum was detected for the device
found at Bus % Device % Function %.
The Vendor ID for the device is % and
the Device ID is %.
Explanation: ROM CHECKSUM ERROR

Severity: Error
1.
If this PCIe device and/or any attached cables

were recently installed, moved, serviced or
upgraded, reseat adapter and any attached cables.
2.
Move adapter to a different system slot, if

available.
3.
Check IBM support site for any applicable service

bulletin or UEFI or adapter firmware update that
applies to this error. NOTE: It may be necessary to
configure slot to Gen1 or to use special utility
software so that adapter firmware can be upgraded.
Gen1/Gen2 settings can be configured via F1 Setup
-> System Settings -> Devices and I/O Ports ->
PCIe Gen1/Gen2/Gen3 Speed Selection, or the ASU
Utility.
4.
Replace adapter.
531
I.3048005 I.3818002
I.3048005
[I.3048005] UEFI has booted from the

backup flash bank.
Explanation: Booting Backup UEFI Image

Severity: Info
1.
Refer to service information for this product section

on UEFI Recovery to return system to primary
bank.
I.3808004
[I.3808004] The IMM System Event log

(SEL) is full.
Explanation: IPMI System Event Log is Full

Severity: Info
Use IMM Web Interface to clear event log.
1.
2.
If IMM communication is unavailable, use F1 Setup

to access System Event Logs Menu and Choose
Clear IMM System Event Log and Restart Server.
I.3818001
[I.3818001] The firmware image capsule

signature for the currently booted flash
bank is invalid.
Explanation: Current Bank CRTM Capsule Update

Signature Invalid
Severity: Info
1.
Reboot system. Will come up on backup UEFI

image. Reflash the primary UEFI image.
2.
If error does not persist no additional recovery

action is required.
3.
If error persists, or boot is unsuccessful, (Trained

service technician only) Replace the system board.
I.3818002
[I.3818002] The firmware image capsule

signature for the non-booted flash bank
is invalid.
Explanation: Opposite Bank CRTM Capsule Update

Signature Invalid
Severity: Info
Reflash backup UEFI image.
1.
2.
If error does not persist no additional recovery

action is required.
3.
If error persists, or boot is unsuccessful, (Trained

service technician only) Replace the system board.
532
I.3818003 I.580A5
I.3818003
[I.3818003] The CRTM flash driver could

not lock the secure flash region.
Explanation: CRTM Could not lock secure flash region

Severity: Info
1.
If system failed to boot successfully, DC cycle

system.
2.
If system boots to F1 setup, flash UEFI image and

reset bank to primary (if required). If system boots
without error, recovery is complete and no
additional action is required.
3.
If system fails to boot, or if flash attempt fails,

(Trained service technician only) Replace the system
board.
I.58015
[I.58015] Memory spare copy initiated.
Explanation: Spare Copy Started

Severity: Info
1.
No user required for this event. This is for

informational purposes only.
I.580A4
[I.580A4] Memory population change

detected.
Explanation: DIMM Population Change Detected

Severity: Info
1.
Check system event log for uncorrected DIMM

failures and replace those DIMMs.
I.580A5
[I.580A5] Mirror Fail-over complete.

DIMM number % has failed over to to
the mirrored copy.
Explanation: DIMM Mirror Fail-over Detected

Severity: Info
1.
Check the system-event log for uncorrected DIMM

failures and replace those DIMMs.
533
I.580A6 S.3020007
I.580A6
[I.580A6] Memory spare copy has

completed successfully.
Explanation: Spare Copy Complete
3.
If problem persists, then remove Adapter Card. If

system reboots successfully without the adapter,
replace that card.
4.

processor.
Severity: Info
1.
Check system log for related DIMM failures and

replace those DIMMs.
S.1100B
[S.1100B] CATERR(IERR) has asserted

on processor %.
Explanation: Processor CATERR(IERR) has asserted

Severity: Error
S.2018001
Explanation: PCIe Uncorrected Error Detected

Severity: Error
1.
If this node and/or any attached cables were

recently installed, moved, serviced or upgraded, a.
Reseat Adapter and any attached cables. b. Reload
Device Driver c. If device is not recognized,
reconfiguring slot to Gen1 or Gen2 may be required.
Utility.
2.
Check IBM support site for an applicable device

driver, firmware update, version of service
information for this product or other information
that applies to this error. Load new device driver
and any required firmware updates.
3.
If problem persists, then remove Adapter Card. If

system reboots successfully without the adapter,
replace that card.

1.

Processor error.
2.

Processor.
S.1100C
[S.1100C] An uncorrectable error has

been detected on processor %.
Explanation: Uncorrectable processor error detected

Severity: Error
1.

error.
2.
Reboot system. If problem persists escalate to the

next level of supprt.
S.2011001
[S.2011001] An Uncorrected PCIe Error

has Occurred at Bus % Device %
Function %. The Vendor ID for the
device is % and the Device ID is %.
Explanation: PCI SERR Detected

Severity: Error
1.
2.
If this node and/or any attached cables were

recently installed, moved, serviced or upgraded, a.
Reseat Adapter and any attached cables. b. Reload
Device Driver c. If device is not recognized,
reconfiguring slot to Gen1 or Gen2 may be required.
Utility.
Check IBM support site for an applicable device
driver, firmware update, revision of service
information for this product or other information
that applies to this error. Load new device driver
and any required firmware updates.
534
[S.2018001] An Uncorrected PCIe Error

has Occurred at Bus % Device %
Function %. The Vendor ID for the
device is % and the Device ID is %.
4.
5.
Replace PCIe riser card.

processor.
S.3020007
[S.3020007] A firmware fault has been

detected in the UEFI image.
Explanation: Internal UEFI Firmware Fault Detected,

System halted
Severity: Error
1.
2.
3.

error.
Reflash UEFI image.
(Trained service technician only) Replace the
system board.
S.3028002 S.3040007
S.3028002
[S.3028002] Boot permission timeout

detected.
Explanation: Boot Permission Negotiation Timeout

Severity: Error
1.
2.
3.
Check FPC/IMM logs for communication errors

and resolve.
Reseat system
If problem persists escalate to the next level of
support
S.3030007


System halted
Severity: Error
1.
2.
3.

error.
Reflash UEFI image.
system board.
S.3040007


System halted
Severity: Error
1.
2.
3.

error.
Reflash UEFI image.
system board.
535
S.3050007 S.3058004
S.3050007


System halted
Severity: Error
1.

error.
Reflash UEFI image.
2.
3.

system board.
S.3058004
[S.3058004] A Three Strike boot failure

has occurred. The system has booted
with default UEFI settings.
Explanation: POST failure has occurred! System

booted with default settings.
Severity: Error
1.
This event resets UEFI to the default settings for

the next boot. If successful, user is forced into F1
setup. Original UEFI settings are still present.
2.
If User did not intentionally trigger the reboots,

check logs for probable cause.
3.
Undo recent system changes (settings or devices

added). If not recent system changes, remove all
options then remove CMOS battery for 30 seconds
to clear CMOS contents. Verify that the system
boots. Then, re-install options one at a time to locate
the problem.
4.

error.
Reflash UEFI firmware.
5.
6.
Remove and re-install CMOS battery for 30 seconds

to clear CMOS contents
7.

system board.
536
S.3060007 S.3108007
S.3060007


System halted
Severity: Error
1.
2.
3.

error.
Reflash UEFI image.
system board.
S.3070007


System halted
Severity: Error
1.
2.
3.

error.
Reflash UEFI image.
system board.
S.3108007
[S.3108007 ] The default system settings

have been restored.
Explanation: System Configuration Restored to

Defaults
Severity: Error
1.

error.
537
S.3818004 S.51009
S.3818004
[S.3818004] The CRTM flash driver

could not successfully flash the staging
area. A failure occurred.
Explanation: CRTM Update Failed
2.
If no problem is observed on the DIMM connectors

or the problem persists, replace the DIMM
identified by LightPath and/or event log entry.
3.
If problem re-occurs on the same DIMM connector,

replace the other DIMMs on the same memory
channel.
4.

memory error.
5.
(Trained Service technician only) If problem

re-occurs on the same DIMM connector, inspect
connector for damage. If found, replace system
board.
6.
(Trained Service technician only) Replace affected

Processor.
Severity: Error
1.
Continue booting sytem. If system does not reset,

manually reset the system.
2.
If the error is not reported on the subsequent boot,

no additional recovery action is required.
3.
If the error persists, continue booting system and

reflash UEFI image.
4.

system board.
S.51006
S.3818007
[S.3818007] The firmware image

capsules for both flash banks could not
be verified.
Explanation: CRTM image capsule could not be

verified
Severity: Error
1.
If system failed to boot successfully, DC cycle

system.
2.
If system boots to F1 steup, flash UEFI image and

reset bank to primary (if required). If system boots
without error, recovery is complete and no
additional action is required.
3.
If system fails to boot, or if flash attempt fails,

(Trained service technician only) Replace the system
board.
S.51003
[S.51003] An uncorrectable memory error

was detected in DIMM slot % on rank
%. [S.51003] An uncorrectable memory
error was detected on processor %
channel %. The failing DIMM within
the channel could not be determined.
[S.51003] An uncorrectable memory error
has been detected during POST.
Explanation: Fatal Memory Error Occurred

Severity: Error
Explanation: One or More Mismatched DIMMs

Detected
Severity: Error
1.
Could follow an uncorrectable memory error or

failed memory test. Check log and service that
event first. DIMMs disabled by other errors or
actions could cause this event.
2.
Verify that the DIMMs are installed in the correct

population sequence, according to the service
3.
Disable memory mirroring and sparing. If this

action eliminates the mismatch, check IBM Support
site for information related to this problem.
4.
Reflash UEFI firmware.
5.
Replace DIMM
6.
S.51009
If the node has recently been installed, moved,

serviced, or upgraded, verify that the DIMM is
properly seated and visually verify that there is no
foreign material in any DIMM connector on that
memory channel. If either of these conditions is
found, correct and retry with the same DIMM.
(Note: Event Log may contain a recent 00580A4
event denoting detected change in DIMM
population that could be related to this problem.)
538
[S.51009] No system memory has been

detected.
Explanation: No Memory Detected

Severity: Error
1.
Make sure that one or more DIMMs are installed in

the server.
2.
If no memory fault is recorded in the logs and no

DIMM connector error LEDs are lit, verify that all
DIMM connectors are enabled using the Setup
utility or the Advanced Settings Utility (ASU).
3.
Re-Install all DIMMs verifying the correct

population sequence, according to the service
4.

processor.

1.
[S.51006] A memory mismatch has been

detected. Please verify that the memory
configuration is valid.
S.58008
5.

system board.
S.58008
[S.58008] A DIMM has failed the POST

memory test.
Explanation: DIMM Failed Memory Test

Severity: Error
1.
You must AC-cycle the system to re-enable affected

DIMM connector or re-enable manually using F1
setup
2.
If the node has been recently installed, serviced,

moved, or upgraded, check to ensure that DIMMs
are firmly seated and that no foreign material can
be seen in the DIMM connector. If either condition
is observed, correct and retry with the same DIMM.
3.
If problem persists, replace the DIMM identified by

LightPath and/or event log entry.
4.
If problem re-occurs on the same DIMM connector,

swap the other DIMMs on the same memory
channel across channels one at a time to a different
memory channel or Processor. (check service
information for this product/Install guide for
population requirements for sparing/paring
modes). If problem follows a moved DIMM to a
different memory channel, replace that DIMM.
5.

memory error.
6.
(Trained service technician only) If problem stays

with the original DIMM connector, re-inspect DIMM
connector for foreign material and remove, if found.
If connector is damaged, replace system board.
7.
(Trained service technician only) Remove affected

Processor and inspect Processor socket pins for
damaged or mis-aligned pins. If damage is found,
or this is an upgrade Processor, replace system
board. If there are multiple Processors, swap
Processors to move affected Procesor to another
Processor socket and retry. If problem follows the
affected Processor (or there is only one Processor),
replace the affected Processor.
539
S.68005 S.680B9
S.68005
[S.68005] An error has been detected by

the the IIO core logic on Bus %. The
Global Fatal Error Status register
contains %. The Global Non-Fatal Error
Status register contains %. Please check
error logs for the presence of additional
downstream device error data.
Explanation: Critical IOH-PCI Error

Severity: Error
1.
Check log for a separate error for an associated

PCIe device and service that error.
2.

bulletin or firmware update for the system or
adapter that applies to this error.
3.

system board.
S.680B8
[S.680B8] Internal QPI Link Failure

Detected.
Explanation: Internal QPI Link Failure Detected

Severity: Error
1.

error.
2.
Inspect processor socket for foreign debris or

damage. If debris is found remove debris.
3.
If error recurs, or socket damage is found, replace

the system board (Trained Service technician only) .
4.
(Trained Service Technician Only) Replace the

processor.
S.680B9
[S.680B9] External QPI Link Failure

Detected.
Explanation: External QPI Link Failure Detected

Severity: Error
1.

error.
2.
Inspect processor socket for foreign debris or

damage. If debris is found remove debris.
3.
If error recurs, or socket damage is found, replace

the system board (Trained Service technician only) .
540
W.11004 W.305800B
W.11004
[W.11004] A processor within the system

has failed the BIST.
W.3058009
Explanation: Processor Self Test Failure Detected

Severity: Error
1.
2.
3.
If the Processor or firmware was just updated,

check IBM support site for an applicable service
Processor error.
(Trained service technician only) If there are
multiple Processors, swap Processors to move
affected Processor to another Processor socket and
retry. If problem follows the affected Processor, or
this is a single Processor system, replace the
Processor. Inspect Processor socket on each
Processor removal and replace system board first if
damaged or mis-aligned pins are found.
system board.
W.3048006
[W.3048006] UEFI has booted from the

backup flash bank due to an Automatic
Boot Recovery (ABR) event.
Explanation: Automated Boot Recovery, Booting

Backup UEFI Image
Severity: Warning
Explanation: DRIVER HEALTH PROTOCOL: Missing

Configuration. Requires Change Settings From F1
Severity: Warning
1.
Go to System Settings > Settings > Driver Health

Status List and find a driver/controller reporting
Configuration Required status.
2.
Search for the driver menu from System Settings

and change settings appropriately.
3.
2.
3.

error.
Save settings and restart system.
W.305800A
[W.305800A] DRIVER HEALTH

PROTOCOL: Reports 'Failed' Status
Controller.
Explanation: DRIVER HEALTH PROTOCOL: Reports

'Failed' Status Controller
Severity: Warning
1.
Reboot the system.
2.
If problem persists, switch to backup UEFI or

reflash current UEFI image.
3.
(Trained Service Technician Only) Replace system

board.

1.
[W.3058009] DRIVER HEALTH

PROTOCOL: Missing Configuraiton.
Requires Change Settings From F1.
W.305800B
[W.305800B] DRIVER HEALTH

PROTOCOL: Reports 'Reboot' Required
Controller.
Reflash Primary UEFI image. Refer to UEFI

Recovery section of service information for this
product.

'Reboot' Required Controller

system board.
Severity: Warning
1.
No action required system will reboot at the end

of POST.
Explanation: RTC Date and Time Incorrect
2.

Severity: Warning
3.

board.
W.305000A
[W.305000A] An invalid date and time

have been detected.

1.
Check IMM/chassis event log. This event should

immediately precede 0068002 error. Service that
event or any other battery related errors.
2.
Use F1 Setup to reset date and time. If problem

returns after a system reset, replace CMOS battery.
3.
If problem persists then check IBM support site for

an applicable service bulletin or firmware update
that applies to this error.
4.
Trained Service technician only) Replace the system

board.
541
W.305800C W.305800E
W.305800C
[W.305800C] DRIVER HEALTH

PROTOCOL: Reports 'System
Shutdown' Required Controller.

'System Shutdown' Required Controller
Severity: Warning
Reboot the system.
1.
2.

3.

board.
W.305800D
[W.305800D] DRIVER HEALTH

PROTOCOL: Disconnect Controller
Failed. Requires 'Reboot'.
Explanation: DRIVER HEALTH PROTOCOL:

Disconnect Controller Failed. Requires 'Reboot'
Severity: Warning
1.
Reboot the system to reconnect the controller.
2.

3.

board.
W.305800E
[W.305800E] DRIVER HEALTH

PROTOCOL: Reports Invalid Health
Status Driver.

Invalid Health Status Driver
Severity: Warning
Reboot the system.
1.
2.

3.

board.
542
W.3808000 W.3808002
W.3808000
[W.3808000] An IMM communication

failure has occurred.
Explanation: IMM Communication Failure

Severity: Warning
1.
Reset the IMM from the FPC.
2.
Use FPC to remove AUX power from the node.

This will reboot the entire node.
3.

error.
4.
5.
Reflash UEFI Firmware.

system board.
W.3808002
[W.3808002] An error occurred while

saving UEFI settings to the IMM.
Explanation: Error Updating System Configuration to

IMM
Severity: Warning
1.
2.
Use F1 Setup, Verify Settings and Save Settings to

recover settings.
3.

4.

error.
5.
Reflash IMM Firmware.
6.

to clear CMOS contents.
7.

board.
543
W.3808003 W.381800D
W.3808003
.[W.3808003] Unable to retrieve the

system configuration from the IMM.
Explanation: Error Retrieving System Configuration

from IMM
Severity: Warning
1.
Use F1 Setup, Verify Settings and Save Settings to

recover settings.
2.
3.

4.

error.
Reflash IMM Firmware.
5.
6.

to clear CMOS contents.
7.

board.
W.3818005
[W.3818005] The CRTM flash driver

could not successfully flash the staging
area. The update was aborted
Explanation: CRTM Update Aborted

Severity: Warning
1.
Continue booting system. If system does not reset,

manually reset the system.
2.
If the error is not reported on the subsequent boot,

no additional recovery action is required.
3.
If the event persists, continue booting system and

reflash UEFI image.
4.

system board.
W.381800D
[W.381800D] TPM physical presence is

in asserted state
Explanation: TPM physical presence is in asserted

state
Severity: Warning
1.
Complete any administrative tasks requiring the

TPM physical presence switch to be in the "ON"
position..
2.
Restore the physical presence switch to the "OFF"

position and reboot the system.
3.

system board.
544
W.3938002 W.580A1
W.3938002
or Processor. (check service information for this

product/Install guide for population requirements
for sparing/paring modes). If PFA follows a moved
DIMM to any DIMM connector on the different
memory channel, replace the moved DIMM.
[W.3938002] A boot configuration error

has been detected.
Explanation: Boot Configuration Error

Severity: Warning
4.
(Trained service technician only) If problem

continues to re-occur on the same DIMM connector,
inspect DIMM connector for foreign material and
remove, if found. If connector is damaged, replace
system board.
5.
(Trained service technician only) Inspect processor

socket for foreign debris or damage. If debris is
found, remove debris.
6.
(Trained service technician only) Remove affected

processor and inspect processor socket pins for
damaged or mis-aligned pins. If damage is found
on processor, replace system board.
7.
(Trained Service technician only) Replace affected

processor.

1.
F1 Setup -> Save Settings
2.
Retry OOB config update
W.50001
[W.50001] A DIMM has been disabled

due to an error detected during POST.
Explanation: DIMM Disabled

Severity: Info
1.
If the DIMM was disabled because of a memory

fault, follow the procedure for that event.
2.
If no memory fault is recorded in the logs and no

DIMM connector error LEDs are lit, re-enable the
DIMM through the Setup utility or the Advanced
Settings Utility (ASU).
3.
If problem persists, Power cycle the node from

management console.
4.
Reset IMM to default settings.
5.
Reset UEFI to default settings.
6.
Reflash IMM and UEFI firmware.
7.
(Trained Service technician only) Replace system

board.
W.58001
[W.58001] The PFA Threshold limit

(correctable error logging limit) has
been exceeded on DIMM number % at
address %. MC5 Status contains % and
MC5 Misc contains %.
Explanation: DIMM PFA Threshold Exceeded
W.58007
Explanation: Unsupported DIMM Population

Severity: Error
1.
Could follow an uncorrectable memory error or

failed memory test. Check log and service that
event first. DIMMs disabled by other errors or
actions could cause this event.
2.
Ensure that the DIMM connectors are populated

according to the guidelines in the service
W.580A1
Severity: Error
1.
If the node has recently been installed, moved,

serviced, or upgraded, verify that the DIMM is
properly seated and visually verify that there is no
foreign material in any DIMM connector on that
memory channel. If either of these conditions is
found, correct and retry with the same DIMM.
2.
Check IBM support site for an applicable firmware

update that applies to this memory error. The
release notes will list the known problems the
update addresses.
3.
If PFA re-occurs on the same DIMM connector,

swap the other DIMMs on the same memory
channel one at a time to a different memory channel
[W.58007] Invalid memory configuration

(Unsupported DIMM Population)
detected. Please verify memory
configuration is valid.
[W.580A1] Invalid memory configuration

for Mirror Mode. Please correct memory
configuration.
Explanation: Unsupported DIMM Population for

Mirror Mode
Severity: Error
1.
If a DIMM connector error LED is lit, resolve the

failure.
2.
Make sure that the DIMM connectors are correctly

populated for mirroring mode, according to the
service information for this product.
545
W.580A2
W.580A2
[W.580A2] Invalid memory configuration

for Sparing Mode. Please correct
memory configuration.
Explanation: Unsupported DIMM Population for

Spare Mode
Severity: Error
1.
Make sure that the DIMM connectors are correctly

populated for sparing mode, according to the
service information for this product.
546
W.68002
W.68002
[W.68002] A CMOS battery error has

been detected
Explanation: CMOS Battery Fault

Severity: Error
1.
If the system was recently Installed, Moved, or

Serviced, make sure the battery is properly seated.
2.

error.
3.
4.
Replace CMOS Battery

system board.
547
548
Appendix C. DSA diagnostic test results

After running the DSA diagnostic tests, use this information to resolve any issues
that were found.
DSA Broadcom network test results

The following messages can result when you run the Broadcom network test.
405-000-000
BRCM:TestControlRegisters Test Passed
Explanation: The test passed.

Severity: Event
Serviceable: No
Recoverable: No
405-001-000
BRCM:TestMIIRegisters Test Passed

Severity: Event
Serviceable: No
Recoverable: No
405-002-000
BRCM:TestEEPROM Test Passed

Severity: Event
Serviceable: No
Recoverable: No
549
405-003-000 405-007-000
405-003-000
BRCM:TestInternalMemory Test Passed

Severity: Event
Serviceable: No
Recoverable: No
405-004-000
BRCM:TestInterrupt Test Passed

Severity: Event
Serviceable: No
Recoverable: No
405-005-000
BRCM:TestLoopbackMAC Test Passed

Severity: Event
Serviceable: No
Recoverable: No
405-006-000
BRCM:TestLoopbackPhysical Test
Passed

Severity: Event
Serviceable: No
Recoverable: No
405-007-000
BRCM:TestLEDs Test Passed

Severity: Event
Serviceable: No
Recoverable: No
550
405-800-000 405-804-000
405-800-000
BRCM:TestControlRegisters Test
Aborted
Explanation: The control registers test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
405-801-000
BRCM:TestMIIRegisters Test Aborted
Explanation: The MII register test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
405-802-000
BRCM:TestEEPROM Test Aborted
Explanation: The EEPROM test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
405-803-000
BRCM:TestInternalMemory Test
Aborted
Explanation: The internal memory test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
405-804-000
BRCM:TestInterrupt Test Aborted
Explanation: The interrupt test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
551
405-805-000 405-900-000
405-805-000
BRCM:TestLoopbackMAC Test Aborted
Explanation: Loopback testing at the MAC layer was

canceled.
Severity: Warning
Serviceable: No
Recoverable: No
405-806-000
BRCM:TestLoopbackPhysical Test
Aborted
Explanation: Loopback testing at the physical layer

was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
405-807-000
BRCM:TestLEDs Test Aborted
Explanation: Verification of status LEDs was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
405-900-000
BRCM:TestControlRegisters Test Failed
Explanation: A failure was detected while testing

internal MAC registers
Severity: Error
Serviceable: Yes
Recoverable: No
1. Check component firmware level and upgrade if
necessary. The installed firmware level can be found
in the DSA Diagnostic Event Log within the
Firmware/VPD section for this component.
2. Rerun the test.
3. If failure remains, refer to "Troubleshooting by
symptom" in the system "Installation and Service
Guide" for the next corrective action.
552
405-901-000 405-902-000
405-901-000
BRCM:TestMIIRegisters Test Failed

internal PHY registers.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
405-902-000
BRCM:TestEEPROM Test Failed

non-volatile RAM.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
553
405-903-000 405-904-000
405-903-000
BRCM:TestInternalMemory Test Failed

internal memory.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
405-904-000
BRCM:TestInterrupt Test Failed

interrupts.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
554
405-905-000
405-905-000
BRCM:TestLoopbackMAC Test Failed
Explanation: BRCM:TestLoopbackMAC Test Failed.

Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
555
405-906-000 218-001-000
405-906-000
BRCM:TestLoopbackPhysical Test Failed
405-907-000
BRCM:TestLEDs Test Failed
Explanation: A failure was detected during the

loopback test at the physical layer.
Explanation: A failure was detected while verifying

operation of the status LEDs.
Severity: Error
Severity: Error
Serviceable: Yes
Serviceable: Yes
Recoverable: No
Recoverable: No


2. Rerun the test.
2. Rerun the test.


DSA Brocade test results

The following messages can result when you run the Brocade test.
218-000-000
Brocade:MemoryTest Passed

Severity: Event
Serviceable: No
Recoverable: No
218-001-000
Brocade:ExternalLoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
556
218-002-000 218-006-000
218-002-000
Brocade:SerdesLoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
218-003-000
Brocade:PCILoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
218-004-000
Brocade:ExternalEthLoopbackTest
Passed

Severity: Event
Serviceable: No
Recoverable: No
218-005-000
Brocade:SerdesEthLoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
218-006-000
Brocade:InternalLoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
557
218-800-000 218-804-000
218-800-000
Brocade:MemoryTest Aborted
Explanation: The test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
218-801-000
Brocade:ExternalLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
218-802-000
Brocade:SerdesLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
218-803-000
Brocade:PCILoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
218-804-000
Brocade:ExternalEthLoopbackTest
Aborted

Severity: Warning
Serviceable: No
Recoverable: No
558
218-805-000 218-901-000
218-805-000
Brocade:SerdesEthLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
218-806-000
Brocade:InternalLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
218-900-000
Brocade:MemoryTest Failed
Explanation: A failure was detected while testing the

adapter memory.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
2. Verify whether the firmware is at proper level.
3. Rerun the test.
4. If the problem remains, contact your IBM
technical-support representative.
218-901-000
Brocade:ExternalLoopbackTest Failed

Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Check cable connections.
2. Rerun the test.
4. Rerun the test.
559
218-902-000 218-904-000
218-902-000
Brocade:SerdesLoopbackTest Failed

Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
218-903-000
Brocade:PCILoopbackTest Failed

Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
218-904-000
Brocade:ExternalEthLoopbackTest Failed

Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Check or replace SFP/cable.
2. Rerun the test.
4. Rerun the test.
560
218-905-000
218-905-000
Brocade:SerdesEthLoopbackTest Failed

Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
561
218-906-000 180-801-000
218-906-000
Brocade:InternalLoopbackTest Failed

Loopback test.

1. Rerun the test.
Severity: Error
3. Rerun the test.
Serviceable: Yes

Recoverable: No
DSA checkpoint panel test results

The following messages can result when you run the checkpoint panel test.
180-000-000
Check-point Panel Test Passed
Explanation: Check-point Panel Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
180-801-000
Check-point Panel Test Aborted
Explanation: Check-point Panel Test Aborted. BMC is

unable to verify that the operator information panel
cable is connected.
Severity: Warning
Serviceable: Yes
Recoverable: No
1. Inspect and reseat operator information panel cable
at both ends.
2. Verify that the Baseboard Management Controller
(BMC) is working.
3. Run the test again.
562
180-901-000 089-802-000
180-901-000
Check-point Panel Test Failed
2. Replace the information panel cable if damage is

present.
Explanation: Check-point Panel Test Failed. Operator

reported incorrect display.
Severity: Error
Serviceable: Yes

Recoverable: No
4. Replace the operator information panel assembly.

1. Check the operator information panel cabling for
loose or broken connections at both ends or damage
to the cable.
DSA CPU stress test results

The following messages can result when you run the CPU stress test.
089-000-000
CPU Stress Test Passed
Explanation: CPU Stress Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
089-802-000
CPU Stress Test Aborted
Explanation: CPU Stress Test Aborted. System

resource unavailability error.
Severity: Warning
Serviceable: Yes
Recoverable: No
089-801-000
Explanation: CPU Stress Test Aborted. Internal

Program Error.
Severity: Warning
Serviceable: Yes

1. Turn off and restart the system.
2. Make sure that the DSA Diagnostic code is at the
latest level.
4. Check system firmware level and upgrade if

6. If the system has stopped responding, turn off and

restart the system and then run the test again.
Recoverable: No

latest level.
Firmware/VPD section for this component. The
latest level firmware for this component can be
found in reference to this system type at the IBM
Support website.


563
089-803-000
089-803-000
Explanation: CPU Stress Test Aborted. Memory size is

insufficient to run the test. At least 1GB is required.
Severity: Warning
Serviceable: Yes
Recoverable: No
564
089-804-000
089-804-000
Explanation: CPU Stress Test Aborted. User pressed

Ctrl-C.
Severity: Warning
Serviceable: Yes
Recoverable: No
565
089-901-000 516-002-000
089-901-000
CPU Stress Test Failed
Explanation: CPU Stress Test Failed.

Severity: Error
Serviceable: Yes

Recoverable: No


latest level.
DSA Emulex adapter test results

The following messages can result when you run the Emulex adapter test.
516-000-000
ELXUCNA: NIC MAC LoopBackTest

Passed

Severity: Event
Serviceable: No
Recoverable: No
516-001-000
ELXUCNA: NIC PHY LoopBackTest

Passed

Severity: Event
Serviceable: No
Recoverable: No
516-002-000
ELXUCNA: ELXUCNA: NIC

LED(Beacon)Test Passed

Severity: Event
Serviceable: No
Recoverable: No
566
516-800-000 516-900-000
516-800-000

Aborted
Explanation: Loopback testing at the MAC layer was

canceled.
Severity: Warning
Serviceable: No
Recoverable: No
516-801-000

Aborted
Explanation: Loopback testing at the physical layer

was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
516-802-000

LED(Beacon)Test Aborted
Explanation: Verification of status LEDs was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
516-900-000

Failed

loopback test at the MAC layer.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
567
516-901-000 401-801-000
516-901-000

Failed
516-902-000

LED(Beacon)Test Failed

loopback test at the physical layer.
Explanation: A failure was detected while verifying

operation of the status LEDs.
Severity: Error
Severity: Error
Serviceable: Yes
Serviceable: Yes
Recoverable: No
Recoverable: No


2. Rerun the test.
2. Rerun the test.


DSA EXA port ping test results

The following messages can result when you run the EXA port ping test.
401-000-000
EXA Port Ping Test Passed
Explanation: EXA Port Ping Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
401-801-000
EXA Port Ping Test Aborted
Explanation: EXA Port Ping Test Aborted. Unable to

get device base address.
Severity: Warning
Serviceable: Yes
Recoverable: No
1. Remove power cables, wait for 45 seconds,
reconnect and rerun the test.
2. Make sure that the scalability cable connections are
as per specification.
3. Make sure that DSA and BIOS/uEFI are at the latest
level.
4. If the problem remains, contact your
technical-service representative.
568
401-802-000 217-800-000
401-802-000
EXA Port Ping Test Aborted
Explanation: EXA Port Ping Test Aborted. Port

connections may not be correct.
Severity: Warning
401-901-001
EXA Port Ping Test Failed
Explanation: EXA Port Ping Test Failed.

Severity: Error
Serviceable: Yes
Serviceable: Yes
Recoverable: No
Recoverable: No

level.

3. Check scalability cables for loose connections.
4. Replace the scalability cable(s) for specified port(s).
DSA hard drive test results

The following messages can result when you run the hard drive test.
217-000-000
HDD Test Passed
Explanation: HDD Stress Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
217-800-000
HDD Test Aborted
Explanation: HDD Test Aborted. The test was

canceled.
Severity: Warning
Serviceable: Yes
Recoverable: No
2. Rerun the test.
3. Verify that Hard drive supports self test and self
test logging.
569
217-900-000 406-002-000
217-900-000
HDD Test Failed
Explanation: HDD Test Failed. The hard drive self-test

detected a failure.
Severity: Error

2. Rerun the test.
3. Verify the firmware is at the latest level.
4. Rerun the test.
Serviceable: Yes

Recoverable: No
DSA Intel network test results

The following messages can result when you run the Intel network test.
406-000-000
IANet:Registers Test Passed

Severity: Event
Serviceable: No
Recoverable: No
406-001-000
IANet:EEPROM Test Passed

Severity: Event
Serviceable: No
Recoverable: No
406-002-000
IANet:FIFO Test Passed

Severity: Event
Serviceable: No
Recoverable: No
570
406-003-000 406-802-000
406-003-000
IANet:Interrupts Test Passed

Severity: Event
Serviceable: No
Recoverable: No
406-004-000
IANet:Loopback Test Passed

Severity: Event
Serviceable: No
Recoverable: No
406-800-000
IANet:Registers Test Aborted
Explanation: Registers test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
406-801-000
IANet:EEPROM Test Aborted
Explanation: EEPROM test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
406-802-000
IANet:FIFO Test Aborted
Explanation: FIFO test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
571
406-803-000 406-903-000
406-803-000
IANet:Interrupts Test Aborted
Explanation: Interrupt test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
406-804-000
IANet:Loopback Test Aborted
Explanation: Loopback test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
406-900-000
IANet:Registers Test Failed

Registers test.
406-902-000
IANet:FIFO Test Failed
Explanation: A failure was detected during the FIFO

test.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Severity: Error
Serviceable: Yes
Recoverable: No
406-903-000
IANet:Interrupts Test Failed

Interrupt test.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.


406-901-000
IANet:EEPROM Test Failed

EEPROM test.
Severity: Error
2. Rerun the test.

3. Check interrupt assignments in the PCI Hardware
section of the DSA Diagnostic Log. If the ethernet
device is sharing interrupts, if possible modify the
interrupt assignments using F1 Setup to assign a
unique interrupt to the device.
Serviceable: Yes
4. Rerun the test.
Recoverable: No


2. Rerun the test.
572
406-904-000
406-904-000
IANet:Loopback Test Failed

Loopback test.
Severity: Error
Serviceable: Yes
1. Check the Ethernet cable for damage and ensure

correct cable type and attachment.
3. Rerun the test.
Recoverable: No

DSA LSI hard drive test results

The following messages can result when you run the LSI hard drive test.
573
407-000-000
407-000-000
LSIESG:DiskDefaultDiagnostic Test
Passed

Severity: Event
Serviceable: No
Recoverable: No
574
407-800-000
407-800-000
Aborted

Severity: Warning
Serviceable: No
Recoverable: No
575
407-900-000 408-800-000
407-900-000
Failed
Explanation: The hard drive self-test detected a

failure.

2. Rerun the test.
3. Verify whether the firmware is at the latest level.
4. Rerun the test.
Severity: Error

Serviceable: Yes
Recoverable: No
DSA Mellanox adapter test results

The following messages can result when you run the Mellanox adapter test.
408-000-000
MLNX:MLNX_DiagnosticTestEthernetPort
Test Passed
Explanation: Port Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
408-001-000
MLNX:MLNX_DiagnosticTestIBPort Test
Passed
Explanation: Port Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
408-800-000
Test Aborted
Explanation: Port Test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
576
408-801-000
408-801-000
Aborted
Explanation: Port Test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
577
408-900-000
408-900-000
Test Failed
Explanation: Port Test Failed.

Severity: Error
Serviceable: Yes
Recoverable: No
1. Make sure that the physical link of the port under
test in the active state.
2. If these condition was met but the test keeps failing
the port's adapter might be faulty.
3. Try replacing the adapter and repeating the test.
578
408-901-000 201-000-002
408-901-000
Failed
Explanation: Port Test Failed.

Severity: Error

1. Make sure that the physical link of the port under
test in the active state and a subnet manager
running on the fabric to which the port is attached.
2. If these condition was met but the test keeps failing
the port's adapter might be faulty.
Serviceable: Yes
3. Try replacing the adapter and repeating the test.
Recoverable: No
DSA memory isolation test results

The following messages can result when you run the memory isolation test.
201-000-000
Standalone Memory Test Passed
Explanation: Quick/Full Memory Test All CPUs

Passed.
Severity: Event
Serviceable: No
Recoverable: No
201-000-001
Explanation: Quick/Full Memory Test CPU 1 Passed.

Severity: Event
Serviceable: No
Recoverable: No
201-000-002

Severity: Event
Serviceable: No
Recoverable: No
579
201-000-003 201-811-003
201-000-003

level.

Severity: Event
201-811-002
Serviceable: No
Explanation: Unable to Locate SMBIOS key "_SM_".
Recoverable: No
Severity: Warning
Serviceable: No
Standalone Memory Test Aborted
Recoverable: No
201-000-004

Severity: Event
Serviceable: No
Recoverable: No
201-811-000

1. Perform the actions mentioned one at a time and
try the test after each action.
3. Turn off the system and disconnect it from power.
Wait for 45 seconds. Reseat DIMM(s). Reconnect it
to power.
level.
Severity: Warning
Serviceable: No
201-811-003
Recoverable: No
Severity: Warning
Serviceable: No

Recoverable: No

to power.
level.
201-811-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
580

to power.
level.
201-812-000 201-812-001
201-812-000
Explanation: Memory test is not supported for this

system.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-812-001

system.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
581
201-812-002 201-812-003
201-812-002

system.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-812-003

system.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
582
201-813-000 201-813-001
201-813-000
Explanation: Chipset Error: Can not turn OFF ECC

error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-813-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
583
201-813-002 201-813-003
201-813-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-813-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
584
201-814-000 201-814-001
201-814-000
Explanation: Chipset Error: Can not disable Scubbing

feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-814-001

feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
585
201-814-002 201-814-003
201-814-002

feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-814-003

feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
586
201-815-000 201-815-001
201-815-000
Explanation: Program Error with Quick Memory

Menu Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-815-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
587
201-815-002 201-815-003
201-815-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-815-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
588
201-816-000 201-816-001
201-816-000
Explanation: Program Error with Full Memory Menu

Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-816-001

Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
589
201-816-002 201-816-003
201-816-002

Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-816-003

Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
590
201-818-000 201-818-001
201-818-000

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-818-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
591
201-818-002 201-818-003
201-818-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-818-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
592
201-819-000 201-819-001
201-819-000
Explanation: The start-end address ranges in the

restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-819-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
593
201-819-002 201-819-003
201-819-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-819-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
594
201-820-000 201-820-001
201-820-000
Explanation: Memory Upper limit is less than 16

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-820-001

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
595
201-820-002 201-820-003
201-820-002

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-820-003

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
596
201-821-000 201-821-001
201-821-000
Explanation: Variable range MTRR registers are larger

than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-821-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
597
201-821-002 201-821-003
201-821-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-821-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
598
201-822-000 201-822-001
201-822-000
Explanation: Invalid MTRR service request.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-822-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
599
201-822-002 201-822-003
201-822-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-822-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
600
201-824-000 201-824-001
201-824-000
Explanation: Node Interleave feature must be OFF. Go

to Setup and disable Node Interleave option and then
re-run the test.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-824-001

re-run the test.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
601
201-824-002 201-824-003
201-824-002

re-run the test.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-824-003

re-run the test.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
602
201-826-000 201-826-001
201-826-000
Explanation: BIOS: Memory Controller has been

disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-826-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
603
201-826-002 201-826-003
201-826-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-826-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
604
201-827-000 201-827-001
201-827-000
Explanation: BIOS: ECC function has been disabled by

BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-827-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
605
201-827-002 201-827-003
201-827-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-827-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
606
201-844-000 201-844-001
201-844-000
Explanation: Chipset Error: Problem in masking MSR

machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-844-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
607
201-844-002 201-844-003
201-844-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-844-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
608
201-845-000 201-845-001
201-845-000
Explanation: Chipset Error: Problem clearing MSR

machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-845-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
609
201-845-002 201-845-003
201-845-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-845-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
610
201-859-000 201-859-001
201-859-000
Explanation: INVALID XSECSRAT type.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-859-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
611
201-859-002 201-859-003
201-859-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-859-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
612
201-860-000 201-860-001
201-860-000
Explanation: No OEM0 type 1 found.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-860-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
613
201-860-002 201-860-003
201-860-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-860-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
614
201-861-000 201-861-001
201-861-000
Explanation: No SRAT type 1 found.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-861-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
615
201-861-002 201-861-003
201-861-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-861-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
616
201-862-000 201-862-001
201-862-000
Explanation: No OEM1 structure found.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-862-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
617
201-862-002 201-862-003
201-862-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-862-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
618
201-863-000 201-863-001
201-863-000
Explanation: No IBMERROR key in OEM1 structure.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-863-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
619
201-863-002 201-863-003
201-863-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-863-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
620
201-864-000 201-864-001
201-864-000
Explanation: No GAS located in OEM1.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-864-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
621
201-864-002 201-864-003
201-864-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-864-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
622
201-865-000 201-865-001
201-865-000
Explanation: No XSECSRAT key in OEM0 structure.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-865-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
623
201-865-002 201-865-003
201-865-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-865-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
624
201-866-000 201-866-001
201-866-000
Explanation: EFI-SAL Invalid parameter from

GetMemoryMap function.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-866-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
625
201-866-002 201-866-003
201-866-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-866-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
626
201-867-000 201-867-001
201-867-000
Explanation: EFI/SAL: Buffer not allocated.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-867-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
627
201-867-002 201-867-003
201-867-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-867-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
628
201-868-000 201-868-001
201-868-000
Explanation: EFI/SAL: Buffer allocated in

GetMemoryMap too small.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-868-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
629
201-868-002 201-868-003
201-868-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-868-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
630
201-869-000 201-869-001
201-869-000
Explanation: EFI/SAL Invalid parameter from

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-869-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
631
201-869-002 201-869-003
201-869-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-869-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
632
201-870-000 201-870-001
201-870-000
Explanation: CPU Doamin in ACPI not valid.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-870-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
633
201-870-002 201-870-003
201-870-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-870-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
634
201-871-000 201-871-001
201-871-000
Explanation: Data Mis-compare encountered.

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-871-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
635
201-871-002 201-871-003
201-871-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-871-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
636
201-877-000 201-877-001
201-877-000
Explanation: BIOS: Sparing in Extended PCI reg. must

be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-877-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
637
201-877-002 201-877-003
201-877-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-877-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
638
201-878-000 201-878-001
201-878-000
Explanation: Sparing feature must be turned OFF. Go

to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-878-001

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
639
201-878-002 201-878-003
201-878-002

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-878-003

Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
640
201-885-000 201-885-001
201-885-000
Explanation: Processor does not support MTRR

register manipulation. Can not write to memory
without cache.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-885-001

without cache.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
641
201-885-002 201-885-003
201-885-002

without cache.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-885-003

without cache.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
642
201-886-000 201-886-001
201-886-000

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-886-001

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
643
201-886-002 201-886-003
201-886-002

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
201-886-003

Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
to power.
level.
644
201-899-000 201-899-003
201-899-000
Explanation: Memory Diagnostics Test Aborted by

user.
Severity: Warning
Serviceable: No
Recoverable: No
201-899-001

user.
Severity: Warning
Serviceable: No
Recoverable: No
201-899-002

user.
Severity: Warning
Serviceable: No
Recoverable: No
201-899-003

user.
Severity: Warning
Serviceable: No
Recoverable: No
645
201-901-000 201-901-001
201-901-000
Standalone Memory Test Failed
Explanation: Memory Diagnostics Test Failed.

Severity: Error
Serviceable: Yes
Recoverable: No
to power.
level.
5. Replace any DIMMS(s) mentioned in error, one by
one.
6. Make sure that all DIMMs are enabled in the
Configuration/Setup Utility program.
201-901-001

Severity: Error
Serviceable: Yes
Recoverable: No
to power.
level.
one.
646
201-901-002 202-802-000
201-901-002
201-901-003
Severity: Error
Severity: Error
Serviceable: Yes
Serviceable: Yes
Recoverable: No
Recoverable: No





to power.

to power.

level.

level.

one.

one.




DSA memory stress test results

The following messages can result when you run the memory stress test.
202-000-000
MemStr Test Passed
Explanation: Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
5. Check the system firmware level and upgrade if

necessary.
6. Run the memory diagnostic to identify the specific
failing DIMM.
7. If the failure remains, refer to "Troubleshooting by

202-802-000
202-801-000
MemStr Test Aborted
Explanation: Internal program error.

Severity: Warning
Serviceable: Yes
Recoverable: No
MemStr Test Aborted
Explanation: Memory size is insufficient to run the

test. At least 1 GB is required.
Severity: Warning
Serviceable: Yes
Recoverable: No

latest level.
restart the system.
647
202-803-000 409-000-000
202-803-000
MemStr Test Aborted
Explanation: User pressed Ctrl-C.

Severity: Warning
202-902-000
Serviceable: Yes
Explanation: Memory size is insufficient to run the

test.
Recoverable: No
202-901-000
MemStr Test Failed
MemStr Test Failed
Explanation: Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Severity: Error
Serviceable: Yes
Recoverable: No
1. Execute the standard DSA memory diagnostics to
validate all memory.
latest level.
4. Reseat the memory cards and DIMMs.
5. Reconnect the system to power and turn the system
on.
1. Ensure that all memory is enabled by checking the

"Available System Memory" in the "Resource
Utilization" section of the DSA Diagnostic Event log.
2. If necessary, access the Configuration/Setup Utility
program by pressing F1 during system boot and
enable all memory.
latest level.

DSA Nvidia GPU test results

The following messages can result when you run the Nvidia GPU test.
409-000-000
NVIDIA User Diagnostic Test Passed
Explanation: NVIDIA User Diagnostic test passed.

Severity: Event
Serviceable: No
Recoverable: No
648
409-003-000 409-006-000
409-003-000
Nvidia::DiagnosticServiceProvider::Bandwidth
Test Passed
Explanation: Nvidia GPU Bandwidth test passed.

Severity: Event
Serviceable: No
Recoverable: No
409-004-000
Nvidia::DiagnosticServiceProvider::Query
Test Passed
Explanation: Nvidia GPU Query test passed.

Severity: Event
Serviceable: No
Recoverable: No
409-005-000
Nvidia::DiagnosticServiceProvider::Matrix
Test Passed
Explanation: Nvidia GPU Matrix test passed.

Severity: Event
Serviceable: No
Recoverable: No
409-006-000
Nvidia::DiagnosticServiceProvider::Binomial
Test Passed
Explanation: Nvidia GPU Binomial test passed.

Severity: Event
Serviceable: No
Recoverable: No
649
409-800-000 409-805-000
409-800-000
NVIDIA User Diagnostic Test Aborted
Explanation: NVIDIA User Diagnostic test was

canceled.
Severity: Event
Serviceable: No
Recoverable: No
409-803-000
Nvidia::DiagnosticServiceProvider::Bandwidth
Test Aborted
Explanation: Nvidia GPU Bandwidth test was

canceled.
Severity: Warning
Serviceable: No
Recoverable: No
409-804-000
Test Aborted
Explanation: Nvidia GPU Query test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
409-805-000
Test Aborted
Explanation: Nvidia GPU Matrix test was canceled.

Severity: Warning
Serviceable: No
Recoverable: No
650
409-806-000 409-905-000
409-806-000
Test Aborted
409-904-000
Test Failed
Explanation: Nvidia GPU Binomial test was canceled.
Explanation: Nvidia GPU Query Test Failed.
Severity: Warning
Severity: Error
Serviceable: No
Serviceable: Yes
Recoverable: No
Recoverable: No

409-900-000
NVIDIA User Diagnostic Test Failed
Explanation: NVIDIA User Diagnostic Test Failed.

Severity: Event
Serviceable: Yes
1. Verify that the GPU is seated in the PCIe slot

correctly by reseating the GPU. Then power cycle
the system.
2. Verify that the power connectors to the GPU are
connected firmly. Then power cycle the system.
Recoverable: No
3. Run nvidia-smi -q In some cases this will report a

poorly connected power cable.
4. Rerun the diagnostics, using the same GPU, on

system that is known to be working. A variety of
system issues can cause diagnostic failure.

the system.


409-905-000

Explanation: Nvidia GPU Matrix Test Failed.
Test Failed

Severity: Error

Recoverable: No
Serviceable: Yes

409-903-000
Nvidia::DiagnosticServiceProvider::Bandwidth User response: Complete the following steps:

Test Failed
Explanation: Nvidia GPU Bandwidth Test Failed.

Severity: Error
Serviceable: Yes

the system.
Recoverable: No



the system.


651
409-906-000 215-801-000
409-906-000
Test Failed
Explanation: Nvidia GPU Binomial Test Failed.

Severity: Error
Serviceable: Yes
Recoverable: No


the system.
DSA optical drive test results

The following messages can result when you run the optical drive test.
215-000-000
Optical Drive Test Passed
Explanation: Optical Drive Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
215-801-000
Optical Drive Test Aborted
Explanation: Optical Drive Test Aborted. Unable to

communicate with driver.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
3. Check the drive cabling for loose or broken
connections at both ends or damage to the cable.
Replace the cable if damage is present.
necessary.The installed firmware level can be found
652
215-802-000 215-902-000
215-802-000
Explanation: Optical Drive Test Aborted. A read error

was encountered.
Severity: Warning
Serviceable: Yes

Recoverable: No
215-901-000
Explanation: Optical Drive Test Aborted. Drive media

is not detected.
1. Insert a new CD or DVD into the drive and wait for

15 seconds for the media to be recognized. Rerun
the test.
215-803-000
Optical Drive Test Failed
Explanation: Optical Drive Test Failed. Disk may be in

use by the operating system.
Severity: Error
Serviceable: Yes
Severity: Warning
Serviceable: Yes
Recoverable: No
the test.
Recoverable: No
215-902-000

1. Wait for the system activity to cease
Explanation: Optical Drive Test Failed. Read

miscompare.
2. Run the test again
Severity: Error
Serviceable: Yes

215-804-000
Explanation: Optical Drive Test Aborted. The media

tray is open.
Severity: Warning
Optical Drive Test Failed
Recoverable: No
the test.
Recoverable: No


Serviceable: Yes
1. Close the media tray and wait for 15 seconds for

the media to be recognized. Run the test again.
the test.
653
215-903-000 166-801-001
215-903-000
Explanation: Optical Drive Test Aborted. Could not

access the device.
Severity: Warning

Recoverable: No

necessary.The installed firmware level can be found

Serviceable: Yes

the test.
DSA system management test results

The following messages can result when you run the system management test.
166-000-001
IMM I2C Test Passed
Explanation: IMM I2C Test Passed.

Severity: Event
Serviceable: No
Recoverable: No
166-801-001
IMM I2C Test Aborted
Explanation: IMM returned incorrect response length.

Severity: Warning
Serviceable: Yes
Recoverable: No
User response: Perform the actions mentioned one at
a time and try the test after each action:
Wait for 45 seconds. Reconnect it to power.
2. Make sure that DSA and BMC/IMM are at the
latest level.
654
166-802-001 166-804-001
166-802-001
Explanation: Test cannot be completed for unknown

reason.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-803-001
Explanation: Node Busy. Try later.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-804-001
Explanation: Invalid Command.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
655
166-805-001 166-807-001
166-805-001
Explanation: Invalid Command for given LUN.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-806-001
Explanation: Timeout while processing command.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-807-001
Explanation: Out of space.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
656
166-808-001 166-810-001
166-808-001
Explanation: Reservation Canceled or Invalid

Reservation ID.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-809-001
Explanation: Request data truncated.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-810-001
Explanation: Request data length invalid.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
657
166-811-001 166-813-001
166-811-001
Explanation: Request data field length limit exceeded.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-812-001
Explanation: Parameter out of range.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-813-001
Explanation: Cannot return number of requested data

bytes.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
658
166-814-001 166-816-001
166-814-001
Explanation: Requested Sensor, data, or record not

present.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-815-001
Explanation: Invalid data field in Request.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-816-001
Explanation: Command illegal for specified sensor or

record type.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
659
166-817-001 166-819-001
166-817-001
Explanation: Command response could not be

provided.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-818-001
Explanation: Cannot execute duplicated request.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-819-001

provided. SDR Repository in?update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
660
166-820-001 166-822-001
166-820-001

provided. Device in firmware update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-821-001

provided. BMC initialization in progress.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-822-001
Explanation: Destination unavailable.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
661
166-823-001 166-901-001
166-823-001
Explanation: Cannot execute command. Insufficient

privilege level.
Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-824-001
Explanation: Cannot execute command.

Severity: Warning
Serviceable: Yes
Recoverable: No
latest level.
166-901-001
IMM I2C Test Failed
Explanation: IMM Indicates failure in RTMM bus

(BUS 0).
Severity: Error
Serviceable: Yes
Recoverable: No
latest level.
662
166-903-001 166-904-001
166-903-001
IMM I2C Test Failed
Explanation: IMM Indicates failure in TMP75 bus

(BUS 2).
Severity: Error
Serviceable: Yes
Recoverable: No
latest level.
166-904-001
IMM I2C Test Failed
Explanation: IMM Indicates failure in TMP75 bus

(BUS 3).
Severity: Error
Serviceable: Yes
Recoverable: No
latest level.
663
166-905-001 264-902-000
166-905-001
IMM I2C Test Failed
166-908-001
IMM I2C Test Failed
Explanation: IMM Indicates failure in the ADS1015

bus (BUS 4).
Explanation: IMM Indicates failure in the PCA9557

bus (BUS 7).
Severity: Error
Severity: Error
Serviceable: Yes
Serviceable: Yes
Recoverable: No
Recoverable: No





latest level.

latest level.


DSA tape drive test results

The following messages can result when you run the tape drive test.
264-000-000
Tape Test Passed
264-902-000
Tape Test Failed
Explanation: Tape Test Passed.
Explanation: Tape Test Failed. Media is not detected.
Severity: Event
Severity: Error
Serviceable: No
Serviceable: Yes
Recoverable: No
Recoverable: No

264-901-000
Tape Test Failed
Explanation: An error was found in the tape alert log.

Severity: Error
Serviceable: Yes
Recoverable: No
1. Clean the tape drive using the appropriate cleaning
media and install new media.
3. Clear the error log.
5. Make sure that the drive firmware is at the latest
level.
6. Rerun the test after upgrading to the latest firmware
level.
664

level.
level.
264-903-000 264-904-000
264-903-000
Tape Test Failed
Explanation: Tape Test Failed. Media is not detected.

Severity: Error
Serviceable: Yes
Recoverable: No
level.
level.
264-904-000
Tape Test Failed
Explanation: Tape Test Failed. Drive hardware error.

Severity: Error
Serviceable: Yes
Recoverable: No
1. Check the tape drive cabling for loose or broken
connections or damage to the cable. Replace the
cable if damage is present.
level.
level.
665
264-905-000 264-906-000
264-905-000
Tape Test Failed
Explanation: Tape Test Failed. Software error: invalid

request.
Severity: Error
Serviceable: Yes
Recoverable: No
restart the system.
restart the system.
level.
264-906-000
Tape Test Failed
Explanation: Tape Test Failed. Unrecognized error.

Severity: Error
Serviceable: Yes
Recoverable: No
level.
level.
latest level.
necessary.
666
264-907-000
264-907-000
Tape Test Failed
Explanation: An error was found in the block address

somewhere.
Severity: Error
Serviceable: Yes
Recoverable: No
667
264-908-000
264-908-000
Tape Test Failed
Explanation: An error was found in getting tape

capacity.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Make sure that medium is present.
668
Appendix D. Getting help and technical assistance

If you need help, service, or technical assistance or just want more information
about IBM products, you will find a wide variety of sources available from IBM to
assist you.
Use this information to obtain additional information about IBM and IBM
products, determine what to do if you experience a problem with your IBM system
or optional device, and determine whom to call for service, if it is necessary.
Before you call

Before you call, make sure that you have taken these steps to try to solve the
problem yourself.
If you believe that you require IBM to perform warranty service on your IBM
product, the IBM service technicians will be able to assist you more efficiently if
you prepare before you call.
v Check all cables to make sure that they are connected.
v Check the power switches to make sure that the system and any optional
devices are turned on.
v Check for updated software, firmware, and operating-system device drivers for
your IBM product. The IBM Warranty terms and conditions state that you, the
owner of the IBM product, are responsible for maintaining and updating all
software and firmware for the product (unless it is covered by an additional
maintenance contract). Your IBM service technician will request that you
upgrade your software and firmware if the problem has a documented solution
within a software upgrade.
v If you have installed new hardware or software in your environment, check
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us to
make sure that the hardware and software is supported by your IBM product.
v Go to http://www.ibm.com/supportportal to check for information to help you
solve the problem.
v Gather the following information to provide to IBM Support. This data will help
IBM Support quickly provide a solution to your problem and ensure that you
receive the level of service for which you might have contracted.
Hardware and Software Maintenance agreement contract numbers, if
applicable
Machine type number (IBM 4-digit machine identifier)
Model number
Serial number
Current system UEFI and firmware levels
Other pertinent information such as error messages and logs
v Go to http://www.ibm.com/support/entry/portal/Open_service_request to
submit an Electronic Service Request. Submitting an Electronic Service Request
will start the process of determining a solution to your problem by making the
pertinent information available to IBM Support quickly and efficiently. IBM
service technicians can start working on your solution as soon as you have
completed and submitted an Electronic Service Request.
669
You can solve many problems without outside assistance by following the
troubleshooting procedures that IBM provides in the online help or in the
documentation that is provided with your IBM product. The documentation that
comes with IBM systems also describes the diagnostic tests that you can perform.
Most systems, operating systems, and programs come with documentation that
contains troubleshooting procedures and explanations of error messages and error
codes. If you suspect a software problem, see the documentation for the operating
system or program.
Using the documentation

Information about your IBM system and preinstalled software, if any, or optional
device is available in the documentation that comes with the product. That
documentation can include printed documents, online documents, readme files,
and help files.
See the troubleshooting information in your system documentation for instructions
for using the diagnostic programs. The troubleshooting information or the
diagnostic programs might tell you that you need additional or updated device
drivers or other software. IBM maintains pages on the World Wide Web where you
can get the latest technical information and download device drivers and updates.
To access these pages, go to http://www.ibm.com/supportportal.
Getting help and information from the World Wide Web

Up-to-date information about IBM products and support is available on the World
Wide Web.
On the World Wide Web, up-to-date information about IBM systems, optional
devices, services, and support is available at http://www.ibm.com/supportportal.
IBM System x information is at http://www.ibm.com/systems/x. IBM BladeCenter
information is at http://www.ibm.com/systems/bladecenter. IBM IntelliStation
information is at http://www.ibm.com/systems/intellistation.
How to send DSA data to IBM

Use the IBM Enhanced Customer Data Repository to send diagnostic data to IBM.
Before you send diagnostic data to IBM, read the terms of use at
http://www.ibm.com/de/support/ecurep/terms.html.
You can use any of the following methods to send diagnostic data to IBM:
v Standard upload: http://www.ibm.com/de/support/ecurep/send_http.html
v Standard upload with the system serial number: http://www.ecurep.ibm.com/
app/upload_hw
v Secure upload: http://www.ibm.com/de/support/ecurep/
send_http.html#secure
v Secure upload with the system serial number: https://www.ecurep.ibm.com/
app/upload_hw
670
Creating a personalized support web page

You can create a personalized support web page by identifying IBM products that
are of interest to you.
To create a personalized support web page, go to http://www.ibm.com/support/
mynotifications. From this personalized page, you can subscribe to weekly email
notifications about new technical documents, search for information and
downloads, and access various administrative services.
Software service and support

Through IBM Support Line, you can get telephone assistance, for a fee, with usage,
configuration, and software problems with your IBM products.
For more information about Support Line and other IBM services, see
http://www.ibm.com/services or see http://www.ibm.com/planetwide for
support telephone numbers. In the U.S. and Canada, call 1-800-IBM-SERV
(1-800-426-7378).
Hardware service and support

You can receive hardware service through your IBM reseller or IBM Services.
To locate a reseller authorized by IBM to provide warranty service, go to
http://www.ibm.com/partnerworld and click Business Partner Locator. For IBM
support telephone numbers, see http://www.ibm.com/planetwide. In the U.S. and
Canada, call 1-800-IBM-SERV (1-800-426-7378).
In the U.S. and Canada, hardware service and support is available 24 hours a day,
7 days a week. In the U.K., these services are available Monday through Friday,
from 9 a.m. to 6 p.m.
IBM Taiwan product service

Use this information to contact IBM Taiwan product service.
IBM Taiwan product service contact information:

IBM Taiwan Corporation
3F, No 7, Song Ren Rd.
Taipei, Taiwan
Telephone: 0800-016-888
Appendix D. Getting help and technical assistance
671
672
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM websites are provided for
convenience only and do not in any manner serve as an endorsement of those
websites. The materials at those websites are not part of the materials for this IBM
product, and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
673
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corporation in the United States, other countries,
or both. If these and other IBM trademarked terms are marked on their first
occurrence in this information with a trademark symbol ( or ), these symbols
indicate U.S. registered or common law trademarks owned by IBM at the time this
information was published. Such trademarks may also be registered or common
law trademarks in other countries.
A current list of IBM trademarks is available on the web at Copyright and
trademark information at http://www.ibm.com/legal/copytrade.shtml .
Adobe and PostScript are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc., in
the United States, other countries, or both and is used under license therefrom.
Intel, Intel Xeon, Itanium, and Pentium are trademarks or registered trademarks of
Intel Corporation or its subsidiaries in the United States and other countries.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc., in
the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in
the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, or service names may be trademarks or service marks of
others.
Important notes
Processor speed indicates the internal clock speed of the microprocessor; other
factors also affect application performance.
CD or DVD drive speed is the variable read rate. Actual speeds vary and are often
less than the possible maximum.
When referring to processor storage, real and virtual storage, or channel volume,
KB stands for 1024 bytes, MB stands for 1,048,576 bytes, and GB stands for
1,073,741,824 bytes.
When referring to hard disk drive capacity or communications volume, MB stands
for 1,000,000 bytes, and GB stands for 1,000,000,000 bytes. Total user-accessible
capacity can vary depending on operating environments.
Maximum internal hard disk drive capacities assume the replacement of any
standard hard disk drives and population of all hard disk drive bays with the
largest currently supported drives that are available from IBM.
674
Maximum memory might require replacement of the standard memory with an

optional memory module.
Each solid-state memory cell has an intrinsic, finite number of write cycles that the
cell can incur. Therefore, a solid-state device has a maximum number of write
cycles that it can be subjected to, expressed as total bytes written (TBW). A
device that has exceeded this limit might fail to respond to system-generated
commands or might be incapable of being written to. IBM is not responsible for
replacement of a device that has exceeded its maximum guaranteed number of
program/erase cycles, as documented in the Official Published Specifications for
the device.
IBM makes no representation or warranties regarding non-IBM products and
services that are ServerProven, including but not limited to the implied warranties
of merchantability and fitness for a particular purpose. These products are offered
and warranted solely by third parties.
IBM makes no representations or warranties with respect to non-IBM products.
Support (if any) for the non-IBM products is provided by the third party, not IBM.
Some software might differ from its retail version (if available) and might not
include user manuals or all program functionality.
Particulate contamination
Attention: Airborne particulates (including metal flakes or particles) and reactive
gases acting alone or in combination with other environmental factors such as
humidity or temperature might pose a risk to the device that is described in this
document.
Risks that are posed by the presence of excessive particulate levels or
concentrations of harmful gases include damage that might cause the device to
malfunction or cease functioning altogether. This specification sets forth limits for
particulates and gases that are intended to avoid such damage. The limits must not
be viewed or used as definitive limits, because numerous other factors, such as
temperature or moisture content of the air, can influence the impact of particulates
or environmental corrosives and gaseous contaminant transfer. In the absence of
specific limits that are set forth in this document, you must implement practices
that maintain particulate and gas levels that are consistent with the protection of
human health and safety. If IBM determines that the levels of particulates or gases
in your environment have caused damage to the device, IBM may condition
provision of repair or replacement of devices or parts on implementation of
appropriate remedial measures to mitigate such environmental contamination.
Implementation of such remedial measures is a customer responsibility.
Notices
675
Table 18. Limits for particulates and gases

Contaminant
Limits
Particulate
v The room air must be continuously filtered with 40% atmospheric

dust spot efficiency (MERV 9) according to ASHRAE Standard 52.21.
v Air that enters a data center must be filtered to 99.97% efficiency or
greater, using high-efficiency particulate air (HEPA) filters that meet
MIL-STD-282.
v The deliquescent relative humidity of the particulate contamination
must be more than 60%2.
v The room must be free of conductive contamination such as zinc
whiskers.
Gaseous
v Copper: Class G1 as per ANSI/ISA 71.04-19853

v Silver: Corrosion rate of less than 300 in 30 days
1 ASHRAE 52.2-2008 - Method of Testing General Ventilation Air-Cleaning Devices for

Removal Efficiency by Particle Size. Atlanta: American Society of Heating, Refrigerating
and Air-Conditioning Engineers, Inc.
2 The deliquescent relative humidity of particulate contamination is the relative humidity
at which the dust absorbs enough water to become wet and promote ionic conduction.
3 ANSI/ISA-71.04-1985. Environmental conditions for process measurement and control
systems: Airborne contaminants. Instrument Society of America, Research Triangle Park,
North Carolina, U.S.A.
Documentation format
The publications for this product are in Adobe Portable Document Format (PDF)
and should be compliant with accessibility standards. If you experience difficulties
when you use the PDF files and want to request a web-based format or accessible
PDF document for a publication, direct your mail to the following address:
Information Development
IBM Corporation
205/A015
3039 E. Cornwallis Road
P.O. Box 12195
Research Triangle Park, North Carolina 27709-2195
U.S.A.
In the request, be sure to include the publication part number and title.
When you send information to IBM, you grant IBM a nonexclusive right to use or
distribute the information in any way it believes appropriate without incurring any
obligation to you.
676
Telecommunication regulatory statement

This product may not be certified in your country for connection by any means
whatsoever to interfaces of public telecommunications networks. Further
certification may be required by law prior to making any such connection. Contact
an IBM representative or reseller for any questions.
Electronic emission notices

Federal Communications Commission (FCC) statement
Note: This equipment has been tested and found to comply with the limits for a
Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates,
uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the
interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to
meet FCC emission limits. IBM is not responsible for any radio or television
interference caused by using other than recommended cables and connectors or by
unauthorized changes or modifications to this equipment. Unauthorized changes
or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that
might cause undesired operation.
Industry Canada Class A emission compliance statement

This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformit la rglementation d'Industrie Canada

Cet appareil numrique de la classe A est conforme la norme NMB-003 du
Canada.
Notices
677
Australia and New Zealand Class A statement

Attention: This is a Class A product. In a domestic environment this product may
cause radio interference in which case the user may be required to take adequate
measures.
European Union EMC Directive conformance statement

This product is in conformity with the protection requirements of EU Council
Directive 2004/108/EC on the approximation of the laws of the Member States
relating to electromagnetic compatibility. IBM cannot accept responsibility for any
failure to satisfy the protection requirements resulting from a nonrecommended
modification of the product, including the fitting of non-IBM option cards.
Attention: This is an EN 55022 Class A product. In a domestic environment this
product may cause radio interference in which case the user may be required to
take adequate measures.
Responsible manufacturer:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900
European Community contact:
IBM Deutschland GmbH
Technical Regulations, Department M372
IBM-Allee 1, 71139 Ehningen, Germany
Telephone: +49 7032 15-2941
Email: lugi@de.ibm.com
Germany Class A statement

Deutschsprachiger EU Hinweis: Hinweis fr Gerte der Klasse A EU-Richtlinie
zur Elektromagnetischen Vertrglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie
2004/108/EG zur Angleichung der Rechtsvorschriften ber die elektromagnetische
Vertrglichkeit in den EU-Mitgliedsstaaten und hlt die Grenzwerte der EN 55022
Klasse A ein.
Um dieses sicherzustellen, sind die Gerte wie in den Handbchern beschrieben zu
installieren und zu betreiben. Des Weiteren drfen auch nur von der IBM
empfohlene Kabel angeschlossen werden. IBM bernimmt keine Verantwortung fr
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der
IBM verndert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Gerte mssen mit folgendem Warnhinweis versehen werden:
Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Strungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Manahmen zu ergreifen und dafr
aufzukommen.
678
Deutschland: Einhaltung des Gesetzes ber die

elektromagnetische Vertrglichkeit von Gerten
Dieses Produkt entspricht dem Gesetz ber die elektromagnetische Vertrglichkeit
von Gerten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in
der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz ber die

elektromagnetische Vertrglichkeit von Gerten (EMVG) (bzw. der
EMC EG Richtlinie 2004/108/EG) fr Gerte der Klasse A
Dieses Gert ist berechtigt, in bereinstimmung mit dem Deutschen EMVG das
EG-Konformittszeichen - CE - zu fhren.
Verantwortlich fr die Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland GmbH
Technical Regulations, Abteilung M372
IBM-Allee 1, 71139 Ehningen, Germany
Telephone: 0049 (0) 7032 15-2941
Email: lugi@de.ibm.com
Generelle Informationen:
Das Gert erfllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse
A.
Japan VCCI Class A statement
This is a Class A product based on the standard of the Voluntary Control Council
for Interference (VCCI). If this equipment is used in a domestic environment, radio
interference may occur, in which case the user may be required to take corrective
actions.
Notices
679
Japan Electronics and Information Technology Industries

Association (JEITA) statement
Japan Electronics and Information Technology Industries Association (JEITA)

Confirmed Harmonics Guidelines with Modifications (products greater than 20 A
per phase)
Korea Communications Commission (KCC) statement
This is electromagnetic wave compatibility equipment for business (Type A). Sellers
and users need to pay attention to it. This is for any areas other than home.
Russia Electromagnetic Interference (EMI) Class A statement
People's Republic of China Class A electronic emission

statement
680
Taiwan Class A compliance statement
Notices
681
682
Index
A
ABR, automatic boot failure
recovery 160
ac good LED 129
ac power LED 21
accessible documentation 676
acoustical noise emissions 8
Active Energy Manager plug-in 9
adapter
installing 52
PCI Express bus 207
PCI-X bus 207
remote battery
installing 71, 228
removing 227
replacing 207
adapter, installation 51
adapter, replacing 209
adapter, ServeRAID
installing 54
removing 225
adapter, ServeRAID SAS/SATA
installing 226
adapters supported 51
administrator password 93
air baffle
removing 37
replacing 78, 206
air baffler
removing 205
applying current firmware
using best practices 25
assertion event, system-event log 130
assistance, getting 669
attention notices 6
Australia Class A statement 678
automatic boot failure recovery
(ABR) 160
availability, server 13
B
backplane assembly, hot-swap SAS/SATA
removing 270
backplane, hot-swap SAS/SATA
removing 269
replacing 269
backup firmware
starting 95
battery, replacing 257
battery, system
installing 257
replacing 255
bays 6
best practices
use to apply current firmware and
device-driver updates 25
bezel
removing 204
blue screen capture features 11, 85
blue-screen capture feature

overview 11, 85, 98
blue-screen feature 98
boot manager program
using 94
Business Partners instructions 25, 26
button, presence detection 17
C
cables
connecting 81
cables, power and signal
connecting to internal drives 174
cabling
the 4x2.5-inch hot-swap drive
backplane 179
backplane 183
the hot-swap SATA drive backplane
assembly 192
the optical drive 174
the power interposer card
assembly 176
the simple-swap SATA drive backplate
assembly 197
call home feature
IBM Electronic Service Agent 137
Service Advisor 136
call home tools 136
caution statements 6
CD drive
installing 220
problems 138
removing 219
replacing 215
CD-RW/DVD
drive activity LED 16
eject button 16
CD/DVD
replacing 216
channels, memory
associated with the DIMM
connectors 39
checkout procedure 116
performing 117
China Class A electronic emission
statement 680
Class A electronic emission notice 677
collecting data 113
completing
the options installation 77
components
on the server 161
server 27
configuration
ServerGuide Setup and Installation
CD 83
Setup utility 83
configuration cable,
routing 179, 183, 192
configuration, server
updating 82
configuring
UEFI compatible devices 84
with ServerGuide 87
configuring the server 84
configuring your server 83
connecting
the cables 81
connecting drive cables 174
connector
Ethernet and system-management 22
power supply 21
serial 21
USB 16, 21
video
front 16
rear 21
connectors
external 28
for options on the system board 31
internal 28
on the rear of the server 19
rear 19
connectors, internal system board 28
consumable parts 169
contamination, particulate and
gaseous 8, 675
controllers
Ethernet 100
controls and LEDs
on the light path diagnostics
panel 18, 122
on the operator information panel 16
controls, LEDs, and power 15
cooling 11
cover
removing 202
cover, removing 36
cover, server
replacing 80, 203
creating
software RAID 102
creating a personalized support web
page 671
CRUs, replacing
adapter 207
CD or DVD drive 215
DIMMs 223
memory 223
system battery 255
custom support web page 671
customer replaceable units (CRUs),
server 161
D
danger statements 6
data collection 113
dc good LED 129
dc power LED 21
683
deassertion event, system-event log 130

device drivers 95
devices
installing 25
devices, static-sensitive
handling 36
diagnostic
test log, viewing 136
text message format 136
tools, overview 118
diagnostic event log 131
diagnostics program
DSA Preboot 9
DIMM connectors
associated with each
microprocessor 39
DIMM connectors on
each memory channel 39
DIMM population sequence 40, 41
DIMMs
installation sequence for independent
mode 40
installing 38
order of installation for non-mirroring
mode 40
removing 223
replacing 224
display problems 146
documentation
Documentation Browser 4
Documentation CD 3
using 670
documentation format 676
documentation, updated
finding 5
drive
hot-swap SAS/SATA
removing 210
drive backplane assembly, 4x2.5-inch
hot-swap
installing 74
drive backplane, 4x2.5-inch hot-swap
cabling 179
drive backplane, 8x2.5-inch hot-swap
cabling 183
drive, CD/DVD
installing 220
removing 219
drive, hot-swap 44, 211
removing 210
SAS/SATA IDs 45, 212
drive, simple-swap 46
drives
connecting power and signal
cables 174
installing 43
drives, SAS/SATA
hot-swap 44, 211
drives, SATA
simple-swap 46
DSA
program, overview 134
DSA data
how to send to IBM 26
DSA event log 131
DSA Portable 118, 134
DSA Preboot 9, 119, 134
684
DSA, sending data to IBM 670

DVD drive
installing 220
problems 138
removing 219
replacing 215
Dynamic System Analysis (DSA) Preboot
diagnostics program 9
E
electrical equipment, servicing x
electrical input 8
electronic emission Class A notice 677
Electronic emission notices 677
embedded hypervisor
using 97
environment 8
error codes and messages
Integrated Management Module II
(IMM2) 291
messages, diagnostic 134
UEFI (POST) 525
error logs
clearing 133
viewing 131
error messages 137
error messages, Integrated Management
Module II (IMM2) 291
error symptoms
CD drive, DVD drive 138
general 139
hard disk drive 140
hypervisor flash device 139
intermittent 142
keyboard, non-USB 143
memory 145
microprocessor 146
monitor 146
mouse, non-USB 143
network 149
optional devices 150
pointing device, non-USB 143
power 151
serial port 152
ServerGuide 153
software 154
USB port 154
errors
format, diagnostic code 136
power supply LEDs 129
Ethernet 11
controller
troubleshooting 155
link status LED 22
Ethernet activity
LED 17, 22
Ethernet and system-management
connector 22
Ethernet support 10
European Union EMC Directive
conformance statement 678
event log, DSA 131
event log, IMM2 131
event log, POST 130
event log, system 130
event log, viewing through the web

interface 131
event logs 130
viewing through the Setup
utility 131
viewing without restarting the
server 131
event logs, methods for viewing 132
events, Integrated Management Module
II (IMM2) 291
expansion bays 6
external connectors 28
F
fan
replacing 221
fans 11
FCC Class A notice 677
features 6
ServerGuide 86
features, remote presence and
blue-screen 11, 85
field replaceable units (FRUs),
server 161
finding
updated documentation 5
firmware updates 1
firmware updates best practices 25
firmware, server
updating 56
firmware, server, recovering 158
firmware, updating 83
front USB connector board
removing 259
replacing 261, 263
front video connector
removing 262
front video connector \
removing 262
front view
LED location 15
front view of the server 15
G
gaseous contamination 8, 675
Germany Class A statement 678
grease, thermal 60, 280
guidelines
for options installation 34
for system reliability 35
servicing electrical equipment x
trained service technicians ix
H
handling static-sensitive devices 36
hard disk drive
problems 140
hard disk drive activity LED 15
hard disk drive status LED 15
hardware RAID cable,
routing 181, 186, 190, 195, 199
hardware service and support telephone
numbers 671
heat output 8
heat sink
installing 55, 59
replacing 275
help
from the World Wide Web 670
from World Wide Web 670
sending diagnostic data to IBM 670
sources of 669
hot-swap dc power supply
installing 64
replacing 240
hot-swap drive
SAS/SATA IDs 45, 212
hot-swap drive backplane assembly,
4x2.5-inch hot-swap
installing 74
hot-swap drive, SAS/SATA
removing 210
hot-swap SAS/SATA backplane
installing 269
removing 269
hot-swap SAS/SATA drive
installing 44, 211
how to send DSA data to IBM 26
Human Interface Infrastructure
configuration utility program 102
humidity 8
hypervisor
removing 229
hypervisor flash device
installing 70
problems 139
hypervisor flash devicer
installing 231
I
IBM Advanced Settings Utility program
overview 104
IBM Electronic Service Agent 137
IBM Systems Director 9
systems management tool 14
updating 104
IBM Taiwan product service 671
IBM, next generation technology 9
IDs for SAS/SATA hot-swap drives 45,
212
IMM IP address
obtaining 99
IMM2 event log 131
important notices 6, 674
independent mode DIMM population
sequence
on the server 40
Industry Canada Class A emission
compliance statement 677
information center 670
inspecting for unsafe conditions ix
installation guidelines 34
installation, options
completing 77
installing
a fan 221
a heat sink 59
a hot-swap power supply 61
a microprocessor 55, 56
installing (continued)
a PCI riser-card assembly 50
a RAID adapter remote battery 71,
228
a ServeRAID controller 226
an adapter 51, 52
battery, system 257
hot-swap dc power supply 64
hot-swap SAS/SATA drive 44, 211
hypervisor flash device 70, 231
memory modules 38
operator-information panel 254
power interposer card assembly 267
simple-swap SATA drive 46
backplane assembly 74
the air baffle 78, 206
the CD/DVD cable 220
the heat sink 55, 59, 279
the hot-swap SAS/SATA
backplane 269
the IBM ServeRAID controller 54
the simple-swap SATA drive and
backplate assembly 271
the system board 286
installing drives 43
installing options 25
installing, DIMMs 38
instructions for IBM Business
Partners 25, 26
integrated baseboard management
controller 23, 24
integrated functions 6
integrated management module
overview 9
(IMM2) error messages 291
(IMM2) events 291
intermittent problems 142
internal connectors 28
internal LEDs 28
internal, system board connectors 28
IP address
obtaining for the IMM 99
IPMItool 131
J
Japan Electronics and Information
Technology Industries Association
statement 680
Japan VCCI Class A statement 679
Japan Voluntary Control Council for
Interference Class A statement 679
JEITA statement 680
jumper
UEFI boot recovery 158
jumpers 28
on the system board 29
jumpers, on the system board 29
K
keyboard problems 143
Korea Communications Commission
statement 680
L
LED
ac power 21
dc power 21
Ethernet-link status 22
for CD-RW/DVD drive activity 16
for Ethernet activity 17, 22
for hard disk drive activity 15
for hard disk drive status 15
for solid state drive activity 15
for solid state drive status 15
power-on 17
power-supply error 21
system locator 17
system log 17
system-error 17
LED errors
power supply 129
LEDs
light path diagnostics 11, 120
LEDs 123
light path diagnostics LEDs 123
light path diagnostics panel
controls and LEDs 18, 122
location 16
local area network (LAN) 10
log, event, viewing through the web
interface 131
logs, event 130
LSI Configuration Utility program 102
M
management, system 9
memory
removing 223
replacing 224
specifications 6
memory installation sequence
for independent mode 40
memory module
installing 38
memory problems 145
memory support 10
memory-mirroring mode 41
description 41
memory-mirroring mode DIMM
population sequence
on the server 41
messages
diagnostic 134
messages, error
POST 525
methods, for viewing event logs 132
microprocessor 11
and thermal grease 60, 280
associated with each DIMM 39
installing 55, 56
problems 146
Index
685
microprocessor (continued)
replacing 275
specifications 6
Mobile access to IBM Service Information
website 11
model and serial number
location 157
monitor problems 146
N
network problems 149
New Zealand Class A statement
next generation technology 9
NOS installation
with ServerGuide 87
without ServerGuide 87
notes 6
notes, important 674
notices 673
electronic emission 677
FCC, Class A 677
notices and statements 6
Nx boot failure 160
678
O
obtaining
the IP address for the IMM 99
online documentation 1
online publications 5
operator information panel
controls and LEDs 16
removing 253, 254
operator information panel release
latch 16
optical
replacing 47
optical drive
cabling 174
optical drive, optional
specifications 6
optional device connectors
optional device problems 150
options
installing 25
P
particulate contamination 8, 675
parts listing, server 161
parts listing, System x3530 M4 163
parts, consumable 169
parts, structural 170
password 93
administrator 93
power-on 93
password, power-on
switch on the system board 94
PCI
riser-card assembly 251
replacing 252
PCI expansion slots 6
PCI riser
slot 1 21
686
PCI riser (continued)

slot 2 21
PCI riser-card assembly
installing 50
replacing 79
People's Republic of China Class A
electronic emission statement 680
POST
error codes 525
error log 131
POST event log 130
POST test 133
power
power-control button 17
specifications 8
supply 6
power and signal cables
power cable,
routing 179, 184, 188, 193, 197
power features
of the server 23
power interposer card assembly
cabling 176
removing 265
replacing 267
power problems 151, 155
power supplies
redundancy support 11
power supply
installing 61
power supply LED errors 129
power supply, fixed
removing 245
replacing 247
power supply, hot-swap
removing 232
replacing 234
power-on LED 17, 23
power-on password 93
power-supply error LED 21
Preboot, DSA 9
presence detection button 17
problem isolation tables 137
problems
CD/DVD drive 138
Ethernet controller 155
hard disk drive 140
intermittent 142
memory 145
microprocessor 146
monitor 146
mouse 143, 144
network 149
optional devices 150
pointing device 144
power 151, 155
serial port 152
software 154
troubleshooting 113
undetermined 156
USB port 154
video 146, 155
procedure, checkout 117
product service, IBM Taiwan 671
R
rack release latches 15
RAID battery cable, remote
routing 178
rank sparing
description 40
rank sparing mode 40
rank sparing mode DIMM population
sequence
on the server 40
RAS features, server 13
rear view 19
of the server 19
recovering the server firmware 158
redundancy support
power supplies 11
redundant
cooling 11
Ethernet connection 11
NIC 11
Redundant
Ethernet capabilities 13
hot-swap power supplies 13
redundant array of independent disks
(RAID)
adapter 45, 47, 212
related documentation 5
reliability, server 13
remind button 19, 123
remote battery, RAID adapter
installing 71, 228
removing 227
remote presence feature 85
using 98
removing
a fan 221
a hot-swap drive 210
a power interposer card
assembly 265
a RAID adapter remote battery 227
a ServeRAID adapter 225
adapter 207
battery, system 255
CD or DVD drive 215
DIMM 223
fixed power supply 245
hypervisor 229
the bezel 204
the front USB connector board 259
the front video connector 262
the hot-swap SAS/SATA
backplane 269
the SATA backplate assembly 270
the simple-swap SATA backplate
assembly 270
removing and replacing
Tier 1 CRUs 207
removing the cover 36, 202
removing/replacing
operator information panel 253, 254
replacement parts for the server 161
replacing
a CD/DVD 216
a heat sink 275
a microprocessor 275
a optical 47
a PCI riser-card assembly 79, 252
battery, system 255, 257
CD or DVD drive 215
fixed power supply 247
hot-swap SAS/SATA backplane 269
memory DIMMs 224
power interposer card assembly 267
the front USB connector board 261,
263
the server cover 80, 203
the simple-swap SATA drive and
backplate assembly 271
notes to consider 286
replacing an adapter 209
reset button 17, 19, 123
riser-card assembly
location 207
routing
the configuration cable 179, 183, 192
the hardware RAID cable 181, 186,
190, 195, 199
the power cable 179, 184, 188, 193,
197
the remote RAID battery cable 178
the software RAID cable 182, 187,
191, 196, 200
Russia Class A electromagnetic
interference statement 680
Russia Electromagnetic Interference (EMI)
Class A statement 680
S
safety vii
safety statements vii, xi
SAS/SATA drive
hot-swap
removing 210
SAS/SATA hot-swap drive
installing 44, 211
SAS/SATA IDs
for hot-swap drives 45, 212
SATA simple-swap drive
installing 46
sending diagnostic data to IBM 670
sending DSA data
to IBM 26
serial and model number
location 157
serial connector 21
serial number 1
serial port problems 152
server
configuring 84
offerings 9
power features 23
server (continued)
turning it off 23
turning it on 23
server , backup firmware
starting 95
server components 27, 161
server configuration
updating 82
server controls, LEDs, and power 15
server firmware
updating 56
server firmware, recovering 158
server rear view 19
server replaceable units 161
server shutdown 23
server, front view 15
ServeRAID controller
installing 54
ServeRAID support 12
ServerGuide
features 86
NOS installation 87
setup 87
Setup and Installation CD 83
using 86
ServerGuide CD 1, 9
Service Advisor feature 136
service and support
before you call 669
hardware 671
software 671
service bulletins 116
serviceability, server 13
servicing electrical equipment x
Setup utility 83
starting 88
using 88
shutting down the server 23
signal and power cables
simple-swap SATA backplate assembly
removing 270
simple-swap SATA drive
installing 46
simple-swap SATA drive and backplate
assembly
installing 271
simple-swap SATA drive backplate
assembly
cabling 192, 197
size 8
slots
PCI expansion 6
SMP 11
software problems 154
software RAID
creating 102
software RAID cable,
routing 182, 187, 191, 196, 200
software service and support telephone
numbers 671
software, RAID
creating 102
solid state drive activity LED 15
solid state drive status LED 15
solid state drive, ServeRAID controller
removing 225
specifications 6
standby mode 23
starting
the backup firmware 95
the Setup utility 88
statements and notices 6
static-sensitive devices
handling 36
structural parts 170
support web page, custom 671
symmetric multiprocessing 11
system
error LED front 17
locator LED, front 17
System
Log LED 17
system board
external connectors 28
installing 286
internal connectors 28
jumpers 29
LEDs 30
power-on password switch 94
removing 281
system board internal connectors 28
system board jumpers
description 29
system board optional devices
connectors 31
system event logs 131
system reliability guidelines 35
system-event log 130
system-event log, assertion event 130
system-event log, deassertion event 130
systems management 9, 12
systems management tool
T
Taiwan Class A compliance
statement 681
telecommunication regulatory
statement 677
telephone numbers 671
temperature 8
test log, viewing 136
thermal grease 60, 280
Tier 1 CRUs
removing and replacing 207
TOE 6
tools, call home 136
tools, diagnostic 118
trademarks 674
trained service technicians, guidelines
troubleshooting 113
turning off the server 23
integrated baseboard management
controller 23, 24
turning on the server 23
ix
U
UEFI
boot recovery jumper
error codes 525
158
Index
687
UEFI compatible devices

configuring 84
undetermined problems 156
undocumented problems 115
United States electronic emission Class A
notice 677
United States FCC Class A notice 677
Universal Serial Bus (USB) problems 154
unsafe conditions, inspecting for ix
UpdateXpress 95
updating
server firmware 56
Systems Director, IBM 104
the server configuration 82
updating firmware 83
USB
connector 16, 21
using
embedded hypervisor 97
the boot manager program 94
the remote presence feature 98
the Setup utility 88
using best practices
to apply firmware and device-driver
updates 25
Utility program
IBM Advanced Settings 104
utility, Setup
starting 88
using 88
V
video connector
front 16
rear 21
video controller, integrated
specifications 6
video problems 146
viewing
event logs through the Setup
utility 131
viewing event logs
without restarting the server 131
W
Wake on LAN feature 23
Web site
UEFI flash diskette 158
weight 8
what the server offers 9
688

Part Number: 00KC103
Printed in USA
(1P) P/N: 00KC103

X 3530 M 4 Ibm

Uploaded by

Copyright:

Available Formats

X 3530 M 4 Ibm

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

X 3530 M 4 Ibm

Uploaded by

Copyright:

Available Formats

Installation and Service Guide

Installation and Service Guide

Seventh Edition (April 2014)

Chapter 1. The IBM System x3530 M4

Chapter 2. Installing optional devices

Chapter 3. Configuration information

Chapter 4. Troubleshooting . . . . . 113

Chapter 5. Parts listing, IBM System

System x3530 M4 Type 7160: Installation and Service Guide

Chapter 6. Removing and replacing

Replacing the system battery . . . . . .

Appendix A. Integrated Management

Appendix C. DSA diagnostic test

Appendix D. Getting help and

System x3530 M4 Type 7160: Installation and Service Guide

Antes de instalar este produto, leia as Informaes de Segurana.

Ls sikkerhedsforskrifterne, fr du installerer dette produkt.

Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.

Copyright IBM Corp. 2014

Les sikkerhetsinformasjonen (Safety Information) fr du installerer dette produktet.

Antes de instalar este produto, leia as Informaes sobre Segurana.

Antes de instalar este producto, lea la informacin de seguridad.

Bu rn kurmadan nce gvenlik bilgilerini okuyun.

System x3530 M4 Type 7160: Installation and Service Guide

Guidelines for trained service technicians

Inspecting for unsafe conditions

Guidelines for servicing electrical equipment

System x3530 M4 Type 7160: Installation and Service Guide

1. Turn everything OFF.

1. Turn everything OFF.

2. First, attach all cables to devices.

2. First, remove power cords from outlet.

3. Attach signal cables to connectors.

3. Remove signal cables from connectors.

4. Attach power cords to outlet.

4. Remove all cables from devices.

5. Turn device ON.

System x3530 M4 Type 7160: Installation and Service Guide

Class 1 Laser Product

System x3530 M4 Type 7160: Installation and Service Guide

Rack Safety Information, Statement 2

System x3530 M4 Type 7160: Installation and Service Guide

Chapter 1. The IBM System x3530 M4 7160 server

Copyright IBM Corp. 2014

Drive bay 1 Drive bay 3 Drive bay 5 Drive bay 7

Drive status LED

Figure 1. Front view: 2.5-inch model

Video connector (optional)

Rack release latch

Figure 2. Front view: 3.5-inch model

IBM System x3530 M4

System x3530 M4 Type 7160: Installation and Service Guide

The IBM Documentation CD

Chapter 1. The IBM System x3530 M4 7160 server

Hardware and software requirements

Using the Documentation Browser

System x3530 M4 Type 7160: Installation and Service Guide

Chapter 1. The IBM System x3530 M4 7160 server

Notices and statements in this document