x3650 m4 Troubleshooting

System x3650 M4
Type 7915
Installation and Service Guide

System x3650 M4
Type 7915
Installation and Service Guide
Note
Before using this information and the product it supports, read the general information in
Appendix D, “Getting help and technical assistance,” on page 981, “Notices” on page 985, the
Warranty Information document, and the Safety Information and Environmental Notices and User Guide
documents on the IBM Documentation CD.
Fourteenth Edition (August 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 Installing an optional ServeRAID upgrade adapter 69
Safety statements . . . . . . . . . . . . ix Installing a ServeRAID SAS controller battery on the
remote battery tray . . . . . . . . . . . . 70
Chapter 1. The System x3650 M4 server 1 Installing the dual-port network adapter. . . . . 73
Installing a hot-swap ac power supply . . . . . 76
The IBM Documentation CD . . . . . . . . .4
Installing a hot-swap dc power supply . . . . . 79
Hardware and software requirements . . . . .4
Installing a hot-swap fan . . . . . . . . . . 84
The IBM Documentation CD . . . . . . . .4
Installing a SAS/SATA 8 Pac HDD option . . . . 86
Related documentation . . . . . . . . . . .5
Installing a 16 x 2.5-inch Hot-Swap HDD Assembly
Notices and statements in this document . . . . .6
Kit with Expander for 12Gb RAID . . . . . . . 92
Server features and specifications . . . . . . .7
Installing a SAS/SATA 8 Pac HDD with a
What your server offers . . . . . . . . . . 11
ServeRAID adapter option . . . . . . . . . 97
Reliability, availability, and serviceability . . . . 15
Installing a 16x2.5-inch Hot-Swap HDD Assembly
IBM Systems Director . . . . . . . . . . . 16
Kit for 12Gb/6Gb RAID . . . . . . . . . . 104
Server controls, LEDs, and power . . . . . . . 17
Installing a SAS/SATA 8 Pac HDD with two 6 GB
Front view. . . . . . . . . . . . . . 17
performance optimized HBA adapters option. . . 110
Operator information panel . . . . . . . . 19
Installing 2 x 8 1.8-inch SSDs with two 6 GB
Light path diagnostics panel . . . . . . . . 20
Rear view . . . . . . . . . . . . . . 21
Installing 4 x 8 1.8-inch SSDs with two 6 GB
Server power features . . . . . . . . . . 24
Turning on the server . . . . . . . . . 24
Installing an optional tape drive . . . . . . . 130
Turning off the server . . . . . . . . . 24
Installing a USB embedded hypervisor flash device 133
Installing an additional microprocessor and heat
Chapter 2. Installing optional devices 27 sink . . . . . . . . . . . . . . . . 134
Instructions for IBM Business Partners . . . . . 28 Thermal grease . . . . . . . . . . . . 141
How to send DSA data to IBM . . . . . . . . 28 Completing the installation . . . . . . . . . 142
Server components . . . . . . . . . . . . 29 Replacing the air baffle . . . . . . . . . 143
System-board internal connectors . . . . . . 30 Installing a PCI riser-card assembly . . . . . 144
System-board external connectors . . . . . . 31 Replacing the cover . . . . . . . . . . 145
System-board switches, jumpers, and buttons . . 32 Connecting the external cables. . . . . . . 146
System-board LEDs. . . . . . . . . . . 34 Updating the server configuration . . . . . 147
System-board optional-device connectors . . . 34
PCI riser-card adapter connectors . . . . . . 35
Chapter 3. Configuration information
PCI riser-card assembly LEDs . . . . . . . 36
Installation guidelines . . . . . . . . . . . 36 and instructions . . . . . . . . . . 149
System reliability guidelines . . . . . . . . 38 Updating the firmware . . . . . . . . . . 149
Working inside the server with the power on . . 38 Configuring the server . . . . . . . . . . 150
Handling static-sensitive devices . . . . . . 39 Using the ServerGuide Setup and Installation
Removing the cover . . . . . . . . . . . 39 CD . . . . . . . . . . . . . . . . 152
Removing a PCI riser-card assembly . . . . . . 40 ServerGuide features . . . . . . . . . 153
Removing the air baffle . . . . . . . . . . 42 Setup and configuration overview . . . . 153
Stretching a PCI riser-card assembly . . . . . . 43 Typical operating-system installation . . . 153
Shrinking a PCI riser-card assembly . . . . . . 44 Installing your operating system without
Installing drives . . . . . . . . . . . . . 44 using ServerGuide. . . . . . . . . . 154
Drive IDs . . . . . . . . . . . . . . 45 Using the Setup utility . . . . . . . . . 154
Installing a hot-swap hard disk drive . . . . . . 45 Starting the Setup utility . . . . . . . 154
Installing a simple-swap hard disk drive . . . . 46 Setup utility menu choices . . . . . . . 155
Installing a 1.8-inch hot-swap solid state drive. . . 48 Passwords . . . . . . . . . . . . 159
Installing an optional DVD drive . . . . . . . 49 Using the Boot Manager. . . . . . . . . 161
Installing an optional DVD drive cable . . . . . 52 Starting the backup server firmware . . . . . 161
Installing a memory module. . . . . . . . . 54 The UpdateXpress System Pack Installer . . . 161
DIMM installation sequence . . . . . . . . 58 Using the integrated management module. . . 162
Memory mirrored channel . . . . . . . . 59 Using the remote presence and blue-screen
Memory rank sparing . . . . . . . . . . 60 capture features . . . . . . . . . . . 163
Installing a memory module. . . . . . . . 61 Obtaining the IMM host name. . . . . . 164
Installing an adapter . . . . . . . . . . . 64 Obtaining the IP address for the IMM . . . 164
© Copyright IBM Corp. 2014 iii

Logging on to the web interface . . . . . 165 ServerGuide problems . . . . . . . . . 224
Using the embedded hypervisor . . . . . . 166 Software problems. . . . . . . . . . . 225
Configuring the Ethernet controller . . . . . 167 Universal Serial Bus (USB) port problems . . . 226
Enabling Features on Demand Ethernet software 167 Video problems. . . . . . . . . . . . 226
Enabling Features on Demand RAID software 167 Solving power problems. . . . . . . . . . 226
Configuring RAID arrays . . . . . . . . 167 Solving Ethernet controller problems . . . . . 228
IBM Advanced Settings Utility program . . . 168 Solving undetermined problems . . . . . . . 229
Updating IBM Systems Director . . . . . . 168 Problem determination tips. . . . . . . . . 230
Installing a newer version . . . . . . . 169 Recovering the server firmware (UEFI update
Installing updates with your management failure) . . . . . . . . . . . . . . . 231
server is connected to the Internet . . . . 169 In-band manual recovery method . . . . . 231
Installing updates with your management In-band automated boot recovery method . . . 233
server is not connected to the Internet . . . 169 Out-of-band method . . . . . . . . . . 233
Updating the Universal Unique Identifier Automated boot recovery (ABR) . . . . . . . 233
(UUID) . . . . . . . . . . . . . . 170 Nx-boot failure . . . . . . . . . . . . . 234
Updating the DMI/SMBIOS data . . . . . . 172
Chapter 5. Parts listing, System x3650
Chapter 4. Troubleshooting . . . . . 177 M4 Type 7915 . . . . . . . . . . . 235
Start here. . . . . . . . . . . . . . . 177 Replaceable server components . . . . . . . 235
Diagnosing a problem . . . . . . . . . 177 Structural parts . . . . . . . . . . . . 246
Undocumented problems . . . . . . . . 179 Power cords . . . . . . . . . . . . . . 247
Service bulletins . . . . . . . . . . . . 180
Checkout procedure . . . . . . . . . . . 180 Chapter 6. Removing and replacing
About the checkout procedure. . . . . . . 180
Performing the checkout procedure . . . . . 181
components . . . . . . . . . . . . 249
Diagnostic tools . . . . . . . . . . . . 182 Returning a device or component . . . . . . 249
Light path diagnostics . . . . . . . . . 184 Internal cable routing and connectors . . . . . 249
Light path diagnostics LEDs . . . . . . 187 General cable routing connections . . . . . 250
Power-supply LEDs . . . . . . . . . 191 Cabling DVD drive . . . . . . . . . 250
System pulse LEDs . . . . . . . . . 195 Cabling front USB and video connector. . . 251
PCI riser-card LEDs . . . . . . . . . 195 Cabling operator information panel . . . . 252
Event logs . . . . . . . . . . . . . 196 Cabling VGA power connector . . . . . 253
Viewing event logs through the Setup utility 197 2.5-inch hard disk drive cable connection . . . 254
Viewing event logs without restarting the 8-drive-capable model . . . . . . . . 254
server . . . . . . . . . . . . . . 197 16-drive-capable model . . . . . . . . 255
Clearing the event logs . . . . . . . . 198 3.5-inch hard disk drive cable connection . . . 257
POST . . . . . . . . . . . . . . . 199 Removing and replacing server components . . . 258
IBM Dynamic System Analysis . . . . . . 199 Removing and replacing structural parts . . . 258
DSA editions . . . . . . . . . . . 200 Removing the cover . . . . . . . . . 259
Running the DSA Preboot diagnostic Replacing the cover . . . . . . . . . 260
programs . . . . . . . . . . . . . 201 Removing the air baffle . . . . . . . . 261
Diagnostic text messages . . . . . . . 202 Replacing the air baffle . . . . . . . . 262
Viewing the test log results and transferring Removing a RAID adapter battery holder 264
the DSA collection . . . . . . . . . . 202 Replacing a RAID adapter battery holder . . 265
Automated service request (call home) . . . . . 202 Removing the bezel . . . . . . . . . 266
IBM Electronic Service Agent . . . . . . . 203 Replacing the bezel . . . . . . . . . 266
Error messages . . . . . . . . . . . . . 203 Removing the 240 VA safety cover . . . . 267
Troubleshooting by symptom . . . . . . . . 203 Replacing the 240 VA safety cover . . . . 268
CD/DVD drive problems . . . . . . . . 204 Removing and replacing Tier 1 CRUs . . . . 270
General problems . . . . . . . . . . . 205 Removing a hot-swap hard disk drive . . . 270
Hard disk drive problems . . . . . . . . 205 Replacing a hot-swap hard disk drive . . . 271
Hypervisor problems . . . . . . . . . . 207 Removing a simple-swap hard disk drive 273
Intermittent problems . . . . . . . . . 208 Replacing a simple-swap hard disk drive . . 274
Keyboard, mouse, or USB-device problems . . 208 Removing a 1.8-inch hot-swap solid state
Memory problems . . . . . . . . . . . 209 drive . . . . . . . . . . . . . . 276
Microprocessor problems . . . . . . . . 211 Replacing a 1.8-inch hot-swap solid state
Monitor and video problems . . . . . . . 212 drive . . . . . . . . . . . . . . 277
Network connection problems . . . . . . . 214 Removing a DVD drive . . . . . . . . 278
Optional-device problems . . . . . . . . 214 Replacing a DVD drive . . . . . . . . 279
Power problems . . . . . . . . . . . 215 Removing the DVD drive cable . . . . . 282
Serial-device problems . . . . . . . . . 224 Replacing the DVD drive cable . . . . . 283
iv System x3650 M4 Type 7915: Installation and Service Guide

Removing a tape drive . . . . . . . . 286 Appendix A. Integrated management
Replacing a tape drive . . . . . . . . 287 module II (IMM2) error messages . . . 373
Removing a memory module . . . . . . 288
Installing a memory module . . . . . . 289
Removing the fan bracket . . . . . . . 298
Appendix B. UEFI/POST diagnostic
Replacing the fan bracket . . . . . . . 300 codes. . . . . . . . . . . . . . . 827
Removing a PCI riser-card assembly. . . . 301
Replacing a PCI riser-card assembly . . . . 302 Appendix C. DSA diagnostic test
Removing an adapter. . . . . . . . . 304 results . . . . . . . . . . . . . . 845
Replacing an adapter . . . . . . . . . 305 DSA Broadcom network test results . . . . . . 845
Removing an optional ServeRAID upgrade DSA Brocade test results. . . . . . . . . . 854
adapter memory module . . . . . . . 308 DSA checkpoint panel test results . . . . . . 862
Replacing an optional ServeRAID upgrade DSA CPU stress test results. . . . . . . . . 863
adapter memory module . . . . . . . 311 DSA Emulex adapter test results . . . . . . . 866
Removing a remotely installed RAID adapter DSA EXA port ping test results . . . . . . . 869
battery/flash power module . . . . . . 313 DSA hard drive test results . . . . . . . . . 871
Replacing a RAID adapter battery/flash DSA Intel network test results . . . . . . . . 873
power module remotely in the server . . . 315 DSA LSI hard drive test results . . . . . . . 878
Removing the dual-port network adapter . . 318 DSA Mellanox adapter test results . . . . . . 879
Replacing the dual-port network adapter . . 319 DSA memory isolation test results . . . . . . 882
Removing a hot-swap ac power supply . . 322 DSA memory stress test results . . . . . . . 952
Replacing a hot-swap ac power supply . . . 324 DSA Nvidia GPU test results . . . . . . . . 955
Removing a hot-swap dc power supply . . 327 DSA optical drive test results . . . . . . . . 961
Replacing a hot-swap dc power supply. . . 330 DSA system management test results . . . . . 965
Removing a hot-swap fan . . . . . . . 336 DSA tape drive test results . . . . . . . . . 976
Replacing a hot-swap fan . . . . . . . 337
Removing the 2.5-inch simple-swap/hot-
Appendix D. Getting help and
swap hard disk drive backplate
assembly/backplane . . . . . . . . . 338 technical assistance . . . . . . . . 981
Replacing the 2.5-inch simple-swap/hot- Before you call . . . . . . . . . . . . . 981
swap hard disk drive backplate Using the documentation . . . . . . . . . 982
assembly/backplane . . . . . . . . . 339 Getting help and information from the World Wide
Removing the 3.5-inch simple-swap/hot- Web . . . . . . . . . . . . . . . . 982
swap hard disk drive backplate How to send DSA data to IBM . . . . . . . 982
assembly/backplane . . . . . . . . . 340 Creating a personalized support web page . . . 983
Replacing the 3.5-inch simple-swap/hot- Software service and support . . . . . . . . 983
swap hard disk drive backplate Hardware service and support . . . . . . . 983
assembly/backplane . . . . . . . . . 341 IBM Taiwan product service . . . . . . . . 983
Removing a USB embedded hypervisor flash
device . . . . . . . . . . . . . . 343 Notices . . . . . . . . . . . . . . 985
Replacing a USB embedded hypervisor flash Trademarks . . . . . . . . . . . . . . 986
device . . . . . . . . . . . . . . 344 Important notes . . . . . . . . . . . . 986
Removing the system battery . . . . . . 345 Particulate contamination . . . . . . . . . 987
Replacing the system battery . . . . . . 347 Documentation format . . . . . . . . . . 988
Removing the operator information panel Telecommunication regulatory statement . . . . 988
assembly . . . . . . . . . . . . . 349 Electronic emission notices . . . . . . . . . 989
Replacing the operator information panel Federal Communications Commission (FCC)
assembly . . . . . . . . . . . . . 350 statement. . . . . . . . . . . . . . 989
Removing and replacing Tier 2 CRUs . . . . 351 Industry Canada Class A emission compliance
Removing a microprocessor and heat sink 351 statement. . . . . . . . . . . . . . 989
Replacing a microprocessor and heat sink 356 Avis de conformité à la réglementation
Removing the heat-sink retention module 365 d'Industrie Canada . . . . . . . . . . 989
Replacing the heat-sink retention module . . 366 Australia and New Zealand Class A statement 989
Removing the system board . . . . . . 367 European Union EMC Directive conformance
Replacing the system board . . . . . . 370 statement. . . . . . . . . . . . . . 990
Germany Class A statement . . . . . . . 990
Japan VCCI Class A statement. . . . . . . 991
Japan Electronics and Information Technology
Industries Association (JEITA) statement . . . 992
Korea Communications Commission (KCC)
statement. . . . . . . . . . . . . . 992
Contents v
Russia Electromagnetic Interference (EMI) Class Taiwan Class A compliance statement . . . . 993
A statement . . . . . . . . . . . . . 992
People's Republic of China Class A electronic Index . . . . . . . . . . . . . . . 995
emission statement . . . . . . . . . . 992
vi System x3650 M4 Type 7915: Installation and Service Guide

Safety
Before installing this product, read the Safety Information.
Antes de instalar este produto, leia as Informações de Segurança.
Læs sikkerhedsforskrifterne, før du installerer dette produkt.
Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.
Ennen kuin asennat tämän tuotteen, lue turvaohjeet kohdasta Safety Information.
Avant d'installer ce produit, lisez les consignes de sécurité.
Vor der Installation dieses Produkts die Sicherheitshinweise lesen.
Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.
© Copyright IBM Corp. 2014 vii

Les sikkerhetsinformasjonen (Safety Information) før du installerer dette produktet.
Antes de instalar este produto, leia as Informações sobre Segurança.
Antes de instalar este producto, lea la información de seguridad.
Läs säkerhetsinformationen innan du installerar den här produkten.
viii System x3650 M4 Type 7915: Installation and Service Guide

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 ix
Statement 2
CAUTION:
When replacing the lithium battery, use only IBM® Part Number 33F8354 or an
equivalent type battery recommended by the manufacturer. If your system has a
module containing a lithium battery, replace it only with the same module type
made by the same manufacturer. The battery contains lithium and can explode if
not properly used, handled, or disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble
Dispose of the battery as required by local ordinances or regulations.
Statement 3
CAUTION:
When laser products (such as CD-ROMs, DVD drives, fiber optic devices, or
transmitters) are installed, note the following:
v Do not remove the covers. Removing the covers of the laser product could
result in exposure to hazardous laser radiation. There are no serviceable parts
inside the device.
v Use of controls or adjustments or performance of procedures other than those
specified herein might result in hazardous radiation exposure.
x System x3650 M4 Type 7915: Installation and Service Guide

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.
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 xi
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
xii System x3650 M4 Type 7915: Installation and Service Guide

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 xiii
xiv System x3650 M4 Type 7915: Installation and Service Guide
Chapter 1. The System x3650 M4 server
This Installation and Service Guide contains information and instructions for setting
up your System x3650 M4 Type 7915 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

27 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 28.
The IBM System x3650 M4 Type 7915 server is a 2-U-high1 rack model server for
high-volume network transaction processing. This high-performance, multi-core
server is ideally suited for networking environments that require superior
microprocessor performance, input/output (I/O) flexibility, 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, see the Warranty Information document that comes with the server.
The server contains IBM X-Architecture® technologies, which help increase

performance and reliability. For more information, see “What your server offers”
on page 11 and “Reliability, availability, and serviceability” on page 15.
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/.
Note: The illustrations in this document might differ slightly from your model.
The server comes with either six 3.5-inch SATA or eight 2.5-inch SAS hot-swap
hard disk drive bays. Most models contain a ServeRAID SAS controller and the
2.5-inch models are capable of expansion to sixteen 2.5-inch SAS hot-swap hard
disk drive bays.
1. Racks are marked in vertical increments of 1.75 inches each. Each increment is referred to as a unit, or a “U”. A 1-U-high device
is approximately 1.75 inches tall.
© Copyright IBM Corp. 2014 1

The following illustration shows a server with 3.5-inch SAS/SATA hot-swap hard
disk drive bays.
SAS hard disk

drive bays
0 1 2 3 4 5
Figure 1. 3.5-inch hot-swap model front view
The following illustration shows a server with six 3.5-inch SATA simple-swap hard
disk drive bays.
SATA hard disk

drive bays
0 1 2 3 4 5
Figure 2. 3.5-inch simple-swap model front view
The following illustration shows a server with eight 2.5-inch SAS hard disk drive
bays.
SAS hard disk

drive bays
0 1 2 3 4 5 6 7
Figure 3. 2.5-inch model front view
You can purchase an optional kit to install the tape drive.
SAS hard disk

drive bays
0 1 2 3 4 5 6 7
Figure 4. Tape drive model front view
You can purchase an optional kit to install the eight additional 2.5-inch SAS hard
disk drive bays.
2 System x3650 M4 Type 7915: Installation and Service Guide

SAS hard disk
drive bays
0 1 2 3 4 5 6 7 8 9 10 1112 13 14 15
Figure 5. 16-drive-capable model front view
The SAS ID for each bay is printed on the server front, above each bay.
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 IBM System x3650 M4 server

Machine type 7915
Model number _____________________________________________
Serial number _____________________________________________
The model number and serial number are 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 6. 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.
Chapter 1. The System x3650 M4 server 3

The following illustration shows the QR code (http://ibm.co/11mn8Gh):
Figure 7. 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 System x 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.
The IBM Documentation CD requires the following minimum hardware and

software:
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
The IBM Documentation CD

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 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 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 format on the IBM Documentation CD. It provides
translated versions of the IBM License Agreement for Machine Code for your
product.
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 Licenses and Attributions Documents
This document is in PDF format on the IBM Documentation CD. It provides the
open source notices.
v Rack Installation Instructions
This printed document contains instructions for installing the server in a rack
and comes with the rack kit.
v Safety Information

This document is in PDF format 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 Safety Information Labels
This document provides the Simplified Chinese, Mongolian, Tibetan, Uygur, and
Zhuang translated versions of the product safety labels.
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.
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/.
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 System x 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 Integrated functions: SATA optical drives (optional):
model): v Integrated Management Module II v DVD-ROM
v Supports up to two Intel Xeon™ (IMM2), which consolidates
v Multi-burner
E5-2600 series multi-core multiple management functions in
microprocessors (one installed) a single chip. Tape drive (optional):
v Intel I350AM4 Quad Port Gigabit
v Level-3 cache v Tape drive bay
Ethernet controller with Wake on
v Two QuickPath Interconnect (QPI) LAN support
links speed up to 8.0 GT per RAID controllers (depending on the
v Eight Universal Serial Bus (USB)
second model):
2.0 ports (two front and four rear
of the chassis, one internal used for v One on-board 8 ports SAS
Notes: ServeRAID M5110e that provides
USB tape drive, and one internal
v Use the Setup utility program to used for Hypervisor USB key) RAID levels 0, 1, and 10
determine the type and speed of v Six network ports (four 1 Gb v A ServeRAID M5110e SAS/SATA
the microprocessors. Ethernet ports on the system board adapter that provides RAID 0, 1,
v For a list of supported and two additional ports when the and 10.
microprocessors, see optional IBM Dual-Port 10 Gb Optional upgrade:
http://www.ibm.com/systems/ Network Daughter Card is
info/x86servers/serverproven/ – RAID 5/50 (Zero Cache)
installed)
compat/us/. v One System Management RJ-45 on – RAID 5/50 (512 MB Cache) with
the rear to connect to a systems optional FoD RAID 6/60 and
Memory (depending on the model): management network. This system SED upgrade
v Minimum: 2 GB management connector is – RAID 5/50 (512 MB Flash) with
v Maximum: 768 GB dedicated to the IMM2 functions. optional FoD RAID 6/60 and
– 64 GB using unbuffered DIMMs v One serial port SED upgrade
(UDIMMs) v Two VGA adapters
– 384 GB using registered DIMMs v Light path diagnostics panel – RAID 5/50 (1 GB Flash) with
(RDIMMs) optional FoD RAID 6/60 and
– 768 GB using HyperCloud SED upgrade
Hard disk drive expansion bays
DIMMs (HCDIMMs) (depending on the model): Video controller (integrated into
– 768 GB using load reduction v 1.8-inch models: Supports up to IMM2):
DIMMs (LRDIMMs) thirty-two 1.8-inch hot-swap v Matrox G200eR2
v Type: solid-state drivers. Note: The maximum video
– PC3-8500 (DDR3-1066),
v 2.5-inch models: resolution is 1600 x 1200 at 75 Hz.
PC3-10600 (DDR3-1333),
– SVGA compatible video
PC3-12800 (DDR3-1600), or – Supports up to sixteen 2.5-inch
controller
PC3-14900 (DDR3-1866) simple-swap SAS/SATA or
– DDR3 528 MHz SDRAM video
– Single-rank, dual-rank, or hot-swap SAS/SATA hard disk
memory controller
quad-rank drive bays.
– Avocent Digital Video
– Registered DIMM (RDIMM), – Supports up to eight 2.5-inch Compression
unbuffered DIMM (UDIMM), simple-swap SAS/SATA or – 16 MB of video memory (not
load reduced DIMM (LRDIMM), hot-swap SAS/SATA hard disk expandable)
or Flash DIMM drive bays with an option to
v Slots: 24 dual inline add up to sixteen 1.8-inch Size (2U):
v Supports (depending on the hot-swap solid-state drives. v Height: 86.5 mm (3.406 in.)
model): v Depth: EIA flange to rear - 714 mm
v 3.5-inch models:
– 4 GB unbuffered DIMM (28.110 in.), Overall - 746 mm
– 2 GB, 4 GB, 8 GB, and 16 GB – Supports up to six 3.5-inch (29.370 in.)
registered DIMMs simple-swap SATA or hot-swap v Width: With top cover - 445 mm
– 16 GB and 32 GB HyperCloud SAS/SATA hard disk drive (17.520 in.), With front bezel - 482.0
DIMMs (HCDIMM) bays. mm (18.976 in.)
– 32 GB load reduction DIMM v Weight: approximately 25 kg (55
– 200 GB and 400 GB Flash lb) to 30 kg (65 lb) depending
DIMMs upon configuration

Table 1. Server features and specifications (continued)
PCI expansion slots: Electrical input: Hot-swap fans:
v Sine-wave input (50 - 60 Hz) v One microprocessor: 3 dual-motor
PCI riser-card assembly 1 required hot-swap fans
v Type 1 v Input voltage low range:
– Slot 1: PCI Express 3.0 x8 v Two microprocessors: 4 dual-motor
– Minimum: 100 V ac
(full-height, full-length) hot-swap fans
– Maximum: 127 V ac
– Slot 2: PCI Express 3.0 x8 v Input voltage high range: Power supply:
(full-height, half-length) – Minimum: 200 V ac
– Slot 3: PCI Express 3.0 x8 – Maximum: 240 V ac v Up to two hot-swap power
(full-height, half-length) v Input kilovolt-amperes (kVA), supplies for redundancy support
v Type 2 approximately: – 550-watt ac
– Slot 1: PCI Express 3.0 x16 – Minimum: 0.14 kVA – 750-watt ac
(full-height, full-length) – Maximum: 1.201 kVA
– Slot 2: PCI Express 3.0 x8 – 900-watt ac
(full-height, half-length) Notes: – 750-watt dc
– Slot 3 (not available) 1. Power consumption and heat
Note: Power supplies in the server
v Type 3 output vary depending on the
must be with the same power rating
– Slot 1: PCI-X (full-height, number and type of optional
or wattage.
full-length) features installed and the
– Slot 2: PCI-X (full-height, power-management optional Acoustical noise emissions:
half-length) features in use. v Sound power, idling: 6.3 bels
– Slot 3: PCI Express 3.0 x16 2. The noise emission level stated is maximum
(full-height, half-length) the declared (upper limit) sound v Sound power, operating: 7.0 bels
v Type 4 power level, in bels, for a random maximum
– Slot 1 (not available) sample of machines. All
– Slot 2: PCI Express 3.0 x16 measurements are made in Heat output:
(full-height, half-length) accordance with ISO 7779 and
– Slot 3: PCI Express 3.0 x8 reported in conformance with ISO Approximate heat output:
(full-height, half-length) 9296. Actual sound-pressure levels v Minimum configuration: 419.68 Btu
in a given location might exceed per hour (AC 123 watts)
PCI riser-card assembly 2 v Maximum configuration: 4053 Btu
the average values stated because
v Type 1 per hour (AC 1188 watts)
of room reflections and other
– Slot 4: PCI Express 3.0 x8
nearby noise sources. The noise
(full-height, full-length)
emission level stated in the
declared (upper limit)
sound-power level, in bels, for a
random sample of system.
(full-height, half-length)
v Type 2
– Slot 6 (not available)
v Type 3
– Slot 4: PCI-X (full-height,
full-length)
– Slot 5: PCI-X (full-height,
full-length)
v Type 4
– Slot 4 (not available)

Table 1. Server features and specifications (continued)
Environment: Environment: Environment:
Server on: Server on: (continued) Server off:

v Temperature: 5°C to 40°C (41°F to v Maximum altitude: 3,050 m (10,000 v Temperature: 5°C to 45°C (41°F to
104°F) ft), 5°C to 28°C (41°F to 82°F) 113°F)
v Altitude: 0 to 950 m (3,117 ft); Attention: v Relative humidity: 8% to 85%
decrease the maximum system – Design to ASHRAE Class A3, v Maximum dew point: 27°C (80.6°F)
temperature by 1°C for every Temperature: 36°C - 40°C (96.8°F
175-m increase in altitude. - 104°F) with relaxed support: Storage (non-operating):
v Humidity: - Support cloud like workload v Temperature: 1°C to 60°C (33.8°F to
– Non-condensing: -12°C dew with no performance 140.0°F)
point (10.4°F) degradation acceptable v Maximum altitude: 3,050 m (10,000
– Relative humidity: 8% to 85% (Turbo-Off) ft)
v Maximum dew point: 24°C (75°F) - Under no circumstance, can v Relative humidity: 5% to 80%
any combination of worst v Maximum dew point: 29°C (84.2°F)
v Maximum rate of temperature
case workload and
change:
configuration result in system Shipment (non-operating):
– Tape drives: 5°C/hr (41°F/hr) shutdown or design exposure
v Temperature: -40°C to 60°C (-40°F
– Hard disk drives: 20°C/hr at 40°C
to 140.0°F)
(68°F/hr) - The worst case workload (like
v Maximum altitude: 10,700 m
Linpack and Turbo-On ) may
(35,105 ft)
have performance
degradation v Relative humidity: 5% to 100%
v Specific microprocessors supported v Maximum dew point: 29°C (84.2°F)
environment:
Particulate contamination: airborne
For more information, see Table 3 particulates and reactive gases acting
on page 10 alone or in combination with other
v Flash DIMM supported environmental factors such as
environment: humidity or temperature might pose
– Temperature: 5°C to 30°C (41°F a risk to the server. For information
to 86°F) about the limits for particulates and
gases, see “Particulate
– Altitude: 0 to 1000 m (3,281 ft)
contamination” on page 987.
Table 2. Power supply configurations

550-watt 750-watt 900-watt
Video adapters Not supported Not supported Quadro Not supported Quadro
600/K600/2000/ 600/K600/2000/
K2000/4000/ K2000/4000/6000
6000/
Microprocessor Support up to Support up to
115-watt 115-watt
The maximum of 16 16 8 16 16
2.5-inch HDDs
The maximum of 81 241 161 24 241
DIMMs
The maximum of 2 4 2 6 2
PCI adapters

Table 2. Power supply configurations (continued)
550-watt 750-watt 900-watt
Table notes:
1. Quad-rank RDIMM, LRDIMM and HCDIMM are not supported.
2. If you install two Quadro 4000 video adapters, you must install two power supplies (750-watt or 900-watt).
3. No limitation on CPU/HDDs/DIMMs/PCIe adapters support when you install 900-watt power supplies with no
video adapter on the order.
4. Power supplies in the server must be with the same power rating or wattage.
5. 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.
Table 3. Specific GPUs supported environment

System with one System with two
K2000/K5000/K20C/ K2000/ K5000/
System with no GPU Q2000/Q4000/Q6000 Q2000/Q4000/Q6000
Microprocessor E5-2690, E5-2609, E5-2690, E5-2609, E5-2690, E5-2609,
E5-2603, E5-2637, E5-2603, E5-2637, E5-2603, E5-2637,
E5-2637 v2, E5-2643 E5-2637 v2, E5-2643 E5-2637 v2, E5-2643
v2, E5-2667 v2 v2, E5-2667 v2 v2, E5-2667 v2
Temperature 5°C to 30°C (41°F to 5°C to 30°C (41°F to 5°C to 25°C (41°F to
85°F) 85°F) 77°F)
Altitude 0 to 304.8m (0 to 0 to 304.8m (0 to 0 to 304.8m (0 to
1,000 ft) 1,000 ft) 1,000 ft)
Note: Ambient temperature reaches up to 35°C for systems installed with GPUs that are
not listed in the table.
EU Regulation 617/2013 Technical Documentation:

International Business Machines Corporation
New Orchard Road
Armonk, New York 10504
http://www.ibm.com/customersupport/
For more information on the energy efficiency program, go to
http://www.ibm.com/systems/x/hardware/energy-star/index.html
Product Type:
Computer server
Year first manufactured:
2012
Internal/external power supply efficiency:
v http://www.plugloadsolutions.com/psu_reports/
IBM_FSA011_550W_SO-301_Report.pdf
v http://www.plugloadsolutions.com/psu_reports/IBM_7001676-
XXXX_550W_SO-458_Report.pdf
v http://www.plugloadsolutions.com/psu_reports/SO-
299_IBM_DPS-750AB-1_750W_Report.pdf
v http://www.plugloadsolutions.com/psu_reports/IBM_DPS-
750AB-14%20A_750W_SO-527_Report.pdf
v http://www.plugloadsolutions.com/psu_reports/IBM_DPS-
900CB%20A_900W_SO-440_Report.pdf
Maximum power (watts):
See Power supply.
Idle state power (watts):
511
Sleep mode power (watts):
Not applicable for servers.
Off mode power (watts):
17
Noise levels (the declared A-weighed sound power level of the
computer):
See Acoustical noise emissions.
Test voltage and frequency:
230V / 50 Hz or 60 Hz
Total harmonic distortion of the electricity supply system:
The maximum harmonic content of the input voltage waveform will be
equal or less than 2%. The qualification is compliant with EN 61000-3-2.
Information and documentation on the instrumentation set-up and circuits used
for electrical testing:
ENERGY STAR Test Method for Computer Servers; ECOVA Generalized
Test Protocol for Calculating the Energy Efficiency of Internal Ac-Dc and
Dc-Dc Power Supplies.
Measurement methodology used to determine information in this document:
ENERGY STAR Servers Version 2.0 Program Requirements; ECOVA
Generalized Test Protocol for Calculating the Energy Efficiency of Internal
Ac-Dc and Dc-Dc Power Supplies.
What your server offers

This section introduces features and technologies the server uses and provides.
v Active Energy Manager
The IBM Active Energy Manager solution is an IBM Systems Director plug-in
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 Information Center at http://pic.dhe.ibm.com/infocenter/director/
pubs/index.jsp?topic=%2Fcom.ibm.director.main.helps.doc%2Ffqm0_main.htmlor
see http://www.ibm.com/systems/management/director/downloads.html.
v Dynamic System Analysis (DSA)
The server comes with the IBM Dynamic System Analysis (DSA) Preboot
diagnostic program. DSA 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 creates a DSA log, which is a
chronologically ordered merge of the system-event log (as the IPMI event log),

the integrated management module (IMM) event log (as the ASM event log),
and the operating-system event logs. You can send the DSA log as a file to IBM
Support or view the information as a text file or HTML file.
Two editions of Dynamic System Analysis are available: DSA Portable and DSA
Preboot. For more information about both editions, see “DSA editions” on page
200.
v Features on Demand
If a Features on Demand feature is integrated in the server or in an optional
device that is installed in the server, you can purchase an activation key to
activate the feature. For information about Features on Demand, see
/http://www.ibm.com/systems/x/fod/.
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 152.
v 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. For more information, see the IBM
Systems Director Information Center at http://publib.boulder.ibm.com/
infocenter/director/v6r1x/index.jsp?topic=/director_6.1/fqm0_main.htmland
“IBM Systems Director” on page 16.
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 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 Interface (IPMI) version 2.0
– Simple Network Management Protocol (SNMP) version 3.0
– Common Information Model (CIM)
– Web browser
Some of the features that are unique to the IMM are enhanced performance,
higher-resolution remote video, expanded security options, and Feature on
Demand enablement for hardware and firmware options.
For additional information, see “Using the integrated management module” on
page 162 and the Integrated Management Module II User’s Guide at
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-
5086346.
v Integrated network support
The server comes with an integrated dual-port Intel Gigabit Ethernet controller,
which supports connection to a 10 Mbps, 100 Mbps, or 1000 Mbps network. For
more information, see “Configuring the Ethernet controller” on page 167.

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. You can enable
TPM support through the Setup utility under the System Security menu option.
v Large data-storage capacity and hot-swap capability
The hot-swap server models support a maximum of eight 2.5-inch or three
3.5-inch hot-swap Serial Attached SCSI (SAS) hard disk drives or hot-swap Serial
ATA (SATA) hard disk drives. The simple-swap server models support a
maximum of three 3.5-inch simple-swap 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 can support up to 768 GB of system memory. The server provides 24
dual inline memory module (DIMM) connectors. The server memory controller
supports error correcting code (ECC) for PC3-8500 (DDR3-1066), PC3-10600
(DDR3-1333), PC3-12800 (DDR3-1600), or PC3-14900 (DDR3-1866), DDR3
(third-generation double-data-rate), synchronous dynamic random access
memory (SDRAM) DIMMs.
v Light path diagnostics
Light path diagnostics provides LEDs to help you diagnose problems. For more
information about light path diagnostics and the LEDs, see “Light path
diagnostics” on page 184 and “Light path diagnostics LEDs” on page 187.
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 QR code information on page Chapter 1, “The System x3650 M4
server,” on page 1.
v Multi-core processing
The server supports up to two Intel Xeon™ E5-2600 series multi-core
microprocessors. The server comes with a minimum of one microprocessor.
v PCI adapter capabilities
The server has two PCI interface slots (one supports low-profile cards, and one
supports half-length, full-height cards). Slot 2 can support PCI Express or PCI-X
adapters through an optional PCI riser card. See “Replacing an adapter” on page
305 for detailed information.
v Redundant connection
The addition of the optional Ethernet adapter 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 on the server, all Ethernet traffic that is associated with the
primary connection is automatically switched to the optional redundant Ethernet
adapter connection. If the applicable device drivers are installed, this switching
occurs without data loss and without user intervention.
v Redundant cooling and optional power capabilities
The server supports a maximum of two 550-watt, 750-watt, or 900-watt hot-swap
power supplies and four dual-motor hot-swap fans, which provide redundancy

and hot-swap capability for a typical configuration. The redundant cooling by
the fans in the server enables continued operation if one of the fans fails. The
server comes with the minimum of one 550-watt, 750-watt, or 900-watt hot-swap
power supply and three fans.
You must install the fourth fan when you install the second microprocessor in
the server. You can order the second optional power supply for power
redundancy.
Note: You cannot mix different wattages of power supplies in the server.
v ServeRAID support
The ServeRAID adapter provides hardware redundant array of independent
disks (RAID) support to create configurations. The standard RAID adapter
provides RAID levels 0, 1, and 10. An optional RAID adapter is available for
purchase.
v Systems-management capabilities
The server comes with an integrated management module II (IMM2). 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
IBM System x Server Firmware (server firmware) offers several features,
including Unified Extensible Firmware Interface (UEFI) 2.1 compliance; Active
Energy Manager 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. UEFI-compliant System x
servers are capable of booting UEFI-compliant operating systems, BIOS-based
operating systems, and BIOS-based adapters as well as UEFI-compliant adapters.
Note: The server does not support DOS (Disk Operating System).
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 can be installed in USB connectors 3 and 4 on
the system board. For more information about using the embedded hypervisor,
see “Using the embedded hypervisor” on page 166.

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 7915)
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 Double-device data correction (DDDC) for x4 DRAM technology DIMMs
(available on 16 GB DIMMs only). Ensures that data is available on a single x4
DRAM DIMM after a hard failure of up to two DRAM DIMMs. One x4 DRAM
DIMM in each rank is reserved as a space device.
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 cooling fans with speed-sensing capability
v Hot-swap hard disk drives
v Information and light path diagnostics LED panels
v Integrated Management Module (IMM)
v Light path diagnostics LEDs for memory DIMMs, microprocessors, hard disk
drives, solid state 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
and PCI/PCI-X 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 and redundant hot-swap fans
v Redundant network interface card (NIC) support

v Remind button to temporarily turn off the system-error LED
v Remote system problem-determination support
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 Solid state drives
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 (IC)
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 or solid state 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 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
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 documentation on the
IBM Systems Director DVD that comes with the server, 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 website 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 34.
Front view
The following illustrations show the controls, LEDs, and connectors on the front of
your server model.
2.5-inch hard disk drive server model.
Hard disk drive USB 2 USB 1 Video Operator

activity LED (green) connector connector connector information panel
Hard disk drive
status LED (yellow)
CD/DVD drive
(optical drive)
Rack Rack
release release
latch latch
Bay 0 Hard disk Bay 7 Tape drive CD/DVD drive CD/DVD

drive bays (optional) activity LED eject button
Figure 8. 2.5-inch front view
3.5-inch hard disk drive server model.

SAS hard disk
drive bays
0 1 2 3 4 5
Figure 9. 3.5-inch hard disk drive front view
v Rack release latches: Press the latches on each front side of the server to remove
the server from the rack.
v Hard disk drive activity LEDs: This LED is used on hot-swap SAS or SATA
hard disk drives. Each hot-swap hard disk drive has an activity LED, and when
this LED is flashing, it indicates that the drive is in use.
v Hard disk drive status LEDs: This LED is used on hot-swap SAS or SATA hard
disk drives. When this LED is 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 Optional DVD eject button: Press this button to release a DVD or CD from the
optional DVD drive.
v Optional DVD drive activity LED: When this LED is lit, it indicates that the
optional 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”
on page 19.
v Operator information panel release latch: Press the blue release latch to pull out
the light path diagnostics panel and view the light path diagnostics LEDs and
buttons. See “Light path diagnostics panel” on page 20 for more information
about the 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 or keyboard to
any of these connectors.

Operator information panel
The following illustration shows the controls and LEDs on the advanced operator
information panel and the operator information panel depending on your server
model.
Figure 10. Advanced operator information panel
Figure 11. Operator information panel
v Power-control button and power-on LED: Press this button to turn the server
on and off manually. The states of the power-on LED are as follows:
Off: 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 will last
approximately 5 to 10 seconds.
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.
v Ethernet activity LEDs: When any of these LEDs is lit, they indicate 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 System-locator button/LED: Use this blue LED to visually locate the server
among other servers. A system-locator LED is also on the rear of the server. This
LED is used as a presence detection button as well. You can use IBM Systems
Director or IMM web interface to light this LED remotely. This LED is controlled
by the IMM. The locator button is pressed to visually locate the server among
the others servers.
v Check log LED: When this yellow LED is lit, it indicates that a system error has
occurred. Check the event log for additional information. See “Event logs” on
page 196 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 or on the
system board is also lit to help isolate the error. This LED is controlled by the
IMM.
Notes:
1. Depending on the type of operator information panel installed in your server,
the Reset button is on the operator information panel or the light path
diagnostics panel.
2. You do not have to pull out the operator information panel to obtain more
information if there's no release latch existed in your server model.
Light path diagnostics panel

The light path diagnostics panel is located on the top of the operator information
panel.
For additional information about the LEDs on the light path diagnostics panel, see
“Light path diagnostics LEDs” on page 187.
Note: The system service label inside the server cover also provides information
about the location of the light path diagnostics LEDs.
To access the light path diagnostics panel, press the blue release latch on the
operator information panel. Pull forward on the panel until the hinge of the
operator information panel is free of the server chassis. Then pull down on the
panel, so that you can view the light path diagnostics panel information.
Operator information
panel
Light path
diagnostics LEDs
Release latch
Figure 12. Light path diagnostics panel exposure
The following illustration shows the LEDs and controls on the light path
diagnostics panel.

Figure 13. Light path diagnostics panel
v Remind button: This button places the system-error LED on the operator
information 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.
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. The Reset button is in the lower-right corner of the light path
diagnostics panel.
Rear view
The following illustration shows the connectors on the rear of the server.
Ethernet1 10G ethernet

(shared system (with optional
management ethernet) Ethernet2 Ethernet3 Ethernet4 10G ethernet card) Power supply 2
System-management Video Serial USB3 USB4 USB5 USB6 NMI Power supply 1
(ethernet)(dedicated) button
v NMI button: Press this button to force a nonmaskable interrupt to the

microprocessor. It allows you to blue screen the server and take a memory
dump (use this button only when directed by the IBM service support). You
might have to use a pen or the end of a straightened paper clip to press the
button. The NMI button is in the lower left-hand corner on the rear of the
server.
v Power connector: Connect the power cord to this connector.

Note: Power supply 1 is the default/primary power supply. If power supply 1
fails, you must replace it immediately.
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 module II (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, such as a USB mouse or keyboard to
any of these connectors.
v Systems-management Ethernet connector: Use this connector to connect the
server to a network for full systems-management information control. This
connector is used only by the integrated management module (IMM2). A
dedicated management network 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. See Using the Setup utility in the
Problem Determination and Service Guide for more information.
v Ethernet connectors: Use either of these connectors to connect the server to a
network. When you enable shared Ethernet for IMM2 in the Setup utility, you
can access the IMM2 using either the Ethernet 1 or the system-management
Ethernet (default) connector. See Using the Setup utility for more information.
The following illustration shows the LEDs on the rear of the server.
Ethernet Ethernet
link LED activity LED AC power
LED (green)
DC power
LED (green)
Power-supply
error LED (yellow)
Power-on System-error
LED (green) LED (yellow)
Locator LED (blue)
The following illustration shows the LEDs on a dc power supply.

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 AC power LED: Each hot-swap ac power supply has an ac power LED. When
the ac power LED is lit, it indicates that sufficient power is coming into the
power supply through the power cord. During typical operation, the ac power
LED is lit. For any other combination of LEDs, see “AC power-supply LEDs” on
page 192.
v DC power LED: Each hot-swap ac power supply has a dc power LED. When
the dc power LED is lit, it indicates that the power supply is supplying adequate
dc power to the system. During typical operation, both the ac and dc power
LEDs are lit. For any other combination of LEDs, see “AC power-supply LEDs”
on page 192.
v IN OK power LED: Each hot-swap dc power supply has an IN OK power LED.
When the IN OK power LED is lit, it indicates that sufficient power is coming
into the power supply through the power cord. During typical operation, both
the IN OK and OUT OK power LEDs are lit. For any other combination of
LEDs, see “DC power-supply LEDs” on page 193.
v OUT OK power LED: Each hot-swap dc power supply has an OUT OK power
LED. When the OUT OK power LED is lit, it indicates that the power supply is
supplying adequate dc power to the system. During typical operation, both the
IN OK and OUT OK power LEDs are lit. For any other combination of LEDs,
see “DC power-supply LEDs” on page 193.
v Power-supply error LED: When the power-supply error LED is lit, it indicates
that the power supply has failed.
Note: Power supply 1 is the default/primary power supply. If power supply 1

fails, you must replace the power supply immediately.
v Power-on LED: When this LED is lit and not flashing, it indicates that the server
is turned on. The states of the power-on LED are as follows:
Off: 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 will last
approximately 5 to 10 seconds.
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.
v System-locator LED: Use this LED to visually locate the server among other
servers. You can use IBM Systems Director or IMM2 web interface to light this
LED remotely.
v System-error LED: When this LED is lit, it indicates that a system error has
occurred. An LED on the light path diagnostics panel is also lit to help isolate
the error.

Server power features
When the server is connected to an ac power source but is not turned on, the
operating system does not run, and all core logic except for the integrated
management module II (IMM2) is shut down.
However, the server can respond to requests from IMM2, such as a remote request
to turn on the server. The power-on LED flashes to indicate that the server is
connected to an ac power source 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 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 5 to 10 seconds after
the server is connected to 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.
Notes:
1. 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.
2. Ethernet 1 connector supports Wake on LAN feature.
3. When you turn on the server with the graphical adapters installed, the IBM
logo displays on the screen after approximately 3 minutes. This is normal
operation while the system loads.
Turning off the server

Use this information to turn off the server.
When you turn off the server and leave it connected to 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 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
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 server can be turned off by Wake on LAN feature with the following
limitation:
Note: When you install any PCI adapter, the power cords must be disconnected
from the power source before you remove the PCI Express riser-card assembly
and the PCI-X riser-card assembly. Otherwise, the Wake on LAN feature might
not work.
v The Integrated Management Module II (IMM2) can turn off the server as an
automatic response to a critical system failure.

Chapter 2. Installing optional devices
This section 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 28.
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, see “Updating the firmware” on page
149. For a list of supported optional devices for the server, see
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/.
2. 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
3. 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 201 for information
about how to run diagnostics.
4. Follow the installation procedures in this chapter and use the correct tools.
Incorrectly installed devices can cause system failure because of damaged pins
in sockets or connectors, loose cabling, or loose components.

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 199.
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.”
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/.
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

Server components
The following illustration shows the major components in the server.
The illustrations in this document might differ slightly from your hardware.
cover
Remote battery
PCI riser-card
assembly
Air baffle
Heat sink
Fans
Microprocessor
Heat sink
retention module
DIMM
Fan bracket
System board
Battery holder
Power supply
filler panel
Battery tray
SAS hard disk

drive backplane
Power supply
Tape drive
DVD drive ( optional )
panel
4-drive
filler panel
Front bezel
Tape drive
filler panel
Figure 14. 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.
Chapter 2. Installing optional devices 29

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.
System-board internal connectors

The following illustration shows the internal connectors on the system board.
PCI riser 10G Ethernet PCI riser

NMI button connector 2 connector Battery connector 1
SAS 1
Video card power
connector 1 SAS 0
USB hypervisor RAID upgrade

connector connector
Power signal Optical disk drive

connector connector
(2nd power supply
to system board)
Power supply
connector
panel connector
(2nd power supply
to system board)
Microprocessor 2 USB tape drive

connector
DIMM connectors
Microprocessor 1
SAS/SATA backplane
config connector 1 Front video
connector
Fan 4 connector
SAS/SATA backplane
power connector
Video card power Fan 3 Fan 2 Tape drive SAS/SATA Front USB Fan 1
connector 2 connector connector power backplane connector connector
connector config
connector 2
Figure 15. System-board internal connectors

System-board external connectors
The following illustration shows the external connectors on the system board.
Ethernet 4
connector
Ethernet 3
connector
Ethernet 2
System connector
USB 3 - 6 Serial Video management Ethernet 1 connector/
connectors connector connector (dedicated) System management (shared)
Figure 16. System-board external connectors

System-board switches, jumpers, and buttons
The following illustration shows the location of the switches, jumpers, and buttons
on the server.
Note: If there is a clear protective sticker on the top of the switch blocks, you must
remove and discard it to access the switches.
UEFI boot backup

jumper(JP2)
CMOS clear
jumper (JP1)
System TPM physical

presence jumper(JP20)
Figure 17. System-board switches, jumpers, and buttons
The following table describes the jumpers on the system board.

Table 4. System board jumpers
Jumper number Jumper name Jumper setting
JP1 CMOS clear jumper v Pins 1 and 2: Normal (default).
v Pins 2 and 3: Clears the real-time
clock (RTC) registry.
JP2 UEFI boot backup 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.
JP20 System TPM physical v Pins 1 and 2: Normal (default).
presence jumper
v Pins 2 and 3: Indicates a physical
presence to the system TPM.
Notes:
1. If no jumper is present, the server responds as if the pins are set to the default.
2. Changing the position of the UEFI boot backup jumper (JP2) 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.

The following table describes the functions of the SW3 switch block on the system
board.
Table 5. System board SW3 switch block definition
Switch
number Default position Description
1 Off Reserved.
2 Off Reserved.
3 Off Reserved.
4 Off Power-on password override. Changing the
position of this switch bypasses the power-on
password check the next time the server is turned
on and starts the Setup utility so that you can
change or delete the power-on password. You do
not have to move the switch back to the default
position after the power-on password in
overridden.
Changing the position of this switch does not affect

the administrator password check if an
administrator password is set.
See “Passwords” on page 159 for additional

information about passwords.
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 36,
“Handling static-sensitive devices” on page 39, and “Turning off the server” on
page 24.
2. Any system-board switch or jumper block that is not shown in the illustrations
in this document are reserved.
The following table describes the functions of the button on the system board.
Table 6. Button on the server
Button name Function
Force NMI button This button is on the rear of the server. Press
this button to force a nonmaskable interrupt
to the microprocessor. You might have to use
a pen or the end of a straightened paper clip
to press the button. You can also use it to
force a blue-screen memory dump (use this
button only when you are directed to do so
by IBM Support).

System-board LEDs
The following illustration shows the light-emitting diodes (LEDs) on the system
board.
System Error
LED Locator LED Power LED
Enclosure management
heartbeat LED
Imm2 heartbeat
LED
Standby power
LED
10G Ethernet card

error LED
Battery
error LED
DIMM 19-24
error LED DIMM 1-6
(under the latches) error LED
(under the latches)
Microprocessor 2 Microprocessor 1
error LED error LED
Fan 4 Fan3 DIMM 7-18 Fan2 System board Fan1

error LED error LED error LED error LED error LED error LED
(under the latches)
Figure 18. System-board LEDs
System-board optional-device connectors

The following illustration shows the connectors on the system board for the
optional devices.

Optional
10G Ethernet
card connector Optional PCI
riser connector 1
Optional PCI
riser connector 2
Optical drive
connector
USB tape
connector
Microprocessor 2 Microprocessor 1
DIMM 19-24 DIMM 1-6
Fan 4 DIMM 7-18

connector
Figure 19. System-board optional-device connectors
PCI riser-card adapter connectors

The following illustration shows the connectors on the PCI riser card for
user-installable PCI adapters.
PCI PCI
riser-card riser-card
assembly assembly
(in short position) (in long position)
Adapter Adapter
connectors connectors
Adapter Adapter
Full-length
adapter
bracket Full-length
adapter
bracket
Figure 20. PCI riser-card adapter connectors

PCI riser-card assembly LEDs
The following illustration shows the light-emitting diodes (LEDs) on the PCI
riser-card assembly.
Note: Error LEDs remain lit only while the server is connected to power.
UpperPCI slot error LED
Center PCI slot error LED
Lower PCI slot error LED
Figure 21. PCI riser-card assembly LEDs
Installation guidelines
Use the installation guidelines to install the System x3650 M4 Type 7915.
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
device.
Before you install optional devices, read the following information:

v Read the safety information in “Safety” on page vii, the guidelines in “Working
inside the server with the power on” on page 38, and “Handling static-sensitive
devices” on page 39. This information will help you work safely.
v Make sure that the devices that you are installing are supported. For a list of
supported optional devices for the server, see 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://publib.boulder.ibm.com/infocenter/toolsctr/v1r0/.

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 201 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, a small Phillips screwdriver, and a T8 torx
screwdriver available.
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 Each of the power-supply bays has a power supply or a filler 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.
Operating the server for extended periods of time (more than 30 minutes) with
the server cover removed might damage server components.
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 fan within 30 seconds of removal.
v You have replaced a hot-swap drive within 2 minutes of removal.
v You have replaced a failed hot-swap power supply within 2 minutes of removal.
v You do not operate the server without the air baffle installed. Operating the
server without the air baffle might cause the microprocessor to overheat.
v Microprocessor socket 2 always contains either a socket cover or a
microprocessor and heat sink.
v You have installed the fourth fan when you installed the second microprocessor
option.
Working inside the server with the power on

Guidelines to work inside the server with the power on.
Attention: Static electricity that is released to internal server components when

the server is powered-on might cause the server 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 you work inside the server with the
power on.
You might have to have the server turned on while the cover is off, to look at light
path diagnostics LEDs or replace hot swap components. Follow these guidelines
when you work inside a server that is turned on:
v Avoid wearing loose-fitting clothing on your forearms. Button long-sleeved
shirts before working inside the server; do not wear cuff links while you are
working inside the server.
v Do not allow your necktie or scarf to hang inside the server.
v Remove jewelry, such as bracelets, necklaces, rings, and loose-fitting wrist
watches.
v Remove items from your shirt pocket, such as pens and pencils, that could fall
into the server as you lean over it.
v Avoid dropping any metallic objects, such as paper clips, hairpins, and screws,
into the server.

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 The use of a grounding system is recommended. For example, wear an
electrostatic-discharge wrist strap, if one is available. Always use an
electrostatic-discharge wrist strap or other grounding system when working
inside the server with the power on.
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 cover

Use this information to remove the cover.
About this task
To remove the server cover, complete the following steps:
Procedure
1. Read the safety information that begins on page “Safety” on page vii and
“Installation guidelines” on page 36.
2. Turn off the server and peripheral devices and disconnect the power cords and
all external cables, if necessary.
3. If the server has been installed in a rack, slide the server out from the rack
enclosure.

3
Cover-release
latch
Figure 22. Cover removal
4. Pull up firmly on the blue latch on the top (in the center of the front of the
server) of the cover and slide the cover toward the rear of the server until the
cover has disengaged from the chassis.
5. Lift the server cover off the server and set it aside.
Attention: For proper cooling and airflow, replace the server cover before you
turn on the server.
Results
Removing a PCI riser-card assembly

Use this information to remove a PIC riser-card assembly.
About this task
The server comes with one riser-card assembly (with option to add one more) that
each contains two to three PCI slots. See http://www.ibm.com/systems/info/
x86servers/serverproven/compat/us/ for a list of riser-card assemblies that you
can use with the server.
To remove a PCI riser-card assembly, complete the following steps:

PCI riser-card
assembly 2
PCI riser-card
assembly 1
Figure 23. Removing PCI riser-card assembly
Procedure
2. Turn off the server and peripheral devices, and disconnect the power cord and
all external cables.
3. Remove the cover (see “Removing the cover” on page 39).
4. Grasp the assembly at the front tab and rear edge and lift it to remove it from
the server. Place the riser-card assembly on a flat, static-protective surface.

Removing the air baffle
When you work with some optional devices, you must first remove the air baffle
to access certain components or connectors on the system board. The following
illustration shows how to remove the air baffle.
About this task
PCI riser-card
assembly 2
PCI riser-card
assembly 1
Air baffle
Figure 24. Air baffle removal
To remove the air baffle, complete the following steps:
Procedure
all external cables (see “Turning off the server” on page 24).
4. Remove PCI riser-card assemblies, if needed (see “Removing a PCI riser-card
assembly” on page 40).
5. Place your fingers under the front and back of the top of the air baffle; then, lift
the air baffle out of the server.

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.
Stretching a PCI riser-card assembly

Use this information to stretch a PCI riser-card assembly.
About this task
Note: It is not necessary to capture adaptor card with the full-length adaptor
bracket when installing half length adaptor cards.
If you are installing a full-length adapter in the upper riser-card PCI slot, you must
first stretch the PCI riser-card assembly.
Figure 25. Stretching a PCI riser-card assembly
To stretch the riser-card assembly, complete the following steps:
Procedure
1. Orient the riser-card assembly as shown.
2. Rotate the thumb screw 1, which is close by the PCI slot end, counterclockwise
and lengthen the PCI riser-card assembly 2.
3. Fasten the thumbscrew.
4. Return to the adapter-installation instructions.

Shrinking a PCI riser-card assembly
Use this information to shrink a PCI riser-card assembly.
About this task
If you are removing a full-length adapter in the upper riser-card PCI slot and will
replace it with a shorter adapter or no adapter, you must shrink the full-length PCI
Figure 26. Shrinking a PCI riser-card assembly
To shrink the full-length PCI riser-card assembly, complete the following steps:
Procedure
1. Rotate the thumb screw 1, which is far from the PCI slot end, counterclockwise
and shorten the PCI riser-card assembly 2.
2. Fasten the thumbscrew.
3. Return to “Installing an adapter” on page 64 or “Installing a PCI riser-card
assembly” on page 144, as applicable.
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.
For a list of supported hard disk drives, see http://www.ibm.com/systems/info/

x86servers/serverproven/compat/us/.
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 Check the instructions that come with the drive to determine whether you have
to set any switches or jumpers on the drive. If you are installing a SAS or SATA
hard disk drive, be sure to set the SAS or SATA ID for that device.
v The hot-swap server models support up to sixteen 2.5-inch or six 3.5-inch
hot-swap SAS or SATA hard disk drives.
v The simple-swap server models support up to thirty-two 1.8-inch solid-state
drives or six 3.5-inch simple-swap SATA hard disk drives.

v The electromagnetic interference (EMI) integrity and cooling of the server are
protected by having all bays and PCI and PCI Express slots covered or occupied.
When you install a drive, PCI, or PCI Express adapter, save the EMC shield and
filler panel from the bay or PCI adapter or PCI Express adapter slot cover in the
event that you later remove the device.
v For a complete list of supported optional devices for the server, see
Drive IDs
The drive ID that is assigned to each drive is printed on the front of the server.
The ID numbers and the drive bay numbers are the same.
Installing a hot-swap hard disk drive

Use this information to install a hot-swap hard disk drive.
About this task

v Before you install an additional hot-swap hard disk drive, go to Table 2 on page
9 for detailed power supply configurations.
To install a hot-swap SAS or SATA hard disk drive, complete the following steps:
Note: If you have only one hard disk drive, you must install it in the bay 0
(upper-left).
Procedure
1. Read the safety information that begins on “Safety” on page vii and
2. Remove the filler panel from the empty drive bay. Keep the filler panel in a
safe place.
3. 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.
4. Install the hard disk drive in the drive bay:
a. Make sure that the tray handle is in the open (unlocked) position.
b. Align the drive with the guide rails in the bay.
Latch
Handle
Filler panel handle
Figure 27. 2.5-inch hot-swap hard disk drives installation

3.5-inch hot-swap
hard disk drive
Latch
Handle Filler panel
c. Gently push the drive into the bay until the drive stops.
d. Rotate the tray handle to the closed (locked) position.
e. Check the hard disk drive status LED to verify that the hard disk drive is
operating correctly. If the yellow hard disk drive status LED of a drive is lit
continuously, that drive is faulty and must be replaced. If the green hard
disk 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
hard disk drives. See the ServeRAID adapter documentation for additional
information about RAID operation and complete instructions for using the
ServeRAID adapter.
If you have other devices to install or remove, do so now. Otherwise, go to
“Completing the installation” on page 142.
Installing a simple-swap hard disk drive

Use this information to install a simple-swap hard disk drive.
About this task
You must turn off the server before installing simple-swap drives in the server.
Before you install a simple-swap SATA hard disk drive, read the following
information. For a list of supported hard disk drives, see http://www.ibm.com/
v Locate the documentation that comes with the hard disk drive and follow those
to set any switches or jumpers on the drive. If you are installing a SATA device,
be sure to set the SATA ID for that device.
v You can install up to six 3.5-inch simple-swap SATA hard disk drives in the
server. Do not install hot-swap drives into a simple-swap server model, it is not
supported.
v The simple-swap server models are available only in non-RAID configurations.

filler panel from the bay or PCI or PCI Express adapter slot cover in the event
that you later remove the device.
v Before you install an additional simple-swap hard disk drive, go to Table 2 on
page 9 for detailed power supply configurations.
To install a simple-swap hard disk drive, complete the following steps:
Procedure
3. Remove the filler panel from the empty drive bay.
a. Grasp the black drive handle and slide the blue release latch to the right
and align the drive assembly with the guide rails in the bay.
b. Gently push the drive into the bay until the drive stops.
2.5-inch
simple-swap
hard disk drive
Release latch
Filler panel
Figure 29. 2.5-inch simple-swap hard disk drive installation
3.5 inch simple-swap

hard disk drive
Filler panel
6. Reinstall the drive bay filler panel that you removed earlier.
7. If you are installing additional simple-swap hard disk drives, do so now.

Installing a 1.8-inch hot-swap solid state drive
Use this information to install a 1.8-inch hot-swap solid state drive.
About this task
To install a 1.8-inch hot-swap solid state drive, complete the following steps:
Procedure
2. Remove the filler panel. Keep the filler panel in a safe place.
a. Make sure that the handle is in the open (unlocked) position.
1.8-inch
hot-swap
hard disk drive
Filler
Figure 31. 1.8-inch hot-swap solid state drives installation
d. Rotate the handle to the closed (locked) position.
e. Check the solid state drive status LED to verify that the solid state drive is
operating correctly. If the yellow solid state drive status LED of a drive is lit
continuously, that drive is faulty and must be replaced. If the green solid
state drive activity LED is flashing, the drive is being accessed.

solid disk drives. See the ServeRAID adapter documentation for additional
ServeRAID adapter.

Results

“Completing the installation” on page 142
Installing an optional DVD drive

Use this information to install an optional DVD drive.
About this task
To install an optional DVD drive, complete the following steps:
Procedure
2. Turn off the server and peripheral devices and disconnect the power cords
and all external cables.
Note: When you disconnect the power source from the server, you lose the
ability to view the LEDs because the LEDs are not lit when the power source
is removed. Before you disconnect the power source, make a note of which
LEDs are lit, including the LEDs that are lit on the operation information
panel, on the light path diagnostics panel, and LEDs inside the server on the
system board.
4. Remove the DVD drive filler panel if it is installed. Locate the blue release tab
on the rear of the DVD drive filler panel; then, while you press the tab, push
the DVD drive filler panel out of the drive bay.
Release tab
Figure 32. DVD drive filler panel removal
5. Remove the retention clip from the side of the DVD drive filler panel. Save
the DVD drive filler panel for future use.
Note: If you are installing an optical drive that contains a laser, observe the
following safety precautions.
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.
Class 1 Laser Product

Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
Appareil A` Laser de Classe 1
6. 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.
7. Follow the instructions that come with the DVD drive to set any jumpers or
switches.
8. Attach the drive retention clip that you removed from the DVD drive filler
panel to the side of the new DVD drive.
Drive retention clip
Alignment pins
Figure 33. DVD drive retention clip installation
9. Align the DVD drive in the drive bay and slide the DVD drive into the optical
drive bay until the DVD drive clicks into place.

Drive retainer
clip
Figure 34. DVD drive installation
10. Connect the DVD drive cable (see “Replacing the DVD drive cable” on page
283). The following illustration shows the cable routing for the DVD drive:
Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch
Figure 35. DVD drive cable routing

Results

Installing an optional DVD drive cable

Use this information to install an optional DVD drive cable.
About this task
To install the DVD drive cable, complete the following steps:
Procedure
4. Remove the air baffle (see “Removing the air baffle” on page 42).
5. Align the cable connector with the connector on the rear of the DVD drive
cage. Press the cable connector into the optical drive cage connector and slide it
to the left until it is firmly seated.
Cable
connector
latch
Figure 36. DVD drive cable latch
The following illustration shows cable routing for the DVD cable:
Attention: Follow the optical drive cable routing as the illustration shows.
Make sure that the cable is not pinched and does not cover any connectors or
obstruct any components on the system board.

Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch
Results


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 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.
v The server supports only industry-standard double-data-rate 3 (DDR3), 800,
1066, 1333, 1600, or 1866 MHz, PC3-6400, PC3-8500, PC3-10600, PC3-12800, or
PC3-14900 registered or unbuffered, synchronous dynamic random-access
memory (SDRAM) dual inline memory modules (DIMMs) with error correcting
code (ECC). See http://www.ibm.com/systems/info/x86servers/serverproven/
compat/us/ for a list of supported memory modules for the server.
– 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
- xff is the device organization (bit width)
x4 = x4 organization (4 DQ lines per SDRAM)
x8 = x8 organization
- v is the SDRAM and support component supply voltage (VDD)
v Blank = 1.5 V specified
v L = 1.35 V specified, 1.5 V operable
Note: Values for these voltages are ‘specified’ which means the device
characteristics such as timing are supported at this voltage. Values are
‘operable’ which means that the devices can be operated safely at this
voltage. However, device characteristics such as timing may not be
guaranteed. All devices must be ‘tolerant’ of the highest DDR3 nominal
voltage of 1.5 V, meaning that they may not operate at 1.5 V but may be
powered at that voltage without damage to the devices.
- wwwww is the DIMM bandwidth, in MBps
6400 = 6.40 GBps (DDR3-800 SDRAMs, 8-byte primary data bus)
- m is the DIMM type
E = Unbuffered DIMM (UDIMM) with ECC (x72-bit module data bus)
L = Load Reduction DIMM (LRDIMM)
R = Registered DIMM (RDIMM)
U = Unbuffered DIMM with no ECC (x64-bit primary data bus)
- aa is the 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
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 PC3v-xxxxxx-xx-xx-xxx.
The numeral in the sixth numerical position indicates whether the DIMM is
single-rank (n=1), dual-rank (n=2), or quad-rank (n=4).
v The following rules apply to DDR3 RDIMM speed as it relates to the number of
RDIMMs in a channel:
– When you install 1 RDIMM per channel, the memory runs at 1866 MHz
– When you install 2 RDIMMs per channel, the memory runs at 1600 MHz
– All channels in a server run at the fastest common frequency
– Do not install registered, unbuffered, and load reduction DIMMs in the same
server
v The maximum memory speed is determined by the combination of the
microprocessor, DIMM speed, DIMM type, Operating Modes in UEFI settings,
and the number of DIMMs installed in each channel.
v In two-DIMM-per-channel configuration, a server with an Intel Xeon™ E5-2600
series microprocessor automatically operates with a maximum memory speed of
up to 1600 MHz when the following condition is met:
– Two 1.35 V single-rank, dual-ranl, or quad-rank UDIMMs, RDIMMs or
LRDIMMs are installed in the same channel. In the Setup utility, Memory
speed is set to Max performance and LV-DIMM power is set to Enhance
performance mode. The 1.35 V UDIMMs, RDIMMs or LRDIMMs will
function at 1.5 V.
v The server supports a maximum of 16 dual-rank UDIMMs. The server supports
up to two UDIMMs per channel.
v The server supports a maximum of 24 single-rank, dual-rank, or 16 quad-rank
RDIMMs. The server does not support three quad-rank RDIMMs in the same
channel.
v The following table shows an example of the maximum amount of memory that
you can install using ranked DIMMs:
Table 7. Maximum memory installation using ranked DIMMs
Number of
DIMMs DIMM type DIMM size Total memory
16 Dual-rank UDIMMs 4 GB 64 GB
24 Single-rank RDIMMs 2 GB 48 GB
24 Dual-rank RDIMMs 8 GB 192 GB
24 HCDIMMs 16 GB 384 GB
16 Quad-rank RDIMMs 8 GB 128 GB
24 Quad-rank LRDIMMs 32 GB 768 GB

v The UDIMM option that is available for the server is 4 GB. The server supports
a minimum of 4 GB and a maximum of 64 GB of system memory using
UDIMMs.
v The RDIMM options that are available for the server are 2 GB, 4 GB, 8 GB, and
16 GB. The server supports a minimum of 2 GB and a maximum of 384 GB of
system memory using RDIMMs.
v The HCDIMM options that are available for the server are 16 GB and 32 GB. The
server supports a minimum of 16 GB and a maximum of 768 GB of system
memory using HCDIMMs.
Note: Do not mix the 16 GB HCDIMM and the 32 GB HCDIMM in the server.
v The LRDIMM option that is available for the server is 32 GB. The server
supports a minimum of 32 GB and a maximum of 768 GB of system memory
using LRDIMMs.
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 150.
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. However, to improve system performance, install a
minimum of four DIMMs for each microprocessor.
v DIMMs in the server must be the same type (RDIMM, UDIMM, HCDIMM, or
LRDIMM) to ensure that the server will operate correctly.
v When you install one quad-rank DIMM in a channel, install it in the DIMM
connector furthest away from the microprocessor.
v When you install Flash DIMMs, follow the following rules strictly:
– Flash DIMM thermal specification supports the maximum temperature up to
70°C (158°F).
Note: The system may indicates specific error messages when the
temperature does not meet 70°C (158°F), these error messages do not impact
the system operation.
– Flash DIMM configuration supports RHEL 6.4 and RHEL 6.5.
– Flash DIMM configuration is only available to mix with one type of 16GB
RDIMM, with quantities of 8 or 16 DIMMs.
– Flash DIMM configuration does not support the fan redundancy function
when the ambient temperature is over 30°C (86°F). Please refer to the retain
tip H212833 at http://www.ibm.com/supportportal/for the detailed
information.
Table 8. Supported RDIMM
DIMM description Option part number FRU part number
16 GB dual-rank 1.5 V, 00D5048 46W0670
DDR3, 1866MHz, PC3-14900
CL 13 ECC LP RDIMM
– SSD Flash DIMM is always installed with a RDIMM in the same channel.
– SSD Flash DIMMs can not be mixed with LRDIMMs and UDIMMs.

– The Flash DIMM options that are available for the server are 200 GB and 400
GB, with quantities of 4 or 8 DIMMs.
Note: Do not mix 200 GB Flash DIMM and 400 GB Flash DIMM in the server.
– Flash DIMM configuration supports the following microprocessors.
Table 9. Supported microprocessors
Microprocessor description Option part number FRU part number
Intel Xeon Processor E5-2643 46W4371 00Y2790
v2, 3.5 GHz, 25 MB, 1866
MHz, 130 W (6-core)
v2, 3.3 GHz, 25 MB, 1866
MHz, 130 W (8-core)
v2, 3.0 GHz, 25 MB, 1866
MHz, 130 W (10-core)
v2, 2.7 GHz, 30 MB, 1866
v Flash DIMM configuration supports one mezz adapter.

Table 10. Supported adapter
Adpater description Option part number FRU part number
Intel x520 dual port 10GbE 49Y7980 49Y7982
SFP+ embedded adapter
v For detailed Flash DIMM installation sequence, go to Flash DIMM installation

sequence .
Notes:
1. You can install DIMMs for microprocessor 2 as soon as you install
microprocessor 2; you do not have to wait until all of the DIMM slots for
microprocessor 1 are filled.
2. DIMM slots 13-24 are reserved for microprocessor 2; thus, DIMM slots 13-24 are
enabled when microprocessor 2 is installed.
The following illustration shows the location of the DIMM connectors on the
system board.

Figure 38. DIMM connectors location
DIMM installation sequence

Depending on the server model, the server may come with a minimum of one 2
GB or 4 GB DIMM installed in slot 1. When you install additional DIMMs, install
them in the order shown in the following table to optimize system performance.
Normal mode DIMM installation sequence
In general, all four channels on the memory interface for each microprocessor can
be populated in any order and have no matching requirements.
Table 11. Normal mode DIMM installation sequence
Number of installed
microprocessor DIMM connector population sequence
One microprocessor 1, 4, 9, 12, 2, 5, 8, 11, 3, 6, 7, 10
installed
Two microprocessors 1, 13, 4, 16, 9, 21, 12, 24, 2, 14, 5, 17, 8, 20, 11, 23, 3, 15, 6, 18,
installed 7, 19, 10, 22
For optimal performance:
Make sure all four memory channels of each microprocessor are populated. Each
memory channels should be populated with the same type and amount of memory
per channel. Each microprocessor socket should be populated with the same type
and amount of memory per socket. 1DPC (one DIMM per channel) or 2DPC (two
DIMM per channel) memory configuration are recommended. Unless there is a
need for memory capacity over memory frequency, 3DPC (three DIMMs per
channel) configuration is not recommended since 3DPC configuration forces the
memory subsystem to run at a lower frequency (1066MHz).
Flash DIMM installation sequence

1. When you install 2 DIMMs per channel as the following installation sequence,
the memory runs at 1600 MHz.

Table 12. Flash DIMM installation sequence
DIMM type DIMM connector population sequence
Flash DIMM 5, 8, 17, 20
RDIMM 1, 4, 9, 12. 13, 16, 21, 24
2. When you install 2 DIMMs (1 Flash DIMM and 1 RDIMM) per channel as the
following installation sequence, the memory runs at 1333 MHz.
Flash DIMM 2, 5, 8, 11. 14, 17, 20, 23
RDIMM 1, 4, 9, 12. 13, 16, 21, 24
3. When you install 3 DIMMs (1 Flash DIMM and 2 RDIMMs) per channel as the
Flash DIMM 3, 6, 7, 10. 15, 18, 19, 22
RDIMM 1, 2, 4, 5, 8, 9, 11, 12, 13, 14, 16, 17, 20, 21, 23, 24
Please refer to the Understanding and Optimizing Memory Performance for Intel
Xeon Processor E5-2600 Series in IBM Flex System, System x, and BladeCenter
Platforms white paper for the detail.
Memory mirrored channel

Memory mirrored channel mode replicates and stores data on two pairs of DIMMs
within two channels simultaneously.
If a failure occurs, the memory controller switches from the primary pair of
memory DIMMs to the backup pair of DIMMs. To enable memory mirrored
channel through the Setup utility, select System Settings > Memory. For more
information, see “Using the Setup utility” on page 154. When you use the memory
mirrored channel feature, consider the following information:
v When you use memory mirrored channel, you must install a pair of DIMMs at a
time. The two DIMMs in each pair must be identical in size, type, and rank
(single, dual, or quad), and organization, but not in speed. The channels run at
the speed of the slowest DIMM in any of the channels.
v The maximum available memory is reduced to half of the installed memory
when memory mirrored channel is enabled. For example, if you install 64 GB of
memory using RDIMMs, only 32 GB of addressable memory is available when
you use memory mirrored channel.
v For UDIMMs, DIMM connectors 3, 6, 7, and 10 for microprocessor 1 and DIMM
connectors 15, 18, 19, and 22 for microprocessor 2 are not used in memory
mirrored channel mode.
The following diagram lists the DIMM connectors on each memory channel.

Figure 39. Connectors on each memory channel
The following table shows the installation sequence for memory mirrored channel
mode:
Table 15. Memory mirrored channel mode DIMM population sequence
Number of installed
Number of DIMMs microprocessor DIMM connector
First pair of DIMMs 1 1, 4
Second pair of DIMMs 1 9, 12
Third pair of DIMMs 1 2, 5
Fourth pair of DIMMs 1 8, 11
Fifth pair of DIMMs 1 3, 6
Sixth pair of DIMMs 1 7, 10
Seventh pair of DIMMs 2 13, 16
Eighth pair of DIMMs 2 21, 24
Ninth pair of DIMMs 2 14, 17
Tenth pair of DIMMs 2 20, 23
Eleventh pair of DIMMs 2 15, 18
Twelfth pair of DIMMs 2 19, 22
Note: DIMM connectors 3, 6, 7, 10, 15, 18, 19, and 22 are not used in memory mirrored
channel mode when UDIMMs are installed in the server.
Memory rank sparing

The memory rank sparing feature disables the failed memory from the system
configuration and activates a rank sparing DIMM to replace the failed active
DIMM.
You can enable rank sparing memory in the Setup utility, select System Settings >
Memory. For more information, see “Using the Setup utility” on page 154. When
you use the memory rank sparing feature, consider the following information:
v The memory rank sparing feature is supported on server models with an Intel
Xeon™ E5-2600 series microprocessor.
v The maximum available memory is reduced when memory rank sparing mode
is enabled.

Follow the installation sequence for rank sparing mode:

v Install at least one quad-rank DIMM in a channel.
v Install at least two single-rank or dual-rank DIMMs in a channel.
Table 16. Memory rank sparing mode DIMM population sequence
Number of installed
Note: DIMM connectors 3, 6, 7, 10, 15, 18, 19, and 22 are not used in memory rank sparing
mode when UDIMMs are installed in the server.

Use this information to install a memory module.
About this task

v Before you install an additional memory module, go to Table 2 on page 9 for
detailed power supply configurations.
Procedure
and all external cables, if necessary.
4. If PCI riser-card assembly 1 contains one or more adapters, remove riser-card
assembly 1 (see “Removing a PCI riser-card assembly” on page 40).

PCI riser-card
assembly 2
PCI riser-card
assembly 1
Air baffle
6. Carefully open the retaining clips on each end of the DIMM connector and
remove the DIMM.
Attention: To avoid breaking the retaining clips or damaging the DIMM
connectors, open and close the clips gently.

Figure 42. DIMM removal
7. 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.
8. Turn the DIMM so that the alignment slot align correctly with the alignment
tab.
9. 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 34 for the locations of the DIMM
connectors).
10. 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. Install the air baffle (see “Replacing the air baffle” on page 262).
12. Install PCI riser-card assembly 2, if you removed it (see “Installing a PCI
riser-card assembly” on page 144).
Results


Installing an adapter
The following illustration shows the PCI adapter expansion slots from the rear of
the server.
About this task

Table 17. The maximal card dimension supported in each slot (rear view)
PCI riser-card assembly 1 PCI riser-card assembly 2
1 Full height, up to full length 4 Full height, up to full length
2 Full height, half length 5 Full height, up to full length
3 Full height, half length 6 Full height, half length
Note: If you are installing a ServeRAID-M5110 with x3650 M4 Plus 8 2.5-inch HS

HDD Assembly Option Kit, it can only be installed in PCI slot 2; if you are
installing a ServeRAID-M5120 or an IBM LLM-SM dual port 10GbE SFP+ adapter,
it can only be installed in PCI slot 1, 2, 4, or 5.
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 Locate the documentation that comes with the adapter and follow those
instructions in addition to the instructions in this section.
v The server provides two internal SAS connectors and two SAS/SATA RAID
riser-card slots on the system board. See “System-board optional-device
connectors” on page 34 for the location of the internal SAS/SATA RAID
connector and riser-card slots. You can replace the IBM ServeRAID SAS/SATA
adapter with an optional IBM ServeRAID SAS/SATA adapter in the slot. For
configuration information, see the ServeRAID documentation at
v Do not set the maximum digital video adapter resolution above 1600 x 1200 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 Read the following table before installing memory modules when any Quadro
adapters is installed.
Table 18. NVIDIA Quadro video adapter configurations
Description Supported maximum total memory size
Quadro 600 adapter 128 GB
v Any high-definition video-out connector or stereo connector on any add-on

video adapter is not supported
v The server does not support legacy 5V PCI adapters.
v When you install any PCI adapter, the power cords must be disconnected from
the power source before you remove the PCI Express riser-card assembly and
the PCI-X riser-card assembly. Otherwise, the active power management event
signal will be disabled by the system-board logic, and the Wake on LAN feature

might not work. However, after the server is powered-on locally, the active
power manager active power management event signal will be enabled by the
system-board logic.
v Before you install an additional adapter, go to Table 2 on page 9 for detailed
power supply configurations.
The following illustration shows the adapter connectors on the PCI riser-card
assembly.
PCI PCI
assembly assembly
Adapter Adapter
Adapter Adapter
Full-length
adapter
bracket Full-length
adapter
bracket
To install an adapter, complete the following steps:
Procedure
3. Remove the server cover (see “Removing the cover” on page 39).
4. Determine which expansion slot you will use for the adapter.
5. If you are installing an adapter in PCI expansion slot 1, 2, or 3, remove PCI
riser-card assembly 1; if you are installing an adapter in PCI expansion slot 4,
5, or 6, remove PCI riser-card assembly 2. See “Removing a PCI riser-card
assembly” on page 40.
6. Rotate the bracket out of the way.
7. Slide the expansion-slot cover out of the PCI riser-card assembly expansion
slot.

PCI
riser-card
assembly
Adapter
connectors Bracket
Expansion-slot
cover
Full-length
adapter Adapter
bracket
Figure 44. Adapter installation
8. Install the adapter:

a. For riser 1: if the adapter is a full-length adapter for the upper expansion
slot in the riser card, remove the full-length-adapter bracket from
underneath the top of the riser-card assembly and insert it in the end of
the upper expansion slot of the riser-card assembly. See “Stretching a PCI
riser-card assembly” on page 43 for instructions.
b. For riser 2: if the adapter is a full-length adapter for the upper expansion
slot in the riser card, the bracket is on the cage by default. Insert it in the
end of the upper expansion slot of the riser-card assembly. See “Stretching
a PCI riser-card assembly” on page 43 for instructions.
PCI
riser-card
assembly
Full-length
adapter
bracket
Figure 45. PCI riser-card assembly
c. Align the adapter with the PCI connector on the riser card and the guide
on the external end of the riser-card assembly.
d. Press the adapter firmly into the PCI connector on the riser card.

PCI PCI
assembly assembly
Adapter Adapter
Adapter Adapter
Full-length
adapter
bracket Full-length
adapter
bracket
9. Connect any required cables to the adapter.

Attention:
v When you route cables, do not block any connectors or the ventilated space
around any of the fans.
v Make sure that cables are not routed on top of components that are under
the PCI riser-card assembly.
v Make sure that cables are not pinched by the server components.
10. Align the PCI riser-card assembly with the selected PCI riser-card connector
on the system board.

PCI riser-card
assembly 2
PCI riser-card
assembly 1
Figure 47. Installing PCI riser-card assembly
v PCI riser-card connector 1: Carefully fit the two alignment slots on the side
of the assembly onto the two alignment brackets in the side of the chassis;
align the rear of the assembly with the guides on the rear of the server.
v PCI riser-card connector 2: Carefully align the bottom edge (the contact
edge) of the riser-card assembly with the PCI riser-card connector on the
system board; align the rear of the assembly with the guides on the rear of
the server.
11. Press down on the assembly. Make sure that the riser-card assembly is fully
seated in the PCI riser-card connector on the system board.
12. Perform any configuration tasks that are required for the adapter.
Results


Installing an optional ServeRAID upgrade adapter
Use this information to install an optional ServeRAID upgrade adapter.
About this task
To install an optional ServeRAID upgrade adapter, complete the following steps:
Procedure
2. Turn off the server and peripheral devices and disconnect all power cords.
4. Connect the supercap cable to the ServeRAID upgrade adapter.
Battery cable
ServeRAID memory module
Figure 48. ServeRAID upgrade adapter and supercap cable
5. Attach the three pegs to the ServeRAID upgrade adapter and install the
ServeRAID upgrade adapter into the system board.
Rententions
ServeRAID memory
module
RAID upgrade
connector
Figure 49. Installing ServeRAID upgrade adapter and supercap cable
6. Connect the other end of the supercap cable to the battery.

Battery cable ServeRAID memory module
Battery
Figure 50. Connecting the supercap cable
Note: Make sure the battery is seated properly (see “Installing a ServeRAID
SAS controller battery on the remote battery tray”).
Results

Installing a ServeRAID SAS controller battery on the remote battery

tray
Use this information to install a ServeRAID SAS controller battery on the remote
battery tray.
About this task
Note: For brevity, in this documentation the Intelligent Battery Backup Unit (iBBU)
is often referred to as the battery.
When you install any RAID adapter that comes with batteries, it is sometimes
necessary to install the batteries in another location in the server to prevent the
batteries from overheating. The batteries must be installed near the fan cage.
To install a RAID adapter battery in the server, complete the following steps:
Note: If you are installing ServeRAID-M5100 Series 512 MB cache RAID 5 upgrade
that comes with a battery, you must install the battery in ServeRAID SAS controller
remote battery retention instead (see "Installing an optional ServeRAID SAS
controller battery holder").

Battery 4 / flash power module 4
Figure 51. Installing a ServeRAID SAS controller battery on the remote battery tray
Procedure
2. Turn off the server and peripheral devices and disconnect all power cords and
external devices (see“Turning off the server” on page 24).
4. Connect one end of the battery cable to the ServeRAID SAS controller battery
connector.
5. Route the remote battery cable along the chassis.
Attention: Make sure that the cable is not pinched and does not cover any
connectors or obstruct any components on the system board.
6. Install the battery near the fan cage:
a. Align the battery cable connector with the slot on the battery holder. Place
the battery into the battery holder and make sure that the battery holder
engages the battery securely.

Connector
Figure 52. RAID adapter battery installation
Note: The positioning of the remote battery depends on the type of the
remote batteries that you install.
b. Connect the other end of the battery cable to the battery cable connector on
the battery.
c. Place the battery retention clip underneath while pressing the release tab
toward the front of the server until it snaps in place to hold the battery
retention clip firmly in place.
Note: The battery must recharge for at least 6 hours under normal operating
conditions. To protect your data, the ServeRAID controller firmware changes
the write policy to write-through until the battery unit is sufficiently charged.
When the battery unit is charged, the ServeRAID controller firmware changes
the write policy to write-back.
Results


Installing the dual-port network adapter
Use this information to install the dual-port network adapter.
About this task
You can purchase one of the following dual-port network adapters to add two
additional network ports in the server. To order a dual-port network adapter
option, contact your IBM sales representative or IBM reseller.
Table 19. Supported dual-port network adapters on the network connector
Option
part FRU part
Dual-port network adapter number number Remark
Mellanox ConnectX-3 dual-port 90Y6338 90Y4956
QDR/FDR10 mezz card
Qlogic dual-port 10GbE SFP+ 90Y6454 90Y5099 Four fans installed
Embedded VFA required.
Emulex dual-port 10GbE SFP+ 90Y6456 90Y5100
Embedded VFA III
Dual-port FDR embedded adapter 00D4143 90Y6606
Note: You can purchase IBM System x3650 M4 Thermal Solution Kit (option part number
46W8422) to acquire an additional fan for your server.
v To configure network adapters, complete the following steps:
1. From the Setup utility main menu (see “Using the Setup utility” on page
154), select System Settings > Network.
2. From the Network Device List, select one network adapter.
Note: You might need to enter each item (displaying MAC address) to see
detailed information.
3. Press Enter to configure the network adapter settings.
v To convert the NIC/iSCSI/FCoE for Emulex Dual Port 10GbE SFP+ Embedded
VFA III, complete the following steps:
154), select System Settings > Network and press Enter.
2. From the Network Device List, select Emulex network adapter.
3. Press Enter to configure Emulex network adapter, select Personality and
press Enter to change the settings.
– NIC
– iSCSI (enabled after FoD installed)
– FCoE (enabled after FoD installed)
v To download the latest version of drivers for iSCSI and FCoE from the IBM
website, complete the following steps:
1. Go to http://www.ibm.com/support/fixcentral/.

2. Click Product support > System x > Product family > System x3650 M4 >
7915.
3. From the Operating system menu, select your operating system, and then
click Search to display the available drivers.
4. Download the latest version of drivers.
– Emulex iSCSI Device Driver for Windows 2008
– Emulex FCoE Device Driver for Windows 2008
Note: Changes are made periodically to the IBM website. The actual procedure
might vary slightly from what is described in this document.
v Port 0 on the Emulex Dual Port 10GbE SFP+ Embedded VFA III can be
configured as shared system management.
v When the server is in standby mode, both ports on the Emulex Dual Port 10GbE
SFP+ Embedded VFA III function at 100M connection speed with Wake on LAN
feature.
The Emulex Dual Port 10GbE SFP+ Embedded VFA III is automatically disabled if
one of the following errors occurs:
v An error log indicates a temperature warning for the Ethernet adapter.
v All power supplies are removed or the server is disconnected from the power
source.
To install the dual-port network adapter, complete the following steps:
Procedure
4. Remove the PCI riser-card assembly (if installed) from PCI riser connector 2
(see “Removing a PCI riser-card assembly” on page 301).
5. Remove the adapter filler panel on the rear of the chassis (if it has not been
removed already).

Network adapter
filler panel
Figure 53. Adapter filler panel removal
6. Touch the static-protective package that contains the new adapter to any
unpainted metal surface on the server. Then, remove the adapter from the
package.
7. Align the adapter so that the port connectors on the adapter line up with the
pin and thumbscrew on the chassis; then, align the connector of the adapter
with the adapter connector on the system board.
Network
adapter Captive screws
Screw holes
Retention
brackets
Thumbscrew
Pin
Network
adapter connector
Figure 54. Network adapter installation

8. Press the adapter firmly until the pin, and retention brackets engage the
adapter. Make sure the adapter is securely seated on the connector on the
system board.
Attention: Make sure the port connectors on the adapter are aligned
properly with the chassis on the rear of the server. An incorrectly seated
adapter might cause damage to the system board or the adapter.
9. Fasten the thumbscrew on the rear side of the chassis.
10. Fasten the two captive screws on the network adapter.
11. Reinstall the PCI riser-card assembly in PCI riser connector 2 if you have
removed it previously (see “Replacing a PCI riser-card assembly” on page
302).
Results

Installing a hot-swap ac power supply

Use this information to install a hot-swap ac power supply.
About this task
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 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.
one of a different wattage, go to Table 2 on page 9 for detailed configurations.
v The server comes with one hot-swap 12-volt output power supply that connects
to power supply bay 1. The input voltage is 100-127 V ac or 200-240 V ac
auto-sensing.
v Power supplies in the server must be with the same power rating or wattage to
ensure that the server will operate correctly. For example, you cannot mix
550-watt and 750-watt power supplies in the server.
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 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
Statement 5

CAUTION:
2
1
Statement 8
CAUTION:
label attached.
technician.
Power supply
filler panel
Hot-swap
power supply 2
Figure 55. Power supply installation
To install a hot-swap ac power supply, complete the following steps:

Procedure
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.
3. 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
power supplies.
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.
Attention: Do not install power supplies of different watt in the server.
5. Route the power cord through the handle and cable tie if any, 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 ac 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.
Figure 56. Power information label
power supplies.

XXXW ~ AC XXXW ~ AC
1 xxx-xxx/ 2 xxx-xxx/
xxx-xxxV~ xxx-xxxV~
x,x/x,x A x,x/x,x A
xx/xx Hz xx/xx Hz
Power supplies
Figure 57. Attaching the redundant power information label
Installing a hot-swap dc power supply

Use this information to install a hot-swap dc power supply.
About this task
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 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.
– Torque the wiring-terminal screws to 0.50 ~ 0.60 newton-meters (4.43 ~ 5.31
inch-pounds).
For more information, see Statement 34 below.

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

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.
1. Turn OFF all power sources and 1. Turn OFF all power sources and
equipment that is to be attached to this equipment that is to be attached to this
product. product.
2. Attach signal cables to the product. v For ac systems, remove all power
3. Attach power cords to the product. cords from the chassis power
receptacles or interrupt power at the
v For ac systems, use appliance inlets.
ac power distribution unit.
v For dc systems, ensure correct polarity
v For dc systems, disconnect dc power
of -48 V dc connections: RTN is + and
sources at the breaker panel or by
-48 V dc is -. Earth ground should use
turning off the power source. Then,
a two-hole lug for safety.
remove the dc cables.
4. Attach signal cables to other devices.
2. Remove the signal cables from the
5. Connect power cords to their sources. 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.

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.

Procedure
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.
Figure 58. DC power supply rear view
5. If you are installing a hot-swap power supply into an empty bay, remove the
power-supply filler from the power-supply bay.
Power cord
connectors
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 on page
“Installing a hot-swap dc power supply” on page 79. 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.
power supplies.
Figure 61. Redundant power information label
Installing a hot-swap fan

Use this information to install a hot-swap fan.
About this task
The server comes standard with three replaceable double fans. For proper cooling,
the server requires that all four fans be installed at all times.
Attention: To ensure proper operation, replace a failed hot-swap fan within 30

seconds.
To install an additional hot-swap fan, complete the following steps:

Vertical tabs
Fan 4
Fan 3
Fan 2
Fan 1
Figure 62. Fan installation
Procedure
Attention: To ensure proper system cooling, do not remove the top cover for
more than 30 minutes during this procedure.
3. Rotate the air baffle up.
4. Orient the new fan over its position in the fan bracket so that the connector on
the bottom aligns with the fan connector on the system board.
5. Align the vertical tabs on the fan with the slots on the fan cage bracket.
6. Push the new fan into the fan connector on the system board. Press down on
the top surface of the fan to seat the fan fully. Make sure that the yellow LED
next to the fan connector on the system board is off.
Results


Installing a SAS/SATA 8 Pac HDD option
Use this information to install a SAS/SATA 8 Pac HDD option.
About this task
You can install an IBM System x3650 M4 Hot-swap SAS/SATA 8 Pac HDD option
to add eight additional 2.5-inch hot-swap hard disk drives in the server. See
http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/ for a
list of supported optional devices. To order a SAS/SATA 8 Pac HDD option,
contact your IBM sales representative or IBM reseller.
The SAS/SATA 8 Pac HDD option kit contains the following components:
v One 2.5-inch hard disk drive backplane
v One SAS expander adapter
v Two M3 x 5 screws
v One SEARAY cable, which contains two SAS signal cables attached to the
expander adapter
v Two SAS signal cables (610 mm)
Note: The 8 pac HDD option including structural parts and Tier 1 parts.
To install a SAS/SATA 8 Pac HDD option, complete the following steps:
Procedure
4. Remove the two 4-drive filler panels that are to the right of drive bay 8,
beneath the IDs 8 - 15 on the front bezel.
4-drive
filler panel
Figure 63. Filler panels
5. To obtain more working room, remove fans 2 and 3 (see “Removing a

hot-swap fan” on page 336).
6. Pull the hard disk drives or fillers out of the server slightly to disengage them
from the backplanes. For more information, (see “Removing a hot-swap hard
disk drive” on page 270).

7. Disconnect the SAS signal cables from the system board. Leave the other end
of the SAS signal cables connected to the hard disk drive backplanes.
8. Remove hard disk drive backplane 1 from the server.
Hard disk drive

backplane
SAS
signal
cable
Configuration
cable
Power
cable
Figure 64. Hard disk drive backplane removal
a. From backplane 1, disconnect the following cables in the order listed:

v Power cable 1
v SAS signal cable 2
v Configuration cable 3
b. Lift backplane 1 out of the server by pulling it toward the rear of the
server and then lifting it up.
9. Install the new backplane in slot 2:
a. Connect two SAS signal cables (610 mm) to new backplane 2. The new
backplane comes with the option kit.
b. Connect the configuration cable to backplane 2.
c. Screw the SEARAY cable to backplane 2 as shown in the following
illustration and connect two SAS signal cables to backplane 1.

SAS Expander
SAS signal adapter
cables (610 mm)
Configuration
cables
SEARAY cable
Configuration
cable Hard disk drive
backplane
Power
cable
SAS signal
cables
Power
cable
Figure 65. Cables connection
d. Connect the configuration cable and the power cable back to backplane 1.
e. Angle the new backplane and place the bottom edge into the slots for
backplane 2 on the chassis next to the optical drive.
SAS Expander
adapter
Hard disk drive

backplane
Figure 66. New backplane installation
f. Angle the backplane and place the bottom edge into the slots for backplane
1 on the chassis.

g. Rotate the backplane upright so that the bracket goes underneath the latch
and tabs on the chassis and is engaged into the slots on the backplane
bracket.
10. Connect the loose end of the SAS signal cables (610 mm) to the system board.
Route the cable underneath the cable retention features on the baffle. See the
illustration.
SAS 1
SAS 0
SAS signal cables (610 mm)
Figure 67. SAS signal cables (610 mm) routing
11. Make sure that the configuration cable is connected to the backplanes and
system board.

Configuration cable
Figure 68. Configuration cable routing
12. Make sure that the SAS power cable is connected to the backplanes and
system board.

SAS/SATA
power cable
Figure 69. SAS power cable routing
13. If you removed any fans, install them.

14. Insert the hard disk drives and the fillers the rest of the way into the bays.
Results


Installing a 16 x 2.5-inch Hot-Swap HDD Assembly Kit with Expander
for 12Gb RAID
Use this information to install a 16 x 2.5-inch Hot-Swap HDD Assembly Kit.
About this task
You can install an IBM System x3650 M4 16 x 2.5-inch Hot-Swap HDD Assembly
Kit with Expander for 12Gb. See http://www.ibm.com/systems/info/x86servers/
serverproven/compat/us/ for a list of supported optional devices. To order a 16 x
2.5-inch Hot-Swap HDD Assembly Kit with Expander for 12Gb RAID,contact your
IBM sales representative or IBM reseller.
The 16 x 2.5-inch Hot-Swap HDD Assembly Kit with Expander for 12Gb RAID
contains the following components:
v One expander
v One backplane connection cable
v Two screws
v One power cable
v One configuration cable
v Two mini-SAS HD cables
v Eight 2.5-inch HDD fillers
To install the 16 x 2.5-inch Hot-Swap HDD Assembly Kit with Expander for 12Gb
RAID, complete the following steps:
Procedure
4-drive
filler panel


a. Connect the following cables in the order listed:
v Mini-SAS cables 2
v Power cable 3
v Backplane connection cable 4
SAS Expander
adapter
Configuration
cables
Mini-SAS
cables
Backplane connection cable
Configuration
cable Hard disk drive
backplane
Power
cable
Power
cable
Figure 71. Cables connection
b. Angle the new expander and place the bottom edge into the slots on the
chassis next to the optical drive.

SAS Expander
adapter
Hard disk drive

backplane
c. Rotate the expander upright so that the bracket goes underneath the latch
bracket.
7. Touch the static-protective package that contains the RAID adapter to any
unpainted metal surface on the server. Then, remove the RAID adapter from
the package.
8. Remove the PCI riser-card assembly 1 (see “Removing a PCI riser-card
9. Install the RAID adapter in the connector on the PCI riser card (see “Installing
an adapter” on page 64).
Attention: Incomplete insertion might cause damage to the server or the
adapter.
10. Connect the mini-SAS signal cables to the connectors on the RAID adapter.
11. Align and install the PCI riser-card assembly in the server (see “Installing a
PCI riser-card assembly” on page 144).

PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter
Figure 73. PCI riser-card assembly installation
12. Route the cables underneath the cable retention .
Adapter
Port 8-11
Port 12-15
SAS signal
cables
Figure 74. Mini-SAS signal cables routing

system board.
Configuration cable
system board.

SAS/SATA
power cable

Results

Installing a SAS/SATA 8 Pac HDD with a ServeRAID adapter option

Use this information to install a SAS/SATA 8 Pac HDD with a ServeRAID adapter
option.
About this task
You can install an IBM System x3650 M4 Hot-swap SAS/SATA 8 Pac HDD with a
ServeRAID adapter option. See http://www.ibm.com/systems/info/x86servers/
serverproven/compat/us/ for a list of supported optional devices. To order a
SAS/SATA 8 Pac HDD with a ServeRAID adapter option, contact your IBM
marketing representative or authorized reseller.
The SAS/SATA 8 Pac HDD with a ServeRAID adapter option kit contains the
following components:
v Eight blank EMC fillers

v Two SAS signal cables
v One internal power cable
v One RAID adapter (part number 00D7082 or 46M0912)
Note: RAID adapter comes in a different option kit. Touch the static-protective
package to any unpainted metal surface on the server.
To install a SAS/SATA 8 Pac HDD with a ServeRAID adapter option, complete the
following steps:
Note: You can install the RAID adapter into PCI riser-card assembly 1 only.
Procedure
4-drive
filler panel


SAS Hard disk drive
signal backplane
cable
Configuration
cable
Power
cable

v SAS signal cable 2
v Power cable 3
b. Angle the new backplane and place the bottom edge into the slots for
c. Rotate the backplane upright so that the bracket goes underneath the latch
bracket.
the package.
Note: While installing the RAID adapter (part number 00D7082) into PCI
riser-card assembly, it can be installed in slot 1 or slot 2 only.
adapter.

10. Connect the SAS signal cables to the connectors on the RAID adapter:
Connector for Connector for

drive bays 8-11 drive bays 12-15
signal cable signal cable
RAID adapter
Figure 79. RAID adapter (part number 46M0912)

RAID adapter
Figure 80. RAID adapter (part number 00D7082)
a. Connect a SAS signal cable that comes with the option kit to the RAID
adapter connector for drive bays 8-11.
b. Connect another SAS signal cable to the other SAS connector for drive
bays 12-15.

PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter
12. Route the cables underneath the cable retention (taking the RAID adapter, part
number 46M0912, as an example).

Adapter
Port 8-11
Port 12-15
SAS signal
cables
Figure 82. SAS signal cables routing
system board.

Configuration cable
system board.

SAS/SATA
power cable

Results

Installing a 16x2.5-inch Hot-Swap HDD Assembly Kit for 12Gb/6Gb

RAID
Use this information to install a 16x2.5-inch Hot-Swap HDD Assembly Kit for
12Gb/6Gb RAID.
About this task
You can install an IBM System x3650 M4 16x2.5-inch Hot-Swap HDD Assembly Kit
for 12Gb/6Gb RAID. See http://www.ibm.com/systems/info/x86servers/
serverproven/compat/us/ for a list of supported optional devices. To order a
16x2.5-inch Hot-Swap HDD Assembly Kit for 12Gb/6Gb RAID, contact your IBM
sales representative or IBM reseller.
The 16x2.5-inch Hot-Swap HDD Assembly Kit for 12Gb/6Gb RAID contains the
following components:

v One hot-swap HDD backplane
v One power cable
v Two mini-SAS cables
v Eight 2.5-inch HDD fillers
To install the 16x2.5-inch Hot-Swap HDD Assembly Kit for 12Gb/6Gb RAID,
complete the following steps:
Procedure
4-drive
filler panel


SAS Hard disk drive
signal backplane
cable
Configuration
cable
Power
cable

v Mini-SAS signal cable 2
v Power cable 3
b. Angle the new backplane and place the bottom edge into the slots for
c. Rotate the backplane upright so that the bracket goes underneath the latch
bracket.
the package.
adapter.
10. Connect the mini-SAS signal cables to the connectors on the RAID adapter.

PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter
12. Route the cables underneath the cable retention .

Adapter
Port 8-11
Port 12-15
SAS signal
cables
Figure 88. Mini-SAS signal cables routing
system board.

Configuration cable
system board.

SAS/SATA
power cable

Results

Installing a SAS/SATA 8 Pac HDD with two 6 GB performance

optimized HBA adapters option
Use this information to install a SAS/SATA 8 Pac HDD with two 6 GB
performance optimized HBA adapters option.
About this task
You can install an IBM System x3650 M4 Hot-swap SAS/SATA 8 Pac HDD with
two 6 GB performance optimized HBA adapters option. See http://www.ibm.com/
systems/info/x86servers/serverproven/compat/us/ for a list of supported
optional devices. To order a SAS/SATA 8 Pac HDD with two 6 GB performance
optimized HBA adapters option, contact your IBM sales representative or IBM
reseller.

The SAS/SATA 8 Pac HDD with two 6 GB performance optimized HBA adapters
option kit contains the following components:
Note: You must purchase the SAS cable option (part number 00D9532) before
installing this kit.
v Eight blank EMC fillers
v SAS signal cables (including the ones from the SAS cable option)
v Two RAID adapters (part number 46M0912)
Note: RAID adapters come in a different option kits. Touch the static-protective
packages to any unpainted metal surface on the server.
To install a SAS/SATA 8 Pac HDD with two 6 GB performance optimized HBA

adapters option, complete the following steps:
Procedure
4-drive
filler panel

6. Remove the 2 SAS cables which connect both the backplane and the system
board.

Port 4-7
Port 0-3
Port 0-3
Port 4-7 SAS signal cables
Figure 92. SAS cables removal
7. Take out the 2 SAS cables (925 mm) from the SAS cable option and connect
them to the backplane.

SAS signal cables
Figure 93. SAS cables connection
the package.
adapter.
a. Connect a SAS signal cable to the RAID adapter connector for drive bays
0-3.
bays 4-7.

RAID adapter
Figure 94. RAID adapter connectors
PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter
13. Route the cables underneath the cable retention.

Adapter
Port 0-3
Port 4-7
SAS signal
cables
14. Refer from step 6 of the “Installing a SAS/SATA 8 Pac HDD with a
ServeRAID adapter option” on page 97 section for installing the second
backplane, arranging the cable routing, installing the fans, and installing the
hard disk drives. The illustration below is the cable routing for the second set
of RAID adapter and backplane.

Adapter
Port 8-11
Port 12-15
SAS signal
cables
Figure 97. Cable routing for the second set of RAID adapter and backplane
Results
Installing 2 x 8 1.8-inch SSDs with two 6 GB performance optimized

HBA adapters option
Use this information to install 2 x 8 1.8-inch SSDs with two 6 GB performance
optimized HBA adapters option.
About this task
To order 2 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA adapters

The 2 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA adapters

v Four SAS signal cables
v Two configuration cables
v Two eXFlash 1.8-inch drive cage and backplane assemblies

To install the 2 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA

adapters option in the server, complete the following steps.
Procedure
4-drive
filler panel

6. Install the new backplane assemblies.
eXFlash 1.8-inch drive cage

and backplane assembly
Figure 99. New backplane assemblies installation
7. Connect the following cables in the order listed:

v SAS signal cables 2
v Power cable 3
SAS signal cables

Configuration
cable
Power
cable
Figure 100. Cable connections
the package.
10. Install both RAID adapters in the connectors on the PCI riser card (see
“Installing an adapter” on page 64).
adapter.
bays 12-15.

Connector for Connector for Connector for Connector for
drive bays 8-11 drive bays 12-15 drive bays 16-19 drive bays 20-23
signal cable signal cable signal cable signal cable
RAID adapter RAID adapter
c. Connect a SAS signal cable that comes with the option kit to the RAID
d. Connect a SAS signal cable that comes with the option kit to the RAID
12. Align and install the PCI riser-card assembly 1 in the server (see “Installing a
PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter

Adapter
Port 8-11
Port 12-15
SAS signal
cables

Adapter
Port 16-19
Port 20-23
SAS signal
cables
system board.

SAS/SATA backplane SAS/SATA backplane
config connector 1 config connector 2
Configuration cable Configuration cable

(Connector for drive (Connector for drive
bays 0-7 and 8-15) 3 bays 16-23)
0
1 2
Figure 105. Configuration cables routing
Note: Leave the cable segment with the label 3 unconnected.

system board.

SAS/SATA
power cable
Figure 106. SAS/SATA power cable routing

Results

Installing 4 x 8 1.8-inch SSDs with two 6 GB performance optimized

HBA adapters option
Use this information to install 4 x 8 1.8-inch SSDs with two 6 GB performance
optimized HBA adapters option.
About this task
To order 4 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA adapters

The 4 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA adapters

v Four SAS signal cables

v Two eXFlash 1.8-inch drive cage and backplane assemblies
To install the 4 x 8 1.8-inch SSDs with two 6 GB performance optimized HBA

adapters option in the server, complete the following steps.
Procedure
4-drive
filler panel

6. Install the new backplane assemblies.

Figure 108. New backplane assemblies installation
7. Connect the following cables in the order listed:

v SAS signal cables 2
v Power cable 3
SAS signal cables

Configuration
cable
Power
cable
the package.
10. Install both RAID adapters in the connectors on the PCI riser card (see
“Installing an adapter” on page 64).
adapter.
bays 20-23.

Connector for Connector for Connector for Connector for
drive bays 16-19 drive bays 20-23 drive bays 24-27 drive bays 28-31
signal cable signal cable signal cable signal cable
RAID adapter RAID adapter
c. Connect a SAS signal cable that comes with the option kit to the RAID
d. Connect a SAS signal cable that comes with the option kit to the RAID
12. Align and install the PCI riser-card assembly 2 in the server (see “Installing a
PCI riser-card
assembly
Bracket
Expansion-slot
cover
Adapter

Adapter
Port 16-19
Port 20-23
SAS signal
cables

Adapter
Port 24-27
Port 28-31
SAS signal
cables
system board.

SAS/SATA backplane
config connector 2
Configuration cable
(Connector for drive
bays 16-31)
2 3
Figure 114. Configuration cables routing
system board.

SAS/SATA
power cable
Figure 115. SAS/SATA power cable routing

Results

Installing an optional tape drive

Use this information to install an optional tape drive.
About this task
The IBM System x3650 M4 RDX-DDS internal enablement kit is used to install an
IBM tape drive in an IBM System x3650 M4 server. The IBM System x3650 M4
RDX-DDS internal enablement kit is compatible only with the following tape
drives:
v IBM DDS Generation 5 (DDS/5) SATA tape drive
v IBM DDS Generation 6 (DDS/6) USB tape drive
v IBM RDX USB Removable Hard Disk Drive
The RDX-DDS internal enablement kit contains the following components:

v One tape enablement tray
v One SAS signal cable (for USB tape drive only)
v One tape drive power cable
v Four M3 x 6 screws
The following illustration shows how to install an optional tape drive.
Figure 116. Tape drive installation
To install a SATA or USB tape drive, complete the following steps:
Procedure
3. Install the tape drive on the tray as shown in the following illustration. If the
tape drive comes with a metal spacer attached, remove the spacer before you
install the tape drive on the tray.
Figure 117. Installing the tape drive on the tray
4. Prepare the drive according to the instructions that come with the drive, setting
any switches or jumpers.

5. Connect the following tape enablement kit cables to the connectors on the
system board:
v SAS signal cables into the SAS connectors on the system board
v Tape drive power cable to the system board
SATA tape
drive signal
cable
Tape drive
power cables
6. Slide the tape-drive assembly most of the way into the tape-drive bay.
7. Connect the SAS signal cable and the power cable to the back of the tape drive.
Attention: Make sure that all the cables are positioned underneath the
tape-drive assembly before you insert the assembly in the tape-drive bay.
Otherwise, the cables might be damaged.
8. Slide the tape-drive assembly the rest of the way into the tape-drive bay.
9. Push the latch to the closed (locked) position.
Results


Installing a USB embedded hypervisor flash device
Use this information to install a USB embedded hypervisor flash device.
About this task
To install a USB hypervisor flash device, complete the following steps:
Procedure
2. Turn off the server and peripheral devices and disconnect the power cords.
4. Remove PCI riser-card assembly (see “Removing a PCI riser-card assembly” on
page 40).
5. Align the flash device with the connector on the system board and push it into
the USB connector until it is firmly seated.
6. Pull up the blue locking collar to lock the flash device into the USB connector.
Lockbar
USB embedded
hypervisor
flash device
Figure 119. USB hypervisor flash device installation
Results

Note: You must configure the server to boot from the hypervisor USB drive. See
Chapter 3, “Configuration information and instructions,” on page 149 for
information about enabling the embedded hypervisor.

Installing an additional microprocessor and heat sink
Use this information to install an additional microprocessor and heat sink.
About this task
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:
v Microprocessors are to be installed only by trained technicians.
Important: Always use the microprocessor installation tool to install a
microprocessor. Failing to use the microprocessor installation tool may damage
the microprocessor sockets on the system board. Any damage to the
microprocessor sockets may require replacing the system board.
v The server supports up to two Intel Xeon™ E5-2600 series multi-core
microprocessors, which are designed for the LGA 2011 socket. See
list of supported microprocessors.
v Do not mix microprocessors with different cores in the same server.
v The first microprocessor must always be installed in microprocessor socket 1 on
the system board.
v When one microprocessor is installed, the air baffle must be installed to provide
proper system cooling.
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 fan. See “Installing a memory module” on page 54 for
details about the 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 to determine
whether you have to update the server firmware. To download the latest level of
server firmware and other code updates for your server, go to
v The microprocessor speeds are automatically set for this server; therefore, you
do not have to set any microprocessor frequency-selection jumpers or switches.
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 more information about applying or
working with thermal grease, see “Thermal grease” on page 141.
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 sales
representative or IBM reseller.
There are two types of microprocessor installation tools. The tools are similar in
function and design, however Tool A has one setting for installing one size of
microprocessor, and supports the following families of microprocessors: E5-26xx,
E5-46xx. Installation Tool B has two settings for installing two different sizes of
microprocessors. The settings that are marked on Tool B are “L” for smaller low
core microprocessors, and “H” for larger high core microprocessors. Installation
Tool B supports the following families of microprocessors: E5-26xx, E5-46xx,
E5-26xx v2, E5-46xx v2.
Microprocessor Installation Tools A and B are shown in the following illustration.
Installation tool
Installation tool
Microprocessor
Cover
Microprocessor
Microprocessor Installation Tool A Microprocessor Installation Tool B
Figure 120. Microprocessor installation tools
To install an additional microprocessor and heat sink, complete the following steps:
Procedure
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 39.
5. Rotate the heat sink retention module release lever to the open position.

Figure 121. Heat-sink lever rotation
6. Open the microprocessor socket release levers and retainer:
Figure 122. Microprocessor socket levers and retainer disengagement
a. Identify which release lever is labeled as the first release lever to open and
open it.
b. Open the second release lever on the microprocessor socket.
c. Open the microprocessor retainer.
Attention: Do not touch the connectors on the microprocessor and the
microprocessor socket.
7. Install the microprocessor on the microprocessor socket:
a. Touch the static-protective package that contains the new microprocessor
to any unpainted on the chassis or any unpainted metal surface on any other
grounded rack component; then, carefully remove the microprocessor from
the package.
b. Release the sides of the cover and remove the cover from the installation
tool. The microprocessor is preinstalled on the installation tool.

Installation tool
Microprocessor
Cover
Figure 123. Installation tool cover removal
Note: Do not touch the microprocessor contacts. Contaminants on the

microprocessor contacts, such as oil from your skin, can cause connection
failures between the contacts and the socket.
c. Align the installation tool with the microprocessor socket. The installation
tool rests flush on the socket only if properly aligned.
Figure 124. Installation tool alignment
d. Install the microprocessor using the following instructions for your

installation tool.
v If using Installation Tool A, twist the handle on the microprocessor tool
assembly counterclockwise to the open position to insert the
microprocessor into the socket, and lift the installation tool out of the
socket.
v If using Installation Tool B, twist the handle of the installation tool
assembly counterclockwise until the microprocessor is inserted into the
socket, and lift the installation tool out of the socket. The following
illustration shows the tool handle in the open position.

Figure 125. Installation tool handle adjustment
E5-x6xx
E5-x6xx v2
L
H
Figure 126. Installation Tool B
Attention:
v Do not press the microprocessor into the socket.
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.
8. Remove the microprocessor socket cover, tape, or label from the surface of the
microprocessor socket, if one is present. Store the socket cover in a safe place.

Socket cover
Microprocessor
Figure 127. Socket cover removal

9. Close the microprocessor socket release levers and retainer:
Microprocessor
release lever
Microprocessor
Microprocessor
release lever
Figure 128. Microprocessor socket levers and retainer engagement
a. Close the microprocessor retainer on the microprocessor socket.

b. Identify which release lever is labeled as the first release lever to close and
close it.
c. Close the second release lever on the microprocessor socket.
10. Install the heat sink.
Attention:
v Do not set down the heat sink after you remove the plastic cover.
v 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” on page 141 for more information.

Figure 129. Thermal grease
a. Remove the plastic protective cover from the bottom of the heat sink.
b. Position the heat sink over the microprocessor. The heat sink is keyed to
assist with proper alignment.
Figure 130. Heat sink installation
c. Align and place the heat sink on top of the microprocessor in the retention
bracket, thermal material side down.
d. Press firmly on the heat sink.
e. Rotate the heat sink retention module release lever to the closed position
and hook it underneath the lock tab.
11. If you installed the second microprocessor, install the fourth fan (see
“Replacing a hot-swap fan” on page 337).
Results


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. Use this information to replace damaged or contaminated
thermal grease on the microprocessor and heat sink.
About this task
When you are installing the heat sink on the same microprocessor that it 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.
Notes:
v Read the safety information that begins on “Safety” on page vii.
v Read the “Installation guidelines” on page 36.
v Read “Handling static-sensitive devices” on page 39.
To replace damaged or contaminated thermal grease on the microprocessor and

heat sink, complete the following steps:
Procedure
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.
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.
0.02 mL of thermal
grease
Microprocessor
Figure 131. Thermal grease distribution
Note: If the grease is properly applied, approximately half of the grease will
remain in the syringe.

Figure 132. Syringe
6. Install the heat sink onto the microprocessor as described in 10 on page 362.
Completing the installation

Use this information to complete the installation.
About this task
To complete the installation, complete the following steps:
Procedure
1. If you removed the air baffle, reinstall it (see “Replacing the air baffle” on page
143).
2. If you removed either of the PCI riser-card assemblies, replace the riser-card
assemblies (see “Installing a PCI riser-card assembly” on page 144).
3. If you removed the server cover, replace it (see “Replacing the cover” on page
145).
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 external cables” on
page 146).
6. Update the server configuration (see “Updating the server configuration” on
page 147).
7. Slide the server back into the rack, if necessary.
8. Start the server. Confirm that it starts correctly and recognizes the newly
installed devices, and make sure that no error LEDs are lit.
9. (IBM Business Partners only) Complete the additional steps in “Instructions for
IBM Business Partners” on page 28.
Results

Replacing the air baffle
Use this information to replace the air baffle.
About this task
To replace the air baffle (if it has been removed), complete the following steps:
Figure 133. Air baffle installation
PCI riser-card
assembly 2
PCI riser-card
assembly 1
Air baffle
Procedure
3. Make sure that PCI riser-card assembly 1 is removed if it is in long position
and sitting on the air baffle (see “Removing a PCI riser-card assembly” on page
40).
4. Align the air baffle pins with the baffle pin holes on both sides of the chassis;
then, lower the air baffle into the server. Press the air baffle down until it is
securely seated.

Note: Close the retaining clip on each end of the DIMM connector before
installing the air baffle for proper cooling.
5. Install PCI riser-card assembly 1, if needed (see “Installing a PCI riser-card
assembly”).
Installing a PCI riser-card assembly

Use this information to install a PCI riser-card assembly.
About this task

To install a PCI riser-card assembly, complete the following steps:
PCI riser-card
assembly 2
PCI riser-card
assembly 1
Figure 134. Installing a PCI riser-card assembly
Procedure
2. Make sure that the server and all peripheral devices are turned off and that the
power cords and all external cables are disconnected.

3. Reinstall any adapters and reconnect any internal cables that you removed in
other procedures.
4. Align the PCI riser-card assembly with the selected PCI riser-card connector on
the system board:
v PCI riser-card connector 1: Carefully fit the two alignment slots on the side
of the assembly onto the two alignment brackets in the side of the chassis.
v PCI riser-card connector 2: Carefully align the bottom edge (the contact edge)
of the riser-card assembly with the PCI riser-card connector on the system
board.
seated in the riser-card connector on the system board.
Results

Replacing the cover

Use this information to replace the cover.
About this task
To replace the server cover, complete the following steps:
Procedure
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.
Important: Before you slide the cover forward, make sure that all the tabs on
the front, rear, and side of the cover engage the chassis correctly. If all the tabs
do not engage the chassis correctly, it will be very difficult to remove the cover
later.
2. Position the cover on top of the server.
3. Slide the cover toward the front of the server.
4. Make sure that the cover correctly engages all the inset tabs on the server.
5. Press down the blue latch on the top (in the center of the front of the server) of
the cover.

1
Cover-release
latch
Figure 135. Cover installation
6. Slide the server all the way into the rack until it latches.
Connecting the external cables

The following illustrations show the locations of the input and output connectors
of the server.
The following illustrations show the locations of the input and output connectors
on the front and rear of the server.
Figure 136. Front view

Ethernet1 10G ethernet
(shared system (with optional
management ethernet) Ethernet2 Ethernet3 Ethernet4 10G ethernet card) Power supply 2
System-management Video Serial USB3 USB4 USB5 USB6 NMI Power supply 1
(ethernet)(dedicated) button
Figure 137. Rear view
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.
If the server comes with an installed operating system, see the documentation that
comes with the operating system for additional cabling instructions.
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.
If you have installed a USB hypervisor memory key on the SAS riser-card, see the
user's guide that comes with the hypervisor memory key. Hypervisor enables guest
operating systems to function on the server.
For information about configuring the integrated Gigabit Ethernet controller, see
“Configuring the Ethernet controller” on page 167.

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 firmware.
Important:
1. Some cluster solutions require specific code levels or coordinated code updates.
If the device is part of a cluster solution, verify that the latest level of code is
supported for the cluster solution before you update the code.
2. 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.
3. 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.
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 website. To check for the latest level of firmware, such as the UEFI
firmware, device drivers, and integrated management module (IMM) firmware, go
to http://www.ibm.com/support/fixcentral/.
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 update the firmware
that is stored in memory on the device or restore the pre-existing firmware from a
CD or DVD image.
The following list indicates where the firmware is stored:

v UEFI firmware is stored in ROM on the system board.
v IMM2 firmware is stored in ROM on the system board.
v Ethernet firmware is stored in ROM on the Ethernet controller and on the
system board.
v ServeRAID firmware is stored in ROM on the system board and the RAID
adapter (if one is installed).
v SAS/SATA firmware is stored in ROM on the SAS/SATA controller on the
system board.
Configuring the server

The following configuration programs come with the server:
v Setup utility
The Setup utility is part of the UEFI firmware. Use it to perform configuration
tasks such as changing interrupt request (IRQ) settings, changing the
startup-device sequence, setting the date and time, and setting passwords. For
information about using this program, see “Using the Setup utility” on page 154.
v Boot Manager program
The Boot Manager is part of the UEFI 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” on page 161.
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 152.
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
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?brand=5000008&Indocid=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” on page 162 and the Integrated
Management Module II User's Guide at http://www.ibm.com/support/entry/
portal/docdisplay?lndocid=MIGR-5086346.

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 can be installed in USB connectors 3 and 4 on
the system board. For more information about using the embedded hypervisor,
see “Using the embedded hypervisor” on page 166.
v Remote presence capability and blue-screen capture
The remote presence and blue-screen capture features are integrated functions of
the integrated management module (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. For more information, see
“Using the remote presence and blue-screen capture features” on page 163.
v Ethernet controller configuration
For information about configuring the Ethernet controller, see “Configuring the
Ethernet controller” on page 167.
v Features on Demand software Ethernet software
The server provides Features on Demand software Ethernet support. You can
purchase a Features on Demand software upgrade key for Fibre Channel over
Ethernet (FCoE) and iSCSI storage protocols. For more information, see
“Enabling Features on Demand Ethernet software” on page 167.
v Features on Demand software RAID software
The server provides Features on Demand software RAID support. You can
purchase a Features on Demand software upgrade key for RAID. For more
information, see “Enabling Features on Demand RAID software” on page 167.
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 run the Setup utility. For more information about using this program,
see “IBM Advanced Settings Utility program” on page 168.
v Configuring RAID arrays
For information about configuring RAID arrays, see “Configuring RAID arrays”
on page 167.
The following table lists the different server configurations and the applications
that are available for configuring and managing RAID arrays.
Chapter 3. Configuration information and instructions 151

Table 20. Server configuration and applications for configuring and managing RAID arrays
RAID array configuration RAID array management
(before operating system is (after operating system is
Server configuration installed) installed)
ServeRAID-M5110 adapter MegaRAID BIOS MegaRAID Storage Manager
Configuration Utility (press (MSM), MegaCLI, and IBM
Ctrl+H to start), pre-boot CLI Director
(press Ctrl+P to start),
ServerGuide, HII
ServeRAID-M5120 adapter MegaRAID BIOS MegaRAID Storage Manager
Configuration Utility (press (MSM), MegaCLI, and IBM
Ctrl+H to start), pre-boot CLI Director
(press Ctrl+P to start),
ServerGuide, HII
Notes:
1. For more information about the Human Interface Infrastructure (HII) and
SAS2IRCU, go to http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5088601.
2. For more information about the MegaRAID, go to http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=MIGR-5073015.
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 from
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-GUIDE.
In addition to the ServerGuide Setup and Installation CD, you must have your
operating-system CD to install the operating system.

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 features:

v An easy-to-use interface
v Diskette-free setup, and configuration programs that are based on detected
hardware
v Device drivers that are provided for the server model and detected hardware
v Operating-system partition size and file-system type that are selectable during
setup
The ServerGuide program performs the following tasks:

v Sets system date and time
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
Setup and configuration overview

ServerGuide setup and configuration overview
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

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/.
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 Set the date and time
v Set and change passwords
v Set the startup characteristics of the server and the order of startup devices
v Set and change settings for advanced hardware features
v View, set, and change settings for power-management features
v View and clear error logs
v Change interrupt request (IRQ) settings
v Resolve configuration conflicts
Starting the Setup utility

Use this information to start up the Setup utility.
About this task
To start the Setup utility, complete the following steps:
Procedure
1. Turn on the server.
Note: Approximately 5 to 10 seconds after the server is connected to 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
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 UEFI 1.10 and UEFI 2.0
compliant adapters and drivers installed in the server.
– Processors
Select this choice to view or change the processor settings.
– Memory
Select this choice to view or change the memory settings.
– 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 controllers, SATA optical drive channels, PCI slots, and video
controller. 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.
– Operating Modes
Select this choice to view or change the operating profile (performance and
power utilization).
– 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. The default is Enable.
- Infinite Boot Retry
Select this choice to enable or disable UEFI to infinitely retry the legacy
boot order. The default is Disable.
- BBS Boot
Select this choice to enable or disable legacy boot in BBS manner. The
default is Enable.
– 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 set the mode of operation after the power lost.
- Commands on USB Interface
Select this choice to enable or disable the Ethernet over USB interface on
IMM. The default is Enable.
- Network Configuration
Select this choice to view the system management network interface port,
the IMM MAC address, the current IMM IP address, and 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 IMM2 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.
- Reset IMM
Select this choice to reset IMM.
– Recovery
Select this choice to view or change the system recovery parameters.
- POST Attempts
Select this choice to view or change the number of attempts to POST.
v POST Attempts Limit
Select this choice to view or change the Nx boot failure parameters.
- System Recovery
Select this choice to view or change system recovery settings.
v POST Watchdog Timer
Select this choice to view or enable the POST watchdog timer.
v POST Watchdog Timer Value
Select this choice to view or set the POST loader watchdog timer value.

v Reboot System on NMI
Select this choice to enable or disable restarting the system whenever a
nonmaskable interrupt (NMI) occurs. Enable is the default.
v Halt on Severe Error
Select this choice to enable or disable the system from booting into OS,
displaying the POST event viewer whenever a severe error was detected.
Disable is the default.
– Storage
Select this choice to view or change the storage device settings.
– Network
Select this choice to view or change the network device options, such as
iSCSI.
– Drive Health
Select this choice to view the status of the controllers installed in the blade
server.
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. This choice is on the full Setup utility menu only.
The POST event log contains the 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 error
messages.
– System Event Log
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” on page
159 for more information.
This choice is on the full and limited Setup utility menu.
– Set Power-on Password
Select this choice to set or change a power-on password. See “Power-on
password” on page 159 for more information.
– Clear Power-on Password
Select this choice to clear a power-on password. See “Power-on password” on
page 159 for more information.
– Set Administrator Password
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. See “Administrator password” on page
160 for more information.
– Clear Administrator Password
Select this choice to clear an administrator password. See “Administrator
password” on page 160 for more information.
v Save Settings
Select this choice to save the changes that you have made in the settings.
v Restore Settings
Select this choice to cancel the changes that you have made in the settings and
restore the previous settings.
v Load Default Settings
Select this choice to cancel the changes that you have made in the settings and
restore the factory settings.
v 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.
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, wait 30 seconds, and then reinstall it.
v Change the position of the power-on password switch (switch 4) on the system
board switch block (SW3) to bypass the power-on password check (see Table 5
on page 33 for more information).

UEFI boot backup
jumper(JP2)
CMOS clear
jumper (JP1)
System TPM physical

Figure 138. System-board switches, jumpers, and buttons
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 “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.
The default for all of the switches on switch block SW3 is Off.
While the server is turned off, move power-on password switch (switch 4) on
the system board switch block (SW3) to the On position to enable the power-on
password override. You can then start the Setup utility and reset the power-on
password. You do not have to return the switch to the previous position.
The power-on password override switch 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
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.
About this task
To use the Boot Manager program, complete the following steps:
Procedure
1. Turn off the server.
2. Restart the server.
3. When the prompt <F12> Select Boot Device is displayed, press F12.
4. Use the Up arrow and Down arrow keys to select an item from the menu and
press Enter.
Results
The next time the server starts, it returns to the startup sequence that is set in the
Setup utility.
Starting 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 UEFI boot backup jumper (JP2) in the backup position (pins 2 and 3). See
“System-board switches, jumpers, and buttons” on page 32 for the location of the
UEFI boot backup jumper (JP2).
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 UEFI boot
backup jumper (JP2) 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
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.
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 (CONFIG) 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 Power/reset control (power-on, hard and soft shutdown, hard and soft reset,
schedule power control).
v Query power-supply input power.
v ROM-based IMM firmware flash updates.
v Serial over LAN (SOL).
v Serial port redirection over telnet or ssh.
v SMI handling
v System event log (SEL) - user readable event log.

The IMM also provides the following remote server management capabilities
through the ipmitool, a 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 II User's
Guide at http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-
5086346.
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.

Obtaining the IMM host name
Use this information to obtain the IMM host name.
About this task
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:
Procedure
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).
Obtaining the IP address for the IMM

Use this information to obtain the IP address for the IMM.
About this task
To access the web interface to use the remote presence feature, you need the IP
address or host name of the IMM. You can obtain the IMM IP address through the
Setup utility and you can obtain the IMM host name from the IMM network access
tag. The server comes with a default IP address for the IMM of 192.168.70.125.
To obtain the IP address, complete the following steps:
Procedure

2. When the prompt <F1> Setup is displayed, press F1. (This prompt is displayed
on the screen for only a few seconds. You must press F1 quickly.) If you have
set both a power-on password and an administrator password, you must type
the administrator password to access the full Setup utility menu.
3. From the Setup utility main menu, select System Settings.

4. On the next screen, select Integrated Management Module.
5. On the next screen, select Network Configuration.
6. Find the IP address and write it down.
7. Exit from the Setup utility.
Logging on to the web interface

Use this information to log on to the web interface.
About this task
To log on to the IMM web interface, complete the following steps:
Procedure
1. On a system that is connected to the server, open a web browser. 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 IMM network access tag provides the
default host name 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 system-event
log.
Note: The IMM is set initially with a user name of USERID and password of
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. Click Log in to start the session. The System Status and Health page provides a
quick view of the system status.
Results
Note: If you boot to the operating system while in the IMM GUI and the message
“Booting OS or in unsupported OS” is displayed under System Status > System
State, disable Windows 2008 or 2012 firewall or type the following command in
the Windows 2008 or 2012 console. This might also affect blue-screen capture
features.
netsh firewall set icmpsetting type=8 mode=ENABLE
By default, the icmp packet is blocked by Windows firewall. The IMM GUI will
then change to “OS booted” status after you change the setting as indicated above
in both the Web and CLI interfaces.

Using the embedded hypervisor
The VMware ESXi embedded hypervisor software is available on the optional IBM
USB flash device with embedded hypervisor.
About this task
The USB flash device can be installed in USB connectors on the system board (see
“System-board internal connectors” on page 30 for the location of the connectors).
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.
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:
Procedure

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 Generic Boot Option > Embedded
Hypervisor. Press Enter, and then select Esc.
5. Select Change Boot Order > Change the order. Use the Up arrow and Down
Arrow keys to select Embedded Hypervisor and use the plus (+) and minus (-)
keys to move Embedded Hypervisor in the boot order. When Embedded
Hypervisor is in the correct location in the boot order, press Enter. Select
Commit Changes and press Enter.
6. Select Save Settings and then select Exit Setup.
Results
If the embedded hypervisor flash device image becomes corrupt, you can
download the image from http://www-03.ibm.com/systems/x/os/vmware/esxi/.
For additional information and instructions, see VMware vSphere 4.1

Documentation at http://www.vmware.com/support/pubs/vs_pages/
vsp_pubs_esxi41_e_vc41.html or the VMware vSphere Installation and Setup Guide at
http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-
esxi-vcenter-server-50-installation-setup-guide.pdf.

Configuring the Ethernet controller
Use this information to configure the 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.
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.
To find device drivers and information about configuring the Ethernet controllers,
go to http://www.ibm.com/supportportal/.
Enabling Features on Demand Ethernet software

You can activate the Features on Demand (FoD) software upgrade key for Fibre
Channel over Ethernet (FCoE) and iSCSI storage protocols that is integrated in the
integrated management module.
For more information and instructions for activating the Features on Demand
Ethernet software key, see the IBM Features on Demand User’s Guide. To download
the document, go to /http://www.ibm.com/systems/x/fod/, log in, and click
Help.
Enabling Features on Demand RAID software

You can activate the Features on Demand (FoD) software upgrade key for RAID
that is integrated in the integrated management module.
For more information and instructions for activating the Features on Demand
RAID software key, see the IBM Features on Demand User’s Guide. To download the
document, go to /http://www.ibm.com/systems/x/fod/, log in, and click Help.
Configuring RAID arrays

Through the Setup utility, you can access utilities to configure RAID arrays.
About this task
The specific procedure for configuring arrays depends on the RAID controller that
you are using. For details, see the documentation for your RAID controller. To
access the utility for your RAID controller, complete the following steps:
Procedure
Note: Approximately 10 seconds after the server is connected to power, the

power-control button becomes active.

2. When prompted, <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 System Settings > Storage.
4. Press Enter to refresh the list of device drivers.
5. Select the device driver for your RAID controller and press Enter.
6. Follow the instructions in the documentation for your RAID controller.
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 IMM2 settings. The remote presence features provide enhanced
systems-management capabilities.
In addition, the ASU program provides IMM LAN over USB interface
configuration 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 IBM Systems Director.
About this task
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.

Installing a newer version
About this task
To locate and install a newer version of IBM Systems Director, complete the
following steps:
Procedure
1. Check for the latest version of IBM Systems Director:
a. Go to http://www.ibm.com/systems/management/director/
downloads.html.
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.
Installing updates with your management server is connected to

the Internet
About this task
If your management server is connected to the Internet, to locate and install

updates and interim fixes, complete the following steps:
Procedure
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.
Installing updates with your management server is not

connected to the Internet
About this task
If your management server is not connected to the Internet, to locate and install
updates and interim fixes, complete the following steps:
Procedure
1. Make sure that you have run the Discovery and Inventory collection tasks.
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 clickContinue.
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)

Use this information to update the Universal Unique Identifier (UUID).
About this task
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.
Procedure
1. Download the Advanced Settings Utility (ASU):
a. Go to http://www.ibm.com/supportportal/.
b. Click 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 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)
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
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 website.
Note: Changes are made periodically to the IBM website. The actual
procedure might vary slightly from what is described in this document.
operating system. Scroll down and look under Online Help to download
the Advanced Settings Utility Users Guide.
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
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 ToolsCenter website at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=TOOL-CENTER. From the IBM ToolsCenter page, scroll
down for the available tools.
Updating the DMI/SMBIOS data

Use this information to update the DMI/SMBIOS data.
About this task
The Desktop Management Interface (DMI) must be updated when the system
board is replaced. Use the Advanced Settings Utility 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 website. To download the ASU and update
the DMI, complete the following steps.
Procedure
1. Download the Advanced Settings Utility (ASU):
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)
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:
<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 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.SysInfoSerialNum <s/n>
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.
To download the Advanced Settings Utility Users Guide, complete the
following steps:
Note: Changes are made periodically to the IBM website. The actual
procedure might vary slightly from what is described in this document.
operating system. Scroll down and look under Online Help to download
the Advanced Settings Utility Users Guide.
v The following commands are examples of using the userid and password
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>
asu set SYSTEM_PROD_DATA.SysEncloseAssetTag <asset_tag> --host <imm_ip>
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:
You can also build a bootable media using the applications available through
the ToolsCenter website at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=TOOL-CENTER. From the IBM ToolsCenter page, scroll
down for the available tools.

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 981 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.
Procedure
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 Hardware components
v Device drivers and firmware
v System software
v UEFI firmware
v 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” on page 184 for
information about using light path diagnostics LEDs.
v Event logs: See “Event logs” on page 196 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.

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=SERV-
XPRESS and “Updating the firmware” on page 149. 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

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 180.
For information about configuring the server, see Chapter 3, “Configuration
information and instructions,” on page 149.
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
http://www.ibm.com/supportportal.
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
http://www.ibm.com/supportportal.
8. Use the troubleshooting tables. See “Troubleshooting by symptom” on page
203 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.
Chapter 4. Troubleshooting 179

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 System x3650 M4
server.
To find service bulletins that are available for the IBM System x3650 M4 server, go
to http://www.ibm.com/supportportal/ and search for 7915, 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 211 for
information about diagnosing microprocessor problems.
v Before you run DSA, 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 diagnostic codes,” on page 827. If the server is halted and no error
message is displayed, see “Troubleshooting by symptom” on page 203 and
“Solving undetermined problems” on page 229.

v For information about power-supply problems, see “Solving power problems”
on page 226, “Power problems” on page 215, and “Power-supply LEDs” on page
191.
v For intermittent problems, check the event log; see “Event logs” on page 196 and
Appendix C, “DSA diagnostic test results,” on page 845.
Performing the checkout procedure

Use this information to perform the checkout procedure.
About this task
To perform the checkout procedure, complete the following steps:
Procedure
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 191).
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 203.
h. 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
184).
i. Check for the following results:
v Successful completion of POST (see “POST” on page 199 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
203; if necessary, see “Solving undetermined problems” on page 229.
v Yes: Run DSA (see “Running the DSA Preboot diagnostic programs” on page
201).
– If DSA reports an error, follow the instructions in Appendix C, “DSA
diagnostic test results,” on page 845.
– If DSA does not report an error but you still suspect a problem, see
“Solving undetermined problems” on page 229.

Diagnostic tools
The section introduces available tools to help you diagnose and solve
hardware-related problems.
v Light path diagnostics
Use light path diagnostics to diagnose system errors quickly. See “Light path
diagnostics” on page 184 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 196 for more
information.
v Integrated management module II
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 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 II (IMM2), see
“Using the integrated management module” on page 162, Appendix A,
“Integrated management module II (IMM2) error messages,” on page 373, and
the Integrated Management Module II User's Guide at http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=MIGR-5086346.
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 collects and analyzes system information to aid in diagnosing
server problems. DSA Portable runs on the server operating system and
collects the following information about the server:
- Drive health information
- Event logs for ServeRAID controllers and service processors
- IMM2 configuration information
- IMM2 environmental information
- Installed hardware, including PCI and USB information
- Installed applications and hot fixes
- Kernel modules
- Light path diagnostics status
- Microprocessor, input/out hub, and UEFI error logs
- Network interfaces and settings
- Option card driver and firmware information

- RAID controller configuration
- Service processor (integrated management module) status and
configuration
- System configuration
- Vital product data, firmware, and UEFI configuration
DSA Portable creates a DSA log, which is a chronologically ordered merge of
the system-event log (as the IPMI event log), the integrated management
module (IMM) event log (as the ASM event log), and the operating-system
event logs. You can send the DSA log as a file to IBM Support (when
requested by IBM Support) 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 199
and Appendix C, “DSA diagnostic test results,” on page 845.
– 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
- IMM2 configuration information
- IMM2 environmental information
- Event logs for ServeRAID controllers and service processors
- Installed hardware, including PCI and USB information
- Light path diagnostics status
- Microprocessor, input/output hub, and UEFI error logs
- Network interfaces and settings
- Option card driver and firmware 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. Emulex network adapter
2. IMM I2C bus
3. Light path diagnostics panel
4. Memory modules
5. Microprocessors
6. Optical devices (CD or DVD)
7. SAS or SATA drives
8. LSI controller
9. Broadcom network adapter

10. FusionIO storage
11. Intel GPU
12. Nvidia GPU
See “Running the DSA Preboot diagnostic programs” on page 201 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 203 for more information.
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.
Before you work inside the server to view light path diagnostics LEDs, read the
safety information “Safety” on page vii and “Handling static-sensitive devices” on
page 39.
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 check log LED is lit, it indicates that information about an un-isolated
fault condition in the server is available in the IMM 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 139. Operator information panel
2. To view the light path diagnostics panel, press the blue release latch on the
operator information panel. Pull forward on the panel until the hinge of the
operator information panel is free of the server chassis. Then pull down on the
panel so that you can view the light path diagnostics panel information. This
reveals the light path diagnostics panel. Lit LEDs on this panel indicate the
type of error that has occurred.

Figure 140. Light path diagnostics panel disengagement
The following illustration shows the light path diagnostics panel.
Figure 141. Light path diagnostics panel
Note any LEDs that are lit, and then reinstall the light path diagnostics panel in
the server.
v Remind button: Press this button to place the system-error LED/check log
LED on the front information panel into Remind mode. 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. In Remind mode, the system-error LED flashes every 2 seconds
until one of the following conditions occurs:

– All known errors are corrected.
– The server is restarted.
– A new error occurs, causing the system-error LED to be lit again.
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. The Reset button is in the lower-right corner
of the light path diagnostics panel.
The system service label inside the server cover provides 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 187 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.
Note: You do not have to remove the server cover to view the LEDs on hard
disk drives and power supplies.
The following illustration shows the LEDs on the system board.
Figure 142. System board error LEDs

Light path diagnostics LEDs
This section 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 17 and
“System-board LEDs” on page 34 for the location of the system board LEDs.
Table 21. 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 an action step is preceded by "(trained technician only)," that step must be performed only by a trained
technician.
LED Description Action
Check log LED An error has occurred and cannot 1. Check the IMM2 system event log and the system-error
be isolated without performing log for information about the error.
certain procedures.
2. Save the log if necessary and clear the log afterwards.
System-error LED An error has occurred. 1. Check the light path diagnostics LEDs and follow the
instructions.
2. Check the IMM2 system event log and the system-error
log for information about the error.
3. Save the log if necessary and clear the log afterwards.
PS When only the PS LED is lit, a The system might detect a power supply error. Complete the
power supply has failed. following steps to correct the problem:
1. Check the power-supply with a lit yellow LED (see
“Power-supply LEDs” on page 191).
2. Make sure that the power supplies are seated correctly
and plugged in a good AC outlet.
3. Remove one of the power supplies to isolate the failed
power supply.
4. Make sure that both power supplies installed in the
server are of the same AC input voltage.
5. Replace the failed power supply.
PS + CONFIG If the PS LED and the CONFIG LED are lit, the system issues
When both the PS and CONFIG an invalid power configuration error. Make sure that both
LEDs are lit, the power supply power supplies installed in the server are of the same rating
configuration is invalid. or wattage.
OVER SPEC The system consumption reaches 1. If the Pwr Rail (A, B, C, D, E, F, G, and H) error was not
the power supply over-current detected, complete the following steps:
protection point or the power
a. Use the IBM Power Configurator utility to determine
supplies are damaged.
current system power consumption. For more
information and to download the utility, go to
http://www.ibm.com/systems/bladecenter/
b. Replace the failed power supply.
2. If the Pwr Rail (A, B, C, D, E, F, G, and H) error was also
detected, follow actions listed in “Power problems” on
page 215 and “Solving power problems” on page 226.

Table 21. Light path diagnostics panel LEDs (continued)
solved.
technician.
PCI An error has occurred on a PCI 1. Check the riser-card LEDs, the ServeRAID error LED, and
card, a PCI bus, or on the system the dual-port network adapter error LED to identify the
board. An additional LED is lit component that caused the error.
next to a failing PCI slot.
2. Check the system-error log for information about the
error.
3. If you cannot isolate the failing component by using the
LEDs and the information in the system-error log, remove
one component at a time; and restart the server after each
component is removed.
4. Replace the following components, in the order shown,
restarting the server each time:
v PCI riser cards
v ServeRAID adapter
v Optional network adapter
v (Trained technician only) System board
5. If the failure remains, go to http://www.ibm.com/
support/entry/portal/docdisplay?lndocid=SERV-CALL.
NMI A nonmaskable interrupt has 1. Check the system-error log for information about the
occurred, or the NMI button was error.
pressed.
CONFIG CONFIG + PS If the CONFIG LED and the PS LED are lit, the system issues
An invalid power configuration an invalid power configuration error. Make sure that both
error has occurred. power supplies installed in the server are of the same rating
or wattage.
CONFIG + CPU If the CONFIG LED and the CPU LED are lit, complete the
A hardware configuration error following steps to correct the problem:
has occurred. 1. 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 356
for additional information about microprocessor
requirements).
2. (Trained technician only) Replace the incompatible
microprocessor.
3. Check the system-error logs for information about the
error. Replace any component that is identified in the
error log.
CONFIG + MEM If the CONFIG LED and the MEM LED are lit, check the
A hardware configuration error system-event log in the Setup utility or IMM2 error messages.
has occurred. Follow steps indicated in Appendix B, “UEFI/POST
diagnostic codes,” on page 827 and Appendix A, “Integrated
management module II (IMM2) error messages,” on page
373.
LINK Reserved.

solved.
technician.
CPU When only the CPU LED is lit, a If the CONFIG LED is not lit, a microprocessor failure occurs,
microprocessor has failed. complete the following steps:
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
for information about installation and requirements.
2. (Trained technician only) Replace the failing
microprocessor (see “Removing a microprocessor and heat
sink” on page 351 and “Replacing a microprocessor and
heat sink” on page 356).
3. For more information, go to http://www.ibm.com/
CPU + CONFIG If the CONFIG LED and the CPU LED are lit, the system
When both the CPU LED and the issues an invalid microprocessor configuration error.
CONFIG LED are lit, the Complete the following steps to correct the problem:
microprocessor configuration is 1. Check the microprocessors that were just installed to
invalid. make sure that they are compatible with each other (see
for additional information about microprocessor
requirements).
2. (Trained technician only) Replace the incompatible
microprocessor.
3. Check the system-error logs for information about the
error. Replace any component that is identified in the
error log.

solved.
technician.
MEM When only the MEM LED is lit, a Note: Each time you install or remove a DIMM, you must
memory error has occurred. disconnect the server from the power source; then, wait 10
seconds before restarting the server.
If the CONFIG LED is not lit, the system might detect a

memory error. Complete the following steps to correct the
problem:
1. Update the server firmware to the latest level (see
“Updating the firmware” on page 149).
2. Reseat or swap the DIMMs with lit LED.
3. Check the system-event log in the Setup utility or IMM
error messages. Follow steps indicated in Appendix B,
“UEFI/POST diagnostic codes,” on page 827 and
Appendix A, “Integrated management module II (IMM2)
error messages,” on page 373.
4. Replace the failing DIMM (see “Removing a memory
module” on page 288 and “Installing a memory module”
on page 54).
MEM + CONFIG If the MEM LED and the CONFIG LED are lit, check the
When both the MEM and system-event log in the Setup utility or IMM2 error messages.
CONFIG LEDs are lit, the Follow steps indicated in Appendix B, “UEFI/POST
memory configuration is invalid. diagnostic codes,” on page 827 and Appendix A, “Integrated
management module II (IMM2) error messages,” on page
373.
TEMP The system or the system 1. Make sure that the heat sink is seated correctly.
component temperature has
2. Determine whether a fan has failed. If it has, replace it.
exceeded a threshold level. A
failing fan can cause the TEMP 3. Make sure that the room temperature is not too high. See
LED to be lit. “Server features and specifications” on page 7 for the
server temperature information.
4. Make sure that the air vents are not blocked.
5. Make sure that the heat sink or the fan on the adapter, or
the optional network adapter is seated correctly. If the fan
has failed, replace it.
6. For more information, go to http://www.ibm.com/
FAN A fan has failed, is operating too 1. Check if your server installed with the adapters
slowly, or has been removed. The mentioned in Table 38 on page 319. If yes, make sure your
TEMP LED might also be lit. server compile with the configuration with four fans
installed.
2. Reseat the failing fan, which is indicated by a lit LED
near the fan connector on the system board.
3. Replace the failing fan (see “Removing a hot-swap fan”
on page 336 and “Replacing a hot-swap fan” on page
337).

solved.
technician.
BOARD An error has occurred on the 1. Check the LEDs on the system board to identify the
system board or the system component that caused the error. The BOARD LED can be
battery. lit due to any of the following reasons:
v Battery
v (Trained technician only) System board
2. Check the system-error log for information about the
error.
3. Replace the failing component:
v Battery (see “Removing the system battery” on page
345 and “Replacing the system battery” on page 347).
v (Trained technician only) System board (see “Removing
the system board” on page 367 and “Replacing the
system board” on page 370).
HDD A hard disk drive has failed or is 1. Check the LEDs on the hard disk drives for the drive
missing. with a lit status LED and reseat the hard disk drive.
2. Reseat the hard disk drive backplane.
3. For more information, see “Light path diagnostics LEDs”
on page 187.
4. 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.
5. If the problem remains, go to http://www.ibm.com/
Power-supply LEDs
The following minimum configuration is required for the server to start.
v One microprocessor in microprocessor socket 1
v One 2 GB DIMM on the system board
v One power supply
v Power cord
v Four cooling fans (fan 1, 2, 3, and 5)
v One PCI riser-card assembly in PCI connector 1

AC power-supply LEDs:
The following minimum configuration is required for the DC LED on the power
supply to be lit:
v Power supply
v Power cord
Note: You must turn on the server for the DC LED on the power supply to be lit.
The following illustration shows the locations of the power-supply LEDs on the ac
power supply.
Figure 143. AC power-supply LEDs
The following table describes the problems that are indicated by various
combinations of the power-supply LEDs on an ac power supply and suggested
AC 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 This is a normal
server or a problem server. condition when no ac
with the ac power power is present.
2. Make sure that the power
source.
cord is connected to a
functioning power source.
3. Restart the server. If the error
remains, check the
power-supply LEDs.
4. If the problem remains,
replace the power-supply.
Off Off On The power supply Replace the power supply.
has failed.
Off On Off The power supply Replace the power supply.
has failed.
Off On On The power supply Replace the power supply.
has failed.

AC power-supply LEDs
AC DC Error (!) Description Action Notes
On Off Off Power-supply not 1. Reseat the power supply. Typically indicates a
fully seated, faulty power-supply is not
2. Follow actions in the “Power
system board, the fully seated.
problems” on page 215.
power supply has
failed, or system 3. If the OVER SPEC LED on
not power-on the light path diagnostics is
lit, follow the actions in
“Light path diagnostics
LEDs” on page 187.
4. If the OVER SPEC LED on
the light path diagnostics is
not lit, check the error LEDs
on the system board and the
IMM2 error messages. Follow
steps in “Power problems”
on page 215 and “Solving
power problems” on page
226 until the problem is
solved.
On Off On The power supply Replace the power supply.
has failed.
On On On The power supply Replace the power supply.
has failed.
DC power-supply LEDs:
The following illustration shows the locations of the power-supply LEDs on the dc
power supply.
Figure 144. DC power-supply LEDs
The following table describes the problems that are indicated by various
combinations of the power-supply LEDs on a dc power supply and suggested
DC power-supply LEDs
IN OK OUT OK Error (!) Description Action Notes
On On Off Normal operation.

DC power-supply LEDs
IN OK OUT OK Error (!) Description Action Notes
Off Off Off No dc power to the 1. Check the dc power to the This is a normal
server or a problem server. condition when no dc
with the dc power power is present.
2. Make sure that the power
source.
cord is connected to a
functioning power source.
3. Restart the server. If the error
remains, check the
power-supply LEDs.
4. If the problem remains,
replace the power-supply.
Off Off On The power supply Replace the power supply.
has failed.
Off On Off The power supply Replace the power supply.
has failed.
Off On On The power supply Replace the power supply.
has failed.
On Off Off Power-supply not 1. Reseat the power supply. Typically indicates a
fully seated, faulty power-supply is not
2. Follow actions in the “Power
system board, or fully seated.
the power supply
has failed. 3. If the OVER SPEC LED on
lit, follow the actions in
“Light path diagnostics
LEDs” on page 187.
4. If the OVER SPEC LED on
not lit, check the error LEDs
on the system board and the
IMM2 error messages. Follow
steps in “Power problems”
on page 215 and “Solving
power problems” on page
226 until the problem is
solved.
On Off On The power supply Replace the power supply.
has failed.
On On On The power supply Replace the power supply.
has failed.

System pulse LEDs
The following LEDs are on the system board and monitor the system power-on
and power-off sequencing and boot progress (see “System-board LEDs” on page 34
for the location of these LEDs).
Table 22. System pulse LEDs
RTMM heartbeat Power-on and power-off 1. If the LED blinks at 1Hz, it is functioning
sequencing. properly and no action is necessary.
2. If the LED is not blinking, (trained
technician only) replace the system board.
IMM2 heartbeat IMM2 heartbeat boot process. The following steps describe the different
stages of the IMM2 heartbeat sequencing
process.
1. When this LED is blinking fast
(approximately 4Hz), this indicates, that the
IMM2 code is in the loading process.
2. When this LED goes off momentarily, this
indicates that the IMM2 code has loaded
completely.
3. When this LED goes off momentarily and
then starts blinking slowing (approximately
1Hz), this indicates that IMM2 is fully
operational. You can now press the
power-control button to power-on the
server.
4. If this LED does not blink within 30
seconds of connecting a power source to
the server, (trained technician only) replace
the system board.
PCI riser-card LEDs

The following illustration shows the location of the PCI riser-card LEDs.
UpperPCI slot error LED
Center PCI slot error LED
Lower PCI slot error LED
Figure 145. PCI riser-card LEDs

Event logs
Error codes and messages 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 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 154). For
more information about POST error codes, see Appendix B, “UEFI/POST
diagnostic codes,” on page 827.
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 373.
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.
v Integrated management module II (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 165. 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 373.
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” on page 197).
For more information about DSA and DSA messages, see “IBM Dynamic System
Analysis” on page 199 and Appendix C, “DSA diagnostic test results,” on page
845.

Viewing event logs through the Setup utility
To view the POST event log or system-event log, complete the following steps:
Procedure
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 Viewers.
v To view the system-event log, select System Event Log.
Viewing 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. 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.
You can view the IMM event log through the Event Log link in the integrated
management module II (IMM2) web interface. For more information, see “Logging
on to the web interface” on page 165.
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 23. 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 v Run DSA Portable to view the diagnostic
controlled network ports). 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).

Table 23. Methods for viewing event logs (continued)
Condition Action
The server is not hung and is not connected v Run DSA Portable to view the diagnostic
to a network (using an operating system event log (requires IPMI driver) or create
controlled network ports). 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 the integrated In a web browser, type the IP address for
management module II (IMM2) is connected the IMM2 and go to the Event Log page. For
to a network. more information, see “Obtaining the IMM
host name” on page 164 and “Logging on to
the web interface” on page 165.
The server is hung, and no communication v If DSA Preboot is installed, restart the
can be made with the IMM. server and press F2 to start DSA Preboot
and view the event logs (see “Running the
DSA Preboot diagnostic programs” on
page 201 for more information).
v Alternatively, you can restart the server
and press F1 to start the Setup utility and
view the POST event log or system-event
log. For more information, see “Viewing
event logs through the Setup utility” on
page 197.
Clearing the event logs

Use this information to clear the event logs.
About this task
To clear the event logs, complete the following steps.
Note: The POST error log is automatically cleared each time the server is restarted.
Procedure
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. To clear the IMM system-event log, select System Event Logs > 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 diagnostic codes,” on page 827 for more information.
If POST detects a problem, an error message is sent to the POST event log, see
“Event logs” on page 196 for more information.
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 Hardware inventory, including PCI and USB information
v Installed applications and hot fixes (available in DSA Portable only)
v Kernel modules (available in DSA Portable only)
v Light path diagnostics status
v Network interfaces and settings
v Performance data and details about processes that are running
v RAID 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 Appendix C, “DSA diagnostic test results,” on
page 845.
If you cannot find a problem by using DSA, see “Solving undetermined problems”
on page 229 for information about testing the server.
Note: 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 unable to restart 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/
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:
– Emulex 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 able to restart the server or if you need comprehensive diagnostics,
use DSA Preboot.
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.
About this task
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, complete the following steps:
Procedure
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. The loading process may take up to 10
minutes.
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. Type gui to display the graphical user interface, or type cmd to display the
DSA interactive menu.
6. Follow the instructions on the screen to select the diagnostic test to run.
Results
If the diagnostic programs do not detect any hardware errors but the problem
remains during normal server operation, a software error might be the cause. If
you suspect a software problem, see the information that comes with your
software.
A single problem might cause more than one error message. When this happens,
correct the cause of the first error message. The other error messages usually will
not occur the next time you run the diagnostic programs.
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,
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 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.
Procedure
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 completed tests to view the results.
Results
You can also send the DSA error log to IBM support to aid in diagnosing the
server problems.
Automated service request (call home)

IBM provides tools that can automatically collect and send data or call IBM
Support when an error is detected. These tools can help IBM Support speed up the
process of diagnosing problems. The following sections provide information about
the call home tools.

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 diagnostic codes,” on page 827, Appendix A,

“Integrated management module II (IMM2) error messages,” on page 373, and
Appendix C, “DSA diagnostic test results,” on page 845 for more information.
Troubleshooting by symptom
Use the troubleshooting tables to find solutions to problems that have identifiable
symptoms.
About this task
If you cannot find a solution to the problem in these tables, see Appendix C, “DSA
diagnostic test results,” on page 845 for information about testing the server and
“Running the DSA Preboot diagnostic programs” on page 201 for additional
information about running DSA Preboot program. For additional information to
help you solve problems, see “Start here” on page 177.
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:
Procedure
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 184).
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 845).
4. Reinstall the new software or new device.
Results

CD/DVD drive problems
symptoms.
solved.
v If an action step is preceded by “(Trained technician only),” that step must be performed only by a Trained
technician.
v Go to the IBM support website at http://www.ibm.com/supportportal/ to check for technical information, hints,
tips, and new device drivers or to submit a request for information.
Symptom Action
The optional DVD drive is not 1. Make sure that:
recognized.
v The SATA connector to which the 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 DVD drive.
2. Run the DVD drive diagnostic programs.
3. Reseat the following components:
a. DVD drive
b. 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 technician only) Replace the system board.
A CD or DVD is not working 1. Clean the CD or DVD.
correctly.
2. Replace the CD or DVD with new CD or DVD media.
3. Run the DVD drive diagnostic programs.
4. Reseat the DVD drive.
5. Replace the DVD drive.
The DVD drive tray is not 1. Make sure that the server is turned on.
working.
2. Insert the end of a straightened paper clip into the manual tray-release
opening.
3. Reseat the DVD drive.
4. Replace the DVD drive.

General problems
symptoms.
solved.
v If an action step is preceded by “(Trained technician only),” that step must be performed only by a trained
technician.
Symptom Action
A cover latch is broken, an LED If the part is a CRU, replace it. If the part is a microprocessor or the system board,
is not working, or a similar the part must be replaced by a trained technician.
problem has occurred.
The server is hung while the 1. See “Nx-boot failure” on page 234 for more information.
screen is on. Cannot start the
2. See “Recovering the server firmware (UEFI update failure)” on page 231 for
Setup utility by pressing F1.
more information.
Hard disk drive problems

symptoms.
solved.
technician.
Symptom Action
A hard disk drive has failed, Replace the failed hard disk drive (see “Removing a hot-swap hard disk drive” on
and the associated yellow hard page 270 and “Replacing a hot-swap hard disk drive” on page 271).
disk drive status LED is lit.

solved.
technician.
Symptom Action
A newly installed hard disk 1. Make sure that the installed hard disk drive or ServeRAID adapter is
drive is not recognized. supported. For a list of supported optional devices, see http://www.ibm.com/
2. Observe the associated yellow hard disk drive status LED. If the LED is lit, it
indicates a drive fault.
3. 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.
4. 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
diagnostics program 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 5).
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 5. If the
activity of the LEDs changes, return to step 2.
5. 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.
6. Reseat the backplane power cable and repeat steps 2 through 4.
7. Reseat the backplane signal cable and repeat steps 2 through 4.
8. Suspect the backplane signal cable or the backplane:
v If the server has eight hot-swap bays:
a. Replace the affected backplane signal cable.
b. Replace the affected backplane.
9. See “Problem determination tips” on page 230.
Multiple hard disk drives fail. Make sure that the hard disk drive, SAS/SATA adapter, and server device drivers
and firmware are at the latest level.
Important: Some cluster solutions require specific code levels or coordinated code
updates. If the device is part of a cluster solution, verify that the latest level of
code is supported for the cluster solution before you update the code.
Multiple hard disk drives are 1. Review the storage subsystem logs for indications of problems within the
offline. storage subsystem, such as backplane or cable problems.
A replacement hard disk drive 1. Make sure that the hard disk drive is recognized by the adapter (the green
does not rebuild. hard disk drive activity LED is flashing).
2. Review the SAS/SATA adapter documentation to determine the correct
configuration parameters and settings.

solved.
technician.
Symptom Action
A green hard disk drive activity If the green hard disk drive activity LED does not flash when the drive is in use,
LED does not accurately run the DSA Preboot diagnostic programs to collect error logs (see “Running the
represent the actual state of the DSA Preboot diagnostic programs” on page 201).
associated drive. v If there is a hard disk drive error log, replace the affected hard disk drive.
v If there is no disk drive error log error log, replace the affected backplane.
An yellow hard disk drive 1. If the yellow hard disk drive LED and the RAID adapter software do not
status 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.
Hypervisor problems
symptoms.
solved.
technician.
Symptom Action
If an optional embedded 1. Make sure that the optional embedded hypervisor flash device is selected on
hypervisor flash device is not the boot manager <F12> Select Boot Device at startup.
listed in the expected boot
2. Make sure that the embedded hypervisor flash device is seated in the
order, does not appear in the
connector correctly (see “Removing a USB embedded hypervisor flash device”
list of boot devices, or a similar
on page 343 and “Replacing a USB embedded hypervisor flash device” on
problem has occurred.
page 344).
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.

Intermittent problems
symptoms.
solved.
technician.
Symptom Action
A problem occurs only 1. Make sure that:
occasionally and is difficult to v All cables and cords are connected securely to the rear of the server and
diagnose. 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 system-error log or IMM event logs (see “Event logs” on page 196).
The server resets (restarts) 1. If the reset occurs during POST and the POST watchdog timer is enabled (click
occasionally. System Settings > Recovery > System Recovery > 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
diagnostic codes,” on page 827 and Appendix C, “DSA diagnostic test results,”
on page 845.
2. If neither condition applies, check the system-error log or IMM system-event
log (see “Event logs” on page 196).
Keyboard, mouse, or USB-device problems

symptoms.
solved.
technician.
Symptom Action
All or some keys on the 1. Make sure that:
keyboard do not work. 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. 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.
4. Replace the keyboard.

solved.
technician.
Symptom Action
The mouse or USB-device does 1. Make sure that:
not work.
v The mouse or USB device cable is securely connected to the server.
v The mouse or USB device drivers are installed correctly.
v The server and the monitor are turned on.
v The mouse option is enabled in the Setup utility.
2. If you are using a USB mouse or USB device and it is connected to a USB hub,
disconnect the mouse or USB device from the hub and connect it directly to
the server.
3. Replace the mouse or USB-device.
Memory problems
symptoms.

solved.
technician.
Symptom Action
The amount of system memory Note: Each time you install or remove a DIMM, you must disconnect the server
that is displayed is less than the from the power source; then, wait 10 seconds before restarting the server.
amount of installed physical 1. Make sure that:
memory.
v No error LEDs are lit on the operator information panel.
v No DIMM error LEDs are lit on the system board.
v Memory mirrored channel does not account for the discrepancy.
v The memory modules are seated correctly.
v You have installed the correct type of memory.
v If you changed the memory, you updated the memory configuration in the
Setup utility.
v All banks of memory are enabled. The server might have automatically
disabled a memory bank when it detected a problem, or a memory bank
might have been manually disabled.
v There is no memory mismatch when the server is at the minimum memory
configuration.
2. Reseat the DIMMs, and then restart the server.
3. Check the POST error 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, reseat the DIMM; then, run
the Setup utility and enable the DIMM.
4. Check that all DIMMs are initialized in the Setup utility; then, run memory
diagnostics (see “Running the DSA Preboot diagnostic programs” on page 201).
5. Reverse the DIMMs between the channels (of the same microprocessor), and
then restart the server. If the problem is related to a DIMM, replace the failing
DIMM.
6. Re-enable all DIMMs using the Setup utility, and then restart the server.
7. (Trained technician only) Install the failing DIMM into a DIMM connector for
microprocessor 2 (if installed) to verify that the problem is not the
microprocessor or the DIMM connector.

solved.
technician.
Symptom Action
Multiple DIMMs in a channel Note: Each time you install or remove a DIMM, you must disconnect the server
are identified as failing. from the power source; then, wait 10 seconds before restarting the server.
1. Reseat the DIMMs; then, restart the server.
2. Remove the highest-numbered DIMM of those that are identified and replace it
with an identical known good DIMM; then, restart the server. Repeat as
necessary. If the failures continue after all identified DIMMs are replaced, go to
step 4.
3. Return the removed DIMMs, one at a time, to their original connectors,
restarting the server after each DIMM, until a DIMM fails. Replace each failing
DIMM with an identical known good DIMM, restarting the server after each
DIMM replacement. Repeat step 3 until you have tested all removed DIMMs.
4. Replace the highest-numbered DIMM of those identified; then, restart the
server. Repeat as necessary.
5. Reverse the DIMMs between the channels (of the same microprocessor), and
then restart the server. If the problem is related to a DIMM, replace the failing
DIMM.
6. (Trained technician only) Install the failing DIMM into a DIMM connector for
microprocessor 2 (if installed) to verify that the problem is not the
microprocessor or the DIMM connector.
Microprocessor problems
symptoms.
solved.
technician.
Symptom Action
The server goes directly to the 1. Correct any errors that are indicated by the light path diagnostics LEDs (see
POST Event Viewer when it is “Light path diagnostics” on page 184).
turned on.
2. Make sure that the server supports all the microprocessors and that the
microprocessors match in speed and cache size. To view the microprocessor
information, run the Setup utility and select System Information > System
Summary > Processor Details.
3. (Trained technician only) Make sure that microprocessor 1 is seated correctly.
4. (Trained technician only) Remove microprocessor 2 and restart the server.
5. Replace the following components one at a time, in the order shown, restarting
the server each time:
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.
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. The IMM2 remote presence function is disabled if you install an optional video
adapter. To use the IMM2 remote presence function, remove the optional video
adapter.
3. If the server installed with the graphical adapters while turning on the server,
the IBM logo displays on the screen after approximately 3 minutes. This is
normal operation while the system loads.
4. Make sure that:
v The server is turned on. If there is no power to the server, see “Power
v The monitor cables are connected correctly.
v The monitor is turned on and the brightness and contrast controls are
adjusted correctly.
5. Make sure that the correct server is controlling the monitor, if applicable.
6. Make sure that damaged server firmware is not affecting the video; see
“Updating the firmware” on page 149.
7. Observe the checkpoint LEDs on the system board; if the codes are changing,
go to step 6.
8. Replace the following components one at a time, in the order shown, restarting
the server each time:
a. Monitor
b. Video adapter (if one is installed)
c. (Trained technician only) System board.
9. See “Solving undetermined problems” on page 229.

solved.
technician.
Symptom Action
The monitor works when you 1. Make sure that:
turn on the server, but the
v The application program is not setting a display mode that is higher than
screen goes blank when you
the capability of the monitor.
start some application
programs. v You installed the necessary device drivers for the application.
2. Run video diagnostics (see “Running the DSA Preboot diagnostic programs”
on page 201).
v If the server passes the video diagnostics, the video is good; see “Solving
undetermined problems” on page 229.
v (Trained technician only) If the server fails the video diagnostics, replace the
system board.
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 149) with the correct language.
2. Reseat the monitor cable.
a. Monitor cable
c. Monitor
d. (Trained technician only) System board.

Network connection problems
symptoms.
solved.
technician.
Symptom Action
Unable to wake the server 1. If you are using the dual-port network adapter and the server is connected to
using the Wake on LAN the network using Ethernet 5 connector, check the system-error log or IMM2
feature. system event log (see “Event logs” on page 196), make sure:
a. Fan 3 is running in standby mode, if Emulex dual port 10GBase-T
embedded adapter is installed.
b. The room temperature is not too high (see “Server features and
specifications” on page 7).
c. The air vents are not blocked.
d. The air baffle is installed securely.
2. Reseat the dual-port network adapter (see “Removing the dual-port network
adapter” on page 318 and “Replacing the dual-port network adapter” on page
319).
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.
Log in failed by using LDAP 1. Make sure the license key is valid.
account with SSL enabled.
2. Generate a new license key and log in again.
Optional-device problems
symptoms.
solved.
technician.
Symptom Action
An IBM optional device that 1. Make sure that:
was just installed does not v The device is designed for the server (see http://www.ibm.com/systems/
work. 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.

solved.
technician.
Symptom Action
An IBM optional device that 1. Make sure that all of the cable connections for the device are secure.
worked previously does not
2. If the device comes with test instructions, use those instructions to test the
work now.
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.
Power problems
symptoms.

solved.
technician.
Symptom Action
The power-control button does 1. Make sure that the power-control button is working correctly:
not work, and the reset button
a. Disconnect the server power cords.
does not work (the server does
not start). b. Reconnect the power cords.
Note: The power-control button c. (Trained technician only) Reseat the operator information panel cable, and
will not function until then repeat steps 1a and 1b.
approximately 5 to 10 seconds v (Trained technician only) If the server starts, reseat the operator
after the server has been information panel. If the problem remains, replace the operator
connected to power. information panel.
v If the server does not start, bypass the power-control button by using the
force power-on jumper (see “System-board switches, jumpers, and
buttons” on page 32). If the server starts, reseat the operator information
panel. If the problem remains, replace the operator information panel.
2. Make sure that the reset button is working correctly:
a. Disconnect the server power cords.
b. Reconnect the power cords.
c. (Trained technician only) Reseat the operator information panel cable, and
then repeat steps 2a and 2b.
v (Trained technician only) If the server starts, replace the operator
information panel.
v If the server does not start, go to step 3.
3. Make sure that both power supplies installed in the server are of the same
type. Mixing different power supplies in the server will cause a system error
(the system-error LED on the front panel turns on and the PS and CONFIG
LEDs on the operator information panel are lit).
4. 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. Operator information panel connector
b. Power supplies
7. 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.
8. See “Power-supply LEDs” on page 191.
9. See “Solving undetermined problems” on page 229.

solved.
technician.
Symptom Action
The OVER SPEC LED on the 1. Disconnect the server power cords.
light path diagnostics panel is
2. (Trained technician only) remove microprocessor 1 if the Pwr rail A error has
lit, or the Pwr rail A error has
been recorded in the IMM event log.
been recorded in the IMM
event log. 3. (Trained technician only) replace the system board (see “Removing the system
board” on page 367 and “Replacing the system board” on page 370).
4. Reinstall the component; then, restarting the server. If the Pwr rail A error has
been recorded in the IMM event log again, the component that you just
reinstalled is defective. Replace the defective component.
v (Trained technician only) Microprocessor 1 (see “Removing a microprocessor
and heat sink” on page 351 and “Replacing a microprocessor and heat sink”
on page 356).
5. Replace the power supply if the OVER SPEC LED on the light path diagnostics
panel is still lit.
2. (Trained technician only) remove microprocessor 2 if Pwr rail B error has been
lit, or the Pwr rail B error has
recorded in the IMM event log.
event log. 3. Restart the server. If the Pwr rail B error has been recorded in the IMM event
log again, (trained technician only) replace the system board (see “Removing
the system board” on page 367 and “Replacing the system board” on page
370).
4. Reinstall the component; then, restarting the server. If the Pwr rail B error has
been recorded in the IMM event log again, the component that you just
reinstalled is defective. Replace the defective component.
v (Trained technician only) Microprocessor 2 (see “Removing a microprocessor
and heat sink” on page 351 and “Replacing a microprocessor and heat sink”
on page 356).
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if Pwr rail C error has been recorded in the
lit, or the Pwr rail C error has
IMM2 event log:
event log. v Optional adapter (if one is present) installed in PCI riser-card assembly 1
v PCI riser-card assembly 1
v Fan 1
v DIMMs 1 through 6
3. Restart the server. If the Pwr rail C error has been recorded in the IMM event
370).
4. Reinstall the components one at a time, in the order shown, restarting the
server each time. If the Pwr rail C error has been recorded in the IMM event
log again, the component that you just reinstalled is defective. Replace the
defective component.
v DIMMs 1 through 6 (see “Removing a memory module” on page 288 and
“Installing a memory module” on page 54).
v Fan 1
v PCI riser-card assembly 1 (see “Removing a PCI riser-card assembly” on
page 301 and “Replacing a PCI riser-card assembly” on page 302).
v Optional adapter (if one is present) installed in PCI riser-card assembly 1
(see “Removing an adapter” on page 304 and “Replacing an adapter” on
page 305).
5. Follow actions in “Solving power problems” on page 226, if the OVER SPEC
LED on the light path diagnostics panel is still lit.
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if the Pwr rail D error has been recorded in
lit, or the Pwr rail D error has
the IMM event log:
event log. v Optional PCI adapter power cable (if one is present)
v Fan 2
v DIMMs 7 through 12
3. Restart the server. If the Pwr rail D error has been recorded in the IMM event
370).
server each time. If the Pwr rail D error has been recorded in the IMM event
v Fan 2 (see “Removing a hot-swap fan” on page 336 and “Replacing a
v Optional PCI adapter power cable (if one is present)
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if the Pwr rail E error has been recorded in
lit, or the Pwr rail E error has
the IMM event log:
event log. v Optional DVD drive (if one is installed)
v Hard disk drives
3. Restart the server. If the Pwr rail E error has been recorded in the IMM event
370).
server each time. If the Pwr rail E error has been recorded in the IMM event
v Hard disk drives
v Optional DVD drive, if one is present (see “Removing a DVD drive” on
page 278 and “Replacing a DVD drive” on page 279).
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if the Pwr rail F error has been recorded in
lit, or the Pwr rail F error has
the IMM event log:
event log. v Optional adapter (if one is present) installed in PCI riser-card assembly 1
v Fan 4
3. Restart the server. If the Pwr rail F error has been recorded in the IMM event
370).
server each time. If the Pwr rail F error has been recorded in the IMM event
“Installing a memory module” on page 54)
hot-swap fan” on page 337)
page 305).
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if the Pwr rail G error has been recorded in
lit, or the Pwr rail G error has
the IMM event log:
event log. v Optional PCI adaptor power cable (if one is present)
v Fan 3
v Hard disk drives
v Hard disk drive backplane assembly
3. Restart the server. If the Pwr rail G error has been recorded in the IMM event
370).
server each time. If the Pwr rail G error has been recorded in the IMM event
v Hard disk drives
hot-swap fan” on page 337)
v Optional PCI adaptor power cable (if one is present) (see “Removing an
adapter” on page 304 and “Replacing an adapter” on page 305).
panel is still lit.

solved.
technician.
Symptom Action
2. Remove the following components if the Pwr rail H error has been recorded in
lit, or the Pwr rail H error has
the IMM event log:
event log. v Optional PCI adaptor power cable (if one is present)
3. Restart the server. If the Pwr rail H error has been recorded in the IMM event
370).
server each time. If the Pwr rail H error has been recorded in the IMM event
page 305).
v Optional PCI adaptor power cable (if one is present) (see “Removing an
adapter” on page 304 and “Replacing an adapter” on page 305).
panel is still lit.
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 power cord for 20 seconds; then, reconnect the 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 See “Solving undetermined problems” on page 229.
down, and the LEDs on the
operator information panel are
not lit.

Serial-device problems
symptoms.
solved.
technician.
Symptom Action
The number of serial ports that 1. Make sure that:
are identified by the operating v Each port is assigned a unique address in the Setup utility and none of the
system is less than the number serial ports is disabled.
of installed serial ports. 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 “System-board internal
connectors” on page 30).
a. Failing serial device
b. Serial cable
ServerGuide problems
symptoms.
solved.
technician.
Symptom Action
The ServerGuide Setup and 1. Make sure that the server supports the ServerGuide program and has a
Installation CD will not start. startable (bootable) CD or DVD drive.
2. If the startup (boot) sequence settings have been changed, make sure that the
CD or DVD drive is first in the startup sequence.
3. 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 1. Make sure that the hard disk drive is connected correctly.
Manager program cannot view
2. Make sure that the SAS/SATA hard disk drive cables are securely connected.
all installed drives, or the
operating system cannot be
installed.

solved.
technician.
Symptom Action
The operating-system Make more space available on the hard disk.
installation program
continuously loops.
The ServerGuide program will Make sure that the operating-system CD is supported by the ServerGuide
not start the operating-system program. For a list of supported operating-system versions, go to
CD. http://www.ibm.com/support/entry/portal/docdisplay?lndocid=SERV-GUIDE,
click the link for your ServerGuide version, and scroll down to the list of
supported Microsoft Windows operating systems.
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
available. is not present. Run the ServerGuide program and make sure that setup is
complete.
Software problems
solved.
technician.
Symptom Action
You suspect a software 1. To determine whether the problem is caused by the software, make sure that:
problem. 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
symptoms.
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 154 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.
Video problems
symptoms.
See “Monitor and video problems” on page 212.
Solving 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.
About this task
To diagnose a power problem, use the following general procedure:
Procedure
1. Turn off the server and disconnect all 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. Check the lit LEDs on the light path diagnostics panel (see “Light path
diagnostics LEDs” on page 187).
4. If the check log LED on the light path diagnostics panel is lit, check the IMM
event log for faulty Pwr rail and complete the following steps. Table 24 on page
227 identifies the components that are associated with each Pwr rail and the
order in which to troubleshoot the components.
a. Disconnect the cables and power cords to all internal and external devices
(see “Internal cable routing and connectors” on page 249). Leave the
power-supply cords connected.
b. For Pwr rail 1 error, complete the following steps:
1) (Trained technician only) Replace the system board.
2) (Trained technician only) Replace the microprocessor.

c. For other rail errors (Pwr rail 1 error, see step 4b on page 226), remove each
component that is associated with the faulty Pwr rail, one at a time, in the
sequence indicated in Table 24, restarting the server each time, until the
cause of the overcurrent condition is identified.
Table 24. Components associated with power rail errors
Pwr rail error in the IMM event log Components
Pwr rail A error v Microprocessor 1
Pwr rail B error v Microprocessor 2
Pwr rail C error v Optional adapter (if one is installed) in PCI
riser-card assembly 1
v Fan 1
v DIMMs 1 through 6
Pwr rail D error v Optional dual-port network adaptor
v Fan 2
Pwr rail E error v Optional DVD drive (if one is installed)
v Hard disk drives
Pwr rail F error v Optional adapter (if one is installed) in PCI
v Fan 4
Pwr rail G error v Optional PCI adaptor power cable (if one is
present)
v Fan 3
v Hard disk drives
Pwr rail H error v Optional PCI adaptor power cable (if one is
present)
v Optional adapter (if one is presented) installed in
PCI riser-card assembly 2
d. Replace the identified component.

5. Remove the adapters and disconnect the cables and power cords to all internal
and external devices until the server is at the minimum configuration that is
required for the server to start (see “Power-supply LEDs” on page 191 for the
minimum configuration).
6. Reconnect all ac power cords and turn on the server. If the server starts
successfully, reseat the adapters and devices one at a time until the problem is
isolated.
Results
If the server does not start from the minimum configuration, see “Power-supply
LEDs” on page 191 to replace the components in the minimum configuration one

at a time until the problem is isolated.
Solving 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.
About this task
Try the following procedures:
Procedure
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.
– 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.
v 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.
v 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.
v Check the LAN activity LED on the rear of the server. The LAN activity LED is
lit when data is active on the Ethernet network. If the LAN activity LED is off,
make sure that the hub and network are operating and that the correct device
drivers are installed.
v Check for operating-system-specific causes of the problem.
v Make sure that the device drivers on the client and server are using the same
protocol.
Results
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) did not diagnose the failure or if the server is
inoperative, use the information in this section.
About this task
If you suspect that a software problem is causing failures (continuous or

intermittent), see “Software problems” on page 225.
Corrupted data in CMOS memory or corrupted UEFI firmware can cause

undetermined problems. To reset the CMOS data, use the CMOS clear jumper (JP1)
to clear the CMOS memory and override the power-on password; see Table 4 on
page 32 for more information. If you suspect that the UEFI firmware is corrupted,
see “Recovering the server firmware (UEFI update failure)” on page 231.
If the power supplies are working correctly, complete the following steps:
Procedure
2. Make sure that the server is cabled correctly.
3. 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.
Results
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 name 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 146. ID label
v Machine type and model

v Microprocessor or hard disk drive upgrades
v Failure symptom
– Does the server fail the 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
v Software versions and levels

v Diagnostic program type and version level
v Configuration option settings
v Operating-system control-file setup
See Appendix D, “Getting help and technical assistance,” on page 981 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 the following way:
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 back up bank.
You must maintain a bootable UEFI firmware image in the back up bank. If the
server firmware in the primary bank becomes corrupted, you can either manually
boot the back up bank with the UEFI boot backup jumper (JP2), or in the case of
image corruption, this will occur automatically with the Automated Boot Recovery
function.
In-band manual recovery method

This section details the in-band manual recovery method.
About this task
To recover the server firmware and restore the server operation to the primary
bank, complete the following steps:
Procedure
2. Turn off the server, and disconnect all power cords and external cables.
4. Locate the UEFI boot backup jumper (JP2) on the system board.

UEFI boot backup
jumper(JP2)
CMOS clear
jumper (JP1)
System TPM physical

Figure 147. UEFI boot backup jumper (JP2) location
5. Move the UEFI boot backup jumper (JP2) from pins 1 and 2 to pins 2 and 3 to
enable the UEFI recovery mode.
6. Reinstall the server cover; then, reconnect all power cords.
7. Restart the server. The system begins the power-on self-test (POST).
8. Boot the server to an operating system that is supported by the firmware
update package that you downloaded.
9. Perform the firmware update by following the instructions that are in the
firmware update package readme file.
10. Turn off the server and disconnect all power cords and external cables, and
then remove the cover (see “Removing the cover” on page 39).
11. Move the UEFI boot backup jumper (JP2) from pins 2 and 3 back to the
primary position (pins 1 and 2).
12. Reinstall the cover (see “Replacing the cover” on page 260).
13. Reconnect the power cord and any cables that you removed.
14. Restart the server. The system begins the power-on self-test (POST). If this
does not recover the primary bank, continue with the following steps.
16. Reset the CMOS by removing the system battery (see “Removing the system
battery” on page 345).
17. Leave the system battery out of the server for approximately 5 to 15 minutes.
18. Reinstall the system battery (see “Replacing the system battery” on page 347).
21. Restart the server. The system begins the power-on self-test (POST).
22. If these recovery efforts fail, contact your IBM service representative for
support.
Results

In-band automated boot recovery method
This section details the in-band automated boot recovery method.
About this task
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.
Procedure
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.
Results
Out-of-band method
See the IMM2 documentation (Integrated Management Module II User's Guide) at
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5086346.
Automated boot recovery (ABR)

Use this information for Automated boot recovery (ABR).
About this task
While the server is starting, if the integrated management module II 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 231.
After you have recovered the firmware in the primary bank, complete the
following steps:
Procedure
2. When the prompt Press F3 to restore to primary is displayed, press F3 to
start the server from the primary bank.

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, in the Setup utility, click System Settings > Recovery > POST
Attempts > POST Attempts Limit. The available options are 3, 6, 9, and 255
(disable Nx-boot failure).

Chapter 5. Parts listing, System x3650 M4 Type 7915
The parts listing of System x3650 M4 Type 7915
The following replaceable components are available for the System x3650 M4 Type
7915 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 System x3650 M4 Type 7915
Replaceable components consist of consumable parts, structural parts, and field

replaceable units (FRUs):
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. See “Structural parts” on page 246 for the list of structural parts.
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 981.
Visit http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
for the latest options supporting plan.
The following illustration shows the major components in the server. The
illustrations in this document might differ slightly from your hardware. For a list
of structural parts, see “Structural parts” on page 246.

1
23
22
2
21
5
20
6
19
7
18
17
16
9
15
10
11
14
12
13
The following table lists the part numbers for the server replaceable components.

Table 25. Parts listing, Type 7915
CRU part CRU part
Index Description number (Tier 1) number (Tier 2)
2 PCI Express riser-card assembly (x 8) 94Y6704
2 PCI Express riser-card assembly (x 16) 94Y6707
2 PCI-X riser-card assembly 94Y6706
2 PCI Express riser-card assembly (x 16) 00D9530
3 Heat sink, 95 watt 94Y6618
Microprocessor installation tool 94Y9955
4 Microprocessor, Intel E5-2630L v2, 2.4 GHz, 15 MB, 60 W (6-core) 00Y2792
4 Microprocessor, Intel E5-2628L v2, 1.9 GHz, 20 MB, 70 W (8-core) 00AE525
4 Microprocessor, Intel E5-2648L v2, 1.90 GHz, 25 MB, 70 W (10-core) 00AE523
4 Microprocessor, Intel E5-2650L v2, 1.7 GHz, 25 MB, 70 W (10-core) 00Y2793
4 Microprocessor, Intel E5-2603 v2, 1.8 GHz, 10 MB, 80 W (4-core) 00Y2778
4 Microprocessor, Intel E5-2697 v2, 2.7 GHz, 30 MB, 1866 MHz, 130 W 00Y2777
(12-core)
4 Microprocessor, Intel Xeon E5-2690, 2.90 GHz, 20 MB, 135 W (8-core) 49Y8115
4 Microprocessor, Intel Xeon E5-2637 3.00 GHz, 5 MB, 80 W (2 core) 49Y8124
4 Microprocessor, Intel Xeon E5-2650L 1.80 GHz, 20 MB, 70 W (8 core) 81Y5160
Chapter 5. Parts listing, System x3650 M4 Type 7915 237

Table 25. Parts listing, Type 7915 (continued)
CRU part CRU part
5 Heat sink retention module 94Y7739
6 Memory, 2 GB single-rank 1.35 V, DDR3, 1333MHz, RDIMM 49Y1423
6 Memory, 4 GB single-rank 1.35 V, DDR3, 1600MHz, RDIMM 00D5026
6 Memory, 4 GB dual-rank 1.35 V, DDR3, 1333MHz, RDIMM 49Y1425
6 Memory, 4 GB dual-rank 1.35 V, DDR3, 1333MHz, UDIMM 49Y1422
6 Memory, 8 GB dual-rank 1.35 V, DDR3, 1600MHz, RDIMM 00D5046
6 Memory, 8 GB dual-rank 1.35 V, DDR3, 1600MHz, UDIMM 00D5018
6 Memory, 8 GB quad-rank 1.35 V, DDR3, 1333MHz, RDIMM 49Y1417
6 Memory, 16 GB dual-rank 1.35 V, DDR3, 1600MHz, RDIMM 46W0674
6 Memory, 16 GB dual-rank 1.5 V, DDR3, 1600MHz, RDIMM 00D4970
6 Memory, 16 GB dual-rank 1.5 V, DDR3, 1866MHz, RDIMM 46W0670
6 Memory, 16 GB 1.5V DDR3, 1333MHz LP HyperCloud DIMM 00D4966
6 Memory, 32 GB 1.35 V, DDR3, 1333MHz LP HyperCloud DIMM 46W0769
6 Memory, 32 GB 1.5V DDR3, 1066MHz LP HyperCloud DIMM 00D5006
6 Memory, 32 GB quad-rank, 1.5 V, DDR3, 1866MHz, LRDIMM 46W0763
7 System board (Server base assembly for use with Intel Xeon 00Y8457/
Processor E5-2600 series) 00Y8499
Type 7915 - A2x, B2x, C2x, C4x, D2x, F2x, 52x, G2x, H2x, J2x, L2x,
62x, E1Y, E2Y, E5Y, EAY, EBY,ECY, EDY, 32x, GSx, M2x

CRU part CRU part
7 System board (Server base assembly for use with Intel Xeon 00AM209
Processor E5-2600 V2 series)
Type 7915 - A3x, B3x, C3x, C5x, D3x, F3x, G3x, H3x, J3x, L3x, 23x,
33x, 43x, M3x, 73x, 83x, E6Y, E7Y, E8Y, E8Y, E9Y, EFY, EGY, EHY,
EJY, EKY, ELx, EOx, ERx, ESx, ETx, EUx, EVx, EWx, EPx, EQx
9 Power supply, 550 Watt, ac - Acbel 94Y8110
9 Power supply, 550 Watt - Emerson 94Y8112
9 Power supply, 750 Watt, ac 69Y5872
9 Power supply, 750 Watt, ac - Delta (This part is interchangeable with 94Y8116
part number 94Y8114)
9 Power supply, 750 Watt, ac - Emerson (This part is interchangeable 94Y8114
with part number 94Y8116)
9 Power supply, 750 Watt, dc - Emerson 69Y5742
9 Power supply, 900 Watt, ac - Delta (This part is interchangeable with 94Y8120
part number 94Y8118)
9 Power supply, 900 Watt, ac - Emerson (This part is interchangeable 94Y8118
with part number 94Y8120)
10 DVD drive, SATA 44W3254
10 DVD drive, SATA 44W3256
11 Advanced operator information panel kit 00AM393
11 Operator information panel assembly 90Y5821
Filler, 3.5-inch hard disk drive bay for hot-swap 69Y5364
Filler, 3.5-inch hard disk drive bay for simple-swap 69Y5368
14 Filler, hard disk drive bay for simple-swap 49Y5360
15 Tape kit (optional) contains: 40K6449
v Assembly, mechanical (1)
v Clamp, round cable (1)
v Filler, tape kit 3.5 inch (1)
v Screws, M3x6 MPC (4)
16 8 pac 2.5-inch hard disk drive backplane (For HDD 1 - 8) 46W9187
Plus 8 pac 2.5-inch hard disk drive backplane with SAS Expander 46W8418
Adapter attached to it (For HDD 9 - 16)
17 6 pac 3.5-inch hard disk drive backplane 90Y5091
20 Fan cage 00AM212
21 Fan 94Y6620
Battery, ServeRAID-M5100 Series 81Y4491
Hard disk drive, 200 GB SATA 43W7721
Hard disk drive, 200 GB SSD 43W7745
Hard disk drive, 300 GB SAS 81Y9671
Hard disk drive, 2.5-inch hot-swap, 146 GB, 15 K 90Y8927
Hard disk drive, 2.5-inch hot-swap, 146 GB, 15 K, SED 90Y8945
Hard disk drive, 2.5-inch hot-swap, 250 GB, 7.2 K 81Y9723

CRU part CRU part
Hard disk drive, 2.5-inch hot-swap, 300 GB, 10 K, SED 90Y8914
Hard disk drive, 2.5-inch hot-swap, 600 GB, 10 K SED 90Y8909
Hard disk drive, 2.5-inch hot-swap, 900 GB, 10 K SED 81Y9663
Hard disk drive, 2.5-inch hot-swap, 1 TB, 7.2 K 81Y9691
Hard disk drive, 2.5-inch, hot-swap, 1 TB, 7.2K SAS SAP 90Y8866
Hard disk drive, 3.5-inch hot-swap, 300 GB, 15K, SAS 49Y6093
Hard disk drive, 3.5-inch hot-swap, 500 GB, 7.2 K, NL SATA 81Y9787
Hard disk drive, 3.5-inch hot-swap, 2 TB, 7.2 K, NL SATA 81Y9795
Hard disk drive, 3.5-inch hot-swap, 4 TB, 7.2K, NL SATA 49Y6003
Hard disk drive, 3.5-inch simple-swap, 500 GB, 7.2 K 81Y9803
Hard disk drive, 3.5-inch simple-swap, 1 TB, 7.2 K 81Y9807
Hard disk drive, 3.5-inch simple-swap, 4 TB, 7.2K NL SATA 49Y6013
Solid state drive, 200 GB 40K6897
Solid state drive, 50 GB 43W7729
Solid state drive, 1.8-inch, SATA, 64 GB 49Y5835
Solid state drive, 1.8-inch, SATA, 100 GB 00W1121
Solid state drive, 1.8-inch, SATA, 120 GB 00AJ336

CRU part CRU part
Solid state drive, 2.5-inch simple-swap, SATA, 120 GB 00AJ376
Solid state drive, 2.5-inch simple-swap, SATA, 128 GB 90Y8669
Solid state drive, 2.5-inch simple-swap, SATA, 256 GB 90Y8664
Solid state drive, 2.5-inch hot-swap, SATA, 64 GB 49Y5840
Solid state drive, 2.5-inch hot-swap, SATA, 100 GB 00W1126
Solid state drive, 2.5-inch hot-swap, SATA, 100 GB 00W1131
Solid state drive, 2.5-inch hot-swap, SATA, 120 GB 00AJ356
Solid state drive, 2.5-inch hot-swap, SAS, 200 GB 49Y6130
Solid state drive backpanel cage, 1.8-inch 59Y6222
HBA 4 GB FC PCI-e single port adapter 00Y5626
HBA 4 GB FC PCI-e dual port adapter 00Y5627
NetXtreme II 1000 Express Ethernet adapter 39Y6070
PRO 1000 PF server adapter 42C1752
QLogic 10GB CNA 00Y3274
QLogic 10Gb dual port CNA 42C1802
Qlogic 10 GB SFP+ SR optical transceiver 42C1816
Qlogic 8200 dual port 10GbE SFP+ VFA 90Y4605
Qlogic dual-port 10GbE SFP+ Embedded VFA 90Y5099
Brocade 10GB SFP+ SR optical transceiver 42C1819
HBA 10 GB adapter 42C1822
Emulex dual port 10GbE SFP+ Embedded VFA IIIr 00Y7731
Emulex 8 GB PCIe single port adapter 42D0491
Emulex 8 GB PCIe dual port adapter 42D0500
Qlogic 8 GB single port adapter 00Y5628
HBA 8 GB dual port adapter 00Y5629
Video adapter, NVIDIA Quadro 600 43V5931
Video adapter, NVIDIA Quadro K600 90Y2383

CRU part CRU part
Video adapter, NVIDIA Quadro 2000 43V5939
Video adapter, NVIDIA Tesla K20c (Actively Cooled) 90Y2391
Video adapter, NVIDIA Quadro 4000 PCI Express x 16 90Y2330
Video adapter, NVIDIA Quadro 6000 PCI Express x 16 43V5921
FC 4 GB PCIe single port adapter 43W7510
FC 4 GB PCIe dual port adapter 43W7512
6 Gb SAS HBA 46C8935
N2215 SAS/SATA HBA 47C8676
IBM 6 Gb Performance Optimized HBA 46C8937
300 GB High IOPS MLC Modular adapter 90Y4362
300 GB High IOPS SLC Modular Adapter 90Y4374
365 GB High IOPS MLC Mono adapter 46C9079
785 GB High IOPS MLC Mono adapter 46C9082
10 GB SFP+ SR optical transceiver 46C9297
6 Gb SSD HBA 46M0913
Brocade 8 GB single port adapter 46M6061
Brocade 9 GB dual port adapter 46M6062
10GbE SW SFP+ transceiver 46W4236
Solarflare SFN5162F MR dual-port 10GbE SFP+ Adapter 47C9955
Solarflare SFN6122F LL dual-port 10GbE SFP+ Adapter 47C9963
Solarflare SFN7122F 2x10GbE SFP+ Flareon Ultra 47C9980
Dual port adapter 94Y5166
Quad port adapter 94Y5167
Broadcom NetXtreme II 10 GB dual port BaseT adapter 49Y7912
NetXtreme II 1000 Express dual port Ethernet adapter 49Y7947
NetXtreme II 1000 Express quad port Ethernet adapter 49Y7949
X520-DA2 10 GB Express dual port SFP+ adapter 49Y7962
X520 dual port 10GbE SFP+ embedded adapter 49Y7982
Brocade HBA 4 GB FC single port 59Y1992
Brocade HBA 4 GB FC dual port 59Y1998
HBA 6 GB adapter SAS 68Y7354
IBM LLM-SM Dual Port 10Gbe SFP+ Adaptor 00D9502
Emulex 16Gb FC Single-port HBA 81Y1658
Emulex 16Gb FC Dual-port HBA 81Y1665
Brocade 16Gb FC Single-port HBA 81Y1671

CRU part CRU part
Brocade 16Gb FC Dual-port HBA 81Y1678
6 GB performance optimized HBA 90Y4356
Emulex dual port 10GbE SFP+ Embedded VFA III adapter 90Y5100
Emulex 10GbE virtual fabric adapter III 95Y3766
Emulex dual-port 10 GBase-T embedded adapter 90Y5101
Dual-port FDR embedded adapter 00J6248
Mellanox ConnectX-3 VPI single-port QSFP FDR14 40GbE HCA 00W0039
Mellanox ConnectX-3 10 GbE adapter 00D9692
Mellanox ConnectX-3 dual-port QDR/FDR10 mezz card 90Y4956
Mellanox ConnectX-3 EN dual-port QSFP+ 40GbE adapter 95Y3461
Adapter, DVI to VGA adapter 25R9043
ServeRAID-M1015 46C8933
ServeRAID-M1015 SAS/SATA adapter 46M0861
ServeRAID-B5015 SSD adapter 46M0970
ServeRAID M5120 SAS/SATA adapter 00AE811
ServeRAID M5210 SAS/SATA adapter 46C9111
ServeRAID M5100 series 512 MB cache (RAID 5 upgrade) 81Y4485
ServeRAID M5100 series 512 MB flash (RAID 5 upgrade) 46C9027
ServeRAID M5100 series 1 GB flash (RAID 5 upgrade) 46C9029
ServeRAID M5200 Series 1GB cahe (RAID 5 Upgrade) 47C8657
ServeRAID M5200 Series 1GB flash (RAID 5 Upgrade) 47C8661
ServeRAID M5200 Series 2GB flash (RAID 5 Upgrade) 47C8665
ServeRAID M5110 SAS/SATA adapter 00AE807
Battery, 3.0 volt 33F8354
Thermal grease kit 41Y9292
Alcohol wipes 59P4739
Battery, ServeRAID 81Y4579
USB module kit 94Y6629
Power paddle card 69Y5787
Power adapter 44E8879
Tape, 160 GB cartridge 46C5393
Cord, power cord 39M5377
Cable, RS 232 to USB 3m 00Y8490
Cable, FDR 3M QSFP 90Y3473
Cable, flash power module cable, 925 mm (for ServRAID M5200 46C9793
Series Flash)
Cable, K20c power 00AM375

CRU part CRU part
Cable, 24-inch SATA 25R5635
Cable, SAS Y-cable 44E8878
Cable, SAS Y-cable 49Y9901
Cable, USB 44E8883
Cable, USB 1 m 44E8893
Cable, USB 46M6475
Cable, USB 46M6477
Cable, USB 81Y3643
Cable, mini-SAS, 820 mm (for 12Gb RAID) 00Y8433
Cable, mini-SAS HD, 925 mm (for 12Gb RAID) 00Y7674
Cable, SAS 610 mm 00D3276
Cable, SAS 69Y2281
Cable, SAS 820 mm 81Y6674
Cable, SATA slimline 81Y6774
Cable, 2.5-inch HDD I2C 46W8469
Cable, Spec power assembly 00D3334
Cable, USB 81Y6770
Cable, 3.5-inch HDD power 81Y6771
Cable, 3.5-inch HDD backplane 81Y6773
Cable, 3.5-inch simple-swap panel 81Y6776
Cable, 2.5-inch HDD power 81Y6772
Cable, 2.5-inch HDD I2C 00D3049
Cable, 3-4 I2C 00D3910
Cable, power 00D3911
Cable, Q6000 power R2 00D4010
Cable, mini SAS 00D4012
Cable assembly, 2.5-inch HDD simple-swap 00D4016
Cable, 1.8-inch SSD hot-swap power 00D4021
Cable, Q6000 power R1 00D9507
Cable, VGA 81Y6775
Cable, 2 x 3 VGA 900 mm 90Y5906
Cable, operation panel 90Y4768
Cable, 1 foot USB Cable 44E8894
Cable, 3M external USB 44E8891
Cable, USB conversion 39M2909
Cable, USB 3.0 46C2598
Cable, USB A-B RDX 69Y5335
Cable, USB A-B DDS 94Y6675
Cable, mini SAS 1 m 39R6530

CRU part CRU part
Cable, mini SAS 3 m 39R6532
Cable, serial conversion 46M4027
Cable, virtual media Gen 3 00AK113
Cable, power graphics 49Y4402
Cable, tape power 81Y6789
Cable, 130-155 Searay 90Y4661
Cable, iBBU09 remote 90Y7309
Cable, supercap 90Y7310
Drive, 5.25-inch, 36 GB, USB 99Y3868
Drive, 5.25-inch, 80 GB, USB 99Y3870
Internal RDX USB 3.0 drive dock 46C2346
External RDX USB 3.0 drive dock 46C2347
External RDX power adapter 81Y8905
Label, service for 3.5-inch hard disk drive model 94Y6720
Label, service for 2.5-inch hard disk drive model 94Y6722
Label, chassis 94Y6721
Half high LTO Gen 3 SAS tape drive 46X5663
Half high LTO Gen 6 SAS tape drive 35P1049
USB optical wheel mouse 39Y9875
Keyboard, UltraNav USB 40K9400
Keyboard, USB 42C0060
Blank USB memory key for VMWare ESXi downloads 42D0545
Supercap pack 47C8696
Supercap kit 00Y8384

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.
The following structural parts are available for purchase from the retail store.
Table 26. Structural parts, Type 7915
Index Description Part number
3.5-inch top cover 94Y6616
1 2.5-inch top cover 94Y6622
8 Power supply bay filler 94Y7610
Bezel, 6 hard disk drive with tape drive 94Y6613
12 Bezel, 16 hard disk drive with tape drive 94Y6623
13 Filler, tape drive bay 41Y8739
18 Remote battery tray 94Y6615
19 Remote RAID battery tray 94Y7609
22 Airflow baffle 94Y6624
23 Baffle 00D9458
Filler, DVD blank 94Y6718
Filler, EMC 44T2248
Filler, fan blank 94Y6736
EIA set kit 49Y5356
4-drive filler panel, hot-swap 49Y5359
3.5-inch mechanical chassis 94Y6617
2.5-inch mechanical chassis 94Y6628
2.5-inch bare chassis 00J6531
3.5-inch bare chassis 00J6532
Safety cover 94Y6619
Slide rail kit, Gen-III 94Y6625
Slide rail kit, universal 94Y6719
CMA kit, Gen-III 94Y6626
CMA kit, Gen-III 2U 94Y6627
CMA kit, 2U/4U 68Y7213
CMA kit 49Y4817
Miscellaneous parts kit 94Y6746
Tape MT bracket 41Y7711
To order a structural part, complete the following steps:
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.
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.
IBM power cords 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

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
39M5081 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
39M5219 Korea (Democratic People’s Republic of), Korea (Republic of)
39M5199 Japan
39M5068 Argentina, Paraguay, Uruguay
39M5226 India
39M5240 Brazil

Chapter 6. Removing and replacing components
Use this information to remove and replace the server components.
The types of replaceable components are:

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.
See Chapter 5, “Parts listing, System x3650 M4 Type 7915,” on page 235 to
determine whether a component is a structural part, Tier 1 CRU, or Tier 2 CRU.
For information about the terms of the warranty, 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 981.
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.
Internal cable routing and connectors

This section provides information about routing the cables when you install some
components in the server.
The following notes describe additional information you must consider when you
install or remove the cables:
v To remove the cables, slightly press the cables toward the chassis; then, pull to
remove the cables from the connectors on the system board. Pulling the cable
out of the connector by excessive force might cause damage to the cable or
connector.
v To connect the cables on the system board, press evenly on the cables. Pressing
on one side of the cable might cause damage to the cable or connector.

General cable routing connections
Cabling DVD drive
The internal routing and connectors for the DVD drive.
Notes:
1. To disconnect the optional optical drive cable, you must first press the
connector release tab, and then disconnect the cable from the connector on the
system board. Do not disconnect the cable by using excessive force.
2. Follow the optical drive cable routing as the illustration shows. Make sure that
the cable is not pinched and does not cover any connectors or obstruct any
components on the system board.
Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch
Figure 148. DVD drive cable connection

Cabling front USB and video connector
The internal routing and connectors for the front USB and video cables.
install or remove the front USB and video cables:
v To remove the front USB and video cables, slightly press the cables toward the
chassis; then, pull to remove the cables from the connectors on the system board.
Pulling the cable out of the connector by excessive force might cause damage to
the cable or connector.
v To connect the front USB and video cables on the system board, press evenly on
the cables. Pressing on one side of the cable might cause damage to the cable or
connector.
USB cable Video cable
Figure 149. Front USB and video cables connection
Chapter 6. Removing and replacing components 251

Cabling operator information panel
The internal routing and connectors for the operator information panel.
install or remove the operator information panel cable:
v You may remove the optional optical drive cable to obtain more room before
you install or remove the operator information panel cable.
v To remove the operator information panel cable, slightly press the cable toward
the fan cage; then, pull to remove the cable from the connector on the system
board. Pulling the cable out of the connector by excessive force might cause
damage to the cable or connector.
v To connect the operator information panel cable on the system board, press
evenly on the cable. Pressing on one side of the cable might cause damage to the
cable or connector.
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.
Operator panel
cable
Figure 150. Operator information panel cable connection

Cabling VGA power connector
The internal routing and connectors for the front USB and video cables.
The following illustration shows the internal routing and connectors for the video
graphic adapter (VGA) power cables:
Video graphic
adapters
VGA power
connector 2
VGA power
cables
VGA power
connector 1
Figure 151. VGA power cables connection

2.5-inch hard disk drive cable connection
8-drive-capable model
The following illustrations show the cabling information for the model of
8x2.5-inch hot-swap drive bays.
The following illustration shows the cabling information for the configuration cable
in the server:
Configuration cable
The following illustration shows the cabling information for the power cable in the
server:
SAS/SATA
backplane
power cable
The following illustration shows the cabling information for the hardware RAID
cable in the server:
Notes:
1. To connect the SAS signal cables, make sure that you first connect the signal
cable, and then the power cable and configuration cable.
2. To disconnect the SAS signal cables, make sure that you first disconnect the
power cable, and then the signal cable and configuration cable.

Port 4-7
Port 0-3
Port 0-3
16-drive-capable model
The following illustrations show the cabling information for the 16x2.5-inch
hot-swap drives model.
in the server:
Configuration cable
The following illustrations show the cabling information for the power cable in the
server:

SAS/SATA
backplane
power cable
Port 8-15
Port 0-7
SAS signal cables

3.5-inch hard disk drive cable connection
The following illustrations show the cabling information for the 3.5-inch drives
model:
in the server:
Configuration cable
The following illustrations show the cabling information for the power cable in the
server:
SAS/SATA
backplane
power cable

Port 4-5
Port 0-3
Port 0-3
Removing and replacing server components

This section provides information for removing and replacing components in the
server.
Removing and replacing structural parts

Replacement of structural parts is your responsibility. If IBM installs a structural
part at your request, you will be charged for the installation.

Removing the cover
Use this information to remove the cover.
About this task
To remove the server cover, complete the following steps:
Procedure
3. If the server has been installed in a rack, slide the server out from the rack
enclosure.
Cover-release
latch
Figure 152. Cover removal
4. Pull up firmly on the blue latch on the top (in the center of the front of the
server) of the cover and slide the cover toward the rear of the server until the
cover has disengaged from the chassis.
5. Lift the server cover off the server and set it aside.
Attention: For proper cooling and airflow, replace the server cover before you
turn on the server.
Results

Replacing the cover
Use this information to replace the server cover.
About this task
To replace the server cover, complete the following steps:
Procedure
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.
Important: Before you slide the cover forward, make sure that all the tabs on
the front, rear, and side of the cover engage the chassis correctly. If all the tabs
do not engage the chassis correctly, it will be very difficult to remove the cover
later.
2. Position the cover on top of the server.
3. Slide the cover toward the front of the server.
4. Make sure that the cover correctly engages all the inset tabs on the server.
5. Press down the blue latch on the top of the cover.
Cover-release
latch
Figure 153. Cover installation
6. Slide the server all the way into the rack until it latches.
7. Reconnect the external cables and power cords.

Removing the air baffle
When you work with some optional devices, you must first remove the air baffle
to access certain components or connectors on the system board. The following
illustration shows how to remove the air baffle.
About this task
PCI riser-card
assembly 2
PCI riser-card
assembly 1
Air baffle
Figure 154. Air baffle removal
To remove the air baffle, complete the following steps:
Procedure
4. Remove PCI riser-card assemblies, if needed (see “Removing a PCI riser-card
5. Place your fingers under the front and back of the top of the air baffle; then, lift
the air baffle out of the server.

Replacing the air baffle

Use this information to replace the air baffle.
About this task
To replace the air baffle, complete the following steps:
Procedure
4. Align the air baffle pins with the baffle pin holes on both sides of the chassis;
then, lower the air baffle into the server. Press the air baffle down until it is
securely seated.
Note: Close the retaining clip on each end of the DIMM connector before
installing the air baffle for proper cooling.

PCI riser-card
assembly 2
PCI riser-card
assembly 1
Air baffle
Figure 155. Air baffle installation
5. Replace PCI riser-card assemblies, if it is in long position.

7. Slide the server into the rack.
8. Reconnect the power cords and any cables that you removed.
9. Turn on the peripheral devices and the server.

Removing a RAID adapter battery holder
Use this information to remove a RAID adapter battery holder.
About this task
If a RAID adapter battery is installed remotely near the fan cage and you need to
replace it, complete the following steps:
Procedure
2. Turn off the server and peripheral devices and disconnect all power cords;
then, remove the cover (see “Removing the cover” on page 39).
3. Remove the filler; then pull the loops of the battery holder toward each other;
then, pull the cage out of the drive bay approximately 25 mm (1 inch).
Figure 156. RAID adapter battery holder removal
4. Disconnect the battery power cables.

5. Pull the drive completely out of the bay.
6. If you are not installing another drive in the bay, insert the filler panel into the
empty drive bay.
Results
If you are instructed to return the RAID adapter battery holder, follow all
packaging instructions, and use any packaging materials for shipping that are
supplied to you.

Replacing a RAID adapter battery holder
Use this information to replace a RAID adapter battery holder.
About this task
To install a RAID adapter battery holder, complete the following steps:
Procedure
external devices; then, remove the cover (see “Removing the cover” on page
39).
3. Install the optional ServeRAID adapter battery (see “Replacing a RAID
adapter battery/flash power module remotely in the server” on page 315).
4. Grasp the handle and slide the holder most of the way into the bay.
Figure 157. RAID adapter battery holder installation
5. Connect the battery power cables to the ServeRAID connector.

6. Make sure that the battery holder is secured firmly on the air baffle.
7. Install the filler.
8. Replacing the cover (see “Replacing the cover” on page 260).
10. Reconnect the power cords and all external cables, and turn on the server and
peripheral devices.

Removing the bezel
Use this information to remove the bezel.
About this task
To remove the bezel, complete the following steps:
Figure 158. Bezel removal
Procedure
2. Remove all the cables that are connected to the front of the server.
3. Remove the screws from the bezel.
4. Rotate the top of the bezel away from the server.
Replacing the bezel

Use this information to replace the bezel.
About this task
To install the bezel, complete the following steps:

Figure 159. Bezel installation
Procedure
3. Insert the tabs on the bottom of the bezel into the slots on the underside of the
chassis and attach it with the screws.
4. Connect any cables you previously removed from the front of the server.
Removing the 240 VA safety cover

Use this information to remove the 240 VA safety cover.
About this task
To remove the 240 VA safety cover, complete the following steps:
Procedure
2. Turn off the server, and disconnect all power cords and external cables.
4. Remove the screw from the safety cover.

Screw
Safety cover
Figure 160. 240 VA safety cover removal
5. Disconnect the hard disk drive backplane power cables from the connector in
front of the safety cover.
6. Slide the cover forward to disengage it from the system board, and then lift it
out of the server.
7. If you are instructed to return the 240 VA safety cover, follow all packaging
you.
Replacing the 240 VA safety cover

Use this information to install the 240 VA safety cover.
About this task
To install the 240 VA safety cover, complete the following steps:

Screw
Safety cover
Figure 161. 240 VA safety cover installation
Procedure
3. Line up and insert the tabs on the bottom of the safety cover into the slots on
the system board.
4. Slide the safety cover toward the back of the server until it is secure.
5. Connect the hard disk drive backplane power cables to the connector in front
of the safety cover.
6. Install the screw into the safety cover.
7. Replacing the cover (see “Replacing the cover” on page 260).
peripheral devices.

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 a hot-swap hard disk drive

Use this information to remove a hot-swap hard disk drive.
About this task
Attention:
v To avoid damage to the hard disk drive connectors, make sure that the server
cover is in place and fully closed whenever you install or remove a hard disk
drive.
v To make sure that there is adequate system cooling, do not operate the server for
more than 2 minutes without either a hard disk drive or a filler panel installed
in each bay.
v Before you make changes to disk drives, disk drive controllers (including
controllers that are integrated on the system board), disk drive backplanes, or
disk drive cables, back up all important data that is stored on hard disks.
v Before you remove any component of a RAID array, back up all RAID
configuration information.
To remove a hot-swap hard disk drive, complete the following steps.
Procedure
2. Make sure you save the data on your drive, especially if it is part of a RAID
array, before you remove it from the server.
3. Slide the release latch (orange) gently to the left to unlock the drive handle.
Handle
Latch
Figure 162. 2.5-inch hot-swap hard disk drives removal

3.5-inch hot-swap
hard disk drive
Latch
Handle Filler panel
Figure 163. 3.5-inch hot-swap hard disk drives removal
4. Grasp the handle and slide the drive out of the drive bay.
5. Reinstall the drive bay filler panel.
6. If you are instructed to return the drive assembly, follow all packaging
you.
Replacing a hot-swap hard disk drive

Use this information to install a hot-swap hard disk drive.
About this task
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.
For a list of supported hard disk drives, see http://www.ibm.com/systems/info/
x86servers/serverproven/compat/us/.
to set any switches or jumpers on the drive. If you are installing a SAS or SATA
hard disk drive, be sure to set the SAS or SATA ID for that device.
v The hot-swap server models support up to eight 2.5-inch or three 3.5-inch
hot-swap SAS or SATA hard disk drives.
v For a complete list of supported optional devices for the server, see
v Before you install an additional hot-swap hard disk drive, go to Table 2 on page
9 for detailed power supply configurations.
To install a hot-swap SAS or SATA hard disk drive, complete the following steps:
Note: If you have only one hard disk drive, you must install it in the bay 0
(upper-left).

Procedure
2. Remove the filler panel from the empty drive bay. Keep the filler panel in a
safe place.
a. Make sure that the tray handle is in the open (unlocked) position.
Latch
Handle
Filler panel handle
3.5-inch hot-swap
hard disk drive
Latch
Handle Filler panel
d. Rotate the tray handle to the closed (locked) position.
e. Check the hard disk drive status LED to verify that the hard disk drive is
operating correctly. If the yellow hard disk drive status LED of a drive is lit
continuously, that drive is faulty and must be replaced. If the green hard
disk drive activity LED is flashing, the drive is being accessed.

hard disk drives. See the ServeRAID adapter documentation for additional
ServeRAID adapter.
5. If you are installing additional hot-swap hard disk drives, do so now.

Removing a simple-swap hard disk drive

Use this information to remove a simple-swap hard disk drive.
About this task
You must turn off the server before removing simple-swap drives from the server.
To remove a simple-swap SATA hard disk drive, complete the following steps.
Attention:
v To avoid damage to the hard disk drive connectors, make sure that the server
cover is in place and fully closed whenever you install or remove a hard disk
drive.
v To make sure that there is adequate system cooling, do not operate the server for
more than 2 minutes without either a hard disk drive or a filler panel installed
in each bay.
Procedure
3. Slide the blue release latch to the right with one finger (to release the drive)
while using another finger to grasp the black drive handle and pull the hard
disk drive out of the drive bay.
2.5-inch
simple-swap
hard disk drive
Release latch
Filler panel
Figure 166. 2.5-inch simple-swap hard disk drive removal

hard disk drive
Filler panel
Figure 167. 3.5-inch simple-swap hard disk drive removal
you.
Replacing a simple-swap hard disk drive

Use this information to install a simple-swap hard disk drive.
About this task
You must turn off the server before installing simple-swap drives in the server.
Before you install a simple-swap SATA hard disk drive, read the following
information. For a list of supported hard disk drives, see http://www.ibm.com/
to set any switches or jumpers on the drive. If you are installing a SATA device,
be sure to set the SATA ID for that device.
v You can install up to six 3.5-inch simple-swap SATA hard disk drives in the
supported.
v You can install one 2.5-inch simple-swap SATA hard disk drives in bay 0 in the
supported.
v The simple-swap server models are available only in non-RAID configurations.
v Before you install an additional simple-swap hard disk drive, go to Table 2 on
page 9 for detailed power supply configurations.
To install a simple-swap hard disk drive, complete the following steps:

Procedure
3. Remove the filler panel from the empty drive bay.
a. Grasp the black drive handle and slide the blue release latch to the right
and align the drive assembly with the guide rails in the bay.
2.5-inch
simple-swap
hard disk drive
Release latch
Filler panel

hard disk drive
Filler panel
b. Gently push the drive into the bay until the drive stops.
7. If you are installing additional simple-swap hard disk drives, do so now.

Removing a 1.8-inch hot-swap solid state drive
Use this information to remove a 1.8-inch hot-swap solid state drive.
About this task
To remove a 1.8-inch hot-swap solid state drive, complete the following steps:
Procedure
3. Press the release latch (orange) gently to unlock the drive handle.
Release latch
1.8-inch
hot-swap
hard disk drive
Handle
Filler
Figure 170. 1.8-inch hot-swap solid state drives removal
4. Pull the tray handle until the handle stops.

5. Slide the drive out of the drive bay.
6. Rotate the tray handle to the closed (locked) position.
7. Reinstall the filler panel.
you.

Replacing a 1.8-inch hot-swap solid state drive
Use this information to install a 1.8-inch hot-swap solid state drive.
About this task
To install a 1.8-inch hot-swap solid state drive, complete the following steps:
Procedure
a. Make sure that the handle is in the open (unlocked) position.
1.8-inch
hot-swap
hard disk drive
Filler
Figure 171. 1.8-inch hot-swap solid state drives installation
d. Rotate the handle to the closed (locked) position.
e. Check the solid state drive status LED to verify that the solid state drive is
operating correctly. If the yellow solid state drive status LED of a drive is lit
continuously, that drive is faulty and must be replaced. If the green solid
state drive activity LED is flashing, the drive is being accessed.

solid disk drives. See the ServeRAID adapter documentation for additional
ServeRAID adapter.
5. If you are installing additional hot-swap solid state drives, do so now.

Removing a DVD drive
Use this information to remove a DVD drive.
About this task
To remove an optional DVD drive, complete the following steps:
Procedure
4. Press and hold the release tab down as you push the drive from the rear to
slide it out of the bay.
Release tab
Figure 172. DVD drive removal
5. Slide the drive retention clip from the side of the drive. Save the clip to use
when you install the replacement drive or replace the DVD drive filler panel.
Alignment pins
Figure 173. DVD drive retention clip removal
6. Attach the drive retention clip to the side of the DVD drive filler panel that you
removed in step 4 on page 279.
7. Slide the DVD drive filler panel into the DVD drive bay until the DVD drive
filler panel clicks into place.
8. If you are instructed to return the DVD drive, follow all packaging instructions,
and use any packaging materials for shipping that are supplied to you.

Replacing a DVD drive
Use this information to install a DVD drive.
About this task
The following notes describe the type of drives that the server supports and other
information that you must consider when you install a drive. For a list of
supported drives, see http://www.ibm.com/systems/info/x86servers/
serverproven/compat/us/.
v Locate the documentation that comes with the drive and follow those
v The server supports one ultra-slim SATA optical drive.
Procedure
Note: When you disconnect the power source from the server, you lose the
ability to view the LEDs because the LEDs are not lit when the power source
is removed. Before you disconnect the power source, make a note of which
LEDs are lit, including the LEDs that are lit on the operation information
panel, on the light path diagnostics panel, and LEDs inside the server on the
system board.
4. Remove the DVD drive filler panel if it is installed. Locate the blue release tab
on the rear of the DVD drive filler panel; then, while you press the tab, push
the DVD drive filler panel out of the drive bay.
5. Remove the retention clip from the side of the DVD drive filler panel. Save
the DVD drive filler panel for future use.
Note: If you are installing an optical drive that contains a laser, observe the
following safety precautions.
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.
Class 1 Laser Product

Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
Appareil A` Laser de Classe 1
6. 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.
7. Follow the instructions that come with the drive to set any jumpers or
switches.
8. Attach the drive retention clip that you removed from the DVD drive filler
panel to the side of the new DVD drive.
Alignment pins
Figure 174. DVD drive retention clip installation
9. Align the DVD drive in the drive bay and slide the DVD drive into the optical
drive bay until the DVD drive clicks into place.

10. Connect the DVD drive cable (see “Replacing the DVD drive cable” on page
283). The following illustration shows the cable routing for the DVD drive:
Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch

Removing the DVD drive cable
Use this information to remove the DVD drive cable.
About this task
To remove the DVD cable, complete the following steps:
Procedure
5. Press and hold the connector release tab; then, remove the DVD drive cable
from the connector on the system board.
Attention: You must press the connector release tab in order to disconnect the
DVD drive cable from the system board. Do not disconnect the DVD drive
cable by using excessive force.
Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch

6. From the rear of the DVD drive cage, press and hold the connector latch (on
the left of the cable connector) and grasp the cable connector and slide it to the
right; then, remove the DVD drive cable from the connector on the back of the
DVD drive and set it aside.
7. If you are instructed to return the DVD drive cable, follow all packaging
you.
Replacing the DVD drive cable

Use this information to install the DVD drive cable.
About this task
To install the DVD drive cable, complete the following steps:
Procedure
5. Align the cable connector with the connector on the rear of the DVD drive
cage. Press the cable connector into the optical drive cage connector and slide
it to the left until it is firmly seated.

Cable
connector
latch
The following illustration shows cable routing for the DVD cable:
Attention: Follow the optical drive cable routing as the illustration shows.
Make sure that the cable is not pinched and does not cover any connectors or
obstruct any components on the system board.

Release tab
Optical drive
connector
DVD drive
cable
Cable connector
latch
6. Replace the air baffle (see “Replacing the air baffle” on page 262).
7. Replace the cover (see “Replacing the cover” on page 260).

Removing a tape drive
Use this information to remove a tape drive.
About this task
To remove an optional tape drive, complete the following steps:
Procedure
4. Open the tape drive tray release latch and slide the drive tray out of the bay
approximately 25 mm (1 inch).
5. Disconnect the power and signal cables from the rear of the tape drive.
6. Pull the drive completely out of the bay.
Figure 180. Tape drive removal
7. Remove the tape drive from the drive tray by removing the four screws on the
sides of the tray.
Figure 181. Screws removal

8. If you are not installing another drive in the bay, insert the tape drive filler
panel into the empty tape drive bay.
9. If you are instructed to return the drive, follow all packaging instructions, and
use any packaging materials for shipping that are supplied to you.
Replacing a tape drive

Use this information to install a tape drive.
About this task
Procedure
4. If the tape drive came with metal spacers on the installed on the sides,
remove the spacers.
5. Install the drive tray on the new tape drive as shown, using the four screws
that you removed from the former drive.
Figure 182. Screws installation
6. Prepare the drive according to the instructions that come with the drive,
setting any switches or jumpers.
7. Slide the tape-drive assembly most of the way into the tape-drive bay.

Figure 183. Tape drive installation
8. Using the cables from the former tape drive, connect the signal and power
cables to the back of the tape drive.
9. Make sure all the cables are out of the way, and slide the tape-drive assembly
the rest of the way into the tape-drive bay.
10. Push the tray handle to the closed (locked) position.
Removing a memory module

Use this information to remove a memory module.
About this task
To remove a dual inline memory module (DIMM), complete the following steps:
Procedure
remove the DIMM.

Figure 184. DIMM removal
6. If you are instructed to return the DIMM, follow all packaging instructions, and
use any packaging materials for shipping that are supplied to you.

The following notes describe the types of DIMMs that the server supports and
other information that you must consider when you install DIMMs.
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.
v The server supports only industry-standard double-data-rate 3 (DDR3), 800,
1066, 1333, 1600, or 1866 MHz, PC3-6400, PC3-8500, PC3-10600, PC3-12800, or
PC3-14900 registered or unbuffered, synchronous dynamic random-access
memory (SDRAM) dual inline memory modules (DIMMs) with error correcting
code (ECC). See http://www.ibm.com/systems/info/x86servers/serverproven/
compat/us/ for a list of supported memory modules for the server.
– 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
- xff is the device organization (bit width)
x4 = x4 organization (4 DQ lines per SDRAM)
- v is the SDRAM and support component supply voltage (VDD)
v Blank = 1.5 V specified
v L = 1.35 V specified, 1.5 V operable

Note: Values for these voltages are ‘specified’ which means the device
characteristics such as timing are supported at this voltage. Values are
‘operable’ which means that the devices can be operated safely at this
voltage. However, device characteristics such as timing may not be
guaranteed. All devices must be ‘tolerant’ of the highest DDR3 nominal
voltage of 1.5 V, meaning that they may not operate at 1.5 V but may be
powered at that voltage without damage to the devices.
- wwwww is the DIMM bandwidth, in MBps
- m is the DIMM type
E = Unbuffered DIMM (UDIMM) with ECC (x72-bit module data bus)
L = Load Reduction DIMM (LRDIMM)
R = Registered DIMM (RDIMM)
U = Unbuffered DIMM with no ECC (x64-bit primary data bus)
- aa is the 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
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 PC3v-xxxxxx-xx-xx-xxx.
The numeral in the sixth numerical position indicates whether the DIMM is
single-rank (n=1), dual-rank (n=2), or quad-rank (n=4).
v The following rules apply to DDR3 RDIMM speed as it relates to the number of
RDIMMs in a channel:
– When you install 1 RDIMM per channel, the memory runs at 1866 MHz
– All channels in a server run at the fastest common frequency
– Do not install registered, unbuffered, and load reduction DIMMs in the same
server
v The maximum memory speed is determined by the combination of the
microprocessor, DIMM speed, DIMM type, Operating Modes in UEFI settings,
and the number of DIMMs installed in each channel.
v In two-DIMM-per-channel configuration, a server with an Intel Xeon™ E5-2600
series microprocessor automatically operates with a maximum memory speed of
up to 1600 MHz when the following condition is met:
– Two 1.35 V single-rank, dual-ranl, or quad-rank UDIMMs, RDIMMs or
LRDIMMs are installed in the same channel. In the Setup utility, Memory
speed is set to Max performance and LV-DIMM power is set to Enhance
performance mode. The 1.35 V UDIMMs, RDIMMs or LRDIMMs will
function at 1.5 V.
v The server supports a maximum of 16 dual-rank UDIMMs. The server supports
up to two UDIMMs per channel.

v The server supports a maximum of 24 single-rank, dual-rank, or 16 quad-rank
RDIMMs. The server does not support three quad-rank RDIMMs in the same
channel.
v The following table shows an example of the maximum amount of memory that
you can install using ranked DIMMs:
Table 27. Maximum memory installation using ranked DIMMs
Number of
DIMMs DIMM type DIMM size Total memory
16 Dual-rank UDIMMs 4 GB 64 GB
16 Quad-rank RDIMMs 8 GB 128 GB
24 Quad-rank LRDIMMs 32 GB 768 GB
v The UDIMM option that is available for the server is 4 GB. The server supports
a minimum of 4 GB and a maximum of 64 GB of system memory using
UDIMMs.
v The RDIMM options that are available for the server are 2 GB, 4 GB, 8 GB, and
16 GB. The server supports a minimum of 2 GB and a maximum of 384 GB of
system memory using RDIMMs.
v The HCDIMM options that are available for the server are 16 GB and 32 GB. The
server supports a minimum of 16 GB and a maximum of 768 GB of system
memory using HCDIMMs.
Note: Do not mix the 16 GB HCDIMM and the 32 GB HCDIMM in the server.
v The LRDIMM option that is available for the server is 32 GB. The server
supports a minimum of 32 GB and a maximum of 768 GB of system memory
using LRDIMMs.
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 150.
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. However, to improve system performance, install a
minimum of four DIMMs for each microprocessor.
v DIMMs in the server must be the same type (RDIMM, UDIMM, HCDIMM, or
LRDIMM) to ensure that the server will operate correctly.
v When you install one quad-rank DIMM in a channel, install it in the DIMM
connector furthest away from the microprocessor.
v When you install Flash DIMMs, follow the following rules strictly:
– Flash DIMM thermal specification supports the maximum temperature up to
70°C (158°F).

Note: The system may indicates specific error messages when the
temperature does not meet 70°C (158°F), these error messages do not impact
the system operation.
– Flash DIMM configuration supports RHEL 6.4 and RHEL 6.5.
– Flash DIMM configuration is only available to mix with one type of 16GB
RDIMM, with quantities of 8 or 16 DIMMs.
– Flash DIMM configuration does not support the fan redundancy function
when the ambient temperature is over 30°C (86°F). Please refer to the retain
tip H212833 at http://www.ibm.com/supportportal/for the detailed
information.
Table 28. Supported RDIMM
DIMM description Option part number FRU part number
16 GB dual-rank 1.5 V, 00D5048 46W0670
DDR3, 1866MHz, PC3-14900
CL 13 ECC LP RDIMM
– SSD Flash DIMM is always installed with a RDIMM in the same channel.
– SSD Flash DIMMs can not be mixed with LRDIMMs and UDIMMs.
– The Flash DIMM options that are available for the server are 200 GB and 400
GB, with quantities of 4 or 8 DIMMs.
Note: Do not mix 200 GB Flash DIMM and 400 GB Flash DIMM in the server.
– Flash DIMM configuration supports the following microprocessors.
Table 29. Supported microprocessors
Microprocessor description Option part number FRU part number
v2, 3.5 GHz, 25 MB, 1866
MHz, 130 W (6-core)
v2, 3.3 GHz, 25 MB, 1866
MHz, 130 W (8-core)
v2, 3.0 GHz, 25 MB, 1866
v2, 2.7 GHz, 30 MB, 1866
v Flash DIMM configuration supports one mezz adapter.

Table 30. Supported adapter
Adpater description Option part number FRU part number
Intel x520 dual port 10GbE 49Y7980 49Y7982
SFP+ embedded adapter
v For detailed Flash DIMM installation sequence, go to Flash DIMM installation

sequence .
Notes:

1. You can install DIMMs for microprocessor 2 as soon as you install
microprocessor 2; you do not have to wait until all of the DIMM slots for
microprocessor 1 are filled.
2. DIMM slots 13-24 are reserved for microprocessor 2; thus, DIMM slots 13-24 are
enabled when microprocessor 2 is installed.
The following illustration shows the location of the DIMM connectors on the
system board.
Figure 185. DIMM connectors location
DIMM installation sequence:
Depending on the server model, the server may come with a minimum of one 2
GB or 4 GB DIMM installed in slot 1. When you install additional DIMMs, install
them in the order shown in the following table to optimize system performance.
Normal mode DIMM installation sequence
In general, all four channels on the memory interface for each microprocessor can
be populated in any order and have no matching requirements.
Table 31. Normal mode DIMM installation sequence
Number of installed
microprocessor DIMM connector population sequence
One microprocessor 1, 4, 9, 12, 2, 5, 8, 11, 3, 6, 7, 10
installed
Two microprocessors 1, 13, 4, 16, 9, 21, 12, 24, 2, 14, 5, 17, 8, 20, 11, 23, 3, 15, 6, 18,
installed 7, 19, 10, 22
For optimal performance:
Make sure all four memory channels of each microprocessor are populated. Each
memory channels should be populated with the same type and amount of memory
per channel. Each microprocessor socket should be populated with the same type

and amount of memory per socket. 1DPC (one DIMM per channel) or 2DPC (two
DIMM per channel) memory configuration are recommended. Unless there is a
need for memory capacity over memory frequency, 3DPC (three DIMMs per
channel) configuration is not recommended since 3DPC configuration forces the
memory subsystem to run at a lower frequency (1066MHz).
Flash DIMM installation sequence

1. When you install 2 DIMMs per channel as the following installation sequence,
the memory runs at 1600 MHz.
Flash DIMM 5, 8, 17, 20
RDIMM 1, 4, 9, 12. 13, 16, 21, 24
2. When you install 2 DIMMs (1 Flash DIMM and 1 RDIMM) per channel as the
Flash DIMM 2, 5, 8, 11. 14, 17, 20, 23
RDIMM 1, 4, 9, 12. 13, 16, 21, 24
3. When you install 3 DIMMs (1 Flash DIMM and 2 RDIMMs) per channel as the
Flash DIMM 3, 6, 7, 10. 15, 18, 19, 22
RDIMM 1, 2, 4, 5, 8, 9, 11, 12, 13, 14, 16, 17, 20, 21, 23, 24
Please refer to the Understanding and Optimizing Memory Performance for Intel
Xeon Processor E5-2600 Series in IBM Flex System, System x, and BladeCenter
Platforms white paper for the detail.
Memory mirrored channel:
Memory mirrored channel mode replicates and stores data on two pairs of DIMMs
within two channels simultaneously.
If a failure occurs, the memory controller switches from the primary pair of
memory DIMMs to the backup pair of DIMMs. To enable memory mirrored
channel through the Setup utility, select System Settings > Memory. For more
information, see “Using the Setup utility” on page 154. When you use the memory
mirrored channel feature, consider the following information:
v When you use memory mirrored channel, you must install a pair of DIMMs at a
time. The two DIMMs in each pair must be identical in size, type, and rank
(single, dual, or quad), and organization, but not in speed. The channels run at
the speed of the slowest DIMM in any of the channels.

v The maximum available memory is reduced to half of the installed memory
when memory mirrored channel is enabled. For example, if you install 64 GB of
memory using RDIMMs, only 32 GB of addressable memory is available when
you use memory mirrored channel.
v For UDIMMs, DIMM connectors 3, 6, 7, and 10 for microprocessor 1 and DIMM
connectors 15, 18, 19, and 22 for microprocessor 2 are not used in memory
mirrored channel mode.
The following table shows the installation sequence for memory mirrored channel
mode:
Table 35. Memory mirrored channel mode DIMM population sequence
Number of installed
Note: DIMM connectors 3, 6, 7, 10, 15, 18, 19, and 22 are not used in memory mirrored
channel mode when UDIMMs are installed in the server.

Memory rank sparing:
The memory rank sparing feature disables the failed memory from the system
configuration and activates a rank sparing DIMM to replace the failed active
DIMM.
You can enable rank sparing memory in the Setup utility, select System Settings >
Memory. For more information, see “Using the Setup utility” on page 154. When
you use the memory rank sparing feature, consider the following information:
v The memory rank sparing feature is supported on server models with an Intel
Xeon™ E5-2600 series microprocessor.
v The maximum available memory is reduced when memory rank sparing mode
is enabled.
Follow the installation sequence for rank sparing mode:

v Install at least one quad-rank DIMM in a channel.
v Install at least two single-rank or dual-rank DIMMs in a channel.
Table 36. Memory rank sparing mode DIMM population sequence
Number of installed
Note: DIMM connectors 3, 6, 7, 10, 15, 18, 19, and 22 are not used in memory rank sparing
mode when UDIMMs are installed in the server.

Replacing a memory module:
Use this information to replace a memory module.
About this task
Note: Before you install an additional memory module, go to Table 2 on page 9 for
detailed power supply configurations.
Procedure
remove the DIMM.
Figure 188. DIMM installation
6. 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.
7. Turn the DIMM so that the alignment slot align correctly with the alignment
tab.
8. 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 34 for the locations of the DIMM
connectors).
9. 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 air baffle (see “Replacing the air baffle” on page 262).
Note: Close all the retaining clips even for slots without DIMMs installed
before replacing the air baffle.
Removing the fan bracket

Use this information to remove the fan bracket.
About this task
To replace some components or to create working room, you might have to remove
the fan-bracket assembly.
Note: To remove or install a fan, it is not necessary to remove the fan bracket. See
“Removing a hot-swap fan” on page 336 and “Replacing a hot-swap fan” on page
337.
To remove the fan bracket, complete the following steps:

Fan-bracket
release latches
Pins
Figure 189. Fan bracket removal
Procedure
4. Remove the fans (see “Removing a hot-swap fan” on page 336).
5. Press the fan-bracket release latches toward each other and lift the fan bracket
out of the server.

Replacing the fan bracket
Use this information to replace the fan bracket.
About this task
To install the fan bracket, complete the following steps:
Fan-bracket
release latches
Pins
Figure 190. Fan bracket removal
Procedure
4. Lower the fan bracket into the chassis.
5. Align the holes in the bottom of the bracket with the pins in the bottom of the
chassis.
6. Press the bracket into position until the fan-bracket release levers click into
place.
7. Replace the fans (see “Replacing a hot-swap fan” on page 337).

Removing a PCI riser-card assembly
Use this information to remove a PCI riser-card assembly.
About this task
The server comes with one riser-card assembly (with option to add one more) that
each contains two to three PCI slots. See http://www.ibm.com/systems/info/
x86servers/serverproven/compat/us/ for a list of riser-card assemblies that you
can use with the server.
To remove a PCI riser-card assembly, complete the following steps:
PCI riser-card
assembly 2
PCI riser-card
assembly 1
Procedure
2. Turn off the server and peripheral devices, and disconnect the power cord and
4. Grasp the assembly at the front tab and rear edge and lift it to remove it from
the server. Place the riser-card assembly on a flat, static-protective surface.

Replacing a PCI riser-card assembly
Use this information to replace a PCI riser-card assembly.
About this task
The server provides two PCI riser-card slots on the system board. The following
information indicates the riser-card slots:
v Standard models of the server come with one PCI Express riser-card assembly
installed. If you want to replace them with PCI-X riser-card assemblies, you
must order the PCI-X riser-card assembly option, which includes the bracket.
v A PCI Express riser-card assembly has a black connector and supports PCI
Express adapters, and a PCI-X riser-card assembly has a white (light in color)
connector and supports PCI-X adapters.
v PCI riser slot 1 (the farthest slot from the power supplies). You must install a
PCI riser-card assembly in slot 1 with microprocessor 1.
v PCI riser slot 2 (the closest slot to the power supplies). You must install a PCI
riser-card assembly in slot 2 with microprocessor 2.
v PCI riser-card brackets must be installed even if you do not install an adapter.
To install a PCI riser-card assembly, complete the following steps:
Procedure
4. Reinstall any adapters and reconnect any internal cables you might have
removed in other procedures (see “Replacing an adapter” on page 305 and
“Internal cable routing and connectors” on page 249).
5. Align the PCI riser-card assembly with the selected PCI connector on the
system board:
a. PCI connector 1: Carefully fit the two alignment slots on the side of the
assembly onto the two alignment brackets in the side of the chassis.

PCI riser-card
assembly 2
PCI riser-card
assembly 1
b. PCI connector 2: Carefully align the bottom edge (the contact edge) of the
riser-card assembly with the riser-card connector on the system board.

Removing an adapter
Use this information to remove an adapter.
About this task
This topic describes removing an adapter from a PCI expansion slot in a PCI
riser-card assembly. These instructions apply to PCI adapters such as video graphic
adapters and network adapters.
The following illustration shows the locations of the adapter expansion slots from
the rear of the server.
Maximal card dimension supported in each slot (rear view)

1 Full height , up to full length 4 Full height , up to full length
2 Full height, half length 5 Full height , up to full length
(Riser 1) (Riser 2)
Note: If you are replacing a high power graphics adapter, you might need to
disconnect the internal power cable from the system board before removing the
adapter.
To remove an adapter, complete the following steps:
PCI PCI
assembly assembly
Adapter Adapter
Adapter Adapter
Full-length
adapter
bracket Full-length
adapter
bracket
Figure 193. Adapter removal
Procedure
2. Turn off the server and peripheral devices and disconnect all power cords;
then, remove the cover (see “Removing the cover” on page 39).
3. Press down on the left and right side latches and slide the server out of the
rack enclosure until both slide rails lock; then, remove the cover (see
“Removing the cover” on page 39).
4. Remove the PCI riser-card assembly that contains the adapter (see “Removing a

v If you are removing an adapter from PCI expansion slot 1, 2, or 3, remove
PCI riser-card assembly 1.
v If you are removing an adapter from PCI expansion slot 4, 5, or 6, remove
PCI riser-card assembly 2.
5. Disconnect any cables from the adapter (make note of the cable routing, in case
you reinstall the adapter later).
6. Carefully grasp the adapter by its top edge or upper corners, and pull the
adapter from the PCI expansion slot.
7. If the adapter is a full-length adapter in the upper expansion slot of the PCI
riser-card assembly and you do not intend to replace it with another full-length
adapter, remove the full-length-adapter bracket and store it on the underside of
the top of the PCI riser-card assembly.
8. If you are instructed to return the adapter, follow all packaging instructions,
Replacing an adapter
Use this information to replace an adapter.
About this task
v Locate the documentation that comes with the adapter and follow those
instructions in addition to the instructions in this section.
v The server provides one internal SAS/SATA RAID connector and two PCI slots
on the system board. See “System-board optional-device connectors” on page 34
for the location of the internal SAS/SATA RAID connector and riser-card slots.
You can replace the IBM ServeRAID SAS/SATA adapter with an optional IBM
ServeRAID SAS/SATA adapter in the slot. For configuration information, see the
ServeRAID documentation at http://www.ibm.com/supportportal/.
v Do not set the maximum digital video adapter resolution above 1600 x 1200 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 Read the following table before installing memory modules when any Quadro
adapters is installed.
Table 37. NVIDIA Quadro video adapter configurations
Description Supported maximum total memory size
v Any high-definition video-out connector or stereo connector on any add-on

video adapter is not supported
v The server does not support legacy 5V PCI adapters.
v When you install any PCI adapter, the power cords must be disconnected from
the power source before you remove the PCI Express riser-card assembly and
the PCI-X riser-card assembly. Otherwise, the active power management event
signal will be disabled by the system-board logic, and the Wake on LAN feature

might not work. However, after the server is powered-on locally, the active
power manager active power management event signal will be enabled by the
system-board logic.
v The server provides two PCI riser-card slots on the system board. If you want to
install a PCI Express or PCI-X adapter, you must order the PCI riser-card option.
v If you are installing a ServeRAID-M5110, ServeRAID-M5120, or an IBM LLM-SM
dual port 10GbE SFP+ adapter, it can only be installed in PCI slot 1, 2, 4, or 5.
v Before you install an additional adapter, go to Table 2 on page 9 for detailed
power supply configurations.
The following illustration shows the locations of the adapter expansion slots from
the rear of the server.
Maximal card dimension supported in each slot (rear view)

1 Full height , up to full length 4 Full height , up to full length
2 Full height, half length 5 Full height , up to full length
(Riser 1) (Riser 2)
To install an adapter, complete the following steps:
PCI
riser-card
assembly
Adapter
connectors Bracket
Expansion-slot
cover
Full-length
adapter Adapter
bracket
Figure 194. Adapter installation
Procedure
4. Follow the cabling instructions, if any come with the adapter. Route the
adapter cables before you install the adapter.
5. Install the adapter in the expansion slot.
a. For riser 1: if the adapter is a full-length adapter for the upper expansion
slot in the riser card, remove the full-length-adapter bracket from

underneath the top of the riser-card assembly and insert it in the end of
the upper expansion slot of the riser-card assembly. See “Stretching a PCI
riser-card assembly” on page 43 for instructions.
b. For riser 2: if the adapter is a full-length adapter for the upper expansion
slot in the riser card, the bracket is on the cage by default. Insert it in the
end of the upper expansion slot of the riser-card assembly. See “Stretching
a PCI riser-card assembly” on page 43 for instructions.
PCI
riser-card
assembly
Full-length
adapter
bracket
c. Align the adapter with the PCI connector on the riser card and the guide
on the external end of the riser-card assembly.
d. Press the adapter firmly into the PCI connector on the riser card.
PCI PCI
assembly assembly
Adapter Adapter
Adapter Adapter
Full-length
adapter
bracket Full-length
adapter
bracket
6. Connect any required cables to the adapter (see “Internal cable routing and
connectors” on page 249

Attention:
v When you route cables, do not block any connectors or the ventilated space
around any of the fans.
v Make sure that cables are not routed on top of components under the PCI
v Make sure that cables are not pinched by the server components.
7. Align the PCI riser-card assembly with the selected PCI connector on the
system board:
v PCI-riser connector 1: Carefully fit the two alignment slots on the side of
the assembly onto the two alignment brackets on the side of the chassis;
v PCI-riser connector 2: Carefully align the bottom edge (the contact edge) of
the riser-card assembly with the riser-card connector on the system board;
9. Install the PCI riser-card assembly in the server (see “Replacing a PCI
riser-card assembly” on page 302).
10. Connect the cable to the newly-installed adapter.
11. Perform any configuration tasks that are required for the adapter.
Removing an optional ServeRAID upgrade adapter memory

module
Use this information to remove an optional ServeRAID upgrade adapter memory
module.
About this task
Before removing an optional ServeRAID upgrade adapter memory module,

complete the following steps for correct configuration:
1. Boot to webbios and delete all configurations.
2. In controller properties of Web-bios, reset to factory defaults.
3. Turn off AC power supply.
For more information about the MegaRAID, go to http://www.ibm.com/support/

entry/portal/docdisplay?lndocid=MIGR-5073015.
To remove an optional ServeRAID upgrade adapter memory module, complete the

following steps:
Procedure
4. Disconnect the battery/flash power module cable from the battery.

Battery
Figure 195. Disconnecting the battery cable
Flash power
module cable ServeRAID memory module
Flash power
module
Figure 196. Disconnecting the flash power module cable
5. Remove the ServeRAID upgrade adapter memory module and the three pegs
from the system board.

Rententions
ServeRAID
memory module
RAID upgrade
connector
Figure 197. Removing ServeRAID upgrade adapter memory module
6. Disconnect the battery/flash power module cable from the ServeRAID upgrade
adapter memory module.
Battery cable
Figure 198. Disconnecting the battery cable
Flash power
module cable
Figure 199. Disconnecting the flash power module cable
7. If you are instructed to return the feature key, follow all packaging instructions,

Replacing an optional ServeRAID upgrade adapter memory
module
Use this information to replace an optional ServeRAID upgrade adapter memory
module.
About this task
To install an optional ServeRAID upgrade adapter memory module, complete the

following steps:
Procedure
4. Connect the battery/flash power module cable to the ServeRAID upgrade
adapter memory module.
Battery cable
Figure 200. ServeRAID upgrade adapter memory module and battery cable
Flash power
module cable
Figure 201. ServeRAID upgrade adapter memory module and flash power module cable
5. Attach the three pegs to the ServeRAID upgrade adapter memory module and
install the ServeRAID upgrade adapter memory module into the system
board.

Rententions
ServeRAID memory
module
RAID upgrade
connector
Figure 202. Installing ServeRAID upgrade adapter memory module and battery/flash power
module cable
6. Connect the other end of the battery/flash power module cable to the
battery/flash power module.
Battery
Figure 203. Connecting the battery cable

Flash power
module cable ServeRAID memory module
Flash power
module
Figure 204. Connecting the flash power module cable
Note: Make sure the battery/flash power module is seated properly (see
“Installing a ServeRAID SAS controller battery on the remote battery tray” on
page 70).
Removing a remotely installed RAID adapter battery/flash power

module
Use this information to remove a remotely installed RAID adapter battery/flash
power module.
About this task
If a RAID adapter battery / flash power module is installed near the fan cage and
you need to replace it, complete the following steps:
Procedure
4. Remove any cable covering or obstructing the battery/flash power module
holder before opening the battery/flash power module holder.
5. Pull the release tab toward the fan cage and unlock the retention clip.

Battery / Flash
power module
Battery / Flash
power module cable
connector
Figure 205. RAID adapter battery/flash power module removal
6. Disconnect the battery/flash power module cable from the connector on the
battery/flash power module.
7. Lift the battery/flash power module up to remove the battery/flash power
module from the holder.
8. If you are instructed to return the RAID adapter battery/flash power module,
follow all packaging instructions, and use any packaging materials for shipping
that are supplied to you.

Replacing a RAID adapter battery/flash power module remotely
in the server
Use this information to replace a RAID adapter battery remotely in the server.
About this task
When you install any ServeRAID adapter that comes with a battery/flash power
module, it is necessary to install the battery/flash power module in another
location in the server to prevent the batteries/flash power modules from
overheating.
Note:
1. The battery/flash power module must be installed near the fan cage first. If
you have more than two batteries/fan power modules, the battery/fan power
module should be installed in ServeRAID SAS controller remote retention (see
“Replacing a RAID adapter battery holder” on page 265). Install your
batteries/flash power modules orderly as the following illustration.
Figure 206. RAID adapter battery/flash power module installation
2. If you are installing ServeRAID-M5100 Series RAID 5 upgrade that comes with
a battery/flash power module, you must install the battery/flash power
module in ServeRAID SAS controller remote retention instead (see “Replacing a
RAID adapter battery holder” on page 265).

To install a RAID adapter battery/flash power module in the server, complete the
following steps:
Procedure
external devices.
4. Install the ServeRAID adapter on the system board (see “Replacing an
adapter” on page 305) or install the ServeRAID adapter on the riser card and
install the riser-card assembly in the server (see “Replacing an adapter” on
page 305).
5. Connect one end of the battery/flash power module cable to the RAID
adapter battery/flash power module connector.
6. Route the remote battery/flash power module cable along the chassis.
7. Remove any cable covering or obstructing the battery/flash power module
holder before opening the battery/flash power module holder.
8. Install the battery/flash power module near the fan cage:
a. Release the retention clip in the open position.
b. Align the battery/flash power module cable connector with the slot on the
battery/flash power module holder. Place the battery/flash power module
into the holder and make sure that the holder engages the battery/flash
power module securely.

Connector
Note: The positioning of the remote battery/flash power module depends

on the type of the remote batteries/flash power modules that you install.
c. Connect the other end of the battery/flash power module cable to the
connector on the battery/flash power module.
Battery
Note: Make sure the battery/flash power module is seated properly.

d. Place the retention clip underneath while pressing the release tab toward
the front of the server until it snaps in place to hold the retention clip
firmly in place.
peripheral devices.
Removing the dual-port network adapter

Use this information to remove the dual-port network adapter.
About this task
To remove the dual-port network adapter, complete the following steps:
Procedure
5. Loosen the two captive screws on the network adapter from the screw holes on
the system board.
Network
Screw holes
Retention
brackets
Thumbscrew
Pin
Network
adapter connector
Figure 210. Screws disengagement
6. Loosen the thumbscrew on the chassis.

7. Grasp the network adapter and disengage it from the pin, retention brackets,
and the connector on the system board; then, lift the adapter out of the port
openings on the rear of the chassis and remove it from the server.
8. If you are instructed to return the adapter, follow all packaging instructions,
Replacing the dual-port network adapter

Use this information to replace the dual-port network adapter.
About this task
You can purchase one of the following dual-port network adapters to add two
additional network ports in the server. To order a dual-port network adapter
Table 38. Supported dual-port network adapters on the network connector
Option
part FRU part
Dual-port network adapter number number Remark
Mellanox ConnectX-3 dual-port 90Y6338 90Y4956
QDR/FDR10 mezz card
Qlogic dual-port 10GbE SFP+ 90Y6454 90Y5099 Four fans installed
Embedded VFA required.
Emulex dual-port 10GbE SFP+ 90Y6456 90Y5100
Embedded VFA III
Dual-port FDR embedded adapter 00D4143 90Y6606
Note: You can purchase IBM System x3650 M4 Thermal Solution Kit (option part number
46W8422) to acquire an additional fan for your server.
v To configure network adapters, complete the following steps:
154), select System Settings > Network.
2. From the Network Device List, select one network adapter.
3. Press Enter to configure the network adapter settings.
v To convert the NIC/iSCSI/FCoE for Emulex Dual Port 10GbE SFP+ Embedded
VFA III, complete the following steps:
154), select System Settings > Network and press Enter.
2. From the Network Device List, select Emulex network adapter.
3. Press Enter to configure Emulex network adapter, select Personality and
press Enter to change the settings.
– NIC
– iSCSI (enabled after FoD installed)

– FCoE (enabled after FoD installed)
v To download the latest version of drivers for iSCSI and FCoE from the IBM
website, complete the following steps:
1. Go to http://www.ibm.com/support/fixcentral/.
2. Click Product support > System x > Product family > System x3650 M4 >
7915.
3. From the Operating system menu, select your operating system, and then
click Search to display the available drivers.
4. Download the latest version of drivers.
– Emulex iSCSI Device Driver for Windows 2008
– Emulex FCoE Device Driver for Windows 2008
v Port 0 on the Emulex Dual Port 10GbE SFP+ Embedded VFA III can be
configured as shared system management.
v When the server is in standby mode, both ports on the Emulex Dual Port 10GbE
SFP+ Embedded VFA III function at 100M connection speed with Wake on LAN
feature.
The Emulex Dual Port 10GbE SFP+ Embedded VFA III is automatically disabled if
one of the following errors occurs:
v An error log indicates a temperature warning for the Ethernet adapter.
v All power supplies are removed or the server is disconnected from the power
source.
To install the dual-port network adapter, complete the following steps:
Procedure
5. Remove the adapter filler panel on the rear of the chassis (if it has not been
removed already).

Network adapter
filler panel
Figure 211. Adapter filler panel removal
6. Touch the static-protective package that contains the new adapter to any
unpainted metal surface on the server. Then, remove the adapter from the
package.
7. Align the adapter so that the port connectors on the adapter line up with the
pin and thumbscrew on the chassis; then, align the connector of the adapter
with the adapter connector on the system board.
Network
Screw holes
Retention
brackets
Thumbscrew
Pin
Network
adapter connector
Figure 212. Network adapter installation

8. Press the adapter firmly until the pin, and retention brackets engage the
adapter. Make sure the adapter is securely seated on the connector on the
system board.
Attention: Make sure the port connectors on the adapter are aligned
properly with the chassis on the rear of the server. An incorrectly seated
adapter might cause damage to the system board or the adapter.
9. Fasten the thumbscrew on the rear side of the chassis.
10. Fasten the two captive screws on the network adapter.
11. Reinstall the PCI riser-card assembly in PCI riser connector 2 if you have
removed it previously (see “Replacing a PCI riser-card assembly” on page
302).
Removing a hot-swap ac power supply

Use this information to remove a hot-swap ac power supply.
About this task
When you remove or install a hot-swap power supply, observe the following
precautions.
Statement 5
CAUTION:
2
1
Statement 8

CAUTION:
label attached.
technician.
To remove a hot-swap ac power supply, complete the following steps:
Procedure
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.
Power supply
filler panel
Hot-swap
power supply 2
Figure 213. Power supply removal
5. If you are instructed to return the power supply, follow all packaging
you.

Replacing a hot-swap ac power supply
Use this information to replace a hot-swap ac power supply.
About this task
to power supply bay 1. The input voltage is 100-127 V ac or 200-240 V ac
auto-sensing.
v Power supplies in the server must be with the same power rating or wattage to
ensure that the server will operate correctly. For example, you cannot mix
550-watt and 750-watt power supplies in the server.
Statement 5
CAUTION:
2
1
Statement 8

CAUTION:
label attached.
technician.
To install a hot-swap ac power supply, complete the following steps:
Procedure
Power supply
filler panel
Hot-swap
power supply 2
Attention: Do not install the different power rating or wattage of power
supplies, high-efficiency and non-high-efficiency power supplies in the server.
connector on the power supply. The following illustration shows the
power-cord connectors on the back of the server.

Power cord
connectors
6. Route the power cord through the clip next to power-supply and through any
cable clamps on the rear of the server, to prevent the power cord from being
accidentally pulled out when you slide the server in and out of the rack.
connector on the power supply.
8. Connect the other end of the power cord to a properly grounded electrical
outlet.
9. Make sure that the ac power LED and the dc power LED on the ac 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.
correctly.

Removing a hot-swap dc power supply
Use this information to remove a hot-swap dc power supply.
About this task
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.

equipment.
conductor.
Statement 31

DANGER
hazardous.

structural damage.
product. product.
Statement 33
CAUTION:

Statement 34
CAUTION:
field wiring.
To remove a hot-swap dc power supply, complete the following steps:
Procedure
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.
Power supply
filler panel
Hot-swap
power supply 2
Figure 216. Power supply removal
5. If you are instructed to return the power supply, follow all packaging
you.
Replacing a hot-swap dc power supply

Use this information to replace a hot-swap dc power supply.
About this task
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 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 on page below.
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.

equipment.
conductor.
Statement 31

DANGER
hazardous.

structural damage.
product. product.
Statement 33
CAUTION:

Statement 34
CAUTION:
field wiring.
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.

Procedure
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.
Figure 217. DC power supply rear view
Power supply
filler panel
Hot-swap
power supply 2

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 on page
“Installing a hot-swap dc power supply” on page 79. 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.
power supplies.
Figure 220. Redundant power information label

Removing a hot-swap fan
Use this information to remove a hot-swap fan.
About this task
Attention: To ensure proper server operation, replace a failed hot-swap fan

within 30 seconds.
To remove a hot-swap-fan, complete the following steps:
Procedure
2. Remove the cover (see “Removing the cover” on page 39). The LED on the
system board near the connector for the failing dual-motor hot-swap fan will be
lit.
Attention: To ensure proper system cooling, do not remove the top cover for
more than 30 minutes during this procedure.
3. Grasp the dual-motor hot-swap fan by the finger grips on the sides of the
dual-motor hot-swap fan.
Vertical tabs
Fan 4
Fan 3
Fan 2
Fan 1
Figure 221. Fan removal

5. Lift the dual-motor hot-swap fan out of the server.
seconds.
6. If you are instructed to return the fan, follow all of the packaging instructions,

Replacing a hot-swap fan
Use this information to replace a hot-swap fan.
About this task
For proper cooling, the server requires that all four dual-motor hot-swap fans be
installed at all times.

seconds.
To replace a hot-swap fan, complete the following steps:
Procedure
4. 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.
5. Orient the fan over the fan slot in the fan assembly bracket so that the fan
connector aligns with the connector on the system board.
6. Insert the fan into the fan slot in the fan assembly bracket and press it down
until it is seated correctly in the slot and the fan connector is seated correctly in
the connector on the system board.
Vertical tabs
Fan 4
Fan 3
Fan 2
Fan 1
Figure 222. Fan installation
Note: Make sure that the newly-installed fan aligns horizontally with other
correctly-seated fans for proper installation.

Removing the 2.5-inch simple-swap/hot-swap hard disk drive
backplate assembly/backplane
Use this information to remove the 2.5-inch simple-swap/hot-swap hard disk drive
backplate assembly/backplane.
About this task
To remove the 2.5-inch simple-swap/hot-swap hard disk drive backplate

assembly/backplane, complete the following steps:
Procedure
4. Pull the hard disk drives out of the server slightly to disengage them from the
hard disk drive backplate assembly/backplane (see “Removing a hot-swap
hard disk drive” on page 270).
5. To obtain more working room, remove the fans (see “Removing a hot-swap
fan” on page 336).
6. Lift the two front tabs and rotate the backplate assembly/backplane toward the
rear of the server to remove the backplate assembly/backplane.
Hard disk drive

backplane
SAS
signal
cable
Configuration
cable
Power
cable
Figure 223. 2.5-inch simple-swap/hot-swap hard disk drive backplate assembly/backplane

removal
7. Disconnect all cables from the hard disk drive backplane.

8. If you are instructed to return the hard disk drive backplate
assembly/backplane, follow all packaging instructions, and use any packaging
materials for shipping that are supplied to you.

Replacing the 2.5-inch simple-swap/hot-swap hard disk drive
Use this information to replace the 2.5-inch simple-swap/hot-swap hard disk drive
About this task
To install the 2.5-inch simple-swap/hot-swap hard disk drive backplate

Procedure
2. Reconnect the signal and power cables to the system board. Route the signal
cable from the drive backplane along the chassis and connect it to the
SAS/SATA signal connector. Then, route the power cable from the drive
backplate assembly along the chassis and connect it to the Simple-swap SATA
power connector. See “2.5-inch hard disk drive cable connection” on page 254.
3. Align the backplate assembly/backplane with the backplate
assembly/backplane slot in the chassis and the small slots on top of the hard
disk drive cage.
4. Lower the backplate assembly/backplane into the slots on the chassis.
5. Rotate the top of the backplate assembly/backplane until the front tab clicks
into place into the latches on the chassis.
Hard disk drive

backplane
SAS
signal
cable
Configuration
cable
Power
cable

installation
6. Replace the fan bracket and fans if you removed them (see “Replacing the fan
bracket” on page 300 and “Replacing a hot-swap fan” on page 337).
7. Reinstall the hard disk drives (see “Replacing a hot-swap hard disk drive” on
page 271).
8. Install the cover (see “Replacing the cover” on page 260).

Removing the 3.5-inch simple-swap/hot-swap hard disk drive

Use this information to remove the 3.5-inch simple-swap/hot-swap hard disk drive
About this task
To remove the 3.5-inch simple-swap/hot-swap hard disk drive backplate

Procedure
4. Pull the hard disk drives or fillers out of the server slightly to disengage them
from the backplate assembly/backplane. See “Removing a simple-swap hard
disk drive” on page 273 for details.
5. To obtain more working room, remove the fans (see “Removing a hot-swap
fan” on page 336).
6. Lift the backplate assembly/backplane out of the server by pulling the latch
and lifting it up.

Power
cable SAS
signal
cable
Latch
Hard disk drive
backplate

removal
7. Disconnect the power and signal cables from the system board.
8. If you are instructed to return the hard disk drive backplate
assembly/backplane, follow all packaging instructions, and use any packaging
materials for shipping that are supplied to you.
Replacing the 3.5-inch simple-swap/hot-swap hard disk drive

Use this information to replace the 3.5-inch simple-swap/hot-swap hard disk drive
About this task
To install the 3.5-inch simple-swap/hot-swap hard disk drive backplate

Procedure
2. Align the sides of the drive backplate assembly/backplane with the slots on
the bracket.
3. Lower the backplate assembly/backplane into the slots on the chassis.
4. Rotate the top of the backplate assembly/backplane until the front tab clicks
into place into the latches on the chassis.

Power
cable SAS
signal
cable
Latch
Hard disk drive
backplate

installation
5. Connect the signal and power cables to the system board. Route the signal
cable from the drive backplane along the chassis and connect it to the
SAS/SATA signal connector. Then, route the power cable from the drive
backplate assembly along the chassis and connect it to the Simple-swap SATA
power connector. See “3.5-inch hard disk drive cable connection” on page 257
for more information.
6. Reinstall the hard disk drives and filler panels (see “Replacing a simple-swap
hard disk drive” on page 274).
7. Replace the fan bracket and fans if you removed them (see “Replacing the fan
bracket” on page 300 and “Replacing a hot-swap fan” on page 337).

Removing a USB embedded hypervisor flash device
Use this information to remove a USB embedded hypervisor flash device.
About this task
To remove a USB hypervisor flash device, complete the following steps:
Procedure
4. Remove the flash device:
Lockbar
USB embedded
hypervisor
flash device
Figure 227. USB hypervisor flash device removal
a. Unlock the retention latch on the USB connector by pushing down the blue
locking collar.
b. Grasp the flash device and pull to remove it from the connector.
5. If you are instructed to return the flash device, follow all packaging
you.

Replacing a USB embedded hypervisor flash device
Use this information to replace a USB embedded hypervisor flash device.
About this task
To install a USB hypervisor flash device, complete the following steps:
Procedure
4. Remove the PCI riser-card assembly (see “Removing a PCI riser-card assembly”
on page 301).
5. Install the flash device:
Lockbar
USB embedded
hypervisor
flash device
Figure 228. USB hypervisor flash device installation
a. Align the flash device with the connector on the system board and push it
into the USB connector until it is firmly seated.
b. Pull up the blue locking collar to lock the flash device into the USB
connector.

Removing the system battery
The following notes describe information that you must consider when replacing
the battery.
About this task

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:
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:
– Throw or immerse into water
– Heat to more than 100°C (212°F)
– Repair or disassemble
To remove the system battery, complete the following steps:
Procedure
4. If necessary, lift the PCI riser-card assembly 2 out of the way (see “Removing a
5. Remove the system battery:

Battery
Figure 229. System battery removal
a. If there is a rubber cover on the battery holder, use your fingers to lift the
battery cover from the battery connector.
b. Use one finger to tilt the battery horizontally out of its socket, pushing it
away from the socket.
Attention: Neither tilt nor push the battery by using excessive force.
Figure 230. System battery removal
c. Use your thumb and index finger to lift the battery from the socket.
Attention: Do not lift the battery by using excessive force. Failing to
remove the battery properly may damage the socket on the system board.
Any damage to the socket may require replacing the system board.
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
The following notes describe information that you must consider when replacing
the system battery in the server.
About this task

v When replacing the system 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 sales representative or IBM 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:
When replacing the lithium battery, use only IBM Part Number 33F8354 or an
equivalent type battery recommended by the manufacturer. If your system has a
module containing a lithium battery, replace it only with the same module type
made by the same manufacturer. The battery contains lithium and can explode if
not properly used, handled, or disposed of.
Do not:
v Throw or immerse into water
v Heat to more than 100°C (212°F)
v Repair or disassemble
To install the replacement system battery, complete the following steps:
Procedure
1. Follow any special handling and installation instructions that come with the
replacement battery.
5. If necessary, lift the PCI riser-card assembly 2 out of the way (see “Removing
a PCI riser-card assembly” on page 301).
6. Insert the new battery:

Battery
Figure 231. System battery installation
a. Tilt the battery so that you can insert it into the socket on the side opposite
the battery clip.
Figure 232. System battery installation
b. Press the battery down into the socket until it clicks into place. Make sure
that the battery clip holds the battery securely.
c. If you removed a rubber cover from the battery holder, use your fingers to
install the battery cover on top of the battery connector.
7. Reinstall the PCI riser-card assembly 2 (see “Replacing a PCI riser-card
assembly” on page 302), if necessary.
10. Reconnect the external cables; then, reconnect the power cords and turn on
the peripheral devices and the server.
11. 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 154 for details.
Removing the operator information panel assembly

Use this information to remove the operator information panel assembly.
About this task
To remove the operator information panel, complete the following steps.
Procedure
4. Disconnect the cable from the back of the operator information panel assembly.
5. Pull up the blue points slightly on the rear of the panel toward the front of the
server.
panel
Figure 233. Operator information panel removal
6. From the front of the server, carefully pull the assembly out of the server while
you move it slightly from side to side.
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.

Replacing the operator information panel assembly
Use this information to replace the operator information panel assembly.
About this task
To install the operator information panel, complete the following steps.
Procedure
4. From the front of the server, slide the operator information panel into the
server until it clicks into place.
panel
Figure 234. Operator information panel installation
5. Inside the server, connect the cable to the rear of the operator information panel
assembly. The following illustration shows the cable routing for the operator
information panel.
The following notes describe additional information when you install the cable:
v To connect the operator information panel cable on the system board, press
evenly on the cable. Pressing on one side of the cable might cause damage to
the cable or connector.
v The operator information panel cable must pass through the chassis latch
between fan 3 and fan 4 in order not to impede the fan cage.

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

Use this information to remove a microprocessor and heat sink.
About this task
Attention:
v Microprocessors are to be removed only by trained technicians.
Important: Always use the microprocessor installation tool to remove a
v Do not allow the thermal grease on the microprocessor and heat sink to come in
contact with anything. Contact with any surface can compromise the thermal
grease and the microprocessor socket.
v Dropping the microprocessor during installation or removal can damage the
contacts.
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.
Note: Be sure to use the installation tool that comes with your microprocessor
installation tool assembly. The tools are similar in function and design, however
Tool A has one setting for installing one size of microprocessor, and supports the
following families of microprocessors: E5-26xx, E5-46xx. Installation Tool B has two
settings for installing two different sizes of microprocessors. The settings that are
marked on Tool B are “L” for smaller low core microprocessors, and “H” for larger
high core microprocessors. Installation Tool B supports the following families of
microprocessors: E5-26xx, E5-46xx, E5-26xx v2, E5-46xx v2.

Installation tool
Installation tool
Microprocessor
Cover
Microprocessor
To remove a microprocessor and heat sink, complete the following steps:
Procedure
5. Locate the microprocessor to be removed (see “System-board internal
6. Remove the heat sink.
Attention: 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, you must wipe off the
contaminated thermal material on the microprocessor or heat sink with the
alcohol wipes and reapply clean thermal grease to the heat sink.
a. Open the heat sink retention module release lever to the fully open
position.
b. Lift the heat sink out of the server. After removal, place the heat sink (with
the thermal grease side up) on a clean, flat surface.

Figure 236. Heat sink removal
7. Open the microprocessor socket release levers and retainer.
Microprocessor
release lever
Microprocessor
Microprocessor
release lever
open it.
Attention: Do not touch the microprocessor contacts. Contaminants on
the microprocessor contacts, such as oil from your skin, can cause
connection failures between the contacts and the socket.
8. Remove the microprocessor from the socket.
a. Select the empty installation tool and ensure that the handle is in the open
position. If the installation tool handle is not in the open position, use the
following instructions for your installation tool:
v If using Installation Tool A, twist the microprocessor installation tool
handle counterclockwise to the open position.

Handle
Installation tool
v If using Installation Tool B,1lift the interlock latch and hold it up

while you2twist the microprocessor installation tool handle
counterclockwise to the open position, and then release the interlock
latch. The following illustration of the installation tool shows the
location of the interlock latch and counterclockwise rotation of the
handle before loading the microprocessor.
b. Align the installation tool with the screws, as shown in the following
graphic, and lower the installation tool on the microprocessor. The
installation tool rests flush on the socket only when it is aligned correctly.

Installation tool
Microprocessor Alignment
pins
c. Using the following instructions for your installation tool to remove the
microprocessor.
v If using Installation Tool A, gently twist the handle clockwise to the
closed position and lift the microprocessor out of the socket.
v If using Installation Tool B, gently twist the handle of the installation
tool clockwise until it locks in the “H” or “L” position, depending on
the size of microprocessor, and then lift the microprocessor out of the
socket.
Handle
Installation
tool
Microprocessor
d. Lift the microprocessor out of the socket.

Installation tool
Microprocessor
Figure 242. Installation tool removal
9. If you do not intend to install a microprocessor on the socket, install the

socket cover that you removed in step 8 on page 361 on the microprocessor
socket.
Attention: The pins on the socket are fragile. Any damage to the pins may
require replacing the system board.
10. If you are instructed to return the microprocessor, follow all packaging
instructions, and use any packaging materials for shipping that are supplied
to you.
Replacing a microprocessor and heat sink

Use this information to replace a microprocessor and heat sink.
About this task
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:
v Microprocessors are to be installed only by trained technicians.
Important: Always use the microprocessor installation tool to install a
v The server supports up to two Intel Xeon™ E5-2600 series multi-core
microprocessors, which are designed for the LGA 2011 socket. See
list of supported microprocessors.
v Do not mix microprocessors with different cores in the same server.
v The first microprocessor must always be installed in microprocessor socket 1 on
the system board.
v When one microprocessor is installed, the air baffle must be installed to provide
proper system cooling.
v Do not remove the first microprocessor from the system board when you install
the second microprocessor.
v Before you install the microprocessor, go to Table 2 on page 9 for detailed power
supply configurations.

v When you install the second microprocessor, you must also install additional
memory and the fourth fan. See “Installing a memory module” on page 54 for
details about the 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 to determine
whether you have to update the server firmware. To download the latest level of
server firmware and other code updates for your server, go to
v The microprocessor speeds are automatically set for this server; therefore, you
do not have to set any microprocessor frequency-selection jumpers or switches.
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 more information about applying or
working with thermal grease, see “Thermal grease” on page 141.
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 sales
representative or IBM reseller.
There are two types of microprocessor installation tools. The tools are similar in
function and design, however Tool A has one setting for installing one size of
microprocessor, and supports the following families of microprocessors: E5-26xx,
E5-46xx. Installation Tool B has two settings for installing two different sizes of
microprocessors. The settings that are marked on Tool B are “L” for smaller low
core microprocessors, and “H” for larger high core microprocessors. Installation
Tool B supports the following families of microprocessors: E5-26xx, E5-46xx,
E5-26xx v2, E5-46xx v2.

Installation tool
Installation tool
Microprocessor
Cover
Microprocessor
To replace a microprocessor and heat sink, complete the following steps:
Procedure
5. Rotate the heat sink retention module release lever to the open position.

Figure 244. Heat-sink lever rotation
6. Open the microprocessor socket release levers and retainer:
open it.
Attention: Do not touch the connectors on the microprocessor and the
microprocessor socket.
7. Install the microprocessor on the microprocessor socket:
a. Touch the static-protective package that contains the new microprocessor
to any unpainted on the chassis or any unpainted metal surface on any other
grounded rack component; then, carefully remove the microprocessor from
the package.
b. Release the sides of the cover and remove the cover from the installation
tool. The microprocessor is preinstalled on the installation tool.

Installation tool
Microprocessor
Cover
Figure 246. Installation tool cover removal
Note: Do not touch the microprocessor contacts. Contaminants on the

microprocessor contacts, such as oil from your skin, can cause connection
failures between the contacts and the socket.
c. Align the installation tool with the microprocessor socket. The installation
tool rests flush on the socket only if properly aligned.
d. Install the microprocessor using the following instructions for your

installation tool.
v If using Installation Tool A, twist the handle on the microprocessor tool
assembly counterclockwise to the open position to insert the
microprocessor into the socket, and lift the installation tool out of the
socket.
v If using Installation Tool B, twist the handle of the installation tool
assembly counterclockwise until the microprocessor is inserted into the
socket, and lift the installation tool out of the socket. The following
illustration shows the tool handle in the open position.

E5-x6xx
E5-x6xx v2
L
H
Figure 249. Installation Tool B
Attention:
v Do not press the microprocessor into the socket.
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.
8. Remove the microprocessor socket cover, tape, or label from the surface of the
microprocessor socket, if one is present. Store the socket cover in a safe place.

Socket cover
Microprocessor
Figure 250. Socket cover removal

9. Close the microprocessor socket release levers and retainer:
Microprocessor
release lever
Microprocessor
Microprocessor
release lever
Figure 251. Microprocessor socket levers and retainer engagement
a. Close the microprocessor retainer on the microprocessor socket.

b. Identify which release lever is labeled as the first release lever to close and
close it.
c. Close the second release lever on the microprocessor socket.
10. Install the heat sink.
Attention:
v Do not set down the heat sink after you remove the plastic cover.
v 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” on page 141 for more information.

Figure 252. Thermal grease
a. Remove the plastic protective cover from the bottom of the heat sink.
b. Position the heat sink over the microprocessor. The heat sink is keyed to
assist with proper alignment.
Figure 253. Heat sink installation
c. Align and place the heat sink on top of the microprocessor in the retention
bracket, thermal material side down.
d. Press firmly on the heat sink.
e. Rotate the heat sink retention module release lever to the closed position
and hook it underneath the lock tab.
11. Reinstall the air baffle (see “Replacing the air baffle” on page 262).
Results

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. Use this information to replace damaged or contaminated
thermal grease on the microprocessor and heat sink.
About this task
When you are installing the heat sink on the same microprocessor that it 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.
Notes:
v Read the safety information that begins on “Safety” on page vii.
v Read the “Installation guidelines” on page 36.
v Read “Handling static-sensitive devices” on page 39.
To replace damaged or contaminated thermal grease on the microprocessor and

heat sink, complete the following steps:
Procedure
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.
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.
0.02 mL of thermal
grease
Microprocessor
Figure 254. Thermal grease distribution

Note: If the grease is properly applied, approximately half of the grease will
remain in the syringe.
Figure 255. Syringe
6. Install the heat sink onto the microprocessor as described in 10 on page 362.
Removing the heat-sink retention module

Use this information to remove the heat-sink retention module.
About this task
To remove a heat-sink retention module, complete the following steps:
Procedure
5. Remove the heat sink (see “Removing a microprocessor and heat sink” on page
351).
Attention: When you remove a microprocessor and heat sink, be sure to keep
each heat sink with its microprocessor for reinstallation.
6. Use a screwdriver and remove the four screws that secure the retention module
to the system board; then, lift the retention module from the system board.
Figure 256. Heat-sink retention module removal
7. If you are instructed to return the heat-sink retention module, follow all the
packaging instructions, and use any packaging materials for shipping that are
supplied to you.

Replacing the heat-sink retention module
Use this information to replace the heat-sink retention module.
About this task
To install a heat-sink retention module, complete the following steps:
Procedure
5. Align the retention module with the holes on the system board.
6. Use a screwdriver to reinstall the four screws.
Figure 257. Heat-sink retention module installation
7. Reinstall the heat sink (see “Replacing a microprocessor and heat sink” on
page 356).
Attention: Make sure that you install each heat sink with its paired
microprocessor.
8. Reinstall the air baffle (see “Replacing the air baffle” on page 262).

Removing the system board
Use this information to remove the system board.
About this task
Notes:
1. 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.
2. When you replace the system board, make sure that you remove the Integrated
Management Module Advanced Upgrade and place it on the new system
board. For information about the Advanced Upgrade, see “Using the remote
presence and blue-screen capture features” on page 163.
3. Before you replace the system board, make sure that you back up any features
on demand (FoD) keys that were enabled. Reactivate any Features on Demand
features. Instructions for automating the activation of features and installing
activation keys is in the IBM Features on Demand User's Guide. To download the
document, go to /http://www.ibm.com/systems/x/fod/, log in, and click
Help.
To remove the system board, complete the following steps:
Procedure
1. Read the safety information that begins on “Safety” on page vii, “Handling
static-sensitive devices” on page 39, and “Installation guidelines” on page 36.
2. Turn off the server and any attached devices.
3. Turn off the peripheral devices and disconnect all power cords.
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.
4. Pull the power supplies out of the rear of the server, just enough to disengage
them from the server.
6. Remove all PCI riser-card assemblies and adapters (see “Removing a PCI
riser-card assembly” on page 301 and “Removing an adapter” on page 304).
8. Remove the ServeRAID SAS/SATA controller (see “Removing an adapter” on
page 304).
9. Remove the dual-port network adapter (see “Removing the dual-port network
adapter” on page 318).
10. Remove the memory modules and set them aside on a static-protective surface
for reinstallation (see “Removing a memory module” on page 288).
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.
11. (Trained technician only) 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 351).

Notes:
a. Remove the socket covers from the microprocessor sockets on the new
system board and place them on the microprocessor sockets of the system
board you are removing.
b. Do not allow the thermal grease to come in contact with anything, and
keep each heat sink paired with its microprocessor for reinstallation.
Contact with any surface can compromise the thermal grease and the
microprocessor socket. A mismatch between the microprocessor and its
original heat sink can require the installation of a new heat sink.
12. Remove the system battery (see “Removing the system battery” on page 345).
13. 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 (see “Internal cable routing and connectors” on page 249 for
more information).
Attention: Disengage all latches, release tabs or locks on cable connectors
when you disconnect all cables from the system board. 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 may require replacing the system board.
14. Remove the hot-swap fans (see “Removing a hot-swap fan” on page 336).
15. Pull out and lift up the pin and the thumbscrews on each side of the system
board.

Pin
Thumbscrew
Figure 258. System board removal
16. 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.
17. If you are instructed to return the system board, follow all packaging
instructions, and use any packaging materials for shipping that are supplied
to you.
Attention: Make sure to place the socket covers for the microprocessor
sockets on the system board before returning the system board.

Replacing the system board
Use this information to replace the system board.
About this task
Notes:
1. When you reassemble the components in the server, be sure to route all cables
carefully so that they are not exposed to excessive pressure.
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. See “Updating the firmware” on
page 149, “Updating the Universal Unique Identifier (UUID)” on page 170, and
“Updating the DMI/SMBIOS data” on page 172 for more information.
3. When you replace the system board, make sure that you remove the Integrated
Management Module Advanced Upgrade and place it on the new system
board. For information about the Advanced Upgrade, see “Using the remote
presence and blue-screen capture features” on page 163.
4. Reactivate any Features on Demand features. Instructions for automating the
activation of features and installing activation keys is in the IBM Features on
Demand User's Guide. To download the document, go to /http://
www.ibm.com/systems/x/fod/, log in, and click Help.
To install the system board, complete the following steps:
Procedure
1. Read the safety information that begins on “Safety” on page vii, “Handling
static-sensitive devices” on page 39, and “Installation guidelines” on page 36.
2. Align the system board at an angle, as shown in the illustration; then, rotate
and lower it flat and slide it back toward the rear of the server. Make sure
that the rear connectors extend through the rear of the chassis.

Pin
Thumbscrew
Figure 259. System board installation
3. Reconnect to the system board the cables that you disconnected in step 13 of
“Removing the system board” on page 367 (see “Internal cable routing and
4. Rotate the system-board thumbscrews toward the rear of the server until the
latch clicks into place.
5. Install the hot-swap fans (see “Replacing a hot-swap fan” on page 337).
6. (Trained technician only) Install the microprocessor and heat sink (see
“Replacing a microprocessor and heat sink” on page 356).
7. Install the memory modules (see “Installing a memory module” on page 54).
8. If necessary, install the virtual media key.
9. Install the system battery (see “Replacing the system battery” on page 347).
10. Install the air baffle (see “Replacing the air baffle” on page 262).
11. Install the PCI riser-card assemblies and adapters, if any were installed (see
“Replacing an adapter” on page 305 and “Replacing a PCI riser-card

13. Push the power supplies back into the server.
17. 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 154 for more details.
18. Either update the server with the latest RAID firmware or restore the
pre-existing firmware from a diskette or CD image.
19. Update the UUID (see “Updating the Universal Unique Identifier (UUID)” on
page 170).
20. Update the DMI/SMBIOS (see “Updating the DMI/SMBIOS data” on page
172).
21. Reactivate any Features on Demand features.

Appendix A. Integrated management module II (IMM2) error
messages
When a hardware event is detected by the IMM on the server, the IMM 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 system-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
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
Whether user action is required to correct the problem.

40000001-00000000
CIM Information
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
The actions that 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.
Below is the list of IMM2 error messages and suggested actions to correct the
detected server problems. For more information about IMM2, see the Integrated
Management Module II User's Guide at http://www.ibm.com/support/entry/portal/
docdisplay?lndocid=MIGR-5086346.
40000001-00000000 Management Controller [arg1] Network Initialization Complete.

Explanation: This message is for the use case where a Management Controller network has completed initialization.
May also be shown as 4000000100000000 or 0x4000000100000000
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.

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].
Explanation: This message is for the use case where a user modifies the Ethernet Port data rate.
Severity: Info
Alert Category: none
Serviceable: No
SNMP Trap ID:
40000004-00000000 Ethernet Duplex setting modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where A user modifies the Ethernet Port duplex setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
Appendix A. Integrated management module II (IMM2) error messages 375

40000005-00000000 • 40000007-00000000
40000005-00000000 Ethernet MTU setting modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where a user modifies the Ethernet Port MTU setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000006-00000000 Ethernet locally administered MAC address modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where a user modifies the Ethernet Port MAC address setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000007-00000000 Ethernet interface [arg1] by user [arg2].

Explanation: This message is for the use case where a user enables or disabled the ethernet interface.
Severity: Info
Serviceable: No
SNMP Trap ID:

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
40000009-00000000 IP address of network interface modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where user modifies the IP address of a Management Controller.
Severity: Info
Serviceable: No
SNMP Trap ID: 37
4000000a-00000000 IP subnet mask of network interface modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where a user modifies the IP subnet mask of a Management
Controller.
May also be shown as 4000000a00000000 or 0x4000000a00000000
Severity: Info
Serviceable: No
SNMP Trap ID:

4000000b-00000000 • 4000000d-00000000
4000000b-00000000 IP address of default gateway modified from [arg1] to [arg2] by user [arg3].
Explanation: This message is for the use case where a user modifies the default gateway IP address of a
Management Controller.
May also be shown as 4000000b00000000 or 0x4000000b00000000
Severity: Info
Serviceable: No
SNMP Trap ID:
4000000c-00000000 OS Watchdog response [arg1] by [arg2] .

Explanation: This message is for the use case where an OS Watchdog has been enabled or disabled by a user.
May also be shown as 4000000c00000000 or 0x4000000c00000000
Severity: Warning
Serviceable: No
SNMP Trap ID:
4000000d-00000000 DHCP[[arg1]] failure, no IP address assigned.

Explanation: This message is for the use case where a DHCP server fails to assign an IP address to a Management
Controller.
May also be shown as 4000000d00000000 or 0x4000000d00000000
Severity: Warning
Serviceable: No
SNMP Trap ID:
User response: Complete the following steps until the problem is solved:
1. Make sure that the IMM network cable is connected.
2. Make sure that there is a DHCP server on the network that can assign an IP address to the IMM.

4000000e-00000000 • 40000010-00000000
4000000e-00000000 Remote Login Successful. Login ID: [arg1] from [arg2] at IP address [arg3].
Explanation: This message is for the use case where a user successfully logs in to a Management Controller.
May also be shown as 4000000e00000000 or 0x4000000e00000000
Severity: Info
Alert Category: System - Remote Login
Serviceable: No
SNMP Trap ID: 30
4000000f-00000000 Attempting to [arg1] server [arg2] by user [arg3].

Explanation: This message is for the use case where a user is using the Management Controller to perform a power
function on the system.
May also be shown as 4000000f00000000 or 0x4000000f00000000
Severity: Info
Serviceable: No
SNMP Trap ID:
40000010-00000000 Security: Userid: [arg1] had [arg2] login failures from WEB client at IP address [arg3].
Explanation: This message is for the use case where a user has failed to log in to a Management Controller from a
web browser.
Severity: Warning
Serviceable: No
SNMP Trap ID: 30
1. Make sure that the correct login ID and password are being used.
2. Have the system administrator reset the login ID or password.

40000011-00000000 • 40000013-00000000
40000011-00000000 Security: Login ID: [arg1] had [arg2] login failures from CLI at [arg3].
Explanation: This message is for the use case where a user has failed to log in to a Management Controller 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].
Explanation: This message is for the use case where a remote user has failed to establish a remote control session
from a Web browser session.
Severity: Info
Serviceable: No
SNMP Trap ID: 30
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].
Explanation: This message is for the use case where a user has failed to log in to a Management Controller from a
telnet session.
Severity: Info
Serviceable: No
SNMP Trap ID: 30
User response: Make sure that the correct login ID and password are being used.

40000014-00000000 • 40000016-00000000
40000014-00000000 The [arg1] on system [arg2] cleared by user [arg3].

Explanation: This message is for the use case where a Management Controller Event Log on a system is cleared by
a user.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000015-00000000 Management Controller [arg1] reset was initiated by user [arg2].

Explanation: This message is for the use case where a Management Controller reset is initiated by a user.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000016-00000000 ENET[[arg1]] DHCP-HSTN=[arg2], DN=[arg3], IP@=[arg4], SN=[arg5], GW@=[arg6],

DNS1@=[arg7] .
Explanation: This message is for the use case where a Management Controller IP address and configuration has
been assigned by the DHCP server.
Severity: Info
Serviceable: No
SNMP Trap ID:

40000017-00000000 • 40000019-00000000
40000017-00000000 ENET[[arg1]] IP-Cfg:HstName=[arg2], IP@=[arg3] ,NetMsk=[arg4], GW@=[arg5] .

Explanation: This message is for the use case where a Management Controller IP address and configuration has
been assigned statically using user data.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000018-00000000 LAN: Ethernet[[arg1]] interface is no longer active.

Explanation: This message is for the use case where a Management Controller ethernet interface is no longer active.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000019-00000000 LAN: Ethernet[[arg1]] interface is now active.

Explanation: This message is for the use case where a Management Controller ethernet interface is now active.
Severity: Info
Serviceable: No
SNMP Trap ID:

4000001a-00000000 • 4000001c-00000000
4000001a-00000000 DHCP setting changed to [arg1] by user [arg2].

Explanation: This message is for the use case where a user changes the DHCP setting.
Severity: Info
Serviceable: No
SNMP Trap ID:
4000001b-00000000 Management Controller [arg1]: Configuration restored from a file by user [arg2].
Explanation: This message is for the use case where a user restores a Management Controller configuration from a
file.
Severity: Info
Serviceable: No
SNMP Trap ID:
4000001c-00000000 Watchdog [arg1] Screen Capture Occurred .

Explanation: This message is for the use case where an operating system error has occurred and the screen was
captured.
Severity: Info
Alert Category: System - other
Serviceable: No
SNMP Trap ID: 22
User response: If there was no operating-system error, complete the following steps until the problem is solved:
1. Reconfigure the watchdog timer to a higher value.
2. Make sure that the IMM Ethernet-over-USB interface is enabled.
3. Reinstall the RNDIS or cdc_ether device driver for the operating system.
4. Disable the watchdog.
If there was an operating-system error, check the integrity of the installed operating system.

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

Explanation: This message is for the use case where an operating system error has occurred and the screen capture
failed.
Severity: Error
Serviceable: No
SNMP Trap ID: 22
2. Make sure that the IMM Ethernet over USB interface is enabled.
4. Disable the watchdog. Check the integrity of the installed operating system.
5. 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.
4000001e-00000000 Running the backup Management Controller [arg1] main application.

Explanation: This message is for the use case where a Management Controller has resorted to running the backup
main application.
Severity: Warning
Serviceable: No
SNMP Trap ID: 22
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.

4000001f-00000000 • 40000021-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.
Explanation: This message is for the use case where a 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.
40000020-00000000 Management Controller [arg1] Reset was caused by restoring default values.
Explanation: This message is for the use case where a Management Controller has been reset due to a user restoring
the configuration to default values.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000021-00000000 Management Controller [arg1] clock has been set from NTP server [arg2].
Explanation: This message is for the use case where a Management Controller clock has been set from the Network
Time Protocol server.
Severity: Info
Serviceable: No
SNMP Trap ID:

40000022-00000000 • 40000024-00000000
40000022-00000000 SSL data in the Management Controller [arg1] configuruation data is invalid. Clearing
configuration data region and disabling SSL.
Explanation: This message is for the use case where a 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
1. Make sure that the certificate that you are importing is correct.
2. Try to import the certificate again.
40000023-00000000 Flash of [arg1] from [arg2] succeeded for user [arg3] .

Explanation: This message is for the use case where a 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:
40000024-00000000 Flash of [arg1] from [arg2] failed for user [arg3].

Explanation: This message is for the use case where a 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

40000025-00000000 • 40000027-00000000
40000025-00000000 The [arg1] on system [arg2] is 75% full.

Explanation: This message is for the use case where a 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
40000026-00000000 The [arg1] on system [arg2] is 100% full.

Explanation: This message is for the use case where a 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
2. Make sure that the IMM Ethernet-over-USB interface is enabled.
5. Check the integrity of the installed operating system.

40000028-00000000 • 4000002a-00000000
40000028-00000000 Management Controller Test Alert Generated by [arg1].

Explanation: This message is for the use case where a user has generated a Test Alert.
Severity: Info
Serviceable: No
SNMP Trap ID: 22
40000029-00000000 Security: Userid: [arg1] had [arg2] login failures from an SSH client at IP address [arg3].
Explanation: This message is for the use case where a user has failed to log in to a Management Controller 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.
Explanation: This message is for the use case where a 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 • 4000002d-00000000
4000002b-00000000 Domain name set to [arg1].

Explanation: Domain name set by user
Severity: Info
Serviceable: No
SNMP Trap ID:
4000002c-00000000 Domain Source changed to [arg1] by user [arg2].

Explanation: Domain source changed by user
Severity: Info
Serviceable: No
SNMP Trap ID:
4000002d-00000000 DDNS setting changed to [arg1] by user [arg2].

Explanation: DDNS setting changed by user
Severity: Info
Serviceable: No
SNMP Trap ID:

4000002e-00000000 • 40000030-00000000
4000002e-00000000 DDNS registration successful. The domain name is [arg1].

Explanation: DDNS registation and values
Severity: Info
Serviceable: No
SNMP Trap ID:
4000002f-00000000 IPv6 enabled by user [arg1] .

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

Explanation: IPv6 protocol is disabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:

40000031-00000000 • 40000033-00000000
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:
40000032-00000000 IPv6 DHCP enabled by user [arg1].

Explanation: IPv6 DHCP assignment method is enabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
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:

40000034-00000000 • 40000036-00000000
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:
40000035-00000000 IPv6 DHCP disabled by user [arg1].

Explanation: IPv6 DHCP assignment method is disabled by user
Severity: Info
Serviceable: No
SNMP Trap ID:
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:

40000037-00000000 • 40000039-00000000
40000037-00000000 ENET[[arg1]] IPv6-LinkLocal:HstName=[arg2], IP@=[arg3] ,Pref=[arg4] .

Explanation: IPv6 Link Local address is active
Severity: Info
Serviceable: No
SNMP Trap ID:
40000038-00000000 ENET[[arg1]] IPv6-Static:HstName=[arg2], IP@=[arg3] ,Pref=[arg4], GW@=[arg5] .

Explanation: IPv6 Static address is active
Severity: Info
Serviceable: No
SNMP Trap ID:
40000039-00000000 ENET[[arg1]] DHCPv6-HSTN=[arg2], DN=[arg3], IP@=[arg4], Pref=[arg5].

Explanation: IPv6 DHCP-assigned address is active
Severity: Info
Serviceable: No
SNMP Trap ID:

4000003a-00000000 • 4000003c-00000000
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:
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:
1. Make sure that the IMM network cable is connected.
2. 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:
2. Make sure that the IMM Ethernet over USB interface is enabled.
5. Check the integrity of the installed operating system.

4000003d-00000000 • 4000003f-00000000
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:
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:
4000003f-00000000 Web-HTTP port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the Web HTTP port number
Severity: Info
Serviceable: No
SNMP Trap ID:

40000040-00000000 • 40000042-00000000
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:
40000041-00000000 CIM/XML HTTP port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the CIM HTTP port number
Severity: Info
Serviceable: No
SNMP Trap ID:
40000042-00000000 CIM/XML HTTPS port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the CIM HTTPS port number
Severity: Info
Serviceable: No
SNMP Trap ID:

40000043-00000000 • 40000045-00000000
40000043-00000000 SNMP Agent port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the SNMP Agent port number
Severity: Info
Serviceable: No
SNMP Trap ID:
40000044-00000000 SNMP Traps port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the SNMP Traps port number
Severity: Info
Serviceable: No
SNMP Trap ID:
40000045-00000000 Syslog port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the Syslog receiver port number
Severity: Info
Serviceable: No
SNMP Trap ID:

40000046-00000000 • 40000048-00000000
40000046-00000000 Remote Presence port number changed from [arg1] to [arg2] by user [arg3].
Explanation: A user has modified the Remote Presence port number
Severity: Info
Serviceable: No
SNMP Trap ID:
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:
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:

40000049-00000000 • 4000004b-00000000
40000049-00000000 SNMP [arg1] enabled by user [arg2] .

Explanation: A user enabled SNMPv1 or SNMPv3 or Traps
Severity: Info
Serviceable: No
SNMP Trap ID:
4000004a-00000000 SNMP [arg1] disabled by user [arg2] .

Explanation: A user disabled SNMPv1 or SNMPv3 or Traps
Severity: Info
Serviceable: No
SNMP Trap ID:
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:

4000004c-00000000 • 4000004e-00000000
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:
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:
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:

4000004f-00000000 • 40000051-00000000
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:
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:
40000051-00000000 Server Power Off Delay set to [arg1] by user [arg2].

Explanation: A user configured the Server Power Off Delay
Severity: Info
Serviceable: No
SNMP Trap ID:

40000052-00000000 • 40000054-00000000
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:
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:
40000054-00000000 Server [arg1] [arg2] cleared by user [arg3].

Explanation: A user cleared a Server Power Action.
Severity: Info
Serviceable: No
SNMP Trap ID:

40000055-00000000 • 40000057-00000000
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:
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:
40000057-00000000 Telnet [arg1] by user [arg2].

Explanation: A user enables or disables Telnet services
Severity: Info
Serviceable: No
SNMP Trap ID:

40000058-00000000 • 4000005a-00000000
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:
40000059-00000000 LAN over USB [arg1] by user [arg2].

Explanation: A user configured USB-LAN
Severity: Info
Serviceable: No
SNMP Trap ID:
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:

4000005b-00000000 • 4000005d-00000000
4000005b-00000000 Secure Web services (HTTPS) [arg1] by user [arg2].

Explanation: A user enables or disables Secure web services
Severity: Info
Serviceable: No
SNMP Trap ID:
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:
4000005d-00000000 Secure LDAP [arg1] by user [arg2].

Explanation: A user enables or disables Secure LDAP services
Severity: Info
Serviceable: No
SNMP Trap ID:

4000005e-00000000 • 40000060-00000000
4000005e-00000000 SSH [arg1] by user [arg2].

Explanation: A user enables or disables SSH services
Severity: Info
Serviceable: No
SNMP Trap ID:
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:
40000060-00000000 License key for [arg1] added by user [arg2].

Explanation: A user installs License Key
Severity: Info
Serviceable: No
SNMP Trap ID:

40000061-00000000 • 40000063-00000000
40000061-00000000 License key for [arg1] removed by user [arg2].

Explanation: A user removes a License Key
Severity: Info
Serviceable: No
SNMP Trap ID:
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:
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:

40000064-00000000 • 40000066-00000000
40000064-00000000 User [arg1] created.

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

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

Explanation: A user account was changed
Severity: Info
Serviceable: No
SNMP Trap ID:

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:
40000068-00000000 User [arg1] custom privileges set: [arg2].

Explanation: User account priveleges assigned
Severity: Info
Serviceable: No
SNMP Trap ID:
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:

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:
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:
4000006c-00000000 SSH Client key removed from user [arg1].

Explanation: User removed an SSH Client key
Severity: Info
Serviceable: No
SNMP Trap ID:

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:
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:
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:

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:
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:
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:

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:
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:
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

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
40000077-00000000 Power capping was activated by user [arg1].

Explanation: Power capping activated by user
Severity: Info
Serviceable: No
SNMP Trap ID:
40000078-00000000 Power capping was deactivated by user [arg1].

Explanation: Power capping deactivated by user
Severity: Info
Serviceable: No
SNMP Trap ID:

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:
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:
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:

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:
4000007d-00000000 Power cap and external throttling occurred.

Explanation: Power cap and external throttling occurred
Severity: Info
Serviceable: No
SNMP Trap ID:
4000007e-00000000 External throttling occurred .

Explanation: External throttling occurred
Severity: Info
Serviceable: No
SNMP Trap ID:

4000007f-00000000 • 40000081-00000000
4000007f-00000000 Power cap throttling occurred.

Explanation: Power cap throttling occurrred
Severity: Info
Serviceable: No
SNMP Trap ID:
40000080-00000000 Remote Control session started by user [arg1] in [arg2] mode.

Explanation: Remote Control session started
Severity: Info
Serviceable: No
SNMP Trap ID:
40000081-00000000 PXE boot requested by user [arg1].

Explanation: PXE boot requested
Severity: Info
Serviceable: No
SNMP Trap ID:

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
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
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 the same level on all nodes.

40000085-00000000 • 40000087-00000000
40000085-00000000 FPGA firmware mismatch between nodes [arg1] and [arg2]. Please attempt to flash the FPGA
firmware to the same level on all nodes.
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 the same level on all nodes.
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
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.

40000088-00000000 • 4000008a-00000000
40000088-00000000 Management Controller [arg1]: Configuration restoration from a file by user [arg2] completed.
file and it completes.
Severity: Info
Serviceable: No
SNMP Trap ID:
40000089-00000000 Management Controller [arg1]: Configuration restoration from a file by user [arg2] failed to
complete.
file and the restoration fails to complete.
Severity: Error
Serviceable: No
SNMP Trap ID: 22
User response:
1. Turn off the server and disconnect it from the power source. You must disconnect the server from ac power to
reset the IMM.
2. After 45 seconds, reconnect the server to the power source and turn on the server.
3. Retry the operation.
4000008a-00000000 Management Controller [arg1]: Configuration restoration from a file by user [arg2] failed to
start.
file and the restoration fails to start.
Severity: Error
Serviceable: No
SNMP Trap ID: 22
User response:
1. Turn off the server and disconnect it from the power source. You must disconnect the server from ac power to
reset the IMM.

4000008b-00000000 • 80010202-0701ffff
2. After 45 seconds, reconnect the server to the power source and turn on the server.
3. Retry the operation.
4000008b-00000000 One or more of the Storage Management IP addresses has changed.

Explanation: This message is for the use case where an IP address for the Storage Management has changed
Severity: Info
Serviceable: No
SNMP Trap ID: 37
80010002-0701ffff Numeric sensor [NumericSensorElementName] going low (lower non-critical) has asserted.
(CMOS Battery)
Explanation: This message is for the use case when an implementation has detected a Lower Non-critical sensor
going low has asserted.
May also be shown as 800100020701ffff or 0x800100020701ffff
Severity: Warning
Alert Category: Warning - Voltage
Serviceable: Yes
CIM Information: Prefix: PLAT and ID: 0476
SNMP Trap ID: 13
User response: Replace the system battery.
80010202-0701ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted.
Explanation: This message is for the use case when an implementation has detected a Lower Critical sensor going
low has asserted.
Severity: Error
Alert Category: Critical - Voltage
Serviceable: Yes
SNMP Trap ID: 1
User response: If the specified sensor is CMOS battery, replace the system battery. 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 in "Power Problems and Solving Power Problems".

80010204-1d01ffff • 80010204-1d02ffff
4. (Trained technician only) Replace the system board. (n = power supply number)
80010204-1d01ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has asserted. (Fan
1A/1B Tach)
low has asserted.
May also be shown as 800102041d01ffff or 0x800102041d01ffff
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)
2A/2B Tach)
low has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:

80010204-1d03ffff • 80010701-0701ffff
3A/3B Tach)
low has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
4A/4B Tach)
low has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
80010701-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted.
(ROMB Temp)
Explanation: This message is for the use case when an 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.

80010701-0c01ffff • 80010701-1001ffff
2. Check the server airflow. Make sure that nothing is blocking the air from coming into or preventing the air from
exiting the server.
80010701-0c01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted.
(Ambient Temp)
May also be shown as 800107010c01ffff or 0x800107010c01ffff
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
(PCI Riser 1 Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010701-1002ffff • 80010701-1003ffff
(PCI Riser 2 Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
(Rear BP Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010701-1401ffff • 80010701-1402ffff
(CPU1 VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
(CPU2 VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010701-1403ffff • 80010701-1404ffff
(DIMM AB VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
(DIMM CD VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010701-1405ffff • 80010701-1406ffff
(DIMM EF VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
(DIMM GH VR Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010701-2c01ffff • 80010701-2d01ffff
80010701-2c01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted.
(Mezz Card Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.
80010701-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has asserted.
(PCH Temp)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
exiting the server.

80010901-0701ffff • 80010901-0c01ffff
80010901-0701ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted.
(ROMB Temp)
Explanation: This message is for the use case when an 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.
exiting the server.
80010901-0c01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted.
(Ambient Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-1001ffff • 80010901-1002ffff
80010901-1001ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (PCI
Riser 1 Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
80010901-1002ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (PCI
Riser 2 Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-1003ffff • 80010901-1401ffff
80010901-1003ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (Rear
BP Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
80010901-1401ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (CPU1
VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-1402ffff • 80010901-1403ffff
80010901-1402ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (CPU2
VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
(DIMM AB VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-1404ffff • 80010901-1405ffff
(DIMM CD VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
(DIMM EF VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-1406ffff • 80010901-2c01ffff
(DIMM GH VR Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
80010901-2c01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (Mezz
Card Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.

80010901-2d01ffff • 80010902-0701ffff
80010901-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has asserted. (PCH
Temp)
high has asserted.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
exiting the server.
high 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 the following steps until the problem is solved:

80010b01-0701ffff • 80010b01-1001ffff
80010b01-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has

asserted. (ROMB Temp)
Explanation: This message is for the use case when an implementation has detected an Upper Non-recoverable
sensor going high has asserted.
May also be shown as 80010b010701ffff or 0x80010b010701ffff
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.
80010b01-0c01ffff Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has

asserted. (Ambient Temp)
May also be shown as 80010b010c01ffff or 0x80010b010c01ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (PCI Riser 1 Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

80010b01-1002ffff • 80010b01-1401ffff

asserted. (PCI Riser 2 Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (Rear BP Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (CPU1 VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

80010b01-1402ffff • 80010b01-1404ffff

asserted. (CPU2 VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (DIMM AB VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (DIMM CD VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

80010b01-1405ffff • 80010b01-2c01ffff

asserted. (DIMM EF VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (DIMM GH VR Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

asserted. (Mezz Card Temp)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0

80010b01-2d01ffff • 80030012-2301ffff
80010b01-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has

asserted. (PCH Temp)
May also be shown as 80010b012d01ffff or 0x80010b012d01ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
80030006-2101ffff Sensor [SensorElementName] has deasserted. (Sig Verify Fail)

Explanation: This message is for the use case when an implementation has detected a Sensor has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only.
80030012-2301ffff Sensor [SensorElementName] has deasserted. (OS RealTime Mod)

Severity: Info
Serviceable: No
SNMP Trap ID:

80030108-1301ffff • 8007010f-2201ffff
80030108-1301ffff Sensor [SensorElementName] has asserted. (PS Heavy Load)

Explanation: This message is for the use case when an implementation has detected a Sensor has asserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
1. Replace the power supply with higher rated power.
2. Reduce the total power consumption by removing newly added or unused option like drives or adapters.
80070101-0c01ffff Sensor [SensorElementName] has transitioned from normal to non-critical state. (Ambient
Status)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to
non-critical from normal.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 12
User response:
1. Check the microprocessor installed is Intel E5-2690.
2. Reduce the ambient temperature under 27 Celsius degree.
8007010f-2201ffff Sensor [SensorElementName] has transitioned from normal to non-critical state. (GPT Status)
May also be shown as 8007010f2201ffff or 0x8007010f2201ffff
Severity: Warning
Alert Category: Warning - Other
Serviceable: Yes
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 to Automatic.
3. Replace the corrupt disk.

8007010f-2582ffff • 80070114-2201ffff
8007010f-2582ffff Sensor [SensorElementName] has transitioned from normal to non-critical state. (I/O
Resources)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 60
User response: Complete the following step to solve PCI I/O resource errors:
1. Go to F1 Setup
2. System Settings
3. Device and I/O ports
4. PCI 64 bit Resource and choose enable
80070114-2201ffff Sensor [SensorElementName] has transitioned from normal to non-critical state. (TPM Phy
Pres Set)
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 60
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.

80070201-0301ffff • 80070201-0302ffff
80070201-0301ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 1
OverTemp)
Explanation: This message is for the use case when an implementation has detected a Sensor transitioned to critical
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
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)
80070201-0302ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 2
OverTemp)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
closed.
2. Check the ambient temperature. You must be operating within the specifications (see Features and specifications
for more information).

80070202-0701ffff • 80070204-0a01ffff
80070202-0701ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd Vol
Fault)
from less severe.
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.
80070204-0a01ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 1 Fan
Fault)
from less severe.
May also be shown as 800702040a01ffff or 0x800702040a01ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
1. Make sure that there are no obstructions, such as bundled cables, to the airflow from the power-supply fan.
2. Replace power supply n. (n = power supply number)

80070204-0a02ffff • 80070208-0a01ffff
80070204-0a02ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 2 Fan
Fault)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
80070208-0a01ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 1 Therm
Fault)
from less severe.
Severity: Error
Alert Category: Critical - Power
Serviceable: Yes
SNMP Trap ID: 4
User response:
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://www-03.ibm.com/systems/bladecenter/resources/
powerconfig.html.

80070208-0a02ffff • 8007020c-2505ffff
80070208-0a02ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (PS 2 Therm
Fault)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response:
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://www-03.ibm.com/systems/bladecenter/resources/
powerconfig.html.
8007020c-2502ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (nvDIMM 02
Status)
from less severe.
Severity: Error
Alert Category: Critical - Other
Serviceable: Yes
SNMP Trap ID: 50
User response: None
Status)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: None

8007020c-2508ffff • 8007020f-2201ffff
Status)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: None
8007020c-250bffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (nvDIMM 11
Status)
from less severe.
May also be shown as 8007020c250bffff or 0x8007020c250bffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: None
8007020f-2201ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (TXT ACM
Module)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
1. If enabling TXT is not required, disable TXT from the Setup Utility.
2. If enabling TXT is required, verify that the TPM is enabled and activated from the Setup Utility.
3. If the problem remains, contact your service representative. nvDIMM Flash :

8007020f-2582ffff • 80070214-2201ffff
8007020f-2582ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (I/O
Resources)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: Complete the following step to solve PCI I/O resource errors:
1. Go to F1 Setup
2. System Settings
3. Device and I/O ports
4. PCI 64 bit Resource and choose enable
80070214-2201ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (TPM Lock)
from less severe.
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).

80070219-0701ffff • 8007021b-0301ffff
80070219-0701ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (SysBrd
Fault)
from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
1. Check for an error LED on the system board.
4. Replace any failing device.
8007021b-0301ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 1
QPILinkErr)
from less severe.
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. Make sure the microprocessor 2 expansion board is installed correctly (see Installing the microprocessor 2
expansion board).
4. (Trained technician only) Replace microprocessor 2.
5. (Trained technician only) Replace microprocessor 2 expansion board.

8007021b-0302ffff • 80070301-0301ffff
8007021b-0302ffff Sensor [SensorElementName] has transitioned to critical from a less severe state. (CPU 2
QPILinkErr)
from less severe.
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. Make sure the microprocessor 2 expansion board is installed correctly (see Installing the microprocessor 2
expansion board).
4. (Trained technician only) Replace microprocessor 2.
5. (Trained technician only) Replace microprocessor 2 expansion board.
80070301-0301ffff Sensor [SensorElementName] has 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
User response:
that the air baffle is 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 Server Features and
specifications for more information).
3. Make sure that the heat sink for microprocessor n.

80070301-0302ffff • 80070603-0701ffff
80070301-0302ffff Sensor [SensorElementName] has transitioned to non-recoverable from a less severe state.
(CPU 2 OverTemp)
non-recoverable from less severe.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
that the air baffle is 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 Server Features and
specifications for more information).
3. Make sure that the heat sink for microprocessor n.
80070603-0701ffff Sensor [SensorElementName] has transitioned to non-recoverable. (Pwr Rail A-H Fault)
non-recoverable.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 4
User response: If the specified sensor is one of the Pwr Rail A-H Fault, please follow actions in "Power Problems
and Solving Power Problems".

80070608-0a01ffff • 80070608-0a02ffff
80070608-0a01ffff Sensor [SensorElementName] has 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.
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
80070608-0a02ffff Sensor [SensorElementName] has 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:

80070614-2201ffff • 8008010f-2101ffff
If the specified sensor is PS n 12V OV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12V UV Fault, complete the following steps until the problem is solved:
If the specified sensor is PS n 12Vaux Fault, complete the following steps until the problem is solved:
80070614-2201ffff Sensor [SensorElementName] has 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 board (see Removing the system board and
Installing the system board).
8008010f-2101ffff Device [LogicalDeviceElementName] has been added. (Phy Presence Jmp)

Explanation: This message is for the use case when an implementation has detected a Device was inserted.
Severity: Info
Serviceable: No
SNMP Trap ID:

80080128-2101ffff • 800b0108-1301ffff
80080128-2101ffff Device [LogicalDeviceElementName] has been added. (Low Security Jmp)

Explanation: This message is for the use case when an implementation has detected a Device was inserted.
Severity: Info
Serviceable: No
SNMP Trap ID:
800b0008-1301ffff Redundancy [RedundancySetElementName] has been restored. (Power Unit)

Explanation: This message is for the use case when an implementation has detected Redundancy was Restored.
Severity: Info
Alert Category: Warning - Redundant Power Supply
Serviceable: No
SNMP Trap ID: 10
800b0108-1301ffff Redundancy Lost for [RedundancySetElementName] has asserted. (Power Unit)

Explanation: This message is for the use case when 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-1e81ffff • 800b010a-1e82ffff
800b010a-1e81ffff Redundancy Lost for [RedundancySetElementName] has asserted. (Fan Zone 1)

May also be shown as 800b010a1e81ffff or 0x800b010a1e81ffff
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)
800b010a-1e82ffff Redundancy Lost for [RedundancySetElementName] has asserted. (Fan Zone 2)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
4. Reseat the fans.

800b010c-2581ffff • 800b030c-2581ffff
800b010c-2581ffff Redundancy Lost for [RedundancySetElementName] has asserted. (Backup Memory)

Severity: Error
Alert Category: Critical - Memory
Serviceable: Yes
SNMP Trap ID: 41
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.
800b0309-1301ffff Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for

[RedundancySetElementName] has asserted. (Power Resource)
Explanation: This message is for the use case when a Redundancy Set has transitioned from Redundancy Degraded
or Fully Redundant to Non-redundant:Sufficient.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 10
User response:
1. Non-redundant sufficient: Power load will be handled by remaining power supply, though the system may
throttle to avoid a power supply over-current condition.
800b030c-2581ffff Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for

[RedundancySetElementName] has asserted. (Backup Memory)
Explanation: This message is for the use case when a Redundancy Set has transitioned from Redundancy Degraded
or Fully Redundant to Non-redundant:Sufficient.
Severity: Warning
Alert Category: Warning - Memory
Serviceable: Yes
SNMP Trap ID: 43
User response:

800b0509-1301ffff • 800b050a-1e81ffff
800b0509-1301ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Power

Resource)
Explanation: This message is for the use case when a Redundancy Set has transitioned to Non-
redundant:Insufficient Resources.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 9
User response:
1. Power load may be handled by remaining power supply. The system will attempt to throttle to avoid a power
supply over-current condition. But a system shutdown may happen anyway if the power load is too great.
2. Reduce the total power consumption by removing newly added or unused options like drives or adaptors.
800b050a-1e81ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Fan

Zone 1)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
4. Reseat the fans.

800b050a-1e82ffff • 800b050c-2581ffff
800b050a-1e82ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted. (Fan

Zone 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 11
User response:
4. Reseat the fans.
800b050c-2581ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has asserted.

(Backup Memory)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f0007-0301ffff • 806f0007-0302ffff
806f0007-0301ffff [ProcessorElementName] has Failed with IERR. (CPU 1)

Explanation: This message is for the use case when an 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 specific code levels or coordinated
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)
806f0007-0302ffff [ProcessorElementName] has Failed with IERR. (CPU 2)

Explanation: This message is for the use case when an 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 firmware and device drivers are installed for all adapters and standard devices,
such as Ethernet, SCSI, and SAS. Important: Some cluster solutions require specific code levels or coordinated

806f0008-0a01ffff • 806f0009-1301ffff
806f0008-0a01ffff [PowerSupplyElementName] has been added to container [PhysicalPackageElementName].

(Power Supply 1)
Explanation: This message is for the use case when an implementation has detected a Power Supply has been
added.
May also be shown as 806f00080a01ffff or 0x806f00080a01ffff
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0008-0a02ffff [PowerSupplyElementName] has been added to container [PhysicalPackageElementName].

(Power Supply 2)
added.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0009-1301ffff [PowerSupplyElementName] has been turned off. (Host Power)

Explanation: This message is for the use case when an implementation has detected a Power Unit that has been
Disabled.
Severity: Info
Alert Category: System - Power Off
Serviceable: No
SNMP Trap ID: 23

806f000d-0400ffff • 806f000d-0402ffff
806f000d-0400ffff The Drive [StorageVolumeElementName] has been added. (Drive 0)

Explanation: This message is for the use case when an implementation has detected a Drive has been Added.
May also be shown as 806f000d0400ffff or 0x806f000d0400ffff
Severity: Info
Alert Category: Critical - Hard Disk drive
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0403ffff • 806f000d-0405ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0406ffff • 806f000d-0408ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0409ffff • 806f000d-040bffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-040affff The Drive [StorageVolumeElementName] has been added. (Drive 10)

May also be shown as 806f000d040affff or 0x806f000d040affff
Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-040bffff The Drive [StorageVolumeElementName] has been added. (Drive 11)

May also be shown as 806f000d040bffff or 0x806f000d040bffff
Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-040cffff • 806f000d-040effff
806f000d-040cffff The Drive [StorageVolumeElementName] has been added. (Drive 12)

May also be shown as 806f000d040cffff or 0x806f000d040cffff
Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-040dffff The Drive [StorageVolumeElementName] has been added. (Drive 13)

May also be shown as 806f000d040dffff or 0x806f000d040dffff
Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-040effff The Drive [StorageVolumeElementName] has been added. (Drive 14)

May also be shown as 806f000d040effff or 0x806f000d040effff
Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-040fffff • 806f000d-0411ffff
806f000d-040fffff The Drive [StorageVolumeElementName] has been added. (Drive 15)

May also be shown as 806f000d040fffff or 0x806f000d040fffff
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0412ffff • 806f000d-0414ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0415ffff • 806f000d-0417ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-0418ffff • 806f000d-041affff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-041affff The Drive [StorageVolumeElementName] has been added. (Drive 26)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-041bffff • 806f000d-041dffff
806f000d-041bffff The Drive [StorageVolumeElementName] has been added. (Drive 27)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-041cffff The Drive [StorageVolumeElementName] has been added. (Drive 28)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-041dffff The Drive [StorageVolumeElementName] has been added. (Drive 29)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

806f000d-041effff • 806f000f-220101ff
806f000d-041effff The Drive [StorageVolumeElementName] has been added. (Drive 30)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000d-041fffff The Drive [StorageVolumeElementName] has been added. (Drive 31)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
806f000f-220101ff The System [ComputerSystemElementName] has detected no memory in the system. (ABR
Status)
Explanation: This message is for the use case when an implementation has detected that memory was detected in
the system.
May also be shown as 806f000f220101ff or 0x806f000f220101ff
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, verify that the latest level of code is
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.

806f000f-220102ff • 806f000f-220103ff
Firmware Error : Sys Boot Status :
806f000f-220102ff Subsystem [MemoryElementName] has insufficient memory for operation. (ABR Status)
Explanation: This message is for the use case when an implementation has detected that the usable Memory is
insufficient for operation.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
Firmware Error : Sys Boot Status :
806f000f-220103ff The System [ComputerSystemElementName] encountered firmware error - unrecoverable boot

device failure. (ABR Status)
Explanation: This message is for the use case when an 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 :

806f000f-220104ff • 806f000f-22010aff
806f000f-220104ff The System [ComputerSystemElementName]has encountered a motherboard failure. (ABR

Status)
Explanation: This message is for the use case when an implementation has detected that a fatal motherboard failure
in the system.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: This is a UEFI detected event. The UEFI diagnostic 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 Info
Center for the appropriate user response. Firmware Error : Sys Boot Status :
806f000f-220107ff The System [ComputerSystemElementName] encountered firmware error - unrecoverable

keyboard failure. (ABR Status)
Explanation: This message is for the use case when an implementation has detected that System Firmware Error
Unrecoverable Keyboard failure has occurred.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
806f000f-22010aff The System [ComputerSystemElementName] encountered firmware error - no video device

detected. (ABR Status)
Explanation: This message is for the use case when an implementation has detected that System Firmware Error No
video device detected has occurred.
May also be shown as 806f000f22010aff or 0x806f000f22010aff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response: This is a UEFI detected event. The UEFI(POST) error 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

806f000f-22010bff • 806f000f-22010cff
806f000f-22010bff 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.
May also be shown as 806f000f22010bff or 0x806f000f22010bff
Severity: Info
Serviceable: Yes
SNMP Trap ID: 40
User response:
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 to the latest level (see Updating the firmware). Important: Some cluster solutions
5. If the problem remains, (trained service technician) replace the system board. Firmware Error : Sys Boot Status :
806f000f-22010cff CPU voltage mismatch detected on [ProcessorElementName]. (ABR Status)

Explanation: This message is for the use case when an implementation has detected a CPU voltage mismatch with
the socket voltage.
May also be shown as 806f000f22010cff or 0x806f000f22010cff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
IMM message text. Please refer to the UEFI(POST) error code in the "UEFI(POST) error code" section of the Info

806f000f-2201ffff • 806f0021-2201ffff
806f000f-2201ffff The System [ComputerSystemElementName] encountered a POST Error. (ABR Status)

Explanation: This message is for the use case when an implementation has detected a Post Error.
May also be shown as 806f000f2201ffff or 0x806f000f2201ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
806f0013-1701ffff A diagnostic interrupt has occurred on system [ComputerSystemElementName]. (NMI State)

Explanation: This message is for the use case when an 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-2201ffff Fault in slot [PhysicalConnectorSystemElementName] on system

[ComputerSystemElementName]. (No Op ROM Space)
Explanation: This message is for the use case when an 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.

806f0021-2582ffff • 806f0021-2c01ffff
3. Update the server firmware (UEFI and IMM) and adapter 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
4. Remove both adapters.
5. Replace the riser card.
6. (Trained service technicians only) Replace the system board.

[ComputerSystemElementName]. (All PCI Error)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
6. (Trained service technicians only) Replace the system board. One of PCI Error :
806f0021-2c01ffff Fault in slot [PhysicalConnectorSystemElementName] on system

[ComputerSystemElementName]. (Mezz Error)
May also be shown as 806f00212c01ffff or 0x806f00212c01ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
6. (Trained service technicians only) Replace the system board.

806f0021-3001ffff • 806f0028-2101ffff

[ComputerSystemElementName]. (PCI 1)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
6. (Trained service technicians only) Replace the system board. PCI 2 : PCI 3 : PCI 4 : PCI 5 : PCI 6 :
806f0023-2101ffff Watchdog Timer expired for [WatchdogElementName]. (IPMI Watchdog)

Explanation: This message is for the use case when an implementation has detected a Watchdog Timer Expired.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0028-2101ffff Sensor [SensorElementName] is unavailable or degraded on management system

[ComputerSystemElementName]. (TPM Cmd Failures)
Explanation: This message is for the use case when an implementation has detected a Sensor is Unavailable or
degraded.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 60
User response:

806f0107-0301ffff • 806f0107-0302ffff
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.
806f0107-0301ffff An Over-Temperature Condition has been detected on [ProcessorElementName]. (CPU 1)

Explanation: This message is for the use case when an implementation has detected an Over-Temperature Condition
Detected for Processor.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
1. Make sure that the fans are 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.
806f0107-0302ffff An Over-Temperature Condition has been detected on [ProcessorElementName]. (CPU 2)

Explanation: This message is for the use case when an implementation has detected an Over-Temperature Condition
Detected for Processor.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
1. Make sure that the fans are 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.

806f0108-0a01ffff • 806f0108-0a02ffff
806f0108-0a01ffff [PowerSupplyElementName] has Failed. (Power Supply 1)

Explanation: This message is for the use case when an 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)
806f0108-0a02ffff [PowerSupplyElementName] has Failed. (Power Supply 2)

Explanation: This message is for the use case when an 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)

806f0109-1301ffff • 806f010c-2001ffff
806f0109-1301ffff [PowerSupplyElementName] has been Power Cycled. (Host Power)

power cycled.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f010c-2001ffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

[MemoryElementName]. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
1. Refer to TIP H212293 for minimum code level.
2. Check the IBM support website for an applicable retain tip or firmware update that applies to this memory error.
3. Swap the affected DIMMs (as indicated by the error LEDs on the system board or the event logs) to a different
memory channel or microprocessor.
4. If the problem follows the DIMM, replace the failing DIMM.
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 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 technician only) Replace the affected microprocessor.
8. 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.
9. (Trained Service technician only) Replace the affected microprocessor.

806f010c-2002ffff • 806f010c-2003ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2004ffff • 806f010c-2005ffff

server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2006ffff
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

806f010c-2007ffff • 806f010c-2008ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2009ffff • 806f010c-200affff

server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.
806f010c-200affff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200affff or 0x806f010c200affff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-200bffff
server.
806f010c-200bffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200bffff or 0x806f010c200bffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

806f010c-200cffff • 806f010c-200dffff
806f010c-200cffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200cffff or 0x806f010c200cffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.
806f010c-200dffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200dffff or 0x806f010c200dffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-200effff • 806f010c-200fffff

server.
806f010c-200effff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200effff or 0x806f010c200effff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.
806f010c-200fffff Uncorrectable error detected for [PhysicalMemoryElementName] on Subsystem

May also be shown as 806f010c200fffff or 0x806f010c200fffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2010ffff
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

806f010c-2011ffff • 806f010c-2012ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2013ffff • 806f010c-2014ffff

server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2015ffff
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

806f010c-2016ffff • 806f010c-2017ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010c-2018ffff • 806f010c-2581ffff

server.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:
server.

[MemoryElementName]. (All DIMMS)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
User response:

806f010d-0400ffff • 806f010d-0401ffff
server.
9. (Trained Service technician only) Replace the affected microprocessor. One of the DIMMs :
806f010d-0400ffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 0)
Explanation: This message is for the use case when an 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)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f010d-0402ffff • 806f010d-0403ffff
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0404ffff • 806f010d-0405ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0406ffff • 806f010d-0407ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0408ffff • 806f010d-0409ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-040affff • 806f010d-040bffff
806f010d-040affff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 10)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-040bffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 11)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-040cffff • 806f010d-040dffff
806f010d-040cffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 12)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-040dffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 13)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-040effff • 806f010d-040fffff
806f010d-040effff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 14)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-040fffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 15)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0410ffff • 806f010d-0411ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0412ffff • 806f010d-0413ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0414ffff • 806f010d-0415ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0416ffff • 806f010d-0417ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-0418ffff • 806f010d-0419ffff
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-041affff • 806f010d-041bffff
806f010d-041affff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 26)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-041bffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 27)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-041cffff • 806f010d-041dffff
806f010d-041cffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 28)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-041dffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 29)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010d-041effff • 806f010d-041fffff
806f010d-041effff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 30)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)
806f010d-041fffff The Drive [StorageVolumeElementName] has been disabled due to a detected fault. (Drive 31)
fault.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
number)

806f010f-2201ffff • 806f0113-0302ffff
806f010f-2201ffff The System [ComputerSystemElementName] encountered a firmware hang. (Firmware Error)

Explanation: This message is for the use case when an implementation has detected a System Firmware Hang.
Severity: Error
Alert Category: System - Boot failure
Serviceable: Yes
SNMP Trap ID: 25
User response:
806f0113-0301ffff A bus timeout has occurred on system [ComputerSystemElementName]. (CPU 1 PECI)

Explanation: This message is for the use case when an implementation has detected a Bus Timeout.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
1. Reseat the microprocessor, and then restart the server.
2. Replace microprocessor n. (n = microprocessor number)
806f0113-0302ffff A bus timeout has occurred on system [ComputerSystemElementName]. (CPU 2 PECI)

Explanation: This message is for the use case when an implementation has detected a Bus Timeout.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:

806f011b-0701ffff • 806f011b-2502ffff
806f011b-0701ffff The connector [PhysicalConnectorElementName] has encountered a configuration error. (Front

USB)
Explanation: This message is for the use case when an implementation has detected an Interconnect Configuration
Error.
May also be shown as 806f011b0701ffff or 0x806f011b0701ffff
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, 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)
Front Video : PwrPaddle Cable :
806f011b-2502ffff The connector [PhysicalConnectorElementName] has encountered a configuration error.

(nvDIMM 02 Cable)
Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50

806f011b-2505ffff • 806f011b-2508ffff

(nvDIMM 05 Cable)
Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50

(nvDIMM 08 Cable)
Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50

806f011b-250bffff • 806f0125-0c01ffff
806f011b-250bffff The connector [PhysicalConnectorElementName] has encountered a configuration error.

(nvDIMM 11 Cable)
Error.
May also be shown as 806f011b250bffff or 0x806f011b250bffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
806f0123-2101ffff Reboot of system [ComputerSystemElementName] initiated by [WatchdogElementName].

(IPMI Watchdog)
Explanation: This message is for the use case when an implementation has detected a Reboot by a Watchdog
occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0125-0c01ffff [ManagedElementName] detected as absent. (Front Panel)

Explanation: This message is for the use case when an implementation has detected a Managed Element is Absent.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f0125-1001ffff • 806f0125-2c01ffff
806f0125-1001ffff [ManagedElementName] detected as absent. (PCI Riser 1)

Severity: Info
Serviceable: No
SNMP Trap ID:
806f0125-1002ffff [ManagedElementName] detected as absent. (PCI Riser 2)

Severity: Info
Serviceable: No
SNMP Trap ID:
806f0125-2c01ffff [ManagedElementName] detected as absent. (Mezz Card)

Severity: Info
Serviceable: No
SNMP Trap ID:

806f0207-0301ffff • 806f0207-0302ffff
806f0207-0301ffff [ProcessorElementName] has Failed with FRB1/BIST condition. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor Failed - FRB1/BIST
condition.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:
1. Make sure that the latest levels of firmware and device drivers are installed for all adapters and standard
devices, such as Ethernet, SCSI, and SAS. 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
806f0207-0302ffff [ProcessorElementName] has Failed with FRB1/BIST condition. (CPU 2)

condition.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:

806f0207-2584ffff • 806f020d-0400ffff
806f0207-2584ffff [ProcessorElementName] has Failed with FRB1/BIST condition. (All CPUs)

condition.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:
806f020d-0400ffff Failure Predicted on drive [StorageVolumeElementName] for array

[ComputerSystemElementName]. (Drive 0)
Explanation: This message is for the use case when an implementation has detected an Array Failure is Predicted.
Severity: Warning
Alert Category: System - Predicted Failure
Serviceable: Yes
SNMP Trap ID: 27
User response:
2. Reseat the following components: a. Hard disk drive b. Cable from the system board to the backplane.
disk drive. b. Cable from the system board to the backplane. c. Hard disk drive backplane. (n = hard disk drive
number)

806f020d-0401ffff • 806f020d-0402ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0403ffff • 806f020d-0404ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0405ffff • 806f020d-0406ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0407ffff • 806f020d-0408ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0409ffff • 806f020d-040affff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-040affff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-040bffff • 806f020d-040cffff
806f020d-040bffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-040cffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-040dffff • 806f020d-040effff
806f020d-040dffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-040effff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-040fffff • 806f020d-0410ffff
806f020d-040fffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0411ffff • 806f020d-0412ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0413ffff • 806f020d-0414ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0415ffff • 806f020d-0416ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0417ffff • 806f020d-0418ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-0419ffff • 806f020d-041affff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-041affff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-041bffff • 806f020d-041cffff
806f020d-041bffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-041cffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-041dffff • 806f020d-041effff
806f020d-041dffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f020d-041effff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)

806f020d-041fffff • 806f0308-0a01ffff
806f020d-041fffff Failure Predicted on drive [StorageVolumeElementName] for array

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 27
User response:
number)
806f0223-2101ffff Powering off system [ComputerSystemElementName] initiated by [WatchdogElementName].

(IPMI Watchdog)
Explanation: This message is for the use case when an implementation has detected a Poweroff by Watchdog has
occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f0308-0a01ffff [PowerSupplyElementName] has lost input. (Power Supply 1)

Explanation: This message is for the use case when an 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.

806f0308-0a02ffff • 806f030c-2001ffff
3. See Power-supply LEDs for more information. (n = power supply number)
806f0308-0a02ffff [PowerSupplyElementName] has lost input. (Power Supply 2)

that has been lost.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
1. Reconnect the power cords.
3. See Power-supply LEDs for more information. (n = power supply number)
806f030c-2001ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 1)
Explanation: This message is for the use case when an 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.
3. Make sure that the DIMMs are firmly seated and no foreign material is found in the DIMM connector. Then,
retry with the same DIMM.
4. If the problem is related to a DIMM, replace the failing DIMM indicated by the error LEDs.
5. 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.
7. (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.
8. (Trained service technician only) If the problem is related to microprocessor socket pins, replace the system
board.

806f030c-2002ffff • 806f030c-2003ffff

(DIMM 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 3)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2004ffff • 806f030c-2005ffff
board.

(DIMM 4)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 5)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2006ffff
board.

(DIMM 6)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

806f030c-2007ffff • 806f030c-2008ffff

(DIMM 7)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 8)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2009ffff • 806f030c-200affff
board.

(DIMM 9)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.
806f030c-200affff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 10)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-200bffff
board.
806f030c-200bffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 11)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

806f030c-200cffff • 806f030c-200dffff
806f030c-200cffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 12)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.
806f030c-200dffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 13)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-200effff • 806f030c-200fffff
board.
806f030c-200effff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 14)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.
806f030c-200fffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 15)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2010ffff
board.

(DIMM 16)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

806f030c-2011ffff • 806f030c-2012ffff

(DIMM 17)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 18)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2013ffff • 806f030c-2014ffff
board.

(DIMM 19)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 20)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2015ffff
board.

(DIMM 21)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

806f030c-2016ffff • 806f030c-2017ffff

(DIMM 22)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.

(DIMM 23)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41

806f030c-2018ffff • 806f0313-1701ffff
board.

(DIMM 24)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
board.
806f0313-1701ffff A software NMI has occurred on system [ComputerSystemElementName]. (NMI State)

Explanation: This message is for the use case when an 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.

806f0323-2101ffff • 806f040c-2001ffff
4. Update the firmware (UEFI and IMM).
806f0323-2101ffff Power cycle of system [ComputerSystemElementName] initiated by watchdog

[WatchdogElementName]. (IPMI Watchdog)
Explanation: This message is for the use case when an implementation has detected a Power Cycle by Watchdog
occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f040c-2001ffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 1)

Explanation: This message is for the use case when an 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).

806f040c-2002ffff • 806f040c-2003ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2004ffff • 806f040c-2005ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2006ffff • 806f040c-2007ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2008ffff • 806f040c-2009ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-200affff • 806f040c-200bffff
806f040c-200affff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 10)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
806f040c-200bffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 11)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-200cffff • 806f040c-200dffff
806f040c-200cffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 12)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
806f040c-200dffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 13)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-200effff • 806f040c-200fffff
806f040c-200effff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 14)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
806f040c-200fffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (DIMM 15)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2010ffff • 806f040c-2011ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2012ffff • 806f040c-2013ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2014ffff • 806f040c-2015ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2016ffff • 806f040c-2017ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:

806f040c-2018ffff • 806f040c-2581ffff

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
806f040c-2581ffff [PhysicalMemoryElementName] Disabled on Subsystem [MemoryElementName]. (All DIMMS)

Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response:
DIMM through the Setup utility or the Advanced Settings Utility (ASU). One of the DIMMs :

806f0413-2582ffff • 806f0507-0301ffff
806f0413-2582ffff A PCI PERR has occurred on system [ComputerSystemElementName]. (PCIs)

Explanation: This message is for the use case when an implementation has detected a PCI PERR.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
2. Reseat the affected adapters and riser cards.
5. Replace the PCIe adapters.
806f0507-0301ffff [ProcessorElementName] has a Configuration Mismatch. (CPU 1)

Explanation: This message is for the use case when an 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.
3. Make sure that the installed microprocessors are compatible with each other.
4. (Trained technician only) Reseat microprocessor n.

806f0507-0302ffff • 806f0507-2584ffff
806f0507-0302ffff [ProcessorElementName] has a Configuration Mismatch. (CPU 2)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:
806f0507-2584ffff [ProcessorElementName] has a Configuration Mismatch. (All CPUs)

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

806f050c-2001ffff • 806f050c-2002ffff
806f050c-2001ffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

Explanation: This message is for the use case when an implementation has detected that the Memory Logging Limit
has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:
4. If the error still occurs on the same DIMM, replace the affected DIMM.

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2003ffff • 806f050c-2004ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2005ffff • 806f050c-2006ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2007ffff • 806f050c-2008ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2009ffff • 806f050c-200affff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:
806f050c-200affff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-200bffff • 806f050c-200cffff
806f050c-200bffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:
806f050c-200cffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-200dffff • 806f050c-200effff
806f050c-200dffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:
806f050c-200effff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-200fffff • 806f050c-2010ffff
806f050c-200fffff Memory Logging Limit Reached for [PhysicalMemoryElementName] on Subsystem

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2011ffff • 806f050c-2012ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2013ffff • 806f050c-2014ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2015ffff • 806f050c-2016ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2017ffff • 806f050c-2018ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:

806f050c-2581ffff • 806f050d-0400ffff

has been Reached.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 43
User response:
7. (Trained technician only) Replace the affected microprocessor. One of the DIMMs :
806f050d-0400ffff Array [ComputerSystemElementName] is in critical condition. (Drive 0)

Explanation: This message is for the use case when an implementation has detected that an Array is Critical.
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 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.

806f050d-0401ffff • 806f050d-0402ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0403ffff • 806f050d-0404ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0405ffff • 806f050d-0406ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0407ffff • 806f050d-0408ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0409ffff • 806f050d-040affff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-040affff Array [ComputerSystemElementName] is in critical condition. (Drive 10)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-040bffff • 806f050d-040cffff
806f050d-040bffff Array [ComputerSystemElementName] is in critical condition. (Drive 11)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-040cffff Array [ComputerSystemElementName] is in critical condition. (Drive 12)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-040dffff • 806f050d-040effff
806f050d-040dffff Array [ComputerSystemElementName] is in critical condition. (Drive 13)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-040effff Array [ComputerSystemElementName] is in critical condition. (Drive 14)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-040fffff • 806f050d-0410ffff
806f050d-040fffff Array [ComputerSystemElementName] is in critical condition. (Drive 15)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0411ffff • 806f050d-0412ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0413ffff • 806f050d-0414ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0415ffff • 806f050d-0416ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0417ffff • 806f050d-0418ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-0419ffff • 806f050d-041affff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-041affff Array [ComputerSystemElementName] is in critical condition. (Drive 26)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-041bffff • 806f050d-041cffff
806f050d-041bffff Array [ComputerSystemElementName] is in critical condition. (Drive 27)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-041cffff Array [ComputerSystemElementName] is in critical condition. (Drive 28)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-041dffff • 806f050d-041effff
806f050d-041dffff Array [ComputerSystemElementName] is in critical condition. (Drive 29)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f050d-041effff Array [ComputerSystemElementName] is in critical condition. (Drive 30)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f050d-041fffff • 806f0513-2582ffff
806f050d-041fffff Array [ComputerSystemElementName] is in critical condition. (Drive 31)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f0513-2582ffff A PCI SERR has occurred on system [ComputerSystemElementName]. (PCIs)

Explanation: This message is for the use case when an implementation has detected a PCI SERR.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
4. Make sure that the adapter is supported. For a list of supported optional devices, see http://www.ibm.com/
6. Replace the PCIe adapters.

806f052b-2101ffff • 806f0607-0301ffff
806f052b-2101ffff Invalid or Unsupported firmware or software was detected on system

[ComputerSystemElementName]. (IMM2 FW Failover)
Explanation: This message is for the use case when an implementation has detected an Invalid/Unsupported
Firmware/Software Version.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
2. Recover the server firmware from the backup page by restarting the server.
3. Update the server firmware to the latest level (see Updating the firmware). Important: Some cluster solutions
5. If the problem remains, (trained service technician) replace the system board.
806f0607-0301ffff An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName] has asserted.
(CPU 1)
Explanation: This message is for the use case when an 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.

806f0607-0302ffff • 806f0607-2584ffff
806f0607-0302ffff An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName] has asserted.
(CPU 2)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:
3. (Trained technician only) Replace the incompatible microprocessor.
806f0607-2584ffff An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName] has asserted. (All
CPUs)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 40
User response:
3. (Trained technician only) Replace the incompatible microprocessor. One of the CPUs :

806f0608-1301ffff • 806f060d-0400ffff
806f0608-1301ffff [PowerSupplyElementName] has a Configuration Mismatch. (PS Configuration)

Explanation: This message is for the use case when an 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.
806f060d-0400ffff Array [ComputerSystemElementName] has failed. (Drive 0)

Explanation: This message is for the use case when an implementation has detected that an Array Failed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0401ffff • 806f060d-0402ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0403ffff • 806f060d-0404ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0405ffff • 806f060d-0406ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0407ffff • 806f060d-0408ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0409ffff • 806f060d-040affff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-040affff Array [ComputerSystemElementName] has failed. (Drive 10)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-040bffff • 806f060d-040cffff
806f060d-040bffff Array [ComputerSystemElementName] has failed. (Drive 11)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-040cffff Array [ComputerSystemElementName] has failed. (Drive 12)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-040dffff • 806f060d-040effff
806f060d-040dffff Array [ComputerSystemElementName] has failed. (Drive 13)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-040effff Array [ComputerSystemElementName] has failed. (Drive 14)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-040fffff • 806f060d-0410ffff
806f060d-040fffff Array [ComputerSystemElementName] has failed. (Drive 15)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0411ffff • 806f060d-0412ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0413ffff • 806f060d-0414ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0415ffff • 806f060d-0416ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0417ffff • 806f060d-0418ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-0419ffff • 806f060d-041affff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-041affff Array [ComputerSystemElementName] has failed. (Drive 26)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-041bffff • 806f060d-041cffff
806f060d-041bffff Array [ComputerSystemElementName] has failed. (Drive 27)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-041cffff Array [ComputerSystemElementName] has failed. (Drive 28)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-041dffff • 806f060d-041effff
806f060d-041dffff Array [ComputerSystemElementName] has failed. (Drive 29)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f060d-041effff Array [ComputerSystemElementName] has failed. (Drive 30)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

806f060d-041fffff • 806f070c-2002ffff
806f060d-041fffff Array [ComputerSystemElementName] has failed. (Drive 31)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
806f070c-2001ffff Configuration Error for [PhysicalMemoryElementName] on Subsystem

Explanation: This message is for the use case when an 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.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2003ffff • 806f070c-2005ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2006ffff • 806f070c-2008ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2009ffff • 806f070c-200bffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.
806f070c-200affff Configuration Error for [PhysicalMemoryElementName] on Subsystem

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.
806f070c-200bffff Configuration Error for [PhysicalMemoryElementName] on Subsystem

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-200cffff • 806f070c-200effff
806f070c-200cffff Configuration Error for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 12)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.
806f070c-200dffff Configuration Error for [PhysicalMemoryElementName] on Subsystem

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.
806f070c-200effff Configuration Error for [PhysicalMemoryElementName] on Subsystem

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-200fffff • 806f070c-2011ffff
806f070c-200fffff Configuration Error for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 15)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.
806f070c-2011ffff Configuration Error for [PhysicalMemoryElementName] on Subsystem [MemoryElementName].

(DIMM 17)
Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2012ffff • 806f070c-2014ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2015ffff • 806f070c-2017ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

806f070c-2018ffff • 806f070d-0400ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 41
and technology. One of the DIMMs :
806f070d-0400ffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 0)

Explanation: This message is for the use case when an implementation has detected that an Array Rebuild is in
Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0401ffff • 806f070d-0403ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0404ffff • 806f070d-0406ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0407ffff • 806f070d-0409ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-040affff • 806f070d-040cffff
806f070d-040affff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 10)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-040bffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 11)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-040cffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 12)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-040dffff • 806f070d-040fffff
806f070d-040dffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 13)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-040effff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 14)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-040fffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 15)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0410ffff • 806f070d-0412ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0413ffff • 806f070d-0415ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0416ffff • 806f070d-0418ffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-0419ffff • 806f070d-041bffff

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-041affff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 26)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-041bffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 27)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-041cffff • 806f070d-041effff
806f070d-041cffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 28)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-041dffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 29)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f070d-041effff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 30)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f070d-041fffff • 806f0807-0301ffff
806f070d-041fffff Rebuild in progress for Array in system [ComputerSystemElementName]. (Drive 31)

Progress.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f072b-2201ffff A successful software or firmware change was detected on system

[ComputerSystemElementName]. (Bkup Auto Update)
Explanation: This message is for the use case when an implementation has detected a Successful Software or
Firmware Change.
Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only. ROM Recovery :
806f0807-0301ffff [ProcessorElementName] has been Disabled. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor has been Disabled.
Severity: Info
Serviceable: No
SNMP Trap ID:

806f0807-0302ffff • 806f0813-2581ffff
806f0807-0302ffff [ProcessorElementName] has been Disabled. (CPU 2)

Severity: Info
Serviceable: No
SNMP Trap ID:
806f0807-2584ffff [ProcessorElementName] has been Disabled. (All CPUs)

Severity: Info
Serviceable: No
SNMP Trap ID:
User response: No action; information only. One of the CPUs :
806f0813-2581ffff A Uncorrectable Bus Error has occurred on system [ComputerSystemElementName]. (DIMMs)

Explanation: This message is for the use case when an implementation has detected a Bus Uncorrectable Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
2. Check the DIMM error LEDs.
3. Remove the failing DIMM from the system board.
5. Make sure that the installed DIMMs are supported and configured correctly.

806f0813-2582ffff • 806f0813-2584ffff
806f0813-2582ffff A Uncorrectable Bus Error has occurred on system [ComputerSystemElementName]. (PCIs)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
3. Remove the adapter from the indicated PCI slot.
806f0813-2584ffff A Uncorrectable Bus Error has occurred on system [ComputerSystemElementName]. (CPUs)

Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
2. (Trained technician only) Remove the failing microprocessor from the system board (see Removing a
microprocessor and heat sink).
4. Make sure that the two microprocessors are matching.

806f0823-2101ffff • 806f090c-2002ffff
806f0823-2101ffff Watchdog Timer interrupt occurred for [WatchdogElementName]. (IPMI Watchdog)

Explanation: This message is for the use case when an implementation has detected a Watchdog Timer interrupt
occurred.
Severity: Info
Serviceable: No
SNMP Trap ID:
806f090c-2001ffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 1)

Explanation: This message is for the use case when an 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)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2003ffff • 806f090c-2005ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2006ffff • 806f090c-2008ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2009ffff • 806f090c-200bffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:
806f090c-200affff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 10)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:
806f090c-200bffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 11)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-200cffff • 806f090c-200effff
806f090c-200cffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 12)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:
806f090c-200dffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 13)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:
806f090c-200effff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 14)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-200fffff • 806f090c-2011ffff
806f090c-200fffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] Throttled. (DIMM 15)

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2012ffff • 806f090c-2014ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2015ffff • 806f090c-2017ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:

806f090c-2018ffff • 806f0a07-0301ffff

Severity: Warning
Serviceable: Yes
SNMP Trap ID: 22
User response:
806f0a07-0301ffff [ProcessorElementName] is operating in a Degraded State. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor is running in the
Degraded state.
Severity: Warning
Alert Category: Warning - CPU
Serviceable: Yes
SNMP Trap ID: 42
User response:
closed.
2. Check the ambient temperature. You must be operating within the specifications.

806f0a07-0302ffff • 806f0a0c-2001ffff
806f0a07-0302ffff [ProcessorElementName] is operating in a Degraded State. (CPU 2)

Explanation: This message is for the use case when an implementation has detected a Processor is running in the
Degraded state.
Severity: Warning
Serviceable: Yes
SNMP Trap ID: 42
User response:
closed.
2. Check the ambient temperature. You must be operating within the specifications.
806f0a0c-2001ffff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

Subsystem [MemoryElementName]. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected an Over Temperature Condition
for Memory that has been Detected.
May also be shown as 806f0a0c2001ffff or 0x806f0a0c2001ffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
1. Make sure that the fans are operating, that there are no obstructions to the airflow, that the air baffles are in
place and correctly installed, and that the server cover is installed and completely closed.
2. Make sure that ambient temperature is within the specifications.
3. If a fan has failed, complete the action for a fan failure.

806f0a0c-2002ffff • 806f0a0c-2003ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2004ffff • 806f0a0c-2005ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2006ffff • 806f0a0c-2007ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2008ffff • 806f0a0c-2009ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-200affff • 806f0a0c-200bffff
806f0a0c-200affff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200affff or 0x806f0a0c200affff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
806f0a0c-200bffff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200bffff or 0x806f0a0c200bffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-200cffff • 806f0a0c-200dffff
806f0a0c-200cffff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200cffff or 0x806f0a0c200cffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
806f0a0c-200dffff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200dffff or 0x806f0a0c200dffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-200effff • 806f0a0c-200fffff
806f0a0c-200effff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200effff or 0x806f0a0c200effff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
806f0a0c-200fffff An Over-Temperature Condition has been detected on the [PhysicalMemoryElementName] on

May also be shown as 806f0a0c200fffff or 0x806f0a0c200fffff
Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2010ffff • 806f0a0c-2011ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2012ffff • 806f0a0c-2013ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2014ffff • 806f0a0c-2015ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2016ffff • 806f0a0c-2017ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:

806f0a0c-2018ffff • 806f0a13-0301ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 0
User response:
806f0a13-0301ffff A Fatal Bus Error has occurred on system [ComputerSystemElementName]. (CPU 1 PECI)
Explanation: This message is for the use case when an implementation has detected a Bus Fatal Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:

806f0a13-0302ffff • 81010202-0701ffff
806f0a13-0302ffff A Fatal Bus Error has occurred on system [ComputerSystemElementName]. (CPU 2 PECI)
Explanation: This message is for the use case when an implementation has detected a Bus Fatal Error.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 50
User response:
81010002-0701ffff Numeric sensor [NumericSensorElementName] going low (lower non-critical) has deasserted.
(CMOS Battery)
Explanation: This message is for the use case when an implementation has detected a Lower Non-critical sensor
going low has deasserted.
Severity: Info
Alert Category: Warning - Voltage
Serviceable: No
SNMP Trap ID: 13
81010202-0701ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted.
(CMOS Battery)
low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 1
User response: If the specified sensor is one of the following, SysBrd 3.3V, SysBrd 5V or SysBrd 12V: No action;
information only.

81010204-1d01ffff • 81010204-1d03ffff
81010204-1d01ffff Numeric sensor [NumericSensorElementName] going low (lower critical) has deasserted. (Fan
1A Tach)
low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11
User response: No action; information only. Fan 1B Tach :
2A Tach)
low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11
3A Tach)
low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11

81010204-1d04ffff • 81010701-0c01ffff
4A Tach)
low has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11
81010701-0701ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has deasserted.
(ROMB Temp)
going high has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 12
81010701-0c01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has deasserted.
(Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12

81010701-1001ffff • 81010701-1003ffff
(PCI Riser 1 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(PCI Riser 2 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(Rear BP Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12

81010701-1401ffff • 81010701-1403ffff
(CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(DIMM AB VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12

81010701-1404ffff • 81010701-1406ffff
(DIMM CD VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(DIMM EF VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
(DIMM GH VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12

81010701-2c01ffff • 81010901-0701ffff
81010701-2c01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has deasserted.
(Mezz Card Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
81010701-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper non-critical) has deasserted.
(PCH Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 12
81010901-0701ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(ROMB Temp)
high has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010901-0c01ffff • 81010901-1002ffff
81010901-0c01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010901-1001ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted. (PCI
Riser 1 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010901-1002ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted. (PCI
Riser 2 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010901-1003ffff • 81010901-1402ffff
(Rear BP Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010901-1403ffff • 81010901-1405ffff
(DIMM AB VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(DIMM CD VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
(DIMM EF VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010901-1406ffff • 81010901-2d01ffff
(DIMM GH VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010901-2c01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(Mezz Card Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010901-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper critical) has deasserted.
(PCH Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010902-0701ffff • 81010b01-0c01ffff
Severity: Info
Serviceable: No
SNMP Trap ID: 1
User response: If the specified sensor is one of the following, SysBrd 3.3V, SysBrd 5V or SysBrd 12V: No action;
information only.

deasserted. (ROMB Temp)
sensor going high has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (Ambient Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010b01-1001ffff • 81010b01-1003ffff

deasserted. (PCI Riser 1 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (PCI Riser 2 Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (Rear BP Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010b01-1401ffff • 81010b01-1403ffff

deasserted. (CPU1 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (CPU2 VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (DIMM AB VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010b01-1404ffff • 81010b01-1406ffff

deasserted. (DIMM CD VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (DIMM EF VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

deasserted. (DIMM GH VR Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81010b01-2c01ffff • 81030006-2101ffff

deasserted. (Mezz Card Temp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81010b01-2d01ffff Numeric sensor [NumericSensorElementName] going high (upper non-recoverable) has

deasserted. (PCH Temp)
May also be shown as 81010b012d01ffff or 0x81010b012d01ffff
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81030006-2101ffff Sensor [SensorElementName] has asserted. (Sig Verify Fail)

Severity: Info
Serviceable: No
SNMP Trap ID:

81030012-2301ffff • 81070101-0c01ffff
81030012-2301ffff Sensor [SensorElementName] has asserted. (OS RealTime Mod)

Severity: Info
Serviceable: No
SNMP Trap ID:
81030108-1301ffff Sensor [SensorElementName] has deasserted. (PS Heavy Load)

Severity: Info
Serviceable: No
SNMP Trap ID:
81070101-0c01ffff Sensor [SensorElementName] has deasserted the transition from normal to non-critical state.
(Ambient Status)
Explanation: This message is for the use case when an implementation has detected that a Sensor has deasserted a
transition to non-critical from normal.
Severity: Info
Serviceable: No
SNMP Trap ID: 12

8107010f-2201ffff • 81070201-0301ffff
8107010f-2201ffff Sensor [SensorElementName] has deasserted the transition from normal to non-critical state.
(GPT Status)
Severity: Info
Serviceable: No
SNMP Trap ID: 60
8107010f-2582ffff Sensor [SensorElementName] has deasserted the transition from normal to non-critical state.
(I/O Resources)
Severity: Info
Serviceable: No
SNMP Trap ID: 60
81070201-0301ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (CPU 1
OverTemp)
Explanation: This message is for the use case when an implementation has detected a Sensor transition to less
severe from critical.
Severity: Info
Serviceable: No
SNMP Trap ID: 0

81070201-0302ffff • 81070204-0a01ffff
81070201-0302ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (CPU 2
OverTemp)
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81070202-0701ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (SysBrd Vol
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 1
81070204-0a01ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 1 Fan
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 11

81070204-0a02ffff • 81070208-0a02ffff
81070204-0a02ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 2 Fan
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
81070208-0a01ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 1 Therm
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 4
81070208-0a02ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (PS 2 Therm
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 4

8107020f-2201ffff • 81070214-2201ffff
8107020f-2201ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (TXT ACM
Module)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. nvDIMM Flash :
8107020f-2582ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (I/O
Resources)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
81070214-2201ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (TPM Lock)
Severity: Info
Serviceable: No
SNMP Trap ID: 50

81070219-0701ffff • 8107021b-0302ffff
81070219-0701ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (SysBrd
Fault)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
8107021b-0301ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (CPU 1
QPILinkErr)
Severity: Info
Serviceable: No
SNMP Trap ID: 50
8107021b-0302ffff Sensor [SensorElementName] has transitioned to a less severe state from critical. (CPU 2
QPILinkErr)
Severity: Info
Serviceable: No
SNMP Trap ID: 50

81070301-0301ffff • 81070603-0701ffff
81070301-0301ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable from a less
severe state. (CPU 1 OverTemp)
Explanation: This message is for the use case when an implementation has detected that the Sensor transition to
non-recoverable from less severe has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81070301-0302ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable from a less
severe state. (CPU 2 OverTemp)
non-recoverable from less severe has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
81070603-0701ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable. (Pwr Rail A
Fault)
non-recoverable has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: No action; information only. Pwr Rail B Fault : Pwr Rail C Fault : Pwr Rail D Fault : Pwr Rail E
Fault : Pwr Rail F Fault : Pwr Rail G Fault : Pwr Rail H Fault :

81070608-0a01ffff • 810b010a-1e81ffff
81070608-0a01ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable.

Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: If the specified sensor is one of the following, PS1 12V OC Fault, PS1 12V OV Fault, PS1 12V UV
Fault or PS1 12Vaux Fault: No action; information only.
81070608-0a02ffff Sensor [SensorElementName] has deasserted the transition to non-recoverable.

Severity: Info
Serviceable: No
SNMP Trap ID: 4
User response: If the specified sensor is one of the following, PS1 12V OC Fault, PS1 12V OV Fault, PS1 12V UV
Fault or PS1 12Vaux Fault: No action; information only.
810b010a-1e81ffff Redundancy Lost for [RedundancySetElementName] has deasserted. (Fan Zone 1)

Explanation: This message is for the use case when Redundacy Lost has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 11

810b010a-1e82ffff • 810b0309-1301ffff
810b010a-1e82ffff Redundancy Lost for [RedundancySetElementName] has deasserted. (Fan Zone 2)

Severity: Info
Serviceable: No
SNMP Trap ID: 11
810b010c-2581ffff Redundancy Lost for [RedundancySetElementName] has deasserted. (Backup Memory)

Severity: Info
Serviceable: No
SNMP Trap ID: 41
810b0309-1301ffff Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for

[RedundancySetElementName] has deasserted. (Power Resource)
Explanation: This message is for the use case when a Redundancy Set has transitioned from Non-
redundant:Sufficient Resources.
Severity: Info
Serviceable: No
SNMP Trap ID: 10

810b030c-2581ffff • 810b050a-1e81ffff
810b030c-2581ffff Non-redundant:Sufficient Resources from Redundancy Degraded or Fully Redundant for

[RedundancySetElementName] has deasserted. (Backup Memory)
redundant:Sufficient Resources.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
810b0509-1301ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has deasserted.

(Power Resource)
Severity: Info
Serviceable: No
SNMP Trap ID: 9
810b050a-1e81ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has deasserted. (Fan

Zone 1)
Severity: Info
Serviceable: No
SNMP Trap ID: 11

810b050a-1e82ffff • 816f0007-0301ffff
810b050a-1e82ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has deasserted. (Fan

Zone 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 11
810b050c-2581ffff Non-redundant:Insufficient Resources for [RedundancySetElementName] has deasserted.

(Backup Memory)
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f0007-0301ffff [ProcessorElementName] has Recovered from IERR. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor Recovered - IERR
Condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40

816f0007-0302ffff • 816f0008-0a02ffff
816f0007-0302ffff [ProcessorElementName] has Recovered from IERR. (CPU 2)

Explanation: This message is for the use case when an implementation has detected a Processor Recovered - IERR
Condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
816f0008-0a01ffff [PowerSupplyElementName] has been removed from container

[PhysicalPackageElementName]. (Power Supply 1)
removed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0008-0a02ffff [PowerSupplyElementName] has been removed from container

[PhysicalPackageElementName]. (Power Supply 2)
removed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f0009-1301ffff • 816f000d-0401ffff
816f0009-1301ffff [PowerSupplyElementName] has been turned on. (Host Power)

Enabled.
Severity: Info
Alert Category: System - Power On
Serviceable: No
SNMP Trap ID: 24
816f000d-0400ffff The Drive [StorageVolumeElementName] has been removed from unit

[PhysicalPackageElementName]. (Drive 0)
Explanation: This message is for the use case when an implementation has detected a Drive has been Removed.
Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
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.

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0402ffff • 816f000d-0403ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0404ffff • 816f000d-0405ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0406ffff • 816f000d-0407ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0408ffff • 816f000d-0409ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-040affff • 816f000d-040bffff
816f000d-040affff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-040bffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-040cffff • 816f000d-040dffff
816f000d-040cffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-040dffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-040effff • 816f000d-040fffff
816f000d-040effff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-040fffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0410ffff • 816f000d-0411ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0412ffff • 816f000d-0413ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0414ffff • 816f000d-0415ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0416ffff • 816f000d-0417ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-0418ffff • 816f000d-0419ffff

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-041affff • 816f000d-041bffff
816f000d-041affff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-041bffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-041cffff • 816f000d-041dffff
816f000d-041cffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-041dffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000d-041effff • 816f000d-041fffff
816f000d-041effff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:
816f000d-041fffff The Drive [StorageVolumeElementName] has been removed from unit

Severity: Error
Serviceable: Yes
SNMP Trap ID: 5
User response:

816f000f-2201ffff • 816f0021-2201ffff
816f000f-2201ffff The System [ComputerSystemElementName] has detected a POST Error deassertion.

Explanation: This message is for the use case when an implementation has detected that Post Error has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: If the specified sensor is one of the following, ABR Status, Firmware Error or Sys Boot Status: No
action; information only.
816f0013-1701ffff System [ComputerSystemElementName] has recovered from a diagnostic interrupt. (NMI State)
Explanation: This message is for the use case when an implementation has detected a recovery from a Front Panel
NMI / Diagnostic Interrupt
Severity: Info
Serviceable: No
SNMP Trap ID: 50
816f0021-2201ffff Fault condition removed on slot [PhysicalConnectorElementName] on system

[ComputerSystemElementName]. (No Op ROM Space)
Explanation: This message is for the use case when an implementation has detected a Fault condition in a slot has
been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50

816f0021-2582ffff • 816f0021-3001ffff

[ComputerSystemElementName]. (All PCI Error)
been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. One of PCI Error :
816f0021-2c01ffff Fault condition removed on slot [PhysicalConnectorElementName] on system

[ComputerSystemElementName]. (Mezz Error)
been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50

[ComputerSystemElementName]. (PCI 1)
been removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. PCI 2 : PCI 3 : PCI 4 : PCI 5 : PCI 6 :

816f0028-2101ffff • 816f0107-0302ffff
816f0028-2101ffff Sensor [SensorElementName] has returned to normal on management system

[ComputerSystemElementName]. (TPM Cmd Failures)
Explanation: This message is for the use case when an implementation has detected a Sensor returned from
degraded/unavailable/failure.
Severity: Info
Serviceable: No
SNMP Trap ID: 60
816f0107-0301ffff An Over-Temperature Condition has been removed on [ProcessorElementName]. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Over-Temperature Condition
has been Removed for Processor.
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0107-0302ffff An Over-Temperature Condition has been removed on [ProcessorElementName]. (CPU 2)

Explanation: This message is for the use case when an implementation has detected a Over-Temperature Condition
has been Removed for Processor.
Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0108-0a01ffff • 816f010c-2001ffff
816f0108-0a01ffff [PowerSupplyElementName] has returned to OK status. (Power Supply 1)

Explanation: This message is for the use case when an implementation has detected a Power Supply return to
normal operational status.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
816f0108-0a02ffff [PowerSupplyElementName] has returned to OK status. (Power Supply 2)

Explanation: This message is for the use case when an implementation has detected a Power Supply return to
normal operational status.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
816f010c-2001ffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

Explanation: This message is for the use case when an implementation has detected a Memory uncorrectable error
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f010c-2002ffff • 816f010c-2004ffff

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

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

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

816f010c-2005ffff • 816f010c-2007ffff

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

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

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

816f010c-2008ffff • 816f010c-200affff

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

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-200affff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

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

816f010c-200bffff • 816f010c-200dffff
816f010c-200bffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-200cffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-200dffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

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

816f010c-200effff • 816f010c-2010ffff
816f010c-200effff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f010c-200fffff Uncorrectable error recovery detected for [PhysicalMemoryElementName] on Subsystem

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

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

816f010c-2011ffff • 816f010c-2013ffff

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

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

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

816f010c-2014ffff • 816f010c-2016ffff

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

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

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

816f010c-2017ffff • 816f010c-2581ffff

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

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

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
User response: No action; information only. One of the DIMMs :

816f010d-0400ffff • 816f010d-0402ffff
816f010d-0400ffff The Drive [StorageVolumeElementName] has been enabled. (Drive 0)

Explanation: This message is for the use case when an implementation has detected a Drive was Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0403ffff • 816f010d-0405ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0406ffff • 816f010d-0408ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0409ffff • 816f010d-040bffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-040affff The Drive [StorageVolumeElementName] has been enabled. (Drive 10)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-040bffff The Drive [StorageVolumeElementName] has been enabled. (Drive 11)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-040cffff • 816f010d-040effff
816f010d-040cffff The Drive [StorageVolumeElementName] has been enabled. (Drive 12)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-040dffff The Drive [StorageVolumeElementName] has been enabled. (Drive 13)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-040effff The Drive [StorageVolumeElementName] has been enabled. (Drive 14)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-040fffff • 816f010d-0411ffff
816f010d-040fffff The Drive [StorageVolumeElementName] has been enabled. (Drive 15)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0412ffff • 816f010d-0414ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0415ffff • 816f010d-0417ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-0418ffff • 816f010d-041affff

Severity: Info
Serviceable: No
SNMP Trap ID: 5

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-041affff The Drive [StorageVolumeElementName] has been enabled. (Drive 26)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-041bffff • 816f010d-041dffff
816f010d-041bffff The Drive [StorageVolumeElementName] has been enabled. (Drive 27)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-041cffff The Drive [StorageVolumeElementName] has been enabled. (Drive 28)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-041dffff The Drive [StorageVolumeElementName] has been enabled. (Drive 29)

Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f010d-041effff • 816f010f-2201ffff
816f010d-041effff The Drive [StorageVolumeElementName] has been enabled. (Drive 30)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010d-041fffff The Drive [StorageVolumeElementName] has been enabled. (Drive 31)

Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f010f-2201ffff The System [ComputerSystemElementName] has recovered from a firmware hang. (Firmware
Error)
Explanation: This message is for the use case when an implementation has recovered from a System Firmware
Hang.
Severity: Info
Serviceable: No
SNMP Trap ID: 50

816f0113-0301ffff • 816f0113-0302ffff
816f0113-0301ffff System [ComputerSystemElementName] has recovered from a bus timeout. (CPU 1 PECI)
Explanation: This message is for the use case when an 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 board (see Removing the system board and Installing the system
board). (n = microprocessor number)
816f0113-0302ffff System [ComputerSystemElementName] has recovered from a bus timeout. (CPU 2 PECI)
Explanation: This message is for the use case when an implemenation has detected that a system has recovered
from a Bus Timeout.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response:

816f011b-0701ffff • 816f0125-1001ffff
816f011b-0701ffff The connector [PhysicalConnectorElementName] configuration error has been repaired. (Front
USB)
was Repaired.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response: No action; information only. Front Video : PwrPaddle Cable :
816f0125-0c01ffff [ManagedElementName] detected as present. (Front Panel)

Explanation: This message is for the use case when an implementation has detected a Managed Element is now
Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0125-1001ffff [ManagedElementName] detected as present. (PCI Riser 1)

Present.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f0125-1002ffff • 816f0207-0301ffff
816f0125-1002ffff [ManagedElementName] detected as present. (PCI Riser 2)

Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0125-2c01ffff [ManagedElementName] detected as present. (Mezz Card)

Present.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0207-0301ffff [ProcessorElementName] has Recovered from FRB1/BIST condition. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor Recovered -
FRB1/BIST condition.
Severity: Info
Serviceable: No
SNMP Trap ID: 40

816f0207-0302ffff • 816f020d-0400ffff
816f0207-0302ffff [ProcessorElementName] has Recovered from FRB1/BIST condition. (CPU 2)

Severity: Info
Serviceable: No
SNMP Trap ID: 40
816f0207-2584ffff [ProcessorElementName] has Recovered from FRB1/BIST condition. (All CPUs)

Severity: Info
Serviceable: No
SNMP Trap ID: 40
816f020d-0400ffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Explanation: This message is for the use case when an implementation has detected an Array Failure is no longer
Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0401ffff • 816f020d-0403ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0404ffff • 816f020d-0406ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0407ffff • 816f020d-0409ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-040affff • 816f020d-040cffff
816f020d-040affff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-040bffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-040cffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-040dffff • 816f020d-040fffff
816f020d-040dffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-040effff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-040fffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0410ffff • 816f020d-0412ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0413ffff • 816f020d-0415ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0416ffff • 816f020d-0418ffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-0419ffff • 816f020d-041bffff

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-041affff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-041bffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-041cffff • 816f020d-041effff
816f020d-041cffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-041dffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f020d-041effff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27

816f020d-041fffff • 816f0308-0a02ffff
816f020d-041fffff Failure no longer Predicted on drive [StorageVolumeElementName] for array

Predicted.
Severity: Info
Serviceable: No
SNMP Trap ID: 27
816f0308-0a01ffff [PowerSupplyElementName] has returned to a Normal Input State. (Power Supply 1)

that has returned to normal.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0308-0a02ffff [PowerSupplyElementName] has returned to a Normal Input State. (Power Supply 2)

that has returned to normal.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f030c-2001ffff • 816f030c-2003ffff
816f030c-2001ffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

recovered. (DIMM 1)
Explanation: This message is for the use case when an implementation has detected a Memory Scrub failure
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

recovered. (DIMM 2)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

recovered. (DIMM 3)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f030c-2004ffff • 816f030c-2006ffff

recovered. (DIMM 4)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

recovered. (DIMM 5)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

recovered. (DIMM 6)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f030c-2007ffff • 816f030c-2009ffff

recovered. (DIMM 7)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41

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-200affff • 816f030c-200cffff
816f030c-200affff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

recovered. (DIMM 10)
recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200bffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200cffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

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

816f030c-200dffff • 816f030c-200fffff
816f030c-200dffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200effff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

recovery.
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f030c-200fffff Scrub Failure for [PhysicalMemoryElementName] on Subsystem [MemoryElementName]has

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

816f030c-2010ffff • 816f030c-2012ffff

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

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

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

816f030c-2013ffff • 816f030c-2015ffff

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

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

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

816f030c-2016ffff • 816f030c-2018ffff

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

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

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

816f0313-1701ffff • 816f040c-2002ffff
816f0313-1701ffff System [ComputerSystemElementName] has recovered from an NMI. (NMI State)

Explanation: This message is for the use case when an implementation has detected a Software NMI has been
Recovered from.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
816f040c-2001ffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 1)

Explanation: This message is for the use case when an implementation has detected that Memory has been Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2003ffff • 816f040c-2005ffff

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2006ffff • 816f040c-2008ffff

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2009ffff • 816f040c-200bffff

Severity: Info
Serviceable: No
SNMP Trap ID:
816f040c-200affff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 10)

Severity: Info
Serviceable: No
SNMP Trap ID:
816f040c-200bffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 11)

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-200cffff • 816f040c-200effff
816f040c-200cffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 12)

Severity: Info
Serviceable: No
SNMP Trap ID:
816f040c-200dffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 13)

Severity: Info
Serviceable: No
SNMP Trap ID:
816f040c-200effff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 14)

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-200fffff • 816f040c-2011ffff
816f040c-200fffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (DIMM 15)

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2012ffff • 816f040c-2014ffff

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2015ffff • 816f040c-2017ffff

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

Severity: Info
Serviceable: No
SNMP Trap ID:

816f040c-2018ffff • 816f0413-2582ffff

Severity: Info
Serviceable: No
SNMP Trap ID:
816f040c-2581ffff [PhysicalMemoryElementName] Enabled on Subsystem [MemoryElementName]. (All DIMMS)

Severity: Info
Serviceable: No
SNMP Trap ID:
816f0413-2582ffff A PCI PERR recovery has occurred on system [ComputerSystemElementName]. (PCIs)

Explanation: This message is for the use case when an implementation has detected a PCI PERR recovered.
Severity: Info
Serviceable: No
SNMP Trap ID: 50

816f0507-0301ffff • 816f0507-2584ffff
816f0507-0301ffff [ProcessorElementName] has Recovered from a Configuration Mismatch. (CPU 1)

Explanation: This message is for the use case when an implementation has Recovered from a Processor
Configuration Mismatch.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
816f0507-0302ffff [ProcessorElementName] has Recovered from a Configuration Mismatch. (CPU 2)

Severity: Info
Serviceable: No
SNMP Trap ID: 40
816f0507-2584ffff [ProcessorElementName] has Recovered from a Configuration Mismatch. (All CPUs)

Severity: Info
Serviceable: No
SNMP Trap ID: 40

816f050c-2001ffff • 816f050c-2003ffff
816f050c-2001ffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2004ffff • 816f050c-2006ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2007ffff • 816f050c-2009ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-200affff • 816f050c-200cffff
816f050c-200affff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200bffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200cffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-200dffff • 816f050c-200fffff
816f050c-200dffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200effff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050c-200fffff Memory Logging Limit Removed for [PhysicalMemoryElementName] on Subsystem

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2010ffff • 816f050c-2012ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2013ffff • 816f050c-2015ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2016ffff • 816f050c-2018ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43

816f050c-2581ffff • 816f050d-0401ffff

has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 43
816f050d-0400ffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 0)

Explanation: This message is for the use case when an 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

816f050d-0402ffff • 816f050d-0404ffff

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

816f050d-0405ffff • 816f050d-0407ffff

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

816f050d-0408ffff • 816f050d-040affff

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-040affff Critical Array [ComputerSystemElementName] has deasserted. (Drive 10)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f050d-040bffff • 816f050d-040dffff
816f050d-040bffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 11)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-040cffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 12)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-040dffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 13)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f050d-040effff • 816f050d-0410ffff
816f050d-040effff Critical Array [ComputerSystemElementName] has deasserted. (Drive 14)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-040fffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 15)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f050d-0411ffff • 816f050d-0413ffff

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

816f050d-0414ffff • 816f050d-0416ffff

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

816f050d-0417ffff • 816f050d-0419ffff

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

816f050d-041affff • 816f050d-041cffff
816f050d-041affff Critical Array [ComputerSystemElementName] has deasserted. (Drive 26)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-041bffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 27)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-041cffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 28)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f050d-041dffff • 816f050d-041fffff
816f050d-041dffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 29)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-041effff Critical Array [ComputerSystemElementName] has deasserted. (Drive 30)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f050d-041fffff Critical Array [ComputerSystemElementName] has deasserted. (Drive 31)

deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f0607-0301ffff • 816f0607-2584ffff
816f0607-0301ffff An SM BIOS Uncorrectable CPU complex error for [ProcessorElementName] has deasserted.
(CPU 1)
Explanation: This message is for the use case when an SM BIOS Uncorrectable CPU complex error has deasserted.
Severity: Info
Serviceable: No
SNMP Trap ID: 40
(CPU 2)
Severity: Info
Serviceable: No
SNMP Trap ID: 40
(All CPUs)
Severity: Info
Serviceable: No
SNMP Trap ID: 40

816f0608-1301ffff • 816f060d-0401ffff
816f0608-1301ffff [PowerSupplyElementName] Configuration is OK. (PS Configuration)

Explanation: This message is for the use case when an implementation when a Power Supply configuration is OK.
Severity: Info
Serviceable: No
SNMP Trap ID: 4
816f060d-0400ffff Array in system [ComputerSystemElementName] has been restored. (Drive 0)

Explanation: This message is for the use case when an implementation has detected that a Failed Array has been
Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0402ffff • 816f060d-0404ffff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0405ffff • 816f060d-0407ffff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0408ffff • 816f060d-040affff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-040affff Array in system [ComputerSystemElementName] has been restored. (Drive 10)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-040bffff • 816f060d-040dffff
816f060d-040bffff Array in system [ComputerSystemElementName] has been restored. (Drive 11)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-040cffff Array in system [ComputerSystemElementName] has been restored. (Drive 12)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-040dffff Array in system [ComputerSystemElementName] has been restored. (Drive 13)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-040effff • 816f060d-0410ffff
816f060d-040effff Array in system [ComputerSystemElementName] has been restored. (Drive 14)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-040fffff Array in system [ComputerSystemElementName] has been restored. (Drive 15)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0411ffff • 816f060d-0413ffff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0414ffff • 816f060d-0416ffff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-0417ffff • 816f060d-0419ffff

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-041affff • 816f060d-041cffff
816f060d-041affff Array in system [ComputerSystemElementName] has been restored. (Drive 26)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-041bffff Array in system [ComputerSystemElementName] has been restored. (Drive 27)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-041cffff Array in system [ComputerSystemElementName] has been restored. (Drive 28)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f060d-041dffff • 816f060d-041fffff
816f060d-041dffff Array in system [ComputerSystemElementName] has been restored. (Drive 29)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-041effff Array in system [ComputerSystemElementName] has been restored. (Drive 30)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5
816f060d-041fffff Array in system [ComputerSystemElementName] has been restored. (Drive 31)

Restored.
Severity: Info
Serviceable: No
SNMP Trap ID: 5

816f070c-2001ffff • 816f070c-2003ffff
816f070c-2001ffff Configuration error for [PhysicalMemoryElementName] on Subsystem

[MemoryElementName]has deasserted. (DIMM 1)
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

816f070c-2004ffff • 816f070c-2006ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-2007ffff • 816f070c-2009ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-200affff • 816f070c-200cffff
816f070c-200affff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200bffff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200cffff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-200dffff • 816f070c-200fffff
816f070c-200dffff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200effff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070c-200fffff Configuration error for [PhysicalMemoryElementName] on Subsystem

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-2010ffff • 816f070c-2012ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-2013ffff • 816f070c-2015ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-2016ffff • 816f070c-2018ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

Severity: Info
Serviceable: No
SNMP Trap ID: 41

816f070c-2581ffff • 816f070d-0401ffff

[MemoryElementName]has deasserted. (All DIMMS)
Severity: Info
Serviceable: No
SNMP Trap ID: 41
816f070d-0400ffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 0)

Explanation: This message is for the use case when an implementation has detected that an Array Rebuild has
Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0402ffff • 816f070d-0404ffff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0405ffff • 816f070d-0407ffff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0408ffff • 816f070d-040affff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-040affff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 10)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-040bffff • 816f070d-040dffff
816f070d-040bffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 11)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-040cffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 12)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-040dffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 13)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-040effff • 816f070d-0410ffff
816f070d-040effff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 14)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-040fffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 15)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0411ffff • 816f070d-0413ffff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0414ffff • 816f070d-0416ffff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-0417ffff • 816f070d-0419ffff

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-041affff • 816f070d-041cffff
816f070d-041affff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 26)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-041bffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 27)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-041cffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 28)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f070d-041dffff • 816f070d-041fffff
816f070d-041dffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 29)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-041effff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 30)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f070d-041fffff Rebuild completed for Array in system [ComputerSystemElementName]. (Drive 31)

Completed.
Severity: Info
Serviceable: No
SNMP Trap ID:

816f0807-0301ffff • 816f0807-2584ffff
816f0807-0301ffff [ProcessorElementName] has been Enabled. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor has been Enabled.
Severity: Info
Serviceable: No
SNMP Trap ID:
816f0807-0302ffff [ProcessorElementName] has been Enabled. (CPU 2)

Severity: Info
Serviceable: No
SNMP Trap ID:
816f0807-2584ffff [ProcessorElementName] has been Enabled. (All CPUs)

Severity: Info
Serviceable: No
SNMP Trap ID:

816f0813-2581ffff • 816f0813-2584ffff
816f0813-2581ffff System [ComputerSystemElementName]has recovered from an Uncorrectable Bus Error.

(DIMMs)
Explanation: This message is for the use case when an implementation has detected a that a system has recovered
from a Bus Uncorrectable Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
816f0813-2582ffff System [ComputerSystemElementName]has recovered from an Uncorrectable Bus Error. (PCIs)

Severity: Info
Serviceable: No
SNMP Trap ID: 50
816f0813-2584ffff System [ComputerSystemElementName]has recovered from an Uncorrectable Bus Error. (CPUs)

Severity: Info
Serviceable: No
SNMP Trap ID: 50

816f090c-2001ffff • 816f090c-2003ffff
816f090c-2001ffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 1)
Explanation: This message is for the use case when an implementation has detected Memory is no longer Throttled.
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 2)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 3)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-2004ffff • 816f090c-2006ffff

(DIMM 4)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 5)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 6)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-2007ffff • 816f090c-2009ffff

(DIMM 7)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 8)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 9)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-200affff • 816f090c-200cffff
816f090c-200affff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 10)
Severity: Info
Serviceable: No
SNMP Trap ID:
816f090c-200bffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 11)
Severity: Info
Serviceable: No
SNMP Trap ID:
816f090c-200cffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 12)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-200dffff • 816f090c-200fffff
816f090c-200dffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 13)
Severity: Info
Serviceable: No
SNMP Trap ID:
816f090c-200effff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 14)
Severity: Info
Serviceable: No
SNMP Trap ID:
816f090c-200fffff [PhysicalMemoryElementName] on Subsystem [MemoryElementName] is no longer Throttled.

(DIMM 15)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-2010ffff • 816f090c-2012ffff

(DIMM 16)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 17)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 18)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-2013ffff • 816f090c-2015ffff

(DIMM 19)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 20)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 21)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f090c-2016ffff • 816f090c-2018ffff

(DIMM 22)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 23)
Severity: Info
Serviceable: No
SNMP Trap ID:

(DIMM 24)
Severity: Info
Serviceable: No
SNMP Trap ID:

816f0a07-0301ffff • 816f0a0c-2001ffff
816f0a07-0301ffff The Processor [ProcessorElementName] is no longer operating in a Degraded State. (CPU 1)

Explanation: This message is for the use case when an implementation has detected a Processor is no longer
running in the Degraded state.
Severity: Info
Serviceable: No
SNMP Trap ID: 42
816f0a07-0302ffff The Processor [ProcessorElementName] is no longer operating in a Degraded State. (CPU 2)

Explanation: This message is for the use case when an implementation has detected a Processor is no longer
running in the Degraded state.
Severity: Info
Serviceable: No
SNMP Trap ID: 42
816f0a0c-2001ffff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

for Memory that has been Removed.
Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2002ffff • 816f0a0c-2004ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2005ffff • 816f0a0c-2007ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2008ffff • 816f0a0c-200affff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a0c-200affff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200affff or 0x816f0a0c200affff
Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-200bffff • 816f0a0c-200dffff
816f0a0c-200bffff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200bffff or 0x816f0a0c200bffff
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a0c-200cffff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200cffff or 0x816f0a0c200cffff
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a0c-200dffff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200dffff or 0x816f0a0c200dffff
Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-200effff • 816f0a0c-2010ffff
816f0a0c-200effff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200effff or 0x816f0a0c200effff
Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a0c-200fffff An Over-Temperature Condition has been removed on the [PhysicalMemoryElementName] on

May also be shown as 816f0a0c200fffff or 0x816f0a0c200fffff
Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2011ffff • 816f0a0c-2013ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2014ffff • 816f0a0c-2016ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0

816f0a0c-2017ffff • 816f0a13-0301ffff

Severity: Info
Serviceable: No
SNMP Trap ID: 0

Severity: Info
Serviceable: No
SNMP Trap ID: 0
816f0a13-0301ffff System [ComputerSystemElementName] has recovered from a Fatal Bus Error. (CPU 1 PECI)
Explanation: This message is for the use case when an implementation has detected that a system has recovered
from a Bus Fatal Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response:

816f0a13-0302ffff
816f0a13-0302ffff System [ComputerSystemElementName] has recovered from a Fatal Bus Error. (CPU 2 PECI)
Explanation: This message is for the use case when an implementation has detected that a system has recovered
from a Bus Fatal Error.
Severity: Info
Serviceable: No
SNMP Trap ID: 50
User response:

Appendix B. UEFI/POST diagnostic codes
UEFI/POST diagnostic error codes can be generated when the server starts or
while the server is running. UEFI/POST codes are logged in the IMM 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 39. 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
The actions that you should take to resolve the event.
Perform the steps 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.

I.11002 • I.18006
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 Processor’s 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. Check IBM support site for an applicable service 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.
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.
socket is damaged.

I.18007 • I.1800A
I.18007 [I.18007] A power segment mismatch has been detected for one or more processor 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.
socket is damaged
I.18008 [I.18008] Currently, there is no additional information for this event.

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
I.18009 [I.18009] A core speed mismatch has been detected for one or more processor 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.
socket is damaged.
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 information
for this product. Correct any mismatch found.
3. Check IBM support site for an applicable service bulletin or firmware update that applies to this processor error.
4. (Trained Service technician only) Replace the Processor. Inspect Processor socket and replace the system board
first if socket is damaged
Appendix B. UEFI/POST diagnostic codes 829

I.1800B • I.1800E
I.1800B [I.1800B] A cache size mismatch has been detected for one or more processor 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 information
for this product. Correct any mismatch found.
3. (Trained Service technician only) Replace the system board.
I.1800C [I.1800C] A cache type mismatch has been detected for one or more processor packages.
Explanation: Processors have one or more cache levels with mismatched type
Severity: Error
for this product.
I.1800D [I.1800D] A cache associativity mismatch has been detected for one or more processor packages.
Explanation: Processors have one or more cache levels with mismatched associativity
Severity: Error
for this product.
I.1800E [I.1800E] A processor model mismatch has been detected for one or more processor packages.
Explanation: Processors have mismatched Model Number
Severity: Error
for this product.

I.1800F • I.2018003
I.1800F [I.1800F] A processor family mismatch has been detected for one or more processor packages.
Explanation: Processors have mismatched Family
Severity: Error
for this product
I.18010 [I.18010] A processor stepping mismatch has been detected for one or more processor packages.
Explanation: Processors of the same model have mismatched Stepping ID
Severity: Error
for this product.
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.

I.3048005 • I.3818003
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
1. Use IMM Web Interface to clear event log.
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
1. Reflash backup 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.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 • S.1100B
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.
I.580A6 [I.580A6] Memory spare copy has completed successfully.

Explanation: Spare Copy Complete
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
2. (Trained Service technician only) Replace the Processor.

S.1100C • S.2018001
S.1100C [S.1100C] An uncorrectable error has been detected on processor %.

Explanation: Uncorrectable processor error detected
Severity: Error
1. Check IBM support site for an applicable service bulletin or firmware update that applies to this 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. 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. 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.
2. 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.
3. If problem persists, then remove Adapter Card. If system reboots successfully without the adapter, replace that
card.
4. (Trained Service technician only) Replace the processor.
S.2018001 [S.2018001] An Uncorrected PCIe Error has Occurred at Bus % Device % Function %. The Vendor ID
for the device is % and the Device ID is %.
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. 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.
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.
4. Trained Service technician only) Replace the processor.

S.3020007 • S.3040007
S.3020007 [S.3020007] A firmware fault has been detected in the UEFI image.
Explanation: Internal UEFI Firmware Fault Detected, System halted
Severity: Error
2. Reflash UEFI image.
3. (Trained service technician only) Replace the system board.
S.3028002 [S.3028002] Boot permission timeout detected.

Explanation: Boot Permission Negotiation Timeout
Severity: Error
1. Check CMM/IMM logs for communication errors and resolve.
2. Reseat system
3. If problem persists escalate to the next level of support
Severity: Error
Severity: Error

S.3050007 • S.3070007
Severity: Error
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.
5. Reflash UEFI firmware.
6. Remove and re-install CMOS battery for 30 seconds to clear CMOS contents
Severity: Error
Severity: Error

S.3108007 • S.51003
S.3108007 [S.3108007 ] The default system settings have been restored.

Explanation: System Configuration Restored to Defaults
Severity: Error
S.3818004 [S.3818004] The CRTM flash driver could not successfully flash the staging area. A failure occurred.
Explanation: CRTM Update Failed
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.
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 %.
Explanation: [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. Fatal Memory Error Occurred
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. (Note: Event Log may contain a recent 00580A4
event denoting detected change in DIMM population that could be related to this problem.)
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. Check IBM support site for an applicable service bulletin or firmware update that applies to this 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.
7. (Trained Service technician only) Replace system board.

S.51006 • S.58008
S.51006 [S.51006] A memory mismatch has been detected. Please verify that the memory configuration is
valid.
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 information for
this product.
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. (Trained Service technician only) Replace Processor.
S.51009 [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 information for this
product.
4. (Trained service technician only) Replace the processor.
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. (Note: Event Log may contain a recent 00580A4 event denoting detected change
in DIMM population that could be related to this problem.)
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. Check IBM support site for an applicable service bulletin or firmware update that applies to this 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
Processor’s, swap Processor’s 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.

S.68005 • W.11004
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. Check IBM support site for an applicable service bulletin or firmware update for the system or adapter that
applies to this error.
S.680B8 [S.680B8] Internal QPI Link Failure Detected.

Explanation: Internal QPI Link Failure Detected
Severity: 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
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) .
W.11004 [W.11004] A processor within the system has failed the BIST.
Explanation: Processor Self Test Failure Detected
Severity: Error
1. If the Processor or firmware was just updated, check IBM support site for an applicable service bulletin or
firmware update that applies to this Processor error.
2. (Trained service technician only) If there are multiple Processor’s, swap Processor’s 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.

W.3048006 • W.305800A
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
2. Reflash Primary UEFI image. Refer to UEFI Recovery section of service information for this product.
W.305000A [W.305000A] An invalid date and time have been detected.

Explanation: RTC Date and Time Incorrect
Severity: Warning
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.
W.3058009 [W.3058009] DRIVER HEALTH PROTOCOL: Missing Configuraiton. Requires Change Settings From
F1.
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. 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
2. If problem persists, switch to backup UEFI or reflash current UEFI image.
3. (Trained Service Technician Only) Replace system board.

W.305800B • W.305800E
W.305800B [W.305800B] DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller.

Explanation: DRIVER HEALTH PROTOCOL: Reports 'Reboot' Required Controller
Severity: Warning
1. No action required – system will reboot at the end of POST.
W.305800C [W.305800C] DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller.
Explanation: DRIVER HEALTH PROTOCOL: Reports 'System Shutdown' Required Controller
Severity: Warning
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.
W.305800E [W.305800E] DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver.
Explanation: DRIVER HEALTH PROTOCOL: Reports Invalid Health Status Driver
Severity: Warning

W.3808000 • W.3818005
W.3808000 [W.3808000] An IMM communication failure has occurred.

Explanation: IMM Communication Failure
Severity: Warning
1. Remove AUX power from the node. This will reboot the entire node.
3. Reflash UEFI Firmware.
W.3808002 [W.3808002] An error occurred while saving UEFI settings to the IMM.
Explanation: Error Updating System Configuration to IMM
Severity: Warning
1. Use F1 Setup, Verify Settings and Save Settings to recover settings.
4. Reflash IMM Firmware.
5. Remove and re-install CMOS battery for 30 seconds to clear CMOS contents.
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.
4. Reflash IMM Firmware.
5. Remove and re-install CMOS battery for 30 seconds to clear CMOS contents.
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.

W.3938002 • W.58001
W.3938002 [W.3938002] A boot configuration error has been detected.

Explanation: Boot Configuration Error
Severity: Warning
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.
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
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. (Note: Event Log may contain a recent 00580A4
event denoting detected change in DIMM population that could be related to this problem.)
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 the previous steps do not resolve the problem, at the next maintenance opportunity, replace the affected DIMM
(as indicated by LightPath and/or failure log entry).
4. 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 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.
5. Check IBM support site for an applicable Service Bulletins (Service bulletins) that applies to this memory error.
(Link to IBM support service bulletins)
6. (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.
7. (Trained service technician only) Remove affected Processor and inspect Processor socket pins for damaged or
mis-aligned pins. If damage is found or Processor is an upgrade part, replace system board.
8. (Trained Service technician only) Replace affected processor.

W.58007 • W.68002
W.58007 [W.58007] Invalid memory configuration (Unsupported DIMM Population) detected. Please verify
memory configuration is valid.
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 information for this
product.
W.580A1 [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.
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.
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, makesure the batter is properly seated.
3. Replace CMOS Battery

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
Related Links:
v IBM Support Website
v Latest level of DSA
v Latest level of BMC/IMM
405-001-000 BRCM:TestMIIRegisters Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

405-002-000 • 405-004-000
405-002-000 BRCM:TestEEPROM Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
405-003-000 BRCM:TestInternalMemory Test Passed

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

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

405-005-000 • 405-007-000
405-005-000 BRCM:TestLoopbackMAC Test Passed

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

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

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
Appendix C. DSA diagnostic test results 847

405-800-000 • 405-802-000
405-800-000 BRCM:TestControlRegisters Test Aborted

Explanation: The control registers test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
405-801-000 BRCM:TestMIIRegisters Test Aborted

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

Explanation: The EEPROM test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

405-803-000 • 405-805-000
405-803-000 BRCM:TestInternalMemory Test Aborted

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

Explanation: The interrupt test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
405-805-000 BRCM:TestLoopbackMAC Test Aborted

Explanation: Loopback testing at the MAC layer was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

405-806-000 • 405-900-000
405-806-000 BRCM:TestLoopbackPhysical Test Aborted

Explanation: Loopback testing at the physical layer was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
405-807-000 BRCM:TestLEDs Test Aborted

Explanation: Verification of status LEDs was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
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.
Related Links:

405-901-000 • 405-902-000
405-901-000 BRCM:TestMIIRegisters Test Failed

Explanation: A failure was detected while testing internal PHY registers.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
405-902-000 BRCM:TestEEPROM Test Failed

Explanation: A failure was detected while testing non-volatile RAM.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:

405-903-000 • 405-904-000
405-903-000 BRCM:TestInternalMemory Test Failed

Explanation: A failure was detected while testing internal memory.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
405-904-000 BRCM:TestInterrupt Test Failed

Explanation: A failure was detected while testing interrupts.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:

405-905-000 • 405-906-000
405-905-000 BRCM:TestLoopbackMAC Test Failed

Explanation: BRCM:TestLoopbackMAC Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
405-906-000 BRCM:TestLoopbackPhysical Test Failed

Explanation: A failure was detected during the loopback test at the physical layer.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:

405-907-000 • 218-000-000
405-907-000 BRCM:TestLEDs Test Failed

Explanation: A failure was detected while verifying operation of the status LEDs.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
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
Related Links:

218-001-000 • 218-003-000
218-001-000 Brocade:ExternalLoopbackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
218-002-000 Brocade:SerdesLoopbackTest Passed

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

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

218-004-000 • 218-006-000
218-004-000 Brocade:ExternalEthLoopbackTest Passed

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

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

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

218-800-000 • 218-802-000
218-800-000 Brocade:MemoryTest Aborted

Explanation: The test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
218-801-000 Brocade:ExternalLoopbackTest Aborted

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

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

218-803-000 • 218-805-000
218-803-000 Brocade:PCILoopbackTest Aborted

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

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
218-805-000 Brocade:SerdesEthLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

218-806-000 • 218-901-000
218-806-000 Brocade:InternalLoopbackTest Aborted

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
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.
Related Links:
218-901-000 Brocade:ExternalLoopbackTest Failed

Explanation: A failure was detected during the Loopback test.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Check cable connections.
2. Rerun the test.
4. Rerun the test.
Related Links:

218-902-000 • 218-903-000
218-902-000 Brocade:SerdesLoopbackTest Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
Related Links:
218-903-000 Brocade:PCILoopbackTest Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
Related Links:

218-904-000 • 218-905-000
218-904-000 Brocade:ExternalEthLoopbackTest Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Check or replace SFP/cable.
2. Rerun the test.
4. Rerun the test.
Related Links:
218-905-000 Brocade:SerdesEthLoopbackTest Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
Related Links:

218-906-000 • 180-801-000
218-906-000 Brocade:InternalLoopbackTest Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Rerun the test.
3. Rerun the test.
Related Links:
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
Related Links:
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.

180-901-000 • 089-000-000
Related Links:
180-901-000 Check-point Panel Test Failed

Explanation: Check-point Panel Test Failed. Operator reported incorrect display.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Check the operator information panel cabling for loose or broken connections at both ends or damage to the
cable.
2. Replace the information panel cable if damage is present.
4. Replace the operator information panel assembly.
Related Links:
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
Related Links:

089-801-000 • 089-802-000
089-801-000 CPU Stress Test Aborted

Explanation: CPU Stress Test Aborted. Internal Program Error.
Severity: Warning
Serviceable: Yes
Recoverable: No
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 necessary. The installed firmware level can be found in the DSA
Diagnostic Event Log within the 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.
6. If the system has stopped responding, turn off and restart the system and then run the test again.
Related Links:

Explanation: CPU Stress Test Aborted. System resource unavailability error.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

089-803-000 • 089-901-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
Related Links:

Explanation: CPU Stress Test Aborted. User pressed Ctrl-C.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:
089-901-000 CPU Stress Test Failed

Explanation: CPU Stress Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

516-000-000 • 516-002-000
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
Related Links:
516-001-000 ELXUCNA: NIC PHY LoopBackTest Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
516-002-000 ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

516-800-000 • 516-802-000
516-800-000 ELXUCNA: NIC MAC LoopBackTest Aborted

Explanation: Loopback testing at the MAC layer was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
516-801-000 ELXUCNA: NIC PHY LoopBackTest Aborted

Explanation: Loopback testing at the physical layer was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
516-802-000 ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Aborted

Explanation: Verification of status LEDs was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

516-900-000 • 516-901-000
516-900-000 ELXUCNA: NIC MAC LoopBackTest Failed

Explanation: A failure was detected during the loopback test at the MAC layer.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
516-901-000 ELXUCNA: NIC PHY LoopBackTest Failed

Explanation: A failure was detected during the loopback test at the physical layer.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:

516-902-000 • 401-000-000
516-902-000 ELXUCNA: ELXUCNA: NIC LED(Beacon)Test Failed

Explanation: A failure was detected while verifying operation of the status LEDs.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
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
Related Links:

401-801-000 • 401-802-000
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.
Related Links:
401-802-000 EXA Port Ping Test Aborted

Explanation: EXA Port Ping Test Aborted. Port connections may not be correct.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

401-901-001 • 217-000-000
401-901-001 EXA Port Ping Test Failed

Explanation: EXA Port Ping Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
3. Check scalability cables for loose connections.
4. Replace the scalability cable(s) for specified port(s).
Related Links:
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
Related Links:

217-800-000 • 217-900-000
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.
4. If the problem remains, contact your technical-support representative.
Related Links:
217-900-000 HDD Test Failed

Explanation: HDD Test Failed. The hard drive self-test detected a failure.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
3. Verify the firmware is at the latest level.
4. Rerun the test.
5. If the problem remains, contact your technical-support representative.
Related Links:

406-000-000 • 406-002-000
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
Related Links:
406-001-000 IANet:EEPROM Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
406-002-000 IANet:FIFO Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

406-003-000 • 406-800-000
406-003-000 IANet:Interrupts Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
406-004-000 IANet:Loopback Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
406-800-000 IANet:Registers Test Aborted

Explanation: Registers test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

406-801-000 • 406-803-000
406-801-000 IANet:EEPROM Test Aborted

Explanation: EEPROM test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
406-802-000 IANet:FIFO Test Aborted

Explanation: FIFO test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
406-803-000 IANet:Interrupts Test Aborted

Explanation: Interrupt test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

406-804-000 • 406-901-000
406-804-000 IANet:Loopback Test Aborted

Explanation: Loopback test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
406-900-000 IANet:Registers Test Failed

Explanation: A failure was detected during the Registers test.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:
406-901-000 IANet:EEPROM Test Failed

Explanation: A failure was detected during the EEPROM test.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
Related Links:

406-902-000 • 406-903-000
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.
Related Links:
406-903-000 IANet:Interrupts Test Failed

Explanation: A failure was detected during the Interrupt test.
Severity: Error
Serviceable: Yes
Recoverable: No
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.
4. Rerun the test.
Related Links:

406-904-000 • 407-000-000
406-904-000 IANet:Loopback Test Failed

Severity: Error
Serviceable: Yes
Recoverable: No
1. Check the Ethernet cable for damage and ensure correct cable type and attachment.
3. Rerun the test.
Related Links:
DSA LSI hard drive test results

The following messages can result when you run the LSI hard drive test.
407-000-000 LSIESG:DiskDefaultDiagnostic Test Passed

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

407-800-000 • 407-900-000
407-800-000 LSIESG:DiskDefaultDiagnostic Test Aborted

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
407-900-000 LSIESG:DiskDefaultDiagnostic Test Failed

Explanation: The hard drive self-test detected a failure.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Rerun the test.
3. Verify whether the firmware is at the latest level.
4. Rerun the test.
Related Links:
DSA Mellanox adapter test results

The following messages can result when you run the Mellanox adapter test.

408-000-000 • 408-800-000
408-000-000 MLNX:MLNX_DiagnosticTestEthernetPort Test Passed

Explanation: Port Test Passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
408-001-000 MLNX:MLNX_DiagnosticTestIBPort Test Passed

Explanation: Port Test Passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
408-800-000 MLNX:MLNX_DiagnosticTestEthernetPort Test Aborted

Explanation: Port Test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

408-801-000 • 408-901-000
408-801-000 MLNX:MLNX_DiagnosticTestIBPort Test Aborted

Explanation: Port Test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
408-900-000 MLNX:MLNX_DiagnosticTestEthernetPort 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.
Related Links:
408-901-000 MLNX:MLNX_DiagnosticTestIBPort 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 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.
3. Try replacing the adapter and repeating the test.
Related Links:

201-000-000 • 201-000-002
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
Related Links:

Explanation: Quick/Full Memory Test CPU 1 Passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

201-000-003 • 201-811-000

Severity: Event
Serviceable: No
Recoverable: No
Related Links:

Severity: Event
Serviceable: No
Recoverable: No
Related Links:
201-811-000 Standalone Memory Test Aborted

Explanation: Unable to Locate SMBIOS key "_SM_".
Severity: Warning
Serviceable: No
Recoverable: No
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.
Related Links:

201-811-001 • 201-811-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-811-003 • 201-812-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Memory test is not supported for this system.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-812-001 • 201-812-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-812-003 • 201-813-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Chipset Error: Can not turn OFF ECC error reporting in CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-813-001 • 201-813-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-813-003 • 201-814-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Chipset Error: Can not disable Scubbing feature for CPU.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-814-001 • 201-814-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-814-003 • 201-815-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Program Error with Quick Memory Menu Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-815-001 • 201-815-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-815-003 • 201-816-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Program Error with Full Memory Menu Option Selection.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-816-001 • 201-816-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-816-003 • 201-818-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-818-001 • 201-818-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-818-003 • 201-819-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: The start-end address ranges in the restricted area of the memory.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-819-001 • 201-819-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-819-003 • 201-820-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Memory Upper limit is less than 16 Mbytes.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-820-001 • 201-820-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-820-003 • 201-821-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Variable range MTRR registers are larger than fixed range MTRR registers.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-821-001 • 201-821-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-821-003 • 201-822-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Invalid MTRR service request.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-822-001 • 201-822-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-822-003 • 201-824-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

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
Related Links:

201-824-001 • 201-824-002

the test.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

the test.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-824-003 • 201-826-000

the test.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: BIOS: Memory Controller has been disabled. Go to Setup and Enable Memory Controller.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-826-001 • 201-826-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-826-003 • 201-827-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: BIOS: ECC function has been disabled by BIOS. Go to Setup and enable ECC generation.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-827-001 • 201-827-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-827-003 • 201-844-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Chipset Error: Problem in masking MSR machine check control MASK registers.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-844-001 • 201-844-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-844-003 • 201-845-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Chipset Error: Problem clearing MSR machine check control registers.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-845-001 • 201-845-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-845-003 • 201-859-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: INVALID XSECSRAT type.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-859-001 • 201-859-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-859-003 • 201-860-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No OEM0 type 1 found.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-860-001 • 201-860-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-860-003 • 201-861-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No SRAT type 1 found.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-861-001 • 201-861-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-861-003 • 201-862-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No OEM1 structure found.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-862-001 • 201-862-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-862-003 • 201-863-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No IBMERROR key in OEM1 structure.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-863-001 • 201-863-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-863-003 • 201-864-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No GAS located in OEM1.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-864-001 • 201-864-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-864-003 • 201-865-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: No XSECSRAT key in OEM0 structure.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-865-001 • 201-865-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-865-003 • 201-866-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: EFI-SAL Invalid parameter from GetMemoryMap function.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-866-001 • 201-866-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-866-003 • 201-867-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: EFI/SAL: Buffer not allocated.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-867-001 • 201-867-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-867-003 • 201-868-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: EFI/SAL: Buffer allocated in GetMemoryMap too small.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-868-001 • 201-868-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-868-003 • 201-869-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: EFI/SAL Invalid parameter from GetMemoryMap function.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-869-001 • 201-869-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-869-003 • 201-870-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: CPU Doamin in ACPI not valid.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-870-001 • 201-870-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-870-003 • 201-871-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Data Mis-compare encountered.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-871-001 • 201-871-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-871-003 • 201-877-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: BIOS: Sparing in Extended PCI reg. must be OFF. Go to setup and disable sparing.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-877-001 • 201-877-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-877-003 • 201-878-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Sparing feature must be turned OFF. Go to setup and turn the sparing feature OFF.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-878-001 • 201-878-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-878-003 • 201-885-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Processor does not support MTRR register manipulation. Can not write to memory without cache.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-885-001 • 201-885-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-885-003 • 201-886-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-886-001 • 201-886-002

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-886-003 • 201-899-001

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Explanation: Memory Diagnostics Test Aborted by user.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

201-899-002 • 201-901-000

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
201-901-000 Standalone Memory Test Failed

Explanation: Memory Diagnostics Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
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.
Related Links:

201-901-001 • 201-901-002

Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

201-901-003 • 202-000-000

Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:
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
Related Links:

202-801-000 • 202-802-000
202-801-000 MemStr Test Aborted

Explanation: Internal program error.
Severity: Warning
Serviceable: Yes
Recoverable: No
4. If the system has stopped responding, turn off and restart the system.
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 symptom" in the system "Installation and Service Guide" for
the next corrective action.
Related Links:

Explanation: Memory size is insufficient to run the test. At least 1 GB is required.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

202-803-000 • 202-901-000

Explanation: User pressed Ctrl-C.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:
202-901-000 MemStr Test Failed

Explanation: Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Execute the standard DSA memory diagnostics to validate all memory.
3. Turn off the system and disconnect it from power.
4. Reseat the memory cards and DIMMs.
5. Reconnect the system to power and turn the system on.
Related Links:

202-902-000 • 409-000-000
202-902-000 MemStr Test Failed

Explanation: Memory size is insufficient to run the test.
Severity: Error
Serviceable: Yes
Recoverable: No
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.
Related Links:
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
Related Links:

409-003-000 • 409-005-000
409-003-000 Nvidia::DiagnosticServiceProvider::Bandwidth Test Passed

Explanation: Nvidia GPU Bandwidth test passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
409-004-000 Nvidia::DiagnosticServiceProvider::Query Test Passed

Explanation: Nvidia GPU Query test passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
409-005-000 Nvidia::DiagnosticServiceProvider::Matrix Test Passed

Explanation: Nvidia GPU Matrix test passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:

409-006-000 • 409-803-000
409-006-000 Nvidia::DiagnosticServiceProvider::Binomial Test Passed

Explanation: Nvidia GPU Binomial test passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
409-800-000 NVIDIA User Diagnostic Test Aborted

Explanation: NVIDIA User Diagnostic test was canceled.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:
409-803-000 Nvidia::DiagnosticServiceProvider::Bandwidth Test Aborted

Explanation: Nvidia GPU Bandwidth test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

409-804-000 • 409-806-000
409-804-000 Nvidia::DiagnosticServiceProvider::Query Test Aborted

Explanation: Nvidia GPU Query test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
409-805-000 Nvidia::DiagnosticServiceProvider::Matrix Test Aborted

Explanation: Nvidia GPU Matrix test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:
409-806-000 Nvidia::DiagnosticServiceProvider::Binomial Test Aborted

Explanation: Nvidia GPU Binomial test was canceled.
Severity: Warning
Serviceable: No
Recoverable: No
Related Links:

409-900-000 • 409-903-000
409-900-000 NVIDIA User Diagnostic Test Failed

Explanation: NVIDIA User Diagnostic Test Failed.
Severity: Event
Serviceable: Yes
Recoverable: No
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.
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.
Related Links:
409-903-000 Nvidia::DiagnosticServiceProvider::Bandwidth Test Failed

Explanation: Nvidia GPU Bandwidth Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

409-904-000 • 409-905-000
409-904-000 Nvidia::DiagnosticServiceProvider::Query Test Failed

Explanation: Nvidia GPU Query Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:
409-905-000 Nvidia::DiagnosticServiceProvider::Matrix Test Failed

Explanation: Nvidia GPU Matrix Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

409-906-000 • 215-000-000
409-906-000 Nvidia::DiagnosticServiceProvider::Binomial Test Failed

Explanation: Nvidia GPU Binomial Test Failed.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:
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
Related Links:

215-801-000 • 215-802-000
215-801-000 Optical Drive Test Aborted

Explanation: Optical Drive Test Aborted. Unable to communicate with driver.
Severity: Warning
Serviceable: Yes
Recoverable: No
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.
5. Check system firmware level and upgrade if necessary.The installed firmware level can be found in the DSA
Related Links:

Explanation: Optical Drive Test Aborted. A read error was encountered.
Severity: Warning
Serviceable: Yes
Recoverable: No
1. Insert a new CD or DVD into the drive and wait for 15 seconds for the media to be recognized. Rerun the test.
damage is present.
Related Links:

215-803-000 • 215-804-000
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
Recoverable: No
1. Wait for the system activity to cease
2. Run the test again
Related Links:

Explanation: Optical Drive Test Aborted. The media tray is open.
Severity: Warning
Serviceable: Yes
Recoverable: No
1. Close the media tray and wait for 15 seconds for the media to be recognized. Run the test again.
damage is present.
Related Links:

215-901-000 • 215-902-000

Explanation: Optical Drive Test Aborted. Drive media is not detected.
Severity: Warning
Serviceable: Yes
Recoverable: No
damage is present.
Related Links:
215-902-000 Optical Drive Test Failed

Explanation: Optical Drive Test Failed. Read miscompare.
Severity: Error
Serviceable: Yes
Recoverable: No
damage is present.
Related Links:

215-903-000 • 166-000-001

Explanation: Optical Drive Test Aborted. Could not access the device.
Severity: Warning
Serviceable: Yes
Recoverable: No
damage is present.
4. Check system firmware level and upgrade if necessary.The installed firmware level can be found in the DSA
Related Links:
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
Related Links:

166-801-001 • 166-803-001
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:
1. Turn off the system and disconnect it from power. Wait for 45 seconds. Reconnect it to power.
2. Make sure that DSA and BMC/IMM are at the latest level.
Related Links:

Explanation: Test cannot be completed for unknown reason.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Node Busy. Try later.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-804-001 • 166-806-001

Explanation: Invalid Command.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Invalid Command for given LUN.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Timeout while processing command.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-807-001 • 166-809-001

Explanation: Out of space.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Reservation Canceled or Invalid Reservation ID.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Request data truncated.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-810-001 • 166-812-001

Explanation: Request data length invalid.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Request data field length limit exceeded.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Parameter out of range.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-813-001 • 166-815-001

Explanation: Cannot return number of requested data bytes.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Requested Sensor, data, or record not present.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Invalid data field in Request.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-816-001 • 166-818-001

Explanation: Command illegal for specified sensor or record type.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Command response could not be provided.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Cannot execute duplicated request.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-819-001 • 166-821-001

Explanation: Command response could not be provided. SDR Repository in?update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Command response could not be provided. Device in firmware update mode.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Command response could not be provided. BMC initialization in progress.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-822-001 • 166-824-001

Explanation: Destination unavailable.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Cannot execute command. Insufficient privilege level.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: Cannot execute command.
Severity: Warning
Serviceable: Yes
Recoverable: No
Related Links:

166-901-001 • 166-904-001
166-901-001 IMM I2C Test Failed

Explanation: IMM Indicates failure in RTMM bus (BUS 0).
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: IMM Indicates failure in PCA9543 IO Expander bus (BUS 3).
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

166-905-001 • 166-907-001

Explanation: IMM Indicates failure in MAX7319 IO Expander bus (BUS 4).
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: IMM Indicates failure in Ambient Temperature Sensor bus (BUS 6).
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

166-908-001 • 264-000-000

Explanation: IMM Indicates failure in PCA9557 IO Expander bus (BUS 7).
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:
DSA tape drive test results

The following messages can result when you run the tape drive test.
264-000-000 Tape Test Passed

Explanation: Tape Test Passed.
Severity: Event
Serviceable: No
Recoverable: No
Related Links:

264-901-000 • 264-902-000
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.
Related Links:

Explanation: Tape Test Failed. Media is not detected.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

264-903-000 • 264-904-000

Explanation: Tape Test Failed. Media is not detected.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

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.
Related Links:

264-905-000 • 264-906-000

Explanation: Tape Test Failed. Software error: invalid request.
Severity: Error
Serviceable: Yes
Recoverable: No
2. Check the system firmware level and upgrade if necessary. The installed firmware level can be found in the DSA
Related Links:

Explanation: Tape Test Failed. Unrecognized error.
Severity: Error
Serviceable: Yes
Recoverable: No
7. Check the system firmware level and upgrade if necessary.
Related Links:

264-907-000 • 264-908-000

Explanation: An error was found in the block address somewhere.
Severity: Error
Serviceable: Yes
Recoverable: No
Related Links:

Explanation: An error was found in getting tape capacity.
Severity: Error
Serviceable: Yes
Recoverable: No
1. Make sure that medium is present.
Related Links:

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.

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

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 983

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.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and
service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the web at http://www.ibm.com/

legal/us/en/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 and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
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.
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.
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.
Table 40. 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
Notices 987
Table 40. Limits for particulates and gases (continued)
Contaminant Limits
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.
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
When you attach a monitor to the equipment, you must use the designated
monitor cable and any interference suppression devices that are supplied with the
monitor.
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 réglementation d'Industrie Canada

Cet appareil numérique de la classe A est conforme à la norme NMB-003 du
Canada.
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.
Notices 989
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
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: [email protected]
Germany Class A statement

Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie
zur Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie

2004/108/EG zur Angleichung der Rechtsvorschriften über die elektromagnetische
Verträglichkeit in den EU-Mitgliedsstaaten und hält die Grenzwerte der EN 55022
Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu

installieren und zu betreiben. Des Weiteren dürfen auch nur von der IBM
empfohlene Kabel angeschlossen werden. IBM übernimmt keine Verantwortung für
die Einhaltung der Schutzanforderungen, wenn das Produkt ohne Zustimmung der
IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung der IBM gesteckt/eingebaut werden.
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:

Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im
Wohnbereich Funk-Störungen verursachen; in diesem Fall kann vom Betreiber
verlangt werden, angemessene Maßnahmen zu ergreifen und dafür aufzukommen.
Deutschland: Einhaltung des Gesetzes über die

elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem Gesetz über die elektromagnetische Verträglichkeit

von Geräten (EMVG). Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in
der Bundesrepublik Deutschland.

Zulassungsbescheinigung laut dem Deutschen Gesetz über die
elektromagnetische Verträglichkeit von Geräten (EMVG) (bzw. der
EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das
EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp.

New Orchard Road
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: +49 7032 15 2941
Email: [email protected]
Generelle Informationen:
Das Gerät erfüllt 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 991
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

Taiwan Class A compliance statement
Notices 993
Index
Numerics battery, system (continued)
replacing 347
configuring hardware 150
configuring your server 149
16 x 2.5-inch Hot-Swap HDD Assembly before you install a legacy operating connecting
Kit with Expander for 12Gb RAID system 153 cable 146
installing 92 bezel connector
16x2.5-inch Hot-Swap HDD Assembly Kit removing 266 USB 17
for 12Gb/6Gb RAID replacing 266 video
installing 104 blue-screen capture feature front 17
2 x 8 1.8-inch SSDs with two 6 GB overview 163 connectors
performance optimized HBA adapters blue-screen feature 163 external 31
option, installing 116 Boot Manager 161 internal 30
240 VA safety cover Boot Manager program 150 options on the system board 34
removing 267 button, presence detection 19 PCI riser-card adapter 35
replacing 268 buttons contamination, particulate and
4 x 8 1.8-inch SSDs with two 6 GB system board 32 gaseous 987
performance optimized HBA adapters controller
option, installing 123 Ethernet 167
8 Pac HDD option, installing 86
8 Pac HDD with a ServeRAID adapter C controls and LEDs
light path diagnostics panel 20
option, installing 97 cable
operator information panel 19
8 Pac HDD with two 6 GB performance connecting 146
controls, LEDs, and power 17
optimized HBA adapters option, cabling 249
cooling 11
installing 110 3.5-inch drive backplane 257
cover
DVD drive 250
removing 39, 259
front
replacing 145, 260
A USB connector 251
video connector 251
creating a personalized support web
ABR, automatic boot recovery 233 page 983
AC power-supply custom support web page 983
the 16x2.5-inch hot-swap drive
LEDs 192 backplane 255
AC power-supply LEDs 192 the 8x2.5-inch hot-swap drive
accessible documentation 988 backplane 254 D
acoustical noise emissions 7 VGA 253 danger statements 6
Active Energy Manager plug-in 11 call home feature data collection 177
active memory 11 IBM Electronic Service Agent 203 DC power-supply
adapter call home tools 202 LEDs 193
installing 64 Canada Class A electronic emission DC power-supply LEDs 193
removing 304 statement 989 deassertion event, system-event log 196
replacing 305 caution statements 6 device drivers 161
adapter, installation 64 checkout procedure 180 devices, static-sensitive
adapter, supported 64 performing 181 handling 39
administrator China Class A electronic emission diagnostic
password 160 statement 992 on-board programs, starting 201
air baffle Class A electronic emission notice 989 tools, overview 182
removing 42, 261 collecting data 177 diagnostic codes and messages
replacing 143, 262 completing POST/UEFI 827
ASM event log 197 options installation 142 diagnostics
assertion event, system-event log 196 components program overview 199
assistance, getting 981 server 29, 235 diagnostics program
attention notices 6 configuration DSA Preboot 11
Australia Class A statement 989 information 149 dimension 7
automatic boot recovery (ABR) 233 instructions 149 DIMM
availability, server 15 Nx-boot failure 234 installing 54, 61, 289
ServerGuide Setup and Installation memory
CD 149 two-DIMM-per-channel
B Setup utility 149 (2DPC) 54, 289
backup firmware configuration cable, removing 288
starting 161 routing 254, 255, 257 replacing 297
battery holder, RAID adapter configuration programs 150 two-DIMM-per-channel (2DPC)
replacing 265 configuring requirement 54, 289
battery, system RAID arrays 167 DIMM installation sequence 58, 293
removing 345 with ServerGuide 153 memory mirrored channel 59, 294

DIMM installation sequence (continued) error symptoms (continued) guidelines
rank sparing 60, 296 hypervisor flash device 207 options installation 36
display problems 212 intermittent 208 system reliability 38
documentation 5 keyboard 208
CD 4 memory 210
Documentation Browser 4
format 988
microprocessor 211
monitor 212
H
handling static-sensitive devices 39
updates 1 mouse 208
hard disk drive
using 982 network connection 214
activity LED 17
documentation, updated optional devices 214
problems 205
finding 5 power 216
status LED 17
drive serial port 224
hardware
IDs 45 ServerGuide 224
requirements 4
installing 44 software 225
hardware RAID cable,
drive backplane, 16x2.5-inch hot-swap USB port 226
routing 254, 255, 257
cabling 255 USB-device 208
hardware service and support telephone
drive backplane, 3.5-inch video 212, 226
numbers 983
cabling 257 errors
hardware, configuring 150
drive backplane, 8x2.5-inch hot-swap format, DSA code 202
heat sink
cabling 254 Ethernet 11
installing 134
DSA 28 controller 228
removing 351
edition 200 Ethernet activity
replacing 356
program, overview 199 LED 19
heat-sink retention module
test log, viewing 202 Ethernet controller configuration 150
removing 365
text message format 202 Ethernet support 11
replacing 366
DSA log 196, 197 European Union EMC Directive
help
DSA Portable 182, 200 conformance statement 990
from the World Wide Web 982
DSA Preboot 182, 200 event log 196
from World Wide Web 982
DSA, sending data to IBM 28, 982 viewing 197
sending diagnostic data to IBM 28,
dual-port network adapter event log, POST 196
982
installing 73 event log, system 196
sources of 981
removing 318 event logs
hot-swap ac power supply
replacing 319 clearing 198
installing 76
DVD event logs, methods for viewing 197
removing 322
drive activity LED 17 external connectors 31
replacing 324
eject button 17
hot-swap dc power supply
DVD drive
installing 79
cabling 250
installing 49
F replacing 330
fan bracket hot-swap drive backplane
problems 204
removing 298 removing 338, 340
removing 278
replacing 300 replacing 339
replacing 279
fans 11 simple-swap drive backplate
DVD drive cable
FCC Class A notice 989 assembly 339
installing 52
features 7 simple-swap drive backplate assembly
removing 282
ServerGuide 153 replacing 339
replacing 283
Features on Demand 11 hot-swap fan
Dynamic System Analysis 28
finding installing 84
Dynamic System Analysis (DSA) Preboot
updated documentation 5 removing 336
diagnostics program 11
firmware replacing 337
updates 1 hot-swap hard disk drive
firmware updates 1 installing 45
E firmware, server, recovering 231 replacing 271
electronic emission Class A notice 989 firmware, updating 149 hot-swap hard disk drives
embedded hypervisor front removing 270
using 166 view 17 hypervisor flash device
enabling front view problems 207
Features on Demand connectors 17
Ethernet software 167 LED location 17
RAID software 167
Enterprise X-Architecture technology 11
I
IBM Advanced Settings Utility program
error codes and messages
IMM2 373
G overview 168
gaseous contamination 987 IBM Electronic Service Agent 203
error messages 203
general IBM Systems Director 11
error symptoms
problems 205 systems management tool 16
DVD drive 204
Germany Class A statement 990 updating 168
general 205
grease, thermal 141, 364 IBM Taiwan product service 983
hard disk drive 205

IDs intermittent memory mirrored channel (continued)
drive 45 problems 208 DIMM population sequence 59, 294
IMM host name 164 internal connectors 30 memory module
IMM web interface 165 introduction 1 installing 54, 289
IMM2 150 IP address for the IMM 164 removing 288
error messages 373 IPMI event log 196, 197 memory rank sparing
IMM2 heartbeat IPMItool 197 description 60, 296
LED 195 memory support 11
important notices 6, 986 menu choices
in-band
automated boot recovery
J Setup utility 155
messages, diagnostic
Japan Class A electronic emission
method 233 POST/UEFI 827
statement 991
manual recovery method 231 method 233
Japan Electronics and Information
information center 982 methods, viewing event logs 197
Technology Industries Association
installation microprocessor 11
statement 992
guidelines 36 installing 134
JEITA statement 992
installation guidelines 36 problems 211
jumper
installation, options removing 351
UEFI boot recovery 231
completing 142 replacing 356
jumpers
installing mirrored channel mode 59, 294
system board 32
16 x 2.5-inch Hot-Swap HDD model name
Assembly Kit with Expander for location 230
12Gb RAID 92
16x2.5-inch Hot-Swap HDD Assembly K
Kit for 12Gb/6Gb RAID 104
2 x 8 1.8-inch SSDs with two 6 GB
Korea Class A electronic emission
statement 992
N
New Zealand Class A statement 989
performance optimized HBA
NMI button 21
adapters option 116
NOS installation
4 x 8 1.8-inch SSDs with two 6 GB
performance optimized HBA
L with ServerGuide 153
LED without ServerGuide 154
adapters option 123
DVD drive activity 17 notes 6
a PCI riser-card assembly 144
Ethernet activity 19 notes, important 986
adapter 64
hard disk drive activity 17 notices 985
DIMM 54, 61, 289
hard disk drive status 17 electronic emission 989
drive 44
IMM2 heartbeat 195 FCC, Class A 989
dual-port network adapter 73
power-on 19 notices and statements 6
DVD drive 49
RTMM heartbeat 195 Nx-boot failure 234
DVD drive cable 52
system information 19
heat sink 134
system locator 19
hot-swap ac power supply 76
hot-swap dc power supply 79
LEDs
system-error 19 O
hot-swap fan 84 obtaining 164
AC power-supply 192
hot-swap hard disk drive 45 online documentation 1
DC power-supply 193
memory module 54, 289 online publications 5
on the PCI riser-card 195
microprocessor 134 operating-system event log 196, 197
power-supply 191
optional devices 27 operator information panel
SAS/SATA 8 Pac HDD option 86 cabling 252
system board 34
SAS/SATA 8 Pac HDD with a controls and LEDs 19
legacy operating system
ServeRAID adapter option 97 removing 349
requirement 153
SAS/SATA 8 Pac HDD with two 6 GB replacing 350
License Agreement for Machine Code 5
performance optimized HBA operator information panel release
Licenses and Attributions Documents 5
adapters option 110 latch 17
light path diagnostics 11, 184
ServeRAID adapter remote optional device problems 214
LEDs 187
battery 70 optional devices
panel 184
ServeRAID upgrade adapter 69 installing 27
light path diagnostics panel
simple-swap hard disk drives 46 optional devices connectors
controls and LEDs 20
tape drive option 130 system board 34
location 17
USB hypervisor flash device 133 out-of-band 233
local area network (LAN) 11
instructions
logging 165
IBM Business Partners 28
integrated management module
overview 11
P
using 162 M particulate contamination
parts listing 235
987
integrated management module II management, system 11
parts, structural 246
error messages 373 memory 11
password 159
event log 196, 197 memory mirrored channel
administrator 159
programs 150 description 59, 294
power-on 159
Index 997
password, power-on
switch on system board 159
R removing (continued)
ServeRAID upgrade adapter memory
PCI rack release latches 17 module 308
riser-card assembly 302 RAID adapter simple-swap drive backplate
PCI riser slots battery holder assembly 338, 340
installation configurations 305 replacing 265 simple-swap hard disk drives 273
supported configurations 305 remote battery system board 367
PCI riser-card removing 313 tape drive 286
LEDs location 195 replacing 315 USB hypervisor flash device 343
PCI riser-card assembly remote battery holder Replaceable server components 235
installing 144 removing 264 replacing
removing 40, 301 RAID arrays 240 VA safety cover 268
replacing 302 configuring 167 adapter 305
PCI riser-card assembly (full-length) rank sparing air baffle 143, 262
stretching 43 DIMM population sequence 60, 296 battery, system 347
PCI riser-card assembly (half-length) rank sparing mode 60, 296 bezel 266
shrinking 44 RAS features, server 15 components 249
People's Republic of China Class A rear cover 145, 260
electronic emission statement 992 view 21 DIMM 297
POST rear view dual-port network adapter 319
event log 197 connectors 21 DVD drive 279
POST event log 196 LED location 21 DVD drive cable 283
POST/UEFI recovering the server firmware 231 fan bracket 300
diagnostic codes 827 redundant heat sink 356
power cooling 11 heat-sink retention module 366
power-control button 19 Ethernet connection 11 hot-swap ac power supply 324
power cable, NIC 11 hot-swap dc power supply 330
routing 254, 255, 257 Redundant hot-swap drive backplane 339
power cords 247 Ethernet capabilities 15 hot-swap fan 337
power features hot-swap power supplies 15 hot-swap hard disk drive 271
server 24 reliability, server 15 microprocessor 356
power problems 216, 226 remind button 20, 184 operator information panel 350
power-on LED 19, 24 remote battery holder, RAID adapter PCI riser-card assembly 302
power-supply removing 264 RAID adapter battery holder 265
LEDs 191 remote battery, RAID adapter RAID adapter remote battery 315
power-supply LEDs 191 removing 313 server components 258
presence detection button 19 replacing 315 ServeRAID upgrade adapter memory
problems remote battery, ServeRAID adapter module 311
DVD drive 204 installing 70 simple-swap drive backplate
Ethernet controller 228 remote presence feature assembly 341
general 205 using 163 simple-swap hard disk drives 274
hard disk drive 205 removing structural parts 258
hypervisor flash device 207 240 VA safety cover 267 system board 370
IMM2 373 a PCI riser-card assembly 40, 301 tape drive 287
intermittent 208 adapter 304 Tier 1 CRUs 270
keyboard 208 air baffle 42, 261 Tier 2 CRUs 351
memory 210 battery, system 345 USB hypervisor flash device 344
microprocessor 211 bezel 266 reset button 20, 184
monitor 212 components 249 returning
mouse 208 cover 39, 259 component 249
network connection 214 DIMM 288 device 249
optional devices 214 dual-port network adapter 318 riser-card assembly
power 216, 226 DVD drive 278 LEDs 36
serial port 224 DVD drive cable 282 routing
ServerGuide 224 fan bracket 298 the configuration cable 254, 255, 257
software 225 heat sink 351 the hardware RAID cable 254, 255,
undetermined 229 heat-sink retention module 365 257
USB port 226 hot-swap ac power supply 322 the power cable 254, 255, 257
video 212, 226 hot-swap dc power supply 327 RTMM heartbeat
procedure, checkout 181 hot-swap drive backplane 338, 340 LED 195
product service, IBM Taiwan 983 hot-swap fan 336 Russia Class A electronic emission
publications hot-swap hard disk drive 270 statement 992
online 1 memory module 288
product data 1 microprocessor 351
RAID adapter battery holder 264 S
RAID adapter remote battery 313 safety vii
Safety Information 6

safety statements vii, ix simple-swap hard disk drives (continued) tools, diagnostic 182
SAS/SATA 8 Pac HDD option replacing 274 trademarks 986
installing 86 size 7 troubleshooting 177
SAS/SATA 8 Pac HDD with a ServeRAID SMP 11 symptom 203
adapter option software turning off the server 24
installing 97 requirements 4 turning on the server 24
SAS/SATA 8 Pac HDD with two 6 GB software problems 225
performance optimized HBA adapters software service and support telephone
option
installing 110
numbers 983
specifications 7
U
UEFI
sending diagnostic data to IBM 28, 982 starting
boot recovery jumper 231
serial number 1 Setup utility 154
undetermined problems 229
location 230 the backup firmware 161
undocumented problems 179
serial port problems 224 statements and notices 6
United States FCC Class A notice 989
server static-sensitive devices
Universal Serial Bus (USB) problems 226
offerings 11 handling 39
UpdateXpress 149, 161
power features 24 stretching
updating
turning off 24 full-length PCI riser-card
firmware 149
turning on 24 assembly 43
IBM Systems Director 168
server , backup firmware structural parts 246
server configuration 147
starting 161 support web page, custom 983
Systems Director, IBM 168
server components 29, 235 switches
Universal Unique Identifier
server configuration system board 32
(UUID) 170, 172
updating 147 symmetric multiprocessing 11
USB
server controls, LEDs, and power 17 system
connector 17
server firmware, recovering 231 error LED front 19
USB hypervisor flash device
server shutdown 24 locator LED, front 19
installing 133
ServeRAID adapter System
removing 343
remote battery information LED 19
replacing 344
installing 70 system board
using
ServeRAID support 11 buttons 32
embedded hypervisor 166
ServeRAID upgrade adapter external connectors 31
integrated management module 162
installing 69 internal connectors 30
Setup utility 154
ServeRAID upgrade adapter memory jumpers 32
the remote presence feature 163
module LEDs 34
Utility program
replacing 311 power-on password switch 159
IBM Advanced Settings 168
ServeRAID upgrade adapter memory removing 367
utility, Setup 150
moduler replacing 370
starting 154
removing 308 switches 32
using 154
ServerGuide 11 system board optional devices
features 153 connectors 34
NOS installation 153 system event log 197
setup 153 system pulse LEDs 195 V
Setup and Installation CD 149 system reliability guidelines 38 video connector
using 152 system-event log 196 front 17
ServerGuide CD 1 system-event log, assertion event 196 viewing event log 197
service and support system-event log, deassertion event 196 VMware Hypervisor support 150
before you call 981 systems management 11
hardware 983 systems management tool
software 983
service bulletins 180
IBM Systems Director 16 W
Wake on LAN feature 24
serviceability, server 15
weight 7
Setup utility 149, 150
menu choices 155
T what the server offers 11
Taiwan Class A electronic emission working inside the server
starting 154
statement 993 power on 38
using 154
tape drive
shrinking PCI riser-card assembly 44
removing 286
shutting down the server 24
simple-swap drive backplate assembly
replacing 287
tape drive option
X
hot-swap drive backplane X-Architecture technology 11
installing 130
replacing 341
tape drive option, installing 130
removing 338, 340
telecommunication regulatory
replacing 341
statement 988
hot-swap drive backplane 341
telephone numbers 983
simple-swap hard disk drives
test log, viewing 202
installing 46
thermal grease 141, 364
removing 273
tools, call home 202
Index 999

Part Number: 00KC243
Printed in USA
(1P) P/N: 00KC243

x3650 m4 Troubleshooting

Uploaded by

Copyright:

Available Formats

x3650 m4 Troubleshooting

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

x3650 m4 Troubleshooting

Uploaded by

Copyright:

Available Formats

Fourteenth Edition (August 2014)

© Copyright IBM Corp. 2014 iii

iv System x3650 M4 Type 7915: Installation and Service Guide

vi System x3650 M4 Type 7915: Installation and Service Guide

Antes de instalar este produto, leia as Informações de Segurança.

Læs sikkerhedsforskrifterne, før du installerer dette produkt.

Lees voordat u dit product installeert eerst de veiligheidsvoorschriften.

Avant d'installer ce produit, lisez les consignes de sécurité.

Vor der Installation dieses Produkts die Sicherheitshinweise lesen.

Prima di installare questo prodotto, leggere le Informazioni sulla Sicurezza.

© Copyright IBM Corp. 2014 vii

Antes de instalar este produto, leia as Informações sobre Segurança.

Antes de instalar este producto, lea la información de seguridad.

Läs säkerhetsinformationen innan du installerar den här produkten.

viii System x3650 M4 Type 7915: Installation and Service Guide

Each caution and danger statement in this documentation is labeled with a

For example, if a caution statement is labeled Statement 1, translations for that

Electrical current from power, telephone, and communication cables is

To avoid a shock hazard:

1. Turn everything OFF. 1. Turn everything OFF.

Dispose of the battery as required by local ordinances or regulations.

x System x3650 M4 Type 7915: Installation and Service Guide

≥ 18 kg (39.7 lb) ≥ 32 kg (70.5 lb) ≥ 55 kg (121.2 lb)

xii System x3650 M4 Type 7915: Installation and Service Guide

Rack Safety Information, Statement 2

v Always lower the leveling pads on the rack cabinet.

In addition to the instructions in Chapter 2, “Installing optional devices,” on page

Performance, ease of use, reliability, and expansion capabilities were key

The server contains IBM X-Architecture® technologies, which help increase

© Copyright IBM Corp. 2014 1

SAS hard disk

Figure 1. 3.5-inch hot-swap model front view

SATA hard disk

Figure 2. 3.5-inch simple-swap model front view

SAS hard disk

Figure 3. 2.5-inch model front view

You can purchase an optional kit to install the tape drive.

SAS hard disk

Figure 4. Tape drive model front view

2 System x3650 M4 Type 7915: Installation and Service Guide

Figure 5. 16-drive-capable model front view

Record information about the server in the following table.

Product name IBM System x3650 M4 server

Chapter 1. The System x3650 M4 server 3

The IBM Documentation CD

Hardware and software requirements

The IBM Documentation CD requires the following minimum hardware and

The IBM Documentation CD

The Documentation Browser automatically detects the regional settings in use in

Use one of the following procedures to start the Documentation Browser:

4 System x3650 M4 Type 7915: Installation and Service Guide

When you select a document, a description of the document is displayed under

The following documentation also comes with the server:

Chapter 1. The System x3650 M4 server 5

Depending on the server model, additional documentation might be included on

Notices and statements in this document

The following notices and statements are used in this document:

6 System x3650 M4 Type 7915: Installation and Service Guide

Chapter 1. The System x3650 M4 server 7